yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] Ultraman Z:
Is your chiron came from miui 12 stable version to PE? How about your acc option? :(
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] flash713:
ACC? IDK what you mean by ACC option.. Please elaborate.
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] Ultraman Z:
AAC...

---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------

I found that Chiron official stable version is MIUI 11. Is your MIUI 12 is unofficial version??
[Tilt, TyTN II, MDA Vario III Themes and Apps] pmtan666:
Hi All,

If I want to display bigger contact picture for incoming call, what programs would you recommend besides Photo Contacts.

The following describe the problem that I have when using Photo Contacts:

1) Setup Contacts Photo using SmartName technology, that mean renaming the JPG files to <FirstName> <LastName>.jpg

2) Update some data on the same contact in Exchange server/ outlook.

3) After the ActiveSync, photo contacts will update the contact. In the process of doing so, the whole directory where the Photos are stored becomes corrupted.

All the files will just disappeared.

At first I thought it is my micro SD card, but I repeat the same process with a new SD card, the same problem still exists.

In fact, I also tried doing a reflash of WM6.1 on the device but it does not help.

Anyone encounters the same issue?

Device: TyTnII

OS: WM6.1 (Original from HTC Asia)

SW: PhotoContacts 5.08
[Tilt, TyTN II, MDA Vario III Themes and Apps] DinoZ1:
I am having the same problem but when I sync with outlook (no exchange).... :confused:

But it does not happen everytime.

When the folder is corrupt, I have to defrag the SD card, delete the "photo contact" folder and create a new one to make it work again,... :mad:
[Tilt, TyTN II, MDA Vario III Themes and Apps] pmtan666:
Looks like I'm not alone. :-(
[Tilt, TyTN II, MDA Vario III Themes and Apps] The Reaper:
I use S2U2n for displaying caller ID pics...here' the link that has more info on this s2u2.

http://xdaforums.com/showthread.php?t=381588
[OnePlus 7 & 7 Pro Cross Device Development] osm0sis:
Very ****ing badass. ?
[OnePlus 7 & 7 Pro Cross Device Development] Deleted member 7671171:
Wow, this is cool. Always wondered if something like this would be possible on AB partitioned devices.

Looking forward to testing it out :)
[OnePlus 7 & 7 Pro Cross Device Development] jaggillararla:
Does the dual boot mean I can boot two roms?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Ya. You can have a different rom on each slot
[OnePlus 7 & 7 Pro Cross Device Development] Kris Chen:
Will it impact on my original data partition if I flashed this TWRP.( I means whether my original data being splitted into 2-individual-parition + 1-common-partition and I need to reinstall my data after entering system ?)
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
The installer will tell you if it'll wipe internal storage or not.

Basically, if you choose to change the partition layout, data will all be wiped since it'll be repartitioned. If you choose to keep your partition layout at the beginning of the install, your data will be fine.

You could just use this zip as twrp, magisk, verity/fec modifer/installer to save you the extra steps and keep with stock layout
[OnePlus 7 & 7 Pro Cross Device Development] f41lbl0g:
This is super cool. Will be testing soon. Just to confirm, this means I can have a custom rom on one slot and oxygen os on the other? Also f2fs should work fine with common data right?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Yup. You can do whatever you want with either slot. This mod formats all data partitions as ext4 since that's what oneplus does. You can always reformat userdata to f2fs in twrp gui later if you want though. Same goes for common data although I don't think there's a gui option for that
[OnePlus 7 & 7 Pro Cross Device Development] Kris Chen:
How does this zip to allocate the each size of userdata ? Can be customized by ourself or automated by zip itself ?
[OnePlus 7 & 7 Pro Cross Device Development] f41lbl0g:
From what I see it can not be customized through the flasher (may be possible by editing values in the zip). In case you were wondering the size of the partitions, they are 96.7gb for the common storage and 62.4gb each for the individual storages.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
It's automated by installer. If you have a 128gb device:

32gb for each userdata slot, commondata gets what's left

256gb device:

Everything's doubled from above
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
Thank you for this work I have screwed up all of my partitions on my Oneplus and could use a pointer on how to restore all of the correct partitions... :-0

I must have screwed up one of the commands on restoring my original partitions here is what I have now

C:\Users\The Family>adb shell

OnePlus7Pro:/ # sgdisk /dev/block/sda --print

Creating new GPT entries.

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

Logical sector size: 4096 bytes

Disk identifier (GUID): B0281E2A-8376-4F4B-98C6-BF5221AD8A20

Partition table holds up to 128 entries

First usable sector is 6, last usable sector is 61409274

Partitions will be aligned on 256-sector boundaries

