Related
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
airdi1 said:
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
Click to expand...
Click to collapse
As I mentioned in the post, I do not have Xposed framework
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
tabletalker7 said:
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
Click to expand...
Click to collapse
I have magisk 16.7
virtyx said:
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
Click to expand...
Click to collapse
How do I do that? Do you have a link to this zip?
quantumcity said:
I have magisk 16.7
Click to expand...
Click to collapse
Google "Magisk uninstaller". Flash that file in TWRP. Then reboot to recovery. Then flash Magisk 16.4
quantumcity said:
How do I do that? Do you have a link to this zip?
Click to expand...
Click to collapse
its in the magisk official thread.
virtyx said:
its in the magisk official thread.
Click to expand...
Click to collapse
Yes
So for me, the safety net check passes in the Magisk app but I am not able to access Google tez which tells me that my device is rooted or custom ROM has been changed. Using Magisk v 16.0
16.4... notice the 4
Just fyi I'm on 5.19 and using Magisk 16.0 and safety net passes just fine. Use Google pay daily and play store shows certified.
I hide everything Google related in magisk hide just to be sure
Eric214 said:
16.4... notice the 4
Click to expand...
Click to collapse
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
I have attached the screenshots below. And I understand that I'm using Magisk 16.0
skr975 said:
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
Click to expand...
Click to collapse
Do you have it hidden in Magisk? Google Pay works here if you hide it.
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
quantumcity said:
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
Click to expand...
Click to collapse
In playstore / settings are you uncertified? After unlocking bootloader I was and couldn't use Google pay. I flashed magisk and it was still uncertified so I cleared playstore app data. Now the phone says certified and Google pay works for me.
I suggest you flash 16.4 magisk and clear app data in playstore to see if you can get them working. Also you will need a different app than magisk manager to check safety net ATM as it will come back with "invalid response"
Sent from my OnePlus6 using XDA Labs
So as the title says safety net breaks just by unlocking the bootloader and doing nothing else, no twrp no magisk and even if i flash magisk it doesnt fix it even with magiskprops module.
I flashed stock rom 10.3.1 with msmtool and booted the phone and everything was fine until i unlocked the bootloader and rebooted. I lost all oneplus wallpapers and even then play store says device not verified and netflix shows as unsupported app.
Even with 10.3.4 the issue is same and cant be fixed with magisk. Previously i was using 10.3.2 with unlocked bootloder and magisk and safety net was fine so how it is now not working with factory rom i flashed with msmtool
https://forum.xda-developers.com/on...etynet-magisk-edxposed-tests-failing-t4077527
Manu11 said:
So as the title says safety net breaks just by unlocking the bootloader and doing nothing else, no twrp no magisk and even if i flash magisk it doesnt fix it even with magiskprops module.
I flashed stock rom 10.3.1 with msmtool and booted the phone and everything was fine until i unlocked the bootloader and rebooted. I lost all oneplus wallpapers and even then play store says device not verified and netflix shows as unsupported app.
Even with 10.3.4 the issue is same and cant be fixed with magisk. Previously i was using 10.3.2 with unlocked bootloder and magisk and safety net was fine so how it is now not working with factory rom i flashed with msmtool
Click to expand...
Click to collapse
Don't think so. I'm on a rooted 10.3.4 and I don't see such issues with playstore or safetynet.
hallo dare said:
https://forum.xda-developers.com/on...etynet-magisk-edxposed-tests-failing-t4077527
Click to expand...
Click to collapse
safetynet fails even without the magisk, so i dont think its a magisk problem
Manu11 said:
safetynet fails even without the magisk, so i dont think its a magisk problem
Click to expand...
Click to collapse
What'd u do ?
jaggillararla said:
What'd u do ?
Click to expand...
Click to collapse
There's nothing you can do about safetynet. The moment you unlock the bootloader, you have tripped the safetynet. Why do you need safetynet btw unless you are using bank apps or secure stuff, safetynet really doesn't help much
amirage said:
There's nothing you can do about safetynet. The moment you unlock the bootloader, you have tripped the safetynet. Why do you need safetynet btw unless you are using bank apps or secure stuff, safetynet really doesn't help much
Click to expand...
Click to collapse
Bro as i told already in my post i was yesterday using unlocked bootloader + magisk+ twrp with passing safety net. The problem started when i clean flashed stock rom with msmtool and unlocked bootloader.
ANYWAYS GUYS AFTER SO MANY USELESS ATTEMPS I SOLVED IT..
Older version of magisk worked and safety net passes, i dont know how new version failed me :/ Device is certified again
That's why I don't update anything if not have to
Config below
Sent from OnePlus 7 Pro, OxygenOS 10.0.3, TWRP 3.3.1-75, Magisk 20.4, TaiChi Xposed 6.1.8, Modded Play Store 16.5.15, android core.java patched and SafetyNet pass OK
Install magisk
Go to magisk settings
Enable magisk hide(if you're getting problems with banking apps or games that detect root just hide magisk manager too)
Enable it for google play services and enjoy!
Playstore uncertified status appeared to me when I flash stock rom through TWRP but it solves flashing new firmware via OTA
Sent from my OnePlus7Pro using XDA Labs
The reason an older version of Magisk worked is because newer versions of Magisk turn MagiskHide off by default, which is needed to pass SafetyNet.
Also, SafetyNet is not an e-fuse like Knox is. You don't "trip" it, you can only fail it when it checks your device.
Read the full page of OnePlus 9 thread! No firmware and boot files were found
iSkyJIE said:
Read the full page of OnePlus 9 thread! No firmware and boot files were found
Click to expand...
Click to collapse
What're you on about?
TheKnux said:
What're you on about?
Click to expand...
Click to collapse
Did not find the T-Mobile version of OnePlus 9 firmware or boot.img! Need boot files to root this phone！
You pull the boot.img yourself
iSkyJIE said:
Did not find the T-Mobile version of OnePlus 9 firmware or boot.img! Need boot files to root this phone！
Click to expand...
Click to collapse
There's ways to pull the boot.img using adb/fastboot commands once your bootloader is unlocked. Then all you have to do is patch it using Magisk and flash it in fastboot.
TheKnux said:
You pull the boot.img yourself
There's ways to pull the boot.img using adb/fastboot commands once your bootloader is unlocked. Then all you have to do is patch it using Magisk and flash it in fastboot.
Click to expand...
Click to collapse
Thank you for your reply！
My bootloader has been unlocked! But I don't know how to extract it to boot.img
You don't specifically need the T-Mobile boot.img to root your phone. Get the boot.img from this post: https://forum.xda-developers.com/t/root-oneplus-9.4253651/page-4#post-84874313
Install the Magisk App on your phone
Reboot into fastboot
fastboot boot boot11244AAmagisk.img
Once your phone boots, open the Magisk app
Ignore any message about it needing to setup
Install Magisk with a direct install
Reboot and now your phone should be rooted
I've tested this on my one T-Mobile OnePlus 9 and it works perfectly, even passing SafetyNet
Lomeli12 said:
You don't specifically need the T-Mobile boot.img to root your phone. Get the boot.img from this post: https://forum.xda-developers.com/t/root-oneplus-9.4253651/page-4#post-84874313
Install the Magisk App on your phone
Reboot into fastboot
fastboot boot boot11244AAmagisk.img
Once your phone boots, open the Magisk app
Ignore any message about it needing to setup
Install Magisk with a direct install
Reboot and now your phone should be rooted
I've tested this on my one T-Mobile OnePlus 9 and it works perfectly, even passing SafetyNet
Click to expand...
Click to collapse
Thank you,
I'll try extracting the 11.2.2.2AA international version of boot, which I'm currently version 11.2.2.2
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
inspron said:
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
Click to expand...
Click to collapse
MagiskHide enabled?
TheKnux said:
MagiskHide enabled?
Click to expand...
Click to collapse
Yes.
inspron said:
Yes.
Click to expand...
Click to collapse
Not sure then. I'm at work right now so I'm kinda tied up for helping you out until I get home.
TheKnux said:
Not sure then. I'm at work right now so I'm kinda tied up for helping you out until I get home.
Click to expand...
Click to collapse
Thank you. I am hopping that the problem will be fixed when I have access to a stock boot.img from T-Mobile oneplus9.
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
inspron said:
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
Click to expand...
Click to collapse
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Jg1234 said:
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Click to expand...
Click to collapse
Wow! Thank you. Failed Magisk but It does pass this https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest
Jg1234 said:
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
Click to expand...
Click to collapse
Thank you stranger!!!
Jg1234 said:
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Click to expand...
Click to collapse
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
inspron said:
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
Click to expand...
Click to collapse
I'm not to sure on that one.. I came from the 6t t-mobile version and it had the local upgrade option.
inspron said:
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
Click to expand...
Click to collapse
No, T-mobile doesn't allow update if bootloader unlocked. has nothing to do with safetynet. If you look in system after unlocking your bootloader and rebooting you will see system update no longer avail.
Jg1234 said:
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
Click to expand...
Click to collapse
11.2.2.2 AA International’s BOOT is only 96MB, and the T-MOBILE 11.2.2.2 BOOT you provide is 192MB, maybe this is the difference.
I recently flashed miui v12.0.6 global rom in my indian version POCO X3 Pro.But after boot it says your device is not google play protect certified.I am not able to use or install any google apps.Why this happened?If i flash other region rom in my POCO X3 Pro i will not able use google apps?
If your bootloader is unlocked right now, it means you're not passing SafetyNet, and that also affects Play Store certification. To fix this, you need to install Magisk, hide Magisk Manager and enable MagiskHide; as well as install the SafetyNet Fix module from here: https://github.com/kdrag0n/safetynet-fix/releases
I selected clean all and lock.that means my bootloader is locked now.
when I flash indian rom google play works properly.But if i try other region rom it gets the same error.
Do you still pass SafetyNet in this state?
Yes,passes safetynet in indian rom but fails in global rom.I used official method(fastboot rom)
Saadman Moyeed said:
Yes,passes safetynet in indian rom but fails in global rom.I used official method(fastboot rom)
Click to expand...
Click to collapse
Read this.
urbanman2004 said:
Read this.
Click to expand...
Click to collapse
I don't said about eu rom,I just simply used the mi flash tool to flash global stock fastboot rom.will the next update fix the issue.
Saadman Moyeed said:
I don't said about eu rom,I just simply used the mi flash tool to flash global stock fastboot rom.will the next update fix the issue.
Click to expand...
Click to collapse
I think the official MIUI ROMs and Google play can distinguish between device regions, though I don't know how. (Most likely due to people buying China devices and try to get global rom, so they do this)
If you flash other official ROMs from other region (say, Indian device with eea/global rom), it will always be consider as "third party" installation, so it will not pass safetynet. (you can't do this with the official "mi-recovery" I assume.)
To make the different region rom pass safetynet, you need help with magisk and modules as urbanman2004 said.
Saadman Moyeed said:
I don't said about eu rom,I just simply used the mi flash tool to flash global stock fastboot rom.will the next update fix the issue.
Click to expand...
Click to collapse
Also read this
Can I flash another region ROM?
I have the IDXM version of the phone and it's still on miui 12.0.1.0 Is it possible to flash the EEA version or will it bootloop?
forum.xda-developers.com
Saadman Moyeed said:
I don't said about eu rom,I just simply used the mi flash tool to flash global stock fastboot rom.will the next update fix the issue.
Click to expand...
Click to collapse
Found any solution to the issue?
RavzsTez said:
Found any solution to the issue?
Click to expand...
Click to collapse
Yeah i rooted with magisk and followed this guide.
Check the below link and let me know are you facing the same issue or not
Unable to update Google Play System Update
I have rooted my mobile, and safteynet is success, Device is also showing certified in play store settings but i'm unable to update google play system update in security status in settings. Its showing update available but when I try to do it...
forum.xda-developers.com
RavzsTez said:
Check the below link and let me know are you facing the same issue or not
Unable to update Google Play System Update
I have rooted my mobile, and safteynet is success, Device is also showing certified in play store settings but i'm unable to update google play system update in security status in settings. Its showing update available but when I try to do it...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes same problem i am on 1 feb 2021 and cant update to 1 april 2021
RavzsTez said:
Check the below link and let me know are you facing the same issue or not
Unable to update Google Play System Update
I have rooted my mobile, and safteynet is success, Device is also showing certified in play store settings but i'm unable to update google play system update in security status in settings. Its showing update available but when I try to do it...
forum.xda-developers.com
Click to expand...
Click to collapse
Let me know how you passed safetynet
Saadman Moyeed said:
Let me know how you passed safetynet
Click to expand...
Click to collapse
Same as you did, installed magisk and hide all Google related stuff.
But if we don't want all this headache then it's better to flash Xiaomi.eu rom
Hello all,
My phone came with ColorOS OOS 12 and I hate it. As soon as I rooted it it started crashing daily, I even reflashed a fresh oos12 image using the local update tool and only granted superuser to one app (solid explorer so I could access user files) and it still crashes. Not to mention all the apps i want to use don't work on android 12 (call recorder, busy box) and no custom recovery.
I've been reading through the forum and I found a downgrade package that looks like its hosted by oneplus: https://oxygenos.oneplus.net/OnePlu...all_2107082125_downgrade_059624cc7298428b.zip
I just wanted to make sure I am doing this correctly...
Do I use the OP Local Update app to flash?
Will I be able to flash TWRP for android 11 afterwards?
Will i need to relock the bootloader?
Should i re-root using the magisk slot b method or wait until its flashed and use TWRP?
Will it try to OTA back to android 12? If so, what's the best method to get on the latest version of android 11?
Thanks for the help.
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
EtherealRemnant said:
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
Click to expand...
Click to collapse
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
aaronbaird1 said:
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
Click to expand...
Click to collapse
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
EtherealRemnant said:
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
Click to expand...
Click to collapse
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
aaronbaird1 said:
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
Click to expand...
Click to collapse
You would need to back to 11 because OnePlus hasn't released working sources for 12. Just use the downgrade package, factory reset, then upgrade to 11.2.10.10 and you'll be good to go for custom ROMs. TWRP isn't used for flashing them, they all generally post their own recovery. StagOS was the best one I used (plus the dev is really responsive when there are issues) and people seem to really be enjoying Nameless but that came out after I went back to stock so I haven't tried it yet.
Before you mess with custom ROMs, make sure that you download the global MSM Tool and make sure you can connect it. Honestly since you have to go back anyway, might as well download and use the MSM Tool to get the device back to 11 anyway.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
Easiest way to get it into EDL is adb reboot edl but if you want to practice the key combination in case you can't get into the OS, I found if you open the MSM, check use lite firehose, and click Start before you connect the phone, it has less connection errors because it's waiting for the phone so as soon as you connect the cable, it pops up.
EtherealRemnant said:
TWRP isn't used for flashing them, they all generally post their own recovery.
Click to expand...
Click to collapse
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
aaronbaird1 said:
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
Click to expand...
Click to collapse
Yeah TWRP has issues. I soft bricked last time I tried to do anything with it and had to use MSM Tool to get back to working order.