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!
Related
Shortly after receiving my bootloader unlock code, I made a real mess. First, I tried to install TWRP via these instructions: https://twrp.me/huawei/huaweihonorview10.html
Specifically, I used the ADB/Fastboot method. Unfortunately, when I went to reboot to recovery by holding power+vol-up, it always took me to the Huawei eRecovery, not TWRP. I assumed the install failed after multiple attempts, and thought I would try to root with Magisk so I could use the TWRP app to flash the recovery instead.
I downloaded the ramdisk.img from here: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I found this link here: https://forum.xda-developers.com/honor-view-10/how-to/honor-source-program-t3732573
I then proceeded to patch it with Magisk and flashed the patched .img file. After doing this, the phone would bootloop a few times before ending up at the eRecovery again. I cannot get the eRecovery to get the packaged data for the Upgrade/Install recovery option, but when I choose the Factory Reset option, it reboots to TWRP (weird!) for about 3 seconds and then reboots to bootloader. I tried reflashing the original ramdisk.img when in the bootloader, but this made no noticeable difference.
My next guess is to try flashing recovery_ramdisk.img to try to remove TWRP and restore whatever stock image that was. I want some advice from the community first because I fear this may make things worse!
I saw that Magisk did in fact cause bootloops due to a compiler bug, according to this post: https://www.xda-developers.com/magisk-16-bootloop-crash-fix-huawei-honor-support/
Has anyone run into a similar issue? I assume since I can still get to the bootloader I can fix it, but I'm at a loss as to what the best next step is.
I flashed that recovery_ramdisk image. The result is that instead of booting to TWRP for a few seconds, it reboots into another eRecovery which allows me to do a factory reset and wipe the cache. After doing these, I still can't access the system.
So it turns out my device is BLK-104 and the problem was that I tried to flash files for BLK-109!
I'm surprised things worked as well as they did!
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Don't bother with twrp
Just use magisk.
Download the factory pixel image on your PC , unzip the boot.img file and transfer to your phone.
Open magisk manager and install magisk by patching the boot.img file U just transferred.
Copy that new patched boot img back to your PC.
Use ADB to ADB reboot bootloader
Type: fastboot flash boot patched_boot.img
That's it
mediaman123 said:
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Click to expand...
Click to collapse
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.0-0.img; in twrp, flashed 3.3.0-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
My safety net passes in magisk, but I don't use any apps that I can verify that with.
jlokos said:
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.3-0.img; in twrp, flashed 3.3.3-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Click to expand...
Click to collapse
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
docluv01 said:
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
Click to expand...
Click to collapse
Sorry; an extra 3; I'm using TWRP 3.3.0.0.
---------- Post added at 07:58 AM ---------- Previous post was at 07:37 AM ----------
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
I DL magisk hide module and use it for two apps, one for comcast business and the other which regulates my home thermostat.
Wow, thanks guys.....you have all laid out pretty well your processes which I will go through later on....
It's strange, as everything is installed and magisk believes it working it just doesn't pass thee root check..
I'll get back to you with my progress...??
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
Got the notice there was an OTA. As per instructions I tried uninstalling magisk and restore images. Got a toast notification saying no backups found.
Tried a complete removal of magisk, now stuck at the Bootloader unlocked screen.
Tried flashing the patched boot.img in fast boot and rebooting. Now I'm stuck on the boot animation.
Done with root on this phone, not worth the headaches. (TiBU was the only thing I use it for these days) Get me back to no magisk without loosing data.
[edit]
Ended up having to wipe litterly everything via recovery then it finally booted. :/
The patched image you're flashing won't work because you updated to 10.0.14. When updating, you're not supposed to uninstall Magisk, just disable the modules you have downloaded in the "Modules" section.
You need the updated root boot.img. I'll try to upload it later.
Snaxe123 said:
The patched image you're flashing won't work because you updated to 10.0.14. When updating, you're not supposed to uninstall Magisk, just disable the modules you have downloaded in the "Modules" section.
You need the updated root boot.img. I'll try to upload it later.
Click to expand...
Click to collapse
Thanks. At that point I hadn't installed the OTA update yet. I had just prepped by going into Magisk manager and (mistakenly) hit completely remove magisk. Which it did, then rebooted but left me hanging at the unlocked bootloader warning.
I tried flashing the patched boot.img from fastboot, and reflashing magisk from inside of the temporary twrp, but after a reboot I was left with the boot animation that never went away.
After I wiped it and got back in, I let it download the latest OTA and installed it.
So currently I'm at 10.0.14 now, but without root.
Hello,
In all of the steps to install Magisk on a phone, I never liked the step in which you have to flash the patched boot image on the boot partition. I always thought it is pruned to errors, especially if you do that at every update, an oversight maybe when you download the ROM or maybe you use an older version of the patched image and your device is soft-bricked. So, I always wondered if there are other, safer, solutions to do that step. When searching for various guides, I found one that instead of directly patching the boot image, boots it instead and then uses the direct installation option in the Magisk app to extract, patch, and re-flash the boot image. I know that the result is pretty much the same, but if you screw up with the patched boot image, the result is just a temporary bootloop that you can resolve by just restarting your device. But in all the guides I've read, only one suggested this alternative solution, so I was wondering why this solution isn't suggested or, at least, mentioned, for those who are afraid to do the blind flash. There are possible issues with using this method or what?
I already used this method two times for installing Magisk on a Oneplus 9 and a Pixel 6, and now I'm here with a brand new Pixel 6 Pro and I've to decide what method to use.
Because you're essentially doing the same thing. Even if you flash the incorrect boot image, just flash the correct one afterwards and problem resolved. You can do either way, the alternative just takes a step longer.
Now that restore images/flash to inactive slot after ota is fixed on Magisk (canary 24306 and later), I would boot the patched image, then do a direct install.
This ensures that Magisk makes a backup of the stock boot image so next update can be taken OTA if desired.
Note: the re-root after OTA method may not work on custom kernels which often make changes to partitions other than boot
shoey63 said:
Now that restore images/flash to the inactive slot after OTA is fixed on Magisk (canary 24306 and later), I would boot the patched image, then do a direct install.
This ensures that Magisk makes a backup of the stock boot image so the next update can be taken OTA if desired.
Note: the re-root after OTA method may not work on custom kernels which often make changes to partitions other than boot
Click to expand...
Click to collapse
Thanks for the answer, this is really helpful. So, should I use the canary version for the first installation or can I use the stable and update to the canary when I have to OTA update? This is just to be sure, I don't know how "stable" is the canary since I never used it.
And since I'm, I'll take the opportunity to ask another related question: how bad can I screw up with the boot image? For example, if I flash a boot image of another device (oriole for example), should I still be able to boot into fastboot and flash the original, or this will prevent me to boot in the fastboot mode at all?
Because I'm still not sure if the initial bootloader phase (the one that boots up the fastboot) is included in the boot image or not, since the recovery has been included in the ramdisk of the boot image since the introduction of the A/B devices (or, at least, I think so).
@fuji97
You can patch intially with stable and change to canary before next OTA if stable hasn't been updated by then.
Booting or flashing boot images can't affect the bootloader partition, which is seperate.
Fastboot boot the patched image, if it boots up you are good to go with a direct install from within Magisk. If it bootloops you will just boot up to your original setup with stock boot intact. Then you can troubleshoot.
If you directly flash a scewed up boot image, it will probably boot to bootloader, and you can flash a working boot.img.
If it bootloops 3 times, the phone will boot to the opposite slot, and you will have a working system again.
shoey63 said:
@fuji97
You can patch intially with stable and change to canary before next OTA if stable hasn't been updated by then.
Booting or flashing boot images can't affect the bootloader partition, which is seperate.
Fastboot boot the patched image, if it boots up you are good to go with a direct install from within Magisk. If it bootloops you will just boot up to your original setup with stock boot intact. Then you can troubleshoot.
If you directly flash a scewed up boot image, it will probably boot to bootloader, and you can flash a working boot.img.
If it bootloops 3 times, the phone will boot to the opposite slot, and you will have a working system again.
Click to expand...
Click to collapse
Awesome, thank you! You clarified a lot of my concerns.
fuji97 said:
When searching for various guides, I found one that instead of directly patching the boot image, boots it instead and then uses the direct installation option in the Magisk app to extract, patch, and re-flash the boot image.
Click to expand...
Click to collapse
I do this exact procedure for every OTA. It's just easier for me and I've had numerous problems trying to "keep" root versus just booting to a patched image and reinstalling.