yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] RMarques:
All right, it did boot into the latest OOS, but I'll have to take a break to run some errands now.

I'll be configuring it while doing so and later on we can try a second round in order to install PiXeN 11.

Another Q, while in file manager is it normal I cant access common storage? If so, whats the idea of having it? Wouldnt it be better to do an option to have 32, 64 or 96GB partitions so we can actually use the most of our storage capacity?

Anyways, cant wait to have 2 ROMs up and running and to configure that ROM switch mod!

Thanks again bud!
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Great. :)

Yes, exactly that seems to be the biggest issue to fix now since the Common data partition is not getting mounted inside the ROM now.

If I dont get that fixed I will eventually remove the common data partition or change the size configuration of it so that we have more space to use for the 2 data partitions for the ROMs.
[OnePlus 6 & 6T Cross Device Development] RMarques:
Awesome, if you manage to have it mounted from inside the ROM, you'll push the bar to another level for sure!
[OnePlus 6 & 6T Cross Device Development] mcdachpappe:
Detected!
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Thanks for checking. Thats great. Then I know that this is working. :)

OK, so for the 64 GB OP6 variant what Data partition sizes do you want to have to choose from?

16 GB and 30 GB ?
[OnePlus 6 & 6T Cross Device Development] mcdachpappe:
Just to be sure: If it would be 30 GB, this means 30 GB for Apps (shared between both ROMs)? The other 34 GB would be used for system_a, system_b and common partition?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
You can choose between two different sizes for each data/system partition (a and b). The rest will be for the common data partition but since that is only usable from within TWRP right now the most space should be used for the data_a and data_b partitions!

So when we have 16GB, it will be 16GB for Data_a and 16GB for Data_b, the rest so 32GB will be for the common data partition in that case!
[OnePlus 6 & 6T Cross Device Development] mcdachpappe:
Alright, now i understand. This TWRP splits the current userdata partition in two [userdata_a, userdata_b] for each system [system_a, system_b], correct? Sorry for these questions, I'm not as much into this topic as you.

But what about system partitions and all the other misc partitions if common data partition would take all the other space [in your example, 32 GB]? Each system partition takes around 3.5 GB if I'm correct resulting in a common data partition around 25 GB?

64 GB total device storage - system_a [3.5 GB] + system_b [3.5 GB] + data_a [16 GB] + data_b [16 GB] = 25 GB common partition
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes exactly it will split the userdata partition into userdata_a and userdata_b, and userdata2 which is used for "common data". It is only touching the userdata partition so the system_a and system_b will stay as they are.
[OnePlus 6 & 6T Cross Device Development] Causical:
Quick question, so if you decide to eliminate common data partition entirely this would essentially mean we could use our A/B slots like they were originally intended however we would never have to format data right, because each slot would have it's own independent data? To me that sounds like how things should have been from the beginning, why aren't we just doing that?

I can literally see NO use in common data partition to those who are interested in using dual boot save for the fact if they wish to upgrade the same Rom and retain data, which they can now simply do by changing to opposite slot before flashing the update.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes correct, each slot have its own data partition. You need to do a format data on a slot when you switched to another ROM. Yes but I want to try to get that working with the common data. That is really useful for files you want to share/access from both ROMS without the need to have to copy them to both of them, like Music, Pictures, Installation files etc.

I will surely adjust something regarding this with the next Update(s) . :)
[OnePlus 6 & 6T Cross Device Development] Causical:
I see, I see that makes sense. How will the ROM differentiate save paths for what should be stored in common data and what should be stored in local data?

Say, something like Call of Duty for example, will this decide to be shared data or local data?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
For most apps etc I would use the local data. Common data is more for common file like Music, Pictures, and so on which you want to have access from both slots.

Also you can actually if you dont want to use the common data choose to not create it during the first flash of the Dualboot-TWRP. Then you will just have the userdata_a and userdata_b.
[OnePlus 6 & 6T Cross Device Development] mitchst2:
Is it not possible to assign some apps to common data? This would be useful for apps like Signal so messages would be synced between ROMs for example.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes I agree but I guess in that cases the place for the data needs to be changed in some way manually in the apps so that it uses commondata and not the normal data.

