Related
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
killer23d said:
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
Click to expand...
Click to collapse
already done, if i flash it again will it work? because im still stuck in the bootloop
Nicster205 said:
already done, if i flash it again will it work? because im still stuck in the bootloop
Click to expand...
Click to collapse
if you reflash the factory boot.img then you'll get out of bootloop.
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse
reflashing the factory boot.img seems useless. you can long-press the power button to force power down. then power up to the fastboot mode,and reflash the full factory image(11 or 10). the nomal methon working on 10 seems dizzy in 11 now.
fwiw, heres the path i used...i hate making it more steps than needed (tranferring boot image to device and back again for magisk patching for example)...
1) flash-all.bat (with wipe enabled - because clean install)
2) Immediately on reboot from 1 and before it gets anywhere near to beginning of setup: fastboot boot twrp-3.4.0-1-taimen.img
3) adb push Magisk-e66b0bf3(20425).zip /tmp
4) adb shell twrp install /tmp/Magisk-e66b0bf3(20425).zip
5) adb reboot
6) after reboot, install canary magisk manager (for whatever reason doesnt install from TWRP flash)
7) open canary magisk manager and enable magiskhide
This is caused by twrp
Use android toolbox, just boot twrp, flash magisk
boot into twrp go to advanced fix bootloop option reboot
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
suloku said:
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
Click to expand...
Click to collapse
Try flashing the older patched boot.img on the new stock firmware.
On the 12.5.3.0 ill patched boot.img from 12.5.1.0 and all right.
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
i have the same issue of auto updated and lost my root access.
Which boot.img I should Magish'd to get the root access again?
Currently installing my twrp
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
if Flash Current TWRP fails, go to Backup > Refresh Sizes and try Flash Current TWRP again
Click to expand...
Click to collapse
Currently at the Resizing stage
Edit 1: failed, I have the error bootctrl error that prevent me from installing after resizing.
I have flashed the twrp3.5.2 directly to boot resulting in bootloop and needed to install the Boot.img from the 12.5.1 from the previous bulit
Edit: actually I can ignore that error.
Magisk installed but safety checked failed even I have the "universal safety check module installed "
Also the app thoax isn't working
I'd try removing all magisk modules, installing stock 12.5.3, then using magisk apk to create patched boot.img and flash it with fastboot (fastboot flash boot magisk_boot_patched.img)
Also, maybe try flashing bot boot_a and boot_b? I had a problem were my active boot partition changed and phone became even more broken.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
Might wanna also uncheck Automatic system updates in the Developer settings to be safe.
suloku said:
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
There is a setting in the Xiaomi system updater that had by default checked auto-update. That setting need to be disabled/unchecked as well.
Since you have root with Magisk, can also Force stop or debloat the updater app, so the system will not update itself.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
I had the same issue on Redmi Note 9 Pro (joyuse). Based on your tip I've removed some modules from `data/adb/modules` and my device is finally booting normally. Thanks!
Wondering what would happen if I downloaded an image, extracted the boot.img, patched it, then took the OTA, stopped at reboot to install update, flashed the patched boot image, then rebooted?
android_dan said:
Wondering what would happen if I downloaded an image, extracted the boot.img, patched it, then took the OTA, stopped at reboot to install update, flashed the patched boot image, then rebooted?
Click to expand...
Click to collapse
you need to uninstall magisk, click on uninstall magisk and click on restore images, after that you can download and intall the update, after update, flash the patched boot.img from the last update package
spinoza23 said:
you need to uninstall magisk, click on uninstall magisk and click on restore images, after that you can download and intall the update, after update, flash the patched boot.img from the last update package
Click to expand...
Click to collapse
Why would I need to uninstall magisk? I use to do something like this with my OP8 and CRdroid. I downloaded the update, extracted the boot image, patched it, reinserted the patched boot image into the update, then ran the install command in adb. In this case I'm simply inserting the patched boot image onto the phone before rebooting.
android_dan said:
Why would I need to uninstall magisk? I use to do something like this with my OP8 and CRdroind. I downloaded the update, extracted the boot image, patched it, reinserted the patched boot image into the update, then ran the install command in adb. In this case I'm simply inserting the boot image onto the phone before rebooting.
Click to expand...
Click to collapse
Because, your current patched boot.img don't allow you to install the update, you will get an error...this is a pixel, I came from oneplus 8 pro and this is some strange for me too
android_dan said:
Why would I need to uninstall magisk? I use to do something like this with my OP8 and CRdroind. I downloaded the update, extracted the boot image, patched it, reinserted the patched boot image into the update, then ran the install command in adb. In this case I'm simply inserting the boot image onto the phone before rebooting.
Click to expand...
Click to collapse
If you are rooted when taking the OTA (even before rebooting) you will fail the pre-OTA block verifications. What it sounds like you are trying to do is update via the "Install to Inactive Slot" method in Magisk, but manually. Why not just do it through Magisk (although this method has been sort of hit or miss for some people)?
Lughnasadh said:
If you are rooted when taking the OTA (even before rebooting) you will fail the pre-OTA block verifications. What it sounds like you are trying to do is update via the "Install to Inactive Slot" method in Magisk, but manually. Why not just do it through Magisk (although this method has been sort of hit or miss for some people)?
Click to expand...
Click to collapse
Because I've tried that like four times. The first it worked, Last three it took multiple attempts to get the phone to boot and lost root.
I was rooted with Magisk on the April build and attempted to update to May. So I used Magisk to uninstall, accepted the OTA, then used Magisk to reinstall (before rebooting) but I got an error about the phone being corrupt,. So I've spent the past several hours flashing the stock boot image to both boot slots, creating new Magisk patched images, flashing those to both boot slots, rebooting, and flashing stock boot images again to both boot slots. I've done every combination of flashing stock to one boot slot and patched to another, patched to both slots, and now stock to both slots. Any time I try to boot a patched boot image the phone reboots a few times and finally tells me it's corrupt and asks to reset it (which I haven't done and prefer not to do).
I can confirm that I'm on the May update and that I'm using the May boot image in my attempts to root again. At this point, I've wiped the Magisk app (thinking a module could be causing the issue when I root) and I'm back on the stock boot image and the phone seems to be working fine, just without root.
I feel like I'm missing something simple. Can someone point me in the right direction?
I stopped to update ROM with this method since march because i had always a bootloop.
Now i install the update by android flash tool and flash boot patched with fastboot command.
You could do it. I hope Twrp wil be released quickly.
Vincent_40 said:
I stopped to update ROM with this method since march because i had always a bootloop.
Now i install the update by android flash tool and flash boot patched with fastboot command.
You could do it. I hope Twrp wil be released quickly.
Click to expand...
Click to collapse
I successfully updated to May and I've flashed the patched boot image in fastboot at least a dozen times (stock to patched, different partitions, patched to stock). The phone won't boot whenever I flash the patched image. It just bootloops and eventually gives me an error about being corrupt and asks if I want to factory reset.
Flash your patched image, then boot to safe mode, then reboot. It should work. I had the same issue and it ended up being something I had in Magisk, even though I had everything disabled. I ended up uninstalling everything in Magisk, and reinstalling.
shiftr182 said:
Flash your patched image, then boot to safe mode, then reboot. It should work. I had the same issue and it ended up being something I had in Magisk, even though I had everything disabled. I ended up uninstalling everything in Magisk, and reinstalling.
Click to expand...
Click to collapse
And if this doesn't work you might have to wipe your phone and re-flash the appropriate build. I remember seeing posts in the past with users discussing a wipe and re-flash resolving the "phone is corrupt" issue.
shiftr182 said:
Flash your patched image, then boot to safe mode, then reboot. It should work. I had the same issue and it ended up being something I had in Magisk, even though I had everything disabled. I ended up uninstalling everything in Magisk, and reinstalling.
Click to expand...
Click to collapse
I wiped data in Magisk since I can't access the modules to disable them right now (no root) and I also wiped data in Rice Tweaks since it was one of the mods I was using. I'll try this tonight and see if it works.
joshw0000 said:
I wiped data in Magisk since I can't access the modules to disable them right now (no root) and I also wiped data in Rice Tweaks since it was one of the mods I was using. I'll try this tonight and see if it works.
Click to expand...
Click to collapse
Before you wipe everything try this:
** ALSO: booting into safe mode automatically disables all Magisk modules **
How I root and update (which is identical whether rooting the first time or updating):
Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
Extracted the new boot.img
Copied new boot.img to the phone
Patched the new boot.img with Magisk Stable
Renamed Magisk'd boot.img so I know what version of firmware it's for
Copied the Magisk'd boot.img back to the computer
Disabled all my Magisk Modules
Removed the "-w " from the flash-all.bat
Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
Open a Command Prompt, navigated to S:\platform-tools
adb reboot bootloader
flash-all.bat
Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
adb reboot bootloader
fastboot flash boot kernel.img (renamed Magisk'd boot.img)
fastboot reboot
Unlock, check everything's working
Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
Reboot, unlock, made sure everything's working
Back to modding!
Click to expand...
Click to collapse
From here:
https://forum.xda-developers.com/t/...central-repository-of-relevant-links.4352027/
biTToe said:
Before you wipe everything try this:
** ALSO: booting into safe mode automatically disables all Magisk modules **
How I root and update (which is identical whether rooting the first time or updating):
From here:
https://forum.xda-developers.com/t/...central-repository-of-relevant-links.4352027/
Click to expand...
Click to collapse
Thanks. Do you know if I can run the flash-all.bat if I'm already on the current update? I have the full firmware on my PC (so I could get the boot image).
It sounds like booting to safe mode is the one thing I haven't tried.
When I updated last night I tried to disable Magisk from within the app but Magisk didn't have a backup (because I had rooted on the April build from fastboot) so I flashed the factory April boot.img, then fastboot boot magisk-boot.img, then allowed Magisk to root my phone. Then disabled all the modules, unrooted with Magisk, accepted the OTA which took unusually long to install (2+ hours), then used Magisk to restore root but I think I forgot to tell it to do the inactive partition which may have cause all of my issues. When I rebooted it gave me the corrupt error.
From there I spent a bunch of time fastboot flashing and fastboot booting the stock and modified May boot images. I've got about 4 copies of the modified boot image where I kept recreating it hoping it'd work again.
Tonight I'll try to flash the modified boot.img and boot directly into safe mode to see if I can get it to load. I may also try wiping cache in recovery to see if that helps.
joshw0000 said:
Thanks. Do you know if I can run the flash-all.bat if I'm already on the current update? I have the full firmware on my PC (so I could get the boot image).
Click to expand...
Click to collapse
YES you can.
Just make sure to edit the flash-all.bat and remove -w
otherwise you WILL wipe.
THEN... after you save the edited flash-all.bat, edit it again to make sure the -w is in fact not there.
Ive been where you are before. I forgot to disable a mod and boot-looped.
I booted to safe mode then re-flashed with flash-all, patched the boot.img and flashed that via Magisk and I was golden.
I always use this method. I even went from 12-beta to 12.1 w/o so much as a hiccup.
OTA can be problematic (or has been for me in the past). this is simple, quick, and works every time.
My suggestion is to start from scratch: delete all those previously used/attempted files -especially the patched image.
d/l the new factory image, extract/patch that boot.img This way you know everything is from the same place.
cheers
Thanks guys for all the help. Safe Mode is going to work for me. I was able to root, boot to safe mode, and reboot normal. I'm slowly enabling modules until it errors again and I've found that Renovate Ice was the culprit. But whenever it errors, I can just boot to safe mode, reboot, and start fresh with modules. Thanks!
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk Canary version. There was an Update to Magisk which I accidentally installed with OTA option instead of full. Now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image file and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
jesrani said:
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
HueyT said:
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
Click to expand...
Click to collapse
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
jesrani said:
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
⭐[ROM][STOCK] 11.0.9.1-GLOBAL-OnePlus7TOxygen_14.O.35_GLO_0350_2206171459-FASTBOOT
Created my own FASTBOOT Rom can anybody test this out, to see if it works please? Used to "Restore the Firmware" on your phone or when bricked you cannot downgrade or upgrade with FASTBOOT Roms, you must be on the same (Firmware Update Global...
forum.xda-developers.com
HueyT said:
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
Click to expand...
Click to collapse
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
jesrani said:
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
Click to expand...
Click to collapse
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
HueyT said:
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work.
jesrani said:
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work
Click to expand...
Click to collapse
Only data partition is shared. All else have both A and B parts