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.
Related
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.
I have the same issue. https://forum.xda-developers.com/g5-plus/help/twrp-bootloop-t3740873
Im using latest twrp, im flashing Syberia Project + Magisk + Gapps
Then I reboot and it boots on TWRP, if I factory reset from the options on fastboot, it will start but without gapps and magisk, and if i try to install again those two, same thing happen, twrp bootloop
I saw some people that can start the phone on the OS using the start option from fastboot mode, but when i do this, it will start to boot on the rom for like 3 seconds, then it will turn the screen off, than twrp appears, please help.
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
I was using OrangeFox and tried to flash PixelExperience 11 from PixelExperience 10.
The flash went smoothly, but it goes to bootloop after i restart.
So i go back to OrangeFox to format my data and tried to reboot once again to finally get it working.
Then i tried to install magisk but my my recovery has encryption problem.
So i tried to install OrangeFox from ADB sideload but got error message halfway.
Now whenever i tried to reboot into recovery, it just go through the system and reboot just fine.
And to make it worse. Everytime i go to bootloader i just get blank screen and fastboot can't detect it.
My problem is PE 11 is so unstable and some of my apps won't even open.
Now is there any way to fix my recovery or bootloader?
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.