HELP - Update gone wrong - OnePlus 7T Pro (Regular & McLaren) Q & A

WAS WORKING FINE WITH:
- OOS HD01AA 10.0.7 (global)
- Stock recovery (with no ADB)
- Rooted via Magisk (had some modules installed/ active)
- EdXposed & modules working fine
- Arter kernel
- Renovate ICE (v.11) Magisk ROM
WHAT I DID:
- Downloaded OTA update HD01AA 10.0.8 (did not install or reboot yet)
- Update Magisk from v20.3 to 20.4 (direct download - did not reboot yet)
- Ensured "forced encryption/ DM-Verity" etc were ticked active (the 3rd option was unticked/ inactive)
- Used Magisk Manager to "install to inactive slot (after OTA)". (No Magisk modules inactivated or uninstalled).
- Rebooted
MY PROBLEM:
- Bootloop (I can still access stock recovery menu & Bootloader/ Fastboot)
SOLUTIONS TRIED:
- Deleted cache
- Changed active slot to A &/ or B etc - neither worked
- (Resorted to, unfortunately) Reset system data (both slots A & B; but my internal data pics vids hopefully remain intact)
I'm looking to recover my previous OOS/ data if possible or retrieve the OTA update I was trying to install.
I don't have any external back-up unfortunately. My Titanium/ contacts back up are all on the "internal memory". I would like to avoid MSM tool reset thereby loosing all.

---

Did you have renovate ice enabled when you updated?
If so that's what's causing the problem.
Use the adb enabled recovery and remove the module
Sent from my OnePlus7TPro using XDA Labs

---

Yes - Renovate ICE was still enabled during the update.
Where do I get the correct version ADB enabled recovery from please? (I checked on XDA here but cannot find one for my OOS version).

---

elmor0 said:
Yes - Renovate ICE was still enabled during the update.
Where do I get the correct version ADB enabled recovery from please? (I checked on XDA here but cannot find one for my OOS version).
Click to expand...
Click to collapse
Never install OTA when you have modules enabled.
I guess you have to clean flash OxygenOS

---

elmor0 said:
Yes - Renovate ICE was still enabled during the update.
Where do I get the correct version ADB enabled recovery from please? (I checked on XDA here but cannot find one for my OOS version).
Click to expand...
Click to collapse
Try making your own or just try flashing one of those from the thread
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs

---

