Develop Bugs

[Guide]Magisk Modules Disabler for Modules gone wrong

Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2239421
The first method was developed by osm0sis and removes magisk and all modules.
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
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3xl.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3xlRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291

Looking forward to this, Tulsa. Will be a real lifesaver and game changer.

sliding_billy said:
Looking forward to this, Tulsa. Will be a real lifesaver and game changer.
Click to expand...
Click to collapse
It's official. It works.

Tulsadiver said:
It's official. It works.
Click to expand...
Click to collapse
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.

sliding_billy said:
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.
Click to expand...
Click to collapse
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time

Tulsadiver said:
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time
Click to expand...
Click to collapse
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.

sliding_billy said:
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.
Click to expand...
Click to collapse
I pasted it again. Hopefully it works now.

Tulsadiver said:
I pasted it again. Hopefully it works now.
Click to expand...
Click to collapse
It works!

Thank you!!!!

Latest magisk canary added an adb command to remove modules if bootlopps happens ?

DvLAx3l said:
Latest magisk canary added an adb command to remove modules if bootlopps happens
Click to expand...
Click to collapse
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?

Tulsadiver said:
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?
Click to expand...
Click to collapse
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know ?

DvLAx3l said:
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know
Click to expand...
Click to collapse
Well, if it's an ADB fix, a person is going to have to, at the very least, flash boot.img (though probably system images depending on what you flashed), reboot without root. Enable the ADB mode, flash ADB commands, and reboot. Remove bad modules. Then, go back and root again.
Seems simpler to just flash the modded image-new.img, reboot with root, remove modules (with ADB if you like) and reboot.
Edit: what would be cool is an option to patch a boot.img in core-only mode, right from Magisk manager, where the other option is to patch the boot.img. All that would be needed on John's part is an edited init file in that option. That's the only difference.

Thanks for this! I could've really used this image a few times in the past...

Face_Plant said:
Thanks for this! I could've really used this image a few times in the past...
Click to expand...
Click to collapse
You and me both, buddy!

Got in to a bootloop situation with Bromite systemless webview module. I restored stock boot image and patched it with the latest canary build (the one with 'recovery mode' checked under advanced settings) and bootlooped again. I flashed this file, got in with magisk working, disabled the offending module, patched the boot image without recovery mode, then flashed the patched boot image and everything is up and running! Thanks for the help!

Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?

Jiggs82 said:
Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?
Click to expand...
Click to collapse
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.

Tulsadiver said:
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.
Click to expand...
Click to collapse
Yes I was able to open magisk but even if I uninstalled it I still had this weird bootlloop so before I saw this message I ended up just flashing factory 10 image clean this time just to be sure everything would flash/install successfully and luckily they did lol but thanks anyways and I will hold onto to these files for future references:good:

would the modded boot img that disables modules work for the pixel 3 as well?

[ROOT]Stock and Magisk patched boot images

Until TWRP is available for this device, root must be done by flashing patched boot image via fastboot. I'm still in the waiting period for the bootloader unlocking, but I prepared files in the meantime. Maybe someone will find them useful. Attached are stock boot and patched image with Magisk 21.1, EEA ROM version. Just unzip them and flash from fastboot.
Full version: V12.0.6.0.QJSEUXM_20201117
Edit: patched boot image reuploaded, the previous one didn't work (at least on my phone). This one has been tested and is working fine.

hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?

carabot said:
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
Click to expand...
Click to collapse
You can flash patched boot image directly, or just hotboot it (fastboot boot patched_image.img) and install Magisk from Magisk manager.

hello,
I did and at the moment everything is ok.
thanks
but there is a strange thing, Mixplorer, it does not change the permissions of the files, yet it has root permissions

I think the root is not perfect, I can't change the permissions of the files

carabot said:
I think the root is not perfect, I can't change the permissions of the files
Click to expand...
Click to collapse
Which files on which partition with what kind of permissions? RO partitions must be remounted as RW, but it's not always possible and using Magisk is usually a better and safer approach.

hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed

carabot said:
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
Click to expand...
Click to collapse
I keep my system partition RO so I can apply OTA updates, so I haven't tried it. You could try another app (for example Total commander), but you will be probably out of luck because of Android 10 limitation. Read more detailed explanation here https://android.stackexchange.com/q...m-partition-locked-to-read-only-in-android-10
I would suggest using Magisk module for system modifications.

hi
i tried other app manager like root explorer and es explorer, but the result is the same. i also installed magiskhideprops module, but my phone is not supported as fingerprint yet

What are you trying to achieve?

