MIUI 14 MIUI 14 STABLE RELEASE


Status
Not open for further replies.
cartwheelbob said:
Exactly the same with me also
Click to expand...
Ref the CTS mismatch the only way to resolve this was having to root it and install the safety net fix via KernelSU or Magisk. Couldn't install all of the apps I need to use day to day otherwise.

I'm using Kernel SU as you can simply install the APK to check it's compatible, then download and install the anykernel zip file via TWRP that corresponds to the kernel the ROM is using (5.15.74 at time of writing for the latest Xiaomi EU stable ROM and the Xiaomi 13 Ultra) then via the KernelSU or Mrepo apps install zygisk on kernelsu module, safetynet fix module which for me was the 2.4.0 mod 1.3 (2.0 version or the playingegrity 8.5/8.6 didn't work...edit 8.8 is out now so might be working now as of writing).

Also added Shamiko, zygisk lsposed and installed Hidemyapplist APK as I use Lloyds Banking group apps which are a challenge with root detection. Avoids root detection very well for KernelSu Vs Magisk. Created a blacklist template with all the apps to hide and then applied to the banking apps and any root checker tools.

KernelSU need care around applying future OTA updates etc and will need to make sure the anykernel is applied to match any kernel change in the ROM etc so you might find Magisk easier to maintain and use. Magisk stable version didn't work for me with the banking apps though Alpha version did, issue there was zygisk needs to be disabled I think so safetynet was still an issue for me.

Didn't try Delta as I think it also needs zygisk disabled though might be wrong and went the KernelSU route. If I have to end up rooting the device KernelSU gives me a fair bit of control via app profiles and unloading modules on a per app basis without them having superuser access if apps start misbehaving such as Roon remote did. Either way would recommend you know what you're doing with whichever method chosen.

It doesn't pass safetynet check and is not certified pure and simple despite the statement otherwise for the ROM, albeit the Devs response is the CN Mi13 ultra devices they have work fine and they don't get this error whilst multiple users report otherwise.

Have the 16GB/1TB model.
 
Last edited:
  • Like
Reactions: Sangreal, katerpanne and Silvio1953
Successfully installed MIUI 14.0.4.0 on Mi 10 pro. I actually got better network stability (sometimes my phone lost signal with no obvious reason, this is now resolved). Thanks a lot, especially to Igor Eisberg for downgrading the package installer !
 
Hello I am currently running v12.5.20 on Xiaomi Mi 11 Ultra (star).
What wipes do I need for a clean install? I already have twrp.
Thanks
 
Only "Format Data", don't delete anything else.
 

Attachments

  • Format_Data.png
    Format_Data.png
    79.3 KB · Views: 179
  • Like
Reactions: katerpanne and haveumetrob
Sangreal said:
Ref the CTS mismatch the only way to resolve this was having to root it and install the safety net fix via KernelSU or Magisk. Couldn't install all of the apps I need to use day to day otherwise.

I'm using Kernel SU as you can simply install the APK to check it's compatible, then download and install the anykernel zip file via TWRP that corresponds to the kernel the ROM is using (5.15.74 at time of writing for the latest Xiaomi EU stable ROM) then via the KernelSU or Mrepo apps install zygisk on kernelsu module, safetynet fix module which for me was the 2.4.0 mod 1.3 (2.0 version or the playingegrity 8.5/8.6 didn't work...edit 8.8 is out now so might be working now as of writing).

Also added Shamiko, zygisk lsposed and installed Hidemyapplist APK as I use Lloyds Banking group apps which are a challenge with root detection. Avoids root detection very well for KernelSu Vs Magisk. Created a blacklist template with all the apps to hide and then applied to the banking apps and any root checker tools.

KernelSU need care around applying future OTA updates etc and will need to make sure the anykernel is applied to match any kernel change in the ROM etc so you might find Magisk easier to maintain and use. Magisk stable version didn't work for me with the banking apps though Alpha version did, issue there was zygisk needs to be disabled I think so safetynet was still an issue for me.

Didn't try Delta as I think it also needs zygisk disabled though might be wrong and went the KernelSU route. If I have to end up rooting the device KernelSU gives me a fair bit of control via app profiles and unloading modules on a per app basis without them having superuser access if apps start misbehaving such as Roon remote did. Either way would recommend you know what you're doing with whichever method chosen.

It doesn't pass safetynet check and is not certified pure and simple despite the statement otherwise for the ROM, albeit the Devs response is the CN Mi13 ultra devices they have work fine and they don't get this error whilst multiple users report otherwise.

Have the 16GB/1TB model.
Click to expand...
For which device you found KernelSU compatible with Xiaomi.eu 14?
 
haveumetrob said:
For some reason I can't uncrypt data
I even tried disabling face unlock, set up a password instead of a pin, but I am stuck and can't wipe data

How to fix this?
Click to expand...
Did you recently install this ROM first time - you had to Format Data (not Wipe, but Format)

Or maybe you did something by TWRP that deleted the FBE (File Base Encryption) keys - or something else affected them

You will have to Format Data from TWRP
 
haveumetrob said:
Do I need to flash magisk for root again?
Click to expand...
If Boot was patched by Magisk, Magisk would recreate itself on reboot (maybe on the second reboot, on first reboot Android must set up itself). Formatting Data does not affect Boot partition (Magisk patch) but it deletes Magisk setup at /data/adb

But you would need to install all apps again, including the Magisk app (and all modules)
 
haveumetrob said:
This is what twrp shows when I click on format data
View attachment 48970
Click to expand...
You can try this 4 possibilities:

- in TWRP click on "Mount" and then "Decrypt Data" insert your PIN and check if the Data is decrypted and try again to format
- in TWRP click on "Advanced" and then "File Manager" search for "data/system" and delete the file "locksettings.db" reboot to recovery and try again to format
- use MiFlash to install original ROM and install all from Scratch
- try to use fastboot with the format-script
 
Last edited:
IMG_20231005_100927.jpg


Update: I solved the decryption (I'm not sure, though) rebooting to system and removing every face/fingerprint data + activating usb debugging and oem unlocking on developer options. Problem is I am still stuck with this
 
Last edited:
katerpanne said:
You can try this 4 possibilities:

- in TWRP click on "Mount" and then "Decrypt Data" insert your PIN and check if the Data is decrypted and try again to format
- in TWRP click on "Advanced" and then "File Manager" search for "data/system" and delete the file "locksettings.db" reboot to recovery and try again to format
- use MiFlash to install original ROM and install all from Scratch
- try to use fastboot with the format-script
Click to expand...
I followed your instructions, but it keeps asking for a password I don't have, since I removed every kind of lock on my phone, when trying to decrypt data via "mount" menu.

I can't find locksettings.db on data/system:
IMG_20231005_102153.jpg
 
Last edited:
haveumetrob said:
I followed your instructions, but it keeps asking for a password I don't have, since I removed every kind of lock on my phone, when trying to decrypt data via "mount" menu.

I can't find locksettings.db on data/system:
Click to expand...
you cantfind it coz it is not decrypted. try to set a PIN - 4 digits and try this again
- in TWRP click on "Mount" and then "Decrypt Data" insert your PIN and check if the Data is decrypted and try again to format
 
katerpanne said:
you cantfind it coz it is not decrypted. try to set a PIN - 4 digits and try this again
- in TWRP click on "Mount" and then "Decrypt Data" insert your PIN and check if the Data is decrypted and try again to format
Click to expand...
New pin set, but still not working
IMG_20231005_103500.jpg


Edit: I somehow managed to get access to data/system and deleted locksettings.db, but after reboot to recovery I still can't format data since twrp is asking for a password
 
Last edited:
Status
Not open for further replies.

Similar threads

ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
245K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
41K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
36K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
38K
HyperOS
KGVER
KGVER
ingbrzy
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
32K
HyperOS
emre_66
E
Top Bottom
Back