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

[Recovery][Stock OOS 11.0.1.3]Oxygen OS Stock recovery with ADB enabled

Search This thread

jhofseth

Senior Member
Feb 27, 2016
473
279
Seattle, Washington
Thanks so much for your builds every month. I don't know what I would do without them.

But I have a question regarding the latest version for OOS11. I've read that stock recovery adds the imei (and I think also a QR code) beginning with OOS11 (11.0.1.2) (and on our specific phone, HD1925).

I didn't check right after updating, installed your nosec image, did what I needed, then reinstalled the stock version you had posted, yet stock recovery looks identical to how it always has.

Just checking, are you positive you uploaded the correct file for the regular (nosec) version of 11.0.1.2? Could you please verify for me? I'd rather not find out when the next OTA comes out and I can't take it ;)

Thanks you again so much for your work every month!
The stock one is the right one, I verified the checksum:
SHA1: 0B1209AE62A7E0C9DF72460307FA40D0D083BAA6
 
  • Like
Reactions: starcms
I am aware that this question isn't relevant to this thread, but I saw in the your video tutorial that your phone booted up relatively quickly(under a min). Ever since updating to OOS11 I've seen experiencing an abnormal boot time that exceeds a min or so. Any idea on what is the issue and how I can fix this?
 
  • Like
Reactions: jhofseth

jhofseth

Senior Member
Feb 27, 2016
473
279
Seattle, Washington
I am aware that this question isn't relevant to this thread, but I saw in the your video tutorial that your phone booted up relatively quickly(under a min). Ever since updating to OOS11 I've seen experiencing an abnormal boot time that exceeds a min or so. Any idea on what is the issue and how I can fix this?
I'm not sure, I think it's probably related to some application(s) you've installed in particular. On my phone, it takes ~26 sec from poweron to pinscreen.
 
  • Like
Reactions: ofunrein1
I'm not sure, I think it's probably related to some application(s) you've installed in particular. On my phone, it takes ~26 sec from poweron to pinscreen.
Interesting, Ill take a look into it. I did also have have custom boot animations before I was unrooted by the update. Do you happen to have the boot.img for the 11.0.1.3 update?
 
  • Like
Reactions: jhofseth

starcms

Senior Member
I am aware that this question isn't relevant to this thread, but I saw in the your video tutorial that your phone booted up relatively quickly(under a min). Ever since updating to OOS11 I've seen experiencing an abnormal boot time that exceeds a min or so. Any idea on what is the issue and how I can fix this?

Factory reset is the only thing that fixes it. On my previous phone, an Essential PH-1, it eventually got to the point that it was sitting for at least 45 seconds at the stupid orange warning screen saying that it's bootloader unlocked. I disabled all Magisk modules, tried everything I could think of, only a clean install fixed it (after I bought this and went to sell it lol)

Not having any issues due to upgrade to OOS11, boot time is about the same, maybe 30 seconds from turning it on to unlock screen. But it takes another 2 minutes until it's done fully loading all background apps, maybe slightly longer than OOS10.

My phone took the upgrade to OOS11 fine with zero issues, but clearly that isn't the same for a lot of people. For those having issues with OOS11, try a simple factory reset without restoring app data backups from Google (or anywhere else) before giving up and going back to OOS10.
 
This is a stop-gap solution until we get a fully working TWRP with data decryption on the OnePlus 7T Pro 5G McLaren.

Tutorial video here (up to 4K; fullscreen recommended): https://youtu.be/rNwyb_gaByE

requirements:
*OnePlus 7T Pro 5G McLaren (HD1925)
*bootloader unlocked
*USB connected to PC with adb/fastboot

installation:
fastboot getvar all
(look for the (bootloader) current-slot text)
fastboot flash recovery_a recovery_11.0.1.3_adb_nosec.img
or
fastboot flash recovery_b recovery_11.0.1.3_adb_nosec.img

usage:
adb shell

removal:
fastboot getvar all
(look for the (bootloader) current-slot text)
fastboot flash recovery_a recovery_11.0.1.3.img
or
fastboot flash recovery_b recovery_11.0.1.3.img


