[Guide] Magisk Modules Disabler for booting into Magisk core-only Mode

[ramsyst]

If `adb shell magisk --remove-modules` didn't fix the issue for you then you might be in the same boat I was and need to nuke all of Magisk's files in /data/adb.

Getting off topic for a Pixel thread, but here's the OnePlus 7T (hotdogb) image I made following my own instructions.

It's with an older Canary of Magisk so once you get it booting you should update to the latest Canary immediately.

Hi osm0sis, I'm having the same issue with Xiaomi Mi 9t. Could you also modify the boot image the Mi 9t. Or, is there an universal image I can use ?

 

[osm0sis]

Follow my instructions and make your own. I will not be making images for every single person that hijacks this thread.

Edit: In fact I'm unsubscribing, good luck to all!

 

[DanielF50]

Boot image uploaded 11-24-19
https://www.androidfilehost.com/?fid=4349826312261644469

Is there any chance you could provide a updated version of this, for the December update? Unfortunately, as with the Pixel 3 & Pixel 4, the December update seems to have screwed up Magisk & stop the device from booting (even when rolling back to Nov update), so I just need root to backup then wipe.

I can provide Dec boot img & patched version (if needed), I just don't have the ability to build this at the moment :good:

 

[Tulsadiver]

Is there any chance you could provide a updated version of this, for the December update? Unfortunately, as with the Pixel 3 & Pixel 4, the December update seems to have screwed up Magisk & stop the device from booting (even when rolling back to Nov update), so I just need root to backup then wipe.

I can provide Dec boot img & patched version (if needed), I just don't have the ability to build this at the moment :good:

This one is a little different. After you remove the modules you will need to delete the .disable_magisk file in the /cache folder before modules will work again.

https://www.androidfilehost.com/?fid=4349826312261654024

 

[DanielF50]

This one is a little different. After you remove the modules you will need to delete the .disable_magisk file in the /cache folder before modules will work again.

https://www.androidfilehost.com/?fid=4349826312261654024

Thanks dude, that worked perfectly - I didn't have to delete the disable file in the /cache (or data/cache) folder though, it was seemingly removed in between booting this .img & flashing the patched image.

 

[Tulsadiver]

Thanks dude, that worked perfectly - I didn't have to delete the disable file in the /cache (or data/cache) folder though, it was seemingly removed in between booting this .img & flashing the patched image.

Because the image was booted and not flashed. Makes sense.

 

[tanipat]

i got this value what is wrong please

downloading 'boot.img'...
OKAY [ 0.807s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)

 

[smithilberry]

i got this value what is wrong please

downloading 'boot.img'...
OKAY [ 0.807s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)

me too! did you ever figure this issue out? I am still having trouble getting out of a bootloop caused by a magisk module. I have dec patch and using the above mentioned core-only file. Anyone have any advice?

however I have pixel 4.

 

[adm1jtg]

me too! did you ever figure this issue out? I am still having trouble getting out of a bootloop caused by a magisk module. I have dec patch and using the above mentioned core-only file. Anyone have any advice?

however I have pixel 4.

Pixel 4 would use a completely different kennel

 

[Tulsadiver]

me too! did you ever figure this issue out? I am still having trouble getting out of a bootloop caused by a magisk module. I have dec patch and using the above mentioned core-only file. Anyone have any advice?

however I have pixel 4.

Go here
https://forum.xda-developers.com/pixel-4/themes/magisk-modules-disabler-booting-magisk-t3991739

 

[NeWCuLTKiNG]

I would like to thank you as this has saved me multiple times now. Haven't had a phone I could root for many years now and how I've missed it. Not having twrp makes things interesting and this saved the day many many times. Thank you

 

[Tulsadiver]

I would like to thank you as this has saved me multiple times now. Haven't had a phone I could root for many years now and how I've missed it. Not having twrp makes things interesting and this saved the day many many times. Thank you

Yes, without TWRP, a person needs to be creative at times and, like you said, it can make things interesting. Thus the occasional need for a recovery boot.img

 

[adm1jtg]

@Tulsadiver
Is there anyway to use the accent mod without root. Each month when I take the update the ONLY reason II dd magisk is to run your accent mod. I might also add the status bar and navbar mods but again hoping WITHOUT a root requirement. Could we mayve adb pusg the files or are they on like the system partition?

 

