I am trying to fix a boot loop problem after installing a problematic Magisk Module, and I am stuck. After multiple efforts to try to undo the problem in Android 11, I believe I need to downgrade first to then boot into Magisk Core-Only mode to uninstall the module. The problem is I can't downgrade. I have tried to install the latest build for Pixel 4 XL on both Android 11 DP4 and 11 Beta, and I always get a boot loop. I used flash-all and Android Flash Tool and still get a bootloop. I switch the active partition and flash Android 10 there, nothing. Can anyone help?
Btw, if I flash Android 11 Beta (or the latest Android 11 build), it works.
Did you remember to wipe the data and factory reset?
Related
Recently tried to install the new magisk update the two ways possible, by patching the boot.img and by installing the .zip file, both which have ended in failure, I am on Google Pixel (Google store version) Android O, running ElementalX kernel, when trying to install the .zip file I get an error about not being able to mount the system (twrp) I tired to manually mount the system and flash the .zip and still nothing. I used to clean boot.imgs and tried to patch them(this worked) but when I flashed them to the system slots and booted I still did not have Magisk.
Maybe??
Since I'm on a completely different device, I'm not sure, but what worked for me on 6p was when app(13) asked, do u want to update to 14?; I select yes, (recommended option) let it install then boot into recovery and flash my kernel again. I'm running flash kernel on superxe Oreo rom. That's what worked for me otherwise it wouldn't boot since I'm on f2fs file system. Hopefully this might help.
After successful installation i am stuck after boot screen animation, htc 10 Android 7 stock rom
Aftab_khatri said:
After successful installation i am stuck after boot screen animation, htc 10 Android 7 stock rom
Click to expand...
Click to collapse
Booting in recovery and reflashing custom kernel fixed this issue for me on Nexus 6p after successful installation of Magisk 14. Maybe this might help (hopefully).
Read a similar problem from this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
I'm already unlocked and I was gonna stick with the China ROM for now, so I flashed Magisk. After an hour I noticed my root access WAS GONE. So tried restarting it and... bootloop! Magisk uninstaller fixed this BUT I want that Magisk. So I kept retrying... Fastboot, flash TWRP(another issue is TWRP wont stick no matter what it will be replaced by stock recovery), Install magisk, bootloop... Rinse and repeat.
I tried 2 methods installing Magisk. TWRP and the Boot Image Patching using boot.img from latest China ROM miui_RAPHAEL_V10.3.12.0.PFKCNXM_75ea367433_9.0.zip
Im running out of ideas, can anyone here help and share how they fixed it? Thanks!
you should change to Xiaomi EU rom, no issues with Magisk.
Try installing ver 18 or 18.1 magisk i had issues with ver 19 and up on pocof1. Also on pocof1 you had to install dfe (disable force encryption) and them twrp wouldnt be replaced with stock boot recovery. Also any update that comes when twrp is installed will rewrite it to stock recovery.
Wipe userdata/factory reset after installing magisk
I have the same issue and resolve it by install OrangeFox-R10.0_8-Stable & Magisk-v20.1.zip.
Hello all. first post here as i only recently found this great site. So ive been wanting a rooted phoje for a long time now as i iswd to jailbreak my uphone back when i used apple and hadnt learned of Androida greatness. I got a pixel 5a and i love it! Its different and i just love it. Maybe more than my s21ultra even. Anyways I updated to android 12 beta and then tried to root my device. I've never done this before so i tried to learn as much as possible. Anyways I followed the magisk tutorials and unlocked my boot loader and downloaded the boot.IMG for Android 12 and patched the image then did the fastboot and adb stuff only to end up with my phone not working. Clearly I did something wrong. It originally said on the fastboot menu failed to load or verify boot image. And was stuck on that menu. Tried to recover reboot and it stayed the same. Somehow I got it to restart then it was in a bootloop going to google to the unlocked bootloader warning screen over and over. I got frustrated and left it. It died and put it on the charger and it was in rescue or recovery mode saying no command. I got it into recovery menu and tried to factory reset and now it boot to the white google screen. I wanna flash it back to android 11 that it came with so I can eventually try and root it again as that seems much more successful then Android 12. ANy help is very appreciated and I am a SUPER noob at this and don't know about any of it so please keep that in mind when replying. Thanks
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
bobpiesz said:
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help I really appreciate it! I'm gonna give it an attempt right now.
I am facing the same type of problems for so long now.
Seems Magisk breaks booting when on the 12 S bootloaders :c even with disable-verity and disable verification in any step of the process
Disabling verity and verification is no longer required with Magisk 23016.
Follow my guide here, use the Factory Image method.
My device is rooted and I want the OTA update for Android 12. I found some guides out there that basically say to try this:
1. disable automatic update
2. uninstall/restore stock boot image with Magisk
3. install OTA update
4. reinstall Magisk to the inactive slot
5. reboot
For example, https://ihax.io/install-ota-updates-rooted-android/
However when I got to step 3 it's still telling my my device is up to date with Android 11. So how to get this updated to Android 12? (without losing any of my data or settings, of course)
Maybe use the Android Flash Tool
According to the Pixel 5 forums, it's not possible to update to 12 without a wipe. So guess I'll wait until things are sorted out.
READ THIS if you're rooted before you upgrade to Android 12
If you're running rooted Android 11 and plan on updating to Android 12, READ THIS FIRST. Two new Verified Boot features implemented in Android 12 will interfere with attempts to root. I will cover what these are and how they can be bypassed...
forum.xda-developers.com
[Closed] Android 12 Update and Root ***Obsolete***
Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.
forum.xda-developers.com
scarlion said:
According to the Pixel 5 forums, it's not possible to update to 12 without a wipe. So guess I'll wait until things are sorted out.
READ THIS if you're rooted before you upgrade to Android 12
If you're running rooted Android 11 and plan on updating to Android 12, READ THIS FIRST. Two new Verified Boot features implemented in Android 12 will interfere with attempts to root. I will cover what these are and how they can be bypassed...
forum.xda-developers.com
[Closed] Android 12 Update and Root ***Obsolete***
Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.
forum.xda-developers.com
Click to expand...
Click to collapse
IDK that flash tool has an option for deselecting wipe, verity and vbmeta.
But I'm staying on 11 for now.
MrPolite said:
IDK that flash tool has an option for deselecting wipe, verity and vbmeta.
Click to expand...
Click to collapse
Ok I'll ask about that, need to be sure.
MrPolite said:
But I'm staying on 11 for now.
Click to expand...
Click to collapse
How come?
scarlion said:
Ok I'll ask about that, need to be sure.
How come?
Click to expand...
Click to collapse
Aesthetics
It just showed up for me on the day it was released.
Sidenote, is anyone else experiencing the video camera being ridiculously cropped after the Android 12 update? I'm tempted to try to find and sideload the older camera app, if you're still running 11, could you tell me what version it's on?
I'm using this one 8.2.204.362396359.12
You shouldn't have to remove Magisk.
The most important and critical issue is to remember to reflash vbmeta BEFORE your phone boots to system, otherwise you will have to wipe /data again.
There's two ways to update:
1. Sideload the OTA (DO NOT use the automatic OTA). When the sideload finishes, immediately reboot to bootloader, and reflash vbmeta:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Now, you can flash a patched boot image, if you already patched it, or you can boot into system to do so, then reboot to bootloader to flash it.
2. Dirty flash the factory image, either via ADB or via Android Flash Tool. To do it via adb:
Code:
fastboot update --disable-verity --disable-verification image-bramble-buildnumber.zip
No need to reflash vbmeta as you already included the flags.
If you want to be able to prevent reboot so you can flash the boot image, add --skip-reboot.
Is not possible now to get Device Certified in PlayStore? After flashing Magisk?
peikojose said:
Is not possible now to get Device Certified in PlayStore? After flashing Magisk?
Click to expand...
Click to collapse
It is - using Universal SafetyNet Fix. I'm using Magisk 23001 + USNF 2.1.1 on my Pixel 5, and pass SafetyNet.
After some time I got a second Axon 10 and I spend some time figuring out what was possible with this phone in terms of root, custom ROM etc.
My results are as follows.
What is working:
Android 9 + Magisk and TWRP
Android 9 + TWRP + Custom ROMs (LineageOS 16 and patched GSI)
Android 10 + Magisk and TWRP
Android 10 + Magisk and MicroG flashed via Magisk (= stock ROM without Google Services)
Android 11 + Magisk
What is not working:
Android 11 + Magisk + TWRP (TWRP logo flashes randomly but TWRP does not load).
Android 11 + Magisk + MicroG (the nanolx patching script does not work with Android 11 as of yet)
Encryption in Custom ROMs
Method to flash files via EDL
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
Unlock Bootloader:
Before you try any of the files, you MUST unlock your bootloader!
BACKUP of your data as it will be lost!
Download the EDL tool from this Thread
If your phone is not on android 9, you must go back to Android 9 first. e.g. by using my Android 9 1.9 backup.
After you restored it, restart while holding the volume + key and do a factory reset / format data.
Boot into EDL again and unlock the bootloader.
Now you are on android 9 with unlocked bootloader.
From here you can follow the other guides in the form and install TWRP or lineageos. Or flash one of my files below.
Flashing EDL files:
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
I put all my files into this MEGA account: MEGA
Android 10 version 2.9 Magisk + TWRP
Android 11 version 3.5 stock
Android 11 version 3.5 Magisk
Android 10 version 2.10 stock
Android 10 version 2.10 Magisk (TWRP can be flashed with Magisk)
Install MicroG:
Only works on Android 9 and 10.
Before you install MicroG you must patch the stock ROM to allow for signature spoofing.
The patcher script I used is on https://downloads.nanolx.org/NanoDroid/Stable/ When I write these lines the up-to-date-version is NanoDroid-patcher-23.1.2.20210117.zip
Reboot.
Install MicroG from the Magisk repository.
After a restart there will be error messages that google apps keep crashing. With each warning, disable the apps one by one.
When you reboot again, no errors should appear and MicroG should report that it is fully working.
You can add the Bromite Framework and give F-droid system rights. Both are available from the Magisk repo.
Updates will likely install the Google apps again and uninstall Magisk...
Revive phone:
Not really related, but I bricked my phone several times.
If your phones does not boot anymore or hangs in a bootloop, try accessing the EDL mode.
The easy way:
Boot while holding volume -
The hard way:
Old Volume +, volume - and power until you end up in EDL. The screen will be black, so it helps if you have the Phone connected to Windows and can hear the system sound when the USB sees a connection.
In anyway you can then use the EDL tool to restore / flash an EDL image.
On custom ROM support:
Well there is LineageOS 16 by Unjustified Dev. https://forum.xda-developers.com/t/rom-unofficial-zte-axon-10-pro-9-lineageos-16-0.3992127/ It works well. But has a patch level that is outdated by now.
On top of it you can install the GSI ROMs created by Rafyvitto. The latest one is Resurrection Remix https://forum.xda-developers.com/t/...nofficial-resurrection-remix-q-8-6-7.4172527/
with a security patch level of mid 2021. Which is recent enough to use. The stock roms are not much better.
With both Custom ROMs, encryption is not working which poses a privacy/security risk when your phone is stolen. Do not forget that your phone does not only contain your photos and data but also your passwords to your accounts.
Added Android 10 2.10 files.
Its nice to see anything new for this phone. I wish I can use these roms but I have the American version.
Hi and thanks for your work and your files.
I'm stuck on "Loading the programmer: prog_ufs_firehose_sdm855.elf >>>", if I try to recover your edl files with EDL Tool, v 3.25.
I have to choose option 2: "Restore Full EDL from backup", right?
Is there a way to check if the bootlaoder is really unlocked?
Thanks in advance
OK, I was able to solve the problem with the "programmer" and try the backups. The next step was almost clear. The device is stuck in bootloop. I've already tried all the backups I could find on Mega. After the EDL Tool has done its work and the device has restarted, the mobile phone goes into the boot loop. And now? So the starting position was: Android 9 with an open bootloader. Maybe someone has an idea?
After I couldn't get the device out of the bootloop, I flashed the A2020G_PRO_V1.6_FULL_EDL via MiFlash and then did an OTA update to 1.8.
Then I tried unlocking the bootloader again, which unfortunately didn't work. The flash is carried out without errors, but the device then apparently does not start in the desired Fastboot mode.
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
brian117 said:
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
Click to expand...
Click to collapse
Maybe you need to switch the slot in TWRP. It sounds as if you install it to the other slot (like A) an then boot B. Or vice versa.