yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 & 7 Pro Cross Device Development] Albinoman:
Are you guys just flashing android 11 treble ROMs or is there a rom I haven't noticed?
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Afaik there is no Android 11 room for OnePlus 7. They are on OnePlus 6T as mentioned above.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes correct. I have a Oneplus 6t now and not the Oneplus 7 anymore.

There is no Android 11 ROM for the OP7 yet.
[OnePlus 7 & 7 Pro Cross Device Development] Albinoman:
My bad. Misread
[OnePlus 7 & 7 Pro Cross Device Development] Dark Fear:
hi there, anyone tried dual booting AOKP A11 rom?
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Yesss,,not work,,
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Is this for OnePlus 7 or OnePlus 6T?

If for OnePlus 7 could you please direct me to where I can find this?
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
https://xdaforums.com/oneplus-7-pro/development/rom-r-kang-os-v11-0-awakening-t4174989

Its for 7 pro
[OnePlus 7 & 7 Pro Cross Device Development] vladvlad12:
Installed this, installed Kang, not working, tried to reboot into recovery and i get No Command... Why is that?

Workaround was to reboot into fastboot, then boot twrp from adb command, and then reboot into recovery...
[OnePlus 7 & 7 Pro Cross Device Development] vladvlad12:
Installed dualboot. Rebooted into recovery, flashed OxygenOS beta on slot A, and then flashed this zip again but It seems to be stuck at patching fstabs, any solution?
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Dualboot not working with android 11,,just wait updated twrp with fully working with android 11 with decrypt supported,,,and dont try dualboot with oos beta 17 and 18 ,you will stuck when patching fstab,,,seem beta 17 and 18 cannot be decrypt either.
[OnePlus 7 & 7 Pro Cross Device Development] vladvlad12:
Thanks for info!
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
I using it with oos beta 18 on a OnePlus 7 (not pro), but I seem to be one of the lucky ones :)
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Lucky u,,maybe this only happen with 7 pro,,but work with new stable update 1.0.3.5 .
[OnePlus 7 & 7 Pro Cross Device Development] vladvlad12:
Installed OxygenOS on both slots, one not rooted, one with root, and on routed one added kali nethunter.

Seems to work fine for now.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Hi!

I guess it is because for Android 11 this Dualboot TWRP needs to be adjusted to detect Android 11 ROMs as with Android 11 some system files for which the Dualboot is searching for are in a different folder as on Android 10.

I unfortunately dont have a Oneplus 7 anymore now.

Having a Oneplus 6t now and have adjusted this Dualboot to work with the Oneplus 6t as well and it can boot both Android 10 and Android 11 now! Still not everything is 100% working on A11 but at least it is booting!
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
Great news!

could you please share the changes you made? (Changes related to boot android 11 I mean:))

thanks!
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
The path for the init.rc file is different in Android 11. So that needs to be adjusted in the script.

Android 10: /system_root/init.rc

Android 11: /system/etc/init/hw/init.rc
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
Thanks a lot for sharing this info!

I modified the script in this way:

if ! $KEEPVERITY; then
if [ -f "/system/etc/init/hw/init.rc" ]; then
ui_print "- Android 11 found - using new path for init.rc"
rm -rf /system_root/datacommon /system_root/init.mount_datacommon.sh /system_root/init.locksettings_dualboot.sh
[ "$(grep '# Zackptg5-DualBoot' /system/etc/init/hw/init.rc)" ] && sed -i -e "/# Zackptg5-DualBootMod/,/init.mount_datacommon.sh/d" -e "$d" /system/etc/init/hw/init.rc
while true; do
[ "$(tail -n1 /system/etc/init/hw/init.rc)" ] && break || sed -i '$d' /system/etc/init/hw/init.rc
done
else
ui_print "- Android 10 found - using standard path for init.rc"
rm -rf /system_root/datacommon /system_root/init.mount_datacommon.sh /system_root/init.locksettings_dualboot.sh
[ "$(grep '# Zackptg5-DualBoot' /system_root/init.rc)" ] && sed -i -e "/# Zackptg5-DualBootMod/,/init.mount_datacommon.sh/d" -e "$d" /system_root/init.rc
while true; do
[ "$(tail -n1 /system_root/init.rc)" ] && break || sed -i '$d' /system_root/init.rc
done
fi

