• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread
Nov 9, 2021
7
1
Apologies if anyone's covered this and I've missed it, but how are folks dealing with Magisk Canary prompts to update?

When I've accepted them, they seem to break Magisk, and I've ended up downloading the full Canary latest and just installing that.

Last time I think I repatched the boot.img, but this time I ended up uninstalling the old Settings app (the previously installed version, hidden with Magisk Hide), and then I could direct install and regain root. Maybe the secret is to unhide Magisk before updating, I'm not sure. But I'd like to know how others are handling updates. Thanks.
Now that I read this, I realize doing this ↑ at least contributed to my recent misadventure. I'm used to thinking in terms of using "Stable" releases only, so, I probably did this by habit, or muscle memory. Something stupid.

I still can't resolve GPay, even after hiding Magisk and rebooting. I've scanned the threads, but the results I'm seeing don't seem to fit my specific 8T scenario.

While I'm here, what version of Magisk Canary should I/probably most people be on?

My current installed:

Magisk
Installed: 258e89c9 (23013) Zygisk: No Ramdisk: Yes

App
Latest: 7e9d4512 (23014) (22) Installed: 7e9d4512 (23014) (22) Package: oo.ft.w.vm.uk.rgxz



🤷‍♂️
 

Rootk1t

Senior Member
Jun 2, 2013
1,535
674
Now that I read this, I realize doing this ↑ at least contributed to my recent misadventure. I'm used to thinking in terms of using "Stable" releases only, so, I probably did this by habit, or muscle memory. Something stupid.

I still can't resolve GPay, even after hiding Magisk and rebooting. I've scanned the threads, but the results I'm seeing don't seem to fit my specific 8T scenario.

While I'm here, what version of Magisk Canary should I/probably most people be on?

My current installed:

Magisk
Installed: 258e89c9 (23013) Zygisk: No Ramdisk: Yes

App
Latest: 7e9d4512 (23014) (22) Installed: 7e9d4512 (23014) (22) Package: oo.ft.w.vm.uk.rgxz



🤷‍♂️
I would suggest sticking with the latest stable build v23.0.
Latest canaries have Magisk hide support dropped.
 
Nov 9, 2021
7
1
I would suggest sticking with the latest stable build v23.0.
Latest canaries have Magisk hide support dropped.
Thanks for this.

Just to clarify: Magisk Canary should only be used for the purposes of this rooting guide. Once rooted, Magisk should be set to "Stable" update channel, located in settings.

Should Magisk be un-hidden prior to switching from Canary to Stable?

Once Magisk is set to 'stable', it's generally safe to accept and install those Magisk updates going forward.

Am I continuing to use the Direct Install method when switching to the Stable Update Channel?

Have I got that right?

While I'm here, I have older (official) zips for modules (call record and YT Vanced), can those be safely installed?

Thanks in advance. Sorry about all the questions. I appreciate your time and patience.
 
Last edited:

Rootk1t

Senior Member
Jun 2, 2013
1,535
674
Thanks for this.

Just to clarify: Magisk Canary should only be used for the purposes of this rooting guide. Once rooted, Magisk should be set to "Stable" update channel, located in settings.

Should Magisk be un-hidden prior to switching from Canary to Stable?

Once Magisk is set to 'stable', it's generally safe to accept and install those Magisk updates going forward.

Am I continuing to use the Direct Install method when switching to the Stable Update Channel?

Have I got that right?

While I'm here, I have older (official) zips for modules (call record and YT Vanced), can those be safely installed?

Thanks in advance. Sorry about all the questions. I appreciate your time and patience.
Hello!

1. Starting from february i used stable builds of magisk (for usage and rooting), so canary is not necessary for rooting (android 11) anymore.
2. It is safe to use direct install method on stable update channel.
3. I see no problems with installing official zips for magisk modules on stable builds.
3. Future magisk canary (and later stable) builds have optimizations for Android 12, but at the same time will have omissions considering magisk hide (which is already absent) and magisk repository with modules.
So when updating to the next version consider what you need more magisk hide & build-in repo access or android 12 support.
 
  • Like
