Database Info

OS reset after update to Magisk 18 - SDCARD untouched, how can I restore best?

Hello,
I use my OnePlus 6 rooted with Magisk since the beginning and had no issues. Today the update to Magisk v18 was proposes, so I installed the update in Magisk Manager and of course didn't do a backup before.
After the reboot the system was not really usable anymore. Every 30 seconds I received the message that the system UI stopped working and it froze for a while.
So I wanted to get rid of Magisk and what I did was:
- boot to twrp and uninstalled Magisk (I didn't use the newest uninstaller, I used the one from September).
- tried to reboot but received the message "Wiping, please wait. Do not remove battery of turn off your phone".
- after some seconds the message disappeared, the screen was black and when I pressed the power button it was vibrating but didn't do anything else.
So my tried to get it working again:
- rebooted to TWRP again
- used the latest uninstaller to uninstall Magisk
- then the OS didn't reboot at all
- once more went to TWRP and installed Magisk 18 again. Then the phone rebooted normally but I got a wiped OS.
My sdcard partition (/storage/emulated/0/) is not wiped, everything is still there.
Is there a possibility to go back to a last "stable" version and continue using the phone with the data on the filesystem?
My thought: is it possible to boot from the other slot (before last update) and would this work with my current data on the sdcard partition? Like this I would just lose the Apps and updates I installed since then, right?
Is there another or better solution?
Thank you and best regards

den_zel said:
Hello,
I use my OnePlus 6 rooted with Magisk since the beginning and had no issues. Today the update to Magisk v18 was proposes, so I installed the update in Magisk Manager and of course didn't do a backup before.
After the reboot the system was not really usable anymore. Every 30 seconds I received the message that the system UI stopped working and it froze for a while.
So I wanted to get rid of Magisk and what I did was:
- boot to twrp and uninstalled Magisk (I didn't use the newest uninstaller, I used the one from September).
- tried to reboot but received the message "Wiping, please wait. Do not remove battery of turn off your phone".
- after some seconds the message disappeared, the screen was black and when I pressed the power button it was vibrating but didn't do anything else.
So my tried to get it working again:
- rebooted to TWRP again
- used the latest uninstaller to uninstall Magisk
- then the OS didn't reboot at all
- once more went to TWRP and installed Magisk 18 again. Then the phone rebooted normally but I got a wiped OS.
My sdcard partition (/storage/emulated/0/) is not wiped, everything is still there.
Is there a possibility to go back to a last "stable" version and continue using the phone with the data on the filesystem?
My thought: is it possible to boot from the other slot (before last update) and would this work with my current data on the sdcard partition? Like this I would just lose the Apps and updates I installed since then, right?
Is there another or better solution?
Thank you and best regards
Click to expand...
Click to collapse
If you can get into TWRP dirty flash your ROM. Otherwise change to the other partition either via TWRP or via fastboot set_active A (or B).
Magisk is only installed on the active partition meaning switching it would let you boot into a non-rooted OS.
Apps etc. should be the same as it uses /data. Only /system and some other partitions are A/B.

How to upgrade rooted/unlocked OOS 9 to latest without losing anything?

I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3

https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Post #3 has the instructions you need
Long story short you need to flash the update via TWRP.

unknown00 said:
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
Click to expand...
Click to collapse
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system

tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk

RASTAVIPER said:
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?

unknown00 said:
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
Click to expand...
Click to collapse
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.

Like above.
Flashing ROM Will also flash stock recovery so after ROM you need to flash twrp again,if you reboot without it it's lost.
Also why magisk isn't flashed right away is because: when you choose to reboot to twrp after the twrp flash it Will change slot, this way you Will get magisk on the correct slot.
All this can be done from the OS.
Install the ROM upgrade as usual,don't reboot.
Open magisk app
Search for a module a/b twrp (you Will only find one module) and install it.ndont reboot just yet.
Go to main screen of magisk
Press install, install, install to inactive slot (after OTA). After this install you can reboot.
Both works, I find the twrp way to be more convenient

I don't about stable i am on open beta 10 i root every beta without twrp using patch boot image i got update every time around 1.5 GB because i am rooted after update i just lose root everything same before update phone not wipe anything

I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).

akxak said:
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
Click to expand...
Click to collapse
No need to reinstall TWRP in the first method?

unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
I do not have TWRP installed, it is basically not necessary as OOS can be updated with the settings/manual update tool and Magisk can be reinstalled via Magisk manager.
I had to use TWRP solely to downgrade to Magisk 17.2 from Magisk 18 as this cannot be done with Magisk Manager. But for that purpose, it's enough to temporarly make TWRP available via fastboot boot command without permanently installing it.
If you have TWRP and want to keep it, that easy process doesn't work to upgrade the OS.

unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
If you wanna keep TWRP you do the way I described few posts up.....

tabletalker7 said:
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Click to expand...
Click to collapse
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.

thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.

tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.

thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
thejase said:
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
Click to expand...
Click to collapse
As promised, I'm writing back with my findings. I believe some enabled module in magisk was the issue. What I did was uninstall magisk 18 with the latest uninstaller. Thinking it was V18 itself that was the problem, I then proceeded to install v17.3 on both slots (reboot to recovery in betweene). This worked and booted! It started to occur to me that I had not disabled any of my modules before installation of the rom/magisk. This is a big mistake as a lot of magisk modules are still using old formatting and cause new installations to fail if left enabled. Since an uninstall also disables all modules, I believe using 17.3 was not necessarily the solution but rather either disabling modules before an install, or uninstalling whatever version magisk was installed to begin with (which essentially disables/uninstalls those modules anyway). After installing 17.3 and getting it to boot, I just updated via magisk manager to v18 with no issues to speak of! Now comes the part where I need to remember all the installed modules I had and test them one by one.
For uninstallation of modules in twrp, you can use https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 Or https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
I hope this helps someone!

Stuck on bootloop TWRP without decryption, help.

Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"

sapalot said:
Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
Click to expand...
Click to collapse
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?

reaper000 said:
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
Click to expand...
Click to collapse
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.

sapalot said:
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
Click to expand...
Click to collapse
Don't mess with stock recovery if you already have TWRP and Magisk aboard.
Here's how to update to 9.5.9 (or whatever) when it arrives:
- download your 3 zips: the latest full ota ROM, the latest Magisk, and the latest TWRP installer.
- boot to TWRP recovery
flash the ROM and TWRP installer
- reboot to TWRP recovery
flash Magisk
wipe dalvik
- reboot to system
There's a possibility after these steps and you're happily on the ROM, you might find that you're not rooted (it's more likely on a custom ROM than OOS). In which case you just reboot to recovery and flash Magisk, and then reboot to system. Done.
Discussion:
If you want a clean flash, you'd simply do a TWRP factory reset (standard wipe) instead of wiping dalvik.
Consider flashing both slots (A and B) whenever you update OOS, for two reasons. First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base. The second reason is more compelling: the way the data partition changes encryption every update has obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck

How to update to Android 10 open beta 1 and keep TWRP / Magisk

EDIT: After a few reboots, TWRP stopped working.. now if I try to enter recovery, I get into fastboot instead. But I can still boot the system fine and I still have Magisk. Sorry.. looks like TWRP on this version is still a no-go for now..
I leave the guide here to keep the discussion open, though.. and after the steps some more info on what exactly worked for me..
Hi all, the following steps worked for me (not really, see edit above), but as usual please proceed at your own risk, backup everything before, and be prepared to reinstall everything from scratch if something goes wrong. I am not responsible of anything that happens to your devices when following this guide.
Prerequisites:
- OnePlus 6 (might work also for 6t, but it's untested)
- Oxygen OS 9 open beta 25 (Might work also with the stable version, but again, untested)
- Enable the "advanced reboot" option in developer options.
- latest blu_spark TWRP installed (3.3.1 v9.101)
- if you have Magisk, make sure it's version 20.0 or later (previous versions don't support Android 10)
- if you have Magisk modules, it's highly recommended to disable or uninstall them before proceeding, as some of them might not be compatible with Android 10 and eventually cause a bootloop.
- A computer that is able to run fastboot commands and that you can connect your phone to.
Now, the steps:
- Reboot into TWRP, open the "reboot" menu and take a note of your current active slot (can be a or b)
- Go back to Oxygen OS and install Android 10 open beta 1 through system updates. At the end of the installation, DO NOT PRESS "REBOOT".
- Press the power button and from the advanced reboot menu, reboot into bootloader.
- Connect the phone to the pc.
- If your active slot, noted in the first step, was "a", type "fastboot --set-active=a" . If it was "b", use the same command but replace the final letter with "b".
- On the phone, use the volume buttons to select "recovery mode", and press the power button to confirm.
- You should now be into TWRP: install TWRP again using its installation zip file, DO NOT REBOOT.
- Go to the reboot menu, and change the active slot to the other one (depending on your currently active one).
- Still in TWRP, reboot to recovery.. you should land in TWRP again.
- If you had Magisk, or if you want it, flash it.
- Reboot to system.
If everything goes well, you should now be on Oxygen OS 10 open beta 1, with TWRP installed!
Note: the current version of TWRP does not support flashing the new OnePlus open betas, so when a new open beta is released and you want to update, you will have to go through this process again (until a new compatible TWRP is released).
EDIT 2: Just to give some more information in case someone else wants to try, here's what I did AFTER the steps below:
- Rebooted into OOS open beta 1, just to check that it was booting.. worked.
- Rebooted into TWRP and did a complete wipe, including the internal storage (I wanted a clean install of OB1)
- Rebooted into OOS and did the phone setup (Google account, ecc) including setting up a lockscreen pattern, but no figerprints yet.
- Rebooted again into TWRP to install Magisk, and everything worked, TWRP also asked for my pattern and decrypted data correctly
- After that I didn't reboot anymore for a while, and completed the setup with apps, fingerprints, etc.. and also installed a magisk module (quickswitch), but without using recovery.
- The next time I tried to reboot into recovery, I wasn't able anymore.. I was getting into fastboot instead, but the system can still boot just fine.

