Database Info

[OOS 5.1.5 | 5.1.6 | 5.1.7 | 5.1.8 | SafetyNet OK] Root without TWRP

Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this procedure before doing it! YOU are choosing to make these modifications.
Click to expand...
Click to collapse
OP6 rooting without TWRP
Checklist before preceed:
Working Fastboot
Be on software OOS 5.1.5 | 5.1.6 | 5.1.7 | 5.1.8
Unlocked bootloader (Instruction here, but remember to enable OEM Unlocking first)
Funk Wizard said:
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Click to expand...
Click to collapse
WARNING:
Please double check that you have unlocked bootloader!
A few users has reported that instaling magisk with locked bootloader or wiping phone (using stock recovery) with patched boot.img can soft brick your phone! Please avoid doing this for now. If you've already done this and you are stuck with only fastboot working please follow this post https://forum.xda-developers.com/showpost.php?p=76608874&postcount=31 to restore your device to working state. Thank's to @SaiBork for more detailed instructions available here https://forum.xda-developers.com/showpost.php?p=76632484&postcount=82
Rooting process:
Make sure that you have UNLOCKED BOOTLOADER. DO NOT attempt to patch boot.img using Magisk Manager without unlocked bootloader because it WILL CAUSE SOFT BRICK!!!
Boot device using patched boot.img.
For OOS 5.1.5 it can be downloaded [here]
For OOS 5.1.6 it can be downloaded [here]
For OOS 5.1.7 it can be downloaded [here]
For OOS 5.1.8 it can be downloaded [here]
It can be also patched manually (see bottom of this post).
To do this you need working fastboot. Fire up your cmd/terminal and cd to directory where you've downloaded/placed patched boot image. When you are in correct directory just type in cmd/terminal:
Code:
fastboot boot patched_boot_magisk1642_518.img
(check if img filename in command is exactly same as name of downloaded boot img) The phone should boot to Android.
Once the phone has booted install Magisk Manager app and open it. It can be downloaded here or here.
Magisk Manager App should show that your phone is rooted - but at this stage it's just temporary, until next reboot (nothing flashed yet).
Go to settings and Tap on "Update channel" and change it to Beta.
Go back to Magisk main screen and make sure that "Preserve force encryption" and "Preserve AVB 2.0/dm-verity" are checked!
Tap on "Install" and select "Direct Install (Recommended)".
Wait until boot.img is patched and flashed and reboot your device when prompted to do so.
After boot there aren't any error messages shown before (or after) entering PIN code, unlike when rooting using other methods.
To check SafetyNet status just open Magisk Manager once again and tap on "Tap to start SafetyNet check". It should be all green.
wOOt wOOt you just got rOOt!
Video showing rooting process:
XDA user @GizmoFreak has made a video showing the whole procedure for 5.1.5! Thank you very much.
How to do an OTA update preserving root
Install OTA. It will be installed on the inactive slot. Do not restart your OP6 when installation finishes.
Start Magisk Manager app.
Tap on Install.
Tap on Install to Second Slot (After OTA).
Reboot your device.
Check if you got root and if safety net checks are passed.
How to extract from OTA and manually patch stock OOS boot.img using Magisk Manager:
Install python3 and PIP manager on your system .
Use pip to install "protobuf" module:
Code:
pip3 install protobuf
Download payload_dumper.py and update_metadata_pb2.py from this gist https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15 and save them in one directory.
Download full update zip with OOS (containing payload.bin). It can be downloaded from this great thread by @Titokhan
Extract payload.bin from update zip to same directory where payload_dumper.py is located.
Use payload_dumper.py to extract original boot.img
Code:
python payload_dumper.py payload.bin
After a while you should have all img's included in payload.bin dumped in your working directory.
Install Magisk Manager app on your OP6.
Place that dumped boot.img on your phone storage.
In Magisk Manager app tap install, and select "Patching boot image file". Select boot.img that you've just uploaded to your phone.
Magisk Manager will patch boot.img and save it on Phone's internal storage in "MagiskManager" directory (file called "patched_boot.img").
Download this patched file to your computer and just use it to boot using fastboot

stock recovery img please

Hi and thx for the Thread. Maybe more Details in your Guide would be nice and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).

NeoNecOP6 said:
Hi and thx for the Thread. Maybe more Details in your Guide would be nice and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).
Click to expand...
Click to collapse
How do they know if you manipulate the CPU frequency?

Thanks, I'd like to try patching the boot.img myself - how did you extract it from the device without root?
I also couldn't figure out how to extract it from the update files OP provided (since they are all A/B updates only containing a payload.bin)

liver20 said:
stock recovery img please
Click to expand...
Click to collapse
There is no separate recovery partition. Recovery in boot.img, as all A/B devices.

NeoNecOP6 said:
and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).
Click to expand...
Click to collapse
I know but it's just a disclaimer
Kaeltis said:
Thanks, I'd like to try patching the boot.img myself - how did you extract it from the device without root?
I also couldn't figure out how to extract it from the update files OP provided (since they are all A/B updates only containing a payload.bin)
Click to expand...
Click to collapse
You can extract it from A/B update using python tool called payload_dumper.py Check this post for more information https://forum.xda-developers.com/showpost.php?p=76598704&postcount=80

jacdelad said:
How do they know if you manipulate the CPU frequency?
Click to expand...
Click to collapse
if that's why your smartphone broke down. Any company can find out if the device has been rooted.

http://tinypic.com/view.php?pic=2dquejq&s=9
Rooted
Thanks op

