Database Info

Systemless Root Help

So I have been struggling the past few hours trying to get the Systemless root to work. I've followed all of the guides on this and the Magisk forum and yet the SafetyNet fails. Here are the steps I have taken:
Downloaded H830 10i ZIP
Downloaded Magisk v7 ZIP
Downloaded phh superuser magisk r259 ZIP
Boot into TWRP
Format Data
Flash the three ZIP files one at a time in the order mentioned
Flash no-veirfy
Reboot System
Step through setup page
Install Magisk Manager apk
Install phh SuperUser apk
Install SafetyNetHelper
The end result of all of that is a failed SafetyNet. Am I missing something? I would really appreciate any help. Thanks

SafetyNet has been undergoing an impressive number of revisions over the past few weeks. Most recently, this past weekend, it effectively shut out the majority of rooted users. There are reports of it shutting out folks purely for having an unlocked bootloader, particularly with the Nexus 6P.
Specifically for our G5, here's my history:
Magisk v7 and earlier was working well up until a few weeks ago. Safetynet was updated to detect Magisk in general. End of that chapter.
Chainfire and phhusson, the 2 main root leaders in Android, each came up with their own workarounds to evade SafetyNet. Chainfire came up with suhide, to be flashed after his supersu zip, and phhusson released his own version of phh root which also hid root from SafetyNet.
These worked for about a week until SafetyNet adapted. suhide was then updated with a manual script to run which evaded it again for several more days. This was working for me on Sunday morning. And then it didn't anymore. There were many variations people then advertised (using different root switch apps, etc), but none worked for me.
Magisk v8 was just released, which includes a setting to hide Magisk and root from SafetyNet. However, this does not work to fully evade Safetynet, and thus Android Pay won't start. It may be that SafetyNet is now looking at other things, such as unlocked bootloader status, and Magisk's presence is irrelevant.
Specifically, while working with these, I accidentally reset my G5 to near stock conditions (no root, encrypted data partition), except for the TWRP recovery and unlocked bootloader. Safetynet checker apps FAILED on this near pristine stock phone. This is disconcerting.
In short, there's no way I've found to get a SafetyNet pass since this past weekend. You could try returning completely to stock and relocking the bootloader, which will also probably wipe all your data, to test this theory, but not worth it in my book.

seconding what waylo said. i was trying all day to get safetynet to pass but i flashed the stock rom, did a factory reset, and still couldn't get safetynet to pass (all i had was unlocked bootloader + TWRP)
i think we just have to wait until we get a custom kernel with the boot verify checker that safetynet uses patched

Thanks for your help a few months ago. Given the time for Magisk to mature I was wondering if Magisk on the H830 is now possible. From reading throughout this forum, some users have had success but no one has an official guide. I just got a new LG G5 (gps issue) and I finally unlocked the bootloader and installed TWRP following the Noob Friendly Guide. Along the way I had to enter in the following code to keep my device from TWRP boot looping:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Once I got the 20a software version up and running I went ahead and flashed Magisk 12.0, went into the Magisk Manager Settings, turned on Busybox/Magisk Hide/Systemless Host, and performed a SafetyNet Check. The end result is a failed CTS Profile Mismatch. Did I miss something or did Google patch SafetyNet again?

SomeguynamedBentley said:
Thanks for your help a few months ago. Given the time for Magisk to mature I was wondering if Magisk on the H830 is now possible. From reading throughout this forum, some users have had success but no one has an official guide. I just got a new LG G5 (gps issue) and I finally unlocked the bootloader and installed TWRP following the Noob Friendly Guide. Along the way I had to enter in the following code to keep my device from TWRP boot looping:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Once I got the 20a software version up and running I went ahead and flashed Magisk 12.0, went into the Magisk Manager Settings, turned on Busybox/Magisk Hide/Systemless Host, and performed a SafetyNet Check. The end result is a failed CTS Profile Mismatch. Did I miss something or did Google patch SafetyNet again?
Click to expand...
Click to collapse
You need to install the latest v13 beta. It's on the magisk threads. Uninstall v12 with the magisk uninstaller and immediately install v13.

