MIUI 13 MIUI 13 STABLE RELEASE


Igor Eisberg

Lead Developer
Staff member
Oct 6, 2016
8,164
322
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.
 
  • Like
Reactions: Zootopia and pejor

pejor

Members
Sep 19, 2022
3
3
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

Lead Developer
Staff member
Oct 6, 2016
8,164
322
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.
 
  • Like
Reactions: pejor

zgfg12

Members
Apr 27, 2021
482
167
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
 
Last edited:

zgfg12

Members
Apr 27, 2021
482
167
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
 
Last edited:

crok.bic

Members
Sep 12, 2017
215
52
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.
 

zgfg12

Members
Apr 27, 2021
482
167
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:
Code:
/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

Members
Sep 12, 2017
215
52
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:
Code:
/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:

Code:
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

Members
May 15, 2022
68
30
Thanks for your reply!
Do you have a joyeuse, too? Because my fstab is really different compared to yours:

Code:
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.
 
Jun 28, 2022
39
20
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?
 
Last edited:

crok.bic

Members
Sep 12, 2017
215
52
mount | grep '/data'
Thanks. userdata is what I should look for?
Code:
/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)
 
Last edited:

zgfg12

Members
Apr 27, 2021
482
167
Thanks for your reply!
Do you have a joyeuse, too? Because my fstab is really different compared to yours:

Code:
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:

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

crok.bic

Members
Sep 12, 2017
215
52
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

Members
Apr 27, 2021
482
167
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
 

crok.bic

Members
Sep 12, 2017
215
52
Maybe, decryption works correctly (it decrypts only if you enter correct pin/pattern) but it just prints an error instead of success
I already answered all these questions here in #5,432

- you don't enter pin/pattern, does OF still decrypts, ie, do you still see correct file names
--> If I don't enter a pin / pattern then internal storage and /data is unreadable (I mean: filenames are gibberish)
- you enter wrong pin/pattern, does OF still decrypts,
ie, do you still see correct file names
--> If enter a wrong pin / pattern then internal storage and /data is unreadable (I mean: filenames are gibberish)

And yes, that's my idea, too, that "it just prints an error instead of success" but without knowing what's the trigger for the error message I won't rely on it (i.e. what if I make a /data backup and I want to use it.. shall I trust the backup or not? Shall I trust the error message or not?). Sorry for being OffTopic but it seems that it does this only with /data encrypted by Xiaomi.EU (and more than likely with Xiaomi factory ROM, too).
 

TuxLin

Members
May 15, 2022
68
30
Thanks. userdata is what I should look for?
Code:
/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)
I think this is OK.
 

TuxLin

Members
May 15, 2022
68
30
I already answered all these questions here in #5,432

- you don't enter pin/pattern, does OF still decrypts, ie, do you still see correct file names
--> If I don't enter a pin / pattern then internal storage and /data is unreadable (I mean: filenames are gibberish)
- you enter wrong pin/pattern, does OF still decrypts,
ie, do you still see correct file names
--> If enter a wrong pin / pattern then internal storage and /data is unreadable (I mean: filenames are gibberish)

And yes, that's my idea, too, that "it just prints an error instead of success" but without knowing what's the trigger for the error message I won't rely on it (i.e. what if I make a /data backup and I want to use it.. shall I trust the backup or not? Shall I trust the error message or not?). Sorry for being OffTopic but it seems that it does this only with /data encrypted by Xiaomi.EU (and more than likely with Xiaomi factory ROM, too).
Instead of making assumptions, one possibility is to make a good copy of your data (outside the device) and install via fastboot the latest stable stock rom release for your device.
Then install xiaomi.eu again (I think xiaomi.eu don't flash /data partition, if it does, then only install latest stable xiaomi.eu via fastboot).
This way, I think you force the device to have all partitions according the last "factory" state.
 

crok.bic

Members
Sep 12, 2017
215
52
Instead of making assumptions, one possibility is to make a good copy of your data (outside the device) and install via fastboot the latest stable stock rom release for your device.
Then install xiaomi.eu again (I think xiaomi.eu don't flash /data partition, if it does, then only install latest stable xiaomi.eu via fastboot).
This way, I think you force the device to have all partitions according the last "factory" state.
I'm thinking about this, too, although this unit in my hands never saw anything else just the factory A10 ROM, upgraded to A11 ROM and then the A11 Xiaomi.EU ROM and now the A12 - so this unit never had any AOSP or LOS based ROM or anything else.
 

Similar threads

Replies
267
Views
247K
Replies
93
Views
47K
Replies
142
Views
45K
Replies
252
Views
83K
Replies
161
Views
55K