Reactions: Lz3807775t

skothiya

Senior Member
May 5, 2014
59
4
How can i uninstalled magisk root?
i'm not able to log in to banking apps cz it detects the root.
what should i do?
 

lloydsw

Senior Member
Feb 19, 2012
181
19
Ok, I'm bewildered. I followed this guide a couple of days ago to root my wife's new 8T, with no problem. Today I went to root my new 8T and am not making progress. Although my inclination was to short the process & just flash the patched image from her phone, I decided to do the whole-meal deal.

Everything goes well until I get to step #9. Instead of having 'direct install' available as an option, the ONLY option I have is to 'select & patch a file' as in step #6. I've gone through this whole process numerous times with the same result. I've also tried flashing the patched image with fastboot, and TWRP as well. I'm getting no indications of any error, yet I don't have root. Any ideas?

11.0.11.11KB05AA
 

lloydsw

Senior Member
Feb 19, 2012
181
19
Ok, I'm bewildered. I followed this guide a couple of days ago to root my wife's new 8T, with no problem. Today I went to root my new 8T and am not making progress. Although my inclination was to short the process & just flash the patched image from her phone, I decided to do the whole-meal deal.

Everything goes well until I get to step #9. Instead of having 'direct install' available as an option, the ONLY option I have is to 'select & patch a file' as in step #6. I've gone through this whole process numerous times with the same result. I've also tried flashing the patched image with fastboot, and TWRP as well. I'm getting no indications of any error, yet I don't have root. Any ideas?

11.0.11.11KB05AA
So update: absent any other ideas, I was prepared to MSM back to new, start over. Instead I booted into recovery , did a wipe & started this process over. Success!
 

M_Game

Member
Aug 2, 2018
18
1
OnePlus 8T
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.
Hey, twrp isn't broken anymore right? If so, what's the new process?
 

Rootk1t

Senior Member
Jun 2, 2013
1,535
674
Hey, twrp isn't broken anymore right? If so, what's the new process?
 
  • Like
Reactions: Lz3807775t

The Apostle

Senior Member
Jan 27, 2012
1,096
351
Saint Louis
OnePlus 6
OnePlus 8T
I didn't read the entire thread, so apologies if this has been posted. I used the method from this video last night and was rooted in about 6 min. Took the phone out of it's box (kb2005), updated to 11.0.11.11, then followed the video.
Zero issues.

 
  • Like
Reactions: GraphMatix

TanakaX5

Senior Member
Dec 17, 2015
73
18
Hey guys,

I have a question about updating the magisk app.
So I'm rooted and running a bunch of modules, the last time I Update the magisk App it completely ****ed up my device.
What is the correct way to Update the app?

That's my setup:

Installiert 5d6d2417 (23015)
Zygisk yes
Ramdisk yes

New 92546e8a (23016) (23)
Installed 5d6d2417 (23015)

Last time I just Hit Update and after that **** up town All the Way, had to unbrick and everything.

So, what's the correct way?

Greets,

TanakaX5
 

Top Liked Posts

  • There are no posts matching your filters.
  • 46
    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.
    4
    a couple of notes for any either newBs or old OPO users rejoining the party with a new onplus phone..
    Some prework I had to do for my OnePlus 8T KB2005
    -ensure you have the correct ADB driver installed, I installed the "15sec adb installer 1.4.2" found here on xda, watch the videos provided.
    -ensure to unlock your bootloader first (*this will wipe your device.. didn't think about that..no pain no gain...)
    -With device in bootloader/fastboot, run: fastboot flashing unlock
    -verify with your phone to accept
    -phone will reboot, just through the setup, I just skipped it all and opted for offline setup..
    -renable OEM lock and USB debug
    -restart back into bootloader/fastboot
    -now you are ready to root
    4
    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.
    3
    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.
    2
    :rolleyes: Forgot to tag it... if an admin is able to do so I'd appreciate it.