Stuck on boot animation - Xiaomi Mi A1 Questions & Answers

After deselecting "Magisk code only mode" and restarting my phone I got stucked in the boot animation ("androidone").
About an hour later it started bootlooping, probably because the battery is getting empty and I dont see a way to poweroff the device.
Is there a way to fix it without flashing an original image? I prefer keeping my Oreo.

You probably have unsupported magisk module enabled. Reflash stock boot.img and then select "complete uninstall" from Magisk manager, it could help. If not, boot TWRP (warning, it's only testing build so far) and flash magisk uninstaller, reboot. After reboot try Magisk again, be careful which modules you install.

Related

S5Neo-Root: Missing custom recovery menu

Hi guys,
first of all i may apologize for my school-engl. and let you know i am really new in the world of roots.
My goal was to flash magisk in the custom recovery mode of twrp. So after about 3h research i flashed twrp with odin, everything worked like described in my intructions (cant post links here yet, it was from android gadgethacks) and root checker confirmed the root.
Now in all the instructions i have read, i am told to reboot in the recovery mode and see the new modificated "custom recovery"-menu where i can flash the magisk.zip in the intall-section.
I dont. Its rebooting in the original recovery mode, where i havent the possibility to flash anything, right?
In my desperation i tried to flash it in the intall section of twrp manager but that didnt work. Magisk Manager doesnt confirm that magisk is installed.
someone here has experience with that missing twrp-recovery-menu or another idea how i could install magisk on my rooted s5neo? Thanks in advance
Bombadadil said:
someone here has experience with that missing twrp-recovery-menu or another idea how i could install magisk on my rooted s5neo? Thanks in advance
Click to expand...
Click to collapse
I'm new to root as well, but I just rooted my own S5 Neo (which is why I saw your post while searching for information), so I'm a couple of weeks ahead of you.
I'm a little unclear why after flashing TWRP you say the root check confirmed root. My understanding is that TWRP alone won't root the phone.
You may have already figured this out, but here's what I needed to do to install TWRP and Magisk. The issue for me was that auto-reboot from ODIN was allowing the phone to clear TWRP before it was installed. I'm not sure what your issue is, but there is one possibility I note below.
My successful procedure follows (ask for clarification if I gloss over something you don't understand). Others should feel free to correct any mistakes I write, since I'm no expert and I'm writing from memory:
1) Download the Magisk ZIP to your phone, so it will be available when needed.
2) Ensure your phone is set for OEM Unlock (via the Settings/Developer Options setting menu, which is only shown after you activate it by going to Settings/About Phone/Software Information and tapping Build number 7 times).
3) Download the TWRP *.img.tar file to your PC. Make sure it was made for your model phone.
4) Start ODIN on your PC, and use the AP button to load the TWRP *.img.tar file. Wait for ODIN to finish checking it.
5) In ODIN's Options tab, unselect "auto reboot", so your phone won't reboot when done.
6) Turn off your phone, then boot into Download mode (vol_down+home+power button) and confirm with vol_up button.
7) Now connect the phone to the PC with a USB cable and confirm that the "Added!" message shows in ODIN.
8) Click Start in ODIN to flash TWRP to your phone. Wait for the top left to show a green PASS message.
9) At this point, your phone is connected and still in Download mode. Detach the cable and hold Vol_down+power until your phone shuts off (maybe 10-20 sec).
10) Boot into Recovery mode (vol_up+home+power). The phone should now be installing TWRP. Wait until it finishes and then shows something.
11) My memory here is fuzzy. I don't recall whether TWRP immediately shows now, or if the phone boots normally, or it asks you whether to boot or shutdown, so here are five possible routes:
11a) If the phone shows the TWRP window, go to step 12. I think this is what should happen.
11b) If the phone shuts off, boot into Recovery mode again. This should now be TWRP, so go to 12.
11c) If the phone boots normally, shut it off and boot into Recovery mode. This should now be TWRP, so go to 12.
11d) If the phone asks you what to do, select power off and then boot into Recovery mode. This should now be TWRP, so go to 12.
11e) If booting into Recovery doesn't show TWRP, then something is not quite right with my instructions, or how you followed them, so come back here with the results.
12) Here's where your issue may be. TWRP is installed temporarily by default, and restarting the phone will overwrite it. During this temporary time, you can immediately flash a Zip, then reboot and get your original stock recovery back. You may have restarted the phone without realizing this, which then overwrote TWRP. So you need to decide whether your want it temporarily to flash Magisk, or keep it permanent for other uses (like making Nandroid backups). To make the choice, TWRP asks you whether your want to "Keep Read Only" mode (temporary) or not (permanent).
13) If TWRP is temporary, you need to install Magisk now before rebooting. If it's permanent, you can reboot and do it later. In the TWRP menu, tap Install. Navigate to the location where you placed the Magisk ZIP. If you don't see it, look at the lower right button. If it says "Install Image", it should be showing available Zips. If it says "Install Zip", then it's showing images, so tap it to show Zips.
14) Select the Magisk Zip and it should be installed. Go back to the main TWRP menus and tap Reboot, then System to restart your phone.
15) Look in your Apps for the Magisk Manager. It should have been installed from the Zip. Open it and check that "Installed Version" has a green check. That should be it.

