yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 & 7 Pro Cross Device Development] Ohh_Trenton:
Thank you! That's what I thought. But when I select 'no', it ends the install right away and I can't select disable force encryption. And If I go back into the zip, I am still on stock layout.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
What's the installer saying? It should tell you what to do
[OnePlus 7 & 7 Pro Cross Device Development] Ohh_Trenton:
So you have the normal checking device compatibility, which says supported device obviously.

Mounted userdata is currently encrypted. This script is unable to format it.

If you want to repartition/change size/format, format data in TWRP gui, then run this zip.

Otherwise, continue

Continue?

If I select yes, I am on stock layout and I can proceed with the options. But choosing No, abruptly ends the zip with nothing said. And it reads successful at the top of TWRP, as if the flash was successful.

---------- Post added at 08:40 PM ---------- Previous post was at 08:32 PM ----------

You know, I think I got it. I thought I selected format data the first time but after re-doing everything a second time, I didn't do it that time. I believe I am where I need to be. I'll follow up if anything else. Thank you!
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Just pushed v3 zip to github - follow download link in OP - grab the zip update from there.

Ya, you need to format data first - the zip can't repartition encrypted data
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
v3 is already here! Just a bug fix release:

* Fixed partition errors users were getting - due to zip using busybox mke2fs rather than twrp copy

* Added ability to flash from data if you're not changing partition layout
[OnePlus 7 & 7 Pro Cross Device Development] LLStarks:
This is really cool.
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
I am looking forward to checking this out! Might get it going tomorrow but probably not until the weekend. Gonna love to keep my daily rom and try out new ones as well. Mainly ParanoidAndroid.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I'd hold off or try a/b only. Paranoid Android doesn't boot with the common data partition. I'm still looking into it
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
Is that still a dual boot one? I see the stock/ab/abc

So stock is how it is now, ab is dual boot without common storage, abc is with common storage?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Right. I suspect it's selinux related but I'll hopefully have it figured out by v4
[OnePlus 7 & 7 Pro Cross Device Development] cantenna:
Yikes! Was excited to try this but after having seeing a warranty replacement I'm afraid not. Looks cool though!

Is their no tool available to backup and restore this data before tinkering with this mod to avoid a warranty claim if things go really south?
[OnePlus 7 & 7 Pro Cross Device Development] kenbrownstone:
I'm gonna try later..Thanks man I never flash other ROMs cause I get tired of all the stuff, but this makes it to were I can have both when I get board, but man this stuff rattles my brain. It gets complicated ..Will do it sooner or later . Will read it a hundred times before I drive in..
[OnePlus 7 & 7 Pro Cross Device Development] cantenna:
---------- Post added at 11:34 AM ---------- Previous post was at 11:30 AM ----------

[/COLOR]

Can you guys clarify why this issue came up? Was this an 'undo/revert mod' gone wrong?

Is their no tool currently that can back up and restore all partitions that would have mitigated this issue?

I though msm tool made it so this phone was unbrickable.
[OnePlus 7 & 7 Pro Cross Device Development] raikkoni27:
can someone please make a video of the whole procedure?

i'm planning of keeping OOS on slot A and havoc on slot B, i'm confused if I select slot A and flash OOS, do I need to flash this twrp post that?
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
I bricked the phone when I tried to redo the original partitions I am now typing on the warranty phone arguing with myself if I am going to give this another shot. The dual boot is a excellent feature but I do not think I can revert without another warranty claim due to my lack of knowledge on the phones partitions and how to set them up
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
You can restore the partitions with msmtool, but there's some device specific data in some partitions on sda that can't be replaced
[OnePlus 7 & 7 Pro Cross Device Development] law16:
Planning on giving this a this a try sometime this week to run OOS stable/"custom ROM"

