Database Info

Need help flashing OOS 5.1.8 zip (via twrp!?) bear with me.

New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !

leondestiny said:
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
Click to expand...
Click to collapse
You need to make sure you are booting the slot you flashed the rom on, A or B.

sting5566 said:
You need to make sure you are booting the slot you flashed the rom on, A or B.
Click to expand...
Click to collapse
how do i do this? i only flashed zip from the root of my SD , there was no option to select either A or B :C
i went into advanced or seomthing and saw SLot a and B i tapped a and reboot sytem now it is stuck on twrp logo.
f** this ab ****.

When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot

OnePlus 6 has two partitions like the Pixel 2. For seamless OTA updates. In TWRP go to the Reboot menu and you'll see your currently active slot. It's either A or B. Switch to the other one and reboot. That should do it if you did flash the ROM.

Bradl79 said:
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
Click to expand...
Click to collapse
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.

leondestiny said:
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
Click to expand...
Click to collapse
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.

mikex8593 said:
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
Click to expand...
Click to collapse
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up

leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.

mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l

leondestiny said:
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
Click to expand...
Click to collapse
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.

mikex8593 said:
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
Click to expand...
Click to collapse
thx mate, so for next time if i were to flash some oos through twrp, i only need to wipe data/cache etc.
then flash the oos zip ? i dont think i had the option to select which Slot to flash it to, so i guess i just have to reboot to the slot that it has it flashed on..?
and also flashing procedure must be like Rom then twrp then reboot twrp then flash magisk yes?

leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.

chrcol said:
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
Click to expand...
Click to collapse
Fastboot boot recovery. Img
Flash oos full ROM zip
Flash recovery. Zip
Reboot recovery
Flash oos full ROM zip AGAIN
flash twrp. Zip AGAIN
Reboot recovery
Flash magisk if you want root.
Make sure your using the correct twrp aswell. I recommend bluespark v86

chrcol said:
And people say its easy.
Click to expand...
Click to collapse
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.

leondestiny said:
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
Click to expand...
Click to collapse
If you're installing havoc os, make sure you're using latest bluespark TWRP first. Reboot recovery, flash oos, flash TWRP, reboot recovery, flash havoc gapps and magisk then reboot. The only difference in a/b partition is that there's a few extra steps in the flashing process. You don't have to flash to both slots to have havoc, but you also shouldn't be manually changing the slot in TWRP to try to boot a specific slot unless you know what you're doing.

Partitions

Hello everyone,
I don't know much about partitions but I know something is not right with mine
So, A few days ago my phone got bricked because I flashed crDroid rom. (I did something wrong)
So, after a lot of research, I found an solution to unbrick my phone. So it worked, I booted into software again and I was free to use.
So later, I decided to install an custom rom again (Havoc OS). I installed the rom but after I clean flashed the rom, I got stuck on booting logo.
So, I thought lets see what partition B does. So I booted into partition B and I got stuck on the logo of TWRP. Not sure why.
I really wanna know why this happend and how to fix my device.
(Btw, now my phone is working again and I am on stock os with rooted using Magisk 16,7.)
But just wanna know what I did wrong
I used the instruction in this thread: https://forum.xda-developers.com/oneplus-6/development/enchilada-romcrdroid-t3827070. And after I did that it got bricked.
I hope anyone knows what happend and how to fix my partition!
Friendly regards,
Crewz

Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!

whizeguy said:
Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!
Click to expand...
Click to collapse
I did the exact steps as in the thread.

ItsCrewz said:
I did the exact steps as in the thread.
Click to expand...
Click to collapse
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?

iElvis said:
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?
Click to expand...
Click to collapse
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp

ItsCrewz said:
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp
Click to expand...
Click to collapse
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?

iElvis said:
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?
Click to expand...
Click to collapse
Yes I know what it means. But it isn't normal that it boots into twrp and get stuck on the logo

disabled encryption

I have successfully decrypted my essential phone using the dm verity disabler by zackptg. Need to test it some more, but twrp boots after flashing it, instantly.it doesn't have that lag

jacksummers said:
I have successfully decrypted my essential phone using the dm verity disabler by zackptg. Need to test it some more, but twrp boots after flashing it, instantly.it doesn't have that lag
Click to expand...
Click to collapse
were u rooted before or not? did u have to format everything in twrp?
edit it actually works!!!!!! I'm unencrypted...i can go into twrp while a pin is set....i can flash magisk with first boot of a rom and it boots...!!!!!

This is a huge advancement. I didn't think it worked until I booted into twrp. And it was instantaneous.so before I flashed the dm verity decryption zip, I did indeed wipe everything on both slots, then mounted system in twrp and flashed the zip, then I flashed the ROM.i will be switching back to stock to test if it stays decrypted later today. I'm running a gsi,(benzo ROM+ all my own customizations)rooted,with all the trimmings) the same mentality will have to follow, but it will be interesting to see how it goes with flashing stock fresh. I imagine restoring my nandroid will be fine and stay decrypted, but probably will have to flash stock, then after setup, back to twrp, wipe factory reset and flash the dm verity decryption zip..I think, I gotta just do it to be sure. Anyone who does this should share notes and that will help the community.
Here is a good question, wtf can I do to have lte again. ever since pie official, I lost lte.phone drops to 3g during calls only. I discovered this while searching for a fix for my volte. Hence,, switching to gsi's because they don't have volte and neither does my stock, even with fresh installs.i have t mobile.all the betas it worked fine.

