For those who would like to root, but not install any version of TWRP, here is a guide I put together. Hopefully it's easy enough and specific enough to understand:
1. Be sure to download the firmware you are CURRENTLY on to avoid any possible issues. Find it under SETTINGS, SYSTEM, ABOUT PHONE, BUILD NUMBER. The region is in parenthesis and the firmware version is the last three digits.
2. Extract the RAMDISK.img file using this Huawei Updater Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
3. Obtain a previously patched RAMDISK file to get an initial Magisk install on your phone first. There is one on XDA floating around named CLT-29-MAGISK.img.
4. Boot into ***FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk CLT-29-MAGSIK.img"
5. Reboot the phone and download Magisk Manager 5.5.5. There may be other versions that work, but this version worked every time for me.
6. After installing Magisk Manager 5.5.5, install the next two upgraded versions while INSIDE Magisk Manager until you get to 7.1.x.x. To avoid any issues with Magisk Manager, don't exit out of the application until you install 7.1.x.x.
7. Click INSTALL on the first option next to the word MAGISK in Magisk Manager to patch your freshly extracted RAMDISK.img file from Step 2. Magisk Manager does not allow for direct installation of the Magisk zip file any longer so you need to patch a stock RAMDISK file to be flashed in Step 9.
8. Copy that RAMDISK.img file to your PC and place the file in your ADB tools folder. It would be good to save a copy of this file for later if you need to re-root. By doing so, you can avoid steps 1-3.
9. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk patched_boot.img"
10. Reboot and you'll have root!
***FASTBOOT
To boot into FASTBOOT, turn off phone, hold down the VOLUME DOWN button for a few seconds, and while still holding it plug your charging cable into the phone. The screen should turn on with a white background indicating you are in FASTBOOT mode.
Hi good guid, I flashed version 9.0.0.252 and had a lot fc. back to 215, everything works, any idea what the latest European working version clt-lgrp2-ovs 9.0.0??
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 ?
Bro can I root op9 running derkpest rom it is safe to root and if safe then how to root tell the possible best way guys?
Patched boot.img with magisk, PS when you find derkpest Rom for op9?
iaio72 said:
Patched boot.img with magisk, PS when you find derkpest Rom for op9?
Click to expand...
Click to collapse
Hoo bro from a12 patched img doesn't work I've saw posts so does it work or flashing magisk zip in recovery which is best way to avoid bootloop
Venkata Prathap said:
Hoo bro from a12 patched img doesn't work I've saw posts so does it work or flashing magisk zip in recovery which is best way to avoid bootloop
Click to expand...
Click to collapse
For OOS:
1) Have Magisk Manager v23016 or above installed
2) Download the boot.img from here and put in phone’s Download folder
3) Open Magisk Manager and click top Install and patch boot.img
4) Move patched image to PC’s adb directory
5) Boot phone into fastboot mode and run the command:
fastboot boot magisk_patched_boot.img
6) Phone will boot into temporary root. Click top Install again but choose Direct Install (recommended) this time
7) Reboot when done and profit
For COS:
1) Have Magisk Manager v23016 or above installed
2) Download rooting files and extract on PC
3) Copy boot.img and vendor_boot.img to phone’s Download folder
4) Open Magisk Manager and click top Install and patch boot.img. When done, go back and repeat the process for vendor_boot.img
5) Move both patched images to adb directory on your pc along with vbmeta.img
6) Run this command:
fastboot –-disable-verity —disable-verification flash vbmeta vbmeta.img
********************Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform–tools
7) If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
incesu said:
For OOS:
1) Have Magisk Manager v23016 or above installed
2) Download the boot.img from here and put in phone’s Download folder
3) Open Magisk Manager and click top Install and patch boot.img
4) Move patched image to PC’s adb directory
5) Boot phone into fastboot mode and run the command:
fastboot boot magisk_patched_boot.img
6) Phone will boot into temporary root. Click top Install again but choose Direct Install (recommended) this time
7) Reboot when done and profit
For COS:
1) Have Magisk Manager v23016 or above installed
2) Download rooting files and extract on PC
3) Copy boot.img and vendor_boot.img to phone’s Download folder
4) Open Magisk Manager and click top Install and patch boot.img. When done, go back and repeat the process for vendor_boot.img
5) Move both patched images to adb directory on your pc along with vbmeta.img
6) Run this command:
fastboot –-disable-verity —disable-verification flash vbmeta vbmeta.img
********************Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform–tools
7) If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
Click to expand...
Click to collapse
for COS: you still only need boot.img and magisk. install magisk patch boot.img temporarily boot on magisk-patchedboot.img and direct install in magisk manager
after the latest apdate 13.0.3 i lose my magisk
and when i want to install it using adb it gives me a boot loop and i shoold to flash the original boot.img
Nb : ramdisk yes
Uninstall it thn flash it using Twrp
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
souhail39 said:
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
Click to expand...
Click to collapse
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
pl1992aw said:
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
Click to expand...
Click to collapse
This is what i did
The original boot run finely but the patched one give me a boot loop
Miui 13 doesn't support yet unless you patch the boot img. Just revert to 12.5.9
souhail39 said:
This is what i did
The original boot run finely but the patched one give me a boot loop
Click to expand...
Click to collapse
The safe way is to not flash boot image with TWRP or Orangefox custom recoveries. Flash with fastboot mode with PC is better to prevent issue.
What version of Magisk?
If you are using the latest Magisk v24.X but it bootloop, you may report issue to Magisk author in his github.
If you used Magisk v23, it is said not working on Android 12, so will not work on MIUI 13.
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
VD171 said:
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
Click to expand...
Click to collapse
thx for your answer but always the same problem with patched img files
Before doing any of this, I am not responsible of any bricked devices, carefully read everything I written before doing anything. I wish you the best luck . You do it once and you will know how to do it every other time.
Spoiler: Minor bug
Keep in mind with this GSI the home screen (custom too) and quick settings will be choppier than on stock firmware on idle (when I charge up the battery it is less noticeable), this can be less annoying by disabling all animations in developer options.
Spoiler: Magisk
Magisk with TWRP
If you want to flash magisk you need TWRP and only place to download it i unofficialtwrp for the phone (be careful what you do while flashing it and DO NOT FLASH orange-Red-state-disabler because your phone will not boot after you flash it and reboot) and when you have it installed you download magisk apk, rename magisk.apk to magisk.zip, put it on an SD card because internal storage is encrypted and flash. If you get issues you will need to download V12 Firmware and reflash all of it using SP Flash tool, but when I did it the phone generated a new IMEI??? I fixed that using MAUI Meta and the IMEI was working after that so when I flashed modded magisk boot img from V12 firmware it all worked.
Magisk with official app
If you want to flash Magisk using magisk app and you are on latest firmware V15 you can’t do it by using Magisk app because every link to the V15 firmware is dead (but if you are on V12 you are lucky because the link for it is alive ) but you do get a working SuperUser app in the GSI if that’s enough. If you want Magisk, your boot img needs to match the firmware or stuff like WIFI will not work because the kernel does not match the rest of the firmware. That means you need to use the SP Flash Tool to completely reflash the whole firmware, but when I did it the phone generated a new IMEI??? I fixed that using MAUI Meta and the IMEI was working after that so when I flashed modded magisk boot img from V12 firmware it all worked.
-----------------
Spoiler: Known issues
Known issues:
So far none besides what I mentioned in minor bug.
-----------------
Spoiler: Things needed
Things needed:
Computer running Windows XP or newer
Phone itself booted into Android and a USB cable
ADB and Fastboot driver with Platform-Tools (there is a tutorial on my youtube channel how to use it)
ZIP file attached below
Phh Terble GSI (only these builds worked for me):
Full gappps
GO Gapps
AOSP Vanilla
If you want to use anything but Phh Treble you need to find an Android 10 arm32 binder64 ab image.
Time and Patience.
------------------------
Spoiler: Preparation
Preparation:
In phone settings, go to about phone and last thing which says "Build Number" tap it 7 times to unlock developer options, go back and go to System, Advanced and developer options.
In developer options, scroll down to "USB Debugging" and toggle it.
Plug the phone into the computer, and on the computer go to platform-tools folder and in the toolbar (thing which shows the path to folder) type cmd.exe.
in command prompt, type in adb devices, and the phone should have a popup asking to allow this computer, check the "Always allow from this computer" option and tap OK.
When you have ADB and Fastboot and Platform-Tools on your computer download the ZIP attached below, open it and copy all the files from it into your platform-tools folder, than download the GSI, open it, copy the img file in the same platform-tools folder and rename it to system.img if you want for convinience.
---------------------
Spoiler: Procedure
Procedure:
In CMD type:
Code:
fastboot reboot bootloader
Now type these commands seperately
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Code:
fastboot reboot fastboot
Computer will say <Waiting for device> and when the phone boots into fastbootd computer will detect it
Now type in:
Code:
fastboot flash product product_gsi.img
Code:
fastboot flash system system.img
Code:
fastboot –w
Code:
fastboot reboot
If there is a wrong resolution boot screen and the phone boots congratulations your phone is now running a GSI
Delete
Smedslund said:
Delete
Click to expand...
Click to collapse
cant delete myself from what i seen so i reported myself and will get deleted at one point, i moved to here
*REMOVED LINK*
and let me know if I made the same mistake
EDIT: The thread has been moved to the right place by itself and the repost had been deleted. I am glad this is over.