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.
Related
Hello everyone,
Today I had a notification telling me that there is a new version of both magisk manager and module. Therefore I first updated the manager successfully and proceeded to update the module through in-app flash. After the flash completed, app prompted me to reboot. However, the reboot process never finished and the phone got stuck while booting. Since then I only tried factory reset which only booted the phone to let me enter my sim card password but after that, it rebooted itself to boot loop again. Some info about the phone:
TWRP installed and still working,
Latest xiaomi.eu from that won't boot anymore,
Only viper4droid and youtube vanced modules were installed.
AdAway for obvious reasons.
and that's it. Now I am planning on flashing crdroid ROM to make the phone work again but the installation process requires me to do:
Flash MIUI11 eea with miflash : min V11.0.8.0.QFAEUXM note : if already on v11.08.0 there's no need to redo
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" note : if already done there's no need to redo
Flash TWRP in fastboot and boot into TWRP
Click to expand...
Click to collapse
is there a step that I should skip? It's been 6 months since I handled the initial process to be able to flash xiaomi.eu from therefore I don't remember how I exactly did that as I have only been OTA updating the from since then. I don't remember or know how to flash V11.0.8.0.QFAEUXM nor vbmeta.img nor TWRP. I don't even know if I "should" flash those. I am open to any different suggestions or help to let me achieve my goal of flashing crdroid to get out of this mess.
Thanks in advance!
Hello,
I Just want an explanation, now its obvious that (core only mode) has gone after latest magisk updates V23, So how to deal with a bootloob caused by magisk module
Because i get into bootloob yesterday and after hopeless trials I had to format my phone and re-install my ROM
PLS someone give me detailed instructions on how to deal with bootloob in case if it's happened again.
Thanks in advance
It was already described but hence to difficulties with searching through those thousands of mails I will repeat it.
In general you boot phone into safe mode.
This causes Magisk modules to be inactivate.
If bootloop was caused by one of them it is enough.
Possibly you may uninstall Magisk this way, too.
I don't remember exactly.
Ok thanks alot for u sir
But I can't boot my device into safe I google it and followed the steps but the device boots in normal mode
My device is XIAOMI Mi10t running one os custom ROM based on android 11 if u could help I'll be very glad.
Zeko Ronaldo said:
But I can't boot my device into safe I google it and followed the steps but the device boots in normal mode
My device is XIAOMI Mi10t running one os custom ROM based on android 11 if u could help I'll be very glad.
Click to expand...
Click to collapse
ADB command to remove all modules or manually remove them through TWRP are two other options:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disablinguninstalling_modules_manually
This is the pain that for many devices there is no TWRP.
It really pisses me off but it takes time for developers to implement TWRP for new devices while they come almost every day.
All those producers and phone models counted in hundreds...
Myself I am not good enough in programming to prepare TWRP starting from zero.
You can also boot into safe mode look up for your device. This will disable all magisk modules and you can delete the bad one and reboot
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.
I bought a used MI 11 Ultra running Xiaomi EU MIUI 13 Stable. The phone had the stock Xiaomi recovery on it, and I tried to flash TWRP onto it.
After having flashed multiple phones with TWRP and custom ROMs before I have run out of patience with this one. TWRP refuses to work. I can flash it and boot onto it the first time, then boot into MIUI. However, any time after that TWRP is useless and unresponsive. Now I have no usable recovery. I am not flashing anything from it, I'm just trying to make it work.
I am aware of the fact that MIUI 13/ Android 12 does not support flashing by TWRP YET, but this is something I wanted to take care of now before I setup the phone for the first time so that when TWRP adds support for Android 12 then I would have it already installed.
At this point I just want to flash the official/stock recovery on the phone, but I can't find a single thread on that.
I'm also worried about the fact that the phone may ask for the password for the MI account that was used to unlock the bootloader.
What should I do?
Any help would be appreciated.
I may be wrong - but the first thing I'd try is to find a stock package, explore it's assets, find the recovery image and flash it with fastboot.
fastboot flash recovery recovery.img
It may or may not work, but I'd try it, before I try going "full-stock" by flashing a complete image.
i have installed aosp gsi android 12 on my device(was miui 13), but android 12 gsis have issue with fingerprint, so i tried going back to stock using xiaomitoolv2 but i couldnt, i get into bootloop.
anyone know a sure and easy way to get back to stock miui 13 or 12.
im a noob to flashing, so pls use babytechtalk.
nvm, my birb brain finally got it. for fellow birb brain to regret using gsi, heres a helpful video.
you wouldnt happen to know a way how to fix it not booting into fastboot recovery or system?
enter into fastboot mode (not fastbootd), and reflash stock fastboot rom via xiaomi adbfastboot tool selecting option update for save your data