Here's the thread folks
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Thanks to Zackptg

jacksummers said:
This is a huge advancement. I didn't think it worked until I booted into twrp. And it was instantaneous.so before I flashed the dm verity decryption zip, I did indeed wipe everything on both slots, then mounted system in twrp and flashed the zip, then I flashed the ROM.i will be switching back to stock to test if it stays decrypted later today. I'm running a gsi,(benzo ROM+ all my own customizations)rooted,with all the trimmings) the same mentality will have to follow, but it will be interesting to see how it goes with flashing stock fresh. I imagine restoring my nandroid will be fine and stay decrypted, but probably will have to flash stock, then after setup, back to twrp, wipe factory reset and flash the dm verity decryption zip..I think, I gotta just do it to be sure. Anyone who does this should share notes and that will help the community.
Here is a good question, wtf can I do to have lte again. ever since pie official, I lost lte.phone drops to 3g during calls only. I discovered this while searching for a fix for my volte. Hence,, switching to gsi's because they don't have volte and neither does my stock, even with fresh installs.i have t mobile.all the betas it worked fine.
Click to expand...
Click to collapse
How did u get wifi to work on gsi..for me i can seem to get it working..and im using the last 8.1 vendor....for the lte go into dialer and *#*#4636#*#* and change the lte/utms/cdma setting around until u get it

Tech_Savvy said:
How did u get wifi to work on gsi..for me i can seem to get it working..and im using the last 8.1 vendor....for the lte go into dialer and *#*#4636#*#* and change the lte/utms/cdma setting around until u get it
Click to expand...
Click to collapse
I have found that after booting up a gsi, factory reset it. Then be sure not to root with magisk. Every time I tried it killed my data and wifi. Use phhhsuperuser ab zip. I think I may have had to flash my modem.img a time as well after the initial install.
And yeah I got it kinda, still no lte. I'm gonna try a modem img from the pie firmware..I think it is the problem

Has anyone had success in decrypting on stock? I cant get it and then i lose touch with the phone booted up. So in other words do not try to decrypt stock. U will wreck your phone and the only way to fix it is to flash stock via fastboot AND adb sideload. One or the other doesnt fix it for some reason. Has to be both.

jacksummers said:
Has anyone had success in decrypting on stock? I cant get it and then i lose touch with the phone booted up. So in other words do not try to decrypt stock. U will wreck your phone and the only way to fix it is to flash stock via fastboot AND adb sideload. One or the other doesnt fix it for some reason. Has to be both.
Click to expand...
Click to collapse
Were you trying on stock oreo or pie?

governmentissuejoe said:
Were you trying on stock oreo or pie?
Click to expand...
Click to collapse
Both

jacksummers said:
Both
Click to expand...
Click to collapse
I tried it on stock Oreo and it works.

governmentissuejoe said:
I tried it on stock Oreo and it works.
Click to expand...
Click to collapse
Ok cool, I was worried I did this as a fluke. What was the steps u did?

jacksummers said:
Ok cool, I was worried I did this as a fluke. What was the steps u did?
Click to expand...
Click to collapse
So these are all the steps I took to get it to work. All of these steps may or may not be necessary. I used aer0zer0's stock dump for the lastest release of oreo and flashed the wipe all bat. It did its thing and wiped and flashed on both slots. I booted into the rom and finished initial setup and enabled adb in developer settings. I rebooted to bootloader and flashed twrp to inactive slot. I booted into recovery and selected the format data option and typed yes. I rebooted to bootloader and reflashed twrp. When I booted into recovery I transferred the stockboot.img, magisk 17.1 zip, and disable encryption zip to the phone. I flashed the stockboot.img to the boot partition. I then flashed the disable encryption zip. I then mounted the system partition and flashed the magisk zip. Finally, I rebooted into the rom and set pin and fingerprint. I installed EX Kernel Manager and created a backup of the decrypted magisked boot.img just in case. I flashed twrp through ex kernel manager and rebooted to recovery. Everything stayed decrypted. I flashed my newly created boot.img backup and booted back to my rom. Thats it. I hope I remembered everything. I hope this helps. Again, I do not know if all the steps I took are required but it worked for me.

Fix infinite boot without resetting data?

Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help

cvfd said:
Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help
Click to expand...
Click to collapse
This is exactly what happened to me! (and I thought it was related to edXposed).
Have you tried flashing only the boot img?

cvfd said:
Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help
Click to expand...
Click to collapse
Boot to twrp
Flash magisk uninstaller
Flash oos full rom
Flash twrp zip
Reboot recovery
Flash oos full ROM
Flash twrp zip
Reboot recovey
Flash magisk.