Total free space is 61409269 sectors (234.3 GiB)

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

OnePlus7Pro:/ #

What commands do I need to fix this. I can still get into adb shell

edit: msmtool cannot restore from this because the partitions are not correct from the way it looks when I try it. when in recovery touch does not work.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I have the steps outlined here: https://github.com/Zackptg5/TWRP-DualBoot-Guac-Unified/#how-to-manually-repartition-back-to-stock

But what did you do? It looks like you formatted all of /dev/block/sda which is essentially a brick. You are able to restore that with msmtool btw but there will still be some device specific data that is lost and you'll likely need to file warranty claim
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
It was this step that I really messed up

Final step is to format the new userdata partition: mke2fs -t ext4 -b 4096 /dev/block/sda$userdata_num $userdata_size - where userdata_size can be calculated with this shell command: sgdisk /dev/block/sda --print | grep "^ *$userdata_num" | awk '{print $3-$2+1}'

with this step I used the result from sgdisk /dev/block/sda --print | grep "^ *$userdata_num" | awk '{print $3-$2+1}' I do not remember the value into the spot where userdata_size was

It looks like have been able to flash partitions manually in fastboot but the two partitions that are no longer recognized are the system_a and system_b the reason I say that is because vendor and boot flash fine on both a and b partitions. and when I send the commands to flash system a or b the reply is partition not found?! I am not sure if it would fix my problem but if I could get help to restore system partitions maybe I can get this thing to boot up.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
The formatting steps is how I initially bricked my phone when I was figuring this stuff out - I since fixed that issue and made sure it'd never happen again in the zip :/

Why were you manually restoring? Did the zip cut off with partition error?

You'll need to use msmtool in this case. Even if your partition block is completely toast, it's able to bring it all back. You can grab the latest one from here: https://androidfilehost.com/?w=files&flid=296306

And here's the guide for it: https://xdaforums.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
When I run the latest 10.4 global I get "device does not match image" and then under status I loose connection. I have also tried the 10.31 file with no luck either.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
In msmtool? Do you have the right variant?

Latest global: https://androidfilehost.com/?fid=4349826312261732245

Latest europe: https://androidfilehost.com/?fid=4349826312261732244

Download mode is really tricky too. It times out after several seconds so you pretty much have to keep holding down the key combo until msmtool picks it up and then you can release them
[OnePlus 7 & 7 Pro Cross Device Development] eyespunker:
I have now tried the latest two and have come up with the same results on the update when the device param load the result of the last communication is device does not match image.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Sounds like you may need to file a warranty claim then :/
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Why do you flash OOS to both slots first? This is the only difference I see with my flashing procedure, but since i have done several updates before using this mod I assume OOS was in slot B already.

I have OOS on slot A and Havoc OS on slot B.

All works except for the CommonData doesn't show up in Havoc OS. (Same with CrDroid)

I'm on OP7 (not pro) disable force encryption, f2fs and magisk on both slots. CommonData is f2fs too.

I'll try again with flashing OOS first on slot B and then Havoc after that.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
I flashed oos the first time only for all of the other partitions included in the zip
[OnePlus 7 & 7 Pro Cross Device Development] thznutz87:
So what I have found is if common doesn't show in a rom just reflash the installer again and any other files you flash after, ie magisk or kernel patch
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Thanks that worked, but not 100%

After releasing the dual boot zip the DataCommon partition is now the main storage (instead of userdata_b)

With a root explorer any link that normally points to userdata_b, (like /sdcard, /storage/emulated/0, /mnt/user/0/primary) now points to CommonData.

I can find userdata_b with my root explorer only under /data/media/0

But it doesn't show up anywhere without root access.

Edit:This all was on CrDroid.

Now tried with Havoc OS and all is as it should be once i flashed the dual boot zip again after rom setup.

Edit2:

I spoke too soon,

I booted back to slot a Where i have OOS installed and noticed that CommonData now there is the default storage location and the userdata_a is only accessible with root in /data/media/0.

Then I went back to Havoc OS in slot B and there CommonData has disappeared. As is there a folder called commondata in the userdata_b partition but it shows empty. Its not mounted.

And it gets even weirder.

Booting back slot a OOS Now shows commondata empty, but everything that was in commondata is now in my main storage?!?!
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
A screenshot of what filesystems in fx filenames shows.

Looks like commondata is my main storage and somehow also the CommonData partition.

In TWRP everything is as it should be, so the partitions are correct, but the way they get mounted on my system is messed up.

Going to do a clean install of everything.
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Why reflash? Everything looks correct there. Read through the readme on GitHub for how it works

Edit: nevermind, see the problem now. What's your mounts.txt file look like?
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Mounts.txt:

Dcim

Music

The dcim mount didn't work. It just showed an empty second dcim folder on my main data.

Since many things seemed to be messed up on my device I did a clean start. This time with ext4 partitions (not sure if that makes a difference).

I'm setting up oos completely now. Everything is as it should be so far, using the 'all' option in mounts.txt.

Next I will make a backup in twrp and then will setup my second ROM.
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
Here is a screenshot of what it looks like now everything is working as it should. (before mounts.txt was created.)
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
BTW even though the read me says 'lost+found' is excluded from being mounted, when using the 'all' option in mounts.txt it fits get mounted.
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Thinking of trying this myself...my main hangup is the encryption/password issue...it seems like a lot of people have had issues getting this to work properly, and i'm concerned i'm not understanding exactly what you mean. here's what i plan to do based on your instructions and i could use some more clarification. Here's what I plan to do based on your tutorial, please let me know if i'm incorrect anywhere.

1. during initial setup, leave slot a encrypted and slot b unencrypted

2. install a ROM on slot a, boot to system, and setup as normal with a password

3. reboot to twrp (still in slot a), choose common data as storage and backup userdata

4. flash a second ROM (which will automatically install on slot b) then boot to system

5. setup will start for second ROM, setup as normal with a password

6. reboot to twrp (still in slot b) then from there reboot to twrp again (which will switch to slot a)

7. restore backup of userdata

8. enjoy your dual booted phone

is any of that wrong?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Note that it's case sensitive so dcim should be in all caps
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
one more question, in your readme you have one instruction...

Boot into twrp. If sgdisk is not present in sbin, grab it from this zip (in tools) and adb push it to /sbin and chmod +x it

I thought chmod +x didn't work on android...am i missing something?
[OnePlus 7 & 7 Pro Cross Device Development] Zackptg5:
Can't speak for older versions of android but it works for me with this twrp and on regular android (pie+ confirmed)
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Installer seemed to work fine, no errors, but it's giving me an error now, unable to mount datacommon (invalid argument), and i can't install any OS...odd thing is, all of my data and files were still there in sd card, but i get bootloop when i try to reboot system. what do i do?
[OnePlus 7 & 7 Pro Cross Device Development] mjb337:
Can someone give me step by step instructions on mounts.txt' file in /datacommon containing a list of every FOLDER to mount directly over top of sdcard. So for example:

/datacommon/Music -> /sdcard/Music
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
update: I managed to boot into havoc, and then into OOS on the other partition, but when i booted to OOS my SIM cards didn't work...did a factory reset and then reflashed OOS, but then i ran dualboot again and it said there was no OS installed on that slot. tried to boot anyway and got bootloop as expected, tried to go back into havoc and now it's saying unable to mount /system...i'm lost guys...what do i do....
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Ok this is the last time i'm going to ask for help, i promise...I've almost got it, so close....

please [MENTION=6037748]Zackptg5[/MENTION] tell me if i'm doing something wrong here.

I can get each slot to boot one time, but when i set a password for slot b, slot a will no longer boot. it gets stuck at the bootloader unlocked warning.

I flashed OOS and then this recovery to each slot in turn, then flash a custom ROM to one of them, then switch to that slot and reboot system, setting it up as normal.

I reboot to recovery and do a backup of the custom slot (although there is no option for userdata like the tutorial says so i just backup data instead), switch to the OOS slot, then reboot system, setting it up as normal.

I reboot to recovery again, switch to the custom slot, restore the data from the backup i just made, and reboot system...

But it never boots...it just freezes...please....any suggestions would be lovely.

By the way, thank you so very much for the work you put into this, and the time you have spent trying to teach us to use it. i'm sorry i have asked so many questions...please try to help me with this last one...

edit: by doing another restore, this time with boot and data, i was able to boot the ROM, but now i'm getting an invalid password problem, so not really much good.
[OnePlus 7 & 7 Pro Cross Device Development] RenanM1989:
Hello.

I already had this password / pin problem when trying to log in to the other rom. What I noticed, is that when installing the other rom, it is necessary to pay attention to whether the "internal storage" or "common data" is mounted. Depending on which one you are in, you will have a problem.

I don't remember now which one is correct, because I installed the 2 roms a while ago. And if I try to reinstall, and have problems, my banking apps may stop working.

So, if I can give you a suggestion, it would be the following:

Restart twrp in the opposite slot where you want to install the other rom and then mount the "internal storage" option and try to install the rom. After installation, restart to the new rom slot and then restart the system. If after a few minutes, the rom does not boot, restart TWRP, go to the new rom slot, and format the data. And try restarting again.

