Database Info

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!

Need a little help, phone won't boot into system after OTA update to PIE

So I finally pulled the trigger on updating my Oneplus 6 to the latest OTA PIE update, but when the phone reboots it goes to the system for 2 seconds then immediately reboots to TWRP recovery. I followed the instructions from a thread here that said to immediately flash the TWRP A/B zip from Magisk, followed by clicking install for Magisk to the inactive slot. Now I can't get my system to boot up properly and I'm only able to access TWRP recovery. What should I do, I'm basically locked out of my phone now?!

Module or theme error, flash magisk uninstaller, flash magisk and boot.
If it still doesn't boot, flash magisk uninstaller boot system and remove theme overlays (like substratum or Swift installer)

whizeguy said:
Module or theme error, flash magisk uninstaller, flash magisk and boot.
If it still doesn't boot, flash magisk uninstaller boot system and remove theme overlays (like substratum or Swift installer)
Click to expand...
Click to collapse
I've tried flashing magisk uninstaller 5 times, same result no matter what I do. I finally just wiped the Data partition from twrp and then system boots. I just have to set everything back up on my phone now.

Big Problem with Magisk 20.1, and OTA Update to 10.0.3

So I downloaded the 10.0.3 update, then went to Magisk and uninstalled the Manager and Magisk, and chose "restore images." It ostensibly did so, and so I had the System install the OTA update as a Local Upgrade. All went well.
But when I returned to Magisk to reinstall, it showed as already (or still) being installed! When I tried to install, it did not give me any sort of options for where it was to be installed.
Now I don't know what to do. I am afraid to reboot because I really don't know what the status of my TWRP Recovery, my Magisk, or my operating system is, though I suspect that the OTA was successful. So I am in this holding pattern trying to decide what to do that will not create an even greater problem.
Any help will be so much appreciated.

Not sure what you mean by restore images. Are you still booted up? It's not complicated at all. Just disable all modules. No need to uninstall. Boot into twrp, flash full ota, press back, install twrp, back and finally magisk. Reboot and open magisk manager. It will show magisk as uninstalled. Reboot into twrp again, flash magisk and reboot. This time magisk manager will say it's installed. Reanble all modules and reboot. I just did that as well as on previous updates. Always works.

tropical cactus said:
Not sure what you mean by restore images. Are you still booted up? It's not complicated at all. Just disable all modules. No need to uninstall. Boot into twrp, flash full ota, press back, install twrp, back and finally magisk. Reboot and open magisk manager. It will show magisk as uninstalled. Reboot into twrp again, flash magisk and reboot. This time magisk manager will say it's installed. Reanble all modules and reboot. I just did that as well as on previous updates. Always works.
Click to expand...
Click to collapse
Uhh.. That seems a little more complicated than it needs to be.
Turn off all Modules. Reboot is probably good idea.
Install update via local upgrade, don't reboot.
Go to magisk, download and flash twrp a/b retention script. Don't reboot.
Go back to magisk and install it, select the after ota option. Reboot.
Enable modules and reboot as needed to get everything going again.

GeekMcLeod said:
Uhh.. That seems a little more complicated than it needs to be.
Turn off all Modules. Reboot is probably good idea.
Install update via local upgrade, don't reboot.
Go to magisk, download and flash twrp a/b retention script. Don't reboot.
Go back to magisk and install it, select the after ota option. Reboot.
Enable modules and reboot as needed to get everything going again.
Click to expand...
Click to collapse
I don't know. I would think doing everything in twrp would be the safest. I've never had to choose between slots or download any script. To each his own, I suppose.

+1 to flashing via TWRP. Definitely quick and seamless.

tropical cactus said:
Not sure what you mean by restore images. Are you still booted up? It's not complicated at all. Just disable all modules. No need to uninstall. Boot into twrp, flash full ota, press back, install twrp, back and finally magisk. Reboot and open magisk manager. It will show magisk as uninstalled. Reboot into twrp again, flash magisk and reboot. This time magisk manager will say it's installed. Reanble all modules and reboot. I just did that as well as on previous updates. Always works.
Click to expand...
Click to collapse
My question is, after having installed the OTA then going back to see that Magisk never uninstalled, is TWRP still there, or has it been replaced by stock?

