[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)

Search This thread

iankscorpio

Member
Jan 20, 2015
6
1
23
Question: Would the smart approach be to wait until "mauronofrio" (dev who maintains twrp) to release a build for oneplus 8t? Reason being is that I'm getting tired of re-downloading all my apps over my slow ass wifi.
I was able to root my phone you seen the broken torque package to make a boot image but when I unlock the bootloader it did wipe my device and so I'm wondering now if I could backup my apps cuz I went ahead and unrooted it I restored it and loaded my apps back up cuz call of duty mobile kept crashing on me and I didn't know why
 

Mpolo87

Member
Dec 16, 2017
16
39
33
I can't understand this sentence:


What does it mean? If I want to root it is because I don't have root yet 🤔

To modify the system boot.img to enable root, you have to have elevated permissions- which you don't have by default. Making a copy of the boot.img and then transferring it back to your device as a standard file without those same protections lets you patch it to enable su. Then you use adb to boot using the patched boot.img (without overwriting your existing boot.img) so that while you're temporarily booted with it you do have root access- at which point you just patch your internal boot.img using the same tool, giving you permanent root.

It's also possible to skip the step of temporarily booting from the patched boot.img and instead just overwrite the unpatched boot.img, but that's risky- it's better to try booting from it first so that if it's not working properly you don't soft brick your phone.
 
  • Like
Reactions: yeyitin

cdragon1982

Member
Feb 16, 2020
7
1
1
thank you this worked without a problem. had to change two file names 1. the img to img.jpg so i could upload to my drive cause my pc wouldent see the file. 2.the img again magisk made magisk_patched_oMFtJ.img i changed it to magisk_patched_a.img . i am using an 8T KB2007 T-mobile. thanks again.
 

yeyitin

Member
Aug 30, 2011
7
2
23
Madrid
I was able to root with this method no problem at all. After the game I play COD mobile would crash randomly. I was wondering if maybe it's because the bootloader is unlocked. Can I lock the bootloader now that I have root. It's greyed out now in developer settings.

Regarding COD mobile crashing randomly, it is probably due to root. Activision implemented a root control a few months back. Since then, it controls if your device is rooted and if it does find it is rooted, it ends the game and forces close.
I had the same issue in my OP 5T and I solved it following these instructions.
 

dogmatism

Senior Member
Dec 20, 2006
290
145
73
This worked well thanks op.

At start after booting the partially working twrp, my computer didn't recognize the adb connection. I simply switched to my original cable which had a c port for the computer as well, and there it appeared.
 

mad4some

Senior Member
Dec 10, 2012
522
160
73
East TN
Ok, brand new OP8t from swappa ($560!!) just followed this guide and success! :D much thanks OP. I probably should have taken an available update before doing this but did not....So if taking an OTA update will break root, what is the easiest to get it back, redo this guide? or something simpler?...
 

yeyitin

Member
Aug 30, 2011
7
2
23
Madrid
Ok, brand new OP8t from swappa ($560!!) just followed this guide and success! :D much thanks OP. I probably should have taken an available update before doing this but did not....So if taking an OTA update will break root, what is the easiest to get it back, redo this guide? or something simpler?...


Check the end of this post from another thread, it worked for me.
 
  • Like
Reactions: mad4some

replica9000

Senior Member
May 31, 2009
2,159
557
193
Check the end of this post from another thread, it worked for me.

I've tried updating with the OTA. Wether I update over WiFi, or try to apply from a local file, it always fails. I've even tried booting while un-rooted. I've seen others have had the same issue. They were able to update only after re-locking the bootloader. I'd rather not as it would wipe the device again. It seems I may have to wait for OnePlus to release another full update for the KB2005 variant.
 
  • Like
Reactions: mad4some

mad4some

Senior Member
Dec 10, 2012
522
160
73
East TN
Check the end of this post from another thread, it worked for me.
Thanks much, it's looking to me like a rabbit hole with OOS updates and root so I am not going to go down it o_O.......I have tried on each oneplus phone I've owned (5 now) to like Oxygen but each time I end up right back to custom rom's. A big fan of crDroid and it's available, so I'll be going that route.
 
  • Like
Reactions: Lz3807775t

xb360

Senior Member
Oct 18, 2010
209
25
58
I've tried updating with the OTA. Wether I update over WiFi, or try to apply from a local file, it always fails. I've even tried booting while un-rooted. I've seen others have had the same issue. They were able to update only after re-locking the bootloader. I'd rather not as it would wipe the device again. It seems I may have to wait for OnePlus to release another full update for the KB2005 variant.
I just updated. I remove root (restore image) from Magisk first then reboot. After that the OTA can be installed. No need to re-locking the bootloader.

After that have to do the whole steps from OP again to gain root.
 

replica9000

Senior Member
May 31, 2009
2,159
557
193
I just updated. I remove root (restore image) from Magisk first then reboot. After that the OTA can be installed. No need to re-locking the bootloader.

After that have to do the whole steps from OP again to gain root.

I was able to update when the full OTA was released, but not the incremental OTA. After install completed, i installed Magisk to the inactive slot before reboot. After reboot I had root already.
 

druguman