This worked perfectly for me. No vendor image issues either. No flashing (that's cool!). Thanks! I saw you posted how you did it but it'd be cool if you could add it to this thread so people can learn.
Thanks!

b1czu said:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this procedure before doing it! YOU are choosing to make these modifications.
For all interested in rooting I suggest to do it this way:
Checklist before preceed:
- Working Fastboot
- Unlocked bootloader
- Be on software OSS 5.1.5!!
1. Boot patched boot.img that can be downloaded here [https://drive.google.com/open?id=1BIH5sGfMADfhWIAfQDsiw4f-UI_1WvqX]
To do this you need working fastboot and cd to directory where you've downloaded patched boot image. When you are in correct directory just type in cmd/terminal:
Code:
fastboot boot patched_boot_magisk1642.img
The phone should boot to Android.
2. Once phone is booted up install Magisk Manager and open it.
3. It should show that you have root - but at this stage it's just temporary, until next reboot (nothing flashed yet).
4. Go to settings and Tap on "Update channel" and change it to Beta.
5. Go back to Magisk main screen and make sure that "Preserve force encrypotion" and "Preserve AVB 2.0/dm-verity" are checked!
6. Tap on "Install" and select "Direct Install (Recommended)"
6. Reboot
After boot there are no any Error messages before entering PIN code.
Just open magisk manager once again and tap on "Tap to start SafetyNet check". It should be all green.
wOOt wOOt you just got rOOt!
Click to expand...
Click to collapse
Thanks for this. Probably a dumb question. But, does this need to be undone when TWRP comes out? Is there a way to revert back?
Thanks again.

mcdavid said:
But, does this need to be undone when TWRP comes out?
Click to expand...
Click to collapse
No, you don't need to undone this. Flashing magisk root using TWRP recovery would lead to same end-effect.
mcdavid said:
Is there a way to revert back?
Click to expand...
Click to collapse
Yes. You can flash back stock OOS 5.1.5's boot.img, because nothing other was modified. Link to download STOCK boot.img for OOS 5.1.5 https://drive.google.com/open?id=1RPQZj6HQxNNdJiMrAjtkxncH3PLBTZp_
To revert you need fastboot tool:
Code:
fastboot flash boot boot.img
And that's it. You're again rootles on stock 5.1.5's boot.img.

thanks man!!!
Op6 rooted and ready for me!

OnePlus 3: TWRP, Root & Cyanogenmod before most users got the device,
OnePlus 5: Unofficial TWRP,
And OnePlus 6: Root without any custom recovery....
Thank you!

Wow thank you for this, can't live without root and I get my OP6 tomorrow so this is great

i installed patched boot file for oss5.1.3 using boot file for oss5.1.3. my question is when i update oss to latest for now i.e oss5.1.5 will i need to re root it? or it will stay rooted? and i won't get stuck at installing the update too right? considering its gonna be full updates now(no partial updates).

dynamic_4444 said:
i installed patched boot file for oss5.1.3 using boot file for oss5.1.3. my question is when i update oss to latest for now i.e oss5.1.5 will i need to re root it? or it will stay rooted? and i won't get stuck at installing the update too right? considering its gonna be full updates now(no partial updates).
Click to expand...
Click to collapse
When you update, boot.img will be overwritten with 5.1.5's one and you'll have to repeat the process again.
@b1czu, thank you very much! Rooted flawlessly .

Worked like a charm! I'm grateful for my fellow impatient people. Time to unlock the Oneplus 6's true potential!

I try it to night

Thanks man, so far it works great!

[Guide] Magisk manager installation on Mi CC 9

If you install twrp recovery then it is very easy to install magisk manager.
just go on your twrp recovery mode
Select advanced and select install root.
Reboot your Phone .
See magisk manager install successfully.
Any help about mi cc9 magisk manager just coment here. I will be ready for replay just like you want.
.
Or Download this file and install through twrp recovery.
Latest stable magisk manager zip [flash file]
https://drive.google.com/file/d/1j6EWKPt1ZNzW7QgtILkgW5xphCzzcKNH/view?usp=drivesdk
Magisk manager apk
https://drive.google.com/file/d/1Hzvi5f2bZcUPyzWx-ETfqZanQjLCJHGq/view?usp=drivesdk

Lijlp0/02plppp000p7 lu6pppp?0lpl
Ul u?????//6000

I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.

eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
I need unlock BL to flash the modded boot.img?

RazrBR said:
I need unlock BL to flash the modded boot.img?
Click to expand...
Click to collapse
Yes, first unlock BL to be able to enter fastboot mode. Apply to unlock bootloader with Mi account, please follow guide on how to unlock the bootloader.

eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
Hi. Did you do these passages also on MIUI 12? Because I installed Magisk app, but it showed Ramdisk: no, and now I don't know if I should install it in recovery partition or not

there's twrp and orangefox that can be used for cc9 meitu/vela. Unlock bootloader, enable adb, flash custom recovery by fastboot. After that use custom recovery to install magisk. I'm sorry I don't use cc9 anymore since last weekend because miui12 notification and permission is too aggressive, have to restart app everytime so that can get contact info.

Android 10 Root Guide?

So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?

Magisk working on final android 10
oscar1823 said:
So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Click to expand...
Click to collapse
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.

Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.

alliance1975 said:
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
Click to expand...
Click to collapse
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.

sic0048 said:
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
Click to expand...
Click to collapse
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed

omiCar said:
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
Click to expand...
Click to collapse
I installed it while still Pie.

sic0048 said:
I installed it while still Pie.
Click to expand...
Click to collapse
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho

I made the mistake of having Magisk set to beta instead of canary when I did the Magisk OTA update, but no issues with the regular boot image patching method.
Simply follow the guide linked above and you should be fine.

omiCar said:
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
Click to expand...
Click to collapse
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.

Got it to work.
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
sic0048 said:
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
All you really need to do is flash Pie back on the phone and start the process over. I realize that seems like a long process, but it really isn't that hard. Just be sure to backup any important data off phone before you start because installing Pie should wipe the phone.
Click to expand...
Click to collapse
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.

darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Thanks for the response, I will download the Andriod 10 and flash it into my phone, hopefully it will work

darkmeridian said:
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
I agree that normally that would work.
However, simply replacing the boot.img file doesn't completely uninstall Magisk. That is why there is a Magisk Uninstaller zip that can be used with TWRP. It normally isn't needed, but it is a great way to completely wipe Magisk if you are having issues. Obviously that isn't an option on Android 10 currently because TWRP doesn't work yet.
Hopefully he doesn't have any issues moving from stable to Canary Magisk versions. But if he does, he will likely have to flash a full factory image to completely wipe the phone and reinstall everything without traces of Magisk

flow5673 said:
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Click to expand...
Click to collapse
This worked for me. Thanks

darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?

If you experience manager telling you that Magisk isn't installed after installing it through fastboot, uninstall manager and reinstall it. Deleting app data won't do the trick. Strange bug but I encountered that in the Q beta

Anyone else having issues with the canary build? I hard reboot and it shows magisk not installed, then I reboot again and its installed again?
Also Android Q is hella laggy for me?
Currently doing a full fresh image install

Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4

alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.

Velcorn said:
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Click to expand...
Click to collapse
For now I disabled the unused apps. Similar behavior also in pie. One update app remover wouldn't work but titanium would, the next update the reverse would happen. I think the apps need updating so as to work with Android 10.

omiCar said:
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
Click to expand...
Click to collapse
I don't have a video but you can look up the individual steps. You want to do the OTA through ADB sideloading. Then patch the stock boot.img with Magisk Canary, which was linked to above, and then flash with fastboot.
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Uninstall and reinstall Canary Magisk Manager (NOT DEBUG). I had both force encryption and preserve avb CHECKED. Then patch boot.img and flash using fastboot.

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

Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2073775
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, in fastboot:
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.
Once in fastboot:
fastboot boot image-newpixel3axl.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-newpixel3axlRemove.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

Ohboy this is helpful. Just out of curiosity, how does one create a magisk patched boot image with core-only mode enabled? I would like to be able to make my own every time a new security patch is out.
Sent from my Google Pixel 3a XL using XDA Labs

Skittles9823 said:
Ohboy this is helpful. Just out of curiosity, how does one create a magisk patched boot image with core-only mode enabled? I would like to be able to make my own every time a new security patch is out.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
I had planned on keeping these updated but here are the instructions.
You have to build your own copy of magisk from GitHub.
Clone magisk
Go to native/jni/core folder and edit the boot stages.cpp file in notepad++ like this:
Approx line 667
If (access(DISABLEFILE, F_ok) ==0)
Change == to !=
Now build magisk as per instructions on GitHub
One you have built it and there were no errors go to native/out/armeb-v7a folder and get a copy of the magiskini64 file.
Unpack your magisk_patched.img
In the ramdisk folder replace the init file with the .magiskini64 file (rename to init)
Repack your magisk_patched.img
The results are a patched IMG that will boot core only mode.

Tulsadiver said:
I had planned on keeping these updated but here are the instructions.
You have to build your own copy of magisk from GitHub.
Clone magisk
Go to native/jni/core folder and edit the boot stages.cpp file in notepad++ like this:
Approx line 667
If (access(DISABLEFILE, F_ok) ==0)
Change == to !=
Now build magisk as per instructions on GitHub
One you have built it and there were no errors go to native/out/armeb-v7a folder and get a copy of the magiskini64 file.
Unpack your magisk_patched.img
In the ramdisk folder replace the init file with the .magiskini64 file (rename to init)
Repack your magisk_patched.img
The results are a patched IMG that will boot core only mode.
Click to expand...
Click to collapse
Nice. Seems easy enough, if you ever disappear and stop updating images for some reason I'll give it a go ?
Sent from my Google Pixel 3a XL using XDA Labs

Hello
I have regular 3a with Android 10 installed, no twrp. I was in bootloop due to some module and was looking for solution to disable modules with only fastboot.
Before I found this thread, I went and reflash to stock.
Now I know.
Thanks for sharing this.

Tulsadiver said:
I had planned on keeping these updated but here are the instructions.
You have to build your own copy of magisk from GitHub.
Clone magisk
Go to native/jni/core folder and edit the boot stages.cpp file in notepad++ like this:
Approx line 667
If (access(DISABLEFILE, F_ok) ==0)
Change == to !=
Now build magisk as per instructions on GitHub
One you have built it and there were no errors go to native/out/armeb-v7a folder and get a copy of the magiskini64 file.
Unpack your magisk_patched.img
In the ramdisk folder replace the init file with the .magiskini64 file (rename to init)
Repack your magisk_patched.img
The results are a patched IMG that will boot core only mode.
Click to expand...
Click to collapse
I tried to do this for a Pixel 4 XL but the resulting boot image errors with "error boot prepare"

gudenau said:
I tried to do this for a Pixel 4 XL but the resulting boot image errors with "error boot prepare"
Click to expand...
Click to collapse
I have these already made for the pixel 4 xl on the pixel 4 xl forum.

Should just make an AK3 zip that pushes the init from this boot.img into any boot partition, so will work universally.

osm0sis said:
Should just make an AK3 zip that pushes the init from this boot.img into any boot partition, so will work universally.
Click to expand...
Click to collapse
Ooft.
Wait, can you flash that through adb though?
Sent from my Google Pixel 3a XL using XDA Labs

Skittles9823 said:
Ooft.
Wait, can you flash that through adb though?
Click to expand...
Click to collapse
Hmm.. true, non-working recovery is a definite problem. I'm in that boat right now on my OnePlus 7T, which is how I came across this thread.
Okay, better idea. Instead of mucking around with recompiling magiskinit for the above, just do it via boot script in overlay.d

osm0sis said:
Hmm.. true, non-working recovery is a definite problem. I'm in that boat right now on my OnePlus 7T, which is how I came across this thread.
Okay, better idea. Instead of mucking around with recompiling magiskinit for the above, just do it via boot script in overlay.d
Click to expand...
Click to collapse
Tbh, a custom boot.img is the only way to recover in some situations. Like if you can't boot into an adb environment or if you've never granted adb she'll root access.
Sent from my Google Pixel 3a XL using XDA Labs

Skittles9823 said:
Tbh, a custom boot.img is the only way to recover in some situations. Like if you can't boot into an adb environment or if you've never granted adb she'll root access.
Click to expand...
Click to collapse
Exactly, so a custom boot.img using overlay.d is the easiest way to accomplish that currently.

osm0sis said:
Exactly, so a custom boot.img using overlay.d is the easiest way to accomplish that currently.
Click to expand...
Click to collapse
How would one do that exactly without being able to use adb shell?
Sent from my Google Pixel 3a XL using XDA Labs

Skittles9823 said:
How would one do that exactly without being able to use adb shell?
Click to expand...
Click to collapse
overlay.d is built into the boot.img, so you take your latest magisk_patched.img, patch it with the overlay.d scripts to have the desired effect, then repack and flash via fastboot.
Same as the OP likely did, but no need to build Magisk to get a modified magiskinit, since you can do it all via boot script, like I said.

If anyone wants to experiment with this idea, here's the basic setup I used for my boot.img to fully reset the /data/adb directory for the soft brick issue (related to a magisk.db failure) I was seeing in the last canary.
Unpack the current magisk_patched.img for your device using my Android Image Kitchen (AIK) project, then create:
ramdisk/overlay.d/init.resetmagisk.rc:
Code:
on post-fs-data
exec u:r:magisk:s0 root root -- /sbin/init.resetmagisk.sh
ramdisk/overlay.d/sbin/init.resetmagisk.sh:
Code:
#!/system/bin/sh
rm -rf /data/adb/* && reboot
So, pretty simple stuff, and I'm sure it could be applied to some sort of Core Only workaround until @topjohnwu decides what he wants to do with all those Core Only boot.img Pull Requests.

osm0sis said:
overlay.d is built into the boot.img, so you take your latest magisk_patched.img, patch it with the overlay.d scripts to have the desired effect, then repack and flash via fastboot.
Same as the OP likely did, but no need to build Magisk to get a modified magiskinit, since you can do it all via boot script, like I said.
Click to expand...
Click to collapse
Cool. What I did was modify the magisk native/jini/core/bootstages.cpp
Edit: yes sir, your method works great to remove magisk and all modules. The method I had gives you the option to just remove the offending module, though sometimes you have to remove everything anyway. Thank you for your awsome input. If it is okay with you, I'd like to offer both methods in my posts on the pixel forums.

Tulsadiver said:
Cool. What I did was modify the magisk native/jini/core/bootstages.cpp
Edit: yes sir, your method works great to remove magisk and all modules. The method I had gives you the option to just remove the offending module, though sometimes you have to remove everything anyway. Thank you for your awsome input. If it is okay with you, I'd like to offer both methods in my posts on the pixel forums.
Click to expand...
Click to collapse
Sure! You could modify my method to remove all modules by running `magisk --remove-modules` instead of my `rm -rf` command (or just changing the `rm -rf` target), or even try to force Core Only mode by changing the setting directly in magisk.db then rebooting. It's a root shell so pretty much sky's the limit.

osm0sis said:
Sure! You could modify my method to remove all modules by running `magisk --remove-modules` instead of my `rm -rf` command (or just changing the `rm -rf` target), or even try to force Core Only mode by changing the setting directly in magisk.db then rebooting. It's a root shell so pretty much sky's the limit.
Click to expand...
Click to collapse
I have tried multiple methods from this thread but with no success.. Could you maybe help me by altering this boot.img to disable/remove all Magisk modules? Or maybe make it boot core only? It's for my OP 7T. Thanks!
https://mega.nz/#F!rxYDyQia!ziPLPvRsu3kxNBGt694OEQ

paplo said:
I have tried multiple methods from this thread but with no success.. Could you maybe help me by altering this boot.img to disable/remove all Magisk modules? Or maybe make it boot core only? It's for my OP 7T. Thanks!
https://mega.nz/#F!rxYDyQia!ziPLPvRsu3kxNBGt694OEQ
Click to expand...
Click to collapse
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.

osm0sis said:
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.
Click to expand...
Click to collapse
Yeah off topic I know.. Just spotted you had been in the same pickle with the same phone as me. I worked like a charm! Thanks!

Magisk patched boot images [Hotdogb][LineageOS 18.1]

This thread will contain the magisk patched boot.img that i use on my oneplus 7t device running lineageos 18.1.
Ill be putting up two boot images on every new lineageos builds, the first one will be the magisk patched image, the other one will be the default bootimage (incase anyone wants to roll back).
Disclaimer:
I will not be held responsible for any bricked devices, you can follow the flashing instructions directly from topjohnwu, the patched bootimage only contains magisk.
Installation Instructions:
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
Reboot and enjoy.
The above instructions are for devices with lineageOs recovery, for other recoveries you would have to figure it out on your own. If i move to other recoveries ill update the installation instructions here.
Download links will be available below in the comments

[16/01/22] lineage-18.1-20220116 patched boot images
[09/01/22] lineage-18.1-20220109 patched boot images
[02/01/22] lineage-18.1-20220102 patched boot images
[26/12/21] lineage-18.1-20211226 patched boot images
[19/12/21] lineage-18.1-20211219 patched boot images
[12/12/21] lineage-18.1-20211212 patched boot images
[05/12/21] lineage-18.1-20211205 patched boot images
[28/11/21] lineage-18.1-20211128 patched boot images
[21/11/21] lineage-18.1-20211121 patched boot images
[14/11/21] lineage-18.1-20211114 patched boot images
[07/11/21] lineage-18.1-20211107 patched boot images
[31/10/21] lineage-18.1-20211031 patched boot images

Reserved

Thanks bro

intp.pisces said:
Thanks bro
Click to expand...
Click to collapse
You're Welcome , hope you found it useful.

Backstab319 said:
[31/10/21] lineage-18.1-20211031 patched boot images
Click to expand...
Click to collapse
I have read in the thread that magisk can be installed via adb sideload
And while updating lineage OS, we have to tick magisk to install on inactive slot before booting.
But I am confused about magisk patched boot image.
What is the method to install it?

sandeep_kumar said:
I have read in the thread that magisk can be installed via adb sideload
And while updating lineage OS, we have to tick magisk to install on inactive slot before booting.
But I am confused about magisk patched boot image.
What is the method to install it?
Click to expand...
Click to collapse
Hi, i would recommend installing the update from the native updater, that takes care of most of the things for you out of the box.
After you install the update keep the patched bootimage in a directory that's easily accessible on your pc. Then follow the below instructions (Make sure your device is connected via adb),
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
And you are done, once booted up you will see that magisk root status is back and all your previously installed magisk modules and xposed modules work as before the update.

Thanks

I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!

NoSauce said:
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
Click to expand...
Click to collapse
Magisk canary removed magisk hide and the list of modules. Stick with magisk v23 stable to get magisk hide and module list.

NoSauce said:
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
Click to expand...
Click to collapse
Hi, the boot.img is the stock boot image, if you want to get magisk 20.3 stable you will have to flash the file named something like "magisk_patched-2300". I have kept the stock boot image as just a last resort for anyone who faces any difficulty with magisk to roll back easily.
You can have the file installed before the flashing and once you are done with flashing the magisk status will be enabled. Personally i dont install the app, after flashing on the first boot you will get a prompt to place a shortcut icon of magisk on your homescreen, which is much better for magisk hide detection.
This is the stable build boot image patch, for canary you will have to patch the image yourself, as i dont use canary for stability purpose.

Backstab319 said:
Hi, the boot.img is the stock boot image, if you want to get magisk 20.3 stable you will have to flash the file named something like "magisk_patched-2300". I have kept the stock boot image as just a last resort for anyone who faces any difficulty with magisk to roll back easily.
You can have the file installed before the flashing and once you are done with flashing the magisk status will be enabled. Personally i dont install the app, after flashing on the first boot you will get a prompt to place a shortcut icon of magisk on your homescreen, which is much better for magisk hide detection.
This is the stable build boot image patch, for canary you will have to patch the image yourself, as i dont use canary for stability purpose.
Click to expand...
Click to collapse
Thank you @HueyT and @Backstab319 for your help. I was able to successfully install Magisk using the .apk version posted in the github repo (link in my original post).
@Backstab319 just to clarify, the boot.img that you include in your links, you say, are of the "stock boot image". By this, do you mean the...
1. boot.img from the OOS Firmware installed before installing LineageOS
OR
2. boot.img from the LineageOS nightly?
I assume it's 2, correct? The boot.img being patched in Magisk manager is the one from the LineageOS being installed, correct?
Thank you.

NoSauce said:
Thank you @HueyT and @Backstab319 for your help. I was able to successfully install Magisk using the .apk version posted in the github repo (link in my original post).
@Backstab319 just to clarify, the boot.img that you include in your links, you say, are of the "stock boot image". By this, do you mean the...
1. boot.img from the OOS Firmware installed before installing LineageOS
OR
2. boot.img from the LineageOS nightly?
I assume it's 2, correct? The boot.img being patched in Magisk manager is the one from the LineageOS being installed, correct?
Thank you.
Click to expand...
Click to collapse
Yes, its the boot.img extracted from each of the lineageOS nightly release.

The latest magisk 24.1 seems to break everything that it is known for except root status. Safteynet fails, zigisk and denylist do not work. External modules cannot be installed. So am gonna stay with 23.0 for now, the latest images will be uploaded in this weekend.

Backstab319 said:
The latest magisk 24.1 seems to break everything that it is known for except root status. Safteynet fails, zigisk and denylist do not work. External modules cannot be installed. So am gonna stay with 23.0 for now, the latest images will be uploaded in this weekend.
Click to expand...
Click to collapse
Yes. Better to switch to Magisk 24.1 after everything gets fixed. For now V23 has no issues.

flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated

Backstab319 said:
This thread will contain the magisk patched boot.img that i use on my oneplus 7t device running lineageos 18.1.
Ill be putting up two boot images on every new lineageos builds, the first one will be the magisk patched image, the other one will be the default bootimage (incase anyone wants to roll back).
Disclaimer:
I will not be held responsible for any bricked devices, you can follow the flashing instructions directly from topjohnwu, the patched bootimage only contains magisk.
Installation Instructions:
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
Reboot and enjoy.
The above instructions are for devices with lineageOs recovery, for other recoveries you would have to figure it out on your own. If i move to other recoveries ill update the installation instructions here.
Download links will be available below in the comments
Click to expand...
Click to collapse
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated

barcia99 said:
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
Click to expand...
Click to collapse
Yeah, the command is correct.
Which magisk version are you having the issue with?
I had similar issue with magisk 24.1 so i rolled back to 23.

Backstab319 said:
Yeah, the command is correct.
Which magisk version are you having the issue with?
I had similar issue with magisk 24.1 so i rolled back to 23.
Click to expand...
Click to collapse
first tried 24 but had problem so now on the 23 rollback and it's been going for 15 minutes. should i have flashed magisk first then lineage? also one question where it say's "And reboot the device by "fastboot reboot" do i just hit reboot into system from fastboot mode?

barcia99 said:
first tried 24 but had problem so now on the 23 rollback and it's been going for 15 minutes. should i have flashed magisk first then lineage? also one question where it say's "And reboot the device by "fastboot reboot" do i just hit reboot into system from fastboot mode?
Click to expand...
Click to collapse
Oh, i had the same scenario. Tried installing 24.1 didn't work, tried rolling back to 23. But sadly rolling back from 24 to 23 caused bootloop for me as well. I ended up flashing the rom again (fresh) and then it started working.