MIUI 13 MIUI 13 STABLE RELEASE


Status
Not open for further replies.
snoopera said:
do not tested for long as i was on 98% battery , but works for a couple of mins no issues, used non-original slow wireless charger 10/15w , tmrw will test full charge if everything is working correctly for ~30-40% till full and will report back
Click to expand...
Any update on wireless charging?
 
Blitzz said:
volume recovery_a is full.
Need to "fastboot boot recovery.img"
I'm glad decryption works
Click to expand...
For me also only this method work. After this i go in TWRP to Properties and then to Install current TWRP. Then TWRP was installed. After that i could install the Xiaomi.eu Rom.

This Things with TWRP are really very tricky. That was the reason, i used for my last two Xiaomi devices Xiaomi.eu anymore. And i also know other Users that do not like this TWRP Methods and use Xiaomi.eu anymore.

The Fastboot Method with the Scirpts was really comfortable. Why do switch back to this TWRP Method? In the Forum many Users have problems with TWRP.
 
Hello Xiaomi.eu
I've booted my Mi 11 Ultra successfully into TWRP and it's already on the previous Xiaomi.eu version but the internal storage show 0kb and can't mount data or anything else! any solution?
Best regards
 
Last edited:
  • Like
Reactions: Vampiro, Jackob and gogocar62
  • Like
Reactions: dailylovely, Vampiro, Jackob and 1 other person
bravonova said:
@ingbrzy Which encryption type does Android 12 based Xiaomi.eu ROM use? FBEv1 or FBEv2?
Click to expand...
For the phones originally deployed with A11 and higher, FBE by default should be v2

Google documentation describing FBE:

File-based encryption | Android Open Source Project

source.android.com source.android.com

With root, open /vendor/etc/fstab.emmc (read-only, textual file) - on your phone it might be fstab.<something-else-than-emmc>

Alternatively, with TWRP copy that file to /sdcard/Download and later from Android open without the need for root

Inside, that file search for /userdata (filesystem definition):
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

Actually, inside that line look for fileencryption definition:
Code: 
fileencryption=aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0

Eg, flag :v2 as above, describes that you would have FBE v2.
Here it is also emmc_optimized with hardware-wrapped keys

IMO - FBE (all together, filesystem definitions) is not up to Xiaomi.eu, but defined by the baseline Xiaomi firmwares
 

Attachments

  • IMG_20220810_182916.jpg
    IMG_20220810_182916.jpg
    361.2 KB · Views: 336
Last edited:
  • Like
Reactions: fouras, sveip, Vampiro and 4 others
Having miui 12 and a11 on a mi 11 ultra what i need to do first to update to miui 13?
First update TWRP via fastboot and making the Install Recovery Ramdisk?
Or i can just enter fastboot boot twrp.img (the a12 one) and flash the rom update?
Thank you. I am a bit lost sorry.

(Having xiaomi.eu rom stable now but v12)
 
  • Like
Reactions: JakSpoon
I'm also very interested in the changelog.
Espevially Changes from 13.0.8 to 13.0.9
Simeone got a Link or Something?
 
  • Haha
  • Like
Reactions: renegade2k, Vampiro and katerpanne
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
733
Views
344K
HyperOS
niebla
niebla
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
332K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
44K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
44K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
53K
HyperOS
KGVER
KGVER
Top Bottom
Back