[GUIDE] Full process of installing Magisk & TWRP on a OnePlus 7 Pro (TMOBILE SUPPORT)

[LoganDark]

New problem, OEM unlocking is greyed out in the options on the developer preview...

EDIT: I'm a retard and didn't follow instructions. Ignore.

Big oof? What instructions did you forget? I'm curious now.

You seem to have had an updater icon in your status bar, did you forget to reboot?

 

[r4w0ne]

Big oof? What instructions did you forget? I'm curious now.

You seem to have had an updater icon in your status bar, did you forget to reboot?

Forgot to move the files and update to developer preview... Now I am stuck trying to get the USB drivers working for fastboot. I wish this stuff was more compatable for my linux machine so i didn't have to use my backup work laptop. Samsung, Google and different version of OnePlus drivers ain't working so I'm downloading every fishy internet driver i can to make it work.

 

[LoganDark]

Forgot to move the files and update to developer preview... Now I am stuck trying to get the USB drivers working for fastboot. I wish this stuff was more compatable for my linux machine so i didn't have to use my backup work laptop. Samsung, Google and different version of OnePlus drivers ain't working so I'm downloading every fishy internet driver i can to make it work.

The L2 drivers should work I think? Also, you can use Linux for fastboot. Windows is only for msm, everything else is nix friendly

 

[r4w0ne]

The L2 drivers should work I think? Also, you can use Linux for fastboot. Windows is only for msm, everything else is nix friendly

Funny story, the L2 driver from your posts didn't work for me. I had to download one from the windows CAB file in this post

EDIT: ADB driver works but not fastboot. I hate windows driver store with a passion.

 

[LoganDark]

Funny story, the L2 driver from your posts didn't work for me. I had to download one from the windows CAB file in this post

But the L2 drivers contain CAB files just like that one... Oh well

 

[r4w0ne]

But the L2 drivers contain CAB files just like that one... Oh well

Alright @LoganDark here are basically my issues and how to fix if someone needs it.

1. Installing the OnePlus USB Drivers
   1. Install using the ones provided on your phone. These are the safest bet.
   2. Depending on your Windows 10 setup, this might not work correctly and the system will not give you any error indicating the driver install is failing, even in the logs. I was running a work Lenovo chinese spy machine, might not be an issue on a custom build. Follow these steps:
      1. You MUST disable Driver Signature Verification in the advanced reboot menu of WIN10.
      2. Once booted back into Windows go to C:/Program Files(x86)/OnePlus and find the .INF file.
      3. Right click the driver .INF file and install. It'll warn you about not being signed but that's okay.
      4. PROFIT!
2. Installing the L2 drivers if they are not allowing you to connect to the MSM tool properly (stuck at preload phase, etc.)
   1. Download the CAB file from this post.
   2. Install every single INF file from that zip file.
      1. *** this is probably unnecessary but that's what I did and it worked soooo...
   3. Go to Device Manager in Windows and check under Ports for a qualcomm device. This means it worked!
   4. PROFIT!

The only left.... My Magisk didn't persist after the OTA to OOS10 so I am going to figure that out right now. I'll update with my results.

 

[LoganDark]

My Magisk didn't persist after the OTA to OOS10 so I am going to figure that out right now. I'll update with my results.

Sigh... You're supposed to use Magisk to install to inactive slot after an OTA. Or else your Magisk is not in the updated OS

 

[r4w0ne]

Sigh... You're supposed to use Magisk to install to inactive slot after an OTA. Or else your Magisk is not in the updated OS

I did it backwards. Magisk, then OTA. Oops.

 

[LoganDark]

I did it backwards. Magisk, then OTA. Oops.

It's ok, you can use fastboot to change boot slot and boot back into the Magisk OS.

fastboot set_active a

If you boot back into the update, try b instead.

edit: use fastboot getvar all to see current slot

Then install to inactive slot and reboot, you will be in the update with Magisk

 

[r4w0ne]

It's ok, you can use fastboot to change boot slot and boot back into the Magisk OS.

fastboot set_active a

If you boot back into the update, try b instead.

edit: use fastboot getvar all to see current slot

Then install to inactive slot and reboot, you will be in the update with Magisk

This is good information, but I just downloaded the OTA and flashed like the original instructions. I didn't want to risk anything with stuff I didn't know a lot about.

