[GUIDE] ROOT OnePlus 7T Pro McLaren 5G (T-Mobile version HD1925)

[js042507]

The hardest part of using the MSM tool is making sure the drivers for you phone are installed first. It's not hard, that's just the hardest part.

I'd say the "hardest" part is getting your phone in the "fastboot" state for msm. I had a heck of a time getting it to boot in that mode.

EDIT: Qualcomm mode is the official term I guess. ?

 

[NotATreoFan]

I'd say the "hardest" part is getting your phone in the "fastboot" state for msm. I had a heck of a time getting it to boot in that mode.

EDIT: Qualcomm mode is the official term I guess.

I've only done it once on this phone, but it was so much easier than the 7 Pro. Didn't even have to fight with the drivers, which was a fresh install due to being on a brand new PC.

 

[js042507]

I've only done it once on this phone, but it was so much easier than the 7 Pro. Didn't even have to fight with the drivers, which was a fresh install due to being on a brand new PC.

Drivers were not the issue. It was the button combination and plugging in USB cable. Normally it's just hold vol - or whatever. Meh.

 

[NotATreoFan]

Drivers were not the issue. It was the button combination and plugging in USB cable. Normally it's just hold vol - or whatever. Meh.

I just use the adb command to get there.

 

[gaww]

I'd say the "hardest" part is getting your phone in the "fastboot" state for msm. I had a heck of a time getting it to boot in that mode.

EDIT: Qualcomm mode is the official term I guess. ?

Reading the instructions, it said if your W10 didn't show Qualcomm in the device manager as the driver, it could be a problem. I tried to get it installed, but Microsoft kept on installing it's one.

 

[js042507]

Reading the instructions, it said if your W10 didn't show Qualcomm in the device manager as the driver, it could be a problem. I tried to get it installed, but Microsoft kept on installing it's one.

Mine never said Qualcomm in device manager. Just make sure the tool shows connected. That should be it.

"adb reboot edl" gets into this mode I guess. That would probably be your safest method.

 

[gaww]

Mike never said Qualcomm in device manager. Just make sure the tool shows connected. That should be it.

"adb reboot edl" gets into this mode I guess. That would probably be your safest method.

I am looking at "some_random_username" s tool, and he had shown it

 

[js042507]

I am looking at "some_random_username" s tool, and he had shown it

Well, I was able to use the msm tool. I don't know. LOL

 

[gaww]

Mine never said Qualcomm in device manager. Just make sure the tool shows connected. That should be it.

"adb reboot edl" gets into this mode I guess. That would probably be your safest method.

I tried getting into that mode and it worked, so I guess I'm good to go. Starting to do backups now. When done, will still be with .27, as that's the latest MSM ROM I have seen. Since I will be un-rooted and BL locked, will it simply update to .31 ?

I think I will stay away from custom kernels for awhile, as the stock kernels I saved with their management apps did not do so, and that's why I think I could not get the update done. Just for the heck of it before I use MSM, is there a .27 stock kernel out there that could be restored ?

 

[js042507]

I tried getting into that mode and it worked, so I guess I'm good to go. Starting to do backups now. When done, will still be with .27, as that's the latest MSM ROM I have seen. Since I will be un-rooted and BL locked, will it simply update to .31 ?

I think I will stay away from custom kernels for awhile, as the stock kernels I saved with their management apps did not do so, and that's why I think I could not get the update done. Just for the heck of it before I use MSM, is there a .27 stock kernel out there that could be restored ?

Yes. Your phone should be locked and stock. Update to .31 now. Then, unlock bootloader and root like normal.

 

[gaww]

Yes. Your phone should be locked and stock. Update to .31 now. Then, unlock bootloader and root like normal.

If there was a stock .27 kernel out there, I was going to give the updae to .31 one more shot before the MSM.

 

[js042507]

If there was a stock .27 kernel out there, I was going to give the updae to .31 one more shot before the MSM.

Stock kernel is just the boot.img. I tried multiple times and ultimately had to use the MSM tool.

 

[NotATreoFan]

Stock kernel is just the boot.img. I tried multiple times and ultimately had to use the MSM tool.

Maybe one reason that is worked for me was because I never got offered the .27 OTA, so I had used MSM to revert to .19 in order to then get .27, before eventually repairing and updating to .31 OTA.

 

