yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 & 7 Pro Cross Device Development] Imminent-darkness:
I was on official oos 9.5.13 on slot A and official oos 10.0.2 on slot B. Slot B locked Slot A out of the network. I flashed official oos 10.0.2 to slot A and it fixed the issue.

---------- Post added at 01:03 AM ---------- Previous post was at 12:18 AM ----------

I experimented a little and found that Nethunter, as a ROM Overlay, flashes to active (same) slot. I attempted to flash it from opposite and ended up flashing it to the wrong slot so I had a little mess to clean up :silly:

I did want to make sure that I share this discovery to the thread for the benefit of anyone intending to attempt the same setup...

NETHUNTER FLASHES TO ACTIVE SLOT ;)
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Sounds like omniROM
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
Soooooo pa quartz 2 boots and runs fine with abc, just can't get common to mount unless I use selinux changer and set permissive but then I get freezes and reboots. Anyone have any ideas.

I've reflashed dual boot, used kpatch, tried a couple kernels (Kiri and smurf). Usually I can get it working but it's just being a pita
[OnePlus 7 & 7 Pro Cross Device Development] langeveld024:
So if i flash this recovery I can disable force encryption via a switch in recovery and then safely flash ROMs and restore nandroid without is messing up my encryption and lose everything? Is it as simple as that?
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
Yup it is indeed a simple unified installer.
[OnePlus 7 & 7 Pro Cross Device Development] langeveld024:
So u can leave encryption on, then only when I want to update or flash rom u can disable encryption on the fly without losing data and enable encryption afterwards? Is that what disabling encryption is for?

And you do not lose data?
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
Encryption means that your entire data partition gets encrypted with a key which can be decrypted only by the rom which setup encryption.

So if you disable encryption,you have to do it before booting the rom, because they encrypt data normally at first boot.

Flashing the zip after first boot won't do anything,but if you format data(the only way to remove encryption) then you can setup the rom again, unencrypted.

You can easily switch roms just by wiping data(not formatting everything including your /sdcard,which is the usual procedure) if you are unencrypted.
[OnePlus 7 & 7 Pro Cross Device Development] langeveld024:
Thanks, so when I'm encrypted I can't switch/install ROMs without losing everything on /sdcard?

I lost all my data once after a mistake while updating OOS so that's why I'm asking.

I'm used to having an external SD card in my previous phones, never lost data on those because twrp doesn't touch extSD.

One more question: when TWRP shows 0mb on /sdcard I lost the encryption, right? Is it possible to restore the encryption by restoring a nandroid? (Assuming you have the nandroid on a OTG drive)

Regards,
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
Yes you can't switch roms without wiping everything if you are encrypted.

Twrp showing 0mb after format data?

Then it's okay..you just have to reboot the recovery.

I haven't tried restoring nandroid into unencrypted data..see for yourself..I think after reboot the rom will start encryption before loading homescreen.
[OnePlus 7 & 7 Pro Cross Device Development] Nevil Sebastian:
Congratulations Dev :good: :) , It's a real tough work to say.
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
So, I'd I understand this correctly, if for some change the partitions mess up, I can't just use msmtool?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
If you dont do anything manually with the partitions and just use the this Dualboot ZIP it should stop when something goes wrong.

I guess it depends on what exactly is messed up with the partitions if MSMtool will work or not.

I could successful restore my phone to OOS stock with MSMtool when I had messed up something while messing around with this ZIP and had done something wrong and wanted to go back to Stock and could not boot up the phone (it just eneded up in the Qualcomm crashdump mode). From that I could successfull recover everything to Stock OOS with the MSMtool.

---------- Post added at 06:12 PM ---------- Previous post was at 06:10 PM ----------

Hi! This works great. I am using this now to flash TWRP after updating my ROM or anything and need to re-flash TWRP. Great work that you just can set everything before and just flash it.
[OnePlus 7 & 7 Pro Cross Device Development] Win1droid1:
for example if I installed oos and crdroid then I wanted to delete crdroid and install havoc . what is the steps that I should do ? ( without affecting oos)
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
-Boot into TWRP

-Select the slot where you have OOS installed

-Flash Havoc

-Flash this Dualboot TWRP

-Reboot to recovery

-Flash everything else you need to flash after Havoc flash

-Format Data

-Reboot to system
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Never got havoc to work with dualboot myself
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
OK. I havent tried Dualboot with Havoc actually. I am running it now with EvolutionX on one Slot and POSP on the other.
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Cool [emoji41]
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
I got it working,oos and havoc

You just have to reflash the dualboot zip after first boot to havoc to mount common storage.