and

if [ "$layout" == "a/b/c" ]; then
ui_print " Installing commondata mount script"
magiskpolicy --load $file --save $file "allow init media_rw_data_file dir mounton" #"allow fsck block_device blk_file { ioctl read write getattr lock append map open }"
mkdir /system_root/datacommon 2>/dev/null
set_perm /system_root/datacommon media_rw media_rw 0771 u:object_r:media_rw_data_file:s0
cp -f $tmp/init.mount_datacommon.sh /system_root/init.mount_datacommon.sh
set_perm /system_root/init.mount_datacommon.sh 0 2000 0755 u:object_r:shell_exec:s0
if [ -f "/system/etc/init/hw/init.rc" ]; then
ui_print "- Android 11 found - using new path for init.rc"
[ "$(grep '# Zackptg5-DualBootMod' /system/etc/init/hw/init.rc)" ] || echo -ne "\n# Zackptg5-DualBootMod" >> /system/etc/init/hw/init.rc
echo -e "\non property:sys.boot_completed=1\n exec_background u:r:$context:s0 -- /init.mount_datacommon.sh\n" >> /system/etc/init/hw/init.rc
else
ui_print "- Android 10 found - using standard path for init.rc"
[ "$(grep '# Zackptg5-DualBootMod' /system_root/init.rc)" ] || echo -ne "\n# Zackptg5-DualBootMod" >> /system_root/init.rc
echo -e "\non property:sys.boot_completed=1\n exec_background u:r:$context:s0 -- /init.mount_datacommon.sh\n" >> /system_root/init.rc
fi
fi

hope it's correct :)
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes that looks correct. :)
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
Thanks mate! Really appreciated!
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
If you have this now booting on a11 could you please share the zip?!
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
Ok this is a file that seems to work, I am posting it Here

Steps taken as per instructions used on Telegram in the Kang11 rom chat

Rohit Padmin

a user

Oct 16, 2020 12:52:22 PM

Came from OOS 10 with Dualboot TWRP

1.Flash Kang11 in inactive slot,,format data inactive slot better

2.Flash original TWRP 3.4.0.0

3.Flash Magisk 21.zip

4.Reboot to Recovery

5.Flash DualbootA11 ( i used OTG storage ) it will stuck when patching inactive slot,,nevermind,just hard reboot ( power+Volume up)

6.Enter Recovery ( power + volume down )

7.Flash Magisk A11.zip ( i use otg storage )

8.Wipe cache and reboot

9.Play with Kang11 while,,

10.Reboot to recovery

11.Change to inactive slot,,Reboot recovery

12.Flash Dualboot TWRP for android 11,,it will stuck when patching inactive slot,nevermind just hard reboot ( power +volume up)

14.hit power button,,enjoy
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
Hi guys,

here you can find the Andorid 10 and Andorid 11 compatible version. It still in alpha stage.

[url]https://github.com/Invernomut0/TWRP-DualBoot-Guac-Unified/releases/tag/A11-0.2[/URL]

Please report problems.

FLASH PROCEDURE:

Example (starting point)

Slot A A10 Rom

Slot B A10 Rom

1 - Flash from slot A OOS, A11 rom

2 - Flash Orangefox-DualBoot-Guac-Unified-A11-V0.2.zip

3 - Reboot to recovery (Now you are in slot B automatically)

4 - Format data

5 - Flash Orangefox-DualBoot-Guac-Unified-A11-V0.2.zip

6 - Flash A11 Magisk zip ([url]https://xdaforums.com/attachment.php?attachmentid=5113849&d=1602473421[/URL])

7 - Reboot to system

Ending point

Slot A A10 rom

Slot B A11 rom

Now you should have a working A10 rom on slot A and a working A11 rom on slot B.

Please report any problems.

Enjoy!
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Ahh great. You build it with Orangefox now. Cool. :)
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
Yeah, thanks to your info!

