MIUI 14 MIUI 14 STABLE RELEASE


Status
Not open for further replies.
New pin set, but still not working


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
ok so one step after the other ...
- reboot to twrp and delete the "data/system/locksettings.db"
- start the system and set a PIN - 4 digits
- reboot to recovery / TWRP
- if it is asking for a PIN -> insert the 4-digits
- in TWRP click on "Mount" and then "Decrypt Data" insert your PIN and check if the Data is decrypted and try again to format

If all this will not work:
- use MiFlash to install original ROM and install all from Scratch
- try to use fastboot to install xiaomi.eu rom with windows_fastboot_first_install_with_data_format.bat

 
- try to use fastboot to install xiaomi.eu rom with windows_fastboot_first_install_with_data_format.bat

Do you mean I need to install official MIUI 14 and then xiaomi.eu rom with .bat?
I tried to directly install latest xiaomi.eu rom with this step, but I still have the encryption issue with TWRP. It keeps saying "Unable to mount storage" :emoji_sob:
 
Is your device Xiaomi 11 Pro/Ultra (star)? Looks like you are using the wrong TWRP.
According to the pictures you showed, it looks like you are using the TWRP for a lower version of android.
Install the current TWRP for that device and android version.

TWRP designed for STAR/Android 13
 
Last edited:
Xiaomi 13 Ultra, anykernel version matching 14.0.19.0 TMACNXM ROM for ishtar - 5.15.74
Unfortunately, KernelSU is not compatible with the Xiaomi.eu (14.0.12) Stable.on Lisa - screenshot

Actually, I've tried already months ago, so I asked you about you (hoping that maybe KSU now supports a border range of kernels), but it still complains that QKI kernel is not supported (probably you have GKI kernel on your device)
 

Attachments

  • Screenshot_2023-10-05-23-38-49-442_me.weishu.kernelsu.jpg
    Screenshot_2023-10-05-23-38-49-442_me.weishu.kernelsu.jpg
    302.1 KB · Views: 153
There's something wrong with the encryption on TWRP that I don't know about. This happened in RedmiNote7 (Lavender). And I had to switch to OrangeFox without encountering any passwords. But I'm not sure OrangeFox is available for your phone model. And I'm not sure if OrangeFox is really more secure than TWRP. But it's worth a try if OrangeFox is available for your phone model.
 
  • Like
Reactions: katerpanne
Hello
I managed to fix the initial issues and to install the latest rom, but I am facing two major issues/bugs now:
1. Messages by Google app is not reading my SMSes, even though Xiaomi Messaging app is
2. The UI for some reason loses gestures and forces me to use buttons

Has anyone faced this before? How to fix these issues?
 
Hello
I managed to fix the initial issues and to install the latest rom, but I am facing two major issues/bugs now:
1. Messages by Google app is not reading my SMSes, even though Xiaomi Messaging app is
2. The UI for some reason loses gestures and forces me to use buttons

Has anyone faced this before? How to fix these issues?

1. You must set up default SMS app to Google Messages.
2. Go to option and enable Gesture.
 

haveumetrob

- clear the all data of the Messages app
- do not launch the application!
- go to permissions and enable everything
- set app as default
- run the app and follow the instructions in it.
 
Hello
I managed to fix the initial issues and to install the latest rom, but I am facing two major issues/bugs now:
1. Messages by Google app is not reading my SMSes, even though Xiaomi Messaging app is
2. The UI for some reason loses gestures and forces me to use buttons

