yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
it's sounding more and more like it's installing from common data is causing issues across the board...i'm gonna try reflashing everything right now from internal storage and setting passwords right away and see what happens...if it doesn't work i will then try this method+the github workaround, perhaps that will be the magic number...report back soon.

---------- Post added at 01:59 PM ---------- Previous post was at 01:11 PM ----------

no joy, first attempt gave incorrect password error on partition A. about to try adding the workaround, and this time i'm going to install from OTG. also, something you mentioned earlier pinged a thought in my head...

if you look at the github method, it says that you make a twrp backup of "userdata," and i remember thinking that was odd because there was no option for "userdata" and dude is usually pretty careful about using precise syntax and stuff...well i've been backing up the data partition and restoring that...did it once with data and boot...but you said that commondata is userdata2, so...userdata is an entire partition, right? which one is it? it must be called something else in my twrp, and i think i may have been doing this wrong.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Just a quick reminder to read the limitations section in the OP. The last couple pages have been rehashing (sometimes incorrectly) already established limitations
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Hmm....not sure exactly what I did wrong now. I tried to set it up with one slot encrypted and the other unencrypted and did a Backup of "Data" in TWRP as mentioned in the limitations. The ROM on the unencrypted slot is booting fine but the ROM I flashed on the other slot is not booting. When I switch to that slot now and try to boot from it it is just booting back into TWRP.

Perhaps for now I should just leave both slots unencrypted and retry it and without setting a password on both slots.

Edit: I tried now to redo everything leaving both slots unencrypted but now the ROM on one slot is just staying forever at the Boot screen and the other Slot/ROM is booting and working fine.

Not sure what exactly I did wrong here now. I mean I had it already working from both slots when I was trying this Dualboot the first time like 2 weeks ago.
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
that is what happened to me the first time i tried to follow the guide to the letter. there must be some detail we're missing. my best guess is that it has to do with how we do the, backup/restore but i don't know what...no matter what i do, as soon as i put a password on the second slot, i either get a bootloop or invalid password glitch. i'm at a loss.
[OnePlus 7 & 7 Pro Cross Device Development] RenanM1989:
I understood what you meant.