recovery_11.0.1.3_adb_nosec.img.zip
https://drive.google.com/file/d/1sxZGQpXG_Fk-yK4NZmB6Im8wSxlcbSPZ/view?usp=sharing

recovery_11.0.1.3.img.zip
https://drive.google.com/file/d/1LDydnV4fdTFbzPD2orZycaYUeSeYYnT-/view?usp=sharing

OLD
recovery_11.0.1.2_adb_nosec.img.zip
https://drive.google.com/file/d/1J0jQXJhKmEiH9sLExUPb1arehXeMQGWn/view?usp=sharing

recovery_11.0.1.2.img.zip
https://drive.google.com/file/d/1Avb2y9bc0oZGVMBS40BXQ-_-efzWNJyj/view?usp=sharing

recovery_10.0.43_adb_nosec.img.zip
https://drive.google.com/file/d/1GD1QWWN_q5Lq5-O_w0OgN2jE3dG2_-M0/view?usp=sharing

recovery_10.0.43.img.zip
https://drive.google.com/file/d/1OL1oy9yb3dFE5gsWdrUQVZd5PcHi9ap-/view?usp=sharing

recovery_10.0.42_adb_nosec.img.zip
https://drive.google.com/file/d/1n7tQWR1nRp2vDwejE2dKCjHONwm32ZTs/view?usp=sharing

recovery_10.0.42.img.zip
https://drive.google.com/file/d/1IdMuwj-onVeUYGe0u0XjlIbU0E4mnz0-/view?usp=sharing

recovery_10.0.41_adb_nosec.img.zip
https://drive.google.com/file/d/1zRBMHHIDmTCtReTUCorhNDknzwU4Z5Jf/view?usp=sharing

recovery_10.0.41.img.zip
https://drive.google.com/file/d/1jPC9R5ZY8obIXfOH9k7ghnm3oCsBfTCs/view?usp=sharing

recovery_10.0.40_adb_nosec.img.zip
https://drive.google.com/file/d/1k_GSg4EBf8ejhA2Yk6JInnd8oQTz4WPE/view?usp=sharing

recovery_10.0.40.img.zip
https://drive.google.com/file/d/12YSaIiQhroRXehGR3xi4nzBUx7oeNiNL/view?usp=sharing

recovery_10.0.39_adb_nosec.img.zip
https://drive.google.com/file/d/1eqPCZ9ExaEDpNt3huTmU07z2WVKR-i72/view?usp=sharing

recovery_10.0.39.img.zip
https://drive.google.com/file/d/1Elpc8jv1kYeNAMWyU1nJyjkzG0rd6zTg/view?usp=sharing

recovery_10.0.37_adb_nosec.img.zip
https://drive.google.com/file/d/1CUplbaMHpSV49siLzK3tSN-tmtfYJ2jd/view?usp=sharing

recovery_10.0.37.img.zip
https://drive.google.com/file/d/1z7uG-F7SedzAJwBHn6pY81Nqa44vkUcz/view?usp=sharing

recovery_10.0.36_adb_nosec.img.zip
https://drive.google.com/file/d/1AHy863Z_CFBHfRNSAhYN7E0UFCzU-YHs/view?usp=sharing

recovery_10.0.36.img.zip
https://drive.google.com/file/d/1AIk09glW0ZVLDWastbQVEXGxxJLZ6sqp/view?usp=sharing

recovery_10.0.35_adb_nosec.img.zip
https://drive.google.com/file/d/1UxRvakxsKHZ-pEaZQcGy6YiL_23jLscK/view?usp=sharing

recovery_10.0.35.img.zip
https://drive.google.com/file/d/1Ut-JqzAJKz7jNvb6bp14zO-L0haVjz57/view?usp=sharing

recovery_10.0.34_adb_nosec.img.zip
https://drive.google.com/open?id=16S3eJS3WrKIekJAijFtIgP4a34sMJE78

recovery_10.0.34.img.zip
https://drive.google.com/open?id=1yCvTsT-2NKzToGUn_-1FtiMbNur6Livw

recovery_10.0.31_adb_nosec.img.zip
https://drive.google.com/open?id=1-H92H_TIQUJjQbIElQLsryRq0299lM1k

recovery_10.0.31.img.zip
https://drive.google.com/open?id=1Lp4wuql8j0FwD1I1OPj1r4ebi1Ti3XTg