rom with issues so far is omni and it's variants and some others which i don't remember now

Crdroid havoc oos evox resurrection have no issues for sure.
[OnePlus 7 & 7 Pro Cross Device Development] Win1droid1:
when I set pattern+FP in oos and rom installed in second slot then reboot from one to another it gives me wrong pattern and I can't enter the rom any more ?

any one faced the same problem
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Delete the lockscreen.db file in the ROM that's giving you the wrong pattern error message and you'll be good to go.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Did you read the OP?

A link is given under the section limitations. With which it says "MAKE SURE YOU READ THIS".
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Quick PSA. My OP7Pro is once again through the warranty process so I won't be able to update this for some time. You could try modifying the installer by replacing the cpio with the new one but you'd be on your own
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Ohhh ok.

Great.

I did that now and it seems to work. I took the ramdisk-recovery.cpio file from the latest TWRP-3.4.0-0 and replaced that file in the Dualboot.zip with that one.

Reflashed my ROM and the Dualboot TWRP and I see that I have TWRP-3.4.0.-0 installed now.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Dualboot TWRP with updated TWRP-3.4.0-0

I have uploaded the Dualboot TWRP with updated TWRP-3.4.0-0 here.
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Confirmed this worked. Flashed it on both slots and I could access both my ROMs with all my magisk modules. :good:
[OnePlus 7 & 7 Pro Cross Device Development] a63548:
This is awesome, and truly exceptional work. Was wondering however if there might be a way to say make a version where a certain percentage, say on the 256GB version, such as 56-60GB be dedicated to the normal A/B flashing method, with then a C partition using the remainder of the space that can keep documents, ROMs, music, videos, backups and would not get flashed using the normal Format Data option. This way going from ROM to ROM when a Format Data is needed, that extra partition would always remain, and stay untouched. Obviously this wouldn't be a Dual Boot method, but for constant flashers it could be a godsend rather than having to copy over everything again and again after performing a Format Data. Sort of like having a C:\ in Windows be small, with other partitions keeping documents, so in the need to re-install Windows doesn't wipe out all the documents, besides the C:\

Could something like this even be possible? Would absolutely love such an option. :)
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
When you set it up with A/B/C Userdata you have the norrnal A and B partitions for the ROMs with either 16GB or 32GB each and the rest of the available space get assigned to the common partition C which you can use to put all the common files like Documents, Pictures, Music etc.

That partition will stay as it is when you switch a ROM and need to Format Data since you do the Formst on the A or B Partiton of the ROM and not touch the Common partition though.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
[MENTION=5839251]Ae3NerdGod[/MENTION] I have updated the Dualboot fast mod you made with the latest TWRP-3.4.0.-0 and latest Magisk Canary v20416. Download here.
[OnePlus 7 & 7 Pro Cross Device Development] Bradl79:
So do they have a separate data partitions?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes that is the Dualboot TWRP which you can use for A/B/C Data partitioning.

So the same as in the OP just with Updated TWRP to the latest Version.
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
So, has anyone had issues using msm tool using the a/b/c layout?
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Not me. I've used it multiple times in the beginning because I messed a few times trying to get dualboot.
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
That's all I needed to know ?
[OnePlus 7 & 7 Pro Cross Device Development] ygecesefa:
Where to delete lockscreen.db?I got dead end.Because you cannot access data because it is encrypted.Also I got error when format data it says you cannot it is encrypted!I fixed it by repartitioning.

By the way we got commondata as a drive or folder?

System Filemanagers cannot see it.Only I can access it by a root browser on commondata folder.I just want keep my slot a unrooted.But you need root to acces commonfolder.It cant be mounted like as an usb drive?So we can use it without root.
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
Any chance this could be modded from current state to work in the op8?
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
The original dev has an OP7P. Unless he plans to upgrade to OP8 and mod this, I'm going to say the answer is no. Or maybe another dev who has an OP8 will create one for it? :confused:
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
only brought it up because the cpio file was the only thing needed to update the recovery to the newest version. Don't know if the same thing could be done just to change it to work for the 8, and of course maybe the actual recovery image and such but...
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
I think somewhere in the beginning of this thread the OP said in theory it could be adapted to work on other devices. But somebody who knows the one and it's off how this works and with the device to test needs to do it.
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
So, flashed this. Changed to A/b/c. OOS didn't boot, flashed Blissrom, and flashed this again. Even tho I see the new common data and stiff in twrp, I have to choose all options evrrytime I flash a ROM?
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Yes
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
But you can use the other modded Dualboot TWRP file done by Ae3NerdBot which can be used to set all the options directly in the ZIP filename. Then you can just flash that with the needed options and dont have to choose all the options manually.

