Database Develop

[Patch][ALE-L21][B594] How to Get back Google Device Certification

UPDATE – 07.03.2017
This patch is no longer required to have Google Device Certification.
After install ROM B594 no further actions are required.
Thanks to "who" did this correction … and I hope somehow this thread helped to speed up solving this mismatching.
Note:
I created a new flashable zip to set original B594 local.prop in case of someone want revert the patch without install the complete ROM
_____________________________
_____________________________
WARNING: I'M NOT RESPONSIBLE FOR SCREWING UP YOUR PHONE
If you are not used to solve soft-brick don't play with this.
After installation of new stock ROM ALE-L21C432B594
- Device become uncertified
- SaftyNet status fail, due to CTS profile mismatch
How to get back device certification and CTS profile match?
- You have to change Fingerprint from B594 to B588 (at least worked to me)
- File to change => local.prop
- Location => /cust/hw/eu/prop
- See image enclosed how to change it
- After you aplied this, unroot your device, run the Safety Net test, check Play Store Settings and check if it works
- I created flashable zip in case your device is not rooted but you have TWRP installed

Thanks, it worked for me
Btw. You can root with magisk to pass SafetyNet with root.

Ok, if we don't have open bootloader, we should wait until certificated automatically? It's just the number, so it's maybe just not documented by Google, right? Hope so

If you're not rooted and do not have a custom recovery, how do you apply this?
I've extracted CUST.img from the UPDATE.APP, edited the file and rebuilt the image. Can I just use fastboot to flash it?

@proze.za
Try first without this patch. I have changed this line back and I can still pass SafetyNet. What's more my device is certified...
You need unlocked bootloader to flash cust.img and if you have unlocked bl you can just flash TWRP.

dominj97 said:
@proze.za
Try first without this patch. I have changed this line back and I can still pass SafetyNet. What's more my device is certified...
You need unlocked bootloader to flash cust.img and if you have unlocked bl you can just flash TWRP.
Click to expand...
Click to collapse
You're right. I just checked and my device is certified with B594.

proze.za said:
You're right. I just checked and my device is certified with B594.
Click to expand...
Click to collapse
So B594 it's certified? Or you did something?

Azzureux said:
So B594 it's certified? Or you did something?
Click to expand...
Click to collapse
I just installed the full B594 update (placed UPDATE.APP in dload on an sdcard, etc). And it says it is certified.

Now CTS is passed without change anything. SafetyNet-Check completly passed, but in Play Store uncertificated. No problems at all

First post updated

After full rom reflash I get no "uncertified" message

Audriuskins said:
After full rom reflash I get no "uncertified" message
Click to expand...
Click to collapse
You want tell us that we just have to update from B594 to B594 to get certificated back?
Edit: I have tried, but that isn't working. So I have to live with that.

dominj97 said:
Thanks, it worked for me
Btw. You can root with magisk to pass SafetyNet with root.
Click to expand...
Click to collapse
Thanks for the hint :good:
I tried and it works

Works, too. Closed Bootloader, no root. Uncertificated is shown on Play Store, but everything is passed since monday.

allrightlite said:
Works, too. Closed Bootloader, no root. Uncertificated is shown on Play Store, but everything is passed since monday.
Click to expand...
Click to collapse
Monday! I thought it was on Tuesday, but anyway, what was tested this time was only if SafetyNet passed on the device with root.
Like dominj97 mention on his post it works if I make root with Magisk.
I tested with SuperSU, Suhide, Superuser, but in my case only worked with Magisk.

Thread closed as per OP request.
Forum moderator,
Matt

Kernel with dm-verity disabled?

Since the sources are out, is there a kernel with dm-verity disabled?
I want to be able to root and keep TWRP, make some changes (hosts, restore some titaniumbackup files), unroot and still pass the checks, which normally fails due to safetynet detecting the unlocked bootloader. If I understood correctly, disabling dm-verity will allow safetynet to pass even with unlocked BL?
Or is that outdated info?

I pass safetynet with an unlocked bootloader,TWRP and root (Magisk). Just install the MagiskHide Props Config module via Magisk Manager->Modules and in a terminal type:
su
props
and apply the fix and select mate 10 as device