yldlj said:
Boot to twrp
Flash magisk uninstaller
Flash oos full rom
Flash twrp zip
Reboot recovery
Flash oos full ROM
Flash twrp zip
Reboot recovey
Flash magisk.
Click to expand...
Click to collapse
Hmm, I just tried that and it didn't help. Is there anything else I can do?
Edit: Tried with official TWRP as well, no luck either.
davidperl99 said:
This is exactly what happened to me! (and I thought it was related to edXposed).
Have you tried flashing only the boot img?
Click to expand...
Click to collapse
Where would I find the newest boot.img? Also, isn't flashing the OOS Full ROM supposed to replace my boot.img with the stock one?

cvfd said:
Hmm, I just tried that and it didn't help. Is there anything else I can do?
Edit: Tried with official TWRP as well, no luck either.
Where would I find the newest boot.img? Also, isn't flashing the OOS Full ROM supposed to replace my boot.img with the stock one?
Click to expand...
Click to collapse
I think you might have to wipe if you can't get your phone to boot after dirty flashing ROM. I would try flashing your boot. Img first in case it's magisk related problem. What ROM are you on?

yldlj said:
I think you might have to wipe if you can't get your phone to boot after dirty flashing ROM. I would try flashing your boot. Img first in case it's magisk related problem. What ROM are you on?
Click to expand...
Click to collapse
Regular OOS 9.0.7.

cvfd said:
Regular OOS 9.0.7.
Click to expand...
Click to collapse
Stock Boot. Img can be found here
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Also try use the latest bluespark twrp

yldlj said:
Stock Boot. Img can be found here
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Also try use the latest bluespark twrp
Click to expand...
Click to collapse
So flash the boot.img through fastboot and then repeat the steps above?

cvfd said:
So flash the boot.img through fastboot and then repeat the steps above?
Click to expand...
Click to collapse
Flash boot. Img and see if the phone boots. I have never flashed a boot. Img so not sure exactly how. If not it might be time to use the fastboot rom. If you flash the boot. Img you will lose twrp.

yldlj said:
Flash boot. Img and see if the phone boots. I have never flashed a boot. Img so not sure exactly how. If not it might be time to use the fastboot rom
Click to expand...
Click to collapse
No luck with that either, so I guess it's time to reset. What's the best way to backup and restore as much of my data as possible, like system settings and app data?

cvfd said:
No luck with that either, so I guess it's time to reset. What's the best way to backup and restore as much of my data as possible, like system settings and app data?
Click to expand...
Click to collapse
You can backup data in twrp but that might be the reason you can't boot. Google backup should of backed up most things. At this point you should be more concerned about getting your phone to boot.

OnePlus 7 Pro OTA Bootloop [Help!]

Woke up this am to an OOS update and remembered that there's a process to go through to not lose root and magisk, so I look up the thread and follow the simple directions.
Allow the OTA but do not reboot.
Go into Magisk and install again to internal
Stay in Magisk and install to inactive slot
Reboot
I did exactly that and upon reboot, my phone booted to my lockscreen pic and just flashes every second. Even in safe mode it bootloops at a flashing lockscreen.
I followed exactly what I was supposed to do, so is there a step missing? Or was I not supposed to take the OOS update that was being pushed today?
I can access TWRP still, and I do have a full backup available if I need it, but I'd much rather figure out how to move forward.
Thanks for any help you can give me!
OnePlus 7 Pro
stock ROM
TWRP & rooted

Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.

FlipmodeBG said:
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
Click to expand...
Click to collapse
What exactly did you do to uninstall magisk from TWRP? I don't know how to do this...
Did you go into TWRP file manager and just delete /data/adb/magisk folder?

Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.

FlipmodeBG said:
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
Click to expand...
Click to collapse
Thanks for that, didn't work for me though. I keep bootlooping at insecure bootloader warning.
I have messed something up pretty bad, after the last reboot, I'm met with the Qualcomm CrashDump mode -- dmverity device corrupted force dump
kernel_restart
Now I'm stuck, because I've tried to recover my backup, it goes through the process at just over 1000 seconds, has no errors or failures but still won't boot.
I need some help here.

Nevermind, I have to have this phone back up and running ASAP, so I used MSM Tool and started over. I figured spending a few hours setting it back up from scratch was the best way forward at this point.
I'm unclear on what caused this problem... maybe I had a magisk module that didn't disable, or maybe I forgot to disable a substratum layer or something, but I really borked myself all because of an OTA update.
Any further advice on what I might have done or what might have corrected it will still be appreciated because I'm sure there will be another OTA someday and I'd really like to avoid this happening again.
Thanks!

What I do when there is a new Ota is
download the update from the updater app
remove any passwords or finger prints
reboot to twrp
install the Ota
do no reboot
install twrp installer
do no reboot
install magisk
wipe dalvick
reboot
check if Magisk is installed and if not reboot back into twrp and install Magisk again

Hi. Magisk 20.4 not working my device. Has anyone managed to get it working?