Miui 13 (with A12)


Patamsis

Members
Sep 18, 2022
1
3
Hi,

I'm writing to share my experience with latest update (V13.0.1.0.SJZMIX). I was a bit hesitant to upgrade, because this one is done differently (fastboot).

My model is: Note 9 Pro Global. And I was on latest stable OrangeFox Recovery.

I updated from latest MIUI12 (V12.5.7.0.RJZMIXM_v12-11) to MIUI13 (V13.0.1.0.SJZMIXM_v13-12-fastboot).

I Followed the instructions from release page and I did NOT format data. After install the phone booted longer than after previous updates. I would say almost 10 minutes.
I tried to install "OrangeFox-miatoll-beta@R11.1_3_3_A12_FBEv2" using the OrageFox app before and after the upgrade. I'm not sure that it actually did install it, because the app still suggest to to upgrade to latest beta, however when I boot to recovery it show version R11.1_3_3. (I tried to install it directly from recovery with the same results).
Furthermore, when I tried to install anything using that recovery I see the message "error making /sdcard/fox directory required key not available", however I don't think it actually influances anything, because I (re)installed Magisk23 (I know I'm using older version) and everything works. I have root access and phone passes SafetyNet (BASIC) check.

After upgrade I noticed that Alex Call Recorder was gone and I had to reinstall it.
This release fixes one bug that actually made me try to upgrade - now it's possible to change bluetooth keyboards layout. Previous versions had a bug that whatever I did the change would not stick. It might show that keyboard layout is not in english, however it would still type only in english.

So, all in all, I would say upgrade went without any issues and it finally fixed a bug that was in MIUI at least for past few releases (3-4 maybe more).
And I just an hour or so after the upgrade and I did not have a lot of time to test it, but everything that is necessary for me - works
 

crok.bic

Members
Sep 12, 2017
195
40
I tried to install "OrangeFox-miatoll-beta@R11.1_3_3_A12_FBEv2"
OrangeFox stable R11.1_3 Android 12 FBEv1 just been released a few hours ago:
OrangeFox-miatoll-stable@R11.1_3_A12_FBEv1.zip
Support for FBEv1 Android 12 and Android 13 decryption only
Allow MIUI 13 to persist after flashing
Update the Magisk addon to v25.2
Update to the latest upstream commits
Remove obsolete addons
Lots of other enhancements

Interestingly it did not solve the /data decryption thing. I'm about to format /data and try it again.. what's the file system of /data on your phone at the moment? EXT4 or F2FS? Mine is F2FS.

[Edit:] I formated data.. same thing.. when OrangeFox is trying to decrypt my /data for my user with the 100% right pattern it says it can't decrypt user and in the same time I'm able to browse /data (no gibberish filenames/dirnames anywhere) and I can do whatever I want with the internal storage (mounting and everything is working, no gibberish filenames/dirnames anywhere). The OFox response on this matter was "it's a ROM issue".. which would be strange knowing that under Android 11 it did work perfectly. Any thoughts or ideas? Thanks!
 
Last edited:

sir_bazz

Members
Jun 18, 2020
138
40
OrangeFox stable R11.1_3 Android 12 FBEv1 just been released a few hours ago:
OrangeFox-miatoll-stable@R11.1_3_A12_FBEv1.zip
Support for FBEv1 Android 12 and Android 13 decryption only
Allow MIUI 13 to persist after flashing
Update the Magisk addon to v25.2
Update to the latest upstream commits
Remove obsolete addons
Lots of other enhancements

Interestingly it did not solve the /data decryption thing. I'm about to format /data and try it again.. what's the file system of /data on your phone at the moment? EXT4 or F2FS? Mine is F2FS.

[Edit:] I formated data.. same thing.. when OrangeFox is trying to decrypt my /data for my user with the 100% right pattern it says it can't decrypt user and in the same time I'm able to browse /data (no gibberish filenames/dirnames anywhere) and I can do whatever I want with the internal storage (mounting and everything is working, no gibberish filenames/dirnames anywhere). The OFox response on this matter was "it's a ROM issue".. which would be strange knowing that under Android 11 it did work perfectly. Any thoughts or ideas? Thanks!
What's the full error msg form Orangefox?

I had this a long time back but it was for user 99, (I think), which is what miui uses for second space.
 

crok.bic

Members
Sep 12, 2017
195
40
What's the full error msg form Orangefox?

I had this a long time back but it was for user 99, (I think), which is what miui uses for second space.
You can check it in the screenshots [here] (under the spoiler tag):