This might be worth adding to the main post for any other common idiots out there like me who haven't rooted since before Magisk.

 

[LoganDark]

This is good information, but I just downloaded the OTA and flashed like the original instructions. I didn't want to risk anything with stuff I didn't know a lot about.

This might be worth adding to the main post for any other common idiots out there like me who haven't rooted since before Magisk.

After the initial installation of patched OOS, any further updates should be done on the phone.

 

[r4w0ne]

After the initial installation of patched OOS, any further updates should be done on the phone.

I should clarify:

after updating I downloaded the OTA from the OP website, extracted the boot.img from the payload in the update zip, patched and flashed that. This should work as a method of patching magisk in any OOS10 update but who knows. Just make sure to anyone else reading that you match the update zip you download matches your currently installed version of OOS. Mismatching can cause issues.

 

[LoganDark]

I should clarify:

after updating I downloaded the OTA from the OP website, extracted the boot.img from the payload in the update zip, patched and flashed that. This should work as a method of patching magisk in any OOS10 update but who knows. Just make sure to anyone else reading that you match the update zip you download matches your currently installed version of OOS. Mismatching can cause issues.

Yes, that's the correct method, although it would not have been required if you had used the updater and then used Magisk to "install to inactive slot"

 

[agentfusion]

Use your computer to copy both updates (developer preview & rollback) to the phone. Don't copy them to the Download folder or anything, copy them into the root (just inside the internal storage). Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.

Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use `fastboot oem unlock`. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.

Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.

I love this guide, and it works perfectly *except* for this bit. This part is a little misleading and incorrect. You copy ONLY the beta, do the local update, etc up to the part of fastboot oem unlock, because this step will wipe internal storage so if you copied both as your guide suggests, the downgrade will be gone after rebooting from the bootloader unlock.

Needs to be: copy beta->local upgrade->oem unlock enabled in settings->reboot to bootloader->fastboot oem unlock->reboot into beta again->copy downgrade->local upgrade the downgrade.

Otherwise this guide is absolute perfection. I know I'm nitpicking, but it could make newbies think they did something wrong when they follow the guide and then go "wait! the file isn't there!"

 

[LoganDark]

I love this guide, and it works perfectly *except* for this bit. This part is a little misleading and incorrect. You copy ONLY the beta, do the local update, etc up to the part of fastboot oem unlock, because this step will wipe internal storage so if you copied both as your guide suggests, the downgrade will be gone after rebooting from the bootloader unlock.

Needs to be: copy beta->local upgrade->oem unlock enabled in settings->reboot to bootloader->fastboot oem unlock->reboot into beta again->copy downgrade->local upgrade the downgrade.

Otherwise this guide is absolute perfection. I know I'm nitpicking, but it could make newbies think they did something wrong when they follow the guide and then go "wait! the file isn't there!"

Well, if you're going to nitpick, so can I!

It's actually possible to change your bootloader status without wiping the phone. If you intentionally screw up the AVB metadata (vbmeta partition) so that the phone no longer boots, you can lock and unlock the bootloader as many times as you want without wiping data.

Of course, it's not very useful to have a locked phone that can't boot. So using EDL mode (and a proper Firehose programmer outside of MSM Download Tool), I theorize that it's possible to fix the phone again to make it boot once the bootloader is successfully locked.

Likewise, it should be comparatively easy to use EDL to screw up the vbmeta of a locked phone somehow (after enabling OEM unlocking), and then just fastboot to unlock the bootloader and flash a stock one after.

But yes, otherwise you are correct. Almost nobody here would be able to pull that off, and I did miss the wipe when writing that portion of the guide. I'll correct it asap.

Edit: OP has been updated.

 

[ndragon798]

Hey I'm trying this on a GM1915 I just got off of ebay and I have been stuck on param preload in the msmdownloadtool for like 20+ minutes. Any suggestions? I unplugged and was able to reboot into the main os so I guess nothing actually happened.

 

[LoganDark]

Hey I'm trying this on a GM1915 I just got off of ebay and I have been stuck on param preload in the msmdownloadtool for like 20+ minutes. Any suggestions? I unplugged and was able to reboot into the main os so I guess nothing actually happened.

Man, a lot more people are having Windows issues than I expected. Try following the instructions in this post?