Related
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
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
I totally know that feeling. I started with a tmo op7p, flashed international, unlocked bootloader, try to boot TWRP, and nope. Switch slot, it works. Flash it, great. Make a backup with TWRP of my working system, flash ROMaur, won't do anything but boot to TWRP. Open TWRP file manager and every file on internal storage is a ton of folders with jumbled strings of letters and numbers for names. MSM tool back to intl stock, try lineage... Nope. Keeps telling me to do a factory reset. I did, but I do another and still boot loop. MSM to intl, try other roms, same outcome.
I can unlock my bootloader and root it and run intl stock but that's it.
oxadedzn said:
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
Click to expand...
Click to collapse
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
tech_head said:
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
Click to expand...
Click to collapse
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
JhinCuatro said:
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
Click to expand...
Click to collapse
If you install TWRP on a 7 Pro without installing Magisk you will absolutely boot loop. If you wipe the system in one slot and have a differing ROM from the active slot you can in fact boot loop. Although the systems are different, the settings between the systems are shared.
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Arden144 said:
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Click to expand...
Click to collapse
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
You can also install TWRP if you like.
No computer needed.
This works.
tech_head said:
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
This works.
Click to expand...
Click to collapse
That's completely unnecessary and just avoiding the purpose of the a/b system.
All it would take is:
1. Local install
2. Install magisk to inactive slot
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
Hi all,
I upgraded to Beta 10 earlier today using the instructions from this post, and now I'm in a bootloop/soft-brick situation:
https://forum.xda-developers.com/showpost.php?p=82005795&postcount=8
Boot Slot A leads to a black screen, which then reboots to TWRP.
Boot Slot B shows the red OnePlus loading screen for eternity.
I still have TWRP access, but get errors when trying to flash any OTA.zip.
Does anyone have any ideas on how to restore a working version of Beta 10, without wiping my data?
Thanks in advance!
slayerdiabolus said:
Hi all,
I upgraded to Beta 10 earlier today using the instructions from this post, and now I'm in a bootloop/soft-brick situation:
https://forum.xda-developers.com/showpost.php?p=82005795&postcount=8
Boot Slot A leads to a black screen, which then reboots to TWRP.
Boot Slot B shows the red OnePlus loading screen for eternity.
I still have TWRP access, but get errors when trying to flash any OTA.zip.
Does anyone have any ideas on how to restore a working version of Beta 10, without wiping my data?
Thanks in advance!
Click to expand...
Click to collapse
Hi, had this some time back.
Search on this thread for a fastboot rom https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Worked for me
1. Boot to slot A
2.To boot normally, use "fix recovery bootloop" in Reboot section of TWRP. You can then reboot normally to check if it worked.
3.Download Magisk uninstaller, Magisk lastest INSTALLER zip, and FULL Beta 10 zip.
4. Then reboot and flash uninstaller zip in recovery.(Slot A and B)
5. When done, reboot back to recovery and choose slot A again
6. Flash Beta 10 zip, don't reboot, then flash Magisk installer.
7. Reboot and enjoy rooted Beta 10
You can possibly get away with skipping the Beta 10 flash in step 5 but rather be safe then sorry. Also, if everything doesn't work when done, change the "Flash Magisk installer" in step 5 to "Flash patched boot .img" which you can get from this thread.
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Hope I helped, and pin this post or change title to help others if this works because I seen few people struggling with this and it saves you from having to wipe phone or lose data. Also regains root. Have a blessed day.
slayerdiabolus said:
Hi all,
I upgraded to Beta 10 earlier today using the instructions from this post, and now I'm in a bootloop/soft-brick situation:
https://forum.xda-developers.com/showpost.php?p=82005795&postcount=8
Boot Slot A leads to a black screen, which then reboots to TWRP.
Boot Slot B shows the red OnePlus loading screen for eternity.
I still have TWRP access, but get errors when trying to flash any OTA.zip.
Does anyone have any ideas on how to restore a working version of Beta 10, without wiping my data?
Thanks in advance!
Click to expand...
Click to collapse
shanar585 said:
1. Boot to slot A
2.To boot normally, use "fix recovery bootloop" in Reboot section of TWRP. You can then reboot normally to check if it worked.
3.Download Magisk uninstaller, Magisk lastest INSTALLER zip, and FULL Beta 10 zip.
4. Then reboot and flash uninstaller zip in recovery.(Slot A and B)
5. When done, reboot back to recovery and choose slot A again
6. Flash Beta 10 zip, don't reboot, then flash Magisk installer.
7. Reboot and enjoy rooted Beta 10
You can possibly get away with skipping the Beta 10 flash in step 5 but rather be safe then sorry. Also, if everything doesn't work when done, change the "Flash Magisk installer" in step 5 to "Flash patched boot .img" which you can get from this thread.
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Hope I helped, and pin this post or change title to help others if this works because I seen few people struggling with this and it saves you from having to wipe phone or lose data. Also regains root. Have a blessed day.
Click to expand...
Click to collapse
Wow just completing Step #1 worked here. I didn't realize TWRP had that option!!
For future reference, how would Step 6 work with flashing the BETA 10 zip? I kept getting errors in TWRP when trying this yesterday.
Thanks so much!
Yeah it's a life saver, helped me many times. Oh okay I thought you were rooted so I gave you extra steps to get root back since it's lost during that process. And TWRP could've gave you errors for many reasons, incomplete update file, TWRP needs update, incompatible file, etc. You can update the ROM through "local upgrade" option by clicking the gear icon in top right corner when on update page in Settings. Just put update file in main directory of storage. Instructions are in many threads.
shanar585 said:
Yeah it's a life saver, helped me many times. Oh okay I thought you were rooted so I gave you extra steps to get root back since it's lost during that process. And TWRP could've gave you errors for many reasons, incomplete update file, TWRP needs update, incompatible file, etc. You can update the ROM through "local upgrade" option by clicking the gear icon in top right corner when on update page in Settings. Just put update file in main directory of storage. Instructions are in many threads.
Click to expand...
Click to collapse
Yeah looks like I've lost root, but am on a working BETA 10 at least.
Tried installing Magisk 20.3 via installable zip in TWRP, but ended up in the bootloop again. Used that handy TWRP 'Fix Bootloop' option, but it removes Magisk.
Any ideas on how to resolve?
@slayerdiabolus Lol follow step by step what I posted above and don't stop on step one this time
OK gotcha, but I get an error when trying to flash the official BETA 10 zip in TWRP.
Sorry for being annoying ?
Hi everyone can help, and anyone can't . Please, help with anything
I haven't been so long here but I'm sure you can help me.
Before:
OnePlus 8, I had installed latest (before 11) OOS 10 with Magisk 22.0 and without TWRP.
I was procrastinated with installation OOS 11 update but at least I decided to do it.
But (always is BUT ) - I made a mistake while uninstalling Magisk procedure (via tutorial: https://forums.oneplus.com/threads/keep-root-with-magisk-with-ota-updates.914099/)
"1. Magisk Manager → Uninstall → Restore Images). Do not reboot or you will have Magisk uninstalled.
2. Now Update the system and let it install completely. Do not press the reboot button.
3. Now install TWRP A/B Retention Script from Magisk Manger. This module is available on Magisk (if you have twrp as custom recovery) Skip this if you do not have TWRP installed
4. Go to (Magisk Manager → UPDATE → Install to Inactive Slot) and install Magisk.
5. Once Magisk installation is done, press the reboot button in Magisk Manager.
Your phone may get into bootloop once, if that happens just restart the phone again"
I went through the points 1-2 (I skipped 3. point because, as I mentioned before, I have no TWRP) with no issues. But when I was going through point 4. I was confused (as I found later, due to my newer version of Magisk I had and older one like in the tutorial). And make a mistake.
MY MISTAKE (I think so):
Into point 4. I pressed button INSTALL into MANAGER section (not into Magisk itself) being sure I did it right .
https://9to5google.com/wp-content/uploads/sites/4/2020/10/EjbdUGLU4AAn2nM.jpg?quality=82&strip=all&w=461
Nothing happened. So, I do it again. And again. Then I realized that I should try button above, into Magisk section. I did it and installed to Inactive Slot (via tut). And restarted phone.
NOW:
My phone can't boot into system. Every time I restarted I got rotating 2 small dots around bigger red one (as standard OOS system loading) but longer. But after 3.5 min (it tries to upgrade from 10 to 11 I think) it restart and boot to stock recovery, ask for pass and decrypting.
And this is over. I don't know what I can do to run system with my apps.
I don't want to wipe my system.
I don't know, is this because of installation of Magisk Manager? Or maybe because of full upgrade from 10 to 11.
I tried boot into safe mode - not helped - same as above - at the end restart and boot into stock recovery.
P.S.
I've my original boot.img (OOS 10) before root by Magisk preserves in computer.
Any suggestions???
[SOLUTION]
For posterity
No one can help me so I decided to clean all stuff through official recovery and reboot. It helped but of course I must now install all apps and try to recover my files. Hope it help someone. CU.