Right now I am most focusing on to get the commondata mounted from inside the ROM.
[OnePlus 6 & 6T Cross Device Development] mitchst2:
Keep doing what you are doing and hope you sort it all out. Used Multirom on my old M7 so would love to see this working out.
[OnePlus 6 & 6T Cross Device Development] UsPdSr:
[MENTION=9574498]Wishmasterflo[/MENTION]

I wanted to express my gratitude for your tremendous work and in particular for this amazing project!

It reminds me of the old days, with my Nexus 5 and Multirom and later the Dualboot patcher.. I hope to see you here a long time around and, again, thank you for your engagement. :)
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Thanks a lot. :)

I have a day off from work today so I am sitting here and try to fix some bugs and re-implement the mounting of the common data as it seems not to work in the way it is implemented now.

Perhaps push another Update after the weekend.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Good news. Seems that these issues I saw with Android 11 (PixenOS) that Magisk was not working anymore after re-flashing the Dualboot-TWRP and Magisk afterwards and it didnt got installed were no issues from the Dualboot-TWRP.

Seems that these were some issues with the PixenOS since I installed the latest Update for PixenOX 11 and I dont have any issue with Magisk now, even after re-flashing Dualboot-TWRP and re-installing Magisk. :)

EDIT: I have more good news now since I got the Common data now mounted from inside the ROM as well but that only works when you have Magisk installed!!
[OnePlus 6 & 6T Cross Device Development] RMarques:
:fingers-crossed::highfive::victory:

About yesterday, I ended up taking it back to normal and rolling with lastest OOS + Magisk after it started to act weird with Dual boot + Latest OOS. It started to not to show internal files on both file manager and ES file explorer anymore...Im not even sure if it was a Dual boot problem but I kinda rolled back because I needed to use my phone during the night.

Anyways, Im still with you and only waiting for a new update on common partition!
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
OK thanks for the info. I see....so you want me to push the new Update today. :) :)

I have to add one small check to the script, I guess otherwise it will fail on the first Install when Magisk is not yet installed.
[OnePlus 6 & 6T Cross Device Development] RMarques:
If you manage to figure out common storage and if are going to be around in order to help if things somehow backfire, then yes, ofc!
[OnePlus 6 & 6T Cross Device Development] Causical:
If we don't create it though, your current predetermined partition sizes don't make use of all available space, is this correct? In other words, without the common data partition is it set up to use all available space or will there be some left over?

Thank you for your work btw ?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
If you choose to not have a Common Data partition during the first install it will split up the whole space into Data_a and Data_b so then you will not loose any space. :)

I actually managed now to get the common data mounted in the ROMs as well using a Magisk boot script. So that actually will only work when Magisk is installed then.

The other method how it was implemented before was too difficuly and I actually had not gotten it to work at all.

I just need to do some more small tests with the latest Version here until I will upload it for all. :)
[OnePlus 6 & 6T Cross Device Development] UsPdSr:
[MENTION=9574498]Wishmasterflo[/MENTION]

I am long-time linux user and hobby kernel developer, but with partitioning do I behave from system to system like a complete newbie. :>

The name changing of the Twrp is a helpful feature, but I thought it would be better to ask you before I hardbrick the device..;)

I own the OnePlus 6 (A6003), with 128GB Storage & 8GB RAM.

I would like to install Oxygen OS (current version) with Magisk and custom kernel (approximately ~60GB) as one rom and if possible, Pixen OS 11 with Magisk or Paranoid rom Quartz 5, with Magisk as well, as second rom (approximately ~68 GB).

I don't want to share user data between both if not necessary.

Both rom partition should be decrypted if possible.

Would you be so kind and could help me out with the correct syntax?That would be great.. :good::)
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Hello!

