Do you know if this recovery should work with 10.0.4?Check my posts, I have a post on how to delete magisk modules
Sent from my HD1913 using Tapatalk
Do you know if this recovery should work with 10.0.4?Check my posts, I have a post on how to delete magisk modules
Sent from my HD1913 using Tapatalk
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 testingDo you know if this recovery should work with 10.0.4?
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 modulesUnfortunately 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![]()
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...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![]()
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 backWell, 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![]()
Would this also work on the 7T? (non-pro)OP Updated with 10.0.4 recoveries - have fun![]()
I can do the same for the 7T, maybe within the next few days. I don't own the device, so I cannot test myself but I guess that is what a community is forWould this also work on the 7T? (non-pro)

Works perfectly. Thank you again!OP Updated with 10.0.4 recoveries - have fun![]()
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. LOLI was in a bootloop, because of the GCam aux Magisk module. For me it was the same at first attempt. I installed withAfter that I rebooted to recovery. I also did not get a password prompt. I connected withCode:fastboot flash recovery OP7TP_StockRecovery_ADB_nosec.imgbut /data was empty. Because I wanted to see if my system still works without Magisk, I booted with the unmodified boot.img by usingCode:adb shellSystem 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 withCode:fastboot boot boot.imgThis time /data was properly mounted and I was able to delete the Magisk module. After that I rebooted to system withCode:adb shelland 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.Code:adb reboot
@s3axel you made my day! Thank you very much!!! Your work is appreciated!
Got softbrick too. Now the latest patched recovery doesn't decrypt, so I can't remove the module from shell.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
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...Got softbrick too. Now the latest patched recovery doesn't decrypt, so I can't remove the module from shell.
Solved it by reflashing the ROM and reflashing the recovery.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 !)
I'm glad you could solve it :good:Solved it by reflashing the ROM and reflashing the recovery.
It was really strange.
Thank you!I'm glad you could solve it :good:
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 thanksWhile 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")Code:fastboot flash recovery <recovery_filename.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 usingto 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.Code:adb shell
Downloads:
10.0.3 Firmware
10.0.4 Firmware
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.
You need to change to that directory with "cd data/adb/modules".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