Failed to decrypt user 0.

So this is not the infamous "second space created user's issue (user 999)" unfortunately..
 
  • Like
Reactions: sir_bazz

crok.bic

Members
Sep 12, 2017
195
40
I see.

I haven't updated to A12 yet, but doesn't it use fbev2?
No, it's FBEv1 - since joyeuse has been released originally with A10 and one can't change it from FBEv1 to FBEv2 with OTA so the official ROM and thus the Xiaomi.EU ROM is also using FBEv1. The problem is that even though I input the correct pattern and I see correct filenames / dirnames the OFox still throws an error message, most probably falsely..
 

sir_bazz

Members
Jun 18, 2020
138
40
No, it's FBEv1 - since joyeuse has been released originally with A10 and one can't change it from FBEv1 to FBEv2 with OTA so the official ROM and thus the Xiaomi.EU ROM is also using FBEv1. The problem is that even though I input the correct pattern and I see correct filenames / dirnames the OFox still throws an error message, most probably falsely..
Yeah the issue is clear but the fix is not so clear. At least it sounds like all the functionality is there though.

I've been resisting the upgrade for not wanting to run into little issues like this one. Do you know if the fastboot rom, (using install rather than update), uses fbev1 or fbev2?
The install.bat typically does a format so could be using fbev2.
 

crok.bic

Members
Sep 12, 2017
195
40
Yeah the issue is clear but the fix is not so clear. At least it sounds like all the functionality is there though.

I've been resisting the upgrade for not wanting to run into little issues like this one. Do you know if the fastboot rom, (using install rather than update), uses fbev1 or fbev2?
The install.bat typically does a format so could be using fbev2.
I quote myself "since joyeuse has been released originally with A10 and one can't change it from FBEv1 to FBEv2 with OTA so the official ROM and thus the Xiaomi.EU ROM is also using FBEv1" so the ROM is FBEv1. If you format /data the ROM will encrypt it with FBEv1 - if you think about it: if people are upgrading.. and the ROM would've change from FBEv1 to v2 then those guys would softbrick their units.
 

sir_bazz

Members
Jun 18, 2020
138
40
I quote myself "since joyeuse has been released originally with A10 and one can't change it from FBEv1 to FBEv2 with OTA so the official ROM and thus the Xiaomi.EU ROM is also using FBEv1" so the ROM is FBEv1. If you format /data the ROM will encrypt it with FBEv1 - if you think about it: if people are upgrading.. and the ROM would've change from FBEv1 to v2 then those guys would softbrick their units.
Yeah I get the upgrading part.
But if you use the install.bat from the fastboot rom, it's a clean install as opposed to an upgrade. So no issue of soft bricking there.
The upgrade process would be no different to switching to one of our other custom ROMs that already utilise fbev2.

But I'm getting off topic, so will leave it there.
 

crok.bic

Members
Sep 12, 2017
195
40
Yeah I get the upgrading part.
But if you use the install.bat from the fastboot rom, it's a clean install as opposed to an upgrade. So no issue of soft bricking there.
The upgrade process would be no different to switching to one of our other custom ROMs that already utilise fbev2.

But I'm getting off topic, so will leave it there.
That has nothing to do with the original question / situation. OFox has a separate build for ROMs using FBEv1 and FBEv2, this is the root cause. Of course moving to a custom ROM with FBEv2 after a format is not a problem, but you can't "upgrade" a ROM that used FBEv1 to use FBEv2 wituout formating.
 

sir_bazz

Members
Jun 18, 2020
138
40
That has nothing to do with the original question / situation. OFox has a separate build for ROMs using FBEv1 and FBEv2, this is the root cause. Of course moving to a custom ROM with FBEv2 after a format is not a problem, but you can't "upgrade" a ROM that used FBEv1 to use FBEv2 wituout formating.
The test that I would do though, (and I may because I haven't upgraded yet), would be to check the behaviour of OrangeFox after a clean install, (via the fastboot rom), using the update.bat.
 

crok.bic

Members
Sep 12, 2017
195
40
The test that I would do though, (and I may because I haven't upgraded yet), would be to check the behaviour of OrangeFox after a clean install, (via the fastboot rom), using the update.bat.
I can save you some time and labour, I'm already done with this -> same OFox issue and -of course- it is still FBEv1, I documented it here. Please read my posts there back and forth for some pages.
 
  • Like
Reactions: sir_bazz