I just want to clarify... shouldn't MSM tool be able to revert phone back to stock in worse case scenario?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Worst case scenario - sda is completely nuked. That can only happen from manual commands, not from the zip. Read my post just above this
[OnePlus 7 & 7 Pro Cross Device Development] raikkoni27:
i encountered the same problem when i tried to revert by flashing this recovery image from the sdcard, however, if you copy it to sdcard then use recovery's file manager to move it to a different location, say, /tmp, if you flash the recovery from the /tmp, then the recovery lets you change the layout to stock
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
No I repartitioned it wrong and for some reason I could not get any msm tool to work and flashing a Rom in fastboot failed also. I am certain that my problem happened only because I do not know fully how to revert and did not ask questions while trying to do so.. on that thought it is too bad there is nothing flashable to revert to original partitions layout. ;)
[OnePlus 7 & 7 Pro Cross Device Development] cantenna:
Yea... I'm usually up for this sort of stuff but this seems like a non-starter for me... this project takes you to a new level where unbrick tools simply do not work! And on the One Plus too... my experience with this device has been MSM tool is essentially always required before jumping to a new rom base, the perma-brick risk here is too great.

Only a couple of months ago I bricked my S8+ completely using "Project Treble" tool... didn't do anything wrong at all, just unlucky with using the auto revert tool and apparently it garaged my fstab tool... was in uncharted territory at that point as Odin would not work by conventional methods... after many, many hours I was able to revive it; required a specific Odin version, specific FW from Sam Mobile and the .pit file .... and even then, multiple try's before it would take... there was something also I had to do but I forget now because even after and Odin re-flash I was unable to factory reset the device from recovery.... Oh maybe that was it, had to choose factory reset from Odin too... and I needed to restore my EFS partition as well which wasn't easy... But I reckon Odin and Samsung devices are a lot more brick proof than One Plus devices

would love to see this develop to a point where its less risky, can better backup/restore tools be developed for this project? Which parition was lost, what data does it contain?
[OnePlus 7 & 7 Pro Cross Device Development] harpin14789:
Hi Zach, great mod. I want to try this out but I have a couple questions before I do so.

I'm currently unencrypted (thanks to your no-verity zip) and running custom roms. I'm unencrypted so that I don't have to wipe internal if I want to go back to OOS or vise versa.

With this mod, do I need to unencrypted ( by flashing your no verity zip each time I flash a rom) if I want to have custom on slot a and OOS on slot b? This is the only part that confuses me.

Thanks for the mod!
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
No, you can be encrypted but note the limitation on the OP. I'd recommend staying unencrypted for now unless you are careful to not set a passcode on the second slot you set up
[OnePlus 7 & 7 Pro Cross Device Development] theoneslr:
their are some confusing parts about this mod and how to set it up. If you can or someone that actually got it to work maybe come up with a little video tutorial explaining the steps and walking it through the process?

Thanks, For all the hard work.
[OnePlus 7 & 7 Pro Cross Device Development] harpin14789:
So that means I need to flash no-verity-encrypt zip after rom flash to stay unencrypted?
[OnePlus 7 & 7 Pro Cross Device Development] GeekMcLeod:
Going too figure out installing it this weekend. I could make a video for it but I don't really know how. Screen and voice recorder? Is there an app for that?
[OnePlus 7 & 7 Pro Cross Device Development] harpin14789:
You can't really record screen in twrp, you have to use another phone or camera to record your phone. You can take screenshots in twrp but they are like to get wiped since they are in internal storage.
[OnePlus 7 & 7 Pro Cross Device Development] vinayak.s19:
Havoc OS doesn't seem to be working on a/b/c but works on a/b.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Havoc works for me on a/b/c
[OnePlus 7 & 7 Pro Cross Device Development] vinayak.s19:
What procedure did you follow? And I'm using guacamoleb.

Trying to boot havoc and oos
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
For initial setup:

Flash oos, then flash this zip (choose new layout/abc - it'll format data)

Reboot to twrp (this switches slot)

Flash oos, then this zip again

Reboot to twrp (switches slot again)

Flash havoc, flash this zip
[OnePlus 7 & 7 Pro Cross Device Development] vinayak.s19:
Tried the same procedure but I get bootloop on havoc.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Read through the can't boot section in the OP, it's possible that havoc is slightly different on your device then mine selinux-wise

Grabbing a logcat via adb and attaching that while stuck at boot would be helpful
[OnePlus 7 & 7 Pro Cross Device Development] ygecesefa:
is there any way to back up all sda with msm tool before messing up? To prevent perma brick
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Not with msmtool. I backed up all partitions other than userdata with dd but I have absolutely no idea if I can restore them msmtool followed by that and I'm not about to risk a brick to test it :)
[OnePlus 7 & 7 Pro Cross Device Development] ygecesefa:
yes dd may work easly but restoring a different issue. But there must be back up and restore section on msm tool as i can remember.Other way too risky. Because "No body succedes on the firs try". :D

Or we need a smart script for whole procces.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
If the zip didn't give an error, you can always return to stock by flashing it again and choosing stock layout
[OnePlus 7 & 7 Pro Cross Device Development] harpin14789:
What does dd mean?
[OnePlus 7 & 7 Pro Cross Device Development] king-totti85:
very interesting project, though I have some questions:

1. can I assume that choosing to keep the stock layout is associated with the lowest risk of bricking the device?

2. if I choose to keep stock layout, will I be able to dual boot? and how is that going to happen since I will be having only 1 data partition?.

3. if I choose to keep stock layout, do I need to format data?

4. what about apps data in each case (stock, a/b and abc), will they be the same apps with the same data in each rom, or each rom will be using its own apps and app data?

Thank you for your work and sorry to bother you with too many noob questions ?
[OnePlus 7 & 7 Pro Cross Device Development] matze19999:
just search on google, its a linux command
[OnePlus 7 & 7 Pro Cross Device Development] :
The zip detects my device as a 128gb one, but my device is actually 256gb. What do I do?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Can you take a recovery log after flashing and send it? I would select no at the "are you sure" part so it doesn't actually install anything
[OnePlus 7 & 7 Pro Cross Device Development] :
Yes, here you go:
[OnePlus 7 & 7 Pro Cross Device Development] Dark Fear:
hello there . i have 128 version and wasnt able to dual boot.. here is what i've done:

rebooted to recovery. flashed dual boot recovery . installation went well but it didnt wipe anything or made new a/b/c slots .. its still a/b and just one 108gb starage ..
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I mean save the log. So select no at that prompt, then go to advanced - copy log. Upload the resulting recovery.log file
[OnePlus 7 & 7 Pro Cross Device Development] :
Here you go
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Ok, that makes sense. Because you're encrypted, userdata is mounted under a different name and so the installer wasn't detecting it. Either decrypt by formatting userdata first or just stay stock
[OnePlus 7 & 7 Pro Cross Device Development] :
Is it possible to decrypt and keep my banking app data?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
No. You will wipe all of userdata including internal storage/sdcard
[OnePlus 7 & 7 Pro Cross Device Development] :
I see.. So how would I do this? Format data then flash?
[OnePlus 7 & 7 Pro Cross Device Development] Dark Fear:
can you please help me too? i've flashed the recovery successfully but storage doesnt get divided and its like i've just flashed normal twrp 79
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
I am having a problem with the script seeing my 256 as a 128 on v3
[OnePlus 7 & 7 Pro Cross Device Development] arvindgr:
He answered it in previous Page..
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Also found a bug related to it too. It'll be fixed in the best release (no eta yet)
[OnePlus 7 & 7 Pro Cross Device Development] Dark Fear:
i have managed to repartitoin to a/b/c and currently running stock on slot A.

but i'm having difficulties for 2nd rom.. some roms like linage os and crdroid was fine and i successfuly dual booted them with stock.

but some roms like bliss, mokee, treskmod i get bootloop .. is there anything i can do to run these?

here's what i'm doing for having stock on A and custom on B:

boot to twrp (slot A) reboot to slot B , format data. reboot back to slot A , flash custom rom , reboot back to slot b , reboot system
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
v4 is finally here! There's actually quite the extensive changelog:

* Add mount all option for datacommon mounts.txt

* Redid how commondata was mounted - fixed issues with lots of roms like AOSPA

* Magisk made optional for commondata - it is still needed for some roms though (like oos)

* Made other vars slot selectable

* Storage size detection fix

* Misc fixes/improvements

* Updated to magisk 20.4

Download is in github releases like always :D

Edit: Reuploaded v4 - needed to make partition size detection more robust
[OnePlus 7 & 7 Pro Cross Device Development] gnabtib8:
What are size of the stock partitions when enabling a/b/c for 128/256? Can you modify the sizes of the partitions?
[OnePlus 7 & 7 Pro Cross Device Development] iamMG:
This project sounds great. However I have a question. Can I use this TWRP as a replacement for mauronofrio's version even if I don't intend to use the repartition abilties which it provides (not right now, maybe later)?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Yup, just choose keep current layout and you'll stay stock
[OnePlus 7 & 7 Pro Cross Device Development] saleemz:
I've successfully boot both OOS and EvolutionX with v4, in v3 i was having bootloop with AOSP rom's, in v4 i install the rom without flashing magisk and i install it after first boot.

Thank you very much for this!
[OnePlus 7 & 7 Pro Cross Device Development] SUPNYUS:
Hello man, congrats ! Could you tell me all the steps you took please ? I'm kinda lost there :/
[OnePlus 7 & 7 Pro Cross Device Development] saleemz:
Hello man, here's what I do:

1- I have flashed the dualboot twrp and repartition to a/b/c a:32Gb, b:32Gb and c the rest, then i reboot to recovery.

2- I copy all the roms and other stuff i need to flash to the common data partition.

3- change to slot a and reboot to recovery from there flash OOS then twrp dualboot :disable encryption and flash magisk, now oos is in slot b.

4- change to slot b and reboot to recovery, flash EvolutionX then flash dualboot twrp: disable encryption and didn't flash magisk.(i flashed it after successfully boot the rom) now evolution X is in slot a.

This is what i basically do, the hard part is to successfully repartition to abc, and the rest steps is easily just pay attention in which slot you are and always flash rom's in the opposite slot as mentioned in the OP.
[OnePlus 7 & 7 Pro Cross Device Development] pro_granade:
do all zips flash to the other slot? or just ones that modify the system partition?
[OnePlus 7 & 7 Pro Cross Device Development] raikkoni27:
i have a question;

if we are using whatsapp on both slots' roms, will the chats be saved on common data?

suppose i use whatsapp from rom on partition 1 today, if i use whatsapp from another partition rom tomorrow, will i get chats there from today?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
All zips flash to the same slot EXCEPT ROMS (they flash to opposite slot).

I don't use it myself but some users report that WhatsApp data is saved to /data/data which is a no. I'm planning on reworking how commondata works to address this in a future release but it'll be a while (I have a lot going on now)
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
For the time being you might be able to use storage isolation (former storage redirect) to archive this.

I haven't tried dualboot myself yet, but storage isolation let's you export the files to a location of your choice.
[OnePlus 7 & 7 Pro Cross Device Development] vinayak.s19:
Using the selinux patch I could successfully boot havoc os but I have another question. Is it possible to share specific app data over the two roms like my IM apps using the mount.txt or any other way.
[OnePlus 7 & 7 Pro Cross Device Development] YousifG7:
Edit (Deleted)
[OnePlus 7 & 7 Pro Cross Device Development] SUPNYUS:
I actually am enjoying a lot my dualboot. Thank you so much for this mod, really.
[OnePlus 7 & 7 Pro Cross Device Development] king-totti85:
can you explain the steps please?
[OnePlus 7 & 7 Pro Cross Device Development] SirSoviet:
/sdcard/CommonData does not show up on the latest official LineageOS build (0401). However, it does show up in OOS and other roms.

EDIT: Just checked the LineageOS downloads page for OnePlus 7 Pro and saw that the build was pulled. Can someone please confirm whether the above is the case on other builds as well?

EDIT 2: CommonData doesn't show up in AOSPA-Extended either. Strange.

Could this be related to the limitation that causes the inactive slot's password to be incorrect when a password is set on the active slot? I haven't gotten the workaround that uses a TWRP backup to work so far, and I resorted to deleting locksettings.db every time I flashed a rom on the opposite slot.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
I have a Oneplus 7 since yesterday and I installed this Dualboot TWRP. Really great thing.

Installed Derpfest on Slot A and AOSiP on Slot B because I want to test both of them to see which ones suites me better.

I have disabled the encryption on both slots and set a password only on the ROM on one slot (the other slot/ROM has no password set).

But now I can not unlock the ROM with my PIN on slot a so I guess I messed something up here.

I thought it should work if one slot has a PIN set but not the other??

Or can/should I leave both slots without a PIN set?

Thanks!
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
No, I don't do so by step tutorials. It's not hard to figure out. I believe it's better to learn the process then follow steps, unless there could be irreversible changes.
[OnePlus 7 & 7 Pro Cross Device Development] theoneslr:
I think a step by step would be useful to a newbie that wanted to try this out. I also think a step by step would be useful for a veteran as well. I have been flashing for years and always follow the directions. I have only bricked two phones in my life. The directions for this is not really laid out all that well. One small mishap of the brief directions and you could get a perm-brick and that's why detailed directions are so important!
[OnePlus 7 & 7 Pro Cross Device Development] pro_granade:
Correct me if I'm wrong, this can't brick you. You always can use MSMDownloadTool to go back to stock if you need.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes or if you want to switch back to stock later, just flash the installer again and choose stock layout. Have done that to go back to stock and it worked without any issues.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
First of all, 'this' as in dualboot can brick your device to the point where you won't be able to fully restored everything even with msm tool. BUT only if you start doing things manually, not while using the provided zip. But again there can be situations where the zip fails and you have to sort out things manually. (That is a good time to follow a step by step guide.)

After reading the whole thread this is my conclusion at least.

Second, the step by step asked for was about storage isolation, not dualboot. For dualboot you can find steps in this thread.

Storage isolation does not make any unrecoverable changes. Therefore I won't give steps because I think a try and learn approach is better.
[OnePlus 7 & 7 Pro Cross Device Development] David_#27:
Is it possible to work for the Redmi K20 Pro in the future or it can be achieved even now?
[OnePlus 7 & 7 Pro Cross Device Development] tmushtare:
So you flash this dualboot TWRP as the main recovery? Not the one in this thread RECOVERY][3.3.1-79][Unified]Official/Unofficial TWRP for OnePlus 7/7 pro/5G (Stable)?
[OnePlus 7 & 7 Pro Cross Device Development] FCBThunder:
Hi,