Now I'm working to automatic install the correct magisk version during slot flash (V21 for a11 and V20.4 for a10).
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Ahhh great. That is cool. For the Oneplus 6 series I had to redo/adjust some other things to get everyrhing working. Also I re-did how the Commondata is mounted with a Magisk Bootscript because the other method how it implemented for this Oneplus 7 series I did not get to work at all. Also I had ro adjust a few more things in the script to have everything as it should because on the Oneplus 6 we dont have a Metadata partition from the beginning.
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
WOW! a lot of work! I made a very little mod :)

Do you think is it possibile to merge the two project? A mod for OP6 and OP7 unified?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Yes. You know I was thinking about the same right now as we both have done great and different things and adjustments to the Oneplus 6 and Oneplus 7 series.

I get back to you later reg. this. :)
[OnePlus 7 & 7 Pro Cross Device Development] invernomut0:
You can find my github here:

https://github.com/Invernomut0/TWRP-DualBoot-Guac-Unified
[OnePlus 7 & 7 Pro Cross Device Development] vladvlad12:
Was support for A11 added?
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Take a look here, that is the reborn project for this with support for A10 and A11 .
[OnePlus 7 & 7 Pro Cross Device Development] vladvlad12:
It works! Thanks! :D
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Added a link in the OP to a guide I made for making this kind of mod for your device :)
[OnePlus 7 & 7 Pro Cross Device Development] amrfayezamer:
step my flash bootloader

- fastboot racovary twrp cmd

- adb sidload twrp dualboot repartion

- reboot

- flash oos 10 rom slot B

- flash twrp reboot

- flash Dm-Verity & Magisk slot A

- reboot and setup Android A

- Reboot into recovery

- flash oos 10 rom slot B

- flash twrp reboot

- flash Dm-Verity & Magisk slot B

- reboot and setup Android B

- Reboot into recovery change slot to A

When reboot into OOS 10 slot A but pin not opening my android but when reboot to into oos 10 slot B b pin opening my android

What is the solution to the pin problem in slot A
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
You can only set a PIN/password in one of the slots! Not in both.

If you have your ROM where the PIN/password is not working now encrypted you need to format data on that slot and set it up again without setting a PIN/password.
[OnePlus 7 & 7 Pro Cross Device Development] Krsmqn:
OOS 11?
[OnePlus 7 & 7 Pro Cross Device Development] vladvlad12:
Did not try with oos 11.
[OnePlus 7 & 7 Pro Cross Device Development] Joker123##:
Should work with decryption, try and let us know here.
[OnePlus 7 & 7 Pro Cross Device Development] killabit:
Anyone tried this with current OS models?
[OnePlus 7 & 7 Pro Cross Device Development] Nimueh:
If by that you mean OOS 11 then no, there is a version for that here though.
[OnePlus 7 & 7 Pro Cross Device Development] 2-e:
Not sure where to post this aware that this thread is pretty dead...But Im repartitioning and have a simple question. Im on the last step trying to calculate my userdata_size. I run the command then get a long list of ascending numbers, with the largest number on the very top. Which number would be my userdata_size? Id hate to enter the wrong number of coarse. Hopefully someone can help me with this quickly.

thanks
[OnePlus 7 & 7 Pro Cross Device Development] Littlemether:
Ty for starting this TWRP build. Been having two roms and learning this stuff from it.
[OnePlus 7 & 7 Pro Cross Device Development] seigtm:
Hello, everyone!