recovery_10.0.27_adb_nosec.img.zip
https://drive.google.com/open?id=13sp8k6Vk6n6v8SpnjvO9sIFr_5mJ6UYV

recovery_10.0.27.img.zip
https://drive.google.com/open?id=13uRw5yfsBiWJ_nviiXB3Qk3yLl7IPxQG

recovery_10.0.25_adb_nosec.img.zip
https://drive.google.com/open?id=1CapeyuagSK0XxKbI-OuRSXjyKf9ylstV

recovery_10.0.25.img.zip
https://drive.google.com/open?id=1CaNNsZ4q3QVKrzzJ8S7LW5r8TUPuW7OC

recovery_10.0.19_adb_nosec.img.zip
https://drive.google.com/open?id=1-gfQlKcHkIoTzWgHaGenyda6AU614dct

recovery_10.0.19.img.zip
https://drive.google.com/open?id=10Nal33Bw5q_dpBQSbdjKpizGghAV4Wda

Android SDK Platform-Tools
https://developer.android.com/studio/releases/platform-tools
-----------------------------------------------------------------
Special thanks to @aer0zer0 for his input
and to @osm0sis for his: [TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux/Mac]
https://forum.xda-developers.com/showthread.php?t=2073775
Hi does it work on

Unlocked OnePlus 7T 5G McLaren 256GB Papaya Orange (T-Mobile)

 

batpoil

Senior Member
Jun 27, 2018
69
9
I'm looking to get back in the mod game with this phone. Anything in particular that I should be aware of? Is it true that the 7t can be rooted and still pass safetynet for banking apps? Thanks!
 

starcms

Senior Member
I'm looking to get back in the mod game with this phone. Anything in particular that I should be aware of? Is it true that the 7t can be rooted and still pass safetynet for banking apps? Thanks!

Yes, with Magisk Hide enabled it passes no problem. Just be sure to backup your persist partition before doing anything and store a copy off the phone. Instructions are in the first couple posts of most of the custom ROM threads.

Just fyi, if you have a 7T, you are in the wrong forums. These forums are specifically for the 7T Pro 5G McLaren from T-Mobile.
 

batpoil

Senior Member
Jun 27, 2018
69
9
Thanks for this! No I'm in the right place, looking at the Mclaren's version since I needed the 256g version. Thanks a lot!!
Yes, with Magisk Hide enabled it passes no problem. Just be sure to backup your persist partition before doing anything and store a copy off the phone. Instructions are in the first couple posts of most of the custom ROM threads.

Just fyi, if you have a 7T, you are in the wrong forums. These forums are specifically for the 7T Pro 5G McLaren from T-Mobile.
 

zintegy

Member
Jul 29, 2021
8
0
I'm pretty sure I've flashed my 1925 with a recovery that makes it think it's a 1917, so I've been unable to use the MSM tool. Would you expect this approach to undo this mistake to the point where MSM works to reset my phone entirely? Do you have a different suggestion?
 

starcms

Senior Member
I'm pretty sure I've flashed my 1925 with a recovery that makes it think it's a 1917, so I've been unable to use the MSM tool. Would you expect this approach to undo this mistake to the point where MSM works to reset my phone entirely? Do you have a different suggestion?

TWRP Recovery has no effect on what model you have or what model your phone thinks it is. The same exact version works on all 7T/7T Pro and even for our T-Mobile HD1925. The latest version even supports full decryption when running stock OOS11.

Recovery is on a completely separate partition on our device, so altering it will have no effect on booting successfully and cannot change what device Android thinks you have (i.e. a 1917 instead of 1925)
 

starcms

Senior Member
I'm pretty sure I've flashed my 1925 with a recovery that makes it think it's a 1917, so I've been unable to use the MSM tool. Would you expect this approach to undo this mistake to the point where MSM works to reset my phone entirely? Do you have a different suggestion?

It also has nothing to do with the MSM restore tool not working properly. You need to follow the directions to the letter and ensure you have the correct drivers installed. If you see an exclamation point by any related drivers in device manager while in EFS mode, you have the wrong version of drivers installed on your PC. Plenty of threads on how to get it working.
 

Top Liked Posts