Hi Everyone, there seems to be a lot of bits and pieces in regards to updating OOS 12 and Root so I thought I put together this guide on the way I do it while retaining Root. Unless something changes, this method should work for all future OOS 12 OTA updates.
Please read through all of the steps below before attempting. I will take no responsibility if something goes wrong, this works for me on my OnePlus 9 LE2115 and it should work for other OnePlus 9/Pro models.
1. Install Oxygen Updater app from the Play Store
2. Download the Full OTA.
3. Download and install the OP Local Update app ( apk).
4. Use the OP Local Update app to flash the Full OTA (you will lose root and custom recovery).
Optional - Retaining Root
DO NOT REBOOT if you want to keep Root
5. Open Magisk and in the Magisk section, tap 'Install'.
6. Select ' Install to Inactive Slot (After OTA)'.
7. Tap ' LET'S GO', let it run and then reboot.
After the system boots back up, check to make sure you have retained Root. You will not lose any data doing it this way.
What do you do if you've rebooted, are on the new OS but don't have root? When I go back to Magisk it's asking for an IMG file... I saved the last used kernel before upgrading (11.2.10.10)
I tried installing that app, which looks like its an udpate for a system app (system updater) which is prob why it fails.
I was previously under the impression that this app was to replace the missing system updater in OOS12.
Nick James said:
What do you do if you've rebooted, are on the new OS but don't have root? When I go back to Magisk it's asking for an IMG file... I saved the last used kernel before upgrading (11.2.10.10)
Click to expand...
Click to collapse
This guide is for updating OOS 12, i have not tested it from OOS 11 to 12. It looks like you just need to flash the patched boot.img again.
Also, just to make sure, you didn't reboot the phone after flashing the Full OTA? After flashing Full OTA, you need to go straight into Magisk as per instruction.
gorilla p said:
I tried installing that app, which looks like its an udpate for a system app (system updater) which is prob why it fails.
I was previously under the impression that this app was to replace the missing system updater in OOS12.
Click to expand...
Click to collapse
Yeah, it does not replace any app, it installs a new one. The Local Updater app is only for OOS 12. In OOS 11, it's integrated into system Updater but for some reason in OOS 12, OP removed it and created a seperate app for Local OTA flashing.
Z-Blade said:
Yeah, it does not replace any app, it installs a new one. The Local Updater app is only for OOS 12. In OOS 11, it's integrated into system Updater but for some reason in OOS 12, OP removed it and created a seperate app for Local OTA flashing.
Click to expand...
Click to collapse
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.
Nick James said:
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.
Click to expand...
Click to collapse
Ah, right. From the other thread. Good to hear it's all sorted out.
If you are looking for the boot.img for a OP9 (not pro) LE2115_11_C.47... here you go:
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
This is valuable if you get stuck in a position like I did on C.47 without root. Patch this file with Magisk and follow the instructions as you normally would when flashing for root:
Installation
The Magic Mask for Android
topjohnwu.github.io
Nick James said:
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.
Click to expand...
Click to collapse
So, how did you get from e.13 to c.47 with root?
1. Download c.47
2. Install it via updater - no resart
3. install the patched_boot.img in inactiv slot
4. restart
Correct?
AxelM said:
So, how did you get from e.13 to c.47 with root?
1. Download c.47
2. Install it via updater - no resart
3. install the patched_boot.img in inactiv slot
4. restart
Correct?
Click to expand...
Click to collapse
I uninstalled Magisk (restored images).
Rebooted (I shouldn't have done this)
Updated via OTA; rebooted.
Confirmed I was on the new version; indeed I was... completely new UI... did not lose any data or apps
Used the update app to redownload the OTA, copied it to my computer, used payload dumper to get the boot.img. Moved that back to my phone, patched with magisk and reflashed and voila.
I'm not sure on the exacts in terms of versions that I was on before but I did back up the kernel prior to all this (force of habit) and it was 11.2.10.10.
Thank you, i will try
1. I will just restore the normal boot.img
2. Update via OnePlus Update app from device
3. reboot
4. install the patched_boot.img in the inactiv slot
5. restart
Done!
So to be clear, we can now upgrade like we used to, by downloading full image From Oxygen Updater, using system update complete the upgrade, then go to magisk and install to inactive slot and reboot?
I tried this with the earlier 12 release and it went poor.
Luckily, I realized before trying this, is this only for 12 to 12 udpates and not 11 to 12? If the former, it may be best to clarify.
I am not sure. But like I understood you have to unroot before...
@Nick James am I right?
AxelM said:
I am not sure. But like I understood you have to unroot before...
@Nick James am I right?
Click to expand...
Click to collapse
I dont think so. It says if you wanna keep root, follow #5, 6, 7
AxelM said:
I am not sure. But like I understood you have to unroot before...
@Nick James am I right?
Click to expand...
Click to collapse
Honestly this OS sucks. I wouldn't waste your time. I'm going to factory reset tomorrow. It's that bad.
The steps I provided is only OOS 12 to OOS 12. I have not tried these steps from OOS 11 to OOS 12. My assumptions is it should still work since you are flashing the Full OTA, it pretty much overrides everything including boot.img. This is why you shouldn't reboot after flashing the OTA if you want to keep root.
However, this is just an assumption, if someone who is currently on OOS 11 can test it out and report here, that would be great.
gorilla p said:
I dont think so. It says if you wanna keep root, follow #5, 6, 7
Click to expand...
Click to collapse
You are right for OS12 but not OS11. Therefore I assume you have to do my mentioned steps, but like @Z-Blade wrote, anyone has tested here yet...
Hello I tried it today. Like this:
1. I will just restore the normal boot.img
2. Update via OnePlus Update app from device
3. install the patched_boot.img in the inactiv slot
4. restart
Everything seems normal, but I am ony able to connect to the internet when in wlan...
I went from OOS 11 to 12... I wouldn't say the upgrade went smooth thus why I have to reinstall the OS to see if that clear things up. This OS is still really buggy from what I can see but it could be due to not clean flashing. Just beware is all I'm sayin'
So, my internet is back to live...after some reboots it works well
Related
I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here
The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.
without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???
please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?
flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks
flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb
Thanks.
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA
k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks
flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system
btw: method above work for me also while i upgrade from Android10 to Android11 ;-)
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.
rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"
Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!
I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,
I'm new to OnePlus again, had a Pixel as my last phone. Got the notice there's a new update for OOS13. I am rooted and, if possible, want to stay on stock ROM.
I checked the process and it seems the two ways to update are applying the full image or temporarily deinstalling Magisk, running the OTA, then reinstalling Magisk to other slot. Well, OxygenOS Updater and the OnePlus website show no full image for this latest update, so I tried the second method and that did not work at all, it went straight to the Qualcomm bugcheck screen on boot and then basically wouldn't start until I went back to fastboot and got back to Slot A.
So, am I missing something or is there just a lag before the full ROM gets posted? Or will OnePlus just never post it and I need to go to a third party ROM?
thx1200 said:
I'm new to OnePlus again, had a Pixel as my last phone. Got the notice there's a new update for OOS13. I am rooted and, if possible, want to stay on stock ROM.
I checked the process and it seems the two ways to update are applying the full image or temporarily deinstalling Magisk, running the OTA, then reinstalling Magisk to other slot. Well, OxygenOS Updater and the OnePlus website show no full image for this latest update, so I tried the second method and that did not work at all, it went straight to the Qualcomm bugcheck screen on boot and then basically wouldn't start until I went back to fastboot and got back to Slot A.
So, am I missing something or is there just a lag before the full ROM gets posted? Or will OnePlus just never post it and I need to go to a third party ROM?
Click to expand...
Click to collapse
Uninstall magisk restore images only. Don't reboot ,start ota let it install. Don't reboot. Go into magisk install and apply to ota . Boots into other slot. Qualcomm crash dump is probably because you left modules enabled. Disable and reboot before you start all of this. All your doing is supplying an apparent stock boot.img to allow ota to install. I just did process going to F-18 and all is well. Actually I msm back to A10 patch boot there. And carry it all the way to latest update. !! Pm me if you have any questions and gl.
mattie_49 said:
Uninstall magisk restore images only. Don't reboot ,start ota let it install. Don't reboot. Go into magisk install and apply to ota . Boots into other slot. Qualcomm crash dump is probably because you left modules enabled. Disable and reboot before you start all of this. All your doing is supplying an apparent stock boot.img to allow ota to install. I just did process going to F-18 and all is well. Actually I msm back to A10 patch boot there. And carry it all the way to latest update. !! Pm me if you have any questions and gl.
Click to expand...
Click to collapse
I did everything except disable modules. Do I disable modules first, then do "restore images?" Is there a reboot after disabling modules? [EDIT: nevermind, i see you did say to reboot after disabling modules]
How do I start over? Right now the other slot doesn't boot and in the OS the system update just says "reboot to apply update" as in it won't reinstall it. I've also tried flashing the boot image over with stock so I've sort of already messed up the inactive slot, probably.
thx1200 said:
I did everything except disable modules. Do I disable modules first, then do "restore images?" Is there a reboot after disabling modules? [EDIT: nevermind, i see you did say to reboot after disabling modules]
How do I start over? Right now the other slot doesn't boot and in the OS the system update just says "reboot to apply update" as in it won't reinstall it. I've also tried flashing the boot image over with stock so I've sort of already messed up the inactive slot, probably.
Click to expand...
Click to collapse
https://onepluscommunityserver.com/list/Unbrick_Tools/
If it was me I'd start fresh. Run msm tool will take you back to Android 10. 11.2.4.4 patch boot here and carry all the way through. Won't have modules to disable. In A10 you just use 23.1 magisk version . Patch boot.img. fastboot boot patched.img direct install then it backs up stock properly. You really need working msm tool handy anyway.
In order to update through A13/f18 you need magisk 25.2 stable to carry it through. Just start with 23.1 to patch . Then update magisk version.
I want to avoid wiping and starting over if possible. My Slot A boots fine, has root (I reflashed the Magisk modified boot image and it came right back), and everything is working on OOS13 F17. I just need to get the new update into Slot B which the updater seems to think is already applied.
Can I just redo the OTA or flash the full OOS13 F17 through OOS Updater?
thx1200 said:
I want to avoid wiping and starting over if possible. My Slot A boots fine, has root (I reflashed the Magisk modified boot image and it came right back), and everything is working on OOS13 F17. I just need to get the new update into Slot B which the updater seems to think is already applied.
Can I just redo the OTA or flash the full OOS13 F17 through OOS Updater?
Click to expand...
Click to collapse
Have you tried updating to build through system updates ? Instead of third party app.
mattie_49 said:
Have you tried updating to build through system updates ? Instead of third party app.
Click to expand...
Click to collapse
I'm sorry, I don't understand what you are asking. I have only used system updates so far. About -> Update. Currently that is saying it's installed and to reboot.
OK, I dug myself out of the hole. Here is how I fixed my situation and successfully updated to F.18 without any data loss.
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!
thx1200 said:
OK, I dug myself out of the hole. Here is how I fixed my situation and successfully updated to F.18 without any data loss.
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!
Click to expand...
Click to collapse
Very nice. Glad you got it. Very frustrating these devices and their A& B partitions.
thx1200 said:
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!
Click to expand...
Click to collapse
way to complicated, is there an easy way?
mattie_49 said:
In order to update through A13/f18 you need magisk 25.2 stable to carry it through. Just start with 23.1 to patch . Then update magisk version.
Click to expand...
Click to collapse
does you mean downgrade magisk to 23 will help?
Nobody ever was able to install F.18 on a rooted phone?
Suncatcher16 said:
Nobody ever was able to install F.18 on a rooted phone?
Click to expand...
Click to collapse
Its not hard as I have done it. Just use latest canary magisk.
Suncatcher16 said:
Nobody ever was able to install F.18 on a rooted phone?
Click to expand...
Click to collapse
I transfered root from f17 to f18 with 25.2 not canary. It works sir..you uninstall magisk only restore images. Start internal ota . Use install feature on magisk to install to inactive. Real simple.
This is how I have been doing it, not the quickest though.
1. Download OOS update from Oxygen Updater.
2. Disable all Magisk modules.
3. Flash stock boot.img
4. Flash OOS update via Local OOS System Update app.
5. Reboot
6. Extract boot.img using MSM readback
7. Patch boot.img through Magisk
8. Flash patched boot.img
9. Turn all Magisk modules back on.
When I was on OOS 12, I did try using the restore image option in Magisk but it never worked for me, this is why I had to do it this way. However, I have not tried on OOS 13 so I will give this another crack on the next update. If it does work, its way easier.
Z-Blade said:
This is how I have been doing it, not the quickest though.
1. Download OOS update from Oxygen Updater.
2. Disable all Magisk modules.
3. Flash stock boot.img
4. Flash OOS update via Local OOS System Update app.
5. Reboot
6. Extract boot.img using MSM readback
7. Patch boot.img through Magisk
8. Flash patched boot.img
9. Turn all Magisk modules back on.
When I was on OOS 12, I did try using the restore image option in Magisk but it never worked for me, this is why I had to do it this way. However, I have not tried on OOS 13 so I will give this another crack on the next update. If it does work, its way easier.
Click to expand...
Click to collapse
That is because you did not let magisk make the backup in the first place. After you patch the img, you are supposed to fastboot boot patch img not flash.
MrSteelX said:
That is because you did not let magisk make the backup in the first place. After you patch the img, you are supposed to fastboot boot patch img not flash.
Click to expand...
Click to collapse
Ahhhh... I take it after you boot into the patched image, you go into Magisk and do a direct install?
Z-Blade said:
Ahhhh... I take it after you boot into the patched image, you go into Magisk and do a direct install?
Click to expand...
Click to collapse
Yes
mattie_49 said:
I transfered root from f17 to f18 with 25.2 not canary. It works sir..you uninstall magisk only restore images. Start internal ota . Use install feature on magisk to install to inactive. Real simple.
Click to expand...
Click to collapse
Did you do any additional steps after you restored images and saw "restoration done" message? I tried several times and installation fails anyway. I did all according to these steps
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
MrSteelX said:
Just use latest canary magisk.
Click to expand...
Click to collapse
Where did you download it? Could you drop the link please?
I cant do normal OTA updates, nor can I install them with the built in installer in settings (that I gained with conversion). Im not exactly sure why and trying to figure this out. Were you able to update as normal to A13?
Its possible I broke something (cant think of what), so Im restoring my after-root twrp "base" backup to see if it can OTA.
Figured Id ask in the meantime...
TimmyP said:
I cant do normal OTA updates, nor can I install them with the built in installer in settings (that I gained with conversion). Im not exactly sure why and trying to figure this out. Were you able to update as normal to A13?
Its possible I broke something (cant think of what), so Im restoring my after-root twrp "base" backup to see if it can OTA.
Figured Id ask in the meantime...
Click to expand...
Click to collapse
You have to uninstall magisk/restore images. Then start ota. Then before you reboot go into magisk again and install to opposite slot and reboot . After ota has installed. Stock boot image is the only way it works. It's will fail upon checksum of partitions by google
I figured as I just went back to my base savior A11 rom fresh root, and still nothing. Thank you!
Uninstall magisk it automatically restores boot images right?
*Actually do I need stock boot? I have twrp. Where do I get stock boot image?
Im screwed. Its unable to restore my old image from usb, so Im bricked now. No idea what to do.
mattie_49 said:
You have to uninstall magisk/restore images. Then start ota. Then before you reboot go into magisk again and install to opposite slot and reboot . After ota has installed. Stock boot image is the only way it works. It's will fail upon checksum of partitions by google
Click to expand...
Click to collapse
Do you know how I can get back to stock boot?
NM found it. So to be sure, when i want to move from A11 I need to uninstall Magisk, boot to fastboot, then fastboot flash stock boot.img?
Here
^But I have twrp, so wont restoring just bring me to unlocked bootloader unrooted with twrp? (*still not stock?)
*Sorry for the questions. It just seems TWRP has problems restoring backup completely (or I missed something, I backed up everything in TWRP maybe I dont need to do that?).
Im trying to avoid what happened a couple nights ago, because I lost confidence in TWRP on this phone. Usually, its just something ****s up? Well restore your backup, because you just made one. That didn't work completely (it didn't restore /data), and I had to set up a ton I dont want to do again, unless Im on custom A13 rom. Got savegames!
Thanks for all help.
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Couldnt Magisk patch boot image from app? Instead of extracting it? Thats how I did it on 11.
I also dont know how to use msm tool to get to 11, or even where to get files. *I think this is it? General - OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool | XDA Forums
*Thats exactly whats happening to me too. update failed. So I guess this would be a sure fix.
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
Wait. How did you unlock bootloader (after MSM put your phone back to lock BL I assume)? Is the option later available on Tmobile roms? Did you need a token?
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
jmadiaga said:
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
Click to expand...
Click to collapse
Doesn't having twrp boot image installed mean that magisk restored twrp image to when before magisk patches it (so it's not actually stock)? Doesn't it just restore a non rooted image with twrp on it?
jmadiaga said:
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
Click to expand...
Click to collapse
This fails if you have TWRP.
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
Are you tmobile? How did you unlock BL on 13?