yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Hi.

I actually have the same issue when trying to set a PIN in my ROMs here I have set up. Strange....have to check whats going on there.

Yes I recognized that as well with Magisk. The files are actually the ones from Magisk 21.0 . I dont really get right now why it shows Magisk 20.4 as installed then. Perhapa it is the Magiskboot and Magiskinit files which are from 20.4 .

When I tried to replace them with the ones from Magisk 21.0 I just got like a bootloop or the phone was just booting directly to recovery. :rolleyes:

Anyway, thanks a lot for the headsup. I will check on these issues.
[OnePlus 6 & 6T Cross Device Development] mcdachpappe:
the file you are looking for is: tools/functions.sh

I can confirm the issues mentioned above. Sometimes magisk won't show up in OOS without any reason. Common partition files are added according to the installer, but magisk is not present afterwards. Flashing a standalone version of magisk (e.g. official 20.4) fixes this Problem.

Especially the Lookscreen issue is a bummer because you won't be able to switch back to your first 'secured' OS after finishing the setup process on your second OS.

To be more precise: Slot A = OOS, unlock via pattern; Slot B = Any custom ROM, without any unlock option (not even swipe to unlock, it's set to none). After finishing the setup process on Slot B, change to Slot A via recovery, pattern isn't recognized on Slot A anymore. This is a huge bug currently.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
So in OOS you are able to set a pattern? In the custom ROMs it is not even possible right now to set a pattern/pin at all. Intressting that you get that issue. Normally it is only happening if you had set a PIN/pattern in the other slot as well. And that actually is something device specific that can not be fixed as far as I know. I am taking a look now why we can not set a pin/pattern at all in custom ROMs.
[OnePlus 6 & 6T Cross Device Development] YousifG7:
ok man thanks for the reply and im excited to see if those issues get fixed or not, as always, no rush. and im glad in helping/reporting bugs since i have my dualboot setup now :))

Best regards.

---------- Post added at 10:19 AM ---------- Previous post was at 10:05 AM ----------

oh damn so it's the same problem we're having except that i booted both roms first then i went and tried setting a password on posp11, anyways thanks for the help it means alot. have a good day/night buddy :))
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
I am running Carbon ROM 10 and POSP 11 now and on both I have the issue that a PIN/password can not be set.

So it is correct that it works in OOS though?

Have to see if I find out what is causing this. I might have an idea but not really sure right now if I will be able to get that fixed but lets see.
[OnePlus 6 & 6T Cross Device Development] YousifG7:
i mean, i can set a password on oos but i cant unlock it because it always says that the entered password is incorrect. so yeah you can set a password but it will lock you out of your slot. i will experiment with making posp11 a 'none' password and I'll try setting a password in oos right now, brb in like 10 minutes

---------- Post added at 10:57 AM ---------- Previous post was at 10:49 AM ----------

uhm yeah no that didnt work? i set security to 'none' on posp11 and then i tried setting a password on oos but it still says im entering an incorrect password when i try to unlock it. i think the person above me can be more of a help to you. btw im having posp11 on slotA and oos on slotB if that makes a difference idk...
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
OK thanks.

If you are in that state on OOS now I think you cant get rid of the issue now since you need to delete the locksettings.db etc files on OOS and I guess that is encrypted now.

Guess you have to reflash OOS. Then set a PIN in oos boot to the other ROM which have no locksetting set.

Boot to recovery and delete the locksettings files on the POSP slot if existing. Then reboot to OOS and see if you can login.
[OnePlus 6 & 6T Cross Device Development] YousifG7:
actually im not encrypted on both slots so i just went to twrp and deleted locksettings straight away. do you want me to later and start from zero by booting oos first and setting a password then booting posp11 and seeing if i can retain my password on oos without corrupting my posp setup???
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes that would be good to know. Thanks a lot for your help.
[OnePlus 6 & 6T Cross Device Development] YousifG7:
I went to oos and set a pin, then i rebooted to recovery then rebooted again to my posp slot, i removed the lockscreen file and then i rebooted to oos and it still says that my pin is incorrect. i tried it the other way around where i delete lockscreen files from oos and then try to set a pin on posp but that just gives me the same error as yesterday so idk about that. this is as far as i did it i hope it's helpful to you in someway :good:
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
OK got it. So right now it seems you can only set a PIN in OOS but not in any custom ROM and yeah when setting a PIN in OOS and rebooting to the OS in the other slot the PIN on OOS is not working anymore.

I will check if I can figure it out and fix it!
[OnePlus 6 & 6T Cross Device Development] YousifG7:
actually i didnt need to reboot to the other slot for the pin to stop working, i just turned off the screen right after i set it and it doesnt work anyways lol. no reboot required to see the effect
[OnePlus 6 & 6T Cross Device Development] RMarques:
OP6 8/128, Dual boot V2.3, rolling with the following:

Slot A

- Lastest OOS

- Magisk 20.4

- Lastest RadioActive Kernel

- XXx Magisk Module

Screen lock with pattern is working as intended. Both kicking and unlocking and even surviving reboots.

Slot B

- Latest OOS as a base

- PiXeN-OS 11

- Magisk (debug) with custom update channel as per introductions on Telegram PiXeN channel

It doesn't allow me to set any screen lock on PiXeN-OS 11. The same problem as described in prior posts.

I'm on vacation ATM and don't need to use screen lock at all. When I do so, I'll use OOS as my daily driver and slot B as my personal test lab!
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Hello!

Thanks for that. I guess I have an idea what the issue is here and how to fix this.

In order to test that I need to repartition back my phone to stock and then repartition to A/B/C Layout again after fixing the issue and see if that solved it.

Hopefully I can have that test during the weekend. :o
[OnePlus 6 & 6T Cross Device Development] YousifG7:
did you flash and setup oos first and then set your screenlock and after that you flashed and setup pixen11? or did you setup both of them one after the other and then you set your screenlock? i did the latter
[OnePlus 6 & 6T Cross Device Development] RMarques:
I did setup both of them and did setup screen lock afterwards...just today as a matter of fact, after doing some have had problems with that, in order to test it.

Some details that might be relevant:

- I did install Magisk on slot A (OOS), using the dual boot option (somehow it ended up installing 20.4 instead of 21)

- I didn't use the in built dual boot option to install Magisk on slot B (PiXeN-OS 11), I did it manually afterwards
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Yes, magisk shows up as 20.4 for some odd reason and Yes, you need to flash A11 magisk seperately. but i had my custom rom on slot a and my oos on slot b. im also using A/B/C idk if having commondata affects this problem. anyways thanks for the reply i believe it will be useful to the Dev too
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes I know why now. :)

The Magiskfiles in the Dualboot-TWRP are the ones from Magisk 21.0 but in addition to that there are another 2 files used when Magisk is flashed from the script and these are Magiskboot and Magiskinit.

Actually those 2 files are from Magisk 20.4 therefor it is flashing Magisk 20.4 but fetching the install Version number from the Magisk 21.0 files in the ZIP.

I actually did replace the Magiskboot and Magiskinit with the ones from Magisk 21.0 as well now but then the phone is not booting to system anymore when trying to boot Android 10. It boots directly to fastboot so I switched the files

back to the ones from Magisk 20.4 . Guess I will replace the Magisk install files with the ones from Magisk 20.4 as well in the next release so that this is not so confusing anymore. :o
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Thanks for clearing this up now?
[OnePlus 6 & 6T Cross Device Development] RMarques:
Does it means "Don't upgrade Magisk kids"?!??
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
I took a bit deeper look at this now so there is actually more to be changed/updated in order to update the Magisk from the script from 20.4 to 21.0 so that is not as easy as I thought first but will take a look if I get the time.

Now at the weekend I will be focusing on the PIN/password set issue. I know why that happens but it will take some time to get this changed/adjusted and test in the script.
[OnePlus 6 & 6T Cross Device Development] YousifG7:
goodluck with that, your time and effort is definetly appreciated by the users ??
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Thank you. :o

