Database Info

[GUIDE] How to root Android Pie build (Temporarily Guide)

Since TWRP is unbootable under this build, you have to use patched boot trick to root this phone.
However, only Magisk 17.1 is usable on this build, Magisk 17.2 - 18.0 can't be installed properly.
So I made a custom update channel that fixed to Magisk 17.1 to assist me.
This guide requires unlocked bootloader - still, I won't introduce how to unlock it here, please Google for it.
Click to expand...
Click to collapse
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.

If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.

taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
OK, thanks for the info.

hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
I hope you can build TWRP for Android P variant of Chinese and it works on non-unlockbootloader. Like you used to do with Oreo? .Thanks

This did not work with TA-1021 while i have pi installed with twrp and patched boot with magisk 16.1 but it do not work not even root access just keep recovery unchanged(twrp).
It says deviceid locked ple if i patch boot with 17.1 what to do! google pay and banking apps dont work.

hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
Can we use official TWRP recovery (3.2.3 made for PLE)
On pie 612H CN - OF YOUR HOMEBREW
and also on 612H ww ??
Please tell
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
Can we install this TWRP recovery on Chinese firmware (or ww firmware of ta-1003)or it can be flashed only on PLE versions

hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
Can I install D1C-612H-WW over 612H-CN using OST ??
OST show that the image is broken

hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
On rebooting Android root gone????

dont work for me
edit: worsk now over ND1-612C-0-00WW , but for firm official for n5 (612h-0-00WW ) not works, ist patched the xploit for magisk 17 and up

hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
Please help I have working 1003 ww pi installed on Ta-1021 and initially rooted using Chinese twrp with magisk later I tried to install update of twrp recovery got crashed and could not enter recovery tried to flash with Qualcomm tools can enter into Edl phone detected but frimware files doesn't flash some errors. Now result is I can operate my phone magisk 16.1 installed but useless. Banking apps don't work. Factory reset don't work. *#*#874#*#* says file not found (may be because I don't have recovery). Ost la as usual don't work. Please help!

Please help me i am on oreo version .. and i have flashed twrp recovery on my nokia 6 (TA - 1021) ..
THE Problem is when i reboot to recovery it's not booting in twrp but it's booting on custome recovery ..
I need pc everytime , if i want to boot it on twrp .
I have to run command every time to boot in on twrp recovery ..
Is there any way to directly boot it on twrp recovery not in custom recovery ? Please help me

@hikari_calyx Does fastboot boot work for you on pie? For me, it does not. Almost shat my pants thinking my TWRP doesn't work but it does in fact work, just fastboot booting it does not work.

Finally got the official pie update on my TA-1033. (unlocked bootloader)
The standard versions of TWRP 3.2.3.0 / Magisk 17.3 / Magisk Manager 6.0.1 worked perfectly.
As above, "fastboot boot" doesn't work, but "fastboot flash" etc. does.
Happy days.

Not working for me please can you tell the procedure step by step as i tried your steps but didn't happen anything please
---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
Not working i have unlocked bootloader but i tried to flash twrp and it's not booting on it any other solution please let me know .

Can you help me please my device is showing me this on my recovery , what's an issue please reply as soon as possible i can't even apply update through sd card or adb it's not detecting everytime it entered to this menu .. please help me

hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
You gave wrong code for booting patched boot.img
It should be as
FASTBOOT FLASH BOOT PATCED_BOOT.IMG
It will permanently root the android pie
You gave the FASTBOOT code only for booting

vineet09i said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
You gave wrong code for booting patched boot.img
It should be as
FASTBOOT FLASH BOOT PATCED_BOOT.IMG
It will permanently root the android pie
You gave the FASTBOOT code only for booting
Click to expand...
Click to collapse
Hey can i use patched boot image on my official update of pie or which version is able to use of magisk?

Emmykay223 said:
Hey can i use patched boot image on my official update of pie or which version is able to use of magisk?
Click to expand...
Click to collapse
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip

vineet09i said:
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
Click to expand...
Click to collapse
Yes but twrp is not booting on my pie build because it is showing "failed to find device for partition system" and i am unable to apply update through sd card or through adb i don't know why so i am thinking to follow this steps hope it will work.

vineet09i said:
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
Click to expand...
Click to collapse
Why any module is not installing by magisk it's showing me unable to extract, i followed each and every steps as mentioned above and rooted my Nokia 6 again but it's not installing any module what's the reason behind it?

