MIUI 14 MIUI 14 STABLE RELEASE


Status
Not open for further replies.
So the main reason im going to stable rom is to fix the wifi issue that im having whenever i connect my airbuds, my wifi just becomes worse which is clear when i play games which is very annoying. So If you're using Stable rom, can i ask you that whether have you faced any similar bug like this?
 
I downloaded the latest update by recovery option. However when i try to install the file dont appears. Said that my internal system have 0 mb.
Anyone can help?
Thanks
 
Migsus said:
3.6.2.12mi11pro v5. 1_a12
Click to expand...
yep, way too outdated.

the one you have doesnt support decryption of Android 13

use this one

Devices with Boot as Recovery (A/B):
These devices don't have a dedicated partition for recovery.
The recovery ramdisk resides in the "boot_a" and "boot_b" partitions.
A shared kernel is used for both the system and the recovery.
Due to that, you should never flash a custom recovery image directly to the "boot_a" and/or "boot_b" partitions. If you do that, the system will fail to boot.

Platforms: Snapdragon 678/680/695/778G/778G+/780G/870/888/888+
Devices: alioth, haydn, lisa, mona, moonstone, munch, odin, psyche, redwood(in), renoir, spes(n), star/mars, sunny, sunstone, taoyao, thyme, venus, veux/peux, vili
Image size: 192 MiB (201,326,592 bytes), or 96/128 MiB (100,663,296/134,217,728 bytes) for low-mid devices
Installation:
Code:
fastboot boot recovery.img
In the recovery interface: Advanced -> Install Recovery Ramdisk
 
  • Like
Reactions: JiaiJ
Hello! I decided to upgrade from the stable POCO F3 version 14.0.6.0 to the stable POCO F3 14.0.7.0 using a fastboot with windows_fastboot_update_rom.bat, I had not encountered such a problem before. At the step: "Sending "super" 523364" I have been waiting for about 40 minutes and I'm still waiting. Very scary. What can you advise?
11.png
 
Last edited:
maxonyx said:
Hello! I decided to upgrade from the stable POCO F3 version 14.0.6.0 to the stable POCO F3 14.0.7.0 using a fastboot with windows_fastboot_update_rom.bat, I had not encountered such a problem before. At the step: "Sending "super" 523364" I have been waiting for about 40 minutes and I'm still waiting. Very scary. What can you advise?
View attachment 48390
Click to expand...
Sounds like the USB connection is hanging. The vital partitions are already flashed at this point, so bricking shouldn't be possible.
The only thing you can do is swap to a trusted cable and USB 2.0 port and retry the flashing process. You'll need to hold Power+Volume Down buttons to re-enter fastboot mode. There's nothing else you can do here.
 
  • Like
Reactions: maxonyx
Igor Eisberg said:
Sounds like the USB connection is hanging. The vital partitions are already flashed at this point, so bricking shouldn't be possible.
The only thing you can do is swap to a trusted cable and USB 2.0 port and retry the flashing process. You'll need to hold Power+Volume Down buttons to re-enter fastboot mode. There's nothing else you can do here.
Click to expand...
Thanks a lot! Now I will try

Update: Everything went well, god I was scared
 
Last edited:
xMarvin732 said:
yep, way too outdated.

the one you have doesnt support decryption of Android 13

use this one

Devices with Boot as Recovery (A/B):
These devices don't have a dedicated partition for recovery.
The recovery ramdisk resides in the "boot_a" and "boot_b" partitions.
A shared kernel is used for both the system and the recovery.
Due to that, you should never flash a custom recovery image directly to the "boot_a" and/or "boot_b" partitions. If you do that, the system will fail to boot.

Platforms: Snapdragon 678/680/695/778G/778G+/780G/870/888/888+
Devices: alioth, haydn, lisa, mona, moonstone, munch, odin, psyche, redwood(in), renoir, spes(n), star/mars, sunny, sunstone, taoyao, thyme, venus, veux/peux, vili
Image size: 192 MiB (201,326,592 bytes), or 96/128 MiB (100,663,296/134,217,728 bytes) for low-mid devices
Installation:
Code:
fastboot boot recovery.img
In the recovery interface: Advanced -> Install Recovery Ramdisk
Click to expand...
Hi. Thanks. But i could install the miui 14, but this update i cant.
I downloaded the file of TWRP update but when i use the recovery option the file dont appears. I go to advanced - install recovery ramdisk but i cant find the file. If i choose internal storage appears nothing. 0 mb
 
JiaiJ said:
If you want "strong integrity", the options seems limited currently.

xiaomi.eu

MIUI 14 - MIUI 14 STABLE RELEASE

Try setting your phone region to Singapur, they dont have volume limit. I'm also going to do this, thanks!
xiaomi.eu xiaomi.eu
Click to expand...
I rooted the phone and used the module to fix integrity check. My banking app still isnt working and only thing i am not passing is Magisk package name.
 

Attachments

  • Screenshot_2023-07-18-06-55-44-999_gr.nikolasspyr.integritycheck.jpg
    Screenshot_2023-07-18-06-55-44-999_gr.nikolasspyr.integritycheck.jpg
    161 KB · Views: 235
  • Screenshot_2023-07-18-06-56-32-681_krypton.tbsafetychecker.jpg
    Screenshot_2023-07-18-06-56-32-681_krypton.tbsafetychecker.jpg
    350.6 KB · Views: 216
  • Screenshot_2023-07-18-06-58-16-526_krypton.tbsafetychecker.png
    Screenshot_2023-07-18-06-58-16-526_krypton.tbsafetychecker.png
    37.4 KB · Views: 211
exibo93 said:
I rooted the phone and used the module to fix integrity check. My banking app still isnt working and only thing i am not passing is Magisk package name.
Click to expand...
To hide apps (like your LSPosed module) you need to use another LSPosed module HMA and configure it

However, no guarantee that your banking app finds that or something else. Eg, you had to install Shamiko module put your banking app to DenyList and not Enforce DenyList (seems you did for TB Checker)

Car and mouse game. Apps can also find that BL is unlocked by not going through Strong Integrity. Ie, you pass Strong Integrity now but KeyAttestation app will still see that your BL is unlocked. There is another LSPosed module to hide it, BootloaderSpoofer

You hide all that and maybe next update of the banking app will find something else

Etc. The only 100% 'method' is to keep Bootloader locked and to stay on stock ROM ;-(
 
  • Like
Reactions: katerpanne and JiaiJ
exibo93 said:
I rooted the phone and used the module to fix integrity check. My banking app still isnt working and only thing i am not passing is Magisk package name.
Click to expand...
To hide apps (like your LSPosed module) you need to use another LSPosed module HMA and configure it

However, no guarantee that your banking app finds that or something else. Eg, you had to install Shamiko module put your banking app to DenyList and not Enforce DN

Car and mouse game. Apps can also find that BL is unlocked not going through Strong Integrity. Ie, you pass now Strong Integrity but KeyAttestation app will still see that your BL is unlocked. There is another LSOosed module to hide it, BootloaderSpoofer

You hide all that and maybe next update of the banking app will find something

Etc. The only 100% 'method' is to keep Bootloader locked and stock ROM and to stay on Stock
 
alison.rm said:
Are you using v13.x? I'm having some heating issues. I'm trying to get around. Thinking about going to 13.x... the older ones are generally good.
Click to expand...
I was on 14, but heating probs like you...I am back to 13 since weeks, all good now. 14 is buggy!!!
 
exibo93 said:
I rooted the phone and used the module to fix integrity check. My banking app still isnt working and only thing i am not passing is Magisk package name.
Click to expand...
you can download an app,,, applist detector to check if the libs or modules are visible. If you are familiar with programming you can use XPrivacyLua. Search this forum for Digitales Amt there is an example.

Best way as zgfg12 mentioned stock rom and BL locked

PS: magisk topics etc should not be discussed in this topic :)
 
Last edited:
During testing, noticed that phone network device (WiFi) ID is reported differently on Global and xiaomi.eu ROMs.

In my case, on Global it says "Xiaomi-13", while on xiaomi.eu ROM says "UNKNOWN".

Any ideas why?

xiaomi-13-issue-wifi-network-id.jpg
 
Hello i'm new here coming from MIUI GLOBAL 14.0.4(TKHMIXM) Using POCOPHONE F3

Is it okay if i install this version of stable version of MIUI.EU 14 STABLE ROM in July 2023 and do i need to format my phone since its said first time installer need to format/wipe data

I have read most of the forums but i somehow cant understand most of it since the last phone i do the custom rom is on older phone back in 2015 with my Samsung Galaxy V

Im afraid that my phone will get broken or stuck bootloop

Hope you answer this.

Love from Malaysia.
 
dtfmi said:
Just updated to Miui 14.0.4.0 (sweet / Redmi Note 10 Pro)
Got a few errors during flash but everything seems to be working fine.
Thanks, devs!
Click to expand...
How much battery drain do you have? "Android System" drain battery very much on all MIUI14 versions before!
 
I Installed this rom on a Redmi Note 12 4G NFC (Topaz) via Fastboot withour any errors. Thank you.
I observe some errors I never had with Xiaomi.EU:
- The whole system appears very jerky so that I have to deacivate animations to get a fluent user experience.
- During google maps navigation, the phone frequently loses cell service and gps service. Deactivating and reactivating the SIM slots recovers the service after 10 minutes. Instant recovery is possible via reboot.
- Opening google chrome frequently crashes throwing me to the home screen

I consider to go back to stock to test if those errors are vendor-firmware related. Do you know where to download?
 
Status
Not open for further replies.

Similar threads

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