Guess I already have a solution almost ready now for both issues. Just had not the time to test that yet as I need to repartiton my phone for that but I am planning to do that later or at the weekend now.
[OnePlus 6 & 6T Cross Device Development] YousifG7:
Yeah no need to rush it, im just hoping that your solution works out 🙌

Have a good day/night
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
New Version Info!

Hi all!

I small hint regarding the new Version I am just cooking!

Before installing that upcoming new Version you will have to repartition back to Stock layout using V3 or MSMtool before flashing the new Version as that will have changes to the partition layout!!!

So if you dont have flashed/used this Dualboot TWRP on your phone yet, it is better to wait with that a few days until the new Version is done and uploaded!!
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
New Updated Version 3.1

Hi all!

New Version 3.1 is up. :highfive:

10/30/2020 - 3.4.0-0 v3.1

- Removed unnessessary stuff which was left from the Oneplus 7 devices

- Fixed Common data mount script for Android 11

- Magisk 20.4

- Dualboot-TWRP can be flashed from USB Storage as well now

I removed some stuff which was left from when I took over this from the Oneplus 7 devices which I removed in this Version now regarding the partitioning.

That means if you had already used this Dualboot TWRP before this Version 3.1 you would need to repartition back to Stock using Version 3 or using MSMtool!!!

Also the issue with setting a PIN/password is not fixed and it seems that this is not possible to fix that easy for our Oneplus 6 devices!

It seems only to work on OOS right now but not on any custom ROM.

The Magisk Version getting flashed with this Dualboot-TWRP is Magisk 20.4 as of now. When I fully updated that with Magisk 21.0 I could not boot into the system anymore!

You need to flash this Magisk from the Dualboot-TWRP if you want to have the common data partiton mounted in the ROMs!!

After that you can directly flash another needed Magisk Version over it!

Another issue I recognized is that on Android 11 it will take like 2 minutes to reboot to system or recovery if the common data partition is mounted!

It is hanging when trying to unmount the common data partition on Android 11. Not sure if that perhaps will get fixed when we have another Magisk Version as

the Canary 20422 one running on Android 11.

Download link is updated in the OP!
[OnePlus 6 & 6T Cross Device Development] koobie777:
Just tried using 3.1 and im getting partition error when going to 32gb a/b/c (havent tried others yet) after repartition back to stock with not only 3.0 and the msm tool. I also tried using not only a usb but copying to /tmp and those didnt work either, Using 6T 128gb here. 3.0 worked great even with commondata mounting. Anyone else get 3.1 working?

Edit: all options for a/b/c 16 32 40 and 45 are not working, tried repartioning with 3.1 and 3.0 back to stock and it does show which layout was used but partioning still fails after using 3.1. MSM tool fixed each time and 3.0 still working normally. Im able to us 3.0 partion layouts and proper formatting and flashing 3.1 with everything working that way.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Ohh ok. Will check on that now.

After getting the error in TWRP can you pull the /tmp/recovery.log file and attach it here?

EDIT: OK I guess I found the issue. Seems that I missed out something for the Oneplus 6T when changing the partition format since I see it is different/correct for the Oneplus 6. I will get that fixed now. Sorry for that!

OK should be fixed now. Please re-download the latest Version again and try again!
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
New Version bugfix release Oneplus 6t!

Hi all!

Thanks to user [MENTION=2026486]koobie777[/MENTION] it was discovered that there was a bug in the new release for the Oneplus 6t devices (Oneplus 6 devices were OK!) causing the flashing to fail when repartitioning.

I have just fixed that issue and re-uploaded the new Version 3.1 for Oneplus 6t again.

So for all users who had already downloaded the new Version 3.1 for the Oneplus 6t before 11:30 CET today 31-10-2020 please re-download the latest Version.

Sorry for that but it should be fixed now and I can go on and cook new stuff for the next Version. :o
[OnePlus 6 & 6T Cross Device Development] koobie777:
3.1 working perfectly now thanks [MENTION=9574498]Wishmasterflo[/MENTION]! Excited to see how much farther you'll take this! Possibly the ability to mount common data as an external sd next? lol
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Thanks! Great that it works now. I saw directly what I had missed when comparing the files for Oneplus 6 and Oneplus 6t so it was easy to fix.