waylo said:
You need to install the latest v13 beta. It's on the magisk threads. Uninstall v12 with the magisk uninstaller and immediately install v13.
Click to expand...
Click to collapse
Awesome! Got it. Hopefully the learning curve from here on out as Google rolls out patches is not as steep so I can keep up!
A word to those reading this thread: you need to reboot after turning on Magisk Hide and Systemless Host in settings (as of 6/19/17).

[Guide] Install Magisk for root & xposed framework and have working OTA updates

Most Nexus phones users use magisk in order to be able to have root and xposed and also be able to easily pass safetynet check tests in order to be able to get OTA updates.
Well now magisk 14.4 works on our device and OTA updates should work just fine according to this https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Of course when Android Oreo rom comes out we should wait before applying it just to be sure that magisk and twrp will work on that rom so that we wont be left without root after updating (or brick the device.
I wrote a guide for installing magisk 14.4 on our device having 2nd october OTA installed, i copy it here so that more people can see it.
DISCLAIMER - USE AT YOUR OWN RISK! Bellow steps worked for my device but they might brick yours, you might lose warranty etc.!!!!!!
I am not a developer, I am just a user that wants to have the new phone setup like the older phones in my possession before using it as the main everyday phone.
All below packages are here due to the hard work of the people who made them. If you use them, give them the appropriate credits. This is also the reason that I don't attach any files in this post, I only give links to download the packages on the the forum threads/ sites I also found them.
Here I just show a combination of packages/ programs that worked.
PREREQUISITES:
1) Read the whole guide before starting. Make sure you are familiar with all the terms used and you understand what you are doing in each step.
2) I advise you to firstly download all the needed packages and have them in a folder in your computer and also make a copy of them in your phone and then start with the steps of this guide.
3) In this guide I use a windows pc. Fastboot commands are written in cmd. If you use a pc with another operating system, just make sure you can use adb/ fastboot commands and that you can also use miflash or another tool to flash the rom to your phone.
4) Make sure you have correct adb drivers installed in your pc. For this guide I have used adb-setup-1.4.3.exe from this thread.
So this is the step by step procedure with links:
Flash official rom with miflash
rom image: Here is the latest rom. (tissot_images_7.10.14_20171014.0000.00_7.1_d791bf99f4.tgz is the image I used while writing this guide)
miflash: MiFlash2017-7-20-0.zip
Boot to freshly flashed rom,
Install second october OTA update (75mb),
Do reboot and wait a few minutes until the update is installed.
If you have not done any changes to your device (other root like supersu, old magisk verision etc) you can ignore above step.
From settings-->developer options:
Usb debuging on
OEM unlocking on
Just to be on the safe side for magisk manager app also go to Settings --> Security and enable Unknown sources.
Then shutdown phone, boot phone to fastboot with Vol- & power button,
send the command "fastboot oem unlock" in order to unlock bootloader.
Phone reboots by it self if I remember correctly.
Boot to rom, now being unlocked, and see the splash screen to see if it says "Unlocked" to be sure that it is unlocked.
Then shut down the phone.
Again boot phone to fastboot with Vol- & power button,
boot twrp (just boot, not flash) with command "fastboot boot recovery.img"
recovery-3.1.1-1
From twrp, install Magisk-v14.4-20171103-073038
It installs magisk 14.4 but magisk manager apk version installed with this is 14.0.
So, in order to have magisk 14.4, reboot to rom, uninstall magisk manager and then install Magisk Manager 5.4.0 (as suggested by matcho13579) MagiskManager-v5.0-20170513.apk
The problem now with this version of magisk manager is that it installs modules correctly and they work just fine, but the installed modules are not listed in magisk manager modules page (they work but they cannot be seen). That means that you cannot disable a single module, you have to enable magisk core mode to disable all of them or normal mode to have all modules enabled - I hope this will be fixed in a newer version. Magisk-v14.4-20171103-073038 zip file as I said installs magisk manager 14.0 which also appears to be working, but I did all tests on my device with MagiskManager-v5.0-20170513.apk installed.
Next, inside magisk manager downloads, search and install xposed framework sdk 25 systemless by topjohnwu.
After installation is completed reboot phone (phone boot takes some time at this step).
Then install this Xposed installer apk -material design XposedInstaller_by_dvdandroid_31_10_17.apk.
Now you have October 2nd update rom in your device, magisk 14.4 & xposed framework.
If you select magisk core only mode (which disables magisk modules), have enabled magisk hide and hide it form all apps except the ones you want to have root access, the device passes safetynet and theoretically you can install OTA updates (xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled), according to this link
Inside magisk manager you can also install this MiA1Plus_V1.01 module in order to enable camera2api & EIS, to be able to use google camera application.
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working, I have not tested it thoroughly though:
https://forum.xda-developers.com/showpost.php?p=73340439&postcount=2
https://forum.xda-developers.com/attachment.php?attachmentid=4317286&d=1509267532

