[Updated/All Versions & Models!] Root OnePlus 7T Pro

[FSadino]

[/COLOR]

This command doesn't work for me:
fastboot boot pathtomagiskpatched.img

Are you sure, there shouldn't be fastboot flash boot pathtomagiskpatched.img ?

Right command is: fastboot flash boot "boot.img"

 

[forever_lol]

[/COLOR]

Right command is: fastboot flash boot "boot.ing"

That's what I thought, there's typo in OP ("flash" is missing). Thank you sir. :good:

 

[Lossyx]

That's what I thought, there's typo in OP ("flash" is missing). Thank you sir. :good:

That's not a typo. Sometimes flashing an image can cause issues with WiFi, so it's always best to boot the image and do a direct install in Magisk manager to avoid any issues.

 

[forever_lol]

That's not a typo. Sometimes flashing an image can cause issues with WiFi, so it's always best to boot the image and do a direct install in Magisk manager to avoid any issues.

Thanks but is it really possible to boot a boot.img? Recovery image i can understand, but boot.img? I always get an error.

 

[Lossyx]

Thanks but is it really possible to boot a boot.img? Recovery image i can understand, but boot.img? I always get an error.

Of course, it is. It's one of the main purposes of it. Must be something on your end.

 

[forever_lol]

Of course, it is. It's one of the main purposes of it. Must be something on your end.

Thnx, i'll give it another try then. so "fastboot boot magiskpatchedboot.img" is correct command?

 

[Donny8485]

....
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
....

There should be a warning for point 1.
A novice user could land on OP page. See point 1. Go off search Internet, see a site where they provide instructions without any warning that it wipes data Yes, it's not your problem, because that site should've provided the warning. But it's courteous to provide warning. For one, it will save someone a lot of time. User can decide whether to spend more time on this or not, once they know it wipes all data.

 

[Lossyx]

There should be a warning for point 1.
A novice user could land on OP page. See point 1. Go off search Internet, see a site where they provide instructions without any warning that it wipes data Yes, it's not your problem, because that site should've provided the warning. But it's courteous to provide warning. For one, it will save someone a lot of time. User can decide whether to spend more time on this or not, once they know it wipes all data.

You get a clear warning on your device, just before you actually unlock the bootloader, and you even have to confirm it.

 

[escalebur]

Problem dump boot.img

Hi,

According to the tuto, the first step was to dump the boot.img file, unfortunately the adb tells me that i have an issue with the permission : permission denied

>> adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
>> permission denied

i tried different ways : "adb root" or "adb shell su" ..

any idea, please i have to root my hotdog phone

thanks a lot :good:

 

[Lossyx]

Hi,

According to the tuto, the first step was to dump the boot.img file, unfortunately the adb tells me that i have an issue with the permission : permission denied
>> adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img>> permission denied


i tried different ways : "adb root" or "adb shell su" ..

any idea, please i have to root my hotdog phone

thanks a lot :good:

OP refuses to acknowledge that his guide is wrong.
Check my 2nd post;
https://forum.xda-developers.com/7t...ot-image-oneplus-7t-pro-t3986351/post80589873

Alternatively, you can browse Guides section for a patched image for your version..
Note though; the image might not matter if you 'fastboot boot' the boot image (not flash). Then from Magisk Managers, click install > Direct Install and reboot.

 

[Donny8485]

Works like a charm!

Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.

Thanks to everyone who made this possible so soon!

You get a clear warning on your device, just before you actually unlock the bootloader, and you even have to confirm it.

If you don't mention here about the wiping of data, for someone doing this first time, the clear warning will be when it dawns on them about doing a full backup. Thanks for that.

 

[MatthewOffical]

I tried to root it on 10.0.10, done it, but sim and wifi not working after booting from patched boot image. Is this magisk specific problem or not?

 

[knpk13]

I tried to root it on 10.0.10, done it, but sim and wifi not working after booting from patched boot image. Is this magisk specific problem or not?

If you use any modules, check/disable them (or try core only mode), magisk works for me on the latest OTA. No such issues.

 

[MatthewOffical]

If you use any modules, check/disable them (or try core only mode), magisk works for me on the latest OTA. No such issues.

I did a full clean, no modules or other liked that. Boot from patched image and after than most every way to the internet, so I can't install magisk properly

 

[MatthewOffical]

If you use any modules, check/disable them (or try core only mode), magisk works for me on the latest OTA. No such issues.

Do you use OOS 10.0.10? Can you send me your patched boot.img file? I'll try to boot from it

 

[knpk13]

Do you use OOS 10.0.10? Can you send me your patched boot.img file? I'll try to boot from it

I'm using the Indian equivalent of 10.0.10 , which is 10.3.4 , might not a good idea to try mine. I'd be patching it the same way as you so doesn't make a difference. Blame OnePlus for the regional variants.

 

[cowgaR]

[edit] typos, added one safeguard step to TWRP
[edit2] personally not using OOS so corrected TWRP section, credit to Lossyx

