Database Users

Stuck on boot animation

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.

Unlocked bootloader and installed twrp but magisk won't install

Alright so, I've managed to uppercut down to 13a from 1ca, unlock the bootloader, install twrp. Never installed supersu, but when the phone booted to twrp I installed the magisk zip with no errors. After booting the magisk manager never showed up as installed. Installed it manually, ran it, said magisk was not installed and device fails safetynet and pts. Downloaded the latest stable magisk, booted into twrp and tried flashing it AGAIN. This time I get an error that it can't flash it. I'm totally lost here. This is all I lack to have systemless root here. Also I can't seem to boot into recovery via button presses. I keep getting the pink triangle and despite holding vol+ and power, the device just boots normally. I have to force recovery via adb on pc.
Any ideas?

Bueller?

nemisans13 said:
Bueller?
Click to expand...
Click to collapse
It's his day off
Sent from my LG-H910 using XDA Labs

I kinda ran into a issue with magisk not installing properly and how I got around it was to get your roms boot image file and make a zip of it. Then, go to twrp and flash the boot image, then flash magisk.

nemisans13 said:
Alright so, I've managed to uppercut down to 13a from 1ca, unlock the bootloader, install twrp. Never installed supersu, but when the phone booted to twrp I installed the magisk zip with no errors. After booting the magisk manager never showed up as installed. Installed it manually, ran it, said magisk was not installed and device fails safetynet and pts. Downloaded the latest stable magisk, booted into twrp and tried flashing it AGAIN. This time I get an error that it can't flash it. I'm totally lost here. This is all I lack to have systemless root here. Also I can't seem to boot into recovery via button presses. I keep getting the pink triangle and despite holding vol+ and power, the device just boots normally. I have to force recovery via adb on pc.
Any ideas?
Click to expand...
Click to collapse
You installed the magisk zip and the magisk manager apk? Did you try flashing the rom and installing masik and the apk again?
For some reason on the lg phones it won't boot directly to twrp. when you boot to recovery and it ask if you want to reset, select yes. If you have twrp installed, it will then boot into recovery.

I have not since my bootloader is unlocked I heard u can't go back to stock on the vs995

nemisans13 said:
I have not since my bootloader is unlocked I heard u can't go back to stock on the vs995
Click to expand...
Click to collapse
Nothing i suggested requires stock.
With the phone off
press and hold volume down
press the power button and hold until you see the lg logo
while holding the volume down, release only the power button and press it again and hold
if you did it correctly, you should be in recovery
it will ask if you are sure if you want to reset your phone a few times
select yes, and yes
If you have twrp installed it should boot up in twrp
Or
If you already have the bootloader unlocked, make sure that developer options are enabled
go and enable adb debugging
connect usb cable
use adb to boot into fastboot
use fastboot to boot into twrp
From twrp you can flash the rom zip, magisk zip, and then install the apk after the phone rom boots up
which rom are you using? which magisk zip? which magiskmanager.apk?

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.

Question Magisk on android 13 beta

does anyone use magisk on android beta 13?

MyRaVEi said:
does anyone use magisk on android beta 13?
Click to expand...
Click to collapse
I can't get magisk to work on android 13. after flashing the boot, I get a bootlap

I was able to fix it.
1) flash the stock boot and install the Magisk application (if removed)
2) press and hold the reset button, press "reboot to safe mode"
3) immediately press the power + volume down to get into fastut and prevent the phone from turning on
4) we get into fastubt
5) flash the patched magisk image, after that the phone should boot in safe mode
6) reboot the phone in normal mode
7) go to magisk and remove the "nothing mod" module
it was a surprise to me that even after deleting the Magisk application, the modules of the old modules cause a bootlap