Related
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
anirbannath said:
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
Click to expand...
Click to collapse
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
sunshinebhushan said:
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
Click to expand...
Click to collapse
mine also any sol to fix this?
Steps to fix any root mess-up that might happened and/or corrupt system from tampering with files.
1. Follow this guide, you can start from the flashing part
2. Download the mi flash app + a1 fastboot stock rom
3. Flash using the guide, make sure you select 'save user data'! or you will lose all your data!!
4. Once the flashing is complete you will reboot into the august patch, go to updates and install all the updates as usual
5. Root/Flash recovery using your favorite method.
I played around the system partition too much and had some issues with play services, also I couldn't update to october patch, after doing the above, everything works great. just use this guide anytime you want a clean slate.
Also always backup everything on twrp, always a useful thing to do.
Good luck
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
sunshinebhushan said:
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
Click to expand...
Click to collapse
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
Hi. As I mentioned, I am not even on the September patch. I used to be but then I rooted it today (installed Magisk) and suddenly I'm back to the August patch. September patch only installs in 'a', which is not rooted. That doesn't really serve my purpose.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
Hi. There seems to be a problem with what you suggest. The video I followed does almost the same thing. I even have TWRP, along with Magisk of course. The problem is, when I boot to 'a' (the partition that successfully installs the September update), I find that it isn't rooted. Magisk is inactive. And root checker says that root isn't properly installed. So obviously, the question of unrooting is rendered moot.
I want to be able to install the OTA update in my rooted partition and make it stick. People have installed OTA updates to rooted ROMs (mostly using FlashFire), but Flash Fire is giving me an unusual error, something about being unable to install OTA even though it has detected it due to being unable to find some files in boot/recovery folder or something like that.
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Ex-Hunter said:
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Click to expand...
Click to collapse
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
I got bootloop when installing october security patch......
I have unlocked bootloader and also rooted my phone using CF-auto-root but when try to install october security update after reboot my phone got bootloop.....
So, what do i do now ?
anirbannath said:
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
Click to expand...
Click to collapse
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
Code:
fastboot getvar all
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
sunshinebhushan said:
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
Click to expand...
Click to collapse
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Ex-Hunter said:
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Click to expand...
Click to collapse
I am trying to edit directly, what is the other way to edit?
sunshinebhushan said:
I am trying to edit directly, what is the other way to edit?
Click to expand...
Click to collapse
You've to use resetprop tool for that. You can modify an existing module or put a script at /magisk/.core/service.d (I think.... haven't done that in a long while). You can ask magisk related queries here (unofficial magisk 13.4) or here (official)
Ex-Hunter said:
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
kiran8631 said:
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74203817&postcount=4
by flashing with flashfire rooted and installed supersu without twrp flash and now wifi stopped working rest everythig works just fine..for now i m back2stock...can any one tell me the most safe procedure wich do not break any drivers. i m on 1st october patch. thank you in advance
I've got an xt1768 RETAIL on npqs26.69-64-2 with bootloader unlocked. I flashed magisk, xposed system-less and the f2fs cache modules a while ago and just got the prompt for the new ota. I thought the update procedure was to disable magisk, reboot and then install the ota normally. After disabling magisk and rebooting the boot process gets stuck at "bad key", i assume because magisk modified one of the images. I'm able to get back into the bootloader and boot twrp and reflash magisk and everything boots up fine after. If anyone has a guide with the steps to actually do the update I'd appreciate it.
xeropressence said:
I've got an xt1768 RETAIL on npqs26.69-64-2 with bootloader unlocked. I flashed magisk, xposed system-less and the f2fs cache modules a while ago and just got the prompt for the new ota. I thought the update procedure was to disable magisk, reboot and then install the ota normally. After disabling magisk and rebooting the boot process gets stuck at "bad key", i assume because magisk modified one of the images. I'm able to get back into the bootloader and boot twrp and reflash magisk and everything boots up fine after. If anyone has a guide with the steps to actually do the update I'd appreciate it.
Click to expand...
Click to collapse
Well the thing is, you've modified your boot.img and unencrypted your device. So ota is not really going to work. Normally, you uninstall magisk and restore your stock boot.img, and if you've only booted twrp, you could take the ota. Did you also flash the no verity opt encrypt zip?
The problem is, when you flash the stock boot.img, your device is going to re encrypt as soon as you boot.
So you'll likely need the full firmware package to update. I do mine with rsdlite and the service file.xml within the full firmware when it becomes available.
Someone else may have better news for you, but I don't.
madbat99 said:
Well the thing is, you've modified your boot.img and unencrypted your device. So ota is not really going to work. Normally, you uninstall magisk and restore your stock boot.img, and if you've only booted twrp, you could take the ota. Did you also flash the no verity opt encrypt zip?
The problem is, when you flash the stock boot.img, your device is going to re encrypt as soon as you boot.
So you'll likely need the full firmware package to update. I do mine with rsdlite and the service file.xml within the full firmware when it becomes available.
Someone else may have better news for you, but I don't.
Click to expand...
Click to collapse
I did not flash the no verity opt encrypt zip, pretty sure magisk sets no verity by default as that setting is unchecked in the magisk manager. Device is still encrypted. It was my understanding that when using the restore image uninstall of magisk boot.img would be restored to its stock state, which leads me to believe that the system partition was modified.
xeropressence said:
I did not flash the no verity opt encrypt zip, pretty sure magisk sets no verity by default as that setting is unchecked in the magisk manager. Device is still encrypted. It was my understanding that when using the restore image uninstall of magisk boot.img would be restored to its stock state, which leads me to believe that the system partition was modified.
Click to expand...
Click to collapse
So you kept encryption too? Then you should be able to restore stock boot.img and take ota. Unless you have modified your system somewhere along the way. Magisk itself doesn't modify it.
Most are not able to get the phone to boot with encryption enabled.
So if you have not modified system at any point, then restoring the stock boot.img should have worked.
You can download the stock firmware that your device is currently on and flash the system.img and boot.img from it to be certain.
Edit:
Oohhh, it's not stuck at bad key, it just takes awhile to pass that. It's because of unlocked bootloader. Without a patched boot.img, it says bad key, but it should proceed after a minute or two. Sorry, just re read your first post.
October Security Patch has been posted.
What is the size of this update? I received only 7.1mb update ?
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
I don't know. Flashed the full image from Google.
in Germany, the update is also so big
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
Yes, it is 7.1 MB. Strange.
Wow huge update! My WiFi couldn't cope up with 7.1mb update. Awesome Google ?
Nothing here yet, T-Mobile, Houston.
Edit: received OTA last evening 10/08. I believe the size was 7.4mb.
Sent from my [device_name] using XDA-Developers Legacy app
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
Dude sometimes this phone just needs a little extra... Lol glad you kept your cool and hung in there.
Sent from my Pixel 2 XL using XDA Labs
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
How did you "reflash magisk and kernel?" Did you boot to system first?
astaineakash said:
What is the size of this update? I received only 7.1mb update ?
Click to expand...
Click to collapse
Me too
jlokos said:
How did you "reflash magisk and kernel?" Did you boot to system first?
Click to expand...
Click to collapse
Yes after flashing factory image without wiping, i booted up to system then checked magisk wasnt installed (only manager app), then i fastbooted to twrp recovery flashed custom kernel then flashed magisk and reboot, thats it, and all my magisk settings returned back to what it was like before all this
Can anyone please post the fingerprint for the October build from build.prop?
Much thanks!!
Any easy way to install this on a rooted phone without wiping data?
Dylan.4 said:
Any easy way to install this on a rooted phone without wiping data?
Click to expand...
Click to collapse
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Since October patch (rooted) I have massive problems my pc/my phone detecting my phone/my pc. I dont know why, its just charging, one time it worked (I need USB-Tethering) I was just restarting and restarting the phone, turning debugging on/off...
Any idea how to fix this?
edit: It just says unknown usb-device, I manually uninstalled and installed the latest android usb drivers. If I try to use an adb command it just says "error: no devices/emulators found"
Probably the worst security patch. My sensors aren't working properly, phone doesn't go off while i talk. It hangs at odd occasions. Battery is weak. Auto brightness isn't working either
hawkjm73 said:
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Click to expand...
Click to collapse
Perfect, it worked. Thank you!
Update 220823: Update for TWRP 12 and some other minor changes due to the switch from SafetyNet API to Play Integrity API
Updated 211203: include Magisk Canary
Edited 220113: correct a mistake in the Keeping Root process; some formatting changes
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggests using "Install to inactive slot" which works provided you do it properly - see https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253.
And here's how to do it using TWRP.
What you'll need:
OOS 11: TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449
OOS 12: TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/...win-recovery-project-8t-9r-2022-07-27.4473983
Magisk apk - using stable from https://github.com/topjohnwu/Magisk/releases or using Canary from https://github.com/topjohnwu/magisk-files/tree/canary
Universal SafetyNet Fix (UNSF-MOD) by @Displax from https://github.com/Displax/safetynet-fix/tree/integrity
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
Boot into bootloader mode.
Boot TWRP using fastboot boot x.img where x.img is the TWRP image file.
Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available.
Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it. Also install USNF if you are using Magisk Canary.
If you want to keep TWRP then install the TWRP installer zip.
Reboot.
If you are using Magisk Canary, in Magisk>Settings enable Zygisk, Enforce DenyList, and Configure DenyList. Then reboot.
Keeping Root on an incremental OTA update
Note: you do NOT need to (but can if you want to) follow this process if you're installing a full OTA. You only need to install the full OTA and then install Magisk to the inactive slot and reboot from Magisk when it prompts you.
If your phone tells you you have an update:
If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot.
In Magisk tap on "Uninstall Magisk" and select "Restore images".
Install the OTA update but don't reboot yet.
Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root.
Reboot
When the phone has successfully rebooted the updated system, boot into bootloader mode.
Boot TWRP using fastboot boot x.img where x.img is the TWRP image file.
Take a backup of the current recovery partition as you'll need it for successfully updating when the next incremental OTA becomes available.
Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
If you want to keep TWRP then flash the TWRP installer zip.
Reboot and disable airplane mode.
BillGoss said:
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggest this method (https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145) but this doesn't work for everybody (it doesn't for me).
And here's how to do it using TWRP.
What you'll need:
• TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/
• Magisk apk - I'm using v23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
1. Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
2. Boot into bootloader mode
3. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
4. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
5. Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it.
6. If you want to keep TWRP then install the TWRP installer zip.
7. Reboot
Keeping Root on an OTA update
If your phone tells you you have an update:
1. If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot
2. In Magisk tap on "Uninstall Magisk" and select "restore images". Or, if you're like using terminal commands, restore the stock boot image (you backed it up with TWRP) to the current slot using dd
3. Install the OTA update but don't reboot yet.
4. Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root
5. Reboot
6. When the phone has successfully rebooted the updated system, boot into bootloader mode
7. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
8. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
9. Clean up old Magisk backup copies of stock boot images by using File Manager to delete /data/magisk_backup_* directories
10. Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
11. If you want to keep TWRP then flash the TWRP installer zip.
12. Reboot and disable airplane mode
Click to expand...
Click to collapse
ctsProfile fails. Is there a way to fix it? Tried stable Magisk and Canary.
morphius88 said:
ctsProfile fails. Is there a way to fix it? Tried stable Magisk and Canary.
Click to expand...
Click to collapse
Best place for getting support for Magisk is https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/
Hi,
Thanks for the guide!
What can i do if i forgot to backup stock boot and recovery?
berthur said:
Hi,
Thanks for the guide!
What can i do if i forgot to backup stock boot and recovery?
Click to expand...
Click to collapse
You have a number of options:
If your update was an incremental OTA:
1. Ask in the Q&A forum or in one of the update threads if someone can share those two partitions with you.
2. If you're on 11.0.10.10kb05aa then you can get boot from a number of the update/rooting threads and the recovery from this thread by @mslezak https://forum.xda-developers.com/t/...-rooted-users-install-from-fastbootd.4316147/
3. Use this tool by @mslezak to create the full partitions from an incremental update https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/
If you updated using a full installation zip:
- use payload dumper to extract the two partitions from payload.bin
BillGoss said:
You have a number of options:
If your update was an incremental OTA:
1. Ask in the Q&A forum or in one of the update threads if someone can share those two partitions with you.
2. If you're on 11.0.10.10kb05aa then you can get boot from a number of the update/rooting threads and the recovery from this thread by @mslezak https://forum.xda-developers.com/t/...-rooted-users-install-from-fastbootd.4316147/
3. Use this tool by @mslezak to create the full partitions from an incremental update https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/
If you updated using a full installation zip:
- use payload dumper to extract the two partitions from payload.bin
Click to expand...
Click to collapse
Than you!
Hello!
Does someone have a backup of the Stock recovery from OOS 11.0.10.10.KB05BA and can share it here?
Thanks in advance.
Wishmasterflo said:
Hello!
Does someone have a backup of the Stock recovery from OOS 11.0.10.10.KB05BA and can share it here?
Thanks in advance.
Click to expand...
Click to collapse
Download the zip from https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ and then use payload dumper to extract the files.
That worked like a charm. Thanks a lot.
I'm Magisk rooted and I have TWRP installed on my 8T EU model.
The OnePlus updater app registers that I am rooted and wants to download the full OTA.
Do I also have to do all the things you described after "Keeping Root on an OTA update" or is there a simpler way?
If yes, then I have a question regarding this step:
2. In Magisk tap on "Uninstall Magisk" and select "restore images".
Click to expand...
Click to collapse
Did Magisk automatically backup these images? Because I didn't do it myself. I only have backed up all my partitions (including boot) after I had installed TWRP and before I rooted.
EDIT:
BillGoss has thankfully already replied in another thread (in which I have basically asked the same question because I am an impatient bast***) where I suggested the overly present "easy" update scheme, which he expects to work. So this should be fine for other people in my situation:
1. Let the system download and install full OTA and DO NOT let the device reboot after it's done
2. Install TWRP A/B Retention Script
3. Install Magisk to inactive slot and reboot
EDIT2:
I just want to add that before having done the above mentioned steps 1-3, I have disabled all Magisk modules and rebooted the device. So the full procedure is the following:
1. Disable all Magisk modules and reboot
2. Let the system download and install full OTA and DO NOT let the device reboot after it's done
3. Install TWRP A/B Retention Script
4. Install Magisk to inactive slot and reboot
Youtube step by step video (he says that he "uninstalls" the Magisk modules but he just deactivates them):
Thanks @haitower
I've updated the OP to make it clear that the process described there only applies to incremental updates.
Also, to answer your question re Magisk backups: Magisk writes a copy of the installed boot image to /data/Magisk* before patching it. A "restore image" uses that backup.
BillGoss said:
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggests using "Install to inactive slot" but this doesn't work for everybody (it doesn't for me) which works provided you do it properly - see https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253.
And here's how to do it using TWRP.
What you'll need:
• TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/
• Magisk apk - I'm using v23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
1. Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
2. Boot into bootloader mode
3. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
4. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
5. Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it.
6. If you want to keep TWRP then install the TWRP installer zip.
7. Reboot
Keeping Root on an incremental OTA update
Note: you do NOT need to follow this process if you're installing a full OTA. You only need to install the full OTA and then install Magisk to the inactive slot and reboot from Magisk when it prompts you
If your phone tells you you have an update:
1. If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot
2. In Magisk tap on "Uninstall Magisk" and select "restore images". Or, if you're like using terminal commands, restore the stock boot image (you backed it up with TWRP) to the current slot using dd
3. Install the OTA update but don't reboot yet.
4. Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root
5. Reboot
6. When the phone has successfully rebooted the updated system, boot into bootloader mode
7. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
8. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
9. Clean up old Magisk backup copies of stock boot images by using File Manager to delete /data/magisk_backup_* directories
10. Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
11. If you want to keep TWRP then flash the TWRP installer zip.
12. Reboot and disable airplane mode
Click to expand...
Click to collapse
Hello,
Thank You for the detailed description, it helped me a lot.
I'm new with the Oneplus 8T phone. The last handset I had was the Mi MIX 2. The rules of using root are familiar to me and I understand everything from your description. I only have a question about TWRP, once I have them permanently installed on device, can I backup the system or date partition via TWRP? I always made backups in case i messed up something and didn't work properly.
This question came from https://twrp.me/oneplus/oneplus8t.html
They write there:
"This device uses Dynamic Partitions
This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.
In order to flash the individual partitions, you will have to boot into fastbootd."
I would be grateful for Your information, Thank You.
e1thx said:
Hello,
Thank You for the detailed description, it helped me a lot.
I'm new with the Oneplus 8T phone. The last handset I had was the Mi MIX 2. The rules of using root are familiar to me and I understand everything from your description. I only have a question about TWRP, once I have them permanently installed on device, can I backup the system or date partition via TWRP? I always made backups in case i messed up something and didn't work properly.
This question came from https://twrp.me/oneplus/oneplus8t.html
They write there:
"This device uses Dynamic Partitions
This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.
In order to flash the individual partitions, you will have to boot into fastbootd."
I would be grateful for Your information, Thank You.
Click to expand...
Click to collapse
See post #3 in https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-29-11.4302449/
Hello!
Today I saw that EU: 11.0.12.12.KB05BA was available as OTA Update so I started to download it using the "Keep root on OTA Update".
During the download I recognized that I was still only connected to mobile network 4G instead of WiFi.
So I stopped the download of the OTA, restarted the phone and turned on WiFi but now I don't get the notification for the new OTA Update anymore and when checking for new Updates it says that my OOS 11.0.11.11 is up to date.
I guess the system has somewhere already stored that I started the download of the new 11.0.12.12 OTA but did not finish it and now I don't get the message to download it anymore.
Any idea how I can fix this so that I can download the new OTA again?
Thanks a lot!
EDIT: I am downloading it now via OxygenOS Updater (the full OTA).
BillGoss said:
See post #3 in https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-29-11.4302449/
Click to expand...
Click to collapse
I understand that if I want to restore system and data when something doesn't work for me then I just do recovery for all the partitions, system, data etc that I do in twrp?
Please see the update in the OP regarding OOS 12.
I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?
I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.
I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..