Using Android Q along with Rooting

Can you use Android Q on the pixel A along with rooting?

sillyshyme said:
Can you use Android Q on the pixel A along with rooting?
Click to expand...
Click to collapse
Unfortunately, not. The pixel 3, 3a as well as the xl versions of both currently do not have magisk for Android q. The dev is working on it though. Keep your ear to the ground
Sent from my Pixel 3a using Tapatalk

Yes. The Pixel 3/3a versions use logical partitions in the Q beta. and it sounds like it's taking a major re-write to support it. I believe it is called system-as-root. The developer John Wu has been posting about it on Twitter. https://twitter.com/topjohnwu

Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09

12paq said:
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
Click to expand...
Click to collapse
It's pushed to the Cannery build https://twitter.com/topjohnwu/status/1144159892430659584
Magisk and TWRP all in the same day!

@pharpe wait TWRP got released?

Tiebe said:
@pharpe wait TWRP got released?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413

did any one successfully root q ?

I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.

pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
Yeah, can confirm, did this earlier today!
Just a question, did you have the issue that many apps show up in the appdrawer of pixel launcher, even if they shouldnt? (like Google PDF Reader, Sd Maid unlock or sideloaded Pixel livewallpapers etc.)
I guess its because of the bootloader is unlocked (for security reasons)?! Just really weird. No other issues observed till now.
peace!

Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.

removed

pharpe said:
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
Click to expand...
Click to collapse
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.

bejunk said:
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
Click to expand...
Click to collapse
Interesting. I never realize that. I keep all my apps organized in folders so I only go to the app drawer for things I rarely use. I just assumed everything that was installed was in there.

pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?

c_tho said:
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
Click to expand...
Click to collapse
That is my understanding from what I have read but I have not actually done it. You would uninstall via Magisk and it restores the original boot.img that it has backed-up. Then you are back to stock to take the OTA.

[Guide][Root Magisk Only][OTA Compatible] Moto G6 Play