tropical cactus said:
Not sure what you mean by restore images. Are you still booted up? It's not complicated at all. Just disable all modules. No need to uninstall. Boot into twrp, flash full ota, press back, install twrp, back and finally magisk. Reboot and open magisk manager. It will show magisk as uninstalled. Reboot into twrp again, flash magisk and reboot. This time magisk manager will say it's installed. Reanble all modules and reboot. I just did that as well as on previous updates. Always works.
Click to expand...
Click to collapse
And by restore images, I mean that when you uninstall Magisk, it asks if you want it to restore the original stock boot images. And youre supposed to say yes.

Problem is I've already installed the OTA. It does give me the option to install the OTA Again

The answer to that question is yes, TWRP was gone when I rebooted, and just stock recovery. So I guess I'm back to basic re-rooting the phone by ADB, etc.

Try seeing this video and where u went wrong

BeachNYC said:
So I downloaded the 10.0.3 update, then went to Magisk and uninstalled the Manager and Magisk, and chose "restore images." It ostensibly did so, and so I had the System install the OTA update as a Local Upgrade. All went well.
But when I returned to Magisk to reinstall, it showed as already (or still) being installed! When I tried to install, it did not give me any sort of options for where it was to be installed.
Now I don't know what to do. I am afraid to reboot because I really don't know what the status of my TWRP Recovery, my Magisk, or my operating system is, though I suspect that the OTA was successful. So I am in this holding pattern trying to decide what to do that will not create an even greater problem.
Any help will be so much appreciated.
Click to expand...
Click to collapse
Correct steps to upgrade without loosing magisk and twrp.
1. Download the update from Oxygen Updater. (DONT INSTALL OR REBOOT)
2. Package is downloaded in /sdcard.
3. Now open Settings>System>System Update and click on the wheel on upper right corner.
4. Select Local Upgrade, then install the update (DONT REBOOT)
5. Open Magiak and Remove modules that may cause problems (i recommend remove all)
6. Go in magisk>downloads and install "twrp a/b retention script".
7. Now final step in main screen of magisk manager click on install magisk and select install to inactive slot. Confirm it. Install and reboot.
8. After reboot you will have magisk and twrp both
9. To confirm you can reboot in recovery mode.
10. My recommendation- after all done wipe cache/dalvik cache once manually in twrp. Then re-install/enable modules that you want.
Regards

Bootloop after magisk module install

Hello everyone,
I recently installed Magisk and TWRP and at first everything was working completely fine, than I installed the f-droid privileged extension module the device started bootlooping.
I managed to fix the issue through TWRP (Fix bootloop option) and completely uninstalled Magisk through the official uninstaller. Thing is every time I'm trying to reinstall Magisk the problem returns.
Please help.

Happened to me to....you need to uninstall that exact module from your system....
You can uninstall any modules even from TWRP...
go to file explorer on TWRP
Open data then adb an then modules and delete unnecessary folder otf module...

James Blode said:
Happened to me to....you need to uninstall that exact module from your system....
You can uninstall any modules even from TWRP...
go to file explorer on TWRP
Open data then adb an then modules and delete unnecessary folder otf module...
Click to expand...
Click to collapse
Thank you for replying but the adb folder is empty.

Anyone?

PsyCoil said:
Hello everyone,
I recently installed Magisk and TWRP and at first everything was working completely fine, than I installed the f-droid privileged extension module the device started bootlooping.
I managed to fix the issue through TWRP (Fix bootloop option) and completely uninstalled Magisk through the official uninstaller. Thing is every time I'm trying to reinstall Magisk the problem returns.
Please help.
Click to expand...
Click to collapse
This is strange normally when you flash magisk uninstaller every module will be uninstalled, it's used to do a clean flash of magisk, infact when you reinstall magisk no module will be there and you need to reinstall everything