the terminal command to try to mount as RO would you know?

_mysiak_ said:
What are you trying to achieve?
Click to expand...
Click to collapse
full root to modify root files

carabot said:
full root to modify root files
Click to expand...
Click to collapse
I meant which files do you want to modify and why..
carabot said:
the terminal command to try to mount as RO would you know?
Click to expand...
Click to collapse
It's in the link above, along with explanation why it might be impossible to do.

I wanted to change the audio files regarding the volume, I wanted it a little higher

carabot said:
I wanted to change the audio files regarding the volume, I wanted it a little higher
Click to expand...
Click to collapse
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.

i read android 10 problem, would you recommend me to mount with termux, installing vim?

_mysiak_ said:
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
Click to expand...
Click to collapse
i don't know about magisk modules that can affect volume controls

carabot said:
i don't know about magisk modules that can affect volume controls
Click to expand...
Click to collapse
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.

_mysiak_ said:
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
Click to expand...
Click to collapse
unfortunately no, I edit the audio value of the system files, but I don't know how to build a module

Hello
the twrp for gauguin is online, to mount it i have to go back to the stock boot?

[ROM] LINEAGEOS [Android 11] [OFFICIAL] [Nightly]

I'm not sure why no one has posted this on here yet. I see the unstable google drive linked Android 11 Lineage but not the official download links and instructions...
i run this rom on my daily driver.
here is the link:
https://download.lineageos.org/walleye
the instructions are what you should foolow as they know alot more than me about all this but they say to temp flash the recovery, that has never worked for me.
WARNING!!!
IT IS NOT RECOMENDED BY LINEAGE TO USE GAPPS, AS SOME OF THEM WILL OVERWRITE/REMOVE OPTIMIZED LINEAGEOS SYSTEM APPS, AND REDUCE SECURITY/STABILITY!
THE SYSTEM WORKS JUST FINE WITHOUT GAPPS BUT IF YOU CHOOSE TO USE THEM LIKE I DO HERE IS THE INSTRUCTIONS I FOLLOW:
-----------------------------------------------------------------------------------------------------------------------
1. remove password on system
2. copy the downloaded system zip to sdcard
Google usb driver found here: https://developer.android.com/studio/run/win-usb
3. adb reboot-bootloader
google platform tools adb & fastboot found here: https://developer.android.com/studio/releases/platform-tools
4. fastboot boot [twrp]
do not allow modifications, do not change any settings and do not install twrp to recovery
Twrp found here: https://dl.twrp.me/walleye/
5. install [Lineage.zip]
sometimes you can sideload this pkg but others not so i just send it to the sdcard and install from there in twrp, ive had issues with usb 3.1 ports with system pgk but not with gapps.
6. reboot to bootloader and fastboot boot [twrp]
if you do not do step 6 the boot slot will not be correct for installing the gapps and will not be able to boot the system
7. adb sideload [gapps-core] and then adb sideload [addons] (without booting system before all gapps installed)
i get these from here: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/
i only do the core first, then i have a short batch file sideload all the addons i want from here:
https://sourceforge.net/projects/nikgapps/files/Releases/Addons-R/ choosing which ones i need because there is not always enough space.
the ones i sideload in order are named like this [NikGapps-Addon-11-*-signed.zip] below:
GBoard
Gmail
GoogleClock
GoogleContacts
GoogleDialer
GoogleMessages
GoogleCalculator
GoogleCalendar
GooglePhotos
Velvet
GoogleChrome
GoogleFi
GoogleTalkback
GoogleTTS
8. reboot system, and let boot up.
9. adb reboot-bootloader
enable usb debugging first
10. fastboot boot twrp
if you wanted to install twrp to system as recovery do it before magisk at this step.
11. adb sideload magisk.zip
magisk.zip is the magisk.apk, just rename the apk found here: https://github.com/topjohnwu/Magisk/releases
12. reboot
If magisk doesn't seem to want to work at this step:
open app while online, reboot, test again, if still no:
adb install -g [magisk.apk]
did i do something wrong? miss something? want me to take this down? make this better?
any feedback is welcome as this is mainly because i've spent many hours trying to figure all this out so i hope it helps someone.

The original post it's at Pixel 2 XL forum

Tony Ronaldo Matute said:
The original post it's at Pixel 2 XL forum
Click to expand...
Click to collapse
why, because the walleye and taimen kernel merge?
link please?

Solomon M said:
why, because the walleye and taimen kernel merge?
link please?
Click to expand...
Click to collapse
Here is the link
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
When will it be getting official and updated to December patch?
forum.xda-developers.com
Maybe you can ask permission to @Eamo5 for make thread in P2 session