[js042507]

Maybe one reason that is worked for me was because I never got offered the .27 OTA, so I had used MSM to revert to .19 in order to then get .27, before eventually repairing and updating to .31 OTA.

Yeah, honestly I think the reason I couldn't update and others is because of messing around with that blu kernel. I don't know.

 

[gaww]

Stock kernel is just the boot.img. I tried multiple times and ultimately had to use the MSM tool.

Thanks again, but you are not going to believe this (yes - going to rub it in). I simply did what I had done before (your response above gave me the idea). In Magisk, I uninstalled and had it restore Images, then rebooted and updated again. It downloaded everything for .31, installed it, and rebooted - done!

Went to fastboot after that and reflashed the patched boot.img, rebooted, and all OK . I had the latest Magisn 20.4, but reinstalled it so it would still be there after reboots. As for the Magisk modules that someone said had to be uninstalled - no problems - they were there after I rebooted.

No MSM.

Again, you and NotATreoFan have been super helpful. If either of you go back to Samsung, and have some issues - I may be able to help, but I think OnePlus will be your home for some time to come.

 

[NotATreoFan]

Thanks again, but you are not going to believe this (yes - going to rub it in). I simply did what I had done before (your response above gave me the idea). In Magisk, I uninstalled and had it restore Images, then rebooted and updated again. It downloaded everything for .31, installed it, and rebooted - done!

Went to fastboot after that and reflashed the patched boot.img, rebooted, and all OK . I had the latest Magisn 20.4, but reinstalled it so it would still be there after reboots. As for the Magisk modules that someone said had to be uninstalled - no problems - they were there after I rebooted.

No MSM.

Again, you and NotATreoFan have been super helpful. If either of you go back to Samsung, and have some issues - I may be able to help, but I think OnePlus will be your home for some time to come.

Did you flash the same kernel again, or did you inject Magisk into a new copy of the .31 kernel? That have been a lot of changes recently, so I would strongly recommend using a matching kernel.

 

[js042507]

Thanks again, but you are not going to believe this (yes - going to rub it in). I simply did what I had done before (your response above gave me the idea). In Magisk, I uninstalled and had it restore Images, then rebooted and updated again. It downloaded everything for .31, installed it, and rebooted - done!

Went to fastboot after that and reflashed the patched boot.img, rebooted, and all OK . I had the latest Magisn 20.4, but reinstalled it so it would still be there after reboots. As for the Magisk modules that someone said had to be uninstalled - no problems - they were there after I rebooted.

No MSM.

Again, you and NotATreoFan have been super helpful. If either of you go back to Samsung, and have some issues - I may be able to help, but I think OnePlus will be your home for some time to come.

Interesting. Glad you were able to update successfully! I tried this too, but it never did work. Oh well. Glad you're up and running! Also, my next phone I'll probably be going back to Google. I used to have Samsung, but honestly I hate them. LOL. Last one I had for a brief period was the note 4.

 

[gaww]

Did you flash the same kernel again, or did you inject Magisk into a new copy of the .31 kernel? That have been a lot of changes recently, so I would strongly recommend using a matching kernel.

I went to Magisk only and had it uninstall/restore image, reboot, and updated. I had been - I thought - restoring saved stock kernels but they weren't.

Now for the next update, will the .27 reserve.img be OK, or should I change it to your .31 ?

 

[NotATreoFan]

I went to Magisk only and had it uninstall/restore image, reboot, and updated. I had been - I thought - restoring saved stock kernels but they weren't.

Now for the next update, will the .27 reserve.img be OK, or should I change it to your .31 ?

Didn't you already update to .31? If so, then you're all set and don't need to repair again. That is only needed if you unlock your bootloader after taking an update.

 

[gaww]

Interesting. Glad you were able to update successfully! I tried this too, but it never did work. Oh well. Glad you're up and running! Also, my next phone I'll probably be going back to Google. I used to have Samsung, but honestly I hate them. LOL. Last one I had for a brief period was the note 4.

Still have Samsung S7e and S9+, but they are Exynos, so don't have US TMo newer frequencies, and of course can't root Snapdragon, so that is why I went here. I am thinking about 8 Pro generic (not TMo if they carry it), as it seems to have the TMo frequencies, and will probably get more development.