Database Info

Booting/Recovery issues, Need help. (yes I researched)

Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?

eracet said:
Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?
Click to expand...
Click to collapse
UPDATE: When booting into TWRP 3.2.2.0 it gives me encrypted files. When booting into TWRP 3.2.3.0 it gives me non-encyrpted files and asks for password.
Booting anything to slot A gives me a load error. failed to authenticate.
Update2: Now I cannot get Bluspark TWRP or stock recovery to load VIA Fastboot. Only TWRP 3.2.3.0 works and loads correctly
Update 3: Keep having to do different versions of TWRP to get anything going, even tried OTA and did not work.
Update 4: Phone wants to boot into Qualcomm HS-USB Diagnostics mode when light is on.

Found you
Next time tag me
I'm the same guy on the oneplus forums
Send me a private message here or on the oneplus forums and I'll take it from there

Update: I have resolved the issue. Please do not post any further comments on this because
The issue is already resolved, duh

very frustrating to install lineage

i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this

Did you also FORMAT your data?

Use MSM Tool
csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.

csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Wrong order. First flash LOS, then TWRP Installer and then Magisk. When you flash LOS after TWRP and Magisk, your TWRP and root will be gone.

n2851991m said:
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.
Click to expand...
Click to collapse
crap... my link is old.. may not work.. i'll try yours.... fingers crossed

csmooth2001 said:
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
Click to expand...
Click to collapse
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.

razorshiv said:
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.
Click to expand...
Click to collapse
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
im guessing big time
is there a forum just for GM1915 ??? anywhere in the world...

csmooth2001 said:
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?.
Click to expand...
Click to collapse
yes.
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
Click to expand...
Click to collapse
flash rom, flash twrp, reboot recovery, flash magisk.
is there a forum just for GM1915 ??? anywhere in the world..
Click to expand...
Click to collapse
They are scattered around the op7pro forum. Just do a search for tmo or tmobile.

boot to other slot & sim will work

Android 10 update broke G7Power (Magisk "Restore Images" method)

I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.

eworm92 said:
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
Click to expand...
Click to collapse
Hi. What software channel does your device have? There's already android 10 firmware available

LuisLFSS said:
Hi. What software channel does your device have? There's already android 10 firmware available
Click to expand...
Click to collapse
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.

On a side note, when I got to that screen, not even re-flashing the OTA, correctly this time, (beware, new updates have 10 sparse system chunks instead of 9...) let me get past it, so the solution was to erase userdata. (no re-flashing involved) As for Magisk, I just re-patch/flash boot.img at every update, it's not like it's updated that frequently

eworm92 said:
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
Click to expand...
Click to collapse
This is kinda weird because reflash stock ROM android 10 should work for you... What errors did you get when trying to flash android 10?

eworm92 said:
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
Click to expand...
Click to collapse
Next time do the following:
1. Restart to bootloader
2. connect to PC, open ADB terminal and type
"fastboot getvar all" to get active slot
3. change active slot by
"fastboot -aa" => change to slot _a
"fastboot -ab" => change to slot _b
You are running a A/B device. Is there is any error after an update then change the slot to the last working one.

eworm92 said:
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
Click to expand...
Click to collapse
Check if you're running 10 sparse system image flash commands instead of 9 (The only difference between flashing Android 9/10)

I've tried everything proposed above: flashed to both slots, made sure to flash all 10 system sparsechunks.
I guess the solution is to erase userdata, which I've avoided doing thus far. What exactly am I gonna lose if I do?

eworm92 said:
I've tried everything proposed above: flashed to both slots, made sure to flash all 10 system sparsechunks.
I guess the solution is to erase userdata, which I've avoided doing thus far. What exactly am I gonna lose if I do?
Click to expand...
Click to collapse
Erasing userdata will make it like you had just bought the phone. (factory reset) I also had to do that, but I assumed it was because I'd forgotten to flash the 10th system sparsechunk, which caused a bootloop asking me to do a factory reset no matter what I did. (Unless blankflash/flashing Android 9 image was the solution, I just flashed the missing sparsechunk and erased userdata)

I'm just confused because it is an update. I'm supposed to be able to keep my data.

eworm92 said:
I'm just confused because it is an update. I'm supposed to be able to keep my data.
Click to expand...
Click to collapse
You're right, you should keep your data. But I had the same issue on my Moto G6 plus. It was only a security patch update without an Android upgrade.
After it was successfully installed I wasn't able to boot and had to erase my data.

Before factory reset, try switching partition for backup
I basically ran into the same problem today, the update banner popped up at an unfortunate moment and I clicked it in accident. I was also running a RETAIL rom.
The G7 Power didn't boot anymore, instead complaining that the image was corrupted, and did not go into recovery.
adb saw nothing, fastboot saw the device after the usual reboot into bootloader.
A mate of mine suggested switching to partition b with `fastboot set_active b` (or a if yours is set to b already) and after rebooting it failed to start ocean 9 instead of 10. Success ?! On the second reboot it came back up normal, which allowed me to do a normal backup of things before getting into the hassle of upgrading (which I have put off until I have more time).

