yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Yes, stock a/b has 2 system (and a few others) partitions, but only one data partition.

So updates can be flashed to the not used partition while the system is running.

So if you keep sick partition and try to dual boot, when you make any changes it effect your single data partition which both ROMs are using.

A password or encryption is stored different between ROMs and will for sure cause problems as you have experienced.

This is why you should understand the basic principles of a/b devices and what they do (as I said before read up on the topic)

So again STOCK PARTITIONING DOES NOT ALLOW DUAL BOOTING.

Which also has been mentioned in this thread before.

So read, read, read.
[OnePlus 7 & 7 Pro Cross Device Development] ele95:
yes i always flash oos with pa as a base
[OnePlus 7 & 7 Pro Cross Device Development] aiamuzz:
Hi,

Hmmmm ... Good to see a dual boot option back after every other dual boot solution died after android 9(pie) was launched ... Hope this thread isn't one of those that support multi boot on devices running Android, versions before version 9 ...

So the crucial question to pop ...

Is Oneplus 3T one such device with an A/B partition ? Can 3T users hope for such dual/multi boot option for their device in the near future ?
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
This is created for the OnePlus 7 series.

The developer said it should be possible on other devices but somebody with the right knowledge needs to adjust it for their devices.

I don't know if anybody is trying to bring it to other devices.
[OnePlus 7 & 7 Pro Cross Device Development] aiamuzz:
ok [MENTION=5993745]JudgeDread11[/MENTION] ... i have a Oneplus 3T ... hopefully somebody is able to get this dualboot option to my device ... I have a 128GB device ... ample storage space ...

[MENTION=6037748]Zackptg5[/MENTION] ... any minimum requirements of the device to qualify for this modd ?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Has the Oneplus 3t A/B Partion layout? Which TWRP Version are you running on it?
[OnePlus 7 & 7 Pro Cross Device Development] aiamuzz:
[MENTION=9574498]Wishmasterflo[/MENTION] ... how do you check If Oneplus 3T has A/B Partition Layout ? any command on the terminal app or on adb shell that will give me this info ?

I am running multiROM TWRP 3.1.1-2 ... i had installed it when i newly bought this phone hoping multirom would work ... then i was already on Android 9(Pie) so turns out MultiROM, EFIDroid and other multiboot solutions that existed no longer worked and all those projects had ended support ... Glad to see this subject(dualboot) has revived ... at least on Oneplus 7 !!!
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

A Google search with key words "OnePlus 3t” and a/b partitioning or seemless updates would probably answer your question as well.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
It seems that the Oneplus 3 and Oneplus 3t does not have A/B Partitions so in that case it is not possible to get that working for dualboot. It least what I can see.
[OnePlus 7 & 7 Pro Cross Device Development] aiamuzz:
Googling resulted in this ... :mad: ... :eek: ... :fingers-crossed: ... :rolleyes:

https://www.indiatoday.in/technolog...-to-partition-requirements-1102429-2017-12-07

Found a thread on the Oneplus community forum ... and posted the following ... not sure if they'll even read ... fingers crossed ...

https://forums.oneplus.com/threads/join-our-oneplus-5t-ama-now.686679/page-52#post-21958121
[OnePlus 7 & 7 Pro Cross Device Development] ele95:
anyone flashed ob 17 with dual boot
[OnePlus 7 & 7 Pro Cross Device Development] emam damon:
Yes I did but it didn't boot up.

I did the same procedure with oos 10.3.4 and b16 and it worked just fine
[OnePlus 7 & 7 Pro Cross Device Development] ele95:
did you faced any problem with mount data / system / vendor issue , or do u know who to fix this issue
[OnePlus 7 & 7 Pro Cross Device Development] Pipodi93:
Guys, in order to return to the a/b partition schema without dual boot, what do I need to do? Do I need to follow the readme section and then flash some other ROM?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
You just reflash the dualboot TWRP zip and chose stock as layout.

Remember that will format all your data as well.
[OnePlus 7 & 7 Pro Cross Device Development] emam damon:
Sorry about delay on answer and yes I did and my phone went off for about 2 days and at the end I had to format data
[OnePlus 7 & 7 Pro Cross Device Development] HSchmotz:
Hello here. After flashing oos beta 17 flashing twrp stops at fstab. Reflashing beta 16 and twrp. Where is the problem. Beta 17 or twrp?:confused:
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
I guess there were several you had issues with OB17.

