MIUI 13 MIUI 13 STABLE RELEASE

[katerpanne]

Read again what I wrote then because I explained it all - I did say everything but let me try it again:
- If I remove the pin or pattern (from the ROM or via formating data) then OFox is not asking for anything (obviously) and I can see all my stuff
- If I set a screenlock pin or pattern in the ROM then OFox asks for pin or pattern and when I input the correct pin or pattern OFox says it is not working BUT if I just tap the back button I can see all my stuff (seemingly decryption did happen even though OFox says "Failed to decrypt user 0", see the screenshot below)
- If I set a screenlock pin or pattern in the ROM then OFox asks for pin or pattern and when I input an incorrect pin or pattern OFox says it is not working (obviously) and if I just tap the back button I don't see my stuff, it's all gibberish (obviously decrypt did not happen).

I really can't describe the situation any better because this is exactly what I experience in OFox with Xiaomi.EU ROM.

It looks NOT to be a ROM but an OFox issue and I wanted to crosscheck with others - probably this is why Joyeuse has only fastboot MIUI 13 ROM and no recovery ROM released as of yet. Guess you have a different phone and you can't crosscheck because I presume you would've already rebooted to OFox to check it.

Here are some screenshots, probably can help you to understand what's going on:
OFox says that storage is encrypted. After I input the correct pattern OFox says FBEv1 decrypt was not successful:

Spoiler: Decrypt did not work.

View attachment 44050

Although as you can see my internal storage is decrypted and you can read the file/dir names.

Spoiler: But still file/dir names are OK - so decrypt did work?!

View attachment 44051

PS: When I input a wrong pin or pattern then everything in internal storage and in /data are gibberish, you can't read proper file/dir names.

TL;DR: When I input a correct pin/pattern then everything in internal storage and in /data are readable but still I receive the very same error message in OFox.

I really-really can't explain it any better........ but a picture says a thousand words, so I hope the screenshots are helping..

i only read the first sentence… it is all working if i remove pin pattern. so there is no challenge

 

[crok.bic]

i only read the first sentence… it is all working if i remove pin pattern. so there is no challenge

That's your problem: "i only read the first sentence" and now I know why you said that I wrote a lot but didn't say anything.
The behavior is not correct, surely not intended and you simply swipe the issue under the carpet with a "workaround".
Still hope someone else can crosscheck for me on a real device, though.

 

[katerpanne]

That's your problem: "i only read the first sentence" and now I know why you said that I wrote a lot but didn't say anything.
The behavior is not correct, surely not intended and you simply swipe the issue under the carpet with a "workaround".
Still hope someone else can crosscheck for me on a real device, though.

good luck

 

[crok.bic]

good luck

I know this was passive-aggressive but thanks anyway

 

[katerpanne]

I know this was passive-aggressive but thanks anyway

i try to help as far as i can… but i dont know where is your challenge…

 

[Igor Eisberg]

Does this mean that "Ok Google" won't work when the screen is off on Chinese phones? Particularly interested whether it will work on Chinese version of Mi 11 Ultra?

Mi 11 Ultra has a Global model, so if you're using our ROM, "OK Google" (Voice Match) should work fine when the screen is off.
What I told him was relevant to Mi 10T Lite (gauguin) which supports Voice Match when the screen is off, while the Chinese model Redmi Note 9 Pro 5G (gauguinpro) does not, due to different codenames.

 

[curi1996]

Hi everyone, if I am in version 12 can i update to 13 by recovery without losing data? In a poco f3, Thanks!

 

[pejor]

Mi 11 Ultra has a Global model, so if you're using our ROM, "OK Google" (Voice Match) should work fine when the screen is off.
What I told him was relevant to Mi 10T Lite (gauguin) which supports Voice Match when the screen is off, while the Chinese model Redmi Note 9 Pro 5G (gauguinpro) does not, due to different codenames.

Thanks for answer. As far as I know Mi 11 Ultra has not only Global model but Chinese model too. So I desperately trying to find out if it be possible to use "OK Google" (Voice Match) when the screen is off with your ROM on Chinese model from Ali...)).

 

[Igor Eisberg]

Thanks for answer. As far as I know Mi 11 Ultra has not only Global model but Chinese model too. So I desperately trying to find out if it be possible to use "OK Google" (Voice Match) when the screen is off with your ROM on Chinese model from Ali...)).