Magisk loop after installation

I had TWRP on my phone and switched to OrangeFox to install MIUI V10.3.12.0
After installing the new MIUI version, I went to root Magisk 19.3
After installing Magisk, my phone has an infinite loop, it enters the lock screen and restarts, stays in this process for about 5 times and goes to recovery mode.
I wonder what I may have done wrong, or if I have to reinstall my system?
Sorry for my english.

No TWRP, Bootloop after installing EdXposed Module

I am running the latest OOS 10.0.1 Stable on my OP6T
I installed the Riru-Core module from magisk manager, rebooted perfectly fine. Afterwards installed the EdXposed module. Now I am stuck in a bootloop. Is there a way to uninstall the module without having TWRP? or factory resetting.
edit: I am unable to boot into fastboot or recovery
Please help me out
Thank you
Press volume up + power button to force reboot then press volume down + power to get into stock recovery. Then you can boot to fastboot through stock recovery...
2 Options ,
1. Try flashing stock boot.img on fastboot to remove Root so EdExposed won't work. (Recommended)
Then you'll have the option to remove EdExposed modules.
2. msmdownloadtool , But it will REMOVE all your data and will put your phone on Android 9.

My 9t stuck on mi logo

Sadly I was messing with the Magisk Modules and Installed Viper4Android, after a while I unistalled it and right afterwards my phone became soft bricked, I can´t use the recovey and my only option is the fastboot; I´ve already tried installing a new rom but it wasn´t usefull if somebody can help me I´ll be very happy.
i kept rebooting in to fast boot also after doing the viper stuff so i held down vol up and power while in fastboot till it forced it to reboot to twrp.
then just reflashed mu rom in twrp.
cmlucht said:
i kept rebooting in to fast boot also after doing the viper stuff so i held down vol up and power while in fastboot till it forced it to reboot to twrp.
then just reflashed mu rom in twrp.
Click to expand...
Click to collapse
If/when you have bootloop because of a Magisk module, just boot to TWRP and in Terminal go to /data/adb/modules and delete the suspect module (the last you messed up with) or all modules
Nevertheless, Viper4Android works fine (follow OP post #1 - guide for stock Q):
https://forum.xda-developers.com/k20-pro/themes/guide-viperfx-miui-11-android-10-t3994621

Magisk 21.4 causing bootloop on LG G5(H850)

Hi all,
So I was triying to update my Magisk through the recommended direct update method. I got a bootloop. Never had any issues with this update method, Magisk always did a splendid job.
Now my only options are:
1. Flash a custom rom (I don't have any stock Telekom roms)
2. Update Android OS to 8.0 with LG Bridge (my goal is to have a stock rooted android os, that's why I'm doing this)
3. adb reboot, flash the latest twrp recovery (at least that's working)
4. flash the latest Magisks without reboot option, just power off and then turn on. And this is stage where I get a bootloop.
I only have v19.3 saved on my HDD. Flashing that is working just fine, not causing any bootloop. However Fake GPS and Pokémon Go are not working with this version anymore. :/ So I'm kinda chess-mated here because of this Magisk bootloop.
Anyone can help me how can we fix this?
I have bootloops with all Magisk 21.x versions, so I'm stuck with 20.4. Can't you download Magisk 20.4 and install it from TWRP? I don't need SafetyNet, so I have no idea if Magisk 20.4 can still pass the check, but at least it would be newer than Magisk 19.3.
I downloaded the previous 21.0 versions from here https://droidfeats.com/download-magisk-zip/ flashed it and it's working. I also tested the previous versions. Seems like only 21.4 version is affected only, which is the latest stable.
I had the same problem: I had Magisk 21.4 and withing Magisk Manager I tried to update to v. 22.0 because I got an update prompt that asked me to do so. Trusting everything was fine I updated but I got a bootloop. I managed to recover from bootloop and get the latest version of Magisk working in my Huawei Y5 MYA-L13 (Android 6.0). For these steps, it is assumed Magisk v21.4 and Magisk v22.0 ZIP files are stored in your storage. This is the way I did it:
Manage to get into stock recovery mode.
This step was more time-consuming than it should have been... This Huawei model with the bootloader unlocked states at boot: "Press volume key up to 3 seconds to enter recovery to restore your device". It didn't... With Vol+ just restarted the device (no TWRP or stock recovery or download mode...) and pressing Vol- it loaded into the bootloop. It took me some time to guess the right way:
Plug the turned-off device into a USB cable plugged into the computer.
Wait for the device to start into "charging mode" (I made up this... I mean wait until the charging percentage appears).
Turn on the device using the Power Button.
Immediately, press and hold Vol+.
The device will reboot. Press and hold Vol -.
The device will get into the stock recovery mode (EMUI Huawei eRecovery).
Try again if this fails... After a few attempts, you'll get it.
Now the device will be visible to ADB. Verify this in a command prompt with adb devices. Mine was listed as 0123456789ABCDEF recovery.
Use the command adb reboot recovery to get into the real recovery mode. I mean TWRP. (It's still there even if it seemed to be it wasn't).
Flash the version that caused the problem. In my case, I had Magisk v21.4 initially, so I installed this same version ZIP I got from the official Magisk GitHub releases section.
Once finished the installation, if it was successful Reboot. The device should boot normally this time, having installed this version of Magisk and not the new one, of course.
Now proceed to uninstall Magisk 21.4 completely using the ZIP file provided in the above URL (step 4) with TWRP.
Follow the official installation guide in the Custom Recovery section to install Magisk 22.0 (that is: having renamed Magisk-v22.0.apk to Magisk-v22.0.zip previously, use TWRP to install it). Reboot.
Your device should boot normally. You'll find a Magisk app where you'll be able to verify latest Magisk 22.0 was successfully installed!!! DONE.
I hope my guide is useful to someone. If so, please like my post to be aware it was useful. Greetings!
TL;DR
adb reboot recovery
Install Magisk-v21-4.zip. This solves bootloop problem!
Uninstall Magisk using Magisk-uninstaller-20210117.zip
Rename Magisk-v22.0.apk to Magisk-v22.0.zip. Install it using TWRP.
Reboot. You have the latest Magisk version v22.0 installed with no bootloop!!!
I've upgraded from v20.4 to v22 yesterday using the new Magisk app, it all went smoothly.

Categories

Resources