Member
Jan 2, 2011
22
9
23
Miami
Ok, I just completely rewrote the guide to be simpler, it has more explanations and context and should be easier to follow. And yes, you could technically flash the boot.img but it's safer to boot from it so you don't brick your device if there's a problem with it.
What could be the problem?
c:\Android>fastboot boot magisk_patched-22006_1iG20.img
Sending 'boot.img' (98304 KB) OKAY [ 3.149s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
 

druguman

Member
Jan 2, 2011
22
9
23
Miami
What could be the problem?
c:\Android>fastboot boot magisk_patched-22006_1iG20.img
Sending 'boot.img' (98304 KB) OKAY [ 3.149s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
I found the answer:
fastboot boot only works from bootloader, it doesn't work from fastbootd.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 29
    CAVEAT
    I've only tested this on my device (KB2005 / KB05AA), but it should be universally helpful as it's using your own boot.img so there's no need to find a matching package for your variant and os version.

    CREDIT
    The steps were buried across a few threads, I'm posting this so it'll be easier for others to find the information. All credit goes to xb360, FullOfHell, and TheUnkn0wn.

    INFO
    The basic rundown is:
    1. Use the semi-broken TWRP package to give yourself temporary su access through adb.
    2. Extract the boot.img your phone is currently using to your pc.
    3. Reboot to OxygenOS, copy over the boot.img you just extracted and then use Magisk to patch it.
    4. Copy the boot.img back to your pc and use adb to temporarily boot your phone with it, giving you root access until reboot.
    5. Use your temporary root access to allow Magisk to patch your internal as-yet unmodified boot.img to give you permanent root.

    There seems to be some confusion in the thread, I'll try to clear up what's happening and why:
    • The primary issue at hand is that you can't root your device without already having root privileges, for security reasons. Without a custom recovery like TWRP, there are a few more steps than usual (but mostly simple stuff).
    • Because we don't flash anything with this guide, it shouldn't cause any permanent bootloops if you use the wrong boot.img, if you get stuck in one just power cycle your phone.
    • Updating with OTAs should be the same process as the other guides here.
    • Because of changes in Android, devices that launched with Android 10 and above will not allow you to modify the system partition, even with root. This is not a fault of this rooting method.

    Prerequisites:
    • ADB and Fastboot installed.
    • An unlocked bootloader and USB debugging enabled.

    ________________________________________________________

    STEPS:

    1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.

    2. On your computer open a terminal/cmd prompt. Set the directory (on your pc) you want to work from, I'm using the desktop:


    for Windows, type cd C:\Users\Yourname\Desktop
    for Mac, type cd desktop or cd /Users/yourname/Desktop
    To usb adb and fastboot commands outside of the folder those programs are located in, you'll need to add their location to the PATH list so your terminal can still find them when it's pointing to a different folder. If you want to skip this step, set the directory to the folder that contains adb instead of the desktop.

    3. Next, use the terminal to check which A/B partition is active on your phone:
    Code:
    fastboot getvar all

    a. You'll find it on this line: (bootloader) current-slot:a/b
    b. For simplicity I'll be referring to boot_a.img throughout the guide, make sure to use boot_b.img if that's the one marked as active on your device.

    4. Download the semi-broken TWRP package to your desktop. We'll be using it to extract a copy of your active boot_a.img. It will give you temporary su access via adb, but there won't be a gui. Only boot from it, DO NOT FLASH IT:
    Code:
    fastboot boot recovery.img
    adb shell
    dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
    exit
    adb pull /sdcard/boot_a.img boot_a.img
    adb reboot


    5. Copy the extracted boot_a.img file to a user accessible area of your phone, like your downloads folder.

    6. Install the latest Magisk Canary apk on your phone. Open it and:

    a. Select the Install option.
    b. Use Select and Patch a File on boot_a.img

    7. Copy the patched magisk_patched_a.img file back to your computer. In terminal, type adb reboot bootloader to get back to fastboot mode.

    8. Temporarily boot with the patched image that corresponds to the active partition, DO NOT FLASH IT:
    Code:
    fastboot boot magisk_patched_a.img

    You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.

    9. By booting with the patched image, you now have temporary root access. To make it permanent open Magisk:
    a. Select the Install option.
    b. Use Direct Install (Recommended) to root your internal boot.img

    10. Reboot and verify it worked.
    3
    I'm a little confused also about rooting the 8t. Couple of threads refer to using payload dumper. Others refer to using the broken twrp method. One produces one boot image while the other produces two. I went with the payload dump method and got the boot image. Just not ready to pull the trigger yet I guess. Seems the payload dump way has worked for many according to different threads.
    They're two different approaches to the same problem, the crux of it is that you can't root without already having root access which is the problem all of the guides are trying to solve. Without having a working custom recovery like TWRP, we have some extra steps to get there.

    The other methods are taking the OTA update pushed to your phone and using Payload Dumper to extract the boot.img, everything after that is pretty much identical to this guide. The difference is that because there are multiple variants of the device all running different roms, those guides are a bit confusing, especially when it comes to cases like KB2005 where OTAs are only incremental and don't even contain the boot.img you need.

    This skips all that extra work with Payload Dumper and just pulls the actual boot.img your phone is already using- so you already know it's the correct one for your device. I could probably update this guide to check which A/B partition is active so you only have to pull that one boot.img.
    2
    i don't understand why people keep making the exact same thread on how to root this phone.
    Because full roms aren't available for all variants, the other methods don't work if you don't have one.
    2
    Thanks for your reply. Since I have already pulled the boot image with the payload dump process I will try that route first, and if that doesn't work I will try your method. Again thanks for the reply. All in all, I guess just booting the image is no harm , no foul.
    Ok, I just completely rewrote the guide to be simpler, it has more explanations and context and should be easier to follow. And yes, you could technically flash the boot.img but it's safer to boot from it so you don't brick your device if there's a problem with it.
    1
    :rolleyes: Forgot to tag it... if an admin is able to do so I'd appreciate it.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone