Database Users

[solved] Stuck on 1+ logo on boot after flashing Magisk, works perfectly without

Spoiler: Culprit was App Systemizer.
I've had Magisk on my OP5 (128) for some time, and had the most common modules installed (can't get the list currently), but when I rebooted the phone this morning to install AllStream (dlna streaming app), the phone got stuck on the 1+ logo screen, that shows before the boot animation. I let it run for around 15 minutes but it was still stuck.
I rebooted into fastboot (recovery didn't work) and did
Code:
fastboot boot twrp-cheeseburger.img
to get into TWRP, and I reflashed the zip of the latest OOS (4.5.8) (of course, wiped caches beforehand). I rebooted and it worked (no root, of course).
So I rebooted into TWRP and flashed a freshly downloaded Magisk 13.3 zip, rebooted, and then it got stuck on the 1+ logo again. Flashed OOS zip, and it worked again (writing from the phone right now).
TL;DR: OP5 128 with Magisk & TWRP works perfectly. And then one day, book, stuck on logo at boot
Flashed latest OOS zip, works. Flash Magisk zip, stuck at boot again. Flashed OOS again, works.
In case of a Magisk module is responsible for that, how can I remove modules without actually installing Magisk?

I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5

Try just installing the magisk manager apk but without installing magisk root. Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.

Wechy77 said:
I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5
Click to expand...
Click to collapse
You don't need to flash the twrp image on every update.

As I said, Magisk has been working perfectly for weeks, it's just that when I random rebooted my phone it didn't boot correctly.
Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.
Click to expand...
Click to collapse
If Magisk is not installed, Magisk Manager doesn't have the Modules tab.
You don't need to flash the twrp image on every update.
Click to expand...
Click to collapse
I do. Stock recovery is restored every time I flash an update.
I am quite sure the problem comes from a module and not from Magisk itself, since it was working before. But I can only remove modules if Magisk is installed.

Quote from my reply on the other thread
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse

I'm having the same problem, look here: https://forum.xda-developers.com/oneplus-5/help/magisk-modules-t3651558
I suppose the magisk's modules stay installed in the background and when we flash it again, the phone bootloops.
I had to use SuperSU for now until I understand what's happening.

Need help getting back root/magisk

I updated to 9.0.12 today and went to magisk app to reinstall and wasnt able to. So i rebooted and when it was all booted back up i didn't have magisk or root. I decided it was time for a permanent twrp so i loaded twrp. Img and installed the twrp installer. Booted back into twrp and flashed magisk 18.1.zip and rebooted. When it was back up i still didn't have magisk or root so i tried to install magisk apk and it fails to install.
I dont know what else to do to be rooted again. Any help would be great.

That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root

did you "fastboot boot twrp img name" then install the Twrp installer to both slots ?

AndyBury said:
did you "fastboot boot twrp img name" then install the Twrp installer to both slots ?
Click to expand...
Click to collapse
That's what I did and have no issues.

BittahWarlock said:
That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root
Click to expand...
Click to collapse
I had this issue yesterday too, where I loaded 9.0.12 and TWRP, rebooted to recovery, loaded Magisk and then the phone would automagically shutdown after boot.
TL;DR; an issue with a magisk module misbehaving.
After some research, this is what worked for me:
Download the latest version of Magisk and the Magisk uninstaller from the Magisk thread. Reboot to recovery, and then zip install Magisk, but don't reboot. Immediately after, run the Magisk uninstaller. This should clear any offending modules. After that, you can reboot back into recovery and install Magisk normally. You'll need to reload your modules, though.

psychen6 said:
I had this issue yesterday too, where I loaded 9.0.12 and TWRP, rebooted to recovery, loaded Magisk and then the phone would automagically shutdown after boot.
TL;DR; an issue with a magisk module misbehaving.
After some research, this is what worked for me:
Download the latest version of Magisk and the Magisk uninstaller from the Magisk thread. Reboot to recovery, and then zip install Magisk, but don't reboot. Immediately after, run the Magisk uninstaller. This should clear any offending modules. After that, you can reboot back into recovery and install Magisk normally. You'll need to reload your modules, though.
Click to expand...
Click to collapse
thanks, that worked

BittahWarlock said:
That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root
Click to expand...
Click to collapse
The best way to take the update is download the full ROM and let the factory installer do the update via local install.
You lose root and TWRP, but that happens anyway.
I typically install, reboot, install.
This forces the OS to be the same in both a and b.
Then I go through the process of TWRP, etc.

after what i mostly do:
in fastboot boot to twrp,
install full rom,
install twrp,
reboot to twrp,
install magisk,
reboot to system
aaand it shut down on me ;(
in twrp i had to:
uninstall magisk (with the magisk uninstaller)
install magisk
almost done (reboot to system)
reinstall your magisk modules (they will be gone thanks to the unistaller, so know what you have magisked)
luckily it was that simple
So to avoid it al together:
take note of your magisk modules
fastboot to twrp,
install full rom,
install twrp,
reboot to twrp,
uninstall magisk,
install magisk,
reboot,
done!

brick after installing latest magisk...

I am trying to install magisk on stock nougat with elementalx installed but after reboot it wont boot and stuck on "your device is unlocked" mensage, I tried to find some tutorial but no success

Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot

echo92 said:
Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot
Click to expand...
Click to collapse
ty bro, i tried 18.3 but still stuck and only 17 works for me

None worked for me. I cant root the phone again after I reinstalled android.

lexie90 said:
None worked for me. I cant root the phone again after I reinstalled android.
Click to expand...
Click to collapse
What device do you have, and which stock ROM are you using? Root steps can be specific to a device and the ROM you're using.

stuck after flashing magisk zip
echo92 said:
Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot
Click to expand...
Click to collapse
I flashed the magisk zip file from twrp and rebooted but its stuck not booting after that i tried wiped all data and formatted also but still the same pls he

Suraj Rawat 271201 said:
I flashed the magisk zip file from twrp and rebooted but its stuck not booting after that i tried wiped all data and formatted also but still the same pls he
Click to expand...
Click to collapse
What device are you using, which ROM are you running and which magisk version have you been using?

Stock Recovery and issues with TWRP

Sorry I'm on mobile! Poor formating and typing is all my fault
So I'm out of my mind trying to fix and find a guide to fix my issues. This is how it all started
I was running the latest magisk (20.1) and OOS (9.0.17), when I installed Vance through magisk. I didn't read the instructions all the way, so I installed the module, it worked, then I saw that you can uninstall the YouTube system apk then install Vance. I deleted the Vance on my next reboot AND uninstalled YouTube system app, and I got stuck rebooting my phone. I have TWRP installed on my phone, not flashed (I didn't know the issues with TWRP when I installed the zip through TWRP). When it got stuck booting, I flashed magisk Uninstaller and it fixed the issue. I tried to reinstall magisk 20.1, and I got the same issue, stuck at boot. So I was able to go home, and use the oneplus 6t manager found here on the forums, which roots with magisk 18.0, and, it worked! But I couldn't update to the new magisk without it freezing my boot. After some deliberation on it, I decided to wipe my phone to try and fix it, and TWRP was still installed, and all my issues still persisted. After this setback, I found fastboot rom also on xda, and got it working, did an Ota to 9.0.17 from 9.0.16. Everything was working, until I went into my recovery and it wiped my phone. I don't even know where to go from here and I need help. Any and all help would be appreciated!
Edit: I just local upgraded to android 10 oos, and it seems to be fine. I don't know yet fully because I'm not at my house!

Phone stuck in bootloop after updating Magisk

I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?

Dirty flash ROM or if 1st step doesn't work factory reset and install everything

Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!

I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.

[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.

en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen

Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.

i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.

I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.

I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system

flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.

flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.