I am using that and it is quite handy. Have also updated that one with the latest TWRP.
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Wooow! Never heard of this before. I'll have to look for it. I've been running dualboot with the same options for a few months now and I don't see myself changing any of the options so if there's a TWRP that will maintain those options, awesome!
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes that is great. So my file is called like this:

TWRP-DualBoot-3.4.0-0-fast-fec.ab-su.aB.zip

That means it leaves both slots unencrypted and Magisk is installed only on slot B.

So you write fec for force encryption followed by the slots a and b and su for Magisk followed by the slots ab.

If you write the slots in small letters then it will not be used for that slot and if in big letters like su.aB Magisk will be installed in Slot B.

With that flashing you just get an overview with all the settings which it will do and you just have to confirm it once.

Even that confirm can be switched off by adding: confirm.y in the filename.

Here the updated readme done by Ae3NerdGod where you can read all the options to add to the filename down under Quickmode usage.

---------- Post added at 01:17 PM ---------- Previous post was at 12:33 PM ----------

The lockscreen.db file is located here /data/system . But you can only do it when you are unencrypted!

These are the files you need to remove if existing there in regards of which method, lockscreen, pattern, or password you have set:

password.key

pattern.key

locksettings.db

locksettings.db-shm

locksettings.db-wal
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
---------- Post added at 01:17 PM ---------- Previous post was at 12:33 PM ----------

In short, can I rename your dualboot zip with the appropriate upper/lower case and it will work? Or I have to generate it from your provided github URL?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes you can take the one I posted in the link from my last post. That is the modded one for that with the latest TWRP.

So you can take that one and just rename it to your preferred needs.

The other one I posted and updated is the original one from the OP just with updated TWRP but without the mod for the upper/lowercase settings to flash.
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
Having issues finding datacommon in android. Like I can find it easily in TWRP but in android, I don't only see it on sdcard with none if the files/folders from the actual partition
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
Within the ROM yiu can't see the CommonData, flash the dualboot zip dude
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
I have flashed the dualboot zip. Slot A has RR slot b has Havoc. A/b/c setup. So how am I supposed to move music and other files to the c(common data) partition?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
When you dont see the common data partition from your ROM then try to reflash the dualboot ZIP in TWRP from the data partition of the ROM not from Common Data. That usually solves that issue.
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
I know this sounds stupid, because this doesn't mess with nor interfere with the radio/modem at all, but ever since I did this, my cell speeds have been horrible. I mean, I would get like 75Mb-175Mb download and now I get 25-60 download

Put my Sim in my backup 7pro running exact same ROM/kernel setup except the dialboot and speeds are back to normal
[OnePlus 7 & 7 Pro Cross Device Development] billyt1:
Cant say I have this issue. Maybe try dualbooting the extra and see if does the same. And usually when you flash custom Kernel theres precautions, I use Kirisakura-Kernel and this is what he has stated.

( WLAN Driver

- use CAF wlan driver and compile it inline, the only way to ensure working wlan with this kernel

- the kernel cannot even force load OP prebuild WLAN module as the kernel base is way to far from stock!

- do no longer rely on the pre compiled OP wlan driver module, where OP doesn´t bother to release the source for

- completely removed qcom_rx wakelock (the amount of wakeups caused by this wakelock over a single night is more than 3 times as high as on my pixel 3 -> this improved overnight deep sleep by a considerable margin)

- removed debugging from wlan driver

- removed logging from wlan driver)

That being said if you ever flash a rom an wifi and sim aint working then flashing a custom kernal can sometimes get it back working. But not by OP source.

If I was you . Id download a kernal manager like FKM and check your TCP congestion algorithm
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
Any way we can get the new orange fox recovery built into this?
[OnePlus 7 & 7 Pro Cross Device Development] ygecesefa:
Any chance to make a coop recovery with orangefox? It looks amazing.It is an aroma skinned twrp with extra features. Imagine add your features to his. You can use for partitioning proccesses with an easy touchable interface.That could be supercool project.
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
The question was already asked and we're waiting for a reply... No need to re-ask the same question
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Just saw that OrangeFox recovery is available for the Oneplus 7 now.

So lets see if we get dualboot with OrangeFox recovery perhaps sometime in the future.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Did you read the last few posts?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes of course.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
[MENTION=5839251]Ae3NerdGod[/MENTION] I have a question regarding the FAILSAFE option for the fast-dualboot file you made. I dont really get how this is ment to be used exactly. Should I create a seperate file to use for 'failsafe' or just add that to the dualboot TWRP options file I use to flash normally?