Yeah lets see I have already some thoughts about the next Version now which I just try to implement. :o
[OnePlus 6 & 6T Cross Device Development] meistr91:
I have 6 and i had i think same problem, when i tried to repartition to stock with 3.1 got a bunch of erros like "cant mount data, sucha directory doesn't exist" also same for commondata but i took msm after it settuped again and everything is working fine except for when i try to reboot if i simple reboot phone hangs up onthe black screen seems like device is off but i can bring it back only while holding power + vol up (my setup is with common data) ao i think isnt this the same bug that was on 3.0 with commondata on a11?

At the moment i have a11 on B skot other is empty, but i don't think its related to this reboot bug
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Hello! Yes I guess you got that issue because you had already re-partitioned to A/B/C with an earlier Version and then used V3.1 to repartition back correct? That would not work in that case since there were partitions existing from before V3.1 which we should not have on our Oneplus 6 devices.

But when using MSMtool or Version 3 to get back to Stock from before V3.1 it should work!

Yes the issue with the black screen on reboot is happening on Android 11 when it tries to unmount the commondata partition it is hanging there for like 2 minutes. So when on Android 11 and you have the common data partition mounted and do a restart to system or recovery the screen goes black for like 2 minutes and after that it reboots! So just wait there until it reboots.

I hope that this issue is perhaps something with the Magisk Canary 20422 we are using on Android 11 so perhaps that will get solved later on with a newer Magisk Version. Otherwise I guess it is due to some things handled different in Android 11 than in Android 10 and therefor this happens. But at least you know now why this is so just wait there until the phone reboots.
[OnePlus 6 & 6T Cross Device Development] meistr91:
Yes, that what i thought too, that when Im on 3.1 it won't happen, cuz im already on fixed version.

About reboot thing i wasn't so patience lol but i will try to wait next time, thabks for clarifying everything!

I have been using previous version pretty successfully I had one stable rom and on other slot i have been flashing different roms, without any problem, of course you need to think carefully when u want to flash a rom lol u need to remeber slots thing and when u can wipe data. Anyway im happy with this dual boot, would be nice to be able use lockscreen paswwords on both roms, but its not biggie for now.

P.S.

I have seen on 1 page you have posted that telegram channel is created and its in OP but i couldn't see. Is this channel still available?

Edit: im so sorry I see you have explained already in the post of rhis new version, honestly i have read it all before flashing, but somehow it got stock in my head that i needto use new version to repartition back... Once again, to read instructions few times is not bad idea..?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Great. Yes the PIN/password issue is still existing. I tried to get that fixed but it seems that it will never work for our Oneplus 6 devices as of now. So I am not sure if we ever get that to work. It seems to be something devlce specific to our devices causing that it is not working now.

Hmmm....yes I had removed the Telegram Channel again for now.
[OnePlus 6 & 6T Cross Device Development] CallMeAldy:
I have a question that I couldn't find an answer to. If I use the stock layout and I have OOS and Android 11 as of now. If tomorrow I decide to change my rom would it wipe my entire partition again if I still stick with stock layout?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
With stock layout you only have one data partition and can not use it for Dualboot!

For Dualboot you need to re-partition to pure A/B or A/B/C Layout (with common data) and that repartitioning wil wipe all data! If you use A/B/(C) Layout for dualboot and want to change a ROM for one slot you will need to wipe data from that slot only, so it will not have any impact to the data on the other slot or to the Common data partition.
[OnePlus 6 & 6T Cross Device Development] meistr91:
Whats about pure A/B storage is split in half with separate data?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes exactly pure A/B partitioning will split your data storage in half so you have data_a for ROM A and data_b for ROM B without Common storage.
[OnePlus 6 & 6T Cross Device Development] Newrooter22:
I don't know if this has been answered but when I tried this it work and both ROMs booted however when I go to download stuff or take a screenshot of the issue I'm experiencing it say not enough storage available.

For example chrome's download path is to emulated/0/downloads or something like that and it always says not enough space.

When I go to check it out it seems that download paths are set up to go to the same place as it would with normal set up however when I do this dualboot theres no space there for it to download it it's moved to elsewhere.

