Database Info

Magisk 19.1 / 7.1.2 Notes

This is for if you have Magisk 18.1 installed with manager version 7.1.1. Upgrading to manager 7.1.2 and then directly installing 19.1 caused my I3223 to go into a boot loop.
Image patching seems to have changed as well. With manager 7.1.1 we were able to directly patch the boot_X_FLASH_ALL-*.sin file. I had to extract boot.000 from the sin file before the new manager would patch it. Even so, the result is still a boot loop.
Reflashing older patched boot images did not restore root. In short, hold off on upgrading Magisk. If you have a solution please share. Thanks.

I was able to flash the older (v18.1) magisk patched boot image using fastboot. I will attach the image here if you need too. I had to split the RAR file into 3 parts due to limitation of XDA of RAR files to be 8MB.
Root is working fine, I was able to grant access to Titanium Backup. But seriously that was messed up. If that happened to my Shield TV and I lost all of my games I will be furious. Luckily, I tried that on the Shield TV before knowing it will mess up my Xperia 10 plus phone. What is more messed up is there is no way from Magisk Manager to keep using older APK or download older version of Magisk, I tried Custom URL in the settings to check the update from, but all I got was a spinning wheel while checking for updates.
Currently running Magisk Manager 7.1.2 and v18.1 , just ignoring the ZIP update.
Rule of thumb, if it aint broken, don't fix / update.

Thank you Rebel_X. I will try again tonight. I was hoping to retain userdata but that's probably what's giving me problems with the revert.

Has anyone tried 19.1 patched boot image on a fully reset phone? Do we know if that works?

Rebel_X said:
I was able to flash the older (v18.1) magisk patched boot image using fastboot. I will attach the image here if you need too. I had to split the RAR file into 3 parts due to limitation of XDA of RAR files to be 8MB.
Root is working fine, I was able to grant access to Titanium Backup. But seriously that was messed up. If that happened to my Shield TV and I lost all of my games I will be furious. Luckily, I tried that on the Shield TV before knowing it will mess up my Xperia 10 plus phone. What is more messed up is there is no way from Magisk Manager to keep using older APK or download older version of Magisk, I tried Custom URL in the settings to check the update from, but all I got was a spinning wheel while checking for updates.
Currently running Magisk Manager 7.1.2 and v18.1 , just ignoring the ZIP update.
Rule of thumb, if it aint broken, don't fix / update.
Click to expand...
Click to collapse
Hay, what model is your Xperia 10 plus?
My phone is I4293, i used your boot.img, when reboot, nothing is changed, just not rooted.

yishisanren said:
Hay, what model is your Xperia 10 plus?
My phone is I4293, i used your boot.img, when reboot, nothing is changed, just not rooted.
Click to expand...
Click to collapse
Mine is I3223. I don't know if it is compatible with your model, but if it flashed fine and the phone booted, try to install magisk manager apk v7.1.1 and see if you are rooted.

Rebel_X said:
Mine is I3223. I don't know if it is compatible with your model, but if it flashed fine and the phone booted, try to install magisk manager apk v7.1.1 and see if you are rooted.
Click to expand...
Click to collapse
It flashed fine, also my phone can be booted, but not rooted.
:crying::crying::crying:

Have you guys tried to summit a bug report on magisk's github issue page?

https://github.com/topjohnwu/Magisk/issues/1537
The bugreport about magisk bootloops on xperia devices

Root broken after forced update on t-mobile.

So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!

Honestly not sure how you got the update with twrp installed it always failed for me. Had to restore original boot.img to install.
But the update relocks the bootloader ... At least it did for me so hopefully you still have your unlock bin. Just unlock the bootloader and root as usual.
Unfortunately unlocking wipes.
If your bootloader didn't relock just root per the guide

nujackk said:
If your bootloader didn't relock just root per the guide
Click to expand...
Click to collapse
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
StrawHatZakk said:
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
Click to expand...
Click to collapse
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
StrawHatZakk said:
Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp.
Click to expand...
Click to collapse
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.

StrawHatZakk said:
So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!
Click to expand...
Click to collapse
Just reflash twrp/magisk with powershell
Go to settings developer mode turn off auto install updates.

redpoint73 said:
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.
Click to expand...
Click to collapse
I took my sweet time trying it but wanted to get root back as I just moved and won't have internet for a while. Everything seemingly went fine, got TWRP going then after installing Magisk it would just hang at the t-mobile screen indefinitely. Attempted to do a restore with TWRP and must have hit a leftover restore from the previous android version now the only thing it does is boot to the fast boot section. Might make a new topic but I'm searching everywhere for a fix, can't seem to get this MSM tool thing to recognize it... thinking I might just be boned. If you know of any fixes let me know lol.

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.