ElFalko said:
I basically ran into the same problem today, the update banner popped up at an unfortunate moment and I clicked it in accident. I was also running a RETAIL rom.
The G7 Power didn't boot anymore, instead complaining that the image was corrupted, and did not go into recovery.
adb saw nothing, fastboot saw the device after the usual reboot into bootloader.
A mate of mine suggested switching to partition b with `fastboot set_active b` (or a if yours is set to b already) and after rebooting it failed to start ocean 9 instead of 10. Success ?! On the second reboot it came back up normal, which allowed me to do a normal backup of things before getting into the hassle of upgrading (which I have put off until I have more time).
Click to expand...
Click to collapse
That's the advantage of the A/B partition scheme. I already advised him to do so in post #6...
BTW: "adb devices" will recognizes your device only when fully booted up into system or TWRP.

WoKoschekk said:
That's the advantage of the A/B partition scheme. I already advised him to do so in post #6...
BTW: "adb devices" will recognizes your device only when fully booted up into system or TWRP.
Click to expand...
Click to collapse
Seems I was selectively blind I read #5 and #7 and somehow skipped that one exactly.
It's been a while since I did anything with adb, so I wasn't sure about when it detects things. I tried getting into TWRP, but at least on the A partition TWRP had been wiped by the update.
Anyway thanks for the solid advice!

I messed up - stock ROM update via TWRP :(

Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?

kold11 said:
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
Click to expand...
Click to collapse
To force restart I need to use power button and both volume keys..
To keep TWRP you need to flash rom, then without restart flash TWRP again, then restart TWRP, then flash Magisk.
Likely the r reason why your system doesn't boot is because it can't decrypt your data.
Why this happens I don't know, maybe in the upgrade they changed something related to the exception and then by downgrading again it isn't able to read it anymore.
I would suggest to:
Flash the latest rom.
Flash TWRP
Reboot TWRP
If TWRP then doesn't ask for PIN or password, then I'm afraid you have lost your data. I hope you have a backup.
I'm that case format (not just clear) data -> yes
Reboot TWRP
Then flash Magisk.

Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.

kold11 said:
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
Click to expand...
Click to collapse
I would suggest do restore your device with msm unbrick tool.
1. From recovery, turn off (i noticed, that when tried to turn off from somewhere else, the device would auto reboot later in downlaod mode)
2. In windows, turn off the connection & open device manager: Get this driver http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab
3. Press volume/down + volume/up, after about 5s connect to pc
4. Your device should show up in device manager, open it and install the driver manuell from step 2 (keep device options open... if fail you need to uninstall the driver before trying again)
5. Now wait for about 40s, if your device stays in download mode, you can open & start the msm tool (leave the options in msm as they are)
6. It will take about 280s, then the device will reboot.... (its normal that it stays longer at the oneplus logo at first start)
MSM Thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
I've also uploaded the 10.0.5OOS Unbrick tool on mega, because android file hosted downloads are so terrible: https://mega.nz/file/ArZFkYpS#Z_rOIwZeYN27IG6L8rOi-yfw8wXGiwvK-uWVDlsmvTI

seeking advice, new to oneplus.

So I've got a US unlocked device running firmware version KB2005_15_200918. I've rooted it with magisk.
Few days ago I got an update notification, to update to 11.0.1.2.KB05AA. So, thinking I could do it like a pixel, I unrooted, installed the update and re rooted installing to the inactive slot (per @topjohnwu's instructions). On reboot I got stuck on the qualcomm kernel crash screen, leaving my slot_A install hosed.
After some tinkering, I was able to get up and running on slot B. However, slot A is hosed up with the update. (system update says failed, reboot to try again, when i do, hoses back up. Probably because it's setting the active slot to A again).
I've tried re-flashing the KB05AA stock boot image someone dd' and shared on here with no luck. And I don't want to use the unbrick tool, and ending up having to backup/restore all my data.
What are my options at this point to fix slot A, and take the update again? I'm coming from a pixel 3, and know nothing about flashing the factory images on this device or the best way to recover from this. Any advice would be appreciated.

-Michael_ said:
So I've got a US unlocked device running firmware version KB2005_15_200918. I've rooted it with magisk.
Few days ago I got an update notification, to update to 11.0.1.2.KB05AA. So, thinking I could do it like a pixel, I unrooted, installed the update and re rooted installing to the inactive slot (per @topjohnwu's instructions). On reboot I got stuck on the qualcomm kernel crash screen, leaving my slot_A install hosed.
After some tinkering, I was able to get up and running on slot B. However, slot A is hosed up with the update. (system update says failed, reboot to try again, when i do, hoses back up. Probably because it's setting the active slot to A again).
I've tried re-flashing the KB05AA stock boot image someone dd' and shared on here with no luck. And I don't want to use the unbrick tool, and ending up having to backup/restore all my data.
What are my options at this point to fix slot A, and take the update again? I'm coming from a pixel 3, and know nothing about flashing the factory images on this device or the best way to recover from this. Any advice would be appreciated.
Click to expand...
Click to collapse
Use msm tool or reflash stock via fastboot. Either way you gotta wipe one way or another.
Or maybe..
Try fastboot erase boot_a
Then fastboot flash boot_a boot.img. With the kernel you had on slot_a. Hopefully you backed it up prior to this. If not, see my first recommendation.

Thanks, I'll give my kernel backup a shot.