Hitman478™ said:
This is strange normally when you flash magisk uninstaller every module will be uninstalled, it's used to do a clean flash of magisk, infact when you reinstall magisk no module will be there and you need to reinstall everything
Click to expand...
Click to collapse
Indeed. How should I proceed then? Could the "Fix bootloop option" in TWRP caused the issue?

PsyCoil said:
Indeed. How should I proceed then? Could the "Fix bootloop option" in TWRP caused the issue?
Click to expand...
Click to collapse
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way

I have just tried the first method and unfortunately it did not work. The device keeps booting into fastboot instead of system. I will try the second method tomorrow and report here. Just to make sure I have it right, dirty flash is flashing the ROM without wiping the data first?
Magisk version is latest stable v20.3
Hitman478™ said:
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way
Click to expand...
Click to collapse

Thanks! The second solution did the trick. I'm pretty sure TWRP "Fix bootloop option" somehow caused the issue.
Hitman478™ said:
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way
Click to expand...
Click to collapse

PsyCoil said:
Thanks! The second solution did the trick. I'm pretty sure TWRP "Fix bootloop option" somehow caused the issue.
Click to expand...
Click to collapse
Great! :good:
Because once you flash "Fix bootloop option" it will stay in system partition and the only way to remove is to reflash system through oos zip

hahaha i think magisk rooting method fail from safetynet check and module install. After a bootloader from specific module (disablerliboemencrypto) i restore my stuff to try another module (Bluetooth ..) a bootloop again happen
sorry but,GOOGLE beats YOU @topjohnwu.

Issues getting root back after Android 11 Update OP6

Hey, after installing android 11 on my Oneplus 6 I have servere issues on getting root back.
Both methods I used result in a stuck boot.
Method 1: fastboot boot twrp, then install magisk.zip (tried with both 21.4 (last with a zip) and the renamed 23.0 (from apk to zip)
Method 2: Extracted boot.img from my OTA update, then patched with magisk 23.0.
Flashed the new boot.img -with fastboot -with twrp both result in a stuck boot.
Suprisingly flashing the extracted boot.img from the OTA boots fine, but that image is without magisk
Update: I have extracted the boot.img directly from the phone, patched it and it still doesn't work

I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it

Thratchen said:
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Click to expand...
Click to collapse
twrp actually works, but after flashing magisk or flashing a magisk boot.img it breaks. I have a working version here
Ping me if you get magisk working

I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help

To remember!

Thratchen said:
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
Click to expand...
Click to collapse
Which installation method of magisk did you use?
How long did you wait after first boot?

I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you

Thratchen said:
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Click to expand...
Click to collapse
Thanks for the reply, as a last question: Which magisk version did you use (could you link i?t). I assume you took the magisk v23 apk and renamed it to .zip? or what did you do?

Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

Thratchen said:
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Click to expand...
Click to collapse
Hmm, I perfectly copied your instructions and still get a bootloop. Even reflashed 11.1.1.1 again. Might be time for a reset

Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.

vkass said:
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
Click to expand...
Click to collapse
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)

is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp latest zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !

tacohell said:
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp lat est zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
Click to expand...
Click to collapse
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)

UraniumDonut said:
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
Click to expand...
Click to collapse
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.

vkass said:
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
Click to expand...
Click to collapse
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!

UraniumDonut said:
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
Click to expand...
Click to collapse
Thhank @UraniumDonut - that worked - I have never before used that method and honestly didn't even know about it. I use the official documented twrp way which is to first fastboot in to twrp and then install the zip file which has to be located on the phone file system. This method seems a lot easier!
As to magisk, I usually flash that from twrp using the zip file method and never have had any issues. But with all the issues surrounding oos 11 I am playing it safe as I don't want to get in to a boot loop. Will do some more research before I try something. But thanks to you I have made 1 step forward progress!

UraniumDonut said:
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
Click to expand...
Click to collapse
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.

vkass said:
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
Click to expand...
Click to collapse
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing

Just for reference here
UraniumDonut said:
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Click to expand...
Click to collapse
I posted detailed steps if you want to give this a try @UraniumDonut: https://forum.xda-developers.com/t/how-to-root-op6-11-1-1-1.4344269/#post-85765879