[Recovery][Stock OOS 10.0.3BA]Oxygen OS Stock recovery with ADB enabled

vooze

Member
Jun 27, 2013
28
7
0
Aarhus
Unfortunately my "Pro" is in exchange due to a fault, expect it to be back this weekend so I can update the recovery to 10.0.4, or I could provide one this evening but without testing :)
Sorry to hear that. But don't worry - I can wait. Does not have a bootloop, just wanted to know how careful I should with modules ;)
 

s3axel

Senior Member
Mar 4, 2013
457
203
63
Sorry to hear that. But don't worry - I can wait. Does not have a bootloop, just wanted to know how careful I should with modules ;)
Well, as long as you have the original, unmodified recovery available you can always try to flash the existing modified 10.0.3 recovery... If it doesn't work just go back to fastboot and re-flash the original recovery again...

I'll update OP this evening with a modified 10.0.4 :)
 

vooze

Member
Jun 27, 2013
28
7
0
Aarhus
Well, as long as you have the original, unmodified recovery available you can always try to flash the existing modified 10.0.3 recovery... If it doesn't work just go back to fastboot and re-flash the original recovery again...

I'll update OP this evening with a modified 10.0.4 :)
If you drop both the original 1.0.4 (not sure where I can find it) and your modified one, I'll test and report back :)
 
  • Like
Reactions: s3axel

slapman

Senior Member
Sep 20, 2011
296
47
48
Temple Terrace
I was in a bootloop, because of the GCam aux Magisk module. For me it was the same at first attempt. I installed with
Code:
fastboot flash recovery OP7TP_StockRecovery_ADB_nosec.img
After that I rebooted to recovery. I also did not get a password prompt. I connected with
Code:
adb shell
but /data was empty. Because I wanted to see if my system still works without Magisk, I booted with the unmodified boot.img by using
Code:
fastboot boot boot.img
System came up without Magisk and was usable. After that I rebooted and it got stuck at fastboot screen again. I tried one more time to select recovery from fastboot screen and it asked me for password. Since I don't have encryption I just tried to connect again with
Code:
adb shell
This time /data was properly mounted and I was able to delete the Magisk module. After that I rebooted to system with
Code:
adb reboot
and now I have my fully functional system back. I don't know why it didn't work in the first attempt but this is awesome.
@s3axel you made my day! Thank you very much!!! Your work is appreciated!
Hi, I'm very hesitant to flash any modules through Magisk anymore. there should be a list available for what not to install this is my sixth time reinstalling from OS from scratch. I couldn't get this method to work it wouldn't boot to recovery., one thing I'm not sure is there a command or just select it on the phone? Well, I selected on the phone and put in a password and nothing. I appreciate all these methods and the work the developers have put into them. I guess I have one of those brains that cant grasp this stuff. Oh well reinstalling and leaving Magisk alone. LOL
 

tibcsi0407

Senior Member
Feb 4, 2013
372
296
0
Nyíregyháza
Hi, I'm very hesitant to flash any modules through Magisk anymore. there should be a list available for what not to install this is my sixth time reinstalling from OS from scratch. I couldn't get this method to work it wouldn't boot to recovery., one thing I'm not sure is there a command or just select it on the phone? Well, I selected on the phone and put in a password and nothing. I appreciate all these methods and the work the developers have put into them. I guess I have one of those brains that cant grasp this stuff. Oh well reinstalling and leaving Magisk alone. LOL
Got softbrick too. Now the latest patched recovery doesn't decrypt, so I can't remove the module from shell.
Had to boot original boot.img, but as soon as I boot the patched boot, it will brick it.
Now I will reflash the full OTA, hope it will remove the Magisk module (Viper..)
 

s3axel

Senior Member
Mar 4, 2013
457
203
63
Got softbrick too. Now the latest patched recovery doesn't decrypt, so I can't remove the module from shell.
Hmm, thats strange. My device (EU OP7T Pro with 10.0.4BA) is encrypted and I just tried the recovery, it decrypts and fully works as intended...
A few questions: Your device directly jumps to the recovery menu ? You did flash the recovery ? (fastboot booting it is not sufficient !)
 

tibcsi0407

Senior Member
Feb 4, 2013
372
296
0
Nyíregyháza
Hmm, thats strange. My device (EU OP7T Pro with 10.0.4BA) is encrypted and I just tried the recovery, it decrypts and fully works as intended...
A few questions: Your device directly jumps to the recovery menu ? You did flash the recovery ? (fastboot booting it is not sufficient !)
Solved it by reflashing the ROM and reflashing the recovery.
It was really strange.
 

Dacoco

Senior Member
Dec 8, 2010
547
22
0
Hi there,

thanks for the great work! I would create it by myself but just to know:

Can I use your modified recovery.img for a HD1910 China Variant with 10.0.4.HD01AA?

Also what is the encryption password? Is it just the PIN for unlocking the phone? I always used decrypted fully rooted phones (and formatted data in twrp) so this is my first "just rooted" phone with encrypted data.

Thanks a lot
 

enricojacko

Member
May 16, 2007
47
2
28
Milano (MI)
Good morning.
I just got my OnePlus 7T PRO. Model HD1910 . Build Oxygen OS Global 10.0.4.HD01AA Global.
Is it possible to use this recovery to format DATA from ADB to permanently decrypt the device? What would be the correct procedure in case?
Thank you.
 

slapman

Senior Member
Sep 20, 2011
296
47
48
Temple Terrace
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery from the 10.0.1BA package but with ADB enabled.

Prerequisites:
  • Oneplus 7T Pro :)
  • unlocked bootloader
  • access to fastboot on the phone
  • adb and fastboot

Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <recovery_filename.img>
(when taking the file as downloaded the filename is "OP7TP_StockRecovery_ADB_nosec.img")

Uninstall:
Same as installation, but flash the original stock recovery instead.

Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.

Downloads:

10.0.3 Firmware
  • Modified 10.0.3 recovery from GDrive
  • Original 10.0.3 stock recovery from Gdrive
10.0.4 Firmware
  • Modified 10.0.4 recovery from GDrive
  • Original 10.0.4 stock recovery from Gdrive

Notes of caution:
  • ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
  • with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing ;)

Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
Hi, first of all, thank you for your thread and the stock and modified recovery files. I successfully installed the modified recovery but my problem is when I'm in recovery mode when I type in the CMD prompt adb shell what is the command to access the Magisk modules cause when I type /data/adb/modules I get this "/system/bin/sh: /data/adb/modules: can't execute: Is a directory". Any help with this would be appreciated thanks
 

Lossyx

Senior Member
Jan 14, 2014
1,347
516
133
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery from the 10.0.1BA package but with ADB enabled.

Prerequisites:
Oneplus 7T Pro :)
unlocked bootloader
access to fastboot on the phone
adb and fastboot


Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
(when taking the file as downloaded the filename is "OP7TP_StockRecovery_ADB_nosec.img")

Uninstall:
Same as installation, but flash the original stock recovery instead.

Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using

Hi, first of all, thank you for your thread and the stock and modified recovery files. I successfully installed the modified recovery but my problem is when I'm in recovery mode when I type in the CMD prompt adb shell what is the command to access the Magisk modules cause when I type /data/adb/modules I get this "/system/bin/sh: /data/adb/modules: can't execute: Is a directory". Any help with this would be appreciated thanks
You need to change to that directory with "cd data/adb/modules".

Sent from my OnePlus7TPro using XDA Labs
 
  • Like
Reactions: slapman