Database Info

[SOLVED] Passing SafetyNet

I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.

Devo7v said:
I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.
Click to expand...
Click to collapse
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/

Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Devo7v said:
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Click to expand...
Click to collapse

inteltecra1700 said:
Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Click to expand...
Click to collapse
It sounds like you're on a fully functioning stock ROM with an unlocked bootloader. If that is the case, then it's pretty easy to get Magisk up and running. The first thing you need to do is get TWRP on your phone, to do that you need to flash a kernel that supports entering TWRP recovery from boot. There are a few kernels that allow you to do that, I am using AndroPlus v38. There is a newer version of AndroPlus, but there have been mixed reports of being able to enter TWRP.
To Flash a new Kernel and TWRP:
Download the latest kernel from https://kernel.andro.plus/ and place the <boot.img> within the zip file in the same folder with the fastboot.exe
Download the version of TWRP from https://dl.myself5.de/ and place the <recovery.img> in the same folder with the fastboot.exe
In the the folder with fastboot.exe, shift+right click and run cmd as admin
Reboot phone in to fastboot mode (hold down the volume up while plugging in usb)
Once the phone is detected type 'Fastboot devices' to make sure you device is detected.
If it's detected flash the kernel by typing the following command 'Fastboot flash boot <boot.img>' (without <>)
Then type 'Fastboot flash recovery <recovery.img>' (without <>)
Once done flashing type 'Fastboot reboot', and make sure you press volume up when the yellow led is showing
Once you've made sure that you can enter TWRP, things will be much easier from here on out. To get Magisk up and running:
Head over to the official Magisk thread and download both the Magisk Manager v2.1 apk and the Magisk v8 zip file to your phone (http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Reboot your phone and enter TWRP by pressing the volume up key when the yellow led is showing
Flash the Magisk v8 zip file. This will patch Magisk into your kernel (boot.img), so if you ever want to get rid of Magisk and it's mods, just reflash your kernel either by using Fastboot or by flashing the kernel zip file through TWRP.
Once Magisk has been successfully flashed, reboot your phone
When you phone has booted up install the Magisk Manager v2.1 apk that you downloaded earlier. If everything went right, the Magisk Manager should show that everything is installed and up to date.
I hope that helps, let me know if you have any other questions.

When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?

piet3r said:
When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?
Click to expand...
Click to collapse
Google has added more checks to SafetyNet and the procedure above no longer works. The issue is the AndroPlus kernel does not pass SafetyNet so anything you do after that will pass either. Maybe @AndroPlus will get some time to look into it and add some fixes. In the meantime I need to find another kernel that will pass SafetyNet, but I haven't had time to try.
Maybe you could try some other kernels and let us know if you find anything that works.

SAFE rooting to HUAWEI MATE 9

hi guys ,
I`ve read this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
my ask : Does this rooting goes well with MHA-L29C185B172 ?
if not , then how can i root my device SAFELY ?
thanks all

one, post, no experience with rooting android phones, do NOT root this phone unless there is some important reason to.
do ALOT more reading before you even think about rooting

Thx to reply. Like the others i wanna root to have root apps in my phone ,

Thx . Wanna have apps requires root in my phone . That simple

You don't even need to decrypt if you don't want to.
Unlock Developer Options (Settings - About: tap build number until it says it's enabled)
Go to the Developer Options and enable OEM Unlocking
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+

super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action

nawraz said:
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
Click to expand...
Click to collapse
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.

ante0 said:
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
Click to expand...
Click to collapse
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!

I failed install su however still waiting for any updates

nawraz said:
I failed install su however still waiting for any updates
Click to expand...
Click to collapse
You flashed the one I linked? And which twrp do you use?

ante0 said:
You don't even need to decrypt if you don't want to.
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
Click to expand...
Click to collapse
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!

FootSlave said:
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
Click to expand...
Click to collapse
He already unlocked and flashed twrp.
3.1.0 installs SuperSU fine. 3.0.3 does not.
And if oem was locked he wouldn't even be in twrp as you can't flash anything with fastboot if it is locked.
But I'll update my post in case anyone does miss to unlock oem.

Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk

FootSlave said:
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
Click to expand...
Click to collapse
Yeah. Only way then would be to rebrand to C636 using the DLOAD method, then rebrand back to your stock version using the Update thread under Guides. The latter requires twrp though so you'd need to rebrand first to get a working system.
To be honest I just figured he had already unlocked and flashed twrp as he was in the decrypt thread
Missing oem was an error on my side. It was long since I had to unlock oem xD

ante0 said:
You flashed the one I linked? And which twrp do you use?
Click to expand...
Click to collapse
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310

nawraz said:
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
Click to expand...
Click to collapse
Weird. I tested with 3.1.0 a few days ago. But I guess it could have to do with builds. 3.1.0 is using kernel for B182. Maybe it's fixed if you use 3.1.0 with B182.
Oh well, good you managed to install it anyway.
Edit: I tested with the SuperSU I linked.

mscion said:
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
Click to expand...
Click to collapse
All I know is that it wasn't present in builds before B182.
 @st_voss is the one who found out it was added in B182 (Kernel build April. 11th probably as that's what I have on B182.).
It might be present in B181 on C636 as well, that was released 8th of May.

mr. ante0 ..... u r the man , thank you so much

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

Rooting on Android 10

Hi, Im new in this forum, just got my OP 7 Pro. I've been away from anything root related for a long time, since my previous devices couldnt be rooted.
I remember using magisk when it was a new thing, and everyone was using greenify to extend battery life.
I just updated to Android 10 Beta, can I root my device?
If it is possible, what do I lose if I root besides widevine?
The only thing I'm really looking forward is gcam port and the use of aux cams, since a lot of things have to be updated to Android 10, I don't think there's a lot to do right now besides that.

I think you have to come back to the android p stable, root, install the twrp and after you will able to update with the root. Now im on the beta with root and twrp throw a dirty installing

vuoshino said:
I think you have to come back to the android p stable, root, install the twrp and after you will able to update with the root. Now im on the beta with root and twrp throw a dirty installing
Click to expand...
Click to collapse
Hi! Thanks. If you don't mind, can you give point me to a guide or something to downgrade? I'm a total noob with everything OnePlus related.

You don't have to downgrade to Pie.
Do it like this:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
You just need stock boot.img:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345

There's also another way which avoids to downgrade.
Flash the magisk patched img you'll find in this forum.
After following instructions from there, you'll be rooted but without TWRP.
If you need that also... flash the TWRP installer zip as a magisk module, reinstall magisk (direct install), reboot and you're done.
Inviato dal mio GM1913 utilizzando Tapatalk

tidschi said:
You don't have to downgrade to Pie.
Do it like this:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
You just need stock boot.img:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Click to expand...
Click to collapse
Wow, thanks!! that seems stupidly easy, even for me. Two questions:
Do I need a PC to do the extraction?
Will this wipe any data?
And as for my initial question, is there anything besides widevine lost when rooting?

donelwero said:
Wow, thanks!! that seems stupidly easy, even for me. Two questions:
Do I need a PC to do the extraction?
Will this wipe any data?
And as for my initial question, is there anything besides widevine lost when rooting?
Click to expand...
Click to collapse
You can download Magisk patched boot.img from second link above.
Flashing boot.img will not wipe any data.
If I remember right, Widevine will get L3 with unlocked bootloader.

tidschi said:
You can download Magisk patched boot.img from second link above.
Flashing boot.img will not wipe any data.
If I remember right, Widevine will get L3 with unlocked bootloader.
Click to expand...
Click to collapse
Awesome!! Thank you very much, thought I had to unlock the bootloader by myself using a PC.
Edit: I'm so dumb, just realized I still have to flash the boot.img using fastboot

I have a question, in order to root and flash twrp coming with android 10 (no root) I must unlock the bootloader, right?

littlejonny17 said:
I have a question, in order to root and flash twrp coming with android 10 (no root) I must unlock the bootloader, right?
Click to expand...
Click to collapse
Yes bootloader must be unlocked to flash TWRP or Root the device also when you unlock the bootloader it will factory reset the device so make sure you backup any personal data you need before unlocking.

Thank you

Question TWRP for Oneplus 9?

Today I tried to install twrp from this link
Install TWRP Recovery on OnePlus 9/9 Pro [Android 13]
In this comprehensive tutorial, we will show you the steps to install the TWRP Recovery on OnePlus 9 and OnePlus 9 Pro devices.
www.droidwin.com
I have the CN version (LE2110 ) with Oxygen 11.2.9.9.LE25AA. I was able to make it unlocked but on the step where I am in the temporary TWRP I can't now browser to any files I copied before. I have no access to the SDCARD, to flash TWRP permanent.
Is there another workaround to get TWRP running on the OP9 and root it after?
thanks
Andy

Great the twrp from op9 pro works perfecet. magisk and root as well. thanks very much for the great work.
Is there a way to disable the unlocked message which appears on the boot?
what happen if I lock it again? does TWRP and root work then?. Bit scary to try as yesterday I was hanging in a boot loop with trying twrp...)
thanks

I unlocked the bootloader with adb fastboot flashing unlock.
what do you mean by MSM?
right now I am on stock rom with all updates, TWRP with Magisk and root.
should I look the bootloader with ad fastboot flashing lock ? Do I still have TWRP and Magisk with root running after I lock the bootloader again?
thanks

Do not ever lock your bootloader with TWRP installed or root! It can and very likely will brick your device! You can only get rid of that message by going back to stock without root and without TWRP and then relock. You have been warned, do not even think about it

Hi,
ok thanks for the information, then I better leave this message,
thanks

Hi,
ok I will leave the message then.
thanks to all for quick support

It is/was "possible" to remove, but the difficulty and risk are not worth it.

Will I get a brick if I lock bootloader with an old stock ROM?

I want to relock bootloader, but will I get brick if I lock bootloader with old stock ROM installed on device?

Look inside here:
Lock BootLoader after Rooting?
Thanks for taking time to read my query. I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero) and before looking can I take everything backup on titanium backup and then restore everything after locking ? I'm I...
forum.xda-developers.com

jwoegerbauer said:
Look inside here:
Lock BootLoader after Rooting?
Thanks for taking time to read my query. I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero) and before looking can I take everything backup on titanium backup and then restore everything after locking ? I'm I...
forum.xda-developers.com
Click to expand...
Click to collapse
I know that if I install modified ROM and lock bootloader I will get a brick. But will I get a brick if i install official (stock) ROM but old version and then lock bootloader? For example, I installed stock ROM (not modified) with Android 10, but the latest is Android 11 then I locked bootloader. Will I get a brick?

jwoegerbauer said:
Look inside here:
Lock BootLoader after Rooting?
Thanks for taking time to read my query. I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero) and before looking can I take everything backup on titanium backup and then restore everything after locking ? I'm I...
forum.xda-developers.com
Click to expand...
Click to collapse
The question is, can I lock the bootloader with the old version of the official firmware installed without getting a brick. Because the old version of the firmware works smoother.

Locking a bootloader doesn't affect ROM actually installed: Lock or Unlock will wipe your data, that's all.

jwoegerbauer said:
Locking a bootloader doesn't affect ROM actually installed: Lock or Unlock will wipe your data, that's all.
Click to expand...
Click to collapse
So can I install old version of fw? I heard something about rollback protection.

Oybek78 said:
So can I install old version of fw? I heard something about rollback protection.
Click to expand...
Click to collapse
You still, or I didn´t find, that you mention the model of your device, that´s matter to have the right answer.
Also, it depends on which method you used to flash the ROM, if you officially, flashed the ROM, and the rollback didn´t affect your device, then it won´t do, locking or unlocking it.

Oybek78 said:
So can I install old version of fw? I heard something about rollback protection.
Click to expand...
Click to collapse
The stock ROM can be installed on the phone at any time. Mostly via ADB / Fastboot tools.

SubwayChamp said:
You still, or I didn´t find, that you mention the model of your device, that´s matter to have the right answer.
Also, it depends on which method you used to flash the ROM, if you officially, flashed the ROM, and the rollback didn´t affect your device, then it won´t do, locking or unlocking it.
Click to expand...
Click to collapse
My phone is Sony Xperia 1 J9110. I flashed it officially to the latest ROM through settings. Then I unlocked the bootloader and flashed the old stock ROM via newflasher. Then I decided to relock the bootloader with old stock ROM installed. Does this mean that I will get my phone bricked if I lock the bootloader with old stock ROM actually installed?

jwoegerbauer said:
The stock ROM can be installed on the phone at any time. Mostly via ADB / Fastboot tools.
Click to expand...
Click to collapse
But can I lock the bootloader with old stock ROM installed?

I saw somewhere that if you lock the bootloader with the old firmware version, you may get brick. But I'm not sure about that.

Why steadily repeat your posts?
FYI: I hereby opt out of this thread.

jwoegerbauer said:
Why steadily repeat your posts?
FYI: I hereby opt out of this thread.
Click to expand...
Click to collapse
Because you answered me

Oybek78 said:
My phone is Sony Xperia 1 J9110. I flashed it officially to the latest ROM through settings. Then I unlocked the bootloader and flashed the old stock ROM via newflasher. Then I decided to relock the bootloader with old stock ROM installed. Does this mean that I will get my phone bricked if I lock the bootloader with old stock ROM actually installed?
Click to expand...
Click to collapse
Yes, always that you flash a stock ROM, you can re-lock it, fastboot will erase the data as a security measurement.