Has anyone managed to solve the problem with 2 pins on 2 slots yet :(?
[OnePlus 7 & 7 Pro Cross Device Development] :
I'm interested in trying this with AOSIP, but I know that ROM bundles TWRP with the ZIP. Will it be a problem? I'm thinking I can just reflash this one from fastboot, but would like clarification if possible lol
[OnePlus 7 & 7 Pro Cross Device Development] mjb337:
Thanks bro
[OnePlus 7 & 7 Pro Cross Device Development] f41lbl0g:
Just flash the dualboot recovery after flashing the aosip zip (before rebooting recovery) and you will be fine.

---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------

Flash the dualboot zip right after flashing oos (before rebooting to recovery). Also try using a custom kernel if that doesn't work. I am on skydragon kernel and it works fine, but I think it should work without it as well. Using OOS 10.3.1 on the 7 Pro.
[OnePlus 7 & 7 Pro Cross Device Development] :
Actually, idk if it really makes a difference but all kernels support F2FS, even stock kernel has support for it.
[OnePlus 7 & 7 Pro Cross Device Development] edong23:
....

Disk /dev/block/sda: 61409280 sectors, 234.3 GiB

Logical sector size: 4096 bytes

Disk identifier (GUID): 22AE74FC-A21B-73BD-5E2B-0A010806501D

Partition table holds up to 32 entries

First usable sector is 6, last usable sector is 61409274

Partitions will be aligned on 2-sector boundaries

Total free space is 0 sectors (0 bytes)

Number Start (sector) End (sector) Size Code Name

1 6 7 8.0 KiB FFFF ssd

2 8 8199 32.0 MiB FFFF persist

3 8200 8455 1024.0 KiB FFFF misc

4 8456 8711 1024.0 KiB FFFF param

5 8712 8839 512.0 KiB FFFF keystore

6 8840 8967 512.0 KiB FFFF frp

7 8968 74503 256.0 MiB FFFF op2

8 74504 77063 10.0 MiB FFFF oem_dycnvbk

9 77064 79623 10.0 MiB FFFF oem_stanvbk

10 79624 79879 1024.0 KiB FFFF mdm_oem_dycnvbk

11 79880 80135 1024.0 KiB FFFF mdm_oem_stanvbk

12 80136 80263 512.0 KiB FFFF config

13 80264 969095 3.4 GiB FFFF system_a

14 969096 1857927 3.4 GiB FFFF system_b

15 1857928 1883527 100.0 MiB FFFF odm_a

16 1883528 1909127 100.0 MiB FFFF odm_b

17 1909128 1913223 16.0 MiB FFFF metadata

18 1913224 1945991 128.0 MiB FFFF rawdump

19 1945992 61409274 226.8 GiB FFFF userdata

This is my output, will it work?

Mine is OP7

Thanks!
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
That's good to know, custom kernel support's up in the error though

Looks good to me :)
[OnePlus 7 & 7 Pro Cross Device Development] rejectedjs:
Has anyone had any success in getting this to work with Havoc OS + F2FS?

I went from a completely clean & stock OOS but with F2FS and flashed this zip, which made OOS on slot B.

I flashed the zip and chose a/b/c with disable verity and keep force encryption. Then I switched to A slot, rebooted recovery and was still A slot, and flashed havoc and then flashed the zip.

Havoc was stuck on the boot logo flashing, and trying to boot from OOS didn't work at all. So I went back to twrp and saw that /data failed to mount and it was set back to ext4. So I changed data back to F2FS and OOS booted right up but Havoc still did the same thing. I made sure both slots were F2FS (not sure if that's a thing, one slot being ext4 and the other F2FS).

