Recently I flashed and updated several magisk modules on my phone running Lineage 19.1 and got stuck in boot animation.
Unfortunately I hadn't enabled adb root access so can't remove the module by hand. Meanwhile there's no suitable recovery that can decrypt A12 /data so Magisk-Manager-for-Recovery-Mode just won't work either, nor can I access /data/adb/magisk.
I do want to escape from reflashing whole phone. Any hints are appreciated!
lineagefan0 said:
Recently I flashed and updated several magisk modules on my phone running Lineage 19.1 and got stuck in boot animation.
Unfortunately I hadn't enabled adb root access so can't remove the module by hand. Meanwhile there's no suitable recovery that can decrypt A12 /data so Magisk-Manager-for-Recovery-Mode just won't work either, nor can I access /data/adb/magisk.
I do want to escape from reflashing whole phone. Any hints are appreciated!
Click to expand...
Click to collapse
Safe Mode is your only chance
Stillhard said:
Safe Mode is your only chance
Click to expand...
Click to collapse
Thank you. Never noticed that the disabled state of modules persists after exiting Safe Mode. That does help.
lineagefan0 said:
Recently I flashed and updated several magisk modules on my phone running Lineage 19.1 and got stuck in boot animation.
Unfortunately I hadn't enabled adb root access so can't remove the module by hand. Meanwhile there's no suitable recovery that can decrypt A12 /data so Magisk-Manager-for-Recovery-Mode just won't work either, nor can I access /data/adb/magisk.
I do want to escape from reflashing whole phone. Any hints are appreciated!
Click to expand...
Click to collapse
Hi will
If Debugging is enabled , Push while booting on ADB and thank me later
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
yot2703 said:
If Debugging is enabled , Push while booting on ADB and thank me later
Click to expand...
Click to collapse
It just removes all modules, which is not the optimistic way. Still a good choice if module disable takes no effect.
lineagefan0 said:
It just removes all modules, which is not the optimistic way. Still a good choice if module disable takes no effect.
Click to expand...
Click to collapse
Yeah but if you got stuck in a bootloop, cause of a module it's a great way to rescue the device
Related
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
6opuc said:
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
Click to expand...
Click to collapse
https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
Get a adb logcat on boot stuck with xposed installed, put it on pastebin and link here to see why isn't booting.
dcastro172 said:
https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
Get a adb logcat on boot stuck with xposed installed, put it on pastebin and link here to see why isn't booting.
Click to expand...
Click to collapse
Hi dcastro172,
Unfortunately adb logcat does not give any info. At this boot stage the device is not detected yet by adb, hence no logcat possible. Is there anything I can collect differently?
Here are two logs from /data/data/de.robv.android.xposed.installer/log/
Perhaps this helps?
6opuc said:
Hi dcastro172,
Unfortunately adb logcat does not give any info. At this boot stage the device is not detected yet by adb, hence no logcat possible. Is there anything I can collect differently?
Click to expand...
Click to collapse
You see bootanimation or only splash logo?
Enviado de meu SM-G900M usando Tapatalk
6opuc said:
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
Click to expand...
Click to collapse
Xposed v87?
I guess it is boot animation. It it like a clock with moving hands....
Yes. 87
6opuc said:
Yes. 87
Click to expand...
Click to collapse
Looks like update break Xposed, bunch of errors in log, open a issue at Xposed github.
Well hello,
I'm on the canary build on Huawei P20 pro. I've installed, I guess... A module, which was not for this version of magisk, or whatever...
The phone, when I press the + button during boot -> to boot with magisk running -> the phone stays in bootloop
If I boot without the + button, therefore without magisk running, the phone works.
But now I'm stuck with some problematic module, which I can't disable nor uninstall, because the Huawei P20 pro has encrypted /Data and the magisk uninstaller tells me it can't access the /data so I should uninstall the magisk with the magisk manager.
But I can't, because I'm booting only without the magisk, so the magisk manager doesn't see any Magisk running.
So, I even flashed back the stock boot, which worked and then flashed the magisk once again (the installer told me I got stock boot and it's patching and stuff...) But I'm back where I was. without +button the phone works, but no magisk. With the +button boot I got stuck in bootloop.
I've serached everywhere to find some "patchable magisk module disabler" but without luck.
Thanks for any advice
Have you tried magisk recovery management? That may work.
Hi thanks, didn't know somethiung like that existed... But still doesn't work. I'm stuck at "error 1" in twrp. I've tried multiple versions of TWRP, tried magisk again, tried reflashing stock boot. but still error 1.
It's wierd...
Do you have access to /cache? If so:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disable_all_modules
Didgeridoohan said:
Do you have access to /cache? If so:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disable_all_modules
Click to expand...
Click to collapse
Hi, I've been browsing the magisk webpages today and I found exactly what you sent to me. Thank you kind sir. It worked
Didgeridoohan said:
Do you have access to /cache? If so:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disable_all_modules
Click to expand...
Click to collapse
Hi, I've been browsing the magisk webpages today and I found exactly what you sent to me. Thank you kind sir. It worked
I updated to build 251 and then was able to root normally.
However, I installed a module which prevented me from booting with root.
Is there a way to fix this?
lambstone said:
I updated to build 251 and then was able to root normally.
However, I installed a module which prevented me from booting with root.
Is there a way to fix this?
Click to expand...
Click to collapse
Boot to recovery and magisk will be used to boot..
So try it with ADB.
ADB reboot recovery
Let the phone reboot.
As it has magisk installed it will not open twrp anymore . But it will use the image installed for magisk, from your perspective you'll just see the phone reboot.
Once you boot up you'll have root access..
Essentially what this means is you would have to boot to recovery to do a normal reboot if you wish to retain root access.
dladz said:
Boot to recovery and magisk will be used to boot..
So try it with ADB.
ADB reboot recovery
Let the phone reboot.
As it has magisk installed it will not open twrp anymore . But it will use the image installed for magisk, from your perspective you'll just see the phone reboot.
Once you boot up you'll have root access..
Essentially what this means is you would have to boot to recovery to do a normal reboot if you wish to retain root access.
Click to expand...
Click to collapse
It refused to boot. Anyway, I dont think there is a way to fix this on emui9 if you have installed a faulty magisk module that results in device being unable to boot with root.
I had to do a complete factory reset in order to get it working again.
lambstone said:
It refused to boot. Anyway, I dont think there is a way to fix this on emui9 if you have installed a faulty magisk module that results in device being unable to boot with root.
I had to do a complete factory reset in order to get it working again.
Click to expand...
Click to collapse
Just allow it to boot without root. Remove the module and magisk and reinstall.
Hi. I have recently rooted my new pixel 4 with magisk and was installing Riru Edexposed to try and get fingerface working. Unfortunately during installing edexposed my phone got stuck in a bootloop. Because the pixel 4 doesn't have a custom recovery I don't know how to flash the exposed uninstaller zip or even to just access my files. Any help would be much appreciated. Thank you.
Have a look in the apps/themes section.
tulsadiver offers a boot image which removes all magisk modules....
pa.pn2 said:
Have a look in the apps/themes section.
tulsadiver offers a boot image which removes all magisk modules....
Click to expand...
Click to collapse
Is there really no Custom recovery or TWRP for Pixel 4's even tho Root works & ontop of that how're you supposed to flash disable dm-verity if you don't have a flashing ROM installed?
Nightshadex543 said:
Is there really no Custom recovery or TWRP for Pixel 4's even tho Root works & ontop of that how're you supposed to flash disable dm-verity if you don't have a flashing ROM installed?
Click to expand...
Click to collapse
No, no custom recovery yet. I thought it was gonna be a pain but I was able to flash DirtyUnicorns ROM without any issues.
Prey521 said:
No, no custom recovery yet. I thought it was gonna be a pain but I was able to flash DirtyUnicorns ROM without any issues.
Click to expand...
Click to collapse
Goddamnit thanks. TWRP 3.3.1 or Blu-spark don't work? So, that means computer based flashes. That's unfortunate, I'd rather have something installed incase of a Bootloop after attempting root. Makes things less problematic.
Thanks again.
Nightshadex543 said:
Goddamnit thanks. TWRP 3.3.1 or Blu-spark don't work? So, that means computer based flashes. That's unfortunate, I'd rather have something installed incase of a Bootloop after attempting root. Makes things less problematic.
Thanks again.
Click to expand...
Click to collapse
Nope, just fastboot and adb commands for now.
Looks like magisk will add a "module disabler mode" in the next updates when the phone will be rebooted in safe mode.
For now the only thing to do is to flash the custom boot image from tulsadiver that enable core mode only.
I heard about another alternative, from didgeridoohan magisk wiki, but never tried if it works in this case:
Since Magisk v19.4, there's an adb command that can be used to uninstall all modules on your device.
If the device is bootlooping or simply haning on the boot animation you have a good chance that you can use this command to get up and running again.
Hook your device up to a computer (or other device you can run adb from) and execute the following command:
adb wait-for-device shell magisk --remove-modules
After that you can start your device and as soon as adb is available the command will activate, the modules will be removed and the device will reboot. There's of course a chance that the troublesome module has done something that the command can't remove...
Click to expand...
Click to collapse
Just checked out both of those contributors. Good stuff, appreciated.
I've flashed the new Lineage 18 on my Samsung Galaxy S10E Exynos and had trouble installing Magisk. I managed to get it installed somehow and tried adding a bunch of Magisk modules, some of which failed.
After rebooting, it booted up and stayed alive for a while before cutting to the bootanim and getting stuck in a loop. Disabling Magisk by flashing the old recovery.img solved it for me, but everytime I try to get Magisk to work again, it gets stuck in a loop after booting up the first time.
Help! Will uninstalling all the modules solve this issue and if it will, how do I go about doing it.
Any/all solutions much appreciated.
Thanks!
To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.
XTrail02 said:
To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.
Click to expand...
Click to collapse
Worked like a charm! Thank you
XTrail02 said:
To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.
Click to expand...
Click to collapse
is it possible somehow to do this with the stock recovery. I can boot with out magisk just fine, but if i enabled it stuck at booting forever. I like to avoid reflashing / Factory resetting.
playfsx said:
is it possible somehow to do this with the stock recovery. I can boot with out magisk just fine, but if i enabled it stuck at booting forever. I like to avoid reflashing / Factory resetting.
Click to expand...
Click to collapse
figure it out.
turn off the phone
open a shell and type: adb wait-for-device shell magisk --remove-modules
boot with magisk enabled.
your phone should reboot and in the next boot you should have a clean magisk with out modules.
playfsx said:
figure it out.
turn off the phone
open a shell and type: adb wait-for-device shell magisk --remove-modules
boot with magisk enabled.
your phone should reboot and in the next boot you should have a clean magisk with out modules.
Click to expand...
Click to collapse
You just saved me an evening reflashing and setting up all **** again.