Related
This is for if you have Magisk 18.1 installed with manager version 7.1.1. Upgrading to manager 7.1.2 and then directly installing 19.1 caused my I3223 to go into a boot loop.
Image patching seems to have changed as well. With manager 7.1.1 we were able to directly patch the boot_X_FLASH_ALL-*.sin file. I had to extract boot.000 from the sin file before the new manager would patch it. Even so, the result is still a boot loop.
Reflashing older patched boot images did not restore root. In short, hold off on upgrading Magisk. If you have a solution please share. Thanks.
I was able to flash the older (v18.1) magisk patched boot image using fastboot. I will attach the image here if you need too. I had to split the RAR file into 3 parts due to limitation of XDA of RAR files to be 8MB.
Root is working fine, I was able to grant access to Titanium Backup. But seriously that was messed up. If that happened to my Shield TV and I lost all of my games I will be furious. Luckily, I tried that on the Shield TV before knowing it will mess up my Xperia 10 plus phone. What is more messed up is there is no way from Magisk Manager to keep using older APK or download older version of Magisk, I tried Custom URL in the settings to check the update from, but all I got was a spinning wheel while checking for updates.
Currently running Magisk Manager 7.1.2 and v18.1 , just ignoring the ZIP update.
Rule of thumb, if it aint broken, don't fix / update.
Thank you Rebel_X. I will try again tonight. I was hoping to retain userdata but that's probably what's giving me problems with the revert.
Has anyone tried 19.1 patched boot image on a fully reset phone? Do we know if that works?
Rebel_X said:
I was able to flash the older (v18.1) magisk patched boot image using fastboot. I will attach the image here if you need too. I had to split the RAR file into 3 parts due to limitation of XDA of RAR files to be 8MB.
Root is working fine, I was able to grant access to Titanium Backup. But seriously that was messed up. If that happened to my Shield TV and I lost all of my games I will be furious. Luckily, I tried that on the Shield TV before knowing it will mess up my Xperia 10 plus phone. What is more messed up is there is no way from Magisk Manager to keep using older APK or download older version of Magisk, I tried Custom URL in the settings to check the update from, but all I got was a spinning wheel while checking for updates.
Currently running Magisk Manager 7.1.2 and v18.1 , just ignoring the ZIP update.
Rule of thumb, if it aint broken, don't fix / update.
Click to expand...
Click to collapse
Hay, what model is your Xperia 10 plus?
My phone is I4293, i used your boot.img, when reboot, nothing is changed, just not rooted.
yishisanren said:
Hay, what model is your Xperia 10 plus?
My phone is I4293, i used your boot.img, when reboot, nothing is changed, just not rooted.
Click to expand...
Click to collapse
Mine is I3223. I don't know if it is compatible with your model, but if it flashed fine and the phone booted, try to install magisk manager apk v7.1.1 and see if you are rooted.
Rebel_X said:
Mine is I3223. I don't know if it is compatible with your model, but if it flashed fine and the phone booted, try to install magisk manager apk v7.1.1 and see if you are rooted.
Click to expand...
Click to collapse
It flashed fine, also my phone can be booted, but not rooted.
:crying::crying::crying:
Have you guys tried to summit a bug report on magisk's github issue page?
https://github.com/topjohnwu/Magisk/issues/1537
The bugreport about magisk bootloops on xperia devices
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
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
matthi383 said:
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
Click to expand...
Click to collapse
Hello,
Did you see this thread right below yours?
Android 11 OB4
Just installed OB4, anybody got a boot.img file or magisk patched boot image file? Also any news on TWRP for Android 11? Thanks in anticipation OK I was just lazy hoping somebody Elese did the work. Ended up using my OB2 patched boot image file...
forum.xda-developers.com
Magisk canary can also cause a lot of issues. I'm using 22.0.
Hey thank you! I already saw this and tried it out before to get TWRP working as in the Oxygen OS 11 Beta but this TWRP version does not work with the official OOS11 for the Oneplus 7. It's strange that on Open Beta it works and now its not working.
Watching this thread because I'm stuck too. I either need locked bootloader or unlocked with Magisk
Does anyone already has a solution to this one?
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
WareDat said:
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
Click to expand...
Click to collapse
I wish someone would upload the fastboot ROM
Thank you man it worked ! i hope others are seeing also your intructions and files so they can use them and have root back again
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,,
Hi folks, I am running a Pixel 6A that I rooted with magisk back in December. I stupidly did not disable OTA updates. Last night the QPR2 update came down and wiped root from my phone.
Bootloader is still unlocked and magisk app is installed.
I am confused about the best way to restore root. I see that the QPR2 beta required the use of the pixel 7 boot image. Does that still hold for the stable QPR2?
Also, the magisk app offers a way to choose and patch an image within the app. Can I get the pixel 7 boot image and patch it in magisk, or do I have to use the ADB/ fastboot method?
Sorry for the trouble. I promise I will disable OTA updates in the future. Thanks for any help.
Hello! I am also root user and if it is true that there was an update with the boot 6a not root and I had to use the pixel 7 or 7 pro (I do not remember which was) but if in doubt I would try only with the 6a just in case, the procedure is to download the full rom of the same version you have now, extract the boot.img, patch it with magisk and flash it by adb from the pc, is the method I use in each update and no problems until today, good luck and greetings!
If you are using Magisk Stable 26.1 or Canary 26101, you can use the Pixel 6a boot image to root as the problems mentioned above have been fixed with these versions of Magisk.
Problem solved. Y'all rock.
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
RimWulf said:
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
Click to expand...
Click to collapse
Download and open the zip => open "image-bluejay-tq2a.230305.008.e1.zip" => find your boot.img