Which TWRP Version are you using?
[OnePlus 7 & 7 Pro Cross Device Development] HSchmotz:
I use dualboot v4.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
OK. You can try with this one which I updated with the new TWRP 3.4.0.0 to see if it makes some difference!
[OnePlus 7 & 7 Pro Cross Device Development] HSchmotz:
Doesn't work. Flashed OB17 and then 3.4.0. Stopped at fstab. Has to fastboot, change slot, reboot recovery, flashed OB16, flashed 3.4.0. This worked. Have OB16 on slot B and PA4 on slot A. Thanks for your help.
[OnePlus 7 & 7 Pro Cross Device Development] emam damon:
me too
[OnePlus 7 & 7 Pro Cross Device Development] emam damon:
any thing new about OOS B17 and problem with dualboot?
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
I'm on OOS b17 and Evolution x without boot problems. Both slots are unencrypted and the password is configured only in OOS.

I'm using Ae3NerdGod twrp.

Only one problem. If I setup a password in evolution, I get password error on OOS even if I have restored the previous data backup, as reported in GitHub.

I did also the backup of locksettings.db, gatekeeper.* and restored, but without success. The only way is to delete the files on OOS data partition and setup a new password.

I continue to investigate :)

Thanks to all guys for this fantastic work!!!
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
So far very few, if any have been able to get passwords on both slots working.

I sure hope you can figure it out.

To recover when you would be encrypted you would need to format the metadata partition. So apparently there are changes made to that partition when setting a password.

Maybe by restoring that partition you can get it to work.

This is something I wanted to try it, but I didn't get there time for it yet.

Also many, including myself, have problems getting beta 17 to work with dual boot.

But I have only tried the version with twrp 3.4, the one you mention is still on twrp 3.3.1 I think.

When I have time I'll play around with it some more.
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
Good point! I will try it :)

It's correct, dual twrp 3.3.1 without any problem at boot (slot A OOS B17, slot B evo).

Now I'm cooking my personal version of Evolution Rom. After I will try the metadata way :)

I report if there will be any progress.
[OnePlus 7 & 7 Pro Cross Device Development] enragedpaza:
Has anyone used this to have nethunter and a stock android build dual boot?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes I guess I have read here that someone had this.

I guess the thing with it was that Nethunter is flashing to the active slot instead of the inactive as it is for all the ROMs.
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
Guess this has been abandoned. Would have been nice to have Orange Fox integrated into this
[OnePlus 7 & 7 Pro Cross Device Development] enragedpaza:
So I had issues with this and could not past boot of any rom. So I used msm tool to revert back to stock and retry with fresh root, twrp, etc... now i cannot get official twrp to flash
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
If you reverted back with msm tool then not being able flash is not likely caused by this mod.

Are your partitions back to stock?

---------- Post added at 05:31 AM ---------- Previous post was at 05:30 AM ----------

Why is it abandoned?
[OnePlus 7 & 7 Pro Cross Device Development] enragedpaza:
I believe so, i cannot access twrp (when i boot to it there is an error then the rom is unbootable.) to see. Devices has 256gb of storage, 20.53 used for system, and 235gb free.
[OnePlus 7 & 7 Pro Cross Device Development] Lossyx:
It's not, last time I checked it worked fine so there is really no need for an update every single day.

And integrating orange fox, that's a big joke lol.

A hint for the future; jamescable is a troll, ignore him.
[OnePlus 7 & 7 Pro Cross Device Development] jamescable:
So, let's get this straight, it never got the OFFICIAL twrp 34 update (dev didn't fix that). If another dev didn't jump in, we would have an outdated twrp that may not have worked with Android 11. In saying that, the original dev has been on xda on other threads but has NOT been on this thread to talk about issues, fixes, updates since June.....when Android 11 officially comes out and if this doesn't work, it's abandoned by the original dev. Just like the original xposed, it was abandoned by original dev but others ha e picked it up. So far, in the recent months, same has happened here
[OnePlus 7 & 7 Pro Cross Device Development] enragedpaza:
Filesystem Size Used Avail Use% Mounted on