Do you use OOS 10.0.10? Can you send me your patched boot.img file? I'll try to boot from it

Did you just boot from patched boot.img or you booted from already flashed boot.img?

a). If you just booted, restart the phone, you will have original kernel back. Install Magisk Manager APK and take it from there.
b). If you flashed someone's else patched boot.img, it is your problem. You should flash only yours patched boot.img from your version of OOS or LOS or anything. If you have used yours, this begs the question, how did you patched your kernel, if you don't have Magisk Manager installed on your phone.

It has been mentioned multiple times in this thread (thanks go to respective ppl) that there are 3 ways to do it, from easiest to the most reliable one:

EASY WAY - Does not work on OOS as advised by Lossyx
1. Place latest Magisk-v20.4.zip on your phone
2. Boot to TWRP 3.4.0-2 (temporarily only, do not flash it on your phone!) and flash the Magisk zip via TWRP Install method
3. Reboot to System
4. [added] Open Magisk Manager and click to Install it (even though it might say is install already) and execute Direct Install. Advised by folks, won't hurt.
5. Restart.
6. Done. Your phone should be rooted and Magisk Manager APK should be also installed.


MODERATE WAY
1. Install latest Magisk Manager APK on your phone (7.5.1)
2. Extract your own boot image and place it on your phone (guides in this thread)
Alternatively on your PC, download exact OOS version .zip that is present on your phone from official website, extract it, navigate to payload.bin and take your boot.img from there using payload dumper. Video linked in this post.
3. Patch it with Magisk Manager (guides in this thread) and upload to your computer (say as magisk_patched_boot.img)
4. Enter fastbootd
5. Flash your patched kernel: fastboot flash boot magisk_patched_boot.img
6. Reboot your phone. You should be rooted.
7. [added] Open Magisk Manager and click to Install it (even though it might say is install already) and execute Direct Install. Advised by video guide, won't hurt I guess.
8. Restart

STABLE WAY
Same as moderate way, but you skip point 5. You do not flash the patched-boot.img (for whatever reason) but boot your phone temporarily with this rooted kernel you have prepared.
5. Boot with patched kernel: fastboot boot magisk_patched_boot.img
6. Open Magisk Manager on your phone
7. Execute Direct Flash (guide in this thread) to patch your current untouched kernel
8. Reboot


According to the info in this thread, stable way does not produce wifi/network problems - but those are usually due to people mixing the process or making way too much errors in the process while rooting (like using someone's else OOS 10.0.9 kernel and they expect it work on their OOS 10.0.10)

 

[Lossyx]

Did you just boot from patched boot.img or you booted from already flashed boot.img?

a). If you just booted, restart the phone, you will have original kernel back. Install Magisk Manager APK and take it from there.
b). If you flashed someone's else patched boot.img, it is your problem. You should flash only yours patched boot.img from your version of OOS or LOS or anything. If you have used yours, this begs the question, how did you patched your kernel, if you don't have Magisk Manager installed on your phone.

It has been mentioned multiple times in this thread (thanks go to respective ppl) that there are 3 ways to do it, from easiest to the most reliable one:

EASY WAY
1. Place latest Magisk-v20.4.zip on your phone
2. Boot to TWRP 3.4.0-2 (temporarily only, do not flash it on your phone!) and flash the Magisk zip via TWRP Install method
3. Reboot to System
4. Done. Your phone should be rooted and Magisk Manager APK should be also installed.


MODERATE WAY
1. Install latest Magisk Manager APK on your phone (7.5.1)
2. Extract your own boot image and place it on your phone (guides in this thread)
3. Patch it with Magisk Manager (guides in this thread) and upload to your computer (say as patched_boot.img)
4. Enter fastbootd
5. Flash your patched kernel: fastboot flash boot patched-boot.img
6. Reboot your phone. You should be rooted.

STABLE WAY
Same as moderate way, but you skip point 5. You do not flash the patched-boot.img (for whatever reason) but boot your phone temporarily with this rooted kernel you have prepared.
5. Boot with patched kernel: fastboot boot patched-boot.img
6. Open Magisk Manager on your phone
7. Execute Direct Flash (guide in this thread) to patch your current untouched kernel
8. Reboot


According to the info in this thread, stable way does not produce wifi/network problems - but those are usually due to people mixing the process or making way too much errors in the process while rooting (like using someone's else OOS 10.0.9 kernel and they expect it work on their OOS 10.0.10)

You should probably add that easy way only works on custom ROMs, since OOS decryption does not work on 7T/Pro.

Otherwise it's a good write-up, and I myself recommend the Stable Way, never had problems with it.

 

[hyperorb]

What does the steps mean ?

6. Open Magisk Manager on your phone
7. Execute Direct Flash (guide in this thread) to patch your current untouched kernel

What do we (direct)flash -- The patched image or Magisk Image ??

 

[FSadino]

What does the steps mean ?

What do we (direct)flash -- The patched image or Magisk Image ??

You patch your current kernel