* Warranty is void
* I'm not responsible for any damage to your phone in mistaking anything specified here
* This guide requires intermediate knowledge
I'm posting this guide because I haven't found any special thread about it, and had to search multiple threads and websites to get a conclusion in how to root Magisk only (without flashing TWRP or any other custom recovery). Focused in not decrypting the phone, or modify any system partition for a full OTA compatibility.
Requirements:
* ADB/Fastboot & Motorola USB drivers installed - (PC)
* Unlocked bootloader - (Phone)
* Stock rom - (Phone)
* Magisk Manager (latest stable version installed on your phone)
* TWRP (compatible to the Moto G6 Play model) - please refer to this thread for more details. ***(Of course, you won't flash it!)
*** PLEASE! REFER TO THE UPDATES BELOW!!! ***
Tutorial:
1. Reboot to bootloader
2. Boot into downloaded TWRP using Fastboot code:
Code:
fastboot boot twrp_downloaded.img
(on TWRP ignore any password by canceling)
3. Backup stock boot image using:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
4. Reboot system using ADB code:
Code:
adb reboot system
5. After rebooted, copy backed up stockboot.img to the phone internal memory
6. Install and open Magisk Manager, click [Instal] > [Install] > [Select and Patch a File] and select stockboot.img on internal memory.
7. After boot image patched, copy magisk_patched.img from phone Download folder to PC
8. Reboot to bootloader and flash magisk_patched.img to phone using Fastboot code:
Code:
fastboot flash boot magisk_patched.img
9. After done, reboot system using fastboot code:
Code:
fastboot reboot
10. All done! Open Magisk Manager and check root! For future OTA updates already rooted with Magisk, I recommend this post: https:// www. the custom droid .com/install-ota-update-rooted-android-device-guide/ - (remove spaces )
[UPDATE 1]
I've noticed that Moto G6 simply forces reboot system before update the device, if we go to restore images in Magisk to try it out tutorial post from 10., it'll simply be removed after that.
Even doing so and going ahead to update the device losing Magisk, and still have to back up once more the new updated boot image and patch it on Magisk following my guide above, I got a bootloop patching the newest OTA with Magisk 20.0 (latest).
After almost losing indefinitely root access, I got it done, downgrading Magisk to 19.3.
For doing so, download Magisk 19.3 zip file from GitHub repository and copy it to the SD Card, boot up into TWRP using fastboot (without flashing) then proceed as read-only, after that, install Magisk 19.3 zip file to patch the OTA updated boot image, then it's done. Root it's working properly without updating Magisk.
I don't know exactly why the latest Magisk it is breaking the OTA updated boot image... Whatever, it's a good approach to get root access back after the recent OTA!
I still need to check if this workaround will be working on new OTA's. That's it.
[UPDATE 2]
After recent update - January 2020, my rooting workaround supporting OTA is working properly as followed solution on UPDATE 1, above.
I didn't test using latest Magisk 20.3 apk due the bootloop when patching boot image in Magisk 20. Don't know if that bug has been fixed...
Updating Magisk after successfully rooted using solution above will not result in a bootloop, but I do recommend downgrade Magisk when new OTA is released.

Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!

gabardal said:
Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!
Click to expand...
Click to collapse
First, if you have the actual boot backup, you'll need to flash it to fix bootloop.
Remember to boot into TWRP (without flashing) to flash it.
* Follow the samples above for the codes if necessary.
After fixing bootloop all you'll need to do is download the Magisk-v19.3.zip from “Magisk GitHub releases” and place it on the external sd card.
Then boot into TWRP (always without flashing) and flash the zip file using TWRP. (Remember to flash to boot image).
It'll simply patch your boot, after that, reboot, if successfully booted go check Magisk.

Magisk/Twrp for GSI (Won't work on stock)

I have a Twrp backup with the boot img patched with Magisk/Twrp boot to recovery boots GSI with magisk boot to recovery hold volume up while rebooting to recovery will boot twrp for this boot img to work u have to be on the vendor of the boot img which is also in the backup so the phone won't bootloop this vendor is modified to work with GSIs pass the magisk environmental setup and notch fix so swiping down is like swiping down on stock.... to implement notch fix go to developer settings hide display cut and choose the first hide option and your notch will be fixed...
Thanks @Spaceminer for the twrp for without this none would of been possible
please note twrp will only boot with a android 9 vendor and your GSI will only boot with magisk and twrrp with the vendor in the backup cause it matches the boot img, GSIs only boot when the vendor and boot img match
the boot img & vendor img in the backup is from Channel/Retail (PPY29. 105-160-4)
Instructions
If on android 9 stock
1. Boot to bootloader
2. fastboot - w
3. fastboot GSI of your choice
4. fastboot boot twrp.img
5. format data
6. Place the twrp folder you downloaded from the zip into your devices internal storage which will be available after u format data
7.Resize system
8.Flash gapps zip if gapps is needed
9.wipe dalvick
10. go to twrp restore boot and vendor
11. reboot to recovery and phone will boot after boot is complete install magisk manager it will do the environmental setup phone will reboot and u will have magisk.... ( if u want the best experience with magisk on this device I recommend that you use havoc cause with the lineage GSI magisk doesn't play nice but with havoc its stable also when making a backup it's boot, system image, vendor image, data if u chose system instead your backup will bootloop your device upon restoration)
Download (twrp img is in twrp folder remove it and place it in ADB folder)
https://mega.nz/file/7t03DLhL#jjS9vgrJMlDS-_-hsApyx4uJ6L8wXCN8HtjSqJrg2ds
if u wanted to do this manually to install the latest canary or stable version magisk need to patch twrp to the recovery flash phh root boot up install magisk manager give it root permissions with phh superuser from apk mirror now with elevated permissions the option patch directly will be avaliable cause u got root (it's the recommended option ?) chose recovery and leave the other 2 unchecked patch the img and reboot to recovery the phone will reboot os with magisk and u hold up while booting recovery will boot twrp after that backup that boot img in twrrp for future installation of the GSI of your choosing....

Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!

xcode22 said:
Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!
Click to expand...
Click to collapse
Everytime u flash a GSI just use the vendor and boot from the twrp folder and your android 10 GSI Will have magisk and twrp no need for data disabler zip cause my backup already has the vendor and boot patches enabled for decryption so twrp will be accessible via boot to recovery
([emoji88]Havoc GSI[emoji88])

Also have edxposed for Android 10 since the one in the repo won't work cause it needs a custom magisk with merged patches for xposed to work on android 10 this version has the patches in the edxposed so having to use a custom magisk won't be an issue cause as ya know obtaining magisk and twrrp in this device was unknown into this OP was made
([emoji88]Havoc GSI[emoji88])

Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!

xcode22 said:
Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!
Click to expand...
Click to collapse
Your on a GSI go in your system settings and activate advance boot and when u have to reboot just put reboot to recovery and you don't have to worry about manually rebooting to recovery everytime u have to reboot also no way u installed the rom to the recovery partion our device doesn't have a recovery partion the recovery lives within the boot img
([emoji88]Havoc GSI[emoji88])]

thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks

xcode22 said:
thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks
Click to expand...
Click to collapse
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])