After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk

How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.

Aman301582 said:
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Click to expand...
Click to collapse
Recovery is included in boot.img

tidschi said:
Recovery is included in boot.img
Click to expand...
Click to collapse
Which means I'll lose root after flashing ?

Aman301582 said:
Which means I'll lose root after flashing
Click to expand...
Click to collapse
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?

blackyz01 said:
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
As I have written in the first post "xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled"
This means that if you enable magisk core mode which disables all modules or if you disable xposed framework module, it passes safetynet.

tidschi said:
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
Click to expand...
Click to collapse
Okay, managed to get stock recovery back. But 2nd ota is not installing. Always fails

Why install old Magisk Manager? New one seems like it works, unless I am missing something..

ilpanos said:
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working
Click to expand...
Click to collapse
Only one question about this: why did you choose NON-FBE version instead of the normal one?

Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?

matcho13579 said:
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Click to expand...
Click to collapse
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.

suryaabadsar said:
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
Click to expand...
Click to collapse
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.

Will we lose root after an OTA update?

You have to do the procedure as described in the link I have provided in the first post. I am putting it again here:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

ilpanos said:
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
Click to expand...
Click to collapse
I'm currently using the normal version and everything is working as intended.
That's why I ask, because it might not work the same way with Magisk (I used CF-Root + SuperSU + standard Xposed method)

ilpanos said:
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Click to expand...
Click to collapse
I HAVE UNROOT PHONE WITH THE SAME METHOD AND RE-LOCK BOOTLOADER WITH FASTBOOT COMMAND fastboot oem lock
NOW OTA WILL WORK PROPERLY ON MY PHONE.?

Thanks for the perfect guide.
One side note: official ROM on the provided link is already version .30, so no need to boot into the ROM and install the updates, the update is already merged in

@ilpanos hello mate! I just ordered my A1 from Trading Shenzhen. I have an clear conception what to do with my A1 when it has arrived. So therefore I am collecting some knowledge about flashing and modding (I am not a beginner, but not familiar with A/B partitions). Your thread is very useful here, many thanks.
I have still one question and maybe you can answer it: i would like to remove the google apps from the system, but I don't know if this works just like usual (to remove it from /system/app or priv-app). The reason is that I am using microG instead gapps.
Or will removing files and folders screw up something?
Thanks in advance!
Cheers!

Well, the thing is that by even mounting system partition as read-write ,and of course doing any change - even adding a line in build.prop - disables the ability to do OTA updates. You will have to reflash the new rom for each update. This is the purpose of this thread, to show that there is a way to mod root etc systemlessly without loosing the ability to update (of course under certain conditions).

