Database Info

SafetyNet Check in magisk failing

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

Anyone running stock rooted 9.0.3 upgrade to Magisk 18.1 yet?

I was thinking of trying to fix a few minor things like won't boot with charger plugged in and Google Pay getting screwed up every once in a while...but figured I would ask first.
To be safe I was going to nandroid backup, TWRP Magisk Uninstaller, TWRP Magisk 18.1 installer and try it out later on....it seems people have reported bootloops on other phones upgrading from the Magisk Manager app...
MW

I am in 9.0.3 but under xxx no limits magisk rom.
It works well

0xPraeT0Rian said:
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
Click to expand...
Click to collapse
Using the new magisk 18.1 or 18?

You asked about 18.1.
I am on 9.0.3 with 18.1 magisk and the new magisk manager

Hi to all,
I am on OB12, and I'm no longer able to root since I tried to upgrade from Magisk 18 to 18.1
I already tried the 2 last versions of Magisk uninstaller and also to reflash OB12, but still impossible to root.
What is very strange is that if I flash Smurfkernel it says that I'm rooted, but after booting, no Magisk APK and impossible to install it !
Any suggestions?
Thank in advance for any help.

I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.

No problems here.

b.huss2 said:
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
Click to expand...
Click to collapse
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)

OP here -- I updated and am having no issues, but I did it all through TWRP by uninstalling Magisk 18.0 first and then re-installing 18.1 before rebooting. I had already updated Magisk Manager from the app.
Only thing I noticed was I had to reset up all my settings (Magisk hide for Direct TV Now, and re SU authorize all root apps). First reboot everything was slow with root apps waiting for SU access before the request came through, but then everything was fine once it was granted.

michelD said:
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
Click to expand...
Click to collapse
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)

b.huss2 said:
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
Click to expand...
Click to collapse
Yes I tried this too, but unsuccessfully !
And I'm even not sure that a full wipe will help, because it concerns another partition.

Edxposed on S10e

I managed to root the device...but didn't have much luck with Edxposed yafa Has anyone managed to get Edxposed working on a S10e yet ? If so which variant

Tried both Variations on my SM-970F , YAHFA and Sandhook. Both hung up the phone at the Samsung logo

Edxosed Canary worked

On my S10e with BeyondROM V6.7 it works fine.
I have the following software istalled:
- Magisk 20.4
- Riru-Core v19.8
- Riru-EdXposed v0.4.6.2 (4529) (YAHFA)
- EdXposed Manager v4.5.7 (Enhancement mode)
The modules that I am using: AFWall+, XPrivacyLua

Same exact setup/config: Interested in knowing how you did it?!
gl000008 said:
On my S10e with BeyondROM V6.7 it works fine.
I have the following software istalled:
- Magisk 20.4
- Riru-Core v19.8
- Riru-EdXposed v0.4.6.2 (4529) (YAHFA)
- EdXposed Manager v4.5.7 (Enhancement mode)
The modules that I am using: AFWall+, XPrivacyLua
Click to expand...
Click to collapse
Its good to see evidence that some one with the device I have just purchased is using the same software loadout as I will be. So I have a few questions -
Regarding magisk install, how did you get this installed? or did you follow JohnWu's instructions on his magisk page..?
Also what recovery are you using, is it twrp and if so what version..?
In what sequence did you install magidsk, twrp, xposed..? Which thread/guide on XDA did you use/follow..?
are you able to reboot the phone normally? or if not why not and what are you work arounds?
is one of the fixes for rebooting, powering off/on the phone to flash Multi-disabler?
and lastly have you had any freezing of crashing issues related to Xposed or any Xposed modules..?
As your post is a few months ago and EdXposed, RiRu/, Magisk have been updated since then, what version are you currently running?