PoochyX said:
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])
Click to expand...
Click to collapse
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?

xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
PoochyX on telegram dm me I walk you threw it
([emoji88]Havoc GSI[emoji88])

xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
The easiest way I know of is from the stock OS using termux and root.
Code:
su
setenforce 0
mkdir /mnt/x && chmod 0755 /mnt/x
mount -o loop /dev/block/by-name/vendor_a /mnt/x
Now navigate to /mnt/x and everything from vendor will be in there. Find the file and delete it with a root explorer. Then unmount the partition and the changes will be permanent. Doing it this way gets around FEC, which is what prevents you from changing anything in vendor.
Code:
umount /mnt/x
If you need to work on the other vendor partition just change out vendor_a with vendor_b

Any recommendation about what GSI to choice for XT1952-6 variant?

mickem said:
Any recommendation about what GSI to choice for XT1952-6 variant?
Click to expand...
Click to collapse
Chaos GSI Bluetooth works without disabling audio effects (so u can use viper with bluetooth headset) it's clean stock with minimum stuff added to it and works with gravitybox then you got havoc that has the majority of stuff gravity has off the rip so it's not as minimum so more memory usage is needed and Bluetooth only works with the phh disable audio effects work around also magisk works good on both of these lineage is good also if you don't care about magisk working cause with our device magisk has issues on lineage don't know if it was fixed on a recent bulid however if lineage is your preference there is a phh root for it so u can be functional
([emoji88]Havoc GSI[emoji88])

My device is xt1952-4. I downloaded the latest firmware (PPYS29-105-160-4-8), and installed it to both slots. I am currently using Resurection Remix Pie. Is your patched boot.img and vendor compatible with the newer firmware or will I get a downgrade error?

[MAGISK][ROOT][BOOT.IMG] How to patch the Oneplus 8, 8T and 8 Pro stock Boot Image (boot.img) from the currently installed Stock ROM