[Tulsadiver]

@Tulsadiver
Is there anyway to use the accent mod without root. Each month when I take the update the ONLY reason II dd magisk is to run your accent mod. I might also add the status bar and navbar mods but again hoping WITHOUT a root requirement. Could we mayve adb pusg the files or are they on like the system partition?

Root is required.

 

[Tulsadiver]

March boot fix images uploaded.

 

[AvisAile]

Can someone make magisk core only img for the dp2 of Android 11 ? I did not succeed and I prefer to have it before installing my modules (I doubt that they are all compatible with Android 11)
Thank you

 

[Tulsadiver]

Can someone make magisk core only img for the dp2 of Android 11 ? I did not succeed and I prefer to have it before installing my modules (I doubt that they are all compatible with Android 11)
Thank you

You will need to upload your magaisk_patched.img

 

[hanschke]

I try

1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg

but stuck. Attached my magisk boot.img from pixel 4 xl dp3 from android 11 and maybe I do a mistake and be happy to get a core image :fingers-crossed:

https://wetransfer.com/downloads/ce...6b2b679a7815f40fb95e3c3e20200429145743/7d7dc9

 

[Tulsadiver]

I try

1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg

but stuck. Attached my magisk boot.img from pixel 4 xl dp3 from android 11 and maybe I do a mistake and be happy to get a core image :fingers-crossed:

https://wetransfer.com/downloads/ce...6b2b679a7815f40fb95e3c3e20200429145743/7d7dc9

Try this.
https://www.androidfilehost.com/?fid=4349826312261786839

 

[zgfg]

Down towards the bottom of op under downloads
https://forum.xda-developers.com/showthread.php?t=2073775

So I tried to make Core Only image for my Xiaomi Mi 9T, MIUI 11, Android 10, based on my Canary 20407 patched image - but it didn't work (see below)

---

Followed the guide from OP posts (various Pixel guides):
https://forum.xda-developers.com/showpost.php?p=80408781&postcount=1
https://forum.xda-developers.com/showpost.php?p=80408801&postcount=1
https://forum.xda-developers.com/showpost.php?p=80657663&postcount=1
and used Android Image Kitchen for Windows from (thank you for pointing directly to):
https://forum.xda-developers.com/showpost.php?p=36067074&postcount=1

It's not really complicated, took me first time 15 minutes, and just few minutes for subsequent tests (incl. flashing and rebooting)

So thank you and to @osm0sis for this nice method(s)

First of all, I don't have a bootloop when booting to Magisk, there is TWRP for my device (supporting the encrypted /data) and
adb shell Magisk -V
works correctly hence I could always fix a Magisk bootloop through TWRP or by adb if needed

---

Unpackimg magisk_patched.img - success.
I copied overlay.d from overlay.dcoreonly1.zip to ramdisk.
Repackimg - success.
Flashed image-new.img but it still booted to Magisk with all modules

Indeed, I checked in /cache but didn't find .disable_magisk file.
To test, I copied that empty .disable_magisk manually to /cache, rebooted and Magisk Manager properly showed the Core Only mode

I also tested with AIK:
Cleanup
Unpacking image_new.img
and it was properly unpacked, containing the overlay.d in ramdisk

I played more with init.resetmagisk.sh script in sbin/overlay.d, by testing to similarly put empty disable file to /data/adb/modules/adb-ndk but it did not help to disable my ADB & Fastboot NDK module

Finally, by modifying overlay.d from overlay.dremove1.zip I tried to remove /data/adb/modules/adb-ndk, but again it did not remove that module

Not sure if I did something wrong, or something changed with Magisk Canary 20407 or could it be (I don't believe) related to the fact that my Magisk Manager is hidden...

One of my image_new.img test images:
https://mega.nz/file/B98HiBxB#3uu-cZWDcBzbG-e2SXcKZHTZ7pr8T3FtB9r-1QctnSU

EDIT:
Now I did the same for my patched ramdisk image for Huawei P9, EMUI 8, Android 8 - and here, P9 properly reboots to the Core Only mode.
Also based on Canary 20407

I made all the same, except unpacking/repacking image for different device

Hence it may depend on device (or Android version - but I think you also use Q on Pixels and it works for you)