So I followed the steps to update to Android 11 while keeping Magisk. During this process, you uninstall magisk, you update, then you install magisk again before you reboot...more to it than that but you get the picture.
I got temporarily stuck in a boot loop, and when the phone did successfully reboot, it didn't update to Android 11 and Magisk isn't installed anymore. The system update page basically says 'restart now.'
I don't really want to lose root, I don't want to update and lose root and somehow lose my data trying to figure this out.
Any thoughts?
If you aren't using Magisk Canary, it won't work.
coachmarino said:
So I followed the steps to update to Android 11 while keeping Magisk. During this process, you uninstall magisk, you update, then you install magisk again before you reboot...more to it than that but you get the picture.
I got temporarily stuck in a boot loop, and when the phone did successfully reboot, it didn't update to Android 11 and Magisk isn't installed anymore. The system update page basically says 'restart now.'
I don't really want to lose root, I don't want to update and lose root and somehow lose my data trying to figure this out.
Any thoughts?
Click to expand...
Click to collapse
just back up your data first and then play around with it. just fresh install a11 then root
Losing root is only temporary and won't cause any trouble.
You just have to update to android 11, reboot, then once it boots with a clean boot img you can patch the boot img file with the latest magisk manager canary, then go in fastboot and flash the patched img.
TENN3R said:
Losing root is only temporary and won't cause any trouble.
You just have to update to android 11, reboot, then once it boots with a clean boot img you can patch the boot img file with the latest magisk manager canary, then go in fastboot and flash the patched img.
Click to expand...
Click to collapse
I don't tinker with my phone as much anymore...what's the process here?
coachmarino said:
I don't tinker with my phone as much anymore...what's the process here?
Click to expand...
Click to collapse
I usually do like this:
- Download full factory image, extract it from the zip and edit the "flash-all.bat" removing the "-w" from the last line, so it won't wipe the data while updating
- Inside the folder you extracted there is another zip, extract the boot.img from it
- Copy the boot image to the phone, and using the latest magisk canary select to install magisk updating a file, and select the image you just copied
- In generates a magisk_patched img, copy that on your adb folder on your pc
- Put phone in fastboot, start the edited flash all bat, once it ends the phone will reboot with your data but no root
- Go again in fastboot and run "fastboot flash boot magisk_patched.img --slot=all"
- Reboot, you should have root now
TENN3R said:
I usually do like this:
- Download full factory image, extract it from the zip and edit the "flash-all.bat" removing the "-w" from the last line, so it won't wipe the data while updating
- Inside the folder you extracted there is another zip, extract the boot.img from it
- Copy the boot image to the phone, and using the latest magisk canary select to install magisk updating a file, and select the image you just copied
- In generates a magisk_patched img, copy that on your adb folder on your pc
- Put phone in fastboot, start the edited flash all bat, once it ends the phone will reboot with your data but no root
- Go again in fastboot and run "fastboot flash boot magisk_patched.img --slot=all"
- Reboot, you should have root now
Click to expand...
Click to collapse
Perfect thank you
Related
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/sho....php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3a.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3aRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
oh my gosh would you believe i desperately needed this on tuesday and, after several hours spent trying unsuccessfully to get magisk manager for recovery working, ended up reflashing and starting again from scratch! crazy timing. anyway thanks for this, will definitely come in handy as i am too stupid to learn from my mistakes, ever.
c_tho said:
oh my gosh would you believe i desperately needed this on tuesday and, after several hours spent trying unsuccessfully to get magisk manager for recovery working, ended up reflashing and starting again from scratch! crazy timing. anyway thanks for this, will definitely come in handy as i am too stupid to learn from my mistakes, ever.
Click to expand...
Click to collapse
Relatable. I've had to hard wipe twice as I'm not used to this a/b stuff without TWRP lol. I've learnt my lesson though and finally granted shell root access, so assuming the phone boots past the bootloader I can use adb to fix up my magisk install.
Sent from my Google Pixel 3a XL using XDA Labs
Thank you! I've been running the stock kernel for the past several days because of a borked Magisk module. I couldn't fix the problem through TWRP since I'm on Android 10. This boot image allowed me to get back root without wiping. So thanks again!
Do you mind explaining how you made the image? I saw on the Magisk website that such a thing was possible but was unable to actually find details on how to create a core only image.
benji said:
Thank you! I've been running the stock kernel for the past several days because of a borked Magisk module. I couldn't fix the problem through TWRP since I'm on Android 10. This boot image allowed me to get back root without wiping. So thanks again!
Do you mind explaining how you made the image? I saw on the Magisk website that such a thing was possible but was unable to actually find details on how to create a core only image.
Click to expand...
Click to collapse
You have to build your own copy of magisk from GitHub.
Clone magisk
Go to native/jni/core folder and edit the boot stages.cpp file in notepad++ like this:
Approx line 667
If (access(DISABLEFILE, F_ok) ==0)
Change == to !=
Now build magisk as per instructions on GitHub
One you have built it and there were no errors go to native/out/armeb-v7a folder and get a copy of the magiskini64 file.
Unpack a copy of your magisk_patched.img.
In the ramdisk folder replace the init file with the .magiskini64 file (rename to init)
Repack your magisk_patched.img
The results are a patched IMG that will boot core only mode.
I definitely need to make sure I have this handy. A few questions, if you don't mind.
1. I would assume one should make a new version everytime they update to the latest security patch, correct? For example, I should not use a patched boot.ing from the December patch if I'm on the January, patch, correct?
2. Do your instructions assume that someone already put a .disable_magisk file in /cache, or does the boot.img itself do that job?
Bramton1 said:
I definitely need to make sure I have this handy. A few questions, if you don't mind.
1. I would assume one should make a new version everytime they update to the latest security patch, correct? For example, I should not use a patched boot.ing from the December patch if I'm on the January, patch, correct?
2. Do your instructions assume that someone already put a .disable_magisk file in /cache, or does the boot.img itself do that job?
Click to expand...
Click to collapse
To update boot would be best but you are just booting the image, not flashing. The old method required building a modded version of Magisk. The new method you just unpack the magisk_patched.img and drop in the overlay folder.
The boot image installs the .disable_magisk file for you.
March boot fix images uploaded.
Thank god for this one. I almost did a fullwipe because I couldn't get Magisk to work after flashing the March factory image in order to update. Turns out I forgot to remove your center clock/battery icon gone module. I didn't expect it to be the culprit, but it seems it was. Regardless, I'm back to working root after days of trying to find a fix
Is it possible to fastboot boot (not flash) the modified boot image for disabling modules and then install Magisk via Magisk Manager?
cucumbersmell said:
Is it possible to fastboot boot (not flash) the modified boot image for disabling modules and then install Magisk via Magisk Manager?
Click to expand...
Click to collapse
You should be able to boot with the modified image, but you don't "install" Magisk then - Magisk is already installed, just you booted with all the modules disabled
Just open Magisk Manager, go to Modules and mark to remove the module(s) causing bootloop.
Pay also attention to remove
.disable-magisk file from /cache
as described in OP post #1
Then reboot with your proper Magisk patched image (no more Core Only) and if you have removed the module in the previous step, this time you should be booted to Magisk with no bootloop and with your other modules re-enabled again
zgfg said:
You should be able to boot with the modified image, but you don't "install" Magisk then - Magisk is already installed, just you booted with all the modules disabled
Just open Magisk Manager, go to Modules and mark to remove the module(s) causing bootloop.
Pay also attention to remove
.disable-magisk file from /cache
as described in OP post #1
Then reboot with your proper Magisk patched image (no more Core Only) and if you have removed the module in the previous step, this time you should be booted to Magisk with no bootloop and with your other modules re-enabled again
Click to expand...
Click to collapse
I used Tulsadiver's core-only boot.img for the OP7T to root the phone by fastboot booting it and then using Magisk Manager to install to the active and inactive slots. Was hoping the boot.img for the 3a would work similarly. Was nice and simple and saved the time of having to download and patch the boot.img.
cucumbersmell said:
I used Tulsadiver's core-only boot.img for the OP7T to root the phone by fastboot booting it and then using Magisk Manager to install to the active and inactive slots. Was hoping the boot.img for the 3a would work similarly. Was nice and simple and saved the time of having to download and patch the boot.img.
Click to expand...
Click to collapse
It is based off of a magisk_patched.img so you might be able to use it like that. You would need to remove the .disable_magisk file from the cache folder though. This is a little different than the one I helped out with on the 7T forum.
cucumbersmell said:
I used Tulsadiver's core-only boot.img for the OP7T to root the phone by fastboot booting it and then using Magisk Manager to install to the active and inactive slots. Was hoping the boot.img for the 3a would work similarly. Was nice and simple and saved the time of having to download and patch the boot.img.
Click to expand...
Click to collapse
Edit: Sorry, seems I just missed the thread ?
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!
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
aktap said:
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
Click to expand...
Click to collapse
You said boot the magisk patched. Do you flash it?
You boot magiskpatched to make sure it works
Then once confirmed you flash magiskpatched
You make no mention that you flash the magiskpatched (unless I'm blind)?
c_86 said:
You said boot the magisk patched. Do you flash it?
You boot magiskpatched to make sure it works
Then once confirmed you flash magiskpatched
You make no mention that you flash the magiskpatched (unless I'm blind)?
Click to expand...
Click to collapse
I use this method:
"Rooting using fastboot commands
Method 1
Booting the patched image first
1. Obtain a patched boot img for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
You should now remain rooted."
So I probably didn't flash ...
aktap said:
I use this method:
"Rooting using fastboot commands
Method 1
Booting the patched image first
1. Obtain a patched boot img for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
You should now remain rooted."
So I probably didn't flash ...
Click to expand...
Click to collapse
After which point should i do it?
I wouldn't do it that way...
When you boot magisk patched image. And get to system to confirm you boot fine
Reboot back into bootloader and
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Fastboot reboot
That will permanently install the boot image.
Don't bother with the direct install on magisk app
c_86 said:
I wouldn't do it that way...
When you boot magisk patched image. And get to system to confirm you boot fine
Reboot back into bootloader and
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Fastboot reboot
That will permanently install the boot image.
Don't bother with the direct install on magisk app
Click to expand...
Click to collapse
Okay i'll try
Thank you for your help
aktap said:
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
Click to expand...
Click to collapse
If you are using lucky patcher, this is the cause. The symptoms you describe are the same. This app became harmful for 8 pro in a11. Causing apps to crash, detachment from gms services, and eventually bootloop. You lose root because of the factory reset. That is expected. Please confirm if this is the cause. I experienced this myself in a test environment.
elmarian756 said:
If you are using lucky patcher, this is the cause. The symptoms you describe are the same. This app became harmful for 8 pro in a11. Causing apps to crash, detachment from gms services, and eventually bootloop. You lose root because of the factory reset. That is expected. Please confirm if this is the cause. I experienced this myself in a test environment.
Click to expand...
Click to collapse
Yes, I use Lucky Patcher. So you're saying that if I don't install the LP, the problem won't occur? And some app that replaces LP?
aktap said:
Yes, I use Lucky Patcher. So you're saying that if I don't install the LP, the problem won't occur? And some app that replaces LP?
Click to expand...
Click to collapse
A fix can't be discussed for that application.
Yes it is the reason you have a fault.. Get rid of it
dladz said:
A fix can't be discussed for that application.
Yes it is the reason you have a fault.. Get rid of it
Click to expand...
Click to collapse
I rooted my phone again, without LP the system is stable. Thank You for Your help!
Good good.
Tbh there is no reason to use that app. And now it causes a lot of crap anyway, best to avoid it
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..