kurokuroninja said:
Here is the link
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
When will it be getting official and updated to December patch?
forum.xda-developers.com
Maybe you can ask permission to @Eamo5 for make thread in P2 session
Click to expand...
Click to collapse
Oh! This is a duplicate. My apologies.
I'm not sure how to delete this. Also maybe they should post in the Walleye form instead of the other to help people find walleye related roms or rom info.
Whoever decided to put all walleye stuff with taimen just because they are both wahoo is dumb.
That's like saying let's put all the phone a with b just because some of it is the same. If they where the same then at least they would both be made by the same hardware manufacturer LG != HTC nor vice versa.

Solomon M said:
Oh! This is a duplicate. My apologies.
I'm not sure how to delete this.
Click to expand...
Click to collapse
Thread has been closed.

Question Root and/or Magisk with LineageOS 19.1

Sorry if I missed it. Anyone able to successfully Root, Magisk or TWRP the OP9p running lineageOS 19.1. loving 19.1 but TWRP fails to decrypt and not finding any other way to install Magisk or get root.

The process is the same as any other ROM based on Android 12. Extract boot.img, patch with Magisk, boot patched image, direct install.
Magisk/install.md at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com

Downloaded latest magisk25.1 apk, installed the apk, then renamed it to .zip. booted to LineageOS recovery and did adb sideload magisk.zip and it worked perfectly!

crowsnestitsupport said:
Downloaded latest magisk25.1 apk, installed the apk, then renamed it to .zip. booted to LineageOS recovery and did adb sideload magisk.zip and it worked perfectly!
Click to expand...
Click to collapse
Thanks for this. I've been having a hell of a time getting magisk to work on certain MIUI roms. With Lineage OS - it works! i guess this is my daily driver now.

marbss said:
Thanks for this. I've been having a hell of a time getting magisk to work on certain MIUI roms. With Lineage OS - it works! i guess this is my daily driver now.
Click to expand...
Click to collapse
Trying to do this as well. I'm getting an error though in Lineage Recovery on the ADB sideload. So my question is what is the point of renaming the APK to a .Zip if I have to sideload a different file from my PC. Should I be downloading the APK to my PC and renaming that as well or using the sourcecode.zip from github?

crowsnestitsupport said:
Downloaded latest magisk25.1 apk, installed the apk, then renamed it to .zip. booted to LineageOS recovery and did adb sideload magisk.zip and it worked perfectly!
Click to expand...
Click to collapse
This doesn't work for me. If you renamed the APK on your phone. What file did you sideload from your computer and what does one have to do with another?

NYFan said:
This doesn't work for me. If you renamed the APK on your phone. What file did you sideload from your computer and what does one have to do with another?
Click to expand...
Click to collapse
If you are trying to root using mentioned method, you 1)download Magisk app to pc 2)rename it by adding ".zip" then 3)boot to recovery, 4)update using adb, 5) "adb sideload magisk.apk.zip."

Shooter7889 said:
If you are trying to root using mentioned method, you 1)download Magisk app to pc 2)rename it by adding ".zip" then 3)boot to recovery, 4)update using adb, 5) "adb sideload magisk.apk.zip."
Click to expand...
Click to collapse
I completely understand the method but it doesn't work plain and simple lol. Not on Lineage recovery by sideloading. unless you were able to get TWRP on somehow and load the file from the device.

NYFan said:
I completely understand the method but it doesn't work plain and simple lol. Not on Lineage recovery by sideloading. unless you were able to get TWRP on somehow and load the file from the device.
Click to expand...
Click to collapse
Oh lol. I see. Yes I forgot some recoveries for some roms won't allow it for some reason. Easier to patch boot.img anyway I think

crowsnestitsupport said:
Downloaded latest magisk25.1 apk, installed the apk, then renamed it to .zip. booted to LineageOS recovery and did adb sideload magisk.zip and it worked perfectly!
Click to expand...
Click to collapse
I won't even begin to understand how this works, but it does.

grtgbln said:
I won't even begin to understand how this works, but it does.
Click to expand...
Click to collapse
I know. It just works! Thank you Magisk and lineage!

crowsnestitsupport said:
Downloaded latest magisk25.1 apk, installed the apk, then renamed it to .zip. booted to LineageOS recovery and did adb sideload magisk.zip and it worked perfectly!
Click to expand...
Click to collapse
Thank you so much! I've just installed Magisk v25.2 apk, then renamed it to .zip, booted to TWRP Recovery and installed the zip file from the SD Card! Cool!