/dev/root 3.2G 3.1G 106M 97% /

tmpfs 3.6G 976K 3.6G 1% /dev

tmpfs 3.6G 0 3.6G 0% /mnt

tmpfs 3.6G 0 3.6G 0% /apex

/dev/block/sda16 92M 780K 89M 1% /odm

/dev/block/dm-1 992M 902M 74M 93% /vendor

none 3.6G 0 3.6G 0% /sys/fs/cgroup

/dev/block/sda2 27M 3.9M 22M 16% /mnt/vendor/persist

/dev/block/dm-2 222G 2.7G 219G 2% /data

/dev/block/loop1 836K 808K 12K 99% /apex/com.android.tzdata@235002100

/dev/block/loop2 4.9M 4.9M 0 100% /apex/com.android.conscrypt@235002100

/data/media 222G 2.7G 219G 2% /storage/emulated
[OnePlus 7 & 7 Pro Cross Device Development] fp1707:
So as some have been reporting, I have the same issue of getting stuck at patching /vendor/fstab.qcom. I'm going to attempt installing Paranoid Android Temporarily on my A Partition, if that doesn't work, then idk, maybe I'll try reverting to stock.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Use the dual boot twrp 3.3.1 version it works with oos ob 17, as [MENTION=10348517]invernomut0[/MENTION] has posted some posts back.
[OnePlus 7 & 7 Pro Cross Device Development] fp1707:
So to be clear, there's no setting passcodes on both roms? I can only set it on one or the other right?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes set passcode only on one of the slots.
[OnePlus 7 & 7 Pro Cross Device Development] fp1707:
Steps to get secure lockscreen working on both OS:

Prerequisites:

1) One of the 2 roms be OOS

2) Both ROMs be Decrypted

Steps:

1) Boot into OOS

2) Setup a secure lock in OOS

3) Boot into Recovery

4) Switch to Other Slot

5) Reboot System

6) Setup Secure lock in other OS

7) Reboot to Recovery

8) Swith to OOS slot

9) Reboot to Recovery

10) Delete Lockscreen.db, gateway, passcode from /data/system

11) Boot to system

12) Setup Secure Boot in OOS

13) Profit

Warning:

1) This isn't actually secure since you aren't encrypted

2) This may not work with other secondary roms or other combos of roms

I tested this with Oxygen OS and Paranoid Android and it works just fine

If you try other combo of ROMs, please do share your results, thanks ?
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
One note, I had the ob17 installed in single boot, before flashing the dual boot twrp, I don't know if that make the difference.
[OnePlus 7 & 7 Pro Cross Device Development] fp1707:
Ooh, thank you for that
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
No, I did the same. With dual boot twrp 3.3.1 it worked, with dual boot twrp 3.4 it didn't.
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
That happens sometimes with certain ROMs..happened to me several times with carbonrom..turns out it was the stock recovery or something that caused the issue.Flashed twrp before flashing dualboot zip and it worked fine.
[OnePlus 7 & 7 Pro Cross Device Development] fp1707:
I've been using 3.3.1 the whole time and nothing haha

---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------

Ohh, I have yet to try this.
[OnePlus 7 & 7 Pro Cross Device Development] almightysiman:
stuck at patching vendor/fstab.qcom when I flashed ob17，no luck with dualboot 3.3.1 or 3.4.
[OnePlus 7 & 7 Pro Cross Device Development] fp1707:
Just tried this, no success. Although, I only had 3.4 twrp(non-dual boot) at hand so that might be why it didn't work.

Update: Also tried 3.1.3 and 3.1.1 and nope, no luck getting OB 17 to work with dualboot
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Yes, non dual boot will not work.
[OnePlus 7 & 7 Pro Cross Device Development] fp1707:
Actually non-dualboot twrp itself works just fine on it itself. From what I've seen. As long as you don't mess up flashing something while on the wrong partition, it should be fine.

They just don't seem to help get OB 17 working with dualboot.

*EDIT*: Actually please don't go around flashing non-dual boot twrp, you'll screw yourself. Other recoveries can't detect the internal storages because it's partitioned weird or some other reason. And without access to internal storage, you can't even flash dual boot twrp back without external device help.