Thanks for this awesome work. I have flashed this mod but did not make it a/b/c. On slot B I have OxygenOS installed, so in TWRP I selected slot B and flashed both Lineage OS and RevolutionX custom ROMs (but they keep bootlooping on the splash screen). Is there anyway I can fix this?

Or can someone link me to a flashable OxygenOS zip so I can try this mod making a/b/c partitions? The main reason why I haven't done this yet is because I'd like to keep my OxygenOS partition without losing data and configs.

Thanks
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
It's not possible to use 2 different ROMS with the same data partition. That is the whole purpose of this tool. You can't have dualboot on stock layout.
[OnePlus 7 & 7 Pro Cross Device Development] FCBThunder:
Thanks, figures it out already. Now Running OxygenOS and EvolutionX (formatted as a/b/c). At first glance I don't see commondata though on both Roms.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
From the 'read me' on GitHub: "The common data partition is mounted to /sdcard/CommonData".
[OnePlus 7 & 7 Pro Cross Device Development] tmushtare:
---------- Post added at 02:50 PM ---------- Previous post was at 02:41 PM ----------

[/COLOR]

In the steps above you only used the dualboot TWRP? No other one? Would you mind making a more detailed step by step guide?

Including how to flash dualboot TWRP? This is a one shot method for me since I have no back up. And my goal is to have Stock OS rooted on one partition & The [ROM] [Official] Kali NetHunter for the OnePlus 7 & OnePlus 7 Pro on the other partition!

---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------

Did you only use the TWRP that is found in this thread?
[OnePlus 7 & 7 Pro Cross Device Development] saleemz:
As mentioned in the OP: You MUST be booted into TWRP already when flashing this zip.

after flashing the dualboot twrp there's no need to flash any twrp other than this, just repartition to a/b/c layout and follow the steps as per my last post and you should be ok.
[OnePlus 7 & 7 Pro Cross Device Development] tmushtare:
Perfect thanks so much for your reply, and help! I will let you know if i achieve a successful dual boot with stock os in partition B & another on A.

Is there any way to tell which partition your current OS is installed on??