MIUI 14 22.12.19/21


Status
Not open for further replies.
when i tried to remove the ram memory extension and my phone rebooted. It got stuck on the logo and then went into xiaomi trwp. it went into bootloop until i did wipe data. this also happened to me in the first release of miui 14 weekly but in a normal reboot. It just didn't start until I did clean install again. Did that happen to anyone else? My phone is Xiaomi 12. Thanks!
 
Tried to install on my Munch and stuck on this for 10 mins. Any suggestions??
 

Attachments

  • Screenshot 2022-12-25 144056.png
    Screenshot 2022-12-25 144056.png
    43.9 KB · Views: 184
  • Like
Reactions: Lyteka
when i tried to remove the ram memory extension and my phone rebooted. It got stuck on the logo and then went into xiaomi trwp. it went into bootloop until i did wipe data. this also happened to me in the first release of miui 14 weekly but in a normal reboot. It just didn't start until I did clean install again. Did that happen to anyone else? My phone is Xiaomi 12. Thanks!
No such problem on my Redmi K40 Pro+. I like to live dangerously so I just tried it out (after backing up data ;) ).

Tried to install on my Munch and stuck on this for 10 mins. Any suggestions??
Might be a USB connection issue. Just try flashing again using a different port on your computer and maybe a different cable. It doesn't matter that the previous partitions were already flashed.
 
Might be a USB connection issue. Just try flashing again using a different port on your computer and maybe a different cable. It doesn't matter that the previous partitions were already flashed.
Ok Will try that.
Thanks a TON it. Changed the port and it flashed the ROM. Cheers
 
Last edited:
  • Like
Reactions: Lim-Dul
On Poco F3, installed fine and testing now.
Thank you so much for a release over this festive season, much appreciated and all the best!

One thing I'd like to ask the community though.
Under Miui 13, Camera in RAW mode (Pro), dng files of the pictures used to be around ~20MB
Miui 14, Camera, RAW mode (Pro), dng files are now ~8MB.
Is this intended behavior? or did I mess something up to cause this?

Camera settings:
Picture quality: "High"
Mode: "Pro"
Lens: "Wide"
W/B, Focus, shutter, ISO: All set to "Auto"
Frame: "Full" (not 3:4, not 9:16)
 
flash for the Alioth is stuck on Sending sparse 'super' 6/9 (732584 KB), that's twice, MIUI won't boot anymore (after 4 tries it works)

Tried to install on my Munch and stuck on this for 10 mins. Any suggestions??
same problem
 
Last edited:
Installation completed on Poco F4 GT (ingres), rooted, working with approximation payments. Safetenet ok, widivine 1. No problem. Just enjoying.



Screenshot_2022-12-24-21-55-42-447_com.android.settings.jpg
Screenshot_2022-12-24-21-54-20-256_gw.z.cnxywf.e.ug.jpg
Screenshot_2022-12-24-21-54-01-962_com.android.vending.jpg
 
Very good ROM once installed, notifications are much improved (but still some apps being killed). NFC payments working fine also

Very few bugs so far, great work for only the 2nd release of MIUI 14!
 
Hey everyone! Ever since this new update, my phone has had a weird brown accent. And it's like this all across the UI. Even notifications
Is there any way to change this?
Thank you everyone and merry Christmas to you all!
IMG_20221225_121951.jpgIMG_20221225_121822.jpgIMG_20221225_121748.jpgScreenshot_2022-12-25-12-16-45-285_com.android.chrome.jpg
 
Dude, what's wrong with this battery usage? It doesn't save anything
 

Attachments

  • Screenshot_2022-12-25-16-22-50-065_com.miui.securitycenter.jpg
    Screenshot_2022-12-25-16-22-50-065_com.miui.securitycenter.jpg
    272.2 KB · Views: 188
1) It's a know unfixed Bug as mentioned in the last MIUI 13 Issues/Bugs Report #4

2) Which USSD Code are you dialling? *#06# is flawless on Poco F3

3) I'm already using Microsoft Office and hasn't multiple same apps into the apps default setting (annex)
The USSD codes that are related to the carrier. Like balance or anything SIM related. The *#06# is ok on my side as well.
 
Do you have any VPNs installed? I have Adguard and I have to deactivate it in order to use my identity certificate
Hi...thanks for replying...
No VPN installed..I've attached a LogCat couple of pages before regarding this issue but no reply yet

Seems like I'm not the only one having this issue. Couple of guys talking about this on the Bugs channel as well.
 
Successful (dirty) flash of the ROM, TWRP and Magisk on my Redmi K40 Pro+. Coming from the previous MIUI 14 Dev ROM.
I'll repost the steps I followed since they seemed to help a few people in previous version's thread.
Merry Christmas to everyone (who is celebrating it)!

My SUPER conservative procedure after years of experience with failing at various steps for certain ROMs, especially new ones:

Optional pre-step for dirty flashing:
Delete / move all scripts apart from the "XXXX_fastboot_update_rom.xxx" script for yor OS from the extracted ROM directory to avoid costly mistakes.
  1. Powered off phone completely
  2. Entered fastboot via Power Button + Volume Down
  3. Checked phone is detected with
    Code:
    fastboot devices
  4. Flashed ROM via PowerShell with
    Code:
    .\windows_fastboot_update_rom.bat
  5. Waited for reboot - entered system and waited for the update to finish - didn't do anything with the phone yet
  6. Powered off phone completely
  7. Entered fastboot via Power Button + Volume Down
  8. Booted into TWRP with
    Code:
    fastboot boot twrp-3.7.0_12-v6.5_A12-haydn-skkk.img
    1671480731539.png
  9. Flashed TWRP via Advanced -> Flash current TWRP
    1671480782089.png
  10. Powered off phone completely
  11. Turned phone on again, waited to get back into system and checked everything is fine

    --- STOP HERE IF YOU DON'T WANT/NEED ROOT ---

  12. Powered off phone completely
  13. Entered recovery via Power Button + Volume Up
  14. Installed Magisk-v25.2.apk via TWRP (changed the extension from .apk to .zip, resulting in Magisk-v25.2.zip)
  15. Powered off phone completely
  16. Turned phone on again

Thanks Lim-Dul, I tried this for Poco F3/Redmi K40 (alioth) but a clean install, and everything went okay. The clues you gave here were perfect! I didn't know i could execute the .bat directly from command line

I used this recovery from skkk, since the official 3.7.0 one couldn't decrypt internal storage: https://www.123pan.com/s/qHhDVv-nuQJv
Download icon in TWRP>A12>v6.5>[BOOT]3.7.0_12-RedmiK40-POCOF3-Mi11X_v6.5_A12-alioth-skkk_d109e8f7.zip
 
  • Like
Reactions: Lim-Dul
The USSD codes that are related to the carrier. Like balance or anything SIM related. The *#06# is ok on my side as well.
I did some standard GSM USSD codes and also MIUI tests flawless on Poco F3. (annex)
But the self care codes are carrier specific to certain networks only. Then I can't assist you.
But my suggestion is to check with your carrier if their customer care business support system through USSD are running smoothly now.
 

Attachments

  • IMG_20221225_100943.jpg
    IMG_20221225_100943.jpg
    177.6 KB · Views: 145
  • IMG_20221225_101028.jpg
    IMG_20221225_101028.jpg
    178.1 KB · Views: 142
  • IMG_20221225_101112.jpg
    IMG_20221225_101112.jpg
    181.5 KB · Views: 143
  • Screenshot_2022-12-25-10-07-48-311_com.xiaomi.mtb.jpg
    Screenshot_2022-12-25-10-07-48-311_com.xiaomi.mtb.jpg
    318.4 KB · Views: 141
Last edited:
Spyche 12X bug report: large gap between dock and icons
 

Attachments

  • Screenshot_2022-12-25-20-23-16-726_com.miui.home.jpg
    Screenshot_2022-12-25-20-23-16-726_com.miui.home.jpg
    1.5 MB · Views: 172
  • Like
Reactions: Ryoma
Status
Not open for further replies.

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
40K
Replies
51
Views
35K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
37K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
32K