TL;DR: Don't flash non-dual boot TWRP.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Does it also work with the data common partition?

Ii thought the dual boot logic was actually in the TWRP code, but I must be wrong then.

But I guess it's separate and TWRP is added to the dual boot logic like Magisk is.
[OnePlus 7 & 7 Pro Cross Device Development] fp1707:
Oh my bad you're right, the internal storage partitions don't work with regular twrp. They just show up as 0MB space.

I'd been using external USB and didn't even notice this ?.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Always good when people are willing to test, so good job anyway. :)
[OnePlus 7 & 7 Pro Cross Device Development] HSchmotz:
Hello, is no one interested to repair this nearly excellent program? Same problem with OB18. Flash okay, but when installing dualboot it stops by fstab. I tried several things but can't find a solution.
[OnePlus 7 & 7 Pro Cross Device Development] ele95:
edit

---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------

yeah for some reason open beta is broken for me too , for now only stable work
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Have you tried with the original zip, posted on the op?

It works for me. No encryption and magisk on both slots open beta 18 and evolution x
[OnePlus 7 & 7 Pro Cross Device Development] almightysiman:
You don't stuck on modify vendor/fstab.qcom?
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
No, I wouldn't have said that it works for me if it didn't. :)
[OnePlus 7 & 7 Pro Cross Device Development] almightysiman:
no matter what I tried,It just stop by fstab.qcom,Can You share your procedure？
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
I can't remember. I know I tried with the TWRP 3.4 zip first and it failed. After that without repartitioning I tried the original zip from the op and it succeeded.. this was with ob17. I flashed on 18 the same way as usual, from the not active sit and worked as well.

I didn't use any special procedures.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
When I reinstalled my phone a week ago or so and set up with the Dualboot again as I wanted to try a new custom ROM (Carbon ROM) in one of the slots I recognized that when I updated Carbon ROM (which is on slot B unencrypted) I had to format data in order to get it booting successfully (so it was just an Update from Carbon ROM to a newer Version!).

So that of course broke my ROM in Slot A (EvolutionX) because that slot is encrypted. So now I can not use slot A anymore since the Format of Data from slot B now broke the encrypted slot A with PIN and then I had to set up Carbon ROM in slot B again as I had to do a Format Data because it was not booting up after the update anymore.

I mean it was just a normal ROM update of the same ROM. I am doing the same with EvolutionX in slot A when there is an Update and had never had the issue that it was not booting anymore and I had to do a FORMAT DATA.

Not sure if this is something special with Carbon ROM or something else as I dont remember that I had issues before when I was running another custom ROM in slot B.

Does anyone have any input on this or perhaps have had the same issues after updating a ROM in one of the slots?

Thank you!
[OnePlus 7 & 7 Pro Cross Device Development] almightysiman:
So you are running ob18 with decrypted data?
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Please after this post you asked if it worked and now you ask if the position is not encrypted. I am starting to regret I wrote it, because apparently it's not being read.

I am willing to help to the best of my ability, but I am not going to spoon feed you with answers that have already been given. Especially if the answer has been given by me to you very recently.
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
I think i'm in trouble here folks, I could really use some help. i've been running this mod with no real issues for months now, enjoying it thoroughly, but today I ran into a problem. I wanted to install a new ROM onto my experimentation slot, so i first went into TWRP and formatted that slot. Next step was to reboot into TWRP with the opposite slot active and flash the ROM, but first i went to flash the dualboot TWRP zip once more, just to be safe...i wasn't sure how formatting the slot would impact it and i didn't want to just reboot to recovery and end up with the stock recovery and have to go through the whole fastboot rigamarole to get my dual boot back. but now i'm stuck. the dualboot installer began to run, but it won't go any further than "patching active slot: _a..." It's been sitting here on the first step for 15 minutes. It's not frozen, because the little blue progress indicator at the bottom of the screen is moving consistently (though it's not a true progress bar, so it never fills up or indicates how far along it has gotten, it just moves to let me know it's still alive). i really don't think it's ever gonna move past this step, something seems to have held it up...but i'm terrified to stop it. Won't it basically ooberscroo my phone if i interrupt this install? or is it still early enough to leave me unscathed? what do i do? should i give it more time or is that futile? how would i go about stopping it in the least nuclear way? is there any hope for me, or is my phone french toast now? please, any assistance would be so appreciated, it's a bit time sensitive also, i'm in the midst of the crisis as i type this and i don't want to do anything without at least getting some input...please help :(
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
If it still hasn't moved on our aborted I think your only option is to force reboot.