Yes, if you dont need the common data you can actually choose during the first install to not have the common data partition. Then you will have ~ 60GB for Data_a and Data_b .

Yes you can have both decrypted and you can only set a PIN/password on one of the slots!!
[OnePlus 6 & 6T Cross Device Development] UsPdSr:
That is amazing. And I can set this all up within the Twrp installer without any other modifications?

I read that you tried the Android 11 version of Pixen OS..is the combination with OOS as second rom so far okay?

PS

I don't need a display pin or fp, just both rom are rooted and on the one additionally a custom kernel :)
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes exactly all the settings are set during the first flash of the Dualboot-TWRP.

I have Pixen OS 11 and Carbon ROM 10 running now but yes OOS and Pixen 11 should work as well.
[OnePlus 6 & 6T Cross Device Development] UsPdSr:
Thanks a lot for the fast help! :)

I will post the result after flashing and setup.

Is it important if stock or custom rom are on first or second place?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
That does not matter, you can choose how you want it.
[OnePlus 6 & 6T Cross Device Development] UsPdSr:
Great =)

Thanks a lot, [MENTION=9574498]Wishmasterflo[/MENTION]
[OnePlus 6 & 6T Cross Device Development] Causical:
Quick question, since only one of the slots can have pin/pass set up does this mean that the same one will work on both slots or that one of the slots will be entirely without security lock?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
No the same will not work on both. You need to leave one slot without!
[OnePlus 6 & 6T Cross Device Development] Causical:
I guess what I'm asking is, if I set the pin on one slot is the other slot also locked with that same pin or does it just not lock at all?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
No if you set a PIN on one slot that is only for that slot. The other will not have a PIN at all!

You can only set a PIN/password/pattern on one of the slots. If you set it on both and reboot to the other slot, you will not be able to login to that slot anymore.

That seems to be some device specific thing and can not be changed/fixed.

So then you can of course if you have that slot unencrypted just delete the locksettings/password key and db files from /data/system to remove the PIN/password/pattern.
[OnePlus 6 & 6T Cross Device Development] mitchst2:
If you choose this method will you lose data? I.e. will you be able to add a second ROM whilst leaving your current ROM intact?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes you will loose all data in both cases (A/B Userdata layout and A/B/C Userdata layout) as it will delete the whole userdata partiton and re-create it as userdata_a and userdata_b (and userdata2 in case of common data).

So you have to do a backup of all data before and you have to re-install your ROMS in both slots after doing this!
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
New Updated Version v2.3

Happy weekend! :highfive:

New Update is up. v2.3

10/17/2020 - 3.4.0-0 v2.3

- Fixed mounting of Common data partition

You need to choose to install Magisk from the Dualboot-TWRP while flashing when you want to use the Common Data partition. The way I have implemented this now needs to use Magisk!

That Magisk from the script will install Magisk 21.0 but you can afterwards just install another Magisk Version per slot like a Canary Version!

Download is updated in the OP or otherwise here.

[MENTION=7030109]mcdachpappe[/MENTION] Here is an updated Version for the 64GB Oneplus 6 as well!
[OnePlus 6 & 6T Cross Device Development] RMarques:
[MENTION=9574498]Wishmasterflo[/MENTION]

Thanks for the update. After a bit of time setting it up and adjusting, I can say it's a keeper as well as a daily driver ready job what you've done here sir!

OP6 8/128

Slot A 32GB

Lastest OOS + Magisk + xXx Module + ACC Module + ROM Switcher Module + RadioActive Kernel

Slot B 32GB

PiXeN 11 + Magisk + ACC Module + ROM Switcher Module + RadioActive Kernel

Rock solid! :victory::highfive:
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Hi!

Thats great to hear. Thanks a lot. :)