A515f custom kernel Android 12

physwizz A515f S kernel version 3.1
For OneUI 4
( also works for GSIs)
Samsung securities disabled
More CPU governors
Conservative, On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
CPU:
Big 936 MHz - 2314MHz
Little 403MHz - 2054MHz
lz4 default compression added to zram
Installation
Post 2
Kernel
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
@physwizz

Installing physwizz custom kernels
INSTALL AT YOUR OWN RISK
I AM NOT RESPONSIBLE FOR ANY BRICKED PHONES
But I will help any well-mannered person to recover.
A. Preparation
1. Root the phone
2. Compress your patched boot.img to make boot.tar
3. Copy boot.tar to PC
B. Installation
Method 1
Install from twrp
Reboot to recovery
Backup boot and dtbo (if available)
Install kernel zip
Wipe both caches
Reboot
Method 2
Install kernel from terminal.
1. Download magisk module (magic-flash.zip) from https://github.com/Magisk-Modules-Alt-Repo/magic-flash
2. Install module and reboot.
3. Open terminal.
4. Navigate to folder containing kernel.zip.
Use
ls to list contents
and
cd to change directories
5. Type su
6. Type flash kernel_name.zip
7. Reboot
Method 3
Using ADB
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload file-name.zip
Method 4
Using boot.img
Install AIK Mobile from magisk modules
Use rootexplorer to access
/data/local/AIK-MOBILE
Add patched boot.img and tap unpackimg.sh
Exit the folder and return to see the files.
Edit the files (eg to add a new Image
rename Image to boot.img-zImage and insert in split-image folder)
Tap repackimg.sh
Rename new_image.img to boot.img
Compress boot.img to boot.tar
Copy boot.tar to PC
Reboot phone to download mode
Install boot.tar from odin
AIKLink
Physwizz Collection
Install from magisk modules Use rootexplorer to access /data/local/AIK-MOBILE Add boot.img or recovery.img and tap unpackimg.sh Exit the folder and return to see the files. Edit the files (eg to add a new Image rename Image to boot.img-zImage and insert in split-image folder) Tap repackimg.sh
t.me
C. Removal
Method 1
Reboot to recovery
Restore boot and dtbo
Reboot
Method 2.
Reboot phone to download mode
Install patched boot.tar from odin
@physwizz

Thank You Great work

hacker812c said:
Thank You Great work
Click to expand...
Click to collapse
I hope it works ok

Any feedback?

physwizz said:
Any feedback?
Click to expand...
Click to collapse
Pixel Expirence ROM v415 installed on OneUI 4(A515FOXM5FVE1). The phone heats up during simple tasks. The core panics and does not reset frequencies.

Brownly said:
Pixel Expirence ROM v415 installed on OneUI 4(A515FOXM5FVE1). The phone heats up during simple tasks. The core panics and does not reset frequencies.
Click to expand...
Click to collapse
Thanks

physwizz said:
Any feedback?
Click to expand...
Click to collapse
I use a translator. Thank you so much. There were no problems on One UI. Pixel experience plus ROM v415 does not heat up in simple tasks yet. File transfer is working (File Transfer/Android Auto mode). Aosp based ROM (GSI) is installed on top of One ui 4.1 without bootloop

Sm.one said:
I use a translator. Thank you so much. There were no problems on One UI. Pixel experience plus ROM v415 does not heat up in simple tasks yet. File transfer is working (File Transfer/Android Auto mode). Aosp based ROM (GSI) is installed on top of One ui 4.1 without bootloop
Click to expand...
Click to collapse
Good news

did anyone know why the battery discharge normal in OneUI, and when I install a GSI the battery discharge too fast?

f42in0 said:
did anyone know why the battery discharge normal in OneUI, and when I install a GSI the battery discharge too fast?
Click to expand...
Click to collapse
Many GSIs have various issues.
I only use debloated stock

UPD: Solved the overheating issue. The problem was not in the kernel. The core is stable, the MTP is working. Thank you!

Brownly said:
UPD: Solved the overheating issue. The problem was not in the kernel. The core is stable, the MTP is working. Thank you!
Click to expand...
Click to collapse
Good to know

Hello, is it compatible with ICBM Rom?

Nachopincha said:
Hello, is it compatible with ICBM Rom?
Click to expand...
Click to collapse
It should be.

Thanks sir, can you underclock more?

rezabahramnezhad said:
Thanks sir, can you underclock more?
Click to expand...
Click to collapse
Just use hktweaks to lower the maximums