b1k3rdude said:
Its good to see evidence that some one with the device I have just purchased is using the same software loadout as I will be. So I have a few questions -
Regarding magisk install, how did you get this installed? or did you follow JohnWu's instructions on his magisk page..?
Click to expand...
Click to collapse
I followed the installation instructions from the BeyondROM thread. I also read many comments in that thread that clarified some doubts, but I don't remember exactly which messages.
b1k3rdude said:
Also what recovery are you using, is it twrp and if so what version..?
Click to expand...
Click to collapse
The BeyondROM requires installation of Ian’s latest patched TWRP. I used version 3.3.1-103. In order to install TWRP I followed the installation instructions in that thread and read many messages to clarify the instructions.
b1k3rdude said:
In what sequence did you install magidsk, twrp, xposed..? Which thread/guide on XDA did you use/follow..?
Click to expand...
Click to collapse
As indicated above, to install the TWRP, BeyondROM and Magisk I used the instructions in Ian's TWRP and BeyondROM threads. Several other messages inside the threads also helped, by I don't remember exactly which ones.
To install EdXposed I used Magisk Manager to download and install the following modules:
Riru-Core v19.8
Riru-EdXposed v0.4.6.2 *4529( *YAHFA)
Then I installed the APK EdXposed Manager v4.5.7 from this page https://github.com/ElderDrivers/EdXposedManager/releases
After restarting the phone, I installed some EdXposed modules from within the application and enabled them, which also required another phone restarting.
b1k3rdude said:
are you able to reboot the phone normally? or if not why not and what are you work arounds?
is one of the fixes for rebooting, powering off/on the phone to flash Multi-disabler?
Click to expand...
Click to collapse
I reboot the phone normally and it restarts in rooted system. This features is provided by BeyondROM and I didn't have to do anything extra.
b1k3rdude said:
and lastly have you had any freezing of crashing issues related to Xposed or any Xposed modules..?
As your post is a few months ago and EdXposed, RiRu/, Magisk have been updated since then, what version are you currently running?
Click to expand...
Click to collapse
I haven't experienced any freezes or crashes in all this time. The only modules that I installed are: AFWall+ and XPrivacyLua.
I haven't updated any software (TWRP, ROM, Magisk, EdXposed) and now there are more up to date packages of all of them.

How to Root OnePlus 8T Build 11.0.6.8.KB05AA

I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.

rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.

Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.

Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.

You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.

alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.

Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.

rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot

Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!

rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"

Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!

I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.

Lost root after installing TWRP. Can anyone share patched boot image for 11.0.5.1.GM21AA?

As above, I would appreciate it if someone could share a copy of a Magisk patched 11.0.5.1.GM21AA boot image. Thanks!
P.S. - Do not update to Magisk 24 or 24.1 unless you want to have to mess around with your phone!

Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.

Dan3ll1 said:
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Click to expand...
Click to collapse
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?

benengyj said:
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
Click to expand...
Click to collapse
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.

Frodolo said:
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Click to expand...
Click to collapse
Once you've upgraded to 24 or 24.1 it seems that the only way to go back to an older version is to use the built-in uninstall button in the Magisk app. Just trying to flash a new boot image over it doesn't seem to stick.
In my case, I had to:
Uninstall any version of the Magisk app
Install 24.1
Extract the boot image using Payload Dumper
Creating a 24.1 patched boot image to re-root my device
Uninstalling 24.1 using the uninstall button in the Magisk app
Install Canary Magisk (23 should work too)
Create a new 23 patched boot image and root using it
Still have not gotten around to fixing my MagiskHide and SafetyNet failing though, I think that requires some cache clearing and other steps to resolve. Also somehow managed to get rid of my TWRP accidentally along the way too, so I'll have to reinstall that again.

Thanks a lot!

benengyj said:
Uninstalling 24.1 using the uninstall button in the Magisk app
Click to expand...
Click to collapse
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?

¿GotJazz? said:
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
Click to expand...
Click to collapse
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol

benengyj said:
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
Click to expand...
Click to collapse
Yep, that's weird. I was having (a ton of) trouble getting my phone rooted at the time, so that's why I didn't see it.