Here some screenshots of what I just implemented for the next Version update. :)
[OnePlus 6 & 6T Cross Device Development] RMarques:
I need that!
[OnePlus 6 & 6T Cross Device Development] brajesh.sharma87:
How do you deal with whatsapp between roms, just curious.
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Hi, thanks for bringing this up for 6/6t and for your work on fixing out all the bugs/issues that were present in v1. may you please consider this as a friendly reminder to my earlier request of having a bit more userdata space whilst using A/B/C layout on 128gb models...? i am in no way asking you to rush this but infact im just excited to see your response. Goodluck with this project and stay safe ?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes of course I can easy adjust that. I am just thinking about how to set that exactly. So for now when using A/B Layout it will just split up the space in half and for the A/B/C Layout you can choose between 16GB or 32GB per partition and the rest will go the the Common Data.

So perhaps I should adjust that to 20 GB and 45 GB or something ??
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Yes around 45gb should be perfect and that would leave something like 10 or 12 gb for the commondata partiton which is plenty to store 2 roms and some related files alongside them. i am very thankful for your friendly and fast response, much appreciated:fingers-crossed:
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Good. Yes I guess then I will change if for the 128 GB devices from 16GB or 32GB to 32GB or 45GB and the rest goes to the Common data. :)
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Sounds real good! again, Thanks alot for taking this into consideration and i wish you the best with this project:laugh::good:
[OnePlus 6 & 6T Cross Device Development] koobie777:
Awesome!
[OnePlus 6 & 6T Cross Device Development] RMarques:
I had this very same doubt. It ended up being like if I never did nothing. Everything is available in both slots. What I did was taking a back up of all my apps and restoring them in each slot.

Every time I boot into one slot, whatsapp, telegram and everything else is there, ready to be used right of the bat!
[OnePlus 6 & 6T Cross Device Development] koobie777:
Seems with the latest 2.3 the zip is made with the folder instead of just the files. Re-zipping fixed for me.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Ohhh ok. Let me check. Thanks for the heads up. Anyway Version 3 is already in the works with improvments and new options for the storage size partitioning. :)

EDIT: ZIP files are corrected and re-uploaded now.
[OnePlus 6 & 6T Cross Device Development] andyjjc:
video guide? Please?:o
[OnePlus 6 & 6T Cross Device Development] isoladisegnata:
+1
[OnePlus 6 & 6T Cross Device Development] RMarques:
Hey there,

I'm kind of a visual learner as well, but trust me, it isn't that hard of a thing to do.

Just follow these steps:

1.

Take a full nandroid back up, place it on your PC

2.

Take an individual backup of any files you may need and/or are importante to you

3.

Take a backup of your apps and data. I did use OABX, it's a free project, stack on XDA to find it.

Suggestions:

1.

l did use a USG OTG in order to place in it all the files that I'd be flashing

2.

Get the above mentioned steps done and wait for V3, I'm sure it'll be even better than V2 already is!

Like always in e flashing scene, you'll need to play around with it in order to set everything up to your needs!

Thanks again [MENTION=9574498]Wishmasterflo[/MENTION] for this amazing project, for your time and support!
[OnePlus 6 & 6T Cross Device Development] brajesh.sharma87:
So, you are saying, you can use whatsapp on both the roms? You see all the messages updated on both slot, each time you reboot on other slot? With telegram and messenger, that can happen but with whatsapp, I guess it works differently. [MENTION=9574498]Wishmasterflo[/MENTION] whats your observation on this?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
I dont use Whatsapp actually. :)
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
I dont have any good possibility to make a Video guide now but if someone else wants to create one, feel free to do so.

I am right now hard working on Version 3 with new cool features, options, and improvments and perhaps I will even leave the BETA stage with that so stay tuned. :):o
[OnePlus 6 & 6T Cross Device Development] RMarques:
Nope, I was trying to say it's there ready to be used, without any sort of confirmations or setup stuff to be done.

Every msg interactions remains in the slot you've had it.

Let's say someone does msg you "Good morning" on slot A, this specific msg will remain on your whatsapp on slot A.

When you boot on slot B, you'll be able to use WhatsApp right off the bat, but you won't be able to see that "Good morning" msg you received on slot A.