Has anyone faced this before? How to fix these issues?
Native Settings, Apps, Manage apps, search for your messaging app and open.
Scroll down to Permissions, open, find Read SMS and MMS and give it Always allow - as on the screenshot (not from your app but that's the general way how to deal with 'problems' like yours)

Or long press to your app's icon, and open App info. That's the faster way than navigating through Settings, Apps, etc
 

Attachments

  • Screenshot_2023-10-07-00-35-41-019_com.miui.securitycenter-edit.jpg
    Screenshot_2023-10-07-00-35-41-019_com.miui.securitycenter-edit.jpg
    131.8 KB · Views: 179
  • Like
Reactions: haveumetrob
I'm downgrading from weekly to stable since no more updates are available for mi 11 ultra, can someone provide me the steps to save, delete and restore all my data as well as installing from weekly to stable. I need a step by step procedure to keep all my data as it is i.e. keep same phone settings, wallpaper, homescreen, etc. Any replies are much appreciated. Tks
 
Thanks for the information.
However, this is not the same.
MIUI > Third Party Launcher = Gestures don't work at all
My Pixel / A13 > NOVA Launcher = gestures work fine. :emoji_thinking:
 
Last edited:
Solved
Thank you

What about the gestures issue?
OK Google still works.
I'm not too sure about the whole Gesture or programming code thing. According to my usage experience. I noticed gestures have 2 levels. And I confirm that both this level 2 still works fine on 3rd party Launcher called "Computer Launcher Pro". You just need to download the free version on GoogleStore. And currently I am still using the device RedmiNote12 8Gb Non-NFC Global Official Rom 14.0.14 (Android 13).
On my RedmiNote7(Lavender) device with MIUIEU 12.5 it works fine.
- 1 level of systematic gestures (Android system in general, e.g. swipe to return, swipe to go to Home...)
- 1 level of gestures on the application. (In this case perhaps developers can develop more advanced gestures in their applications). For example, a third-party application is Computer Launcher Pro. Or Google's Message still has a swipe left gesture to delete messages or customize message storage...)
 
I can confirm my gestures are somehow bugged
My device keeps losing them and forces me to change to button - > gestures again from settings
 

KHPKero

It seems like some very useful information might be here if I could be sure exactly. Just to be clear:

A) It it safer for Android 11 & 12 (& maybe 13 +) to avoid using TWRP to flash Rom except for updates?
B) Or is it wiser to avoid dirty flash Rom upgrades (major updates between Android/Miui versions?
C) But Fastboot dirty flash, as long as it is same Rom (e.g xiaomi.eu) is safe?

I am considering flashing both lisa & topaz twrp which both have unofficial versions (12). I gather xiaomi-eu rom installs twrp automatically & maybe even patches the boot.img for magisk. But whereas I thought I knew roughly what I am doing, now I am no longer sure at all!

If anyone can improve my understanding, thanks in advance
 
It seems like some very useful information might be here if I could be sure exactly. Just to be clear:

A) It it safer for Android 11 & 12 (& maybe 13 +) to avoid using TWRP to flash Rom except for updates?
B) Or is it wiser to avoid dirty flash Rom upgrades (major updates between Android/Miui versions?
C) But Fastboot dirty flash, as long as it is same Rom (e.g xiaomi.eu) is safe?

I am considering flashing both lisa & topaz twrp which both have unofficial versions (12). I gather xiaomi-eu rom installs twrp automatically & maybe even patches the boot.img for magisk. But whereas I thought I knew roughly what I am doing, now I am no longer sure at all!

If anyone can improve my understanding, thanks in advance
Flashing FastBoot is quite safe and does not require TWRP. Just make sure of the following:
1. Unlock Bootloader (If possible, enable USB Debug in case you get disconnected in bad situations)
2. Activation allows OEM to unlock Bootloader
3. Turn off your phone, hold down the Volume key (-) and the Power key for about 3 seconds to enter Fastboot mode.
4. Connect the cable to the computer.
5. You may temporarily turn off anti-virus programs to avoid them interfering with the Flash process. (although this hasn't happened to me yet on Windows 11 Lastest version with Windows Security lastest)
6. Extract your RoomFlash then run the command.
7. Wait until your phone restarts (During this process, it is a good idea that you should not open any applications on your computer to avoid the risk of applications accidentally interfering with the process. Flash program...)

And that's all.

I made this on Topas.

There is one thing I haven't tried yet but I have seen some information people say that after Flashing FastBoot MIUIEU ROM. TWRP will automatically install on your device. Please confirm this for yourself.
 
Flashing FastBoot is quite safe and does not require TWRP. Just make sure of the following:
1. Unlock Bootloader (If possible, enable USB Debug in case you get disconnected in bad situations)
2. Activation allows OEM to unlock Bootloader
3. Turn off your phone, hold down the Volume key (-) and the Power key for about 3 seconds to enter Fastboot mode.
4. Connect the cable to the computer.
5. You may temporarily turn off anti-virus programs to avoid them interfering with the Flash process. (although this hasn't happened to me yet on Windows 11 Lastest version with Windows Security lastest)
6. Extract your RoomFlash then run the command.
7. Wait until your phone restarts (During this process, it is a good idea that you should not open any applications on your computer to avoid the risk of applications accidentally interfering with the process. Flash program...)

And that's all.

I made this on Topas.

There is one thing I haven't tried yet but I have seen some information people say that after Flashing FastBoot MIUIEU ROM. TWRP will automatically install on your device. Please confirm this for yourself.
Thanks for the reply.

I am reasonably comfortable with Fastboot. I know it is safe with Android 11+. What I am unsure about is whether TWRP now works safely with recent Android versions. Topaz for example.
 
Nova launcher works fine with the latest version? ( without gestures)?

Wysłane z mojego 22081212UG przy użyciu Tapatalka
 
Status
Not open for further replies.

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
44K
Replies
51
Views
45K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
54K