Quick and concise how to for obtaining a Stock Boot Image from your Oneplus 8, 8T or 8 Pro device and patching with Magisk to create a fastboot flashable patched boot.img.
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked, broken or dead devices. This is a high-level
* how to for users with a basic knowledge of ADB and Fastboot. YOU alone are
* choosing to make these modifications, and you are solely responsible for your
* device's fit for use and wellbeing.
*
* Backup your data!
*
*/
PREREQUISITS:
An unpatched Stock Boot.img running on your device
General knowledge and understanding of ADB and Fastboot
Download latest op8, op8p, or op8t Horizon Kernel img from [e.g., op8p_7.img]:
https://dl.akr-developers.com/?dir=oneplus/horizon_kernel/R/images
Download latest Magisk Canary build from Github [e.g., app-debug.apk]:
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
DEVICE/PC OPERATIONS:
→ ADB
Enumerate devices
Code:
adb devices
Boot into Fastboot
Code:
reboot bootloader
→ FASTBOOT
Enumerate devices
Code:
fastboot devices
Determine the current slot (A/B), whichever slot you're on should be the "good" img
Code:
fastboot getvar current-slot
Boot with the custom kernel downloaded from Horizon to use root [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot boot "C:\Users\User\Downloads\op8p_R7.img"​
Code:
fastboot boot xxxxxxx.img
→ ADB
Copy the boot.img from each slot to the root of the device
Code:
adb shell
su
dd if=/dev/block/sde11 of=/sdcard/boot_a.img
dd if=/dev/block/sde35 of=/sdcard/boot_b.img
→ Android Device [NOTE: Some Android 11 devices experience patching issues on the Beta Channel like bootloop] [NOTE: Some users experience issues on Canary like no SIM detected; if so switch to Beta]
Install Magisk app-debug.apk (Canary)
Go to Settings → Update Channel → Canary
Go to Home → Install → Install → Select and Patch A File
Navigate to internal storage and select the stock boot.img [choose the img from whichever slot you're on]
When it’s done patching copy the file, named magisk_patched.img, from the root → Downloads of your device to PC
→ ADB
Code:
reboot bootloader
→ FASTBOOT
Test to ensure it boots before flashing; if not you'll need to patch the other img
Code:
fastboot boot magisk_patched.img
→ Android Device
If the device boots and you have root in the Magisk Manager app, reboot the device into Fastboot then flash the active slot [NOTE: Both slots do not need to be flashed; just the current active slot]
→ FASTBOOT
Flash the patched image file [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot flash boot_b "C:\Users\User\Downloads\magisk_patched.img"
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
- OR -​
Code:
fastboot flash boot_a magisk_patched.img
fastboot reboot
- OR -​
Code:
fastboot flash boot_b magisk_patched.img
fastboot reboot
ADDITIONAL RESOURSES:
→ FASTBOOT
If you need to set the other slot to be the active slot use:
Code:
fastboot --set-active=a
- OR -​
Code:
fastboot --set-active=b
→ ADB
ADB Magisk Bootloop Fix
Code:
adb shell
magisk --remove-modules
→ OTA Help
Magisk stock boot.img missing fix [NOTE: Android 11 onwards, the /sbin folder might not exist, so Magisk will randomly create a folder under /dev and use it as the base folder]
Rename to: stock_boot_0.img
Compress with gzip = stock_boot_0.img.gz
Copy stock_boot_0.img.gz file to the root of: /data
Edit the config file: /dev/xxxxxxx/.magisk/config → Change SHA1= to 0
Magisk Manager → Uninstall Magisk → Restore Images
→ ADB
Determine the random folder name generated by Magisk on Android 11+
Code:
ls -laR /dev | grep '.magisk/rootdir'
→ ADB
Determine the Boot Image partition location [NOTE: Will list all partitions; look for boot_a and boot_b]
Code:
ls /dev/block/bootdevice/by-name/ -all

Tried some other way on android 11 but failed, so back to android 10.
maybe i won't get android 11 until TWRP is work.
can't easily backup data without root is very annoying, thanks for the work!

I have followed every step, but root only last until I restart my Oneplus.
What am I doing wrong? Why want the device stay rooted?

mrram said:
I have followed every step, but root only last until I restart my Oneplus.
What am I doing wrong? Why want the device stay rooted?
Click to expand...
Click to collapse
Guessing here, but have a second look at these two commands:
Code:
fastboot boot magisk_patched.img
△ This will NOT flash the rooted image, it will only boot up once so you can test it or use it for temporary root
verses
Code:
fastboot flash boot magisk_patched.img
▲ This will flash the rooted image and is used after you've tested the patched image to be sure it doesn't bootloop and to have persistent root

If I use this Horizon kernel to boot with root on 11.0.4.4, could I use directly Magisk 22.0 to root the device permanently? Thanks in advance.

MagikGab said:
If I use this Horizon kernel to boot with root on 11.0.4.4, could I use directly Magisk 22.0 to root the device permanently? Thanks in advance.
Click to expand...
Click to collapse
I only use the Horizon to boot then grab my kernel to patch with Magisk. You could use the Horizon kernel, but you would have to flash it, not just boot it. So, root device, backup stock dtbo, flash Horizon & dtbo, re-root if lost during flash. I would recommend against that until there's a custom recovery available in case there were any issues. Additionally, you must backup your stock dtbo if you ever want to return to stock. You should visit the Horizon thread for more details, but again if you're not familiar with kennel mods you might not want to start learning on a device without a custom recovery.

CarvedArt said:
I only use the Horizon to boot then grab my kernel to patch with Magisk. You could use the Horizon kernel, but you would have to flash it, not just boot it. So, root device, backup stock dtbo, flash Horizon & dtbo, re-root if lost during flash. I would recommend against that until there's a custom recovery available in case there were any issues. Additionally, you must backup your stock dtbo if you ever want to return to stock. You should visit the Horizon thread for more details, but again if you're not familiar with kennel mods you might not want to start learning on a device without a custom recovery.
Click to expand...
Click to collapse
I'd like only to root my device, remaining as more stock as possible, for now. If I want to avoid using a custom kernel (also for the rooting process), should I extract the boot.img with Python, then patch it with Magisk 22? Thanks in advance for your reply, but I'm coming from a Xiaomi that was quite easier to root

MagikGab said:
I'd like only to root my device, remaining as more stock as possible, for now. If I want to avoid using a custom kernel (also for the rooting process), should I extract the boot.img with Python, then patch it with Magisk 22? Thanks in advance for your reply, but I'm coming from a Xiaomi that was quite easier to root
Click to expand...
Click to collapse
Just follow the steps above -- that'll get you a stock kernel (your current kernel) patched with Magisk and permanently rooted. The above process is only using the Horizon kernel to boot your device with root so that you can extract your kernel and patch it. The final result will be as stock as you can get with root.

Hey everyone. OP8 Pro user here. Just took OTA going from 11.0.9.9 running Magisk Canary 23 to the newest 11.0.10.10. I restored images before taking the OTA and reinstalled magisk to the other slot like I always do to retain root. Ive now lost root and am trying to boot the last two versions of the Horizon kernel. Ive tried the two latest ones (r9.2 and r9.2.1 from February 2021) and while they do boot my phone, I cant get SU access to extract the stock images.
Anything else that anyone things I should try? All i want from Christmas is root.

Isn't there a more easy way to obtain root?
That's strange. I use OnePlus smartphones with LineageOS for years now and cannot remember to execute such a complicated procedure. Just now I got a OnrPlus 8, installed LineageOS and Magisk and restored my apps with Titanium. So, it definitely worked.
Now, after a Lineage system update, root is gone.
Unfortunately I cannot tell exactly how I installed Magisk. I have a very poor memory. Think I just installed the app and said either just "install" or patched the zip with TRWP
But I definitely never downloaded or extracted any boot image manually.
Has anyone an explanation for this?
Even more strange: I just tried to flash magisk.zip again with TRWP. Now it tells me
"Magisk patched boot image detected"
and later:
"Failed to mount '/system_root' (Device or resource busy)"
After reboot the Magisk app now offers me three choices in the install tab:
- choose a file and patch (only this one existed before)
- direct installation (recommended)
- install into inactive slot (after OTA)
I don't understand the last one and tried the recommendet one.
Now, root is there again. Do I have to do this after each update? With my OnePlus5 I didn't.

Unfortunately I have another problem with my OnePlus8 and Lineage:
I'm using AdAway which replaces the hosts file, but on my OP8 it cannot.
"Unable to cppy the hosts file to /System partition. Please check if the Magisk Systemless module is active"
What does it mean? The Magisk app says: "ramdisk yes"

tosho1 said:
Unfortunately I have another problem with my OnePlus8 and Lineage:
I'm using AdAway which replaces the hosts file, but on my OP8 it cannot.
"Unable to cppy the hosts file to /System partition. Please check if the Magisk Systemless module is active"
What does it mean? The Magisk app says: "ramdisk yes"
Click to expand...
Click to collapse
Magisk → Settings (Gear icon) → Systemless hosts ← Click it

tosho1 said:
Isn't there a more easy way to obtain root?
That's strange. I use OnePlus smartphones with LineageOS for years now and cannot remember to execute such a complicated procedure. Just now I got a OnrPlus 8, installed LineageOS and Magisk and restored my apps with Titanium. So, it definitely worked.
Now, after a Lineage system update, root is gone.
Unfortunately I cannot tell exactly how I installed Magisk. I have a very poor memory. Think I just installed the app and said either just "install" or patched the zip with TRWP
But I definitely never downloaded or extracted any boot image manually.
Has anyone an explanation for this?
Even more strange: I just tried to flash magisk.zip again with TRWP. Now it tells me
"Magisk patched boot image detected"
and later:
"Failed to mount '/system_root' (Device or resource busy)"
After reboot the Magisk app now offers me three choices in the install tab:
- choose a file and patch (only this one existed before)
- direct installation (recommended)
- install into inactive slot (after OTA)
I don't understand the last one and tried the recommendet one.
Now, root is there again. Do I have to do this after each update? With my OnePlus5 I didn't.
Click to expand...
Click to collapse
LineageOS is not the stock ROM so it's slightly different and not covered in this thread.

Thank you, CarvedArt. I wasn't aware of this.

Does anyone have the latest stable Android 13 patched boot image for the IN2015 that they can share with me ?