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

A/B slot issue, TWRP only on one... unrooted rom on other. Can't mount from TWRP

TWRP is on slot B but not slot A. I can only reboot to system from TWRP when I've got in on Slot A so my ROM seems to be on A,
But from TWRP I can't see the storage device, it says 0MB. It won't let me mount. From what I gather, this is because it's failing to decrypt the device from TWRP? I trying resetting my pin but it didn't work.
I'm trying to figure out how to root my slot A image that doesn't seem to be rooted anymore after an update. How can I get TWRP from Slot B to see the device?
I'm a bit confused about the whole A/B images. What is the function of having two images, besides one being the backup?
Thanks for any suggestions anyone might have.

el80ne said:
I'm trying to figure out how to root my slot A image that doesn't seem to be rooted anymore after an update. How can I get TWRP from Slot B to see the device?
Click to expand...
Click to collapse
So it sounds like slot A is booting to OS (and the updated OS version)?
My suggestion would be to: on slot A, fastboot boot TWRP img, and flash TWRP installer zip again. Then (still booted TWRP) flash Magisk.
Make sure it is a recent version TWRP (latest is unofficial version -76), as it seems that some of the data partition issues are related to using old TWRP.
el80ne said:
I'm a bit confused about the whole A/B images. What is the function of having two images, besides one being the backup?
Click to expand...
Click to collapse
Yeah, the A/B partition scheme was new to me for this device as well (and lots of other folks).
The main purpose is to have what Google calls "seamless updates". Where on a stock device, it is just installing the update in the background and you can still use the phone as it updates. Then once the update is complete, just reboot, and you are on the new OS version. And yes, if something goes wrong, it still has the other (not updated) slot to fall back to. The following xda article is a good read, and explains the basic premise of A/B partitions:
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
The A/B partitions do makes things more complicated when modifying/rooting, etc. But there is a pretty easy way to do an OTA update on this phone, and keep TWRP/root. But let's get the current situation fixed up, before I confuse you with other scenarios.

Flashing & slot A/B

Hi all,
now, I started modifying the phone and trying around with custom ROMs. And after several fails, I could indeed install one ROM properly, but I have to admit that I am puzzled about how this slot management works.
Can someone please explain me how this works? Considering, I am running a custom rom, unlocked bootloader (of course), I would like to install a new ROM, don't care about data/apps/etc. Just tell me what I should do, please.
Thanks,
abprie
PS: I thought, wiping and flashing ROM and TWRP would suffice, but it does somehow not (I am always ending up in the bootloader).

This is quite a common thread, there are many sources available to search. There's even an explaining thread here: https://forum.xda-developers.com/ze...uide-how-to-root-asus-zenfone-6-twrp-t3940168 . If it's still not enough for you, search for "A/B partitions flashing" or "how does A/B slot works".

aleksander002 said:
This is quite a common thread, there are many sources available to search. There's even an explaining thread here: https://forum.xda-developers.com/ze...uide-how-to-root-asus-zenfone-6-twrp-t3940168 . If it's still not enough for you, search for "A/B partitions flashing" or "how does A/B slot works".
Click to expand...
Click to collapse
OK, thanks for the link. I understand now why this was introduced, but not how to use twrp with this.
Considering, I am booting into recovery and see slot A to be active. If I wipe anything, does this affect slot A or B? Same for install, backup or recover. Also: will the next boot be slot B?

It depends on what you wipe. /data is independent but /vendor, /system and /boot partitions will be wiped on the active slot. Backup will work on data+currently active slot. Recovery too. Installation is not so easy. Every zip that isn't a ROM will be flashed on the active slot. If it is a ROM, it will be flashed on inactive one and after a reboot the phone will switch currently active slot. That's why you have to reboot the phone after flashing if you want to add any mods to the device, otherwise they'll flash on inactive one and won't work.

aleksander002 said:
It depends on what you wipe. /data is independent but /vendor, /system and /boot partitions will be wiped on the active slot. Backup will work on data+currently active slot. Recovery too. Installation is not so easy. Every zip that isn't a ROM will be flashed on the active slot. If it is a ROM, it will be flashed on inactive one and after a reboot the phone will switch currently active slot. That's why you have to reboot the phone after flashing if you want to add any mods to the device, otherwise they'll flash on inactive one and won't work.
Click to expand...
Click to collapse
Thank a lot, this helps!

A/B slot questions

I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..

dumbl3 said:
I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
Click to expand...
Click to collapse
Yoo.. So Many Questions. Will try to explain in easiest way..
1. Yes. It Does Flash OOS in Both Slot via Qualcomm Download Mode which is mainly for Manufactures to restore Device..
2. Let me clear that Most people's who face issue in booting custom ROM have their data encrypted by previous or stock ROM.
Here is Link Thread to know how to decrypt your device..
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
My own Instructions to Flash Custom ROM (Strictly for Decrypted Device):-
Boot Into Recovery
Wipe Cache, Data & System
Flash Latest Stable/Beta OOS10 & Recovery
Reboot Into Recovery(Ignore No OS Installed Warning)
Flash Latest Stable/Beta OOS10 & Recovery again
Reboot Into Recovery
Now flash Custom ROM + Recovery(If Not Included)
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
For Installing Update on Same Custom ROM :-
Download the Update
Reboot Into Recovery
Flash Update ZIP & Recovery
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
3. Fastboot Don't always work if You try to Upgrade/Downgrade Android Version as it won't flash Critical Partitions.. Meanwhile MSMDownload tool Use Download mode which is more powerful.
4. Nope. Both are Different AS both use different mode to flash ROM.
5. Clean install required while flashing new custom ROM because Not All ROM uses Same Base. Some uses Stable OOS or some uses Beta OOS... Now, your answer is in these two build Types...
In my Opinion, Custom ROM have nothing to do with your System partition but it most like to related to Vendor Partition... Both Stable & Beta OOS Have little difference in Vendor partition data..
When any dev Build Any ROM, he uses any one of those Build as base for which he tweak/fix bugs.. That's why always Use Dev specified OOS build for avoid Bootloop/bugs..
6. I prefer last option as it's more reliable..
7. It's like when you clean install any ROM.. When you install Any ZIP, It get installed in an Inactive Slot which make those ZIP data Allowed to use in Active slot..
But when you update ROM for 1st time, You install Gapps as well.. So i don't think you need to Install Gapps on 2nd Update as it already installed in both slots.
1st time when Clean installed & 2nd time when Updated 1st time...
8. It's Because how A/B Partition works... Any zip you flash get installed in inactive slot & this applies to both Stock OOS & Custom ROM...
That's why we have to flash OOS twice before flashing any custom ROM.. Which confirms you will have same Vendor partition regardless to your current slot so when you flash custom ROM it will get booted anyways even after an update..
Hope that's helpful.. Any question or help, you can DM or reply here..

Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?

dumbl3 said:
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
Click to expand...
Click to collapse
Well, In my Opinion Every Device is Vulnerable to Hackers.. Doesn't matter if it's bootloader is Locked or Unlocked...
Your device is more Vulnerable at the time you unlocked bootloader because after that you can execute advanced commands with fastboot.....
If your device have pin/pattern, Thief gone reset your device anyway to reset pass.. Eventually your data get wiped as well....
Well, you can encrypt your data but you might face issue while migrating to other ROM if you face any bug + decrypting your encrypted device again is time taking process if you have alot of data..

I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?

dumbl3 said:
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
Click to expand...
Click to collapse
you can.. But do it only if you gone use it for long term....
Not fine to waste your whole day transfer your date from mobile to PC then PC to mobile..