I'm trying to avoid using magisk to avoid losing safetynet access when an update comes. I really only need root once.

I believe you can fully uninstall magisk and pass safetynet as it was stock again

No, unfortunately not, since safetynet detects the unlocked bootloader.

Arak0n said:
No, unfortunately not, since safetynet detects the unlocked bootloader.
Click to expand...
Click to collapse
Oh sorry didn't knew that, thought maybe just using unsu.zip would do the trick

When I get onto huawei with a legal threat of GPL violation, hopefully the kernel sources will build a working bootable image, rather than the broken, unbootable one I have installed right now. Side note: I need the working stock kernel & ramdisk if anyone has it.
Sent from my kminiltexx using XDA Labs

hackintosh5 said:
When I get onto huawei with a legal threat of GPL violation, hopefully the kernel sources will build a working bootable image, rather than the broken, unbootable one I have installed right now. Side note: I need the working stock kernel & ramdisk if anyone has it.
Sent from my kminiltexx using XDA Labs
Click to expand...
Click to collapse
Can't you use Huawei Firmware Finder and Huawei Update Extractor to get stock kernel & ramdisk? I could send you these extracted from an full OTA update.zip. What I can't do is send you these files extracted from my phone because it took a long time going back to stock and get safetynet running, so I don't want to risk that by unlocking the bootloader and flashing twrp again. Just tell me if the extracted files would be enough for you.

kaiomatico said:
Can't you use Huawei Firmware Finder and Huawei Update Extractor to get stock kernel & ramdisk? I could send you these extracted from an full OTA update.zip. What I can't do is send you these files extracted from my phone because it took a long time going back to stock and get safetynet running, so I don't want to risk that by unlocking the bootloader and flashing twrp again. Just tell me if the extracted files would be enough for you.
Click to expand...
Click to collapse
The files are great, but, sorry to tell you, someone else already sent them to me.
However, there's good news, I got Honor Support to escalate my request to a supervisor so maybe someone will actually give me sources now! Yay.

Magisk root S10e

Hi all
On the S10e is a problem by the rooting part from magisk. The approach with 'system-as-root' will not work.
It look likes, that the system not load the new ramdisk.packed. The hex-patch for skip_initramfs > want_* works.
The dt.img patch has also an error. This img must be manualy add to the boot.img for the hex-patches.
Has any one a fix?
*On the G970U works the approach.

Are you using Canary magisk ?
https://www.xda-developers.com/magisk-canary-update-support-aonly-system-root-android-pie/

spartanz51 said:
Are you using Canary magisk ?
https://www.xda-developers.com/magisk-canary-update-support-aonly-system-root-android-pie/
Click to expand...
Click to collapse
Yes. On the new s10 are no ramdisks included in the boot.img. So the 'system-as-root' is the way to go.
*On the actual magisk source, is an error for the dtb-patch.

sq_dev said:
Yes. On the new s10 are no ramdisks included in the boot.img. So the 'system-as-root' is the way to go.
*On the actual magisk source, is an error for the dtb-patch.
Click to expand...
Click to collapse
You use Canary or Official Magisk??
Cause on Canary there is a fix for system-as-root support

spartanz51 said:
You use Canary or Official Magisk??
Cause on Canary there is a fix for system-as-root support
Click to expand...
Click to collapse
Yes I have try both.
Now is the kernel available. I will check the functions.

How can you root without custom recovery?
Maybe I'm missing something cos I always root with TWRP + Magisk!

Lord Spectre said:
How can you root without custom recovery?
Maybe I'm missing something cos I always root with TWRP + Magisk!
Click to expand...
Click to collapse
With Odin

spartanz51 said:
With Odin
Click to expand...
Click to collapse
Thank you for reply. Could you please point me to the magisk package I have to flash with odin?
Is it ok the following one?
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json

Subscribed, wanting to root my 970u
Sent from my SM-G970U using Tapatalk

