Related
{ ROOT } Twrp & Magisk Installation in Official Oreo { (N2G47H.7.12.29 (Android O) }
Needed Files :
1. Fastboot Rom
Http://bigota.d.miui.com/7.12.29/tissot_images_7.12.29_20171228.0000.00_8.0_c9a6ea979b.tgz
2. Platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
3.Twrp recovery
https://androidfilehost.com/?fid=962157660013069602
4.. Twrp Installer
http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
5. Magisk 15.2
http://www.stechguide.com/download-magisk-v15-2/
Flashing Guide:
Download all the needed files copy magisk zip file in your device.
1. Flash Fastboot rom using Mi flash tool. ( clean install recommended )
2. After flashing, complete setup and other setting.
( Note : Please Skip adding Finger print. if you are added by mistakenly kindly delete your finger print in settings. )
3. Enable oem unlocking & usb debugging in developor options.
4. Extract platform tool in your pc.
5. Paste the downloaded twrp recovery(3) & twrp installer(4) in platform tools folder.
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
9. Type following command in command window
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
10. reboot to recovery.
11. your internal storage is available in twrp now.
12. Flash Magish 15.2 ( strictly use this version )
13. Goto to reboot option in twrp and select your current slot a or b . ( twrp will showing your current slot )
14. reboot system and enjoy.
***** Sorry for my bad english ****
will try soon and will update you.
please let me know if after following this method are we able to install Magisk modules and does it work?
Yes.
Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.
ota updates
after root by this method ..how to install ota updates
navneet1 said:
after root by this method ..how to install ota updates
Click to expand...
Click to collapse
1. Download and flash stock rom (same version that you are currently on) using mi flashtool with save user data option.
2. Your device will be in the same condition (including apps, settings, data etc.) but unrooted.
3. You'll have an ota notification. Install it with normal procedure.
4. Follow the op from step 3.
Apoorv AR said:
Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.
Click to expand...
Click to collapse
Follow the steps with clean flashed rom.
Spk1690 said:
Follow the steps with clean flashed rom.
Click to expand...
Click to collapse
It worked when I flashed Magisk again without loosing any modules or anything.
get block at
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
the first file i downladed got different name and when i put this command they tell me
No such file or directory
@Spk1690 SO this file twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip only for show internal storage?
edit
After enter this command fastboot boot recovery-3.2.1-1.img my device boot into system, not twrp, how to solve?
Does this work on the January Oreo STABLE patch??
KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
upp
KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
I have tried , it works, but do it on your own risks
root
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?
Spk1690 said:
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
Click to expand...
Click to collapse
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.
These files are old, a new ones have been released some time ago:
An updated ROM file:
http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
An updated recovery:
https://www.androidfilehost.com/?fid=818070582850498337
Updated TWRP installer:
(check the attachment section)
Updated Magisk 16.0:
(Check the attachment section)
realtebo said:
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.
Click to expand...
Click to collapse
Have you selected the partition you've installed your recovery to?
Because if not, boot the TWRP .img again and switch the partitions.
Reboot afterwards.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
cregen said:
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?
Click to expand...
Click to collapse
You might want to try this: https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
Check steps 7-10. Read the whole instructions even if they aren't for your ROM. (Skip the copying process and other LOS related stuff.)
I have a problem while flashing twrp on march patch after flashing twrp on both slots android will automatically degrade to February patch ? I'm fed up of trying things please anyone help me
Im new in mi a1, why we need to flash new rom before flash twrp? My rom position on latest update
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!
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?
History...
I originally wrote this guide to upgrade from 10.0.4.0 to 10.0.7.0.
I have also used this same guide to install every OTA from 10.0.7.0 to 11.0.11.0.
This guide assumes you have both Magisk and TWRP, that Magisk cannot "uninstall" (because of TWRP installation) and that you want to keep both Magisk and TWRP after installation. Parts of this guide may still be useful if you aren't in this exact situation.
If you only have Magisk, you should be able to follow these much simpler instructions: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Things to have on hand:
- vanilla_boot.img (for the version you currently have)
- patched_boot.img (your current boot image with Magisk)
- TWRP img and zip (see version info below)
I think that TWRP also causes the vendor partition to be modified. It may also touch system but I have a modified bootanimation.zip which modifies system, so I can't be sure. In any case, I also have a backup of system.img and vendor.img.
Because Magisk is installed after TWRP, Magisk's "backup" of the "stock boot image" is not vanilla. This means that in order to take the OTA, I have to flash the vanilla boot image.
0 - Update your patched_boot.img
If you don't have a patched_boot.img for your current Magisk (eg. my patched_boot.img was old, since I had installed several Magisk updates), you should build a new patched_boot.img so that when you boot it, the system will continue to work.
Push the vanilla image to the phone.
Code:
adb push vanilla_boot.img /sdcard
Then get Magisk to install using the "Select and Patch a File" method, select the file you uploaded. Then pull down the patched image.
Code:
adb pull /sdcard/Download/magisk_patched.img patched_boot.img
1 - Prepare to OTA
For some reason, my carrier does not like the OTA process so I always turn on Airplane mode + Wifi.
Get to fastboot and check the current slot.
Code:
adb reboot bootloader
fastboot getvar current-slot
My current slot was b
Flash the system and vendor partitions (if necessary).
Code:
fastboot flash system_b vanilla_system.img
fastboot flash vendor_b vanilla_vendor.img
Flash vanilla and boot the patched image (so that Magisk is active and the OTA can be applied).
Code:
fastboot flash boot_b vanilla_boot.img
fastboot boot patched_boot.img
2 - Do the OTA
Install OTA (DO NOT REBOOT)
If the OTA fails
If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions. As previously mentioned, I've had to flash all of boot, vendor and system for each OTA.
Code:
adb logcat | grep update_engine
...
07-01 06:52:38.470 E/update_engine(935): [0701/065238.470683:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
07-01 06:52:38.470 E/update_engine(935): [0701/065238.470931:ERROR:delta_performer.cc(995)] Expected: sha256|hex = A4AD686D7BF628486668446221D0089BF5915DBC1158C83D30A06222FE7D2ACB
07-01 06:52:38.471 E/update_engine(935): [0701/065238.471002:ERROR:delta_performer.cc(998)] Calculated: sha256|hex = 4CADBE88EC1C019913A0B416EB9031840D4BA6B2287A3FC814A2B8B7F9871F7D
07-01 06:52:38.473 E/update_engine(935): [0701/065238.471072:ERROR:delta_performer.cc(1009)] Operation source (offset:size) in blocks: 0:5221,5461:405,5869:1,5873:343,6221:589
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473233:ERROR:delta_performer.cc(1191)] ValidateSourceHash(source_hash, operation, source_fd_, error) failed.
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473340:ERROR:delta_performer.cc(298)] Failed to perform BROTLI_BSDIFF operation 187, which is the operation 0 in partition "boot"
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473411:ERROR:download_action.cc(337)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
07-01 06:52:38.739 E/SystemUpdate(15410): [Execution,NonStreamingAbApplyAction] Installation failed with error code: 20.
3 - Backup the vanilla boot image
Note that you need to pull from the other slot (in my case, a).
Code:
adb shell
su
dd if=/dev/block/by-name/boot_a of=/sdcard/vanilla_boot.img bs=1024k
Backup system.img and vendor.img too (if required).
Code:
dd if=/dev/block/by-name/system_a of=/sdcard/vanilla_system.img bs=1024k
dd if=/dev/block/by-name/vendor_a of=/sdcard/vanilla_vendor.img bs=1024k
4 - Magisk patch the other slot
Use Magisk to "Install to Inactive Slot (After OTA)" (DO NOT REBOOT)
5 - Backup the patched boot image
Note that you need to pull from the other slot (in my case, a).
Code:
dd if=/dev/block/by-name/boot_a of=/sdcard/patched_boot.img bs=1024k
exit
exit
# back on your computer
adb pull /sdcard/vanilla_boot.img
adb pull /sdcard/patched_boot.img
Pull down system and vendor images too (if required).
Code:
adb pull /sdcard/vanilla_system.img
adb pull /sdcard/vanilla_vendor.img
Now you can let Magisk reboot. This is the moment of truth...
At this point you should have an upgraded, Magisk-enabled system and backups of the vanilla and patched boot images. Congratulations on completing the OTA!
If the system fails to boot
There's a few things to try before giving up if the system fails to boot...
1) Boot without Magisk (fastboot boot vanilla_boot.img). Probably indicates that a Magisk module you have is no longer compatible.
2) Boot TWRP (fastboot boot twrp.img) and poke at things. As an example, I used the /sdcard/mm program (part of Magisk Manager for recovery) to disable EdXposed when the OTA to Android 10 failed to boot.
6 - Restore TWRP
It is possible to boot TWRP from fastboot so you don't strictly need to install TWRP. I like to have it available anyway.
Old version info...
I had been using the official TWRP 3.2.3, which worked great up until 10.0.9.0. With 10.0.9.0, I couldn't get to TWRP, I just got the system destroyed screen. I could fastboot boot it, but it couldn't mount /data (a problem it has always had).
I figured out that TWRP 3.3.1-dees_troy (from the official TWRP site) works with 10.0.9.0 and up. What's more, it works (can decrypt /data) if you fastboot boot it, not just after install. So you could in theory simply not install TWRP and fastboot boot if in the event that you actually need it.
I know that people have their own favourite versions, with the offain version being popular (didn't work for me). There's OrangeFox too (also didn't work for me).
In summary, I recommend Official TWRP 3.3.1-dees_troy but if you have a favourite alternative, feel free to use it instead.
TWRP thread: https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
Download link: https://dl.twrp.me/daisy/
Restoring TWRP is the same as installing it the first time. This is the process that I use.
Flash vanilla boot, then install TWRP to it.
Code:
adb reboot bootloader
fastboot boot twrp-3.3.1-dees_troy-daisy.img
Install TWRP
Code:
adb push twrp-installer-3.3.1-dees_troy-daisy.zip /sdcard
Use TWRP to install twrp-installer-3.3.1-dees_troy-daisy.zip
I install my modified bootanimation.zip at this time.
Mount System from TWRP (it is normally already mounted for me).
From a shell:
Code:
adb shell
cd /sdcard
cp bootanimation.zip /system/system/media/bootanimation.zip
Umount System
You must re-install Magisk after installing TWRP.
Code:
adb reboot bootloader
fastboot boot patched_boot.img
Use Magisk to "Direct Install (Recommended)"
Reboot
For some reason, my carrier does not like the OTA process so at this point I normally power off the phone rather than just rebooting. When the phone boots, I can turn off airplane mode and check that a mobile data connection can be made.
7 - Confirm that everything works
Make sure the system comes up and Magisk Manager says that Magisk is installed.
Make sure you can get to TWRP. Boot while holding VOL+ or
Code:
adb reboot recovery
Make sure TWRP can see your files.
Congratulations! You have installed an OTA while keeping Magisk and TWRP!
8 - Backup boot.img with TWRP + Magisk (optional)
If you want a copy of the boot.img with both Magisk and TWRP. This pulls from the now-current slot (in my case, a). I'm not totally sure of the value of this, since I can't get fastboot to boot this image. It may come in handy if you upgrade TWRP and that breaks (since you can flash this back rather than having to install the old TWRP again).
Code:
adb shell
su
cd /sdcard
dd if=/dev/block/by-name/boot_a of=twrp_boot.img bs=1024k
exit
exit
# back on the computer
adb pull /sdcard/twrp_boot.img
Thanks. Could you upload or indicate where we can get the necessary files?
Will i loose all user data and internal storage wiped if i do this?
Thanks for sharing, looks complicated, also i think you should use a fixed twrp, since the official dont have acces to sdcard.
rossarnie said:
Thanks. Could you upload or indicate where we can get the necessary files?
Click to expand...
Click to collapse
If you have Magisk, you should already have the vanilla and patched boot.img files.
Of you don't already have Magisk, just follow the install procedure here. https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
If you're running 10.0.4.0 without magisk and need to extract your vanilla boot.img. Use fastboot to boot into twrp and then you can do the DD command to extract boot. Use adb pull to save it to PC.
I used official TWRP from here.
https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
Apparently there's a different twrp that can access the external SD card. I don't have an external SD card so I don't need it.
dr.bahaeddin said:
Will i loose all user data and internal storage wiped if i do this?
Click to expand...
Click to collapse
I didn't lose any data.
I've never had a problem with Magisk. TWRP does tend to bootloop after install, which is why I install magisk again.
You should be able to flash the patched or vanilla boot if twrp is boot looping to fix it too. Just won't have twrp anymore.
a1291762 said:
I didn't lose any data.
Click to expand...
Click to collapse
Mind you. I have a backup of my apps and data that's off of my phone so even if I do need to factory reset I can get it back. That's a longer and more complicated guide.
Txatxiquesi said:
looks complicated.
Click to expand...
Click to collapse
Before I had twrp the standard Magisk ota process was enough. But that loses twrp and with twrp in my magsik backup, the uninstall didn't work. So extra steps are needed. Plus some extra steps to make backups of important files for the next OTA
a1291762 said:
If you have Magisk, you should already have the vanilla and patched boot.img files.
Click to expand...
Click to collapse
Hmm... This may not be the case. I'm careful to make backups but it's easy to skip this.
If you don't have a patched boot image you can backup your current boot partition from a root shell. You need to find out if you are booting a or b slot. Then
dd if=/dev/block/by-name/boot_a of=/sdcard/patched_boot.img bs=1024k
Magisk puts old stock backups into /data. I had 4 files in there which makes it hard to know what each file is.
That's why I made sure to backup my vanilla boot image immediately.
If you're stuck without a vanilla 10.0.4.0 boot you can't do the OTA. I can upload mine somewhere when I get home tonight if it's not already online.
a1291762 said:
...If you're stuck without a vanilla 10.0.4.0 boot you can't do the OTA. I can upload mine somewhere when I get home tonight if it's not already online.
Click to expand...
Click to collapse
This would be very helpful, please
FunkmasterC said:
This would be very helpful, please
Click to expand...
Click to collapse
Here is the backup I made of the 10.0.4.0 vanilla boot.img. You'll need to decompress this before flashing.
URL REMOVED
What's new on 10.0.7.0 bro? Should me wait for 10.1 update if im on 10.0.4.0 rooted?
10.0.7.0 has the March security patches. I haven't noticed any actual changes.
Thank you, your Linux commands are sick, I never know I can get the vanilla and patched boot.img like that.
Cheer~
is there an update for file version 10.0.8.0??
I only just got the notification this morning. I'll do the upgrade tonight but I expect the same process will work.
I just used the same process to go from 10.0.7.0 to 10.0.8.0. This time I was installing to slot b instead of slot a, but otherwise, things were the same.
A side note... I hadn't got around to installing TWRP 3.3.0 so I did that but it couldn't mount /data. TWRP 3.2.3 can mount /data, so I installed that again.
a1291762 said:
I just used the same process to go from 10.0.7.0 to 10.0.8.0. This time I was installing to slot b instead of slot a, but otherwise, things were the same.
A side note... I hadn't got around to installing TWRP 3.3.0 so I did that but it couldn't mount /data. TWRP 3.2.3 can mount /data, so I installed that again.
Click to expand...
Click to collapse
I have successfully updated to 10.0.8.0 with Magisk 18.1, now on Magisk 19.1, everything is running fine. I'd like to also install TWRP but refrain from doing so because of the problems (bootloops, crashes, etc) the official TWRP 3.2.3 shows with decryption in Pie and mounting external or even internal sdcard. I wonder if the latter is fixed in the inofficial fixed version. I think the benefit of TWRP is not worth the effort of repeating a1291762 wonderful tricky procedure on the monthly OTA update basis.
However the procedure is very smart, a back-to-the-roots approach of former days... great, I like it.
But I don't understand how a patched_boot.img can be created from an empty file (boot_a)?
[dd if=/dev/block/by-name/boot_a of=patched_boot.img bs=1024k] Locating the boot_a in </dev/block/by-name/> reveals a boot_a file with 0 bytes. Moreover, to unzip the zipped stock boot Image in </data/stock_boot*.img> or </sbin/.magisk/mirror/data/> I am looking for a command that just returns the boot file rather than expanding it to the full partition. Weird, can anybody help?
Thanks again to a1291762
grufty47
It appears that it is not possible to add some boot.img as attachment
grufty47 said:
I'd like to also install TWRP but refrain from doing so because of the problems (bootloops, crashes, etc) the official TWRP 3.2.3 shows with decryption in Pie and mounting external or even internal sdcard.
Click to expand...
Click to collapse
I use official TWRP 3.2.3. Only really to fix bootloop problems.
I don't have a SD and no problems mounting data.
Lots of people following the TWRP install guide seem to get bootloop. I solve that by patching boot with Magisk. Some people recommend installing an old about image.
If you have a backup of boot you can at least restore that if you have problems.
grufty47 said:
But I don't understand how a patched_boot.img can be created from an empty file (boot_a)?
Click to expand...
Click to collapse
Welcome to Unix, where nearly everything is a file.
Hard disk? /dev/sda
Partition? /dev/sda1
File? /mnt/sda1/file.txt
In this case, boot_a is a way to access a partition on the phone's flash. Actually a link (shortcut) to /dev/mmcblk0p52. Partition number 53 on flash chip 1. The size can't be seen because it's a device and not a file.
grufty47 said:
I am looking for a command that just returns the boot file rather than expanding it to the full partition.
Click to expand...
Click to collapse
dd is a command to read a device. The partition is 64M big so that's the size of the file. gzip can compress well because the actual image is only 24M big and the rest is empty.
Magisk knows how to do it. A tool called magiskboot but I don't know where it lives or how to run it.
I found this header from magiskboot. It shows how the boot.img is structured.
https://github.com/topjohnwu/Magisk/blob/master/native/jni/magiskboot/bootimg.h
I just did the 10.0.9.0 OTA. I added a section of updating your patched_boot.img (since the Magisk updates I did made my old one useless) and I changed the backup instructions due to changes in Magisk 19. If you know where the stock boot lives before reboot, please let me know.
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 ?