yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
Yeah I kinda figured that's how it worked. It's just, when I first posted my enthusiasm about this, I mentioned I wanted paranoid android as one of them. OP said it wasn't working (yet) with that partition layout. That is nice to not lose the data from formatting, didnt know that.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Paranoid Android should work with v4
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Ok you guys, I feel like an idiot, but I've been struggling with the mounts.txt concept, which I feel is probably the simplest part of the whole process, but it's been making my head hurt. I think I finally might understand it, but if someone could please confirm what I think I have figured out...

Basically any folder you list in mounts.txt, which you place in datacommon, will also show up in sdcard, also temporarily overwriting any folder in sdcard with the same name. I think my main issue was understanding how to utilize efficiently, but here's what im thinking...

So ideally you would use this to make certain folders (like and music or pictures) available to both partitions by deleting or emptying The corresponding folder in sdcard and instead populating the common data folder with your media. This serves a dual purpose, making any files you choose universally accessible while simultaneously giving you the ability to segregate any files you want to be invisible to one partition, and it also saves storage by eliminating the need to have shared files stored in 2 locations. However, here's where I get stuck... No matter which partition you have active, you can still go into the file tree and access any of these folders by navigating to common data directly, so... Why not just store them there and leave it at that? Any files you want isolated can be stored only in the sdcard and the rest, in common data, will be available everywhere... What am I missing?
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
I don't think it's intended to hide anything. Data in slot a will only be available and visible for the room in slot a.

I think the intended used is for aid using standard locations, like music or downloads. Not all apps allow aloe to set a pay manually.
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Right but any files you need you can just go straight to common data no matter which partition youre using
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
First of all, thanks to the dev for a great tool.

I am not a dev and I don't know if the following suggestions are even possible but in my opinion this tool could be simplified in 2 ways.

1. Do not include Magisk.

Make it a requirement to flash for certain ROMs (like OOS).

Including it will often result in an outdated Magisk version.

2. Make common days mount as an external sd-card.

Many apps would be able to more easily access it and there are many told available to manage data on sd-cards, making the need for extra mount options obsolete.

No need to reinvent the wheel.

Maybe something to think about for a next version.
[OnePlus 7 & 7 Pro Cross Device Development] esi2121:
Any suggestion??? Any fix? what is my wrong???
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
has anybody tried this with the new open beta?

i've been reading the support thread in this forum, everyone freaking about some bug that makes people's password stop working when they restart after update. at first i wondered very curiously whether that was somehow related to the issues we've been having? didn't you say it was a hardware related issue and that's why we can't fix? but very soon i stopped wondering about that because i was too disctracted laughing at all the people throwing hissy fits and going into panic mode because their screen password isn't working....it seems like such a trivial issue to me after playing with this mod for so long xD....i spent so much time on this particular thread i feel like everyone i talk to should already know the information, even if they weren't here for any of it xD

butfor real...has anyboyd tried this with new open beta? i'd like to give it a shot, but is there anything about upgrading to another android that would combine with this and make my phone catch on fire, or blow up, or spit in my face and then blow up?
[OnePlus 7 & 7 Pro Cross Device Development] esi2121:
what ia best size for slot a/b for best performance ?

in my case i have 25Gb of apps

---------- Post added at 01:49 PM ---------- Previous post was at 01:46 PM ----------

i have issue with password on my oos, after i boot custom rom in other slut and revert back my backup from /datacommon and going back to oos , password didn't work
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
I can't tell if he's being serious or not...

yes, friend, this is a known issue. it's pointed out by the OP on the first page with a link to a possible workaround that has only had occasional success but is still the best solution available. then it is discussed at great length, several times, throughout the entire thread, in multiple distict conversations, some resolving with a positive solution and others not so much. finally this most recent time we came to the conclusion that this problem cannot be fixed, at least not by anyone here (or i would think not by anyone on this device). thus, the best way to deal with it is to disable encryption on the phone and then leave one partition unlocked, i.e., don't set a password. if you have a password set on one, and then you set a password on the other, it will leave you unable to access the first until you delete the password files in twrp, and if you keep resetting a new password every time you boot, it'll keep happening over and over until you get better at words, reading more of them and using fewer.
[OnePlus 7 & 7 Pro Cross Device Development] fxz:
Installation fail

Hey, I was trying this with OOS and Carbonrom. Every time I flash the twrp dualboot zip it gets stuck on "patching inactive slot: _a..." How can I fix this? The installer doesn't stop or anything, and I'm not sure if it's safe to restart.
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
Don't know the fix, but I have had to reboot to fastboot and do "fastboot --set-active=other" then reboot recovery and redo the installer again. My work around is after a rom go to reboot click the opposite slot and the the current then reboot recovery and flash installer.

