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,,
Related
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
https://forum.xda-developers.com/on...-to-uninstall-magisk-module-t3940369#poststop
Just had the same issue an hour ago. Do this then re-root your phone again. Easy. Then re-install magisk modules.
spart0n said:
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
Click to expand...
Click to collapse
Had the same issue.
Same here. I just reflashed TWRP (flash boot command), flashed the TWRP installer zip, rebooted recovery and then flashed Magisk. That solved it.
By the way, theres a new TWRP out for the 7 Pro.
I got the same problem but my internal storage is encrypted (it shows 0kb). TWRP is not asking for PIN to unencrypt the partition. What can I do now?
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
dude9946 said:
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
Click to expand...
Click to collapse
Your best bet is to use the oxygen updater app, download 9.5.9 and then copy it to a PC then use boot.img extract thingy and then use magisk to patch it and then use fastboot to to root it
Dears,
I have a OnePlus 6 unlocked and rooted with magisk and TRWP.
Currently I'm running stock firmware: oxygenos 10.3.
I got a message from system to update to 10.3.1.
Last time (when I have to update to 10.3) I tried to update in every way but without success and at the end I had to format everything and I lost my data.
So here is my question: which is the correct procedure to update software?
Thanks!
Look in TWRP and Root for OnePlus 6 on Oxygen OS 10 Stable/Beta thread
So you need to download latest Oxygen zip which is 042 buil if I'm not wrong...put it on your phone if you already didn't done that...then reboot to TWRP...and here starts the procedure....I HIGHLY RECCOMEND TO DO A WIPE WITHOUT FORMATTING INTERNAL STORAGE ONLY DATA...FOR AVOIDING ISSUES...but you can go without it...so here we start
Boot into twrp
Flash oxygen os zip(latest)
Flash twrp
Reboot to twrp(if it says no os installed just ignore it and swipe reboot anyway)
Flash magisk
and your done...thats it...nothing could go wrong.... I'm always doing it this way....
ilpratti said:
Dears,
I have a OnePlus 6 unlocked and rooted with magisk and TRWP.
Currently I'm running stock firmware: oxygenos 10.3.
I got a message from system to update to 10.3.1.
Last time (when I have to update to 10.3) I tried to update in every way but without success and at the end I had to format everything and I lost my data.
So here is my question: which is the correct procedure to update software?
Thanks!
Click to expand...
Click to collapse
For me, the phone downloaded the whole package instead of just the little OTA. I let it install it, bit did not let it restart it. Then I went to magisk modules and installed "twrp-keep". Then in magisk manager I had it install magisk on the other slot. Then I restarted the phone. Everything worked great.
tabletalker7 said:
For me, the phone downloaded the whole package instead of just the little OTA. I let it install it, bit did not let it restart it. Then I went to magisk modules and installed "twrp-keep". Then in magisk manager I had it install magisk on the other slot. Then I restarted the phone. Everything worked great.
Click to expand...
Click to collapse
Try this method... im also done my update like this!
my way of doing it
Here's what i did and it didn't took me long at all i'm a newbie
I unroot my phone via magisk
install os 10.3.1 then flash twrp and root my phone again.
Dears,
Thanks for the replay.
I forgot that I was without TWRP.
What I did, and it worked, is:
- uninstall magisk manager by magisk
- install full update
- reboot
- flash by fastboot boot.img patched by magisk.
Thanks again
Hey guys
I need your help to be happy having my phone rooted....
After update to android 11 I try to install TWRP 3.5.2 but the phone stuck on fastboot screen and TWRP not opens. So, I found an another way to root the device patching boot.img trough magisk, even it not pass on SafetyNet validation.
The root works but after reboot the phone lose it.
Some one have a solution for root on android 11?
Thanks for your help.
At the moment the TWRP in android 11 is giving problems when the mobile is encrypted does not work, you would have to make a backup and decrypt the phone to be able to use it. Any questions let me know
You need to decrypt your data and stay decrypted to get twrp working in A11.
And for the magisk part (assuming you don't wanna use twrp and stay encrypted), after booting using the patched boot image, open Magisk app, then select the Install option, then Direct Install. And that's it. You won't lose root access after reboot.
dewri21 said:
You need to decrypt your data and stay decrypted to get twrp working in A11.
And for the magisk part (assuming you don't wanna use twrp and stay encrypted), after booting using the patched boot image, open Magisk app, then select the Install option, then Direct Install. And that's it. You won't lose root access after reboot.
Click to expand...
Click to collapse
Are you referring to the patched boot.img you make yourself using Magisk? I've tried that myself, but the phone keeps being stuck at the boot logo (not a boot loop). I'm always forced to flash the original boot.img file to make the phone operational again.
Skyrider said:
Are you referring to the patched boot.img you make yourself using Magisk? I've tried that myself, but the phone keeps being stuck at the boot logo (not a boot loop). I'm always forced to flash the original boot.img file to make the phone operational again.
Click to expand...
Click to collapse
You patched the boot.img yourself? I mean did you get the proper image using payload dumper? It should have booted. Check it again and try. If that doesn't help you still, decryption is the way to go. I have been decrypted since a long time, with a working twrp.
dewri21 said:
You patched the boot.img yourself? I mean did you get the proper image using payload dumper? It should have booted. Check it again and try. If that doesn't help you still, decryption is the way to go. I have been decrypted since a long time, with a working twrp.
Click to expand...
Click to collapse
I thought TWRP wasn't/isn't fully supported on Android 11?
And yes, I used the proper proper image as I grabbed the entire package using Oxygen Updater, while using the patched version to update the OS. And if I didn't get the proper image, I would assume reverting back to the original boot.img (from the full package) wouldn't have worked.
Skyrider said:
I thought TWRP wasn't/isn't fully supported on Android 11?
And yes, I used the proper proper image as I grabbed the entire package using Oxygen Updater, while using the patched version to update the OS. And if I didn't get the proper image, I would assume reverting back to the original boot.img (from the full package) wouldn't have worked.
Click to expand...
Click to collapse
I found working patched boot at OnePlus forum, I guess it was patched with canary version of magisk. Maybe you can try.
Skyrider said:
I thought TWRP wasn't/isn't fully supported on Android 11?
Click to expand...
Click to collapse
It is, if and only if you're decrypted. TWRP doesn't support encryption on A11.
Hey I am on KB2003.F13 and wanted to upgrade to F15.
When I start the process by uninstalling Magisk before I download the update and then would re-install Magisk to the inactive slot to retain root I get the errror message "Stock image does not exist".
I'm imagining this is because I did not patch the stock image myself. After MSM-ing back to OOS11 and updating to OOS13 I rooted by flashing a F13 image that I found on these forums that was already patched.
What can I do? Thanks in advance
kevinco1 said:
Hey I am on KB2003.F13 and wanted to upgrade to F15.
When I start the process by uninstalling Magisk before I download the update and then would re-install Magisk to the inactive slot to retain root I get the errror message "Stock image does not exist".
I'm imagining this is because I did not patch the stock image myself. After MSM-ing back to OOS11 and updating to OOS13 I rooted by flashing a F13 image that I found on these forums that was already patched.
What can I do? Thanks in advance
Click to expand...
Click to collapse
I never add problems updating my 8T while it was rooted. I never restored the stock image before installing the update, I would just install to inactive slot before rebooting when the update finished.
Anyway, if you want to be super safe you could extract the stock boot.img from the full update package of your current version and flash it (it would be the same as restoring the stock image with Magisk). Btw I suggest you never flash images patched by others to avoid this exact problem. You can still use images from others if you want, just boot them (fastboot boot boot.img) instead of flashing them and then do a direct install with Magisk.
TheNewHEROBRINE said:
I never add problems updating my 8T while it was rooted. I never restored the stock image before installing the update, I would just install to inactive slot before rebooting when the update finished.
Anyway, if you want to be super safe you could extract the stock boot.img from the full update package of your current version and flash it (it would be the same as restoring the stock image with Magisk). Btw I suggest you never flash images patched by others to avoid this exact problem. You can still use images from others if you want, just boot them (fastboot boot boot.img) instead of flashing them and then do a direct install with Magisk.
Click to expand...
Click to collapse
So if I booted the F13 image I previously used and then did a direct install, Magisk would then make that backup IMG file and then I can proceed with the update to F15?
Or can I not boot the F13 image and do a direct install if I've already flashed it?
kevinco1 said:
So if I booted the F13 image I previously used and then did a direct install, Magisk would then make that backup IMG file and then I can proceed with the update to F15?
Or can I not boot the F13 image and do a direct install if I've already flashed it?
Click to expand...
Click to collapse
I think that Magisk backups the currently flashed boot image, so if you just boot the stock image it would backup the patched image.
kevinco1 said:
Hey I am on KB2003.F13 and wanted to upgrade to F15.
Click to expand...
Click to collapse
Update straightforward to F.62
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?