I've done several installations (until it worked). So, I don't specifically remember how it worked, the way you want it to be (with a password that doesn't "disable" the other partition).

I will tell you my conditions (which I remember):

I left the 2 partitions at EXT4;

I disabled encryption on the 2 roms;

I always use an OTG / USB to install the roms;

I always install the most up-to-date Oxygen OS rom and then install "at the top" the rom I want. Then, I install the modified TWRP again;

If the second rom doesn't boot, I boot twrp, switch to the slot where the rom I just installed is and format the data. And I try to boot again;

To restore my backup, I do the backup through titanium backup and then do the restoration after initializing the rom;

I will try to do these procedures again and make a video (or pictures). If it works, I'll post here the step by step I did.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yea....got it. After I read your post here I did a FORMAT DATA on the Slot where the ROM was not booting and after that I got that to boot. :)
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Above is from the OP

---------- Post added at 06:55 PM ---------- Previous post was at 06:50 PM ----------

It's it possible to have common data emulate a external sd card?

That way many apps would have direct access to it without mounting folders.
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Yeah man, we're all aware of the limitations...what we're discussing isn't surprise that the password issue exists, but how to fix it, because all of us are trying our best to follow the workaround you give us in the github linked in the OP...unfortunately none of us can make it work correctly, which is why i've asked for your help a few times. apparently there is a step somewhere in there that we're not interpreting correctly. sure could use your assistance figuring out which one it is and where we've gone wrong so we can enjoy the marvelous work you've done as it was intended.:fingers-crossed:
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
The problem is at a hardware level so there's no fix for it unfortunately. The workaround I outlined is the only solution currently. Easiest option is to stay unencrypted on both slots.

What it ultimately boils down to, you can only set a lockscreen passcode on one of the slots
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Then that's where we've all gone wrong...we've all been under the impression that the workaround was how you get a passcode working on both slots...but what you're saying is that allows you to alternate between the 2 slots without losing data by following this procedure every time you switch in order to keep your active slot password protected...is that right?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Theoretically, the workaround is that you setup one slot, backup data, then setup the other slot, the switch back to the first slot and restore data. It may work but as you can see, mileage varies a lot. I recommend just not even setting a passcode for one of the slots.

Password protect your main slot and don't with your second one. Still backup data though because some roms apply a lockscreen by default
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yeah I thought that too. So for now I stay unencrypted and without setting a passcode at all.

I had no luck when trying to do the workaround for only one slot set with a passcode.

That data backup in TWRP I do from the slot where I set a passcode and then restore it again to the same slot after setting up the second slot without a passcode or??
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
1.Flash OOS/twrp on both slots. leave both unencrypted.

2.Boot OOS in slot A and setup w/ password

3. Reboot to twrp in slot A, perform nandroid backup, storing backup on slot C

4. Reboot to twrp in slot B and reformat data

5. Reboot to twrp in slot A and flash custom ROM (will install on slot B)

6. Boot system in slot B and setup password

At this point, setting up the password will render slot A inaccessible. You have 2 options...

1. theoretically, you can restore the backup you made before you flashed a new rom in slot b and it should allow you to boot slot a again. if not...

2. go to twrp in slot A and delete the lockscreen settings files to remove the password in slot A. This will allow you to set slot A back up and use it again, but setting a new password will leave you unable to access slot B, so you're just backwards now...best bet is to do steps 1 through 5, then just don't setup the password for slot B and you will be able to use both slots at will

I see...I suppose we were all (or at least i was) under the impression that the workaround was more consistent, assuming one applied it correctly. i've spent the last 2 days trying to figure out what i was doing wrong...womp xD

oh well, at least now i know i've got it working as well as it can be. i'll just reformat my partitions so slot b is very small so it's less intrusive and use it for my play slot....actually now that i'm thinking about it..

TO ANYONE STILL READING THIS THREAD...

How are you guys setting up the size of your partitions? now that we have options, it obviously comes down to personal preference....there's no right or wrong way, but which size layout have you chosen, and why do you find it to be the most convenient for you?

Personally I think my idea would be (for a 256 gb device)...

Slot a - 128gb

slot b - 32gb

slot c - 96gb

Reasoning is that, given the password issue, functionality of slot b is a bit limited, i will use it more for experimentation. slot A gets the most because i'll be using it the most, and slot c gets everything that's leftover. i have slot A bigger than c because while the ability to share data between the 2 ROMs is really cool, the lack of a password on slot b leaves an obvious security concern...this setup gives me plenty of storage for anything i might need to use on both partitions while leaving slot A big enough to keep any secure data inaccessible from slot b.

now that i've typed this i can't remember if the sizes are indeed that flexible...i was so nervous when i reformatted them i forgot haha...anyway, possible or not, that's what i would prefer...thoughts?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Do I need to flash OOS first on both slots? (even if I plan to have a custom ROM (and no OOS) on both slots?)

It is so I have it now. I didnt flash OOS first before doing all this. :confused:

Because now I just recognized that I can not turn on WiFI in any of the ROMs I flashed so I wonder if it has something to do with how I start to flash this here?

And step 3 to perform a nandroid Backup, it is just DATA I need to Backup or more? Just to be sure.

Also by some reason I only have commondata visible from one of my ROMs (EvolutionX) but not from the other (AOSiP).

Thank you.
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Flashing oos first is like a redundancy, it's probably not necessary, but it's something that we know works, is safe and stable, and it's what your phone was made to run. It gives you a working base to start from so, so if you try to flash something else on it right after and it gives you problems you have a good idea of where you did something wrong.

The Android backup... I was a little unsure of that myself, the first couple times I just tried data and the next few times I did the whole phone, all partitions, and I got the same result both times. Honestly the workaround never worked for me, so I don't use those steps anymore, I was just lining them out for you. The idea is to use the backup to undo whatever the password setting does to mess it up but we've been unable to make it work consistently. Just make sure you have a backup to restore whatever you want to keep in case anything does wrong.
[OnePlus 7 & 7 Pro Cross Device Development] RenanM1989:
Hello.

I actually reinstalled my roms - i know that "problem" exists. I really wanted to take the test - and I had this password problem. I made these new installations to really test if it would work.

Searching the internet, I found that through TWRP it is possible to delete password protection and log in again. At least it is not necessary to reinstall the entire ROM again.

What I was thinking here is this: if there is a file where the password is, and deleting the file, the password - and thus, the protection - "ends", wouldn't it be possible to create a password file that would be usable for the 2 ROMs? Or copy that file and paste into the other ROM?

If I'm talking nonsense, tell me :)
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Do you already have the answer??
[OnePlus 7 & 7 Pro Cross Device Development] mjb337:
yes with know help I had to figure it out now I'm switching ROMs like there's no tomorrow thanks anyway
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Tell me the answer,,i need that too,,
[OnePlus 7 & 7 Pro Cross Device Development] mjb337:
after flashing what felt like days I finally figured it out. Flashing from the inactive slot only install the same rom to the active slot but if you flash whatever rom you want from the active slot it'll automatically flash the new rom to the inactive slot. Of course I always format the inactive slot then switch to the active slot then reboot recovery then flash whatever rom I want from the active slot which automatically install to the inactive slot. For example if I'm running (oss on active slot A) and want (aosp on inactive slot B) I'll have to flash (aosp from active slot A) which automatically flashes new rom to (inactive slot B)...hope I explained this correctly.....
[OnePlus 7 & 7 Pro Cross Device Development] daveve:
Can you please tell me which steps you did because I am not able to run oos on dual boot, keeps hanging and crashing
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
mounts.txt

I have created a mounts.txt file in /datacommon to mount folders which are in my CommonData partition. Install and Music

So I put it like this in my mounts.txt and place the file in /datacommon:

Install

Music

After restarting my phone I can see the 2 folders Install and Music mounted on my /SDCARD but I dont see any files in there.

I think I should see all the files which are in Commondata/Install now in SDCARD/Install or???

Because the ones mounted over SDCARD now are empty and dont show any files. Or am I thinking or doing something wrong here?
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
You cant mount folder that inside is a folder,,its must be folder inside a files,
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
I have both folders and files inside the folder I want to mount. So it will only work if inside the folder I want to mount are only files and no sub-folders???
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Yes,,you can try it,,,folder that inside only files
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
I have folders inside my mounted folders and it works just fine.

So that isn't the issue.

Try flashing the dual boot zip again, and make sure you flash it from internal storage, not common data.

If that doesn't work, then I don't know.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Have tried that now but still the same that I dont see any files in my mounted folders.
[OnePlus 7 & 7 Pro Cross Device Development] CaeLum764:
Edit: Fixed
[OnePlus 7 & 7 Pro Cross Device Development] mjb337:
first thing I do is format data on (slot A and slot B) before flashing dual boot recovery. After flashing dual boot here is what I do. Flash oos on (slot A then flash dual boot afterwards then reboot to recovery. Again flash oos on (slot B then flash dual boot afterwards then reboot recovery. Now that I have oos on both slots I then flash whatever rom I want and that's it. If oos don't boot format data and it'll boot right up...
[OnePlus 7 & 7 Pro Cross Device Development] Velrix:
So I am getting a weird message now on boot that says SMT Download Failed "Please check your download flow is right". The phone does work however and boots but I am not sure how I can get rid of that. I have used the MSMTool which did not fix it.

I also cant use DHCP at all anymore. I have to statically assign WIFI IP's now :X
[OnePlus 7 & 7 Pro Cross Device Development] vettejock99:
I'm getting the same SMT message. I also get a NV backup warning when booted, says Dynanamic partition is invalid. It appears my sensors and maybe my IMEI is borked, and I've flashed all sorts of factory ROMs via MSM and I can't fix it. I first went wrong at the last step of OPs instructions, because I think they're unclear. Running the command showed a list of numbers, and I just plugged the last one, the largest one, in and it messed up the entire partition table. I've bricked and recovered tons of phones before, but this is the worst. Definitely if you try this, make sure you have a backup of ALL partiitons, including EFS, etc..
[OnePlus 7 & 7 Pro Cross Device Development] SUPNYUS:
Woah, how did you manage to do this :eek: I just followed someone's steps in this thread and it worked really simple and smooth for me !
[OnePlus 7 & 7 Pro Cross Device Development] vettejock99:
By messing up the last step in OPs first post. Now I'm in desperate search of the T-Mobile MSM recovery pack because the thread here for that has an expired link and no one has posted a mirror. My phone can make calls, but no data, no text messages, no orientation sensors, etc.
[OnePlus 7 & 7 Pro Cross Device Development] SUPNYUS:
Oof, good luck with that :'(
[OnePlus 7 & 7 Pro Cross Device Development] sekk:
sorry, I didn't understand exactly how to properly install it

from the beginning, see if the steps are right:

unlock bootloader

boot mauronofrio twrp

install twrp.zip

install magisk.zip

with all set up, go to twrp again and flash you mod.zip?

after flashing it, what should I do, and how would I install 2 ROMS on the device?

thanks in advance
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
What last step? The only way this could happen is if you messed up a manual format or partitioning command. Only fix at this point is an RMA unfortunately
[OnePlus 7 & 7 Pro Cross Device Development] vettejock99:
Yes, it was a partitioning command. How confident are you that's the only recovery? If so, then I'd suggest OP add to his/her stern warning advice to back up EFS, as I suspect that like many, I have a number of TWRP backups, just not with EFS, unfortunately.

My data has started working, and wifi, BT, etc continue to do so, but the sensors are shot. I've been reading about persist packages, and I'm thinking that might help.

EDIT: LOL, I just noticed you have about 4k posts. Guess you're probably pretty comfortable that I'm effed. That sucks. I was reading about others who corrupted their EFS and it sounded like it was recoverable, if painful.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Efs may not even be enough. Maybe you could backup all sda partitions with dd but I don't know if restoring them would work

If only issue is sensors, then that's persist partition. Mauronofrio has persist img on a different thread (just Google it and it'll show up)
[OnePlus 7 & 7 Pro Cross Device Development] vettejock99:
So late last night I tried a few more things. IIRC, I was able to flash that persist.img via "fastboot flash persist persist.img", and I have sensors working now. In fact, most everything seems to be working, from cellular calls to text messages, GPS, wifi, BT, orientation, etc. But, I'm still getting tat "dynamic partition invalid error" and no baseband shows on my bootloader screen. I'm guessing there's still some corruption in EFS? I'd understood from reading that even with persist.img one good thing was to erase the modem files and persist first, because then they will regenerate, according to this post:

https://xdaforums.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793

So, I tried this with plans to then flash persist.img again....

fastboot erase modemst1

fastboot erase modemst2

fastboot erase persist

It won't let me erase them though, as it says the critical partitions are locked. Do you think this might get rid of this message, and if so, do you know how to do it? I think I may have use dd, but I'm not sure which partitions I'll be looking to erase and how to do it that way, either.
[OnePlus 7 & 7 Pro Cross Device Development] vettejock99:
Anyone?
[OnePlus 7 & 7 Pro Cross Device Development] sekk:
is the following scenario possible?

slot A: stock OOS 10.0.5 rooted with magisk

slot B: latest kali nethunter rooted with magisk

Obs.: to install kali, I must first set up completely the OOS on the slot, so I should have latest OOS 10.0.5 with magisk on both slots, then I would flash kali.img on slot B.

But my question is, can I do that? And also, can I flash blu spark kernel? If so, how and when should I flash it?

if someone could share a more detailed step-by-step to do these stuffs, I'd appreciate your help xD
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
Deleted
[OnePlus 7 & 7 Pro Cross Device Development] billyt1:
fastboot flashing unlock_critical

Pixel 2's (some) have to do this for factory images.

So did you wipe all of sda. And did you post sgdisk screen shot after all this has happened.

---------- Post added at 06:34 AM ---------- Previous post was at 06:23 AM ----------

Flash the kernel after you went thru setting up your phone make sure it's boots and gets thru the set up.

Let us know if it's possible with kali.

I did it with the pixel 4 port.

All I can say with it all, is your better off repartitioning down to only one data partition before flashing the dualboot zip for the first time, that way the zip does all the partitioning with no hiccups. Jus my 2¢.
[OnePlus 7 & 7 Pro Cross Device Development] oscarmaldonado:
First thanks Dev. for this project Hello everyone, question, I went through all 25 pages and I did not find my answer, there was someone who had problems with the installation and endup putting the partition values manually, now to go back and repartition everything back to the way it was before installing this dual boot TWRP, do I need to msm back to stock? Thanks in advance.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
No just run the zip again and choose stock layout.
[OnePlus 7 & 7 Pro Cross Device Development] oscarmaldonado:
Sweet...thanks bud.
[OnePlus 7 & 7 Pro Cross Device Development] esi2121:
Normal flash procedure:

1) Boot into twrp

2) reboot into twrp selecting slot you do NOT want rom installed to