---------- Post added at 09:18 PM ---------- Previous post was at 09:16 PM ----------

I use mounts so that my downloads and pictures are in the same folder from both slots. Like chrome download location can't be changed.
[OnePlus 7 & 7 Pro Cross Device Development] billyt1:
Yeah I got open beta 12 on a and lineageOS on b.

I also disable dmverty ,encryption, f2fs on both slots. And I use swipe to unlock so no password. nothing to hide ;)
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
ok interesting, so if i mount a folder called downloads, and it takes the place of a folder that already exists in that partition, any files i subsequently move to that folder on that partition will be saved to the shared version of that partition, thus becoming available on the other partition as well? i was not aware of this....very clever. glad i asked, i never would have thought of that.

another question, regarding the partition sizing, how does the phone react if you try to mount a folder with contents greater than the available storage on that partition? like my a/b are 32 gb each, leaving like 120 or so for c...but if i store all my crap in there and mount those folders...what if i mount one folder with 50 gigs of movies or whatever? has anybody experimented with this?
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
I don't think it affects it, it's kind of like symlink I think
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
ok great, that would address my primary concerns, specifically some sort of malfunction when the phone suddenly has access to more data than it believes it can hold or perhaps limited accessibility to files past the size of the partition....but it brings up another curiosity i have....if that is the case, is there a reliable way to view how much free space is actually left in a given partition from within the android UI? i assume you could just go into the file tree using a pc and a usb cable and check, but is there a place where this data is not distorted or confused by the mounting of a large file over a small partition?
[OnePlus 7 & 7 Pro Cross Device Development] oscarmaldonado:
Titanium Backup recognizes the size of the partition.
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
Resurrection remix anyone? Common doesn't show up
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Try flashing the dual boot zip again from the data partition of your ROM.
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
Well I'm finally taken the dive into dualboot. I've gotten the boot animation of paranoid android, but doesn't seem to want to boot. and my other slot is doing nothing. Other slot may be because I tried to adb sideload a full ota package? or maybe because I started just from booting to twrp/flashing dualboot from my last working setup? EIther way, I'm just gonna start from scratch if PA doesn't boot up soon. Been awhile since I've done much like this with my phone, I missed it!
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Have you done a Format Data on the slot which is not booting?
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Thank you so much!! I'm not the one who asked the question, but I was having the same issue and this totally worked!
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
I did not. Kinda thought the dualboot zip was going to format everything. PA didn't even boot. Gonna be starting from scratch tomorrow morning. Formatting everything, maybe even just use msm to start completely from scratch.
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
If you change layout (which I recommend), yes it will format data from both slots.

Once you get your main ROM/slot setup, get back into TWRP and flash the 2nd ROM then the dualboot zip. Note: make sure to read carefully so that the dualboot script can put the zip in the tmp folder to be able to change the layout and format data.

If you need GApps, wait until the dualboot script is done, then reboot back into TWRP but in the 2nd ROM/slot and flash it.

After that, you should be good. Planning on running Paranoid + OOS?
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
In addition to that;

When flashing this zip again after you installed your system, flash it from the data partition, not from the temp position anymore. This seems to avoid some mounting issues with the common data partition of you use it.
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
Thanks for the info! Hopefully I can get it going today. Yeah,trying for those 2. PA and oos with no limits.
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
Thanks! I feel like I finally got it working, but Paranoid android is just stuck booting. I'm not entirely sure if I did it all right though. I got this twrp going, then I installed a full OOS package on both slots, flashed this zip again, then PA on one slot and dualboot zip again.

Although I am not sure if I should be installing OOS through twrp or not..

I'm setup as stock right now, from msm. How do I proceed?

Unlock bootloader

boot twrp

flash this twrp

reboot twrp

install oos through twrp to both slots (not sure if I am doing this right or not)

reboot twrp

install rom on one slot

flash this twrp

?

Those are the steps I took, but I still haven't been able to get anything to boot. I thought this was just gonna be get the twrp installed and flash both roms I want to separate slots. But it seems a little more complicated than that. I'm not bad at messing with my phone but I'm kinda lost on this one right now.

Well I feel like I did everything right, no slot will boot though. Might just have to give up on dualboot.