[UPDATE/KEEP ROOT GUIDE] JAN 2021 (RQ1A.210105.003) "CORAL" Magisk/Stock Boot Images

GravityBox [R] was pre-released today! Thus, I was able to update, using this very method, all the way from August 2020 thru January 2021. Entire process took only about an hour, with no hiccups. =) =) =)
But luckily, that also means I can actually start confirming again, personally, that everything is working fine. I can happily report everything is working great after this update. SafetyNet is passing with the correct configurations, and January 2021 build is working perfectly so far with Kirisakura 6.6.6 (why @Freak07, why did you have to release as this particular version number?? lol).
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ1A.210105.003, Jan 2021"!
Magisk v21.2 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145709333
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145709334
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145709335
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ1A.201205.008, Dec 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq1a.201205.008-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675600188
coral-rq1a.201205.008-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675600190
January 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq1a.210105.003-ad8d5ecc.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq1a.201205.008-factory-boot.img
3. fastboot flash dtbo coral-rq1a.201205.008-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq1a.210105.003-ad8d5ecc.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq1a.210105.003-magisk_patched-21.2.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------​
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16

[EDIT 01-13-2021] YET ANOTHER NEW SAFETYNET WORKAROUND (AS OF AROUND JANUARY 12 / 13):
Please see this post: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84285539

Thank you for the update guides as always.

Just wanted to say a quick thanks. Worked like a charm!

Worked like a charm