3) Flash rom

4) Flash this zip

5) Reboot into twrp

6) Flash everything else

-----------------------------------------

after 3)flash rom what is that mean 4) flash this zip

what is this zip???
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
This Dualboot TWRP Zip from this thread here is that.
[OnePlus 7 & 7 Pro Cross Device Development] esi2121:
i flash it and its wok fine ,but

slot a :oos slot b: treskmod

i copy my file to common data in oos and make mount.txt with All ...but when i restart and back to treskmod its didnt show any file or folder

how i can fix this???
[OnePlus 7 & 7 Pro Cross Device Development] r0fless:
Interesting! I have one question.

Is it possible to dualboot a Pie ROM from (for exemple) on Slot A and A10 ROM on Slot B? Or will firmware differences interfere?

Thanks
[OnePlus 7 & 7 Pro Cross Device Development] Slack3r:
Thanks for this! Works like a charm dual-booting between Lineage and the stock OS for Nethunter.

My apologies if this has been asked/answered before, but is there any way to update Lineage using the built-in updater without installing the Lineage recovery or would I have to re-flash this package every time?
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
Been slacking on my phone lately. Are you up to v4? Just curious on if I can do the abc layout with stable paranoid android now. Or if I should stick to the ab. Going to get it going this weekend either way.
[OnePlus 7 & 7 Pro Cross Device Development] oscarmaldonado:
My personal opinion, I did abc because of the common data partition, considering I have 256gb of storage not being used, I have about 30gb of music, important zips like TWRP, OOS magisk, Titanium backup etc.just in case I need to reinstall, . By having that extra storage(Common data) I don't have to carry my OTG usb with me at all times, so if I need to format data I don't have to reload all my music, the music player will find it automatically, I simply love it. Give it a try, you wouldn't be disappointed.

And the way I had it setup was

32gb A(OOS)

32gb B(CUSTOM ROM)

And around 160gb of common data (storage)which it does not get erased when you format data, the only way for you to erase that data is if you do it manually with TWRP.

Good luck bud.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I've been busy lately plus I lost my to do list for this when my computer almost died :/

I'll get around to v5 some point in the nearish future hopefully