Then I answered your question. Both Chinese and Global models of Mi 11 Ultra are codename star, so Voice Match will work the same.

 

[katerpanne]

Hi everyone, if I am in version 12 can i update to 13 by recovery without losing data? In a poco f3, Thanks!

look here…

[HowTo] Install Recovery image

How to install a xiaomi.eu recovery image Because of more and more working TWRP or OrangeFox on MIUI13 Android12 a little How To and here we go .... Unlock your device (only once) - you need to unlock bootloader -> a small [howto] to unlock bootloader Install Tools and Drivers - install USB...

xiaomi.eu

 

[Breathe of fate]

Hello everyone.
Can I update from 12.5 to 13 via recovery? If so which data I will loose?

So... Sorry for upping this message but I didnt get an answer If I can find info somewhere please give me a link.

 

[zgfg12]

So, you boot to OFox, it asks for a decryption pattern, I input the pattern, it says it doesn't work and after I hit the back button it still drops to the OFox menu and I can browse the files, I can manage backups, I can even go to the app manager in OFox and it sees all my apps, etc, so ___seemingly___ the pattern did work and it was able to decrypt + mount everything but still, there was an error message etc..
When I remove the pattern is doesn't ask for anything, just drops me to the file browser. When I add back the pattern and all my fingerprints it starting this again. Even after formating /data.
Hope this helps to understand the situation.

Make a screenshot and post

For a screenshot in TWRP/OF, press Vol- and Pow in parallel

It should say Successful decryption for User 0 but Failed for User 999 - and that's ok

 

[Breathe of fate]

look here…

[HowTo] Install Recovery image

How to install a xiaomi.eu recovery image Because of more and more working TWRP or OrangeFox on MIUI13 Android12 a little How To and here we go .... Unlock your device (only once) - you need to unlock bootloader -> a small [howto] to unlock bootloader Install Tools and Drivers - install USB...

xiaomi.eu

If I read well:

1. I have Poco F3 and 12.5 stable xiaomi.eu
2. I should install TWRP that supports A12 and I can udate from 12.5 xiaomi.eu to 13 xiaomi.eu iwthout loosing data

Am I right?

 

[zgfg12]

OTA uptades? You mean, is it possible that after installing the latest rom, the next will come like a regular udpate? No need for computer, and twrp? Or did I misunderstand?

Yes, once you will be upgrading from the Recovery type ROM

Upgrade will look like:
Download the latest Xiaom.eu from Updater, read pop-up instructions, accept to reboot (automatically to custom recovery), custom recovery will automatically start to install and will automatically reboot to the system when finished.
As you can see, no need for PC (and fastboot) anymore

That's why Xiaomi.eu pushes Recovery type ROMs, whenever the appropriate custom recovery becomes available

 

[curi1996]

So... Sorry for upping this message but I didnt get an answer If I can find info somewhere please give me a link.

yes i update and i didnt loose data, you can upload

 

[crok.bic]

Make a screenshot and post

Press in parallel Vol- and Pow for screenshot in OF/TWRP

It should say Successful decryption for User 0 but Failed for User 999 - and that's ok

Please read back properly and check post #5432 and see the screenshots under the spoiler tag: it's not the second space (or whatever other) user (999) issue, it says decryption of user 0 was unsuccessful.

 

[jokervero]

12 Pro
After flashing last stable by twrp it reboots again in twrp, anyone can help me ?

 

[zgfg12]

Please read back properly and check post #5432 and see the screenshots under the spoiler tag: it's not the second space (or whatever other) user (999) issue, it says decryption of user 0 was unsuccessful.

Then strange

But the answer to your other question:

Inspect /vendor/etc/fstab.* file (by MiXPlorer with root or copy the file to Download folder by TWRP/OF)

Inside, find the filesystem definition for userdata:

/dev/block/bootdevice/by-name/userdata                  /data                  f2fs    noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier    latemount,wait,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc,checkpoint=fs

(scroll to the right to read...)

In my case, above, it is f2fs with aes-256 encryption

 

[crok.bic]

Then strange

But the answer to your other question:

Inspect /vendor/etc/fstab.* file (by MiXPlorer with root or copy the file to Download folder by TWRP/OF)

Inside, find the filesystem definition for userdata:

/dev/block/bootdevice/by-name/userdata                  /data                  f2fs    noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier    latemount,wait,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc,checkpoint=fs