cc_rock said:
Hi all, the following steps worked for me, but as usual please proceed at your own risk, backup everything before, and be prepared to reinstall everything from scratch if something goes wrong. I am not responsible of anything that happens to your devices when following this guide.
Prerequisites:
- OnePlus 6 (might work also for 6t, but it's untested)
- Oxygen OS 9 open beta 25 (Might work also with the stable version, but again, untested)
- Enable the "advanced reboot" option in developer options.
- latest blu_spark TWRP installed (3.3.1 v9.101)
- if you have Magisk, make sure it's version 20.0 or later (previous versions don't support Android 10)
- if you have Magisk modules, it's highly recommended to disable or uninstall them before proceeding, as some of them might not be compatible with Android 10 and eventually cause a bootloop.
- A computer that is able to run fastboot commands and that you can connect your phone to.
Now, the steps:
- Reboot into TWRP, open the "reboot" menu and take a note of your current active slot (can be a or b)
- Go back to Oxygen OS and install Android 10 open beta 1 through system updates. At the end of the installation, DO NOT PRESS "REBOOT".
- Press the power button and from the advanced reboot menu, reboot into bootloader.
- Connect the phone to the pc.
- If your active slot, noted in the first step, was "a", type "fastboot --set-active=a" . If it was "b", use the same command but replace the final letter with "b".
- On the phone, use the volume buttons to select "recovery mode", and press the power button to confirm.
- You should now be into TWRP: install TWRP again using its installation zip file, DO NOT REBOOT.
- Go to the reboot menu, and change the active slot to the other one (depending on your currently active one).
- Still in TWRP, reboot to recovery.. you should land in TWRP again.
- If you had Magisk, or if you want it, flash it.
- Reboot to system.
If everything goes well, you should now be on Oxygen OS 10 open beta 1, with TWRP installed!
Note: the current version of TWRP does not support flashing the new OnePlus open betas, so when a new open beta is released and you want to update, you will have to go through this process again (until a new compatible TWRP is released).
Click to expand...
Click to collapse
Anyone tried?

This sounds plausible. Nice!
Question though, how much working functionality remains? Can TWRP be used to install zips, clear cache, do factory reset, install magisk stuff, etc..? Are these still compatible with android 10? Have you tried to do something with it?

kyljys said:
This sounds plausible. Nice!
Question though, how much working functionality remains? Can TWRP be used to install zips, clear cache, do factory reset, install magisk stuff, etc..? Are these still compatible with android 10? Have you tried to do something with it?
Click to expand...
Click to collapse
Hi, first of all, see the edit above.. looks like my TWRP stopped working now.. but it was working for a while.
Initially I was able to flash TWRP itself, and then flash Magisk (which still works) .. not sure exactly when TWRP stopped working.

I bet it stopped working after magisk install. It does the same fir the stock recovery also. No recovery, goes to bootloader.

Oh.. So that means we either have twrp and no root... Or root and no recovery... Choose whatever one wants... Hehe.. Thnx op for the efforts though

cc_rock said:
Hi, first of all, see the edit above.. looks like my TWRP stopped working now.. but it was working for a while.
Initially I was able to flash TWRP itself, and then flash Magisk (which still works) .. not sure exactly when TWRP stopped working.
Click to expand...
Click to collapse
One thing to try would be installing magisk 19.4 from twrp. In canary thread there's a discussion on this very problem with other oneplus devices with A10 and magisk 20.1 that the recovery disappears. Magisk 19.4 did have some fixes regarding Android 10, maybe worth a shot?
Though we could wait the next version of magisk as this problem seems to be under investigation.

I'm able to to keep twrp with magisk 19.3

[email protected] said:
I'm able to to keep twrp with magisk 19.3
Click to expand...
Click to collapse
Ive also managed to do this after a fair bit of fiddling. A quick guide below as im off to bed.
1) you need to be rooted
2) Flash twrp installer in magisk manager (twrp-3.3.1-x_blu_spark_v9.101_op6.zip)
3) reboot to bootloader
3) fastboot flash boot boothybridbeta2.img ( https://drive.google.com/open?id=1JCltKatjRUk1XdEibAme8MnDJxMkzhwE ) boot image is from [ROM][PORT][10.0.0] OnePlus7 Open Beta 3 Port for OnePlus 6 [12.10.19]
4) fastboot reboot
5) reboot to recovery via adb
6) run magisk uninstaller.zip
7) flash stock boot.img in twrp
8) flash twrp installer.zip
9) reboot recovery (to see if it works)
10) reboot phone and choose boot to recovery from phone system again to test it works
11) install magisk v19.3 installer zip in twrp
12) reboot

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