Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Can you not uninstall/flash modules through magisk?
Levi4cyber said:
Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Click to expand...
Click to collapse
Not sure if it still works, but you should be able to go in through safe mode to delete magisk. Not sure about just modules, but it would get you out of a hole anyway.
hallo dare said:
Not sure if it still works, but you should be able to go in through safe mode to delete magisk. Not sure about just modules, but it would get you out of a hole anyway.
Click to expand...
Click to collapse
Yes, that's a really good suggestion, I was in that situation couple of days ago, force reboot to safe mode, you don't have to do anything in safe mode, then just do a normal system boot and all modules should be disabled and just uninstall them before your next reboot.
Levi4cyber said:
Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Click to expand...
Click to collapse
if you are getting bootloops and in a jam, use method 2 (adb) to remove modules, this method saved me when a module caused a BL situation, only downside is it will remove all modules.
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
oscarmaldonado said:
Yes, that's a really good suggestion, I was in that situation couple of days ago, force reboot to safe mode, you don't have to do anything in safe mode, then just do a normal system boot and all modules should be disabled and just uninstall them before your next reboot.
Click to expand...
Click to collapse
For some unknown reason my modules are still installed after reboot in save mode.
Am I doing something wrong?
netgar said:
For some unknown reason my modules are still installed after reboot in save mode.
Am I doing something wrong?
Click to expand...
Click to collapse
Hey there bud, what exactly are you trying to do, a bad module creating a boot loop in you phone?
oscarmaldonado said:
Hey there bud, what exactly are you trying to do, a bad module creating a boot loop in you phone?
Click to expand...
Click to collapse
I did before so I had to basically reinstall all my apps from scratch.
I installed bootloop saver module and I hope I will be safe once any not compatible module will cause bootloop.
I'm not safe since after reboot from save mode all my modules are still active and installed.
use this command in debugging mode enabled
Code:
adb wait-for-device shell magisk --remove-modules
Related
Hello!
I installed the new Android 11 stable and everything went well. I installed OTA and was able to flash a modified boot.img for root. I then wanted to re-enable the modules I turned off for the update. That's when I got stuck in a boot loop. I'm not sure the correct procedure for re-enabling the modules but immediately after restarting to let the modules take effect I ran into a boot loop.
To remedy this I tried re-flashing the modified boot image, which always leads to a boot loop.
I have also tried the "adb shell magisk --remove-modules" command during the boot loop but that immediately brings me to the fastboot screen with the reason "Invalid boot slot" and then it stays there until I flash another boot.img.
I've tried unpacking and repacking a magisk_patched.img with both the Pixel 3a XL's "core only" and "remove modules" but those lead to a fastboot error where it doesn't like the image and won't boot from it.
If I flash the stock Android 11 boot.img the phone boots up fine but doesn't have root obviously. I am also using the newest (30.0.4) version of android platform tools.
I was wondering if anyone else had some insight as to what I'm doing wrong or where to go from here?
Thank you in advance
scyther3989 said:
Hello!
I installed the new Android 11 stable and everything went well. I installed OTA and was able to flash a modified boot.img for root. I then wanted to re-enable the modules I turned off for the update. That's when I got stuck in a boot loop. I'm not sure the correct procedure for re-enabling the modules but immediately after restarting to let the modules take effect I ran into a boot loop.
To remedy this I tried re-flashing the modified boot image, which always leads to a boot loop.
I have also tried the "adb shell magisk --remove-modules" command during the boot loop but that immediately brings me to the fastboot screen with the reason "Invalid boot slot" and then it stays there until I flash another boot.img.
I've tried unpacking and repacking a magisk_patched.img with both the Pixel 3a XL's "core only" and "remove modules" but those lead to a fastboot error where it doesn't like the image and won't boot from it.
If I flash the stock Android 11 boot.img the phone boots up fine but doesn't have root obviously. I am also using the newest (30.0.4) version of android platform tools.
I was wondering if anyone else had some insight as to what I'm doing wrong or where to go from here?
Thank you in advance
Click to expand...
Click to collapse
Sounds like an incomparable magisk module. You need to isolate which module is the problem and leave it disabled or look for an updated version
adm1jtg said:
Sounds like an incomparable magisk module. You need to isolate which module is the problem and leave it disabled or look for an updated version
Click to expand...
Click to collapse
I would be fine with this but I have no idea how to disable the modules without root. And the adb shell isn't working for me either.
scyther3989 said:
I would be fine with this but I have no idea how to disable the modules without root. And the adb shell isn't working for me either.
Click to expand...
Click to collapse
I think it's in the themes forum here but they're is a magisk module disabler. They're are also other utilities to do so.
adm1jtg said:
I think it's in the themes forum here but they're is a magisk module disabler. They're are also other utilities to do so.
Click to expand...
Click to collapse
The only things I've seen for Module disablers are...
the adb shell magisk module disable
the patched "core only" and "module remover" repacked boot images
magisk uninstaller that requires a recovery to run it
I've tried the first two and I can't find a TWRP that works with a Pixel 3a XL running Android 11.
scyther3989 said:
The only things I've seen for Module disablers are...
the adb shell magisk module disable
the patched "core only" and "module remover" repacked boot images
magisk uninstaller that requires a recovery to run it
I've tried the first two and I can't find a TWRP that works with a Pixel 3a XL running Android 11.
Click to expand...
Click to collapse
And you won't find one. Twrp only works on Android 9 or older. Starting with 10 the partitions are dynamic and to date twrp can't handle them at all. Since we haven't had a working twrp in over a year i wouldn't get my hopes up.
adm1jtg said:
And you won't find one. Twrp only works on Android 9 or older. Starting with 10 the partitions are dynamic and to date twrp can't handle them at all. Since we haven't had a working twrp in over a year i wouldn't get my hopes up.
Click to expand...
Click to collapse
Yeah I'm hoping for some kind of insight on how to disable modules without root or maybe some new patch I haven't tried.
Try booting into safe mode, this is supposed to disable all modules. When you boot back into regular mode they should still be disabled and you can delete or update the bad one.
Sent from my SM-T860 using XDA-Developers Legacy app
rifraf1 said:
Try booting into safe mode, this is supposed to disable all modules. When you boot back into regular mode they should still be disabled and you can delete or update the bad one.
Sent from my SM-T860 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Wow this actually worked!!
For anyone having a similiar issue:
I flashed the magisk_patched.img from Android 11 and let it go back into it's bootloop
As soon as the booting animation started I pressed volume UP and volume DOWN and it booted into safe mode
I restarted once I successfully made it into safe mode
The modules causing the bootloop were disabled and I am now able to have root in Android 11
Thank you @rifraf1
Hi guys,
just updated my op9p to the newer oos 11.2.5.5LE15BA and repatched with magisk, everything gone fine.
I re-deleted some google system app with sdmaid that i had debloated yet before this oos update.
Once i re-install vanced apps i detached it using magisk module from termux, rebooted and now i'm in stuck with boot loop.
Tried to clear cache from recovery but still keep in stuck.
What can i have corrupted?
Can i solve it reflashing stk boot.img?
Thanks in advance
Hunter_87 said:
Hi guys,
just updated my op9p to the newer oos 11.2.5.5LE15BA and repatched with magisk, everything gone fine.
I re-deleted some google system app with sdmaid that i had debloated yet before this oos update.
Once i re-install vanced apps i detached it using magisk module from termux, rebooted and now i'm in stuck with boot loop.
Tried to clear cache from recovery but still keep in stuck.
What can i have corrupted?
Can i solve it reflashing stk boot.img?
Thanks in advance
Click to expand...
Click to collapse
you can try booting in safe mode, this will disable all magisk modules
Same issue tring to boot into safe mode
I just posted a tutorial to use adb to remove magisk modules for a situation just like this. worth to check it out if you can't get it done via safemode
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
there might be the same tutorial on xda but i had this copied to my clipboard
Scary that a detach module could cause bootloop...
Hunter_87 said:
Same issue tring to boot into safe mode
Click to expand...
Click to collapse
Did you able to make it work?
Nope, same result tring to follow thirtythr33 tips..
Really don't undestand what i did it wrong to get this problem.
Nothing.. i had to do an hard reset!! Thanks to all anyway..
Hunter_87 said:
Nope, same result tring to follow thirtythr33 tips..
Really don't undestand what i did it wrong to get this problem.
Click to expand...
Click to collapse
Have you removed all modules via abd?
netgar said:
Have you removed all modules via abd?
Click to expand...
Click to collapse
Nope, i tried with adb command as reported on linked guide but nothing happen and i receive just an error on cmd for too waitings.
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!
Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?
posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.
thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.
thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.
Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you
I tried a mod from here but it put my phone into a bootloop, I think it was for android 9.
how did you install it, via magisk, recovery or others?
JuanTamqd21 said:
how did you install it, via magisk, recovery or others?
Click to expand...
Click to collapse
It was either magisk or recovery
MikeRWK said:
It was either magisk or recovery
Click to expand...
Click to collapse
How to Uninstall a Magisk Module and Magisk zip from a Rooted Device
You might have often come across a boot loop on your smartphone due to a specific Magisk Module. This is quite a common problem as sometimes, a cific
www.getdroidtips.com
JuanTamqd21 said:
How to Uninstall a Magisk Module and Magisk zip from a Rooted Device
You might have often come across a boot loop on your smartphone due to a specific Magisk Module. This is quite a common problem as sometimes, a cific
www.getdroidtips.com
Click to expand...
Click to collapse
I'm long after wiping the phone and starting fresh. I just need to disable the camera sound
Anyone use the magisk bootloopsaver module with our phones? Wanted to make sure it wouldn't mess anything up before I installed it lol
Veid71 said:
Anyone use the magisk bootloopsaver module with our phones? Wanted to make sure it wouldn't mess anything up before I installed it lol
Click to expand...
Click to collapse
Using it on OOS11. Saved me when one of the recent Magisk Canary releases had conflicts with modules and caused bootloops, it's a Godsend.
Basically if you bootloop because of modules, the boot animation stays on for like a minute, then the device restarts with all modules disabled (except for the Magisk Bootloop Saver module). You will need to re-enable them manually afterwards (and subsequently rebuild substratum themes etc).
Fishawy said:
Using it on OOS11. Saved me when one of the recent Magisk Canary releases had conflicts with modules and caused bootloops, it's a Godsend.
Basically if you bootloop because of modules, the boot animation stays on for like a minute, then the device restarts with all modules disabled (except for the Magisk Bootloop Saver module). You will need to re-enable them manually afterwards (and subsequently rebuild substratum themes etc).
Click to expand...
Click to collapse
Awesome thanks man!
Magisk has this by default for a long time now. pressing down vol key on boot will boot into safe mode with all modules disabled
Try this.
JohnFawkes said:
Magisk has this by default for a long time now. pressing down vol key on boot will boot into safe mode with all modules disabled
Click to expand...
Click to collapse
True, but this module makes it a normal boot not into safe mode.
TheKnux said:
Try this.
Click to expand...
Click to collapse
Will it work on a12l?
Tazist said:
Will it work on A12l?
Click to expand...
Click to collapse
@Tazist Try it. Sorry, the xda app is ****ing stupid.
Does anyone have a fresh copy of this? I keep getting an unzip error. Is development dead?
Droid_Nut said:
Does anyone have a fresh copy of this? I keep getting an unzip error. Is development dead?
Click to expand...
Click to collapse
Why not use magisk delta this have a bootloop protect build in
Thank you, should I patch the boot image or not?
ChrisFeiveel84 said:
Why not use magisk delta this have a bootloop protect build in
Click to expand...
Click to collapse
Tell us more, is it a module, or a version of Magisk?
Droid_Nut said:
Thank you, should I patch the boot image or not?
Click to expand...
Click to collapse
For magsik delta ?
Droid_Nut said:
Tell us more, is it a module, or a version of Magisk?
Click to expand...
Click to collapse
Is a magsik version from huskydg with build in bootloop protect and magisk hide
So its a fork of Magisk. https://magiskzip.com/magisk-delta/
ChrisFeiveel84 said:
For magsik delta ?
Is a magsik version from huskydg with build in bootloop protect and magisk hide
Click to expand...
Click to collapse
Huskydg also made the bootloop module, so patch it for either?
Actually never mind I just patched it on 3 phones with no problem.
As far as Delta, the newest Lsposed requires Zygisk, so you might find that you will need that anyways as more modules go that route. Any ways, I will give Delta try some time.
ChrisFeiveel84 said:
For magsik delta ?
Is a magsik version from huskydg with build in bootloop protect and magisk hide
Click to expand...
Click to collapse
I installed Delta, can I now turn off the bootloop module?
Droid_Nut said:
I installed Delta, can I now turn off the bootloop module?
Click to expand...
Click to collapse
No then when you enable it on magsik this isnatlled this modul
Few days ago, magisk brought update. I updated and restarted. 1st restart was ok, but 2nd restart after updating youtube revanved module caused bootloop. I had to flash firmware in, data gone. Will this module really help me if it happens next time or i should use TWRP. TWRP is not available for my device BTW. I will try to build it as it's open source.