is there a magisk boot img with modules disabled?. i have a boot loop and need a boot img with it disabled.
prgopala said:
is there a magisk boot img with modules disabled?. i have a boot loop and need a boot img with it disabled.
Click to expand...
Click to collapse
I responded in your other thread. Generally multi-posting isn't recommended, if someone can assist they'll do so.
Related
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
! Boot img patched by other programs
! please restore stock boot img
Click to expand...
Click to collapse
I don't have any custom rom, i'm actually oos 5.0.3. I first try to root but dm-verity was triggered and then followed all the steps to disable it.
Any solutions?
Nube420 said:
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
Click to expand...
Click to collapse
Magisk is a root zip. It sounds like you are flashing SuperSU and Magisk. You can only use one or the other, not both!
Reflash stock ROM (or at least stock boot.img). Then flash Magisk. That's it.
Getting the error message that boot.img is modified is normal and expected in your case. SuperSU patched the boot image. Now Magisk is looking for the stock image to patch, and finding a patched one.
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
whoiam55 said:
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
Click to expand...
Click to collapse
You can remove a module via recovery (mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img to disable magisk then you can remove the module from the manager itself.
Sent from my MI 5 using Tapatalk
teddy0209 said:
(mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img
Click to expand...
Click to collapse
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
whoiam55 said:
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
Click to expand...
Click to collapse
You can find the latter in the download section, the first on the compilation of modules... Your unpatched boot.img/stock boot.img, you can find it inside your room zip, from your twrp backup if you did backup prior to installing magisk. Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Sent from my MI 5 using Tapatalk
teddy0209 said:
Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Click to expand...
Click to collapse
So your are saying that if it stuck on boot then I can go back to TWRP, select /data/boot.img and flash it to boot partition?
One more think suppose I install *X* module and it succeed, then I install *Y* module and it failed to boot. Now I flashed boot.img as written above will it contain *X* module or just a fresh boot.img?
Thanks again for the reply.
Hello
My Device is running on Stock Android Q BN 11.0.5.0
Recently i installed magisk in my device (keeping OTA).
When i install Magisk Module for Internal audio recording and reboot device it was stucked in bootloop.
Then i flashed stock boot img
After flashing i reboot the device and it is rebooted successfully. But Magisk and Root Access has gone.
Then after i again flash Magisk patched img created by Magisk installer but this time it is again stucked in bootloop.
I tried to flash zip with temporary Twrp but problem is not solved.
Currently i dont have Magisk installed.
Please Help Me to gain root access again
Thank you.
Please reply or DM me https://t.me/adarsh_ad007
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
thank you bro it diid not work. i tried but not working
Aerobatic said:
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
Click to expand...
Click to collapse
not working
adarsh.ad007 said:
not working
Click to expand...
Click to collapse
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Aerobatic said:
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Click to expand...
Click to collapse
I did everything what you said but problem is still there.
adarsh.ad007 said:
I did everything what you said but problem is still there.
Click to expand...
Click to collapse
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Aerobatic said:
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Click to expand...
Click to collapse
Thanks for you support and attention dear.
Actually i flashed PE ROM and then install magisk. Now it works.
And i was booting correct patched img.
I created it via magisk manager myself.
adarsh.ad007 said:
..And i was booting correct patched img. I created it via magisk manager myself.
Click to expand...
Click to collapse
Maybe there was still something that skipped your attention. Pls look at scenario:
- patch stock boot image using MagiskManager with, let us say, Magisk 20.1; boot this patched image, make direct install - root got;
- update Magisk to. e.g., 20.3 installing Magisk-v20.3(20300).zip (root got, everything ok);
- play with new Magisk modules, install wrong version, get bootloop;
- make some otherwise correct steps, like reflashing stock boot;
- finally try to get root with boot image previously patched by Magisk 20.1.
Result: no root, MagiskManager does not accept Magisk 20.1., it expects boot image patched with 20.3
Anyone else the latest Magisk update causes Bootloop when installing modules?
use 24.1, is perfect
OK THANKS, I HOPE FUTURE UPDATES WILL WORK CORRECTLY ON THE DEVICE
a question: do u have repatched boot.img with new magisk version? you must do it
wetito said:
use 24.1, is perfect
Click to expand...
Click to collapse
I'm still using v23 .. just to be sure lol ! but now i know 24.1 is good thank you!
PonchoNz said:
Anyone else the latest Magisk update causes Bootloop when installing modules?
Click to expand...
Click to collapse
Use Magisk 24.3 and patch the boot file -> Flash the boot file in fastbootd
Done.
i have flashed 24.1 using fastboot. for 24.3 fastbiitd is necessary? i ask just i case in the future i will decide update to latest version
wetito said:
a question: do u have repatched boot.img with new magisk version? you must do it
Click to expand...
Click to collapse
Yep but update it by TWRP
nguadien said:
Use Magisk 24.3 and patch the boot file -> Flash the boot file in fastbootd
Click to expand...
Click to collapse
Done I did it too but when I install a Module called NFS Injector or Magnetar when I restart the device it gives bootloop
PonchoNz said:
Done I did it too but when I install a Module called NFS Injector or Magnetar when I restart the device it gives bootloop
Click to expand...
Click to collapse
Then the problem is the modules you installed, not "latest Magisk update" like you stated.
Not all modules work for all devices, each device reacts to modules very differently, so boot loop caused by modules should not be mistaken for the whole Magisk.
Device ZTE Quest 5, Z3351S
Android version: 9
Magisk version name: 831a398b
Magisk version code: 25206
After flashing the patched `recovery.img`, trying what the guide says (using recovery keys) will not boot Magisk. Even booting the image file itself just results in the phone refusing to boot until it reboots. Anyone know what is happening?
you do it wrong, flash boot.img with fastboot
I've done that and none of my connections will work. Magisk also says that I don't have boot ramdisk. The first time I did do the boot image, it wasn't fully rooted and root apps couldn't do much.