MIUI 13 MIUI 13 STABLE RELEASE


Status
Not open for further replies.
crok.bic said:
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..
Click to expand...
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
 
zgfg12 said:
Maybe, decryption works correctly (it decrypts only if you enter correct pin/pattern) but it just prints an error instead of success
Click to expand...
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).
 
crok.bic said:
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)
Click to expand...
I think this is OK.
 
crok.bic said:
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).
Click to expand...
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.
 
TuxLin said:
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.
Click to expand...
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.
 
crok.bic said:
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.
Click to expand...
Nah.. same issue.. I flashed the factory MIUI V13 via fastboot then reflashed Xiaomi.EU V13.0.1.0 and.. same issue with OFox.. I'm about to give up.. or somehow read through the whole source of OFox.. or I don't know.. :/
 
crok.bic said:
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).
Click to expand...
Cannot help you further. You could try to contact OF developers and report

But IMO, if you carefully enter pin/pattern and you see the file names decrypted, you can trust that it's only a bogus error printed

I use (also) OF on Lisa but only for updating Xiaomi.eu (I'm on Weeklies). I install Magisk by patching and flashing the boot img

For backup/restore I don't use OF (custom recovery). System (with Vendor, Product, etc) is read-only and you can always reflash

I manually transfer pictures and so from Internal mem to PC

For apps, I use Swift Backup (root) app (from Playstore) - you can backup/restore app by app (practical, if I update an app but don't like the update). I also use Google and Mi Cloud

Btw, if you install dual apps (like dual WA) or you create Second space, then OF (for me) fails to backup Data (bcs of not supporting user 999 decryption)

Hence I don't do (nandroid) backups in custom recovery
 
  • Like
Reactions: crok.bic
Just download the new 13.0.10.0 but fails. Why?

Screenshot_2022-09-20-15-10-37-161-edit_com.google.android.apps.photos.jpg
 
can I install this without unlocking bootloader and twrp? since it can be installed thru fastboot? my phone is poco x4 pro 5g. thanks!
 
blitzlee07 said:
can I install this without unlocking bootloader and twrp? since it can be installed thru fastboot? my phone is poco x4 pro 5g. thanks!
Click to expand...
no… custom rom needs unlocked bootloader
xiaomi.eu

[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 xiaomi.eu
 
  • Like
Reactions: blitzlee07
blitzlee07 said:
can I install this without unlocking bootloader and twrp? since it can be installed thru fastboot? my phone is poco x4 pro 5g. thanks!
Click to expand...
For Fastboot installation obviously TWRP is not needed

But how do you think to flash in Fastboot if your Bootloader is locked?

Fastboot flash ... is blocked for the locked Bootloader.
Not only for flashing Xiaomi.eu ROM, not only for Bootloader/Fastboot on Xiaomi devices - but generally for Android

With the locked Bootloader you can only stay on your stock firmware and keep getting OTA updates.
To flash anything else - even if your stock is eg China and you want to switch to official Global, you have to unlock Bootloader to be able to flash in Fastboot
 
  • Like
Reactions: blitzlee07
is there any way to download this rom for fastboot version for the poco f3? I can't install twrp. it always gives me the error: FAILED (remote: '(recovery_a) No such partition')
 
Have you entered your lock screen password/PIN/pattern in TWRP?
Did you use the current TWRP (download and unzip the zip file) ?
 
I have a question. I have installed TRWP om my MI 11 Ultra. I did a wipe. Then I wanted to dowload the new rom on my phone. The phone showed on my computer with no maps on it, it was blanc. I couldn't download the rom on my phone. So I did a fastboot downloaded the recovery rom in the downloadfolder and I installed the new updated rom. Everything works fine. I don't understand why I can't downlod the zip file of the recovery rom on my phone after a wipe. I followed the trwp tutorial on Trading Shenzhen.
 
I'm downgrading back to 13.0.8 because 13.0.9 got a ****** camera focus. I tried to go to pro mode and set the focal to infinity and it cannot so i can only focus to things less than 1m
 
Hum okay guys I tried on 2 different pc with 2 different cables andy phone is no more recognized while in fastboot. Using comment fastboot devices and it is not found and the fastboot update is on "waiting for devices". What can I do?
 
Do you have the necessary drivers on your PC?
xiaomi.eu

Problems with updating

Hello I just received a Xiaomi Mi 11 ultra Chn model with EU firmware installed. It's on version 12.5.3 and the build in updater just downloaded version 12.5.7. When I try to install it, I get to the point where I have confirm that I want reboot into Recovery mode. But nothing happens, the...
xiaomi.eu xiaomi.eu
xiaomifirmware.com

[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools

Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com xiaomifirmware.com
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
960
Views
401K
HyperOS
vthnlk
V
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
342K
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
45K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
54K
HyperOS
KGVER
KGVER
Top Bottom
Back