Just tested it this morning as all is working well. Now we are officially in the supported device (along side with Pixel 2 and 2XL). Thus means that we can now patch boot.img on the fly using Magisk Manager when there's an OTA update.
Steps would be the same as Pixel 2 series as our phones apparently using the same partition and logic method as the Pixel 2. Mentioned here : https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I would suggest anyone who uses magisk snapshot build to upgrade to this latest version for proper magisk patching without TWRP. For minimal issue :
1. install magisk manager 5.4.1 (your current app will prompt for update usually, if not sideload from the official magisk beta xda forum.)
2. Uninstall magisk using the manager app, this will restore your boot.img backup. DO NOT REBOOT, just tap close.
3. Tap update/install magisk. It will then ask which method of installation. Choose install right now (recommend).
4. Reboot and wait, latest magisk should be installed after reboot.
Note : if the backup boot img is not stock, not available or is already patched. You'll need to boot to fastboot, flash your current build boot img. And then boot twrp to flash the magisk 14.5 flashable zip.
Full details here : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
joemossjr said:
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
Click to expand...
Click to collapse
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
i.Design said:
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
This didn't work. I was able to at least see my storage now and installed OTA via TWRP > TWRP installer > Magisk to update Slot B now I'm having the same issue in both slots.
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
I have downloaded the 11 update via OxygenUpdater using VPN (Location is set to France)
Since i diden't get the update on my real location.
Rebooted to TWRP->Flashed 11 update->Flashed TWRP->Rebooted to TWRP>Flashed Magisk>Flashed Kernel>Rebooted to System.
Everything seems to be working.
Try this simple and straight forward method,
Download the full zip 9.5.11, not the update zip but full zip,
Transfer to phone storage,
wipe only dalvik cache and data, DO NOT WIPE SYSTEM OR VENDOR, OR INTERNAL STORAGE,
Flash the oos zip,
Flash twrp, Reboot recovery,
Flash oos zip file again followed by twrp,
Reboot recovery,
Flash magisk 19.3,
Now Reboot system,
Do not click on any slots in twrp let the system select the appropriate slot, system will take some time to boot also will Reboot itself, but will boot eventually,
hope this helps, cheers.
How this helps, worked for me, I don't have T-Mobile version
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
OP7PRO, stock ROM, stock kernel
This has been ABSOLUTELY working for me and how i was used doing it back in the days..
*After switching off all modules in Magisk and do a system reboot to apply this..
(Do I have to mention it's probably best, when updating to disable any password/fingerprint protection when rebooting AFTER FLASHING OTA, TWRP and Magisk in recovery?)
*I didn't use local update setting.
*What's on in developer options?
-OEM Unlock allowed
-Advanced reboot
-USB Debugging
*Don't know if having these developer settings otherwise would interfere, I just try to write it down as specific as of how i did this.
*Also: I didn't even bother looking at A/B partitioning and where to install what, please correct me if i could be wrong, but using this method worked for me and also when installing TWRP zip in recovery, the log showed A/B sloth solution success when installing.
*Not using substratum themes etc., but I want to say it's probably best to go as clean as you can anyway, since you can always go back being beautiful afterwards I guess?
So try remember where you left off being a makeup loving customiser and momentary revert being as clean as possible.. at least for maybe 20 minutes okay?
How I did it:
-Download the OTA update zip on your phone (full update file zip just shy of 2 Gb) using oxygen updater app in Google playstore.
(Don't install the systemsoftware zip from the oxygen updater once downloaded), you're going to install the systemsoftware.zip in TWRP recovery as opposed to update via Magisk to install the new systemsoftware).
-Download TWRP (INSTALLER!!) have this ZIP on phone (Find it by reading some posts about TWRP Installer zip or use link below)
*I used: twrp-installer-3.3.1-4-guacamole.zip
https://dl.twrp.me/guacamole/ (for TWRP zip)
-Download Magisk zip
*I used: Magisk-v19.3.zip
(So far 3 zip files, have them somewhere pretty obvious on your phone)
-Boot into recovery (I did this by using this option in Magisk manager)
Then:
-Flash the update OTA ROM.zip (just shy of 2Gb)
*DON'T REBOOT*!!!!
-Go back in TWRP recovery menu, Flash TWRP Installer zip
-Still in TWRP recovery menu go back, Reboot to recovery
-Back in TWRP, flash Magisk zip
-Clear Dalvik cache (not sure if this is actually still needed)
-Reboot system normally, enable Magisk modules you want, reboot system...
Updated to 9.5.10 works
Updated to 9.5.11 works
Updated to 10.0.0 works
I can't find the full zip for 9511 anywhere
joemossjr said:
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
Click to expand...
Click to collapse
I ended up having to reformat to deal with the encryption issue. After reformatting I was able to boot to slot b and am at .11 now!
I'm really hoping this ordeal fixed whatever the problem was so that future OTA's aren't this much of a headache. I'll keep the tips in mind. I'm just glad to have a working device at .11 with root even if I have to re-install all of my apps etc.
virtyx said:
I can't find the full zip for 9511 anywhere
Click to expand...
Click to collapse
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
smariob said:
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
Click to expand...
Click to collapse
just came up now
what i normally do is flash full zip
reboot
then reboot fastboot and boot twrp, then flash twrp then magisk.
i like the OS boot first time without twrp or magisk, just habit i guess
everything working fine, nightscape also
EDIT:
i think SWAP has been turned off in 9.5.11
it no longer displays in ElementalX app (with stock kernel)
What did I do wrong?
Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?
I don't know why people have such difficulty?
1. Get the full zip via Oxygen Updater or some other method.
2. Do a local install vis the settings. DO NOT REBOOT.
3. Install Magisk via the "Install after OTA" from Magisk Manager.
4. Reboot
5. You will now have the slot rooted that you updated.
6. Run the local install again. This will install to the other slot. It will fail the first attempt. Do it again.
7. Install Magisk via the OTA option and reboot.
You have now updated both slots and rooted them.
If you would like TWRP or custom kernels, follow those instructions.
If you install TWRP, you MUST install Magisk in the same slot or you will get a boot loop for that slot.
That is the reason why I keep both slots at the same OS level and rooted with TWRP installed.
What country guys you are from that you are getting update? Im in USA and still got nothing.
netgar said:
What country guys you are from that you are getting update? Im in USA and still got nothing.
Click to expand...
Click to collapse
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Krsmqn said:
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Click to expand...
Click to collapse
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
netgar said:
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
Click to expand...
Click to collapse
Yeah, meant magisk modules, sorry. But looks like you got it anyway. ?
All update methods to 11 failed.
* Warranty is void
* I'm not responsible for any damage to your phone in mistaking anything specified here
* This guide requires intermediate knowledge
I'm posting this guide because I haven't found any special thread about it, and had to search multiple threads and websites to get a conclusion in how to root Magisk only (without flashing TWRP or any other custom recovery). Focused in not decrypting the phone, or modify any system partition for a full OTA compatibility.
Requirements:
* ADB/Fastboot & Motorola USB drivers installed - (PC)
* Unlocked bootloader - (Phone)
* Stock rom - (Phone)
* Magisk Manager (latest stable version installed on your phone)
* TWRP (compatible to the Moto G6 Play model) - please refer to this thread for more details. ***(Of course, you won't flash it!)
*** PLEASE! REFER TO THE UPDATES BELOW!!! ***
Tutorial:
1. Reboot to bootloader
2. Boot into downloaded TWRP using Fastboot code:
Code:
fastboot boot twrp_downloaded.img
(on TWRP ignore any password by canceling)
3. Backup stock boot image using:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
4. Reboot system using ADB code:
Code:
adb reboot system
5. After rebooted, copy backed up stockboot.img to the phone internal memory
6. Install and open Magisk Manager, click [Instal] > [Install] > [Select and Patch a File] and select stockboot.img on internal memory.
7. After boot image patched, copy magisk_patched.img from phone Download folder to PC
8. Reboot to bootloader and flash magisk_patched.img to phone using Fastboot code:
Code:
fastboot flash boot magisk_patched.img
9. After done, reboot system using fastboot code:
Code:
fastboot reboot
10. All done! Open Magisk Manager and check root! For future OTA updates already rooted with Magisk, I recommend this post: https:// www. the custom droid .com/install-ota-update-rooted-android-device-guide/ - (remove spaces )
[UPDATE 1]
I've noticed that Moto G6 simply forces reboot system before update the device, if we go to restore images in Magisk to try it out tutorial post from 10., it'll simply be removed after that.
Even doing so and going ahead to update the device losing Magisk, and still have to back up once more the new updated boot image and patch it on Magisk following my guide above, I got a bootloop patching the newest OTA with Magisk 20.0 (latest).
After almost losing indefinitely root access, I got it done, downgrading Magisk to 19.3.
For doing so, download Magisk 19.3 zip file from GitHub repository and copy it to the SD Card, boot up into TWRP using fastboot (without flashing) then proceed as read-only, after that, install Magisk 19.3 zip file to patch the OTA updated boot image, then it's done. Root it's working properly without updating Magisk.
I don't know exactly why the latest Magisk it is breaking the OTA updated boot image... Whatever, it's a good approach to get root access back after the recent OTA!
I still need to check if this workaround will be working on new OTA's. That's it.
[UPDATE 2]
After recent update - January 2020, my rooting workaround supporting OTA is working properly as followed solution on UPDATE 1, above.
I didn't test using latest Magisk 20.3 apk due the bootloop when patching boot image in Magisk 20. Don't know if that bug has been fixed...
Updating Magisk after successfully rooted using solution above will not result in a bootloop, but I do recommend downgrade Magisk when new OTA is released.
Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!
gabardal said:
Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!
Click to expand...
Click to collapse
First, if you have the actual boot backup, you'll need to flash it to fix bootloop.
Remember to boot into TWRP (without flashing) to flash it.
* Follow the samples above for the codes if necessary.
After fixing bootloop all you'll need to do is download the Magisk-v19.3.zip from “Magisk GitHub releases” and place it on the external sd card.
Then boot into TWRP (always without flashing) and flash the zip file using TWRP. (Remember to flash to boot image).
It'll simply patch your boot, after that, reboot, if successfully booted go check Magisk.
Hi, I have a simple question, but I couldn't find the answer anywhere - how do I update the modified OxygenOS? I have, for example, TWRP, Magisk, Renovate ICE, what should I do about it when the update comes out? Do I need to reinstall all these things after flashing the system?
You can flash the upgrade and install your mods again.
ThaRealSaad said:
You can flash the upgrade and install your mods again.
Click to expand...
Click to collapse
I don't think this is accurate, according to the TWRP thread. I believe you're supposed to remove all the magisk modules and then flash.
https://forum.xda-developers.com/on...covery-unofficial-twrp-recovery-t3931322/amp/
HOW TO UPDATE a ROM and KEEP TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk;
- Reboot.
If you want you can also update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- Menu/modules/+ button/select the twrp installer.zip and flash it;
- Always in Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Click to expand...
Click to collapse
Check what TWRP version you have.
Also, search for the magisk module about the A/B partition flash. I learned about that a little too late.
Just disable all magisk mods and reboot before update.
And do your research about support before reanabling magisk mods