I'd like to ask someone for help! If you haven't updated yet (i.e. you're still on 2020-12 patch level [non-AT&T]), and NOT using Edge Sense Plus (Active Edge Mod in Magisk Manager and/or EdXposed Manager) NOR any of Tulsadiver's theming mods (3minit / clock / 9tiles / etc), could you please send me your stock SystemUIGoogle.apk file? You can find it, using a root capable file explorer app, under:
(root) /system_ext/priv-app/SystemUIGoogle/SystemUIGoogle.apk
It needs to be the stock, completely unmodified .apk, which is why I'm asking to make sure you're not using any of those mods I mentioned. Or, you could disable those mods temporarily (both Magisk and EdXposed), reboot, and pull the .apk file. Unfortunately whenever I pull it from Google's factory system image always seems to be corrupted. Would just be easier for me if I could get it from someone's up-and-running system...
Thanks!! I really hope someone can do me a solid...
Or, does anybody know if it's safe to "downgrade" to December 2020? Using the full factory image and removing -w flag (and replacing boot.img with magisk patched)? I would think it would work, but I've never tried, nor needed, to flash the previous month's firmware before.

i5lee8bit said:
I'd like to ask someone for help! If you haven't updated yet (i.e. you're still on 2020-12 patch level [non-AT&T]), and NOT using Edge Sense Plus (Active Edge Mod in Magisk Manager and/or EdXposed Manager) NOR any of Tulsadiver's theming mods (3minit / clock / 9tiles / etc), could you please send me your stock SystemUIGoogle.apk file? You can find it, using a root capable file explorer app, under:
(root) /system_ext/priv-app/SystemUIGoogle/SystemUIGoogle.apk
It needs to be the stock, completely unmodified .apk, which is why I'm asking to make sure you're not using any of those mods I mentioned. Or, you could disable those mods temporarily (both Magisk and EdXposed), reboot, and pull the .apk file. Unfortunately whenever I pull it from Google's factory system image always seems to be corrupted. Would just be easier for me if I could get it from someone's up-and-running system...
Thanks!! I really hope someone can do me a solid...
Or, does anybody know if it's safe to "downgrade" to December 2020? Using the full factory image and removing -w flag (and replacing boot.img with magisk patched)? I would think it would work, but I've never tried, nor needed, to flash the previous month's firmware before.
Click to expand...
Click to collapse
Well I have a pixel 4 xl and I've rolled back to android 10 back in October, due to 11's bugs. So in my experience it is safe to roll back to previous updates. Being that I flashed

Suavie103 said:
Well I have a pixel 4 xl and I've rolled back to android 10 back in October, due to 11's bugs.
Click to expand...
Click to collapse
Would you mind sharing what kind of bugs you are facing on 11 please? I was going to update from 10 soon.

Ghisy said:
Would you mind sharing what kind of bugs you are facing on 11 please? I was going to update from 10 soon.
Click to expand...
Click to collapse
No those bugs were when 11 was first released. The January 11 update is perfectly fine imo. You should update

Thanks as always. Works like a charm

I just got the OTA update this week (1-14-2021) and was just wondering if the 1st post is still valid? Right now I am on Android 11 (RP1A.200720.009). Which files do I need to download from Google to go from RP1A.200720.009 to the latest OTA? Thanks in advance!

I am confused on number 8 ( 8. fastboot flash boot coral-rq1a.210105.003-magisk_patched-21.2.img ) where do I get that patched img file from? I am already rooted with Magisk vf5593e05 (4835)

One more small question.... what does DTBO stand for? I have never heard of that?

OMG!!!! I did it!!! Woo Hoo!!! Took me about 30 minutes! I did not flash the " coral-rq1a.201205.008-factory-dtbo.img " because I am not using a custom kernel just straight stock!
It scared me at first because it was taking so long for my Pixel 4 Xl to boot back up but it finally came back on.
I also had to update Magisk to f5593e05 (21401).
I have now went from Android 11 (RP1A.200720.009) to Android 11 (RQ1A.210105.003) and I still have ROOT!!!
Thank you @i5lee8bit for this easy to use guide! I am still a noob using ADB but I am learning more and more!
Oh yea... you said "GravityBox [R] was pre-released today!" where can I get that from? Does it work good?
Is anyone monitoring this thread? I feel all alone!

Perfect write-up. Followed it as instructed, had my phone rebooted with the new update in less than 10 minutes. Even had to double-check that it actually updated since it rebooted so fast!
Thanks!

The February update is out. Anyone got the magisk patched file?

For some reason I'm getting installation error when trying to patch boot image. Tried canary & stable magisk APK. Can someone confirm this?

I got the same, on canary

No issues here. Everything worked first try. Updating phone now, guide will be up soon (assuming no other errors otherwise).
Edit: It's up: https://forum.xda-developers.com/t/...5-004-coral-magisk-stock-boot-images.4227845/
Will also be editing the Active Edge Mod for Edge Sense Plus module really soon, and will be indicated on that thread: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/

i5lee8bit said:
No issues here. Everything worked first try. Updating phone now, guide will be up soon (assuming no other errors otherwise).
Click to expand...
Click to collapse
Same here. Working fine with Beta 21.4 on February update.

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.

Magisk 24.1 no Zygisk option available

I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.

Your screenshot shows that Magisk is not installed.
You only installed the app. Try install in the upper right corner and choose for direct install without patching.

Prof_Shekhar said:
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Click to expand...
Click to collapse

xabu said:
Your screenshot shows that Magisk is not installed.
You only installed the app. Try install in the upper right corner and choose for direct install without patching.
Click to expand...
Click to collapse
Thank you xabu for your reply.
I had tried to install it numerous times using the direct install method as suggested by you but it gives me a "installation failed" message (Screenshot attached).
Also, presuming that my previously installed magisk v 23.0 may not have been uninstalled during the process of auto update to magisk version 24.1 (only 24.1 app installed but not magisk itself not upgraded due to unknown reasons), I reinstalled the app v 23 and uninstalled magisk completely. Frustrated, I installed the stock firmware again, reinstalled TWRP and flashed magisk 24.1. However, the result appears to be same. No magisk installation.
It appears to me that magisk v 23 is not yet completely uninstalled as if I delete this 24.1 app, reinstall app for 23.1 most of the functionality comes back though not all. I still can't hide magisk but it passes safety check.

Also I have tried to uninstall any previous version of magisk using renamed magisk app as uninstall.zip via TWRP. Also I get following message:
"cannot find vbmeta partition, patch vbmeta in boot image.
Removing magisk files."
Now when I go to Magisk app, I get only option to "select and patch a file."
Appreciate if anyone can suggest me a way forward.

Also, I get the vbmeta partition not found error while trying to install Magisk via TWRP (screenshot attached)

I have selected and installed Magisk patched boot image file using ODIN3. Removed TWRP. Tried to install using Magisk app 24.1 but get installation failed due to unable to check signature (screenshot attached).
Request some guidance.

Start here ....
Magisk - The Age of Zygisk.​Your questions are very interesting but too difficult for me to answer. Magisk 24.1 normally replaces the 23 almost automatically .... By uninstalling the module the situation becomes completely different and you should probably start from scratch. In my link "start here" you'll find the place where real specialists are.
Wishing you all the best !

Appreciate your advice.
However, I have reinstalled the stock firmware 3 times since this morning just as to ensure that I start from a clean slate. Also used Adb commands to uninstall any remanants of the previous Magisk manager if at all left there.
However, still stuck with the puzzling question as to where am I going wrong.

Prof_Shekhar said:
Also I have tried to uninstall any previous version of magisk using renamed magisk app as uninstall.zip via TWRP. Also I get following message:
"cannot find vbmeta partition, patch vbmeta in boot image.
Removing magisk files."
Now when I go to Magisk app, I get only option to "select and patch a file."
Appreciate if anyone can suggest me a way forward.
Click to expand...
Click to collapse
Exact same issue for me!

Also for me....same tests that @Prof_Shekhar have done

Prof_Shekhar said:
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Click to expand...
Click to collapse
The same thing happened to me so i tried and tried and tried for like 4-5 hours after reinstalling multiple times the firmware so i gave up and came to the conclusion that its not supported yet for a few phones like the Note8 (SM-N950F ~ my version of the phone).So the only thing you can do rn is to stick to version 23.0 then go to settings and change the channel to custom channel and paste this link "https://raw.githubusercontent.com/t...304e59f631280cc26ccc6d40a7cf04f7f37/beta.json" in there so the magisk version doesn't update itself or you update it by accident

Beast-chan said:
The same thing happened to me so i tried and tried and tried for like 4-5 hours after reinstalling multiple times the firmware so i gave up and came to the conclusion that its not supported yet for a few phones like the Note8 (SM-N950F ~ my version of the phone).So the only thing you can do rn is to stick to version 23.0 then go to settings and change the channel to custom channel and paste this link "https://raw.githubusercontent.com/t...304e59f631280cc26ccc6d40a7cf04f7f37/beta.json" in there so the magisk version doesn't update itself or you update it by accident
Click to expand...
Click to collapse
@Beast-chan
Hope you were able to install Magisk 24.1 Canary version without any further issues.

Prof_Shekhar said:
@Beast-chan
Hope you were able to install Magisk 24.1 Canary version without any further issues.
Click to expand...
Click to collapse
tbh i didnt try the Canary version...does it work or why do you ask?

Beast-chan said:
tbh i didnt try the Canary version...does it work or why do you ask?
Click to expand...
Click to collapse
@Beast-chan
Definitely. I have installed Magisk 24.1 Canary using patched AP file from stock firmware, and then reinstalled the Magisk 24.1 Canary version. It has been working without any issues since then.
Don't forget to install universal safetyNet Fix.
Let me know if you run into any issues.

Prof_Shekhar said:
@Beast-chan
Definitely. I have installed Magisk 24.1 Canary using patched AP file from stock firmware, and then reinstalled the Magisk 24.1 Canary version. It has been working without any issues since then.
Don't forget to install universal safetyNet Fix.
Let me know if you run into any issues.
Click to expand...
Click to collapse
ok ty i will try it