(scroll to the right to read...)

In my case, above, it is f2fs with aes-256 encryption

Thanks for your reply!
Do you have a joyeuse, too? Because my fstab is really different compared to yours:

joyeuse:/ # grep "/dev/block/bootdevice/by-name/userdata" /vendor/etc/fstab.*
/vendor/etc/fstab.default:/dev/block/bootdevice/by-name/userdata                  /data                    f2fs    noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt    latemount,wait,check,formattable,fileencryption=ice,wrappedkey,quota,reservedsize=128M,checkpoint=fs
/vendor/etc/fstab.emmc:/dev/block/bootdevice/by-name/userdata                  /data                    f2fs    noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt    latemount,wait,check,formattable,fileencryption=ice,wrappedkey,quota,reservedsize=128M,checkpoint=fs

For example even though it is f2fs it has no metadata_encryption specified and fileencryption is ice not aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0 as I see in your output..

 

[TuxLin]

Thanks for your reply!
Do you have a joyeuse, too? Because my fstab is really different compared to yours:

joyeuse:/ # grep "/dev/block/bootdevice/by-name/userdata" /vendor/etc/fstab.*
/vendor/etc/fstab.default:/dev/block/bootdevice/by-name/userdata                  /data                    f2fs    noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt    latemount,wait,check,formattable,fileencryption=ice,wrappedkey,quota,reservedsize=128M,checkpoint=fs
/vendor/etc/fstab.emmc:/dev/block/bootdevice/by-name/userdata                  /data                    f2fs    noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt    latemount,wait,check,formattable,fileencryption=ice,wrappedkey,quota,reservedsize=128M,checkpoint=fs

For example even though it is f2fs it has no metadata_encryption specified and fileencryption is ice not aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0 as I see in your output..

That isn't a problem. If you write:
mount | grep '/data'
you will see the actual mount. ICE becomes the encryption method.

 

[IntegratedGraphics]

WHY every time we want to edit a picture or video the editor needs to be downloaded? i dont even clear my apps cache and this happens all the time. There isn't any way to keep the editor on our phones?

 

[crok.bic]

mount | grep '/data'

Thanks. userdata is what I should look for?

/dev/block/bootdevice/by-name/userdata on /data type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=23056,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/bootdevice/by-name/userdata on /data/user/0 type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=23056,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)

 

[zgfg12]

Thanks for your reply!
Do you have a joyeuse, too? Because my fstab is really different compared to yours:

joyeuse:/ # grep "/dev/block/bootdevice/by-name/userdata" /vendor/etc/fstab.*
/vendor/etc/fstab.default:/dev/block/bootdevice/by-name/userdata                  /data                    f2fs    noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt    latemount,wait,check,formattable,fileencryption=ice,wrappedkey,quota,reservedsize=128M,checkpoint=fs
/vendor/etc/fstab.emmc:/dev/block/bootdevice/by-name/userdata                  /data                    f2fs    noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt    latemount,wait,check,formattable,fileencryption=ice,wrappedkey,quota,reservedsize=128M,checkpoint=fs

For example even though it is f2fs it has no metadata_encryption specified and fileencryption is ice not aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0 as I see in your output..

I have Lisa (device was originally launched with A11)

You can read the official FBE documentation:

File-based encryption | Android Open Source Project

source.android.com

Seems that your device was originally launched with A10 (or lower) - search in the document for:
fileencryption=ice

 

[crok.bic]

Seems that your device was originally launched with A10 (or lower) - search in the document for:
fileencryption=ice

Indeed, joyeuse been released running Android 10 originally. It's clear that it's FBEv1 but not clear how && why now, running on A12 MIUI 13 OFox runs to an error even though decrypt by OFox seems to work anyway..

 

[zgfg12]

Indeed, joyeuse been released running Android 10 originally. It's clear that it's FBEv1 but not clear how && why now, running on A12 MIUI 13 OFox runs to an error even though decrypt by OFox seems to work anyway..

Strange but have you tested scenarios like:

- you don't enter pin/pattern, does OF still decrypts, ie, do you still see correct file names

- you enter wrong pin/pattern, does OF still decrypts,
ie, do you still see correct file names

Maybe, decryption works correctly (it decrypts only if you enter correct pin/pattern) but it just prints an error instead of success