I can't screenshot to show because it won't let me so just wondering if anyone's experienced this situation.

Thanks.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Hmmm thats strange. The download path is not moved somewhere else and I dont have any issue with it.
[OnePlus 6 & 6T Cross Device Development] Newrooter22:
It might have been something av done on my end, am gonna try it again soon but with the latest release of the dualboot and see if it works.
[OnePlus 6 & 6T Cross Device Development] meistr91:
[MENTION=9574498]Wishmasterflo[/MENTION]

Hello, i have been using this for a while as i said before successfully, but now on version 3.1 in the beginning i got commondata running with a11, but now after installing some roms i have noticed that commondata is not mounting anymore, tried to reflash dual boot and then aftet magisk for a11 but still nothing, reflashed a rom by the instructions but still nothing.. maybe im doing something wrong?

Also what you mean by we need to flash dual boot after roms boots up?

So flash rom in twrp

Flash dual boot

Reboot to recovery

Flash magisk

Reboot to rom

Reboot to recoveru amd flash dual boot + magisk again?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Yes exactly you will need to flash Dualboot once again after you installed a new ROM and Magisk and booted once to it.

After that you should get the Common Data mounted.
[OnePlus 6 & 6T Cross Device Development] koobie777:
I've noticed the same goes for OTA updates as long as you export the update and manually flash or dirty flashing per slot. You also don't have to boot once you can switch back to main slot your using and reboot recovery and flash dual boot again.
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
New Updated Version 3.2

New Version 3.2 is up. :highfive:

11/14/2020 - 3.4.0-0 v3.2

- Updated with Magisk 21.1

- Prepared script for some future features

Download link is updated in the OP.

Note:

For Android 11 ROMs you still need to flash the needed Magisk Canary 20422 manually!
[OnePlus 6 & 6T Cross Device Development] YousifG7:
woah thanks for the continued support, İ'll update to this after some time when the rom im using gets an update so i can re-partiton again since im still on v3.0 and so i can clean flash some new roms. thanks again and have a good day/night :))
[OnePlus 6 & 6T Cross Device Development] koobie777:
I'm having issues mounting common data in system with 3.2 fajita, also what exactly is mount android data in common data for? Does it make it so both slots share Android data inside of the common data partition, or is it basically a switch to mount common data which is causing my issue? Btw thanks for this update I like where I can switch partition formats from ext4 to f2fs on the fly and the updated magisk is a plus.

Edit: reflashed with roms installed to both slots and common data is working again but only on slot A (could be a resurrection remix issue) still would like to know what mount android data in common data does ?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
If Common Data is not getting mounted try to reflash the Dualboot-TWRP after ROM and Magisk are set-up/installed.

Mount Android data to Common Data is something new I am just trying to implement but right now it is not really working/doiung anything yet.

I want that to mount android/data to the Common Data partition so that it will share all the apps data through both ROMS via Common Data. :o
[OnePlus 6 & 6T Cross Device Development] koobie777:
I tried reflashing already still nothing on slot B resurrection remix a10, crDroid on slot A is ok. As far as android data goes in common data it's just gonna be apps? Not google accounts or system settings like how pure A/B is correct?
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
Hmmm ok. Yes that will be just for Android Data not for system settings etc.
[OnePlus 6 & 6T Cross Device Development] koobie777:
I think I figured out what the problem was, if you flash from an external drive the common data mount script doesn't get installed no matter how many times you flash it, if you flash from internal storage the script does get installed. Working on both slots now
[OnePlus 6 & 6T Cross Device Development] meistr91:
What you mean by external drive? Otg storage? Just didnt get you cuz we must flash it from /tmp folder which is in internal storage. Cuz i had similar issue, but i always flash it from /tmp folder
[OnePlus 6 & 6T Cross Device Development] Wishmasterflo:
The first you flash it should be from tmp folder but it should work from USB Storage as well.

When reflashibg the Dualboot-TWRP to get the common data mounted it can be flashed from Common or internal storage. So there it obviously did not work when flashibg from USB Storage to get Commondata mounted.