That's all quite interesting. I wonder if Magisk will also work with my Chinese Snapdragon S10+, or if something specific needs to be done for the particular architecture. I downloaded the zip file that's supposed to be installed and saw in boot_patch.sh that some changes are to be made in binary files. If those binaries are the same for both Exynos and Snapdragon, it should work on both, and if not, then my phone probably wouldn't boot because the binaries would be corrupt.
One of my questions is: were those patches based on compiling the kernel source code released by Samsung, or reverse engineering the binaries? Because if it's based on compiling from source with a couple modifications and then finding the difference with the stock binaries, it's less work than reverse engineering the binaries.

This is the only reason I got Exynos S10. Last year, it took a while for Chinese Snapdragon S10 root. Also Pie update was released first week of this year for Exynos whereas for SD it took them another month and a half.

[2022][ROOT] [Extreme Syndicate] [G960U/U1/W][G965U/U1/W][N960U/U1/W]

Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Below Method is no longer supported if you choose to use the unstable method below you do so on your own
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Before Starting This Process Get A USB2 Mini Hub You Are Most Likely Going Too Need It​
EXTREME SYNDICATE ROOT METHOD
​OEM Toggle Does Nothing On US Model Phones
This root method breaks things and most likely will not be able to be used as a daily driver
You can be on any version bootloader. This will update you to V9 bootloader
This method will work if you are on Android 10 or Android 9 Pie but will put you on Android 8 Oreo. There is no root for Android 10 or Android 9 Pie
You will not be able to use magisk
You will not be able to flash full custom rom like Lineage or any other AOSP roms however GSI system images can be used
You cannot flash custom boot images or recovery images such as regular TWRP
Odin does not work on some later computers with USB 3.1 chip controllers the only work around is using a USB 2.0 mini hub
It is your responsibility to make sure you can use adb properly
Root will break things such as safetynet so deal with it
Disclaimer:
The Extreme Syndicate team and it's affiliates are not responsible for your actions or your device if any issues are to arise. You flash this and utilize these files at your own risk. You have been warned!
Notes:
- Safestrap recovery is now available with working MTP while in Safestrap
- This does NOT trip KNOX so don't ask.
- Bootloader is of course still locked.
- This uses some partitions from combo firmware which means 80% battery.
- Each variant will have its own post in its own download section. Download the right stuff!
* Variants this should work on are: N960U/U1/W, G965U/U1/W, G960U/U1/W. If you do not have one of these variants then this forum is not for you!
- Initial files/method will leave you on Oreo stock root.
- It works on latest rev's from rev1 up to the most recent revs.
- As of the initial first release, all variants have an issue with MTP not working except while in Safestrap
- S9 and S9+ also might have some issues with the selfie cam.
- Note 9 @elliwigy
- S9+ @klabit87
- S9 @jrkruse
- Telegram Support Group for All 3: https://t.me/joinchat/DxwvAlhtzHjg4EI9973BGQ
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed as a zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Downloads S9 Files:
Safestrap_S9_Cmd_Line.7z
Download S9+ Files:
Safestrap_S9_Plus_Cmd_Line.7z
Download Note9 Files: -- Only For Bit 8 Or Lower
Safestrap_N9_Cmd_Line_Bit8.7z
Instructions to Inject Safestrap:
1. Download and unzip Safestrap_S9__Cmd_Line.7z for your device
2. Plug phone into computer and run Safestrap.exe
3. Follow instructions on screen to enable USB Debugging
4. Then from there the process will be mostly automatic just follow prompts on screen
5. When done flashing BootSwap file you need to hold the buttons to boot to recovery but since we swapped boot and recovery images it will boot system.
Instructions For Flash Rom:
1. Download below files and copy files for rom to phone system img and vendor img and odm zip
Downloads S9 Files:
Stock_Rom_G960.7z
GSI_Rom_G960.7z
Download S9+ Files:
Stock_Rom_G965.7z
GSI_Rom_G965.7z
2. In safestrap flash system img then vendor img and odm zip .
3. Choose data wipe and advance and check data
4.. Now reboot system you will have to hold buttons to reboot to recovery until you see safestrap splash then click continue. You must do this on every reboot. If you do not it will reboot to stock recovery. If it reboots to stock recovery just reboot system and hold buttons to reboot to recovery again.
5. When rom is booted up your computer will not recognize the phone for mtp file transfer. Adb does still work so you can transfer stuff that way (you need to switch to ptp transfer method in the dropdown) or use USB adapter and use a thumb drive.
6. Biometrics do not work so don’t try to setup fingerprint or face recognition.
The GSI rom mtp works GSI rom is rooted already just flash phhsupersu.apk found in GSI_Rom zip
If using other GSI roms you have too choose A_Only ones and will probably need to flash the Sh_Remover.zip found in the GSI_Rom zip
ShoutOuts:
@elliwigy For the method and help and everything else
@klabit87 - Ditto
@me2151 - Ditto
@gsm-CHEN - Ditto
@mweinbach - For always posting my achievements on the XDA News portal as well as giving me someone to troll sometimes when bored.
@ShaDisNX255 - He was our best tester, give him credits for testing out GSI as well!
@everyone else I am forgetting!
ENJOY!