It's important to have in mind what this project mainly allows you to do and it's main goal IMHO.

To have the ROM the majority of us are used to (OOS) as our daily driver and yet to be able to test whatever we want on the opposite slot, having always in hand our main ROM ready to be used whenever we need it.

In my case, I've been using PiXeN OS 11 as my secondary ROM and I got to be honest, it has grown on me so much that I've been using it non stop now. I barely even got back to OOS!
[OnePlus 6 & 6T Cross Device Development] brajesh.sharma87:
About whatsapp, its exactly what I thought. Thats beyond the scope of any dual boot mechanism.

About dual boot, its really great. I was looking for a working way on my 6t. In past, I have used dual/tripple boot kernel mods. Also, uses multirom on many devices which is dead now. I am always in favour of such project.

Thanks [MENTION=9574498]Wishmasterflo[/MENTION] for your time and effort.
[OnePlus 6 & 6T Cross Device Development] mitchst2:
Following on from the conversations above shared app installations to common data would be brilliant if possible. Imagine settling up one ROM, installing and setting up all your apps then moving to the second ROM and they're all there pre-installed and setup. When I read common data originally this is what I imagined.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
New Updated Version 3

Hi all!

Now Version 3 is up and I also left the beta stage with that one. :highfive:

10/20/2020 - 3.4.0-0 v3

- Added Blackout TWRP Themed by acuicultor and Morphine1

- Added support/detection for 64GB Oneplus 6 enchilada devices

- Added that Magisk 21.0 does not get flashed on Android 11 ROMs (as that is not working now!)

- removed automatic launch of Common data mount script on Android 11 as that caused strange behaviour when rebooting the phone!

- Some more small adjustments in the flashing script

- Adjusted sizes for the userdata partitions when using A/B/C Layout as follows:

64GB 16, 24 GB partition size for A/B/C Layout

128GB 16, 32, 40, 45 GB partition size for A/B/C Layout

256GB 16, 32, 64, 96 GB partition size for A/B/C Layout

Download link is updated in the OP or otherwise here.

On Android 11 there are some issues with the Magisk Version we can run on Android 11 now which caused some strange behaviour when rebooting the phone from Android 11 when the Common Data mount script was

injected there so for now I removed it when an Android 11 ROM as installed.

Also Magisk needs to be flashed manually on Android 11 now. The Dualboot will not flash Magisk anymore when an Android 11 ROM is detected.

I hope we will get a better working Version of Magisk on Android 11 soon that hopefully will fix some of the issues existing due to that now!

Have fun! :o
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Thank you for v3? i will report back as soon as i get to flashing this! Have a good day/night :>
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Hii, I just installed this using the A/B/C layout with dm-verity disabled, forceencryption disabled and with magisk enabled. i installed posp11 on slot A and oos on slot B but I am not seeing the commondata partition in my oos rom, i thought it was only disabled for A11 roms? thanks for the answer in advance.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Hi. Yes it should work in OOS. Try if ir works when you reflash the dualboot TWRP once again now after Magisk and everything is installed.

Take a look during the flashing if you see the message Installing Common Data mount script.
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Yes i just did that and now i can see the commondata folder in internal storage. but im having some other slight problems currently, i can not set any type of password on posp11, it gives me a toast message saying that the passowrd had already been changed and it just discards my attempt at setting a password. i tried setting a password on oos and it worked but when i enter it from the lockscreen it says that my password is invalid {i tried this twice} luckily im not encrypted so i delelted the lockscreen files using twrp. and finally i see in the flashing script that it says it's flashing magisk21.0, but i got magisk 20.4 in oos10 which leads me to believe that you might've included 20.4 or mislabled it in the flashing script. that isn't a problem for me but i just wanted to point it out anyway. i know this message is long enough already but could you also tell me which file in the zip is responsible for the re-partitioning sizing? i might try and experiment with different sizes later for fun lol. thanks in advance and sorry for the paragraph.

https://ibb.co/9WL4k9S