I've given up.. Just going with PA no dual boot.
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
I numbered your steps above. Step 3 is where you went wrong. You initially just need to have OOS installed and working. MSM tool will do that for you in step 0 (after you go through initial setup). Then proceed with steps 1 & 2 (assuming you're booting into TWRP 3.3.1-79 and then flash the installer TWRP to make it permanent on both slots). Next, instead of using this TWRP in step 3, flash the PA ROM then this TWRP (and follow my previous instructions from there).

It is difficult. It took me a while to figure out the mechanics after many failures but if it's not for everybody so I understand.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
That would work but after installing the ROMs you need to format (full format, not just wipe) the data partitions.

Unlock bootloader

boot twrp

flash this twrp from temp partition

reboot twrp

install oos through twrp (it will install to the inactive slot)

Flash this twrp again from data partition

Reboot twrp (it will automatically boot to the skit where you just installed oos)

Format data

Flash Magisk (or use this twrp to include Magisk, but make sure it's in the right slot; oos needs Magisk)

If you want you can boot and setup oos now to see if everything went correct. Or continue with flashing the other slot.

reboot twrp

install rom

flash this twrp from data partition

Reboot twrp again (again it will change slot)

Format data

Flash gapps.

Flash Magisk.

Boot second ROM.

Remember ROMs always flash to the inactive slot.

Rebooting after flashing a ROM will change the active slot automatically.

Use full formats on data to remove encryptions.

Remember there password limitations. If during setup you are required to set a password to can remove it once so it's complete before you reboot (not sure if this works out you use encryption)
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
Thanks, both of you! I gave up for today but I definitely want this working eventually so this will help a lot. Msm'd my device like 4 times attempting to get this right and just said screw it. I'mma just stick with the clean PA install I got going right now.

Really appreciate the help tho and I will definitely use this help in the future!
[OnePlus 7 & 7 Pro Cross Device Development] Imminent-darkness:
This is truly outstanding! Much respect!

I read through this whole thread, page by page a couple weeks ago to find the answer to this question that was already asked:

I wanted to refrain from asking again in an attempt to avoid cluttering the thread with repeated questions, but it looks like this one might have slipped through the cracks. Does the developer or anybody else know of any issues that would stand in the way of dual booting Android Pie and Android 10?

Thank you again for sharing the fruits of your impressive developing skills and exercising patience with all these questions.
[OnePlus 7 & 7 Pro Cross Device Development] king-totti85:
yes it will work.. it worked for me.. in a/b/c layout android 9 "carbon rom" booted and worked fine with oos 10 in the other slot.. but I don't remember if common data worked.
[OnePlus 7 & 7 Pro Cross Device Development] oscarmaldonado:
Well guys here I go, excuse my ignorance when it comes to cellphones, computers etc. My question to you guys is what can I do to have all my downloads, music and everything else to go straight to CommonData, I'm always transferring all my downloads manually, I read the OP and I'm totally blank, I don't understand any of it, so can someone explain step by step how to create that or what to do? Thanks in advance guys and stay safe.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
You copy all your files you want to have in both ROMS to the Common Data partition.

Then you create a file called Mounts.txt in Commondata and in that file you write the folders from your Commondata you want to mount directly over internal storage like Music, or Downloads (one folder per line).
[OnePlus 7 & 7 Pro Cross Device Development] oscarmaldonado:
Thanks for your reply bud, one more question, looking at the extension (Mounts.txt)that needs to be created using notepad in windows? Thanks again.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes exactly you can create that file with the Notepad in Windows.
[OnePlus 7 & 7 Pro Cross Device Development] oscarmaldonado:
Thanks again bud.
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
Actually there is one,if you flash magisk to the inactive slot in manager then the next reboot will be to the inactive slot,so maybe topjohnwu can do something like a switch in the app right?
[OnePlus 7 & 7 Pro Cross Device Development] Imminent-darkness:
Thank you for taking the time to clear this up for me. It is much appreciated.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Osmosis, you're the most knowledgeable person I know when it comes to scripting. Would you be able to help out here.

Do you know a possibility to reboot from one slot to the other slot without having to go into recovery first?

Or do you know how Magisk (and ota's) do it?

---------- Post added at 04:44 AM ---------- Previous post was at 04:33 AM ----------

I have a a/b/c setup with OOS on slot A as my daily driver and using slot B fort testing custom ROMs.

So slot A is fully setup and I don't need to touch it.

But every time I flag a new ROM to sit slot B I need to re-flash the dual boot zip. Doing so well also re-flash Magisk on slot A.

After which I need to update again.

And several times i lost all my Magisk settings and modules.

Is it possible to flash to one slot?
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
There is an issue

My current setup:

Omni treskmod latest on slot A,clean flashed

crDroid clean flashed,latest on slot B

In crdroid, Commondata is mounted and I can access files and everything works crystal.

In Omni treskmod,after first boot common data was not mounted so I flashed the dualboot zip from recovery again,now the commondata folder is shown in file manager but I can't open it, it's more like empty.Tried to open datacommon from root,not opening.Tried multiple reboots and reflashing again,still no luck

Previously I had oos in slot A and I was able to mount datacommon in both the slots just fine

I have tried resurrection remix,and omni and their different builds,still the same.

Any ideas?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Have you flashed the Dualboot ZIP from your Data partition of the ROM when re-flashing it?
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
At first,then reflashed it from tmp,still no change
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
From tmp only flashing when doing it the first time and whe n you do a re-partition. Later only flash from the Data partition.
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
I am not flashing it for the first time,like I said I had successfully booted oos and crdroid both of them mounting datacommon without an issue,after flashing other roms only crdroid was capable of mounting it

Or am I understanding your reply wrongly?

I flashed oos 10.3.3 and zip(from data) and booted on slot a,datacommon was mounted and I was able to access files

Flashed omni over it,then the zip(from tmp),then formatted data and rebooted,still the same problem.

Flashed the zip again from data,still nothing.

Even tried formatting common data,still no change

The folder common data is shown in file manager,I can add files and folders into it but it's like part of internal storage, formatting common data didn't change its contents (and these are not appearing in /datacommon)
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
It's a kernel issue, try some custom kernels that's how I get it to work when it absolutely won't
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
It is definitely kernel.

Kirisakura didn't work,arter did

You are awesome ?

But there is a problem,using arter kernel breaks fp,using kirisakura or smurf datacommon cannot be mounted.

Any other way?
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
kirisakura with magisk module kernel sepolicy patch, works for me.
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
This
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
I will definitely give it a shot

Thank you?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Ahh ok. So with SmurfKernel the datacommon is not working? Thats good to know.

And is the Kernel to be flashed to the current slot or is it flashing to the opposite slot as it is when flashing the ROMs?
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
Flashes to current slot. The module I posted should help Mount common data
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
SmurfKernel is not mounting in Omni treskmod,I don't know about oos

Kernel always flashes to the current slot.

---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------

Didn't work for me

Can you please tell me the steps you followed so I can do it all correct from start
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
Kernel, module and dual boot all flashed in twrp
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
In that case it's the same as mentioned many times before and at least for this kennel, not kennel dependent.

If commondata doesn't mount flash the dual boot zip again, but make sure your bored to the slot where the issue is and that the zip is on the data partition (not tmp or commondata).
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
Module should be flashed selecting permissive selinux right?

Didn't work though.

I think there is no way:rolleyes:

---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------

Still not mounting

---------- Post added at 07:56 AM ---------- Previous post was at 07:40 AM ----------

I think the issue is that omni won't set selinux as permissive (mentioned in OP that some Roms might not work with the mod)

This actually figures because if you set selinux to permissive then android trust should show up mentioning that selinux is set to permissive.In my case it doesn't.

Now I can sleep peacefully:o
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
Yeah Omni has issues with dual boot, I forgot about that.
[OnePlus 7 & 7 Pro Cross Device Development] Imminent-darkness:
Behavior of ROM overlay

Does anybody happen to know whether a ROM overlay, such as Nethunter, flashes to current slot or inactive slot.
[OnePlus 7 & 7 Pro Cross Device Development] Imminent-darkness:
Dual booting Android 9 and 10

I just tried this and it doesn't seem to work well with the sim card. The network worked on the slot with 10 but locked 9 out of it.
[OnePlus 7 & 7 Pro Cross Device Development] Ae3NerdGod:
I made a fork that adds the ability to set options in the zip name, repartition from /usb storage, and has a failsafe option

here is the links if anyone wants to try it.

updated readme: https://github.com/Ae3NerdGod/TWRP-DualBoot-Guac-Unified/blob/master/README.md

premade zip: http://bowtie-ent.com/stuff/TWRP-DualBoot-Guac-Unified.zip

source code fork: https://github.com/Ae3NerdGod/TWRP-DualBoot-Guac-Unified

[MENTION=6037748]Zackptg5[/MENTION]

made a pull request Check GitHub.
[OnePlus 7 & 7 Pro Cross Device Development] Ae3NerdGod:
was the 9 rom you were flashing OOS? sounds like a modem version issue

try flashing the official oos 9.5.13 rom to the slot before you flash the custom 9 rom

just so you know to me that sounds like a bad idea. id try to stick with one android version