Mine

Wow, this is actually pretty good. S9 Snapdragon + treble enabled device? Man, this is going to change everything! I hope something good comes out of this

Does it work on the U/U1 variants of the S9+ as well?

krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified

krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It’s confirmed working on both SM-G960U/U1 and SM-G965U/U1
Sent from some device I modified

Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.

Argyrus said:
Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.
Click to expand...
Click to collapse
You cannot trip knox on a locked bootloader
Sent from some device I modified

jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?

Argyrus said:
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?
Click to expand...
Click to collapse
Did you not read la couple post above yoir question
Sent from some device I modified

jrkruse said:
Did you not read la couple post above yoir question
Sent from some device I modified
Click to expand...
Click to collapse
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.

Argyrus said:
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.
Click to expand...
Click to collapse
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified

jrkruse said:
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified
Click to expand...
Click to collapse
Awesome, sorry for any confusion.

jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
jrkruse said:
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified
Click to expand...
Click to collapse
That means I can have root and have Samsung pay? God damn that makes me wet

Dhdeanha said:
That means I can have root and have Samsung pay? God damn that makes me wet
Click to expand...
Click to collapse
As of right now it's still detecting su binaries. So Samsung Pay probably may not work.

On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?

elguy said:
On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?
Click to expand...
Click to collapse
Don't worry about it. It will work on it, it's been proven to work exactly on Android 9, Dec 2019 security patch.

Wow! that's exciting, I can't wait until this releases. Looks like I'm not updating my phone anymore until then. Especially exciting if it works on Android 9 December 2019 security patch

the question is how likely this will be patched in Samsung's next update and how much time this may cause them to delay their next security patch.

Extreme Syndicate Root for S9 is live!!

ANDROID 11

Which custom rom is best for redmi note 8 in ANDROID 11

Opinions are different from person to person. You should do a research on this subject then choose anything to your taste. Easier this way than asking someone. In this way you'll gain knowledge and you'll be able to provide tips and advises to others.
Anyway, you should stay away from the latest update to A11 from Xiaomi!!! The official update is garbage!!! I regret so much doing this step... lost some useful and basic functions. Looks like their devs are stupid really... or just hate their customers.
Just try whatever you thing is ok for you.

MadK9 said:
Opinions are different from person to person. You should do a research on this subject then choose anything to your taste. Easier this way than asking someone. In this way you'll gain knowledge and you'll be able to provide tips and advises to others.
Anyway, you should stay away from the latest update to A11 from Xiaomi!!! The official update is garbage!!! I regret so much doing this step... lost some useful and basic functions. Looks like their devs are stupid really... or just hate their customers.
Just try whatever you thing is ok for you.
Click to expand...
Click to collapse
You are absolutely right. Android 11 update is like a diseaster

rafat.mym said:
You are absolutely right. Android 11 update is like a diseaster
Click to expand...
Click to collapse
whats the problem? mine works fine and much faster

jjsan said:
whats the problem? mine works fine and much faster
Click to expand...
Click to collapse
There must be something that makes your device smooth... maybe rom variant? Locked bootloader??
Share us more details please.

MadK9 said:
There must be something that makes your device smooth... maybe rom variant? Locked bootloader??
Share us more details please.
Click to expand...
Click to collapse
Unlocked bootlader, rooted (magisk for payment and adaway)
Rom variant is
Miui 12.0.2 RCXEUXM
Full wipe after upading to 11