[Pixel 3a][Android 11][ROOTED][TWRP 3.6.0] Install OTA without reverting to stock

Hello!
I am on an older version of Android 11 and I would like to install the latest Android 11 OTA without losing root and TWRP.
I know that I could just manually flash the lasted Android 11 firmware, then re-install TWRP and Magisk, but this would mean losing all data and having to reinstall apps, restore backups, etc...
So I was wondering if there were a quicker way to install OTA updates without losing data and root.
I know that there are many articles on the subject but they all refer to a previous version of TWRP and Magisk. Because TWRP 3.6.0 sports a completely revamped codebase I would like to know what is the latest recommended method if any.
This is my system info:
Android 11 sargo-rq1a.201105.002-factory-2433e0c0
Magisk v23
TWRP 3.6.0-11_0
Japan region
PS I do not intend to update to Android 12 yet

I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.

I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).

reyqn said:
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
Click to expand...
Click to collapse
The flashall script will still remove TWRP and root though, right?

blksith0 said:
The flashall script will still remove TWRP and root though, right?
Click to expand...
Click to collapse
Yeah it does, you have to reflash them after

It's annoying that we can't choose the OTA android installs, it has to be the latest one. On some phones you can choose a local file, but I didn't find a way to do so with a pixel 3a.
If you were able to do this, in theory you could just flash the magisk module for twrp retention and preflash magisk on the unactive partition after installing the ota but before rebooting. Then just reboot and you keep everything.
I'm not ready to update to android 12 either (gravitybox, twrp), but I'll try then...

LastStarDust said:
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
Click to expand...
Click to collapse
I don't understand. Just flash the Full Factory OTA zip in TWRP. That won't remove any data. And you can just check the box to "Automatically flash TWRP after zip" so that you'll keep whatever TWRP you're using. Then you just have to reboot recovery (so that you're on the updated slot) and flash the Magisk APK in TWRP. Reboot and profit.
P.S. This post belongs in Q&A.

Captain_Throwback said:
I don't understand. Just flash the Full Factory OTA zip in TWRP
Click to expand...
Click to collapse
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?

reyqn said:
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
Click to expand...
Click to collapse
That 'recommendation' is specific to incremental OTAs. Also, it not generally being supported isn't the same as it not being recommended.
TWRP will install the zip to the inactive slot, and then when you reboot, the device will automatically boot into the updated slot.

Thanks for the precisions, I'll know for the next time. TWRP really is awesome

hi everyone, i flashed pixel 3a to android 12 and now my imei is 004400.... and no service ..... what should i do?

Probably encrypted device TWRP files with weird file names - Android 12

Since oneplus 6 nas no security updates i decide to install custom ROM LineageOS 19.1 the newest build from official website.
Before installing this ROM i do all steps gently from Funky Wizard guide.
I have ADB drivers, unlock bootloader, installed magisk (rootet phone) backup my OOS and EFS, and installed twrp.
All basic stuff. Now i was ready to go to installed lineageOS.
I install lineage and i do all steps by their official website but with twrp. ( only what i dont flash copy partition zip file i wasnt sure if that will be work with twrp ).
After restart to recovery i must install gapps. Unfortunely the recovery was replaced i was assumed istead of twrp.
I installed gapps with their recovery and all work fine until i want to replace to twrp.
Now when i boot temporarly from img to install it perm. I have weird folder names wihtout any possibility to add ZIP file.
With some research i guess that folders are somehow encrypted.
Could you help me to install twrp with lineageOS when i have still access to this files? I need it for ex. recovery to stock if something in future goes wrong.
And i am currently on android 12 for sure.
Thank you from feedback!

first of all, you'd be better of if you posted this in the right area ==> https://forum.xda-developers.com/t/rom-official-enchilada-12-lineageos-19.4437321/ ==> more chance to get help related to LOS 19 questions (it's pure chance I saw your post here)
second: make sure to follow the instructions given at the LOS instructions pages ==> https://wiki.lineageos.org/devices/enchilada/
Mostly it is important that you have latest OOS 11 firmware installed in both slots before you start with LOS.
For the first steps never mind which recovery you have, just follow the instructions using LOS recovery. Reason is that TWRP is having problems wiping data / performing factory reset, at least it never worked for me. Then later on you can switch to TWRP
Back in May this year I wrote an instruction set here: https://forum.xda-developers.com/t/rom-official-enchilada-12-lineageos-19.4437321/post-86879331
Interesting for you right now is everything below 1.x
2.x is a separate instructiopn set for OTA updates coming later on
Good luck!

Thank you for response. You have right its better to install it directly from dedicated recovery (lineage) and than replace with twrp. Also i fill missing steps (install recovery again and flash parition integration file) and also wipe all data as instruction says. Now after reinstall lineageos and then install twrp i have all normal structure files as before. Thanks again