I get exactly that issue when having the POSP ROM on slot B and flash the dualboot TWRP from active slot A then it hangs at "Flashing inactive slot B..."

Then I usually connect my phone to the Computer and reboot it to fastboot and set the active slot to A again and can then boot to TWRP on Slot A again and re-flash the Dualboot.zip that will fix this issue but of course I need a Computer for this so therefor I am wondering how this is exactly working with the 'failsafe' option to the dualboot file?

Thanks a lot.

Thanks!

EDIT: OK got it I just have test it and it worked as expected when just adding 'failsafe' to the ZIP-name and just use that file when flashing dualboot-TWRP. Then I could just reboot to the TWRP recovery from the active slot and re-flash TWRP and that worked then as expected!
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
Hmmm. No communication from OP in a long while......the warranty process must take forever
[OnePlus 7 & 7 Pro Cross Device Development] AndroidRooterKev:
The warranty never mentioned dualboot....
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
Just so you're aware, they cover any and all software modifications. They said so themselves
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
Alright.. The warranty phone is on its way. Thank you for the help.

I was just thinking does I matter of it was opennbeta 10 when it comes to the msmtool file?
[OnePlus 7 & 7 Pro Cross Device Development] f41lbl0g:
Hey [MENTION=6037748]Zackptg5[/MENTION] I've switched to the a/b/c partition. But I am facing an issue where my password is "incorrect" after installing a rom on the other slot and setting it up. For example if I set a password on rom A, then boot into rom B and set up a password on there, and switch back to rom A, the password on rom A does not work anymore. This renders me being unable to boot into the rom as password is required on first boot. Only way to get it past the lockscreen is wiping data. Maybe the roms are overwriting password info or encryption somehow. Plus with decrypted, I cant get through the setup without setting a password, which means that the opposite rom would be locked.

Info: Decrypted, dmverity disabled, a/b/c partition, op7 pro 256gb

I managed to get into my locked os by deleting a couple files through twrp.

/data/system/gatekeeper.password.key, gatekeeper.pattern.key, locksettings.db

/data/system/users/0/settings_fingerprint.xml

After doing this, I set a fingerprint + pin again and now both roms work. Rom A has a password+fingerprint and rom B has a pin+fingerprint. My guess is that password+fingerprint on both messed it up, but not sure (I had set same the password for both).
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
It shouldn't, it should completely replace everything

Not sure what the problem was there. I have metadata partition repartitioned as a/b too and fstabs updated for that so encryption should be completely separate/working on both slots. Glad to hear you got it worked out.

For myself, I have oos stable encrypted on one slot, and random unencrypted roms on the other
[OnePlus 7 & 7 Pro Cross Device Development] Kris Chen:
I managed 2-system in my OP7Pro by this TWRP mod successfully(slot a=OOS10 10.3.1; slot b=Pixelexperienceplus).

Just one recommendation here: Could you help do another one with F2FS file system or add another option with EXT4 or F2FS in your original zip file ?

Another doubt about your description about how to flash OTA even new ROM in new a/b/c:

1. flashing OTA or ROM to the slot you don't want to flash in;

2.flashing zip file ==> Is it your zip file or original twrp installer zip file ?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I'll look into it when I get the chance.

1. Right. Rom flashes to opposite slot. Keep that in mind and you'll be fine

2. My twrp zip. You won't need/don't want to use the original anymore if you're not on stock layout (mine has stock option too so you could just use it for that)
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
So for any users of a/b/c layout

Datacommon folders are effectively mounted twice - once to internal storage/Common Data and once over top of internal storage directly (setup this way so files in datacommon root are accessible). So files like music will show up twice

Either have your media player only search a specific folder or if that's not an option, use riru + storage isolation
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Looked back through my stuff and I tested that out while initially making it. I decided to leave it all ext4 and let the user format data to f2fs if they choose with twrp gui - it was the way that would have the least issues since the kernel needs to have f2fs support to work with this.
[OnePlus 7 & 7 Pro Cross Device Development] Kris Chen:
I'm really appreciated for your patient to explain every questions I asked, [MENTION=6037748]Zackptg5[/MENTION].

I'm thinking whether any app to switch 2-ROM smoothly(i.e. no need to reboot to TWRP and switch slot)
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
If you find one let me know, I don't know of any
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Maybe kind like this,,,https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
No, multiboot worked by using a custom bootloader, that was way before a/b slot was a thing so that wouldn't work unfortunately