Thanx.
Well, I also have an unlocked bootloader, but no Magisk and EEA Rom... but did not tried factory reset after update.
I also tried to flash Magisk but had issues with bootloop when I patched boot image and I gave up...

MadK9 said:
Thanx.
Well, I also have an unlocked bootloader, but no Magisk and EEA Rom... but did not tried factory reset after update.
I also tried to flash Magisk but had issues with bootloop when I patched boot image and I gave up...
Click to expand...
Click to collapse
ive installed magisk via twrp (renaming .apk to .zip and flashing)
i've read many posts about wiping data after upgrade

jjsan said:
Unlocked bootlader, rooted (magisk for payment and adaway)
Rom variant is
Miui 12.0.2 RCXEUXM
Full wipe after upading to 11
Click to expand...
Click to collapse
My firend, how did you fix the payment (with magisk)?

Jendrooo said:
My firend, how did you fix the payment (with magisk)?
Click to expand...
Click to collapse
5 days ago something happened and its not working for now. waiting for solution. you can search for cts profile here in forum.

Jendrooo said:
My firend, how did you fix the payment (with magisk)?
Click to expand...
Click to collapse
Android Repository
MagiskHide Props Config v6.0.2-v132 (72) ⚡Magisk Module ⚡Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Set/reset MagiskHide sensitive prop values. Change any prop values easily, and set your own custom props. ⚡️GitHub Repository ⚙Changelog: - Fix problems when trying...
t.me
Remember : A11 sux !

loopypalm said:
Android Repository
MagiskHide Props Config v6.0.2-v132 (72) ⚡Magisk Module ⚡Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Set/reset MagiskHide sensitive prop values. Change any prop values easily, and set your own custom props. ⚡️GitHub Repository ⚙Changelog: - Fix problems when trying...
t.me
Remember : A11 sux !
Click to expand...
Click to collapse
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?

Jendrooo said:
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Click to expand...
Click to collapse
payment is not possible even on android 10 now.
i like 11 more than 10

Jendrooo said:
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Click to expand...
Click to collapse
1-none , -----> custom rom
2-IDK about payment things

jjsan said:
ive installed magisk via twrp (renaming .apk to .zip and flashing)
i've read many posts about wiping data after upgrade
Click to expand...
Click to collapse
Managed to install Magisk again (older version...), gain root and activated OTA survival on OrangeFox Recovery. So far, no issues but still afraid to try A11 again...

MadK9 said:
Managed to install Magisk again (older version...), gain root and activated OTA survival on OrangeFox Recovery. So far, no issues but still afraid to try A11 again...
Click to expand...
Click to collapse
what were your problems?
best thing for me is setting phone to airplane mode and it lets bt on if was connected before.
and really nice and smooth system

Well, there were several bugs on my device which I was unable to sort them out and decided to go back to 12.0.4.0...
Most annoying one was the impossibility to share a file from file manager by swiping up to a file... A message came on screen telling me there is no app to handle the action on my personal profile or something like that... Whaaat?
Another bug was the 3 fingers screenshot option... Not there... Just not working... Or dynamic icons... This function also was not available anymore...
I had no patience digging for bugs, was pissed and flash the goddamn device with the previous working version of android... Was so angry that I forgot to back up my data and lost all my personal files!!!
But of course, I did not factory reset my device after A11 update... This move, should not exist!!! Why this option is never applied on iphones??? Of course they're not perfect but update after update and never, ever had issues with the device and never had to factory reset it after a major update.... Jesus Christ, this android....

well. i understand that.
3 fingers screenshot can be activated from notifications.
funny thing is possibility to activate new notification centre. its not there. unless you look for it in search. funny thing - your phone has to be in english
i was android developer for 3 years and I like this system just because these possibilities.
im rooted. i can edit hosts file and make adblock perfect and simple.
but for normal people just for using phone there is iPhone. its simple and working.
or also samsung devices are quite good but pricey

About 3 fingers screenshoot: The option was enabled in my device, so even if it was active, the function did not worked!

start camera from lock screen was moved to double volume up but also not working. ist still beta