If it goes wrong, do the same procedure above, but this time, set the "common data" option before installing the new rom.

Hope this helps.

And I'm sorry for my English. I'm from Brazil and I'm using the google translator :)
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Your English is fine, and I very much appreciate the response. I may try that...currently what I am doing is simply not having the second ROM password protected...it gives me no issues this way, but I really don't like it as a permanent solution. Currently it's kinda convenient because that slot is my experimentation slot anyway, so it's nice to not have a password when I'm jumping back and forth and setting up apps on repeat, but when I find something I like and want to stick with i'm gonna want it secured, at least a little. In any case, i'm thinking about trying your tactic, but here's my problem...

I never know if it's not working until I set up the second password, and then it's the other partition that stops working. For example, i'm currently running OOS on slot A as my main. it is set up already, and say i want to install havoc OS on slot B. I can set up the ROM find and boot perfectly and everything seems dandy, but if I set a password at any point, slot A will not boot again...see what I mean? in other words, i would have to set up my main ROM second....so I guess I could wipe everything and start from scratch, doing everything backwards this time...just kind of a pain at this point, i've wiped this phone so many times now already, it might be easier to just wait, surely someone will come up with a better fix... merrrrrr, i'll think about it, but thank you very much for taking the time to reply and share your success...

Just to be certain we're on the same page, let me confim....when you say to mount internal storage/common data, which screen are you referring to? (see attached screenshots) i believe you mean the screen from the first picture, the one where you choose what storage you are accessing in the install screen when you're choosing a ROM to flash (says install zip at the top), but you could be talking about the second one where you actually mount partitions for TWRP to access (says mount at the top) which of these two do you mean?

thanks again sir...much obliged.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
I was thinking about the same and I guess it is the first one where you select the Storage to be shown.
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
yes that's what it sounds like based on the instructions, and plus in the second shot there is really no option for internal storage verbatim, so if i was on who wants to be a millionaire, i'd go with door number A...but then again, he did say he was using google translate, and this is the hardest mod i've ever performed on my phone, so it makes me uncomfortable to make assumptions.

also, if he's right and this fixes it, it seems obvious to me which is the correct choice...if i go into the install screen and click

select storage, it has common data selected by default...i don't remember ever changing this manually, and in fact I couldn't have, at least not once i started flashing ROMS, because common data is where all my rom zips are stored...if i go to internal storage they aren't there (i realize this isn't a problem, i can just move them over before flashing, but it demonstrates my point...with my current configuration/file system, i could not have been flashing from internal storage)...so by this logic, flashing from commondata should be what's causing the problem. and this brings up another interesting thought...

what about using neither of these? i have a type-C/usb-a OTG flash drive i used to use for flashing sometimes...it was super handy when i wanted to **** around with a device away from home or if something went wrong and i needed to flash something and wasn't near a computer...i used to keep stable versions of 4 or 5 ROMS, the latest twrp zip and img, and a few basic tools and apks on it and carry it with me all the time, and it saved my ass more than once...highly recommend, it may have been the best 15 dollars i've ever spent...but i wonder if flashing directly from an OTG instead of internal storage/common data would work, perhaps better? i think i'll give it a go here in a bit, will report back.
[OnePlus 7 & 7 Pro Cross Device Development] Wishmasterflo:
Ohh yes that with USB OTG is a great thing. I am doing that as well a lot of times and have all my needed Flash things and files on a USB Stick.

But as I understand it and tried it once a few weeks ago when I wanted to try out this dualboot I copied all the files to COMMONDATA and flashed from there. Then I had of course this issue after flashing a ROM on the second slot that the passcode on the first slot I flashed was not working anymore.
[OnePlus 7 & 7 Pro Cross Device Development] nbarrett423:
Ok then, that confirms it...maybe not that that's the cause of the problem, but at least that the problem occurred for you while you had commondata selected...SO...

If you assume we are correct that that Mr. Renan was talking about the storage selection screen, AND that his method is a working solution to this problem, selecting internal storage (or perhaps OTG, anything other than commondata) should fix...we'll know soon enough...just doing some overkill backing up right now, i have a bunch of stuff set just right and i really don't feel like retweaking the last 3 days of work, quarantine or no quarantine, so i'm gonna make sure as much of it is saved as possible before i go destroying stuff...
[OnePlus 7 & 7 Pro Cross Device Development] JudgeDread11:
My latest try I made sure I always flashed the dual boot zip from internal storage. And I had no issue with any storage mounting wrong, like I had before. But I also changed changed to ext4, so that might have made a difference as well.

For now I have both slots without a password.

O firsts wanted to have everything setup, before setting any passwords.

I'll update when I feel like trying to set up passwords.