Your other slot, b, might still be bootable.

If you didn't repartitioning it probably didn't mess up too much. And you should be able to just flash a new rom (boot image) to the slot.

If the partitions are messed up, you can find instructions to manually reputation in the read me on GitHub. See op for the link.

Good luck.
[OnePlus 7 & 7 Pro Cross Device Development] HSchmotz:
Hi, had the same problem. There is no OS in that slot. Reboot to fastboot, set slot with OS as active, reboot.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I've got bad news everybody. I was hoping to finally get my op7pro back from warranty but it was lost at the repair center. Furthermore, there's no op7pro's to replace it (or even 7ts for that matter) and so I'll be getting a oneplus 8 instead. This means it's the end of this mod (at least from me). As per usual, I have everything on my github so if anyone wants to pick up where I left off with a fork or something, they're more then welcome to
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
yeah i wasn't repartitioning and it was the first slot, so it didn't hurt anything at all. thanks for the reply
[OnePlus 7 & 7 Pro Cross Device Development] oscarmaldonado:
Great news for me, any chance for you to create a dual boot for ONEPLUS 8 PRO, I enjoyed my dual boot OnePlus 7 pro which I still have it but since I bought the 8 pro I really missed the dual boot and the extra partition for storage. Thanks for your great work.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yeah lets hope he will built it for the Oneplus 8 series. That would be great.

Guess my next device will be the Oneplus 8t after the Oneplus 7 now!
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Too bad,,but good luck for you,,this is the best Mod,,
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Ohh.....my Oneplus 7 is dead now and I got a used Oneplus 6t for now to play with.

I have adjusted this dualboot now for my Oneplus 6t to be able to use dualboot on that phone. It works after some more adjustments.

Have also just updated this dualboot-TWRP for the Oneplus 7 Series with the latest Magisk 21.0
[OnePlus 7 & 7 Pro Cross Device Development] SirMario1:
Will a old DUALBOOT version prove problems in the future?

Hi, I just got a OnePlus 7 Pro and I wanted to install DUALBOOT on it. However, I see that the project got discontinued last week.

Could there be a problem in the future if i install DUALBOOT now and new version of OxygenOS comes out?

Or are those two separate and is DUALBOOT expected to be stable enough for prolonged use (2-3 years)?

I don't think new ROM version will conflict with the partitions DUALBOOT makes but I'm asking just to be sure.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Hello!

Yes I already see issues now when one slot is haveing Android 11 and the other has Android 10.

It works but when flashing the dualboot to the slot where Android 11 is installed it gets stuck when patching that Android 11 slot so that slot stays without TWRP then.

I actually dont have the Oneplus 7 anymore since it broke a few days ago so I got a Oneplus 6t now and will adjust this script to that one now but there seems to be some things that needs to be adjusted in order to work correctly with Android 11 as it seems.

Lets hope that someone else will pick up this project again and try to modify/adjust it for Android 11 etc. I guess I have dificulties to figure out/fix this myself.
[OnePlus 7 & 7 Pro Cross Device Development] SirMario1:
Thanks for the answer! This saves me a lot of trouble to know.

Are there other ways I can have multiple ROMS on the same phone?

Like with a virtual machine application?
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
You got Android 11 on OnePlus 7 or did you manage to get dual boot running on OnePlus 8?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
No, I have a Oneplus 6t now since my Oneplus 7 is dead.
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
When you flash android 11 with dualboot and slot stay without twrp is it booted? I think there will be invalid argument metadata
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes I got it to boot.
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Please share the step,,is it depcrypt?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes I have both slots dekrypted.

I am doing some debugging right now to see at which command exactly the script is hanging when having Android 11 in one slot and I am actually doing this on a Oneplus 6t now as I dont have the Oneplus 7 anymore but I guess when we have figured out where exactly it hangs and know what to fix to get this working properbly it can be easy adjusted to the Oneplus 7 series here as well.