(I'm using VMware as on Mac)
I have seemingly flashed stock recovery with ADB enabled (as per message on cmd window) --> when I type "adb shell" in cmd - nothing happens. I have opened the cmd window within the platform-tools folder. I have tried both in ??fastboot mode as well as in recovery mode.
Is there any way that I can confirm that I have successfully enabled adb visually on the phone itself? When I reboot to recovery it still looks exactly like stock recovery (so how to know adb enabled?).
I am trying to install either the 10.0.7 or 10.0.8 firmware .zip (I have both files). I cannot get past the 1+ start screen bootloop.

---

I managed to get out of bootloop by "flashboot flash boot boot.img" (my old 10.0.5 boot.img). My OOS update however succeeded to 10.0.8 global during this mess-up.
Now I had no reception signal or WiFi --> extracted & flashed boot.img of OOS 10.0.8 --> WiFi & reception signal now working fine.
I have up-to-date Magisk manager installed & managed to patch the stock boot.img.
Should I "flashboot flash" or "flashboot boot" (or both) the magisk_patched.img? I tried both ways, sometimes bootloop returned, other times rebooted fine but not rooted anymore.
Magisk (v20.4) is not installed --> when I try installation, I only get 2 options:
- Download .zip only (how to flash this if root gone?)
- Select & patch a file (which I have already done to generate the magisk_patched.img)
I am unable to flash the downloaded Magisk 20.4 .zip file as no longer rooted.
I'm not getting the option of "direct download" in Magisk. Force encryption/ AVB/ dm-verity are all ticked to preserve.
I cannot get ADB shell to work/ nor uninstall my previous Magisk modules (which may be causing the failure to re-root).
I managed to boot to modified TWRP recovery but nothing mounts therefore again unable to flash the downloaded Magisk.zip.
Please help (with step-by-step details) to gain root again - many thanks.

---

elmor0 said:
I managed to get out of bootloop by "flashboot flash boot boot.img" (my old 10.0.5 boot.img). My OOS update however succeeded to 10.0.8 global during this mess-up.
Now I had no reception signal or WiFi --> extracted & flashed boot.img of OOS 10.0.8 --> WiFi & reception signal now working fine.
I have up-to-date Magisk manager installed & managed to patch the stock boot.img.
Should I "flashboot flash" or "flashboot boot" (or both) the magisk_patched.img? I tried both ways, sometimes bootloop returned, other times rebooted fine but not rooted anymore.
Magisk (v20.4) is not installed --> when I try installation, I only get 2 options:
- Download .zip only (how to flash this if root gone?)
- Select & patch a file (which I have already done to generate the magisk_patched.img)
I am unable to flash the downloaded Magisk 20.4 .zip file as no longer rooted.
I'm not getting the option of "direct download" in Magisk. Force encryption/ AVB/ dm-verity are all ticked to preserve.
I cannot get ADB shell to work/ nor uninstall my previous Magisk modules (which may be causing the failure to re-root).
I managed to boot to modified TWRP recovery but nothing mounts therefore again unable to flash the downloaded Magisk.zip.
Please help (with step-by-step details) to gain root again - many thanks.
Click to expand...
Click to collapse
The rogue module is still in /data/adb/modules, unrooting does not remove the installation that's why you still have bootloop.
There are 3 ways;
1. Modded recovery
2. Boot stock img and do a factory reset
3. The slightly complicated way;
Basically booting a rooted image and in booting process it runs a command in root shell which removes the modules.
https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
If you're having problems, try tagging him with your patched image, maybe he can help you.
Sent from my OnePlus7TPro using XDA Labs

---

Thanks for the suggestions.
OPTION 1: I have tried with modded recoveries:
- Modded TWRP does not show or mount anything at all (slot A or B); shows 0 GB; any folders I can see I cannot delete or add any files to.
- Modded stock recovery (i.e with ADB enabled) just doesn't seem to ?flash or I'm doing something wrong for ADB shell to work. On the CMD window it says modified stock recovery has been flashed fine. Do I try the ADB shell commands in the same CMD folder?
(a step-by-step guide of how to use ADB shell in this context would really be appreciated).
OPTION 2 will wipe internal (personal) data so not keen on this (especially now that I cannot back-up my data with Titanium due to lack of root).
OPTION 3 - looks complicated for me; will try if having no luck with above 2.

---

elmor0 said:
Thanks for the suggestions.
OPTION 1: I have tried with modded recoveries:
- Modded TWRP does not show or mount anything at all (slot A or B); shows 0 GB; any folders I can see I cannot delete or add any files to.
- Modded stock recovery (i.e with ADB enabled) just doesn't seem to ?flash or I'm doing something wrong for ADB shell to work. On the CMD window it says modified stock recovery has been flashed fine. Do I try the ADB shell commands in the same CMD folder?
(a step-by-step guide of how to use ADB shell in this context would really be appreciated).
OPTION 2 will wipe internal (personal) data so not keen on this (especially now that I cannot back-up my data with Titanium due to lack of root).
OPTION 3 - looks complicated for me; will try if having no luck with above 2.
Click to expand...
Click to collapse
Don't bother with TWRP, it's not functional.
After flashing the modded recovery, enter recovery and type "adb shell", it should change to a #.
Sent from my OnePlus7TPro using XDA Labs

---

I'm getting there I think - baby steps.
Mistake I did with modded stock recovery was that I was not in recovery mode (which looks the same as un-modified stock recovery) whilst trying "adb shell" via CMD.
Initially, I got messages of adb server version does not match client & daemon cannot connect etc. Executing "adb kill-server" seemed to get rid of these errors.
Finally I could "adb shell" to generate the #.
When I try "ls -Ral data/adb/modules" I get message of "no such file or directory".
Just trying "ls -Ral data/" gives me:
- total 0 drwxr-xr-x 2 root root 40 2020-02-15
drwxr-xr-x 28 root root 1100 1970-01-01
How shall I proceed next?

---

elmor0 said:
I'm getting there I think - baby steps.
Mistake I did with modded stock recovery was that I was not in recovery mode (which looks the same as un-modified stock recovery) whilst trying "adb shell" via CMD.
Initially, I got messages of adb server version does not match client & daemon cannot connect etc. Executing "adb kill-server" seemed to get rid of these errors.
Finally I could "adb shell" to generate the #.
When I try "ls -Ral data/adb/modules" I get message of "no such file or directory".
Just trying "ls -Ral data/" gives me:
- total 0 drwxr-xr-x 2 root root 40 2020-02-15
drwxr-xr-x 28 root root 1100 1970-01-01
How shall I proceed next?
Click to expand...
Click to collapse
Do you get to enter a pin when entering recovery? If not you're most likely using a recovery for an older version/other version.
Sent from my OnePlus7TPro using XDA Labs

---

elmor0 said:
I'm getting there I think - baby steps.
Mistake I did with modded stock recovery was that I was not in recovery mode (which looks the same as un-modified stock recovery) whilst trying "adb shell" via CMD.
Initially, I got messages of adb server version does not match client & daemon cannot connect etc. Executing "adb kill-server" seemed to get rid of these errors.
Finally I could "adb shell" to generate the #.
When I try "ls -Ral data/adb/modules" I get message of "no such file or directory".
Just trying "ls -Ral data/" gives me:
- total 0 drwxr-xr-x 2 root root 40 2020-02-15
drwxr-xr-x 28 root root 1100 1970-01-01
How shall I proceed next?
Click to expand...
Click to collapse
Try /data/adb/modules. A "/" is missing

---

Tried to make my own modified recovery.img with ADB enabled using s3axel's instructions --> clearly I messed up as ended up with Qualcomm crash-dump error.
Thankfully, GrayJack's ADB enabled recovery worked. I managed to delete the culprit Magisk modules (Renovate ICE; xXx from previous installation; ?viper4android etc) by following this guide guide.
Now the patched Magisk .img flashed fine; rooted again (yay) - thank you @ Lossyx for persisting with me.
Back on Renovate-ICE (v.12 now) & arter97 kernel.
Phew!