Havoc mentions to flash it and twrp installer, reboot recovery, flash it and twrp installer again, reboot recovery and then you can boot it, but I first tried it with the dualboot tutorial (reboot to slot you don't want to install rom to, install rom, install dualboot zip) and nothing changed. I tried the havoc instructions where it says flash it and then flash twrp, so I did havoc>dualboot zip, reboot recovery, havoc>dualboot zip, and that just screwed everything up and made /data ext4 again.

What am I doing wrong? Thanks for any help
[OnePlus 7 & 7 Pro Cross Device Development] Travisholt92:
This does not work on guacamoleb and following your steps wiped /dev/sda. I had to manually reformat /dev/by-name/persist as ext4 (I think it was emmc after using msm tool to repartition the device)

in twrp terminal (or adb shell) use

mke2fs -t ext4 /dev/block/by-name/persist

And do a factory reset. This will fix camera and a few other issues. But a file will still be missing for sensors in /mnt/vendor/persist/sensors/
[OnePlus 7 & 7 Pro Cross Device Development] Nikhilesh_@14:
:/ $ su -c sgdisk /dev/block/sda --print

Disk /dev/block/sda: 30169088 sectors, 115.1 GiB

Logical sector size: 4096 bytes

Disk identifier (GUID): 90B67897-BCAC-F4C6-2B7B-32216F4FCBB6

Partition table holds up to 32 entries

First usable sector is 6, last usable sector is 30169082

Partitions will be aligned on 2-sector boundaries

Total free space is 0 sectors (0 bytes)

Number Start (sector) End (sector) Size Code Name

1 6 7 8.0 KiB FFFF ssd

2 8 8199 32.0 MiB FFFF persist

3 8200 8455 1024.0 KiB FFFF misc

4 8456 8711 1024.0 KiB FFFF param

5 8712 8839 512.0 KiB FFFF keystore

6 8840 8967 512.0 KiB FFFF frp

7 8968 74503 256.0 MiB FFFF op2

8 74504 77063 10.0 MiB FFFF oem_dycnvbk

9 77064 79623 10.0 MiB FFFF oem_stanvbk

10 79624 79879 1024.0 KiB FFFF mdm_oem_dycnvbk

11 79880 80135 1024.0 KiB FFFF mdm_oem_stanvbk

12 80136 80263 512.0 KiB FFFF config

13 80264 969095 3.4 GiB FFFF system_a

14 969096 1857927 3.4 GiB FFFF system_b

15 1857928 1883527 100.0 MiB FFFF odm_a

16 1883528 1909127 100.0 MiB FFFF odm_b

17 1909128 1913223 16.0 MiB FFFF metadata

18 1913224 1945991 128.0 MiB FFFF rawdump

19 1945992 30169082 107.7 GiB FFFF userdata

OnePlus 7 128gb
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I haven't messed with f2fs yet so you're on your own there

Only way all of sda got wiped is if you did something manually, the zip would abort before that would occur (and if not, a recovery.log immediately after flashing it would be great.

You'll need to use msmtool to bring everything back but even then you'll likely need to run it through warranty

128gb is as of now, untested (mine is 256gb) but should work
[OnePlus 7 & 7 Pro Cross Device Development] Nikhilesh_@14:
Mine is the Non pro model.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Right, partition layout is the same other than userdata size
[OnePlus 7 & 7 Pro Cross Device Development] rejectedjs:
Damn. Well it's still a pretty cool project and massive props to you for figuring it out. If F2FS ever gets a method I'll definitely come back and give it a try sometime.
[OnePlus 7 & 7 Pro Cross Device Development] Terrigible:
Isn't bricking your phone due to user mistake and unlocked bootloader not covered under warranty?
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
I succesfully manage dualboot OOS Beta 11 and Evolution 4.1 ,,heres what i did :

1.Reboot TWRP >Format Data

2.Reboot TWRP > Flash original TWRP 79

3.Reboot TWRP > Flash Dualboot TWRP ( sideload ) - choose a.b.c layout -disable.force encryption

4.Reboot TWRP (dualboot now) > Flash OOS Beta 11 >Flash Dualboot TWRP

5.Reboot TWRP > Flash OOS Beta 11 again -

> Flash Dualboot TWRP

6.Reboot TWRP > Flash Evolution 4.1-> Flash Dualboot TWRP

7.Reboot to System,enjoy Dual Boot,,its Awesome!!

Oneplus 7 Pro 256 gb
[OnePlus 7 & 7 Pro Cross Device Development] theoneslr:
Can you flash a different kernel for each rom or does it have to be the same kernel for both roms?
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
I flash different kernel with FKM,,Arter97 for OOS Beta 11 and Weeb Kernel for Evolution 4.1,,so far so good,,,its all boot normaly,,,

Try Flash kernel with its support with FKM or EXKM,,more simply.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Released v2 of the zip! Changelog:

* Changed datacommon mounting script to be more granular - user chooses what folders are mounted directly over internal storage - see README for more details

* Added f2fs format option - can choose format type for each slot

* Added more options for common data partition sizing

* Formerly investigated lockscreen issue - unfixable - see Limitations section in readme for workaround
[OnePlus 7 & 7 Pro Cross Device Development] muphetz:
Can i just dirty flash ?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
This isn't a rom so yes, just choose keep current layout
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Rereleased v2 with bug fix for f2fs datacommon
[OnePlus 7 & 7 Pro Cross Device Development] Amr Fathii:
Sorry, but this is kind of confusing to me.

So, currently I'm on OOS 10.0.2 and would like to flash Luis custom rom on the other slot (actually not sure which one OOS is currently flashed on) while keeping the same setup of the current stock rom without wiping or deleting any stuff.

So first, is that possible?

Secondly, how to do so? Just flashing the linked zip in the op in my current flashed twrp and then flash the intended custom rom?
[OnePlus 7 & 7 Pro Cross Device Development] theoneslr:
Yes, I would like to flash and setup the dualboot twrp. Can we get a detailed step by step process? Seems like a lot of steps are involved. If you could provide this I’d greatly appreciate it! Great work by the way on this. I have been looking forward to a dualboot ever since dualboot patcher was discontinued. Thank you for all the hard work on this!
[OnePlus 7 & 7 Pro Cross Device Development] Nikhil:
https://xdaforums.com/oneplus-7/one...ficial-twrp-oneplus-7-7-t4066851/post82061725

Couldn't be simpler ^
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
It's in the OP
[OnePlus 7 & 7 Pro Cross Device Development] pro_granade:
I tried removing the abc layout and going back to stock and keeping the same ROM on my a slot, now it shows I only have about 64gb remaining of 128gb, system taking half, and flashing the recovery script it says my userdata is 226gb and my device is 128gb
[OnePlus 7 & 7 Pro Cross Device Development] matze19999:
OnePlus is the only phone manufacturer, which covers this in its warranty
[OnePlus 7 & 7 Pro Cross Device Development] Terrigible:
They must have changed it. I remember clearly they said they would not cover damage due to bootloader unlock.
[OnePlus 7 & 7 Pro Cross Device Development] matze19999:
[MENTION=6037748]Zackptg5[/MENTION] how do I have to format the mounts.txt file? I tried to write the name of every folder in a line, but it didn't work.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I'll update the OP with this later today but it's for example:

DCIM
Music
Pictures

You list a folder per line - no preceding datacommon or whatever.

If you're using a Windows texr editor, make sure EOL character is LF and not CRLF
[OnePlus 7 & 7 Pro Cross Device Development] pro_granade:
hey could I get help with that issue like 3 or 4 posts above, sorry but I'm very confused on why its doing this now
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Hmm, try formatting data in twrp gui, flashing stock oos from both slots, then flash whatever rom you want
[OnePlus 7 & 7 Pro Cross Device Development] theoneslr:
Great work but I'll wait until all the bugs are worked out on this!
[OnePlus 7 & 7 Pro Cross Device Development] pro_granade:
Just formatting data fixed it, thank you so much!
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Thanks for the report though. This means I'm still missing something with the formatting
[OnePlus 7 & 7 Pro Cross Device Development] gjtjbl:
Great post! I'm kind of a noob here, but would this general methodology be theoretically possible on other A/B partition phones like a Pixel? As in modifying TWRP to repartition the /data partition to have fully separate apps, etc? I've seen posts in the Pixel forums with a "limited" dual boot that shares the data partition but something like this would be really cool!
[OnePlus 7 & 7 Pro Cross Device Development] YousifG7:
Hey!

This is without a doubt incredible work, but i was wondering if we can have the same mod for the 6/6T if it is possible...

just asking.
[OnePlus 7 & 7 Pro Cross Device Development] Ohh_Trenton:
Super NOOB question, I apologize If I overlooked it but I can't seem to find an answer. How do you select A/B/C layout when flashing this zip? I can only/keep choosing stock layout. Thanks
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Theoretically this method can be applied to any a/b device

If someone with a 6/6t wants to make one. My code has mit license meaning people can take it and do what they want with it :)

In the beginning, you need to select no when it asks if you want to keep your current partition layout. Make sure you back up all your data to your PC first as itll get wiped