Killua.Zoldyck
Members
- 24 May 2019
- 31
- 20
Hi, did you dirty flash or clean flash?Green light to go!
Installing smoothly on Poco F3...
- Status
Jorisimone
Members
- 14 Jul 2018
- 46
- 20
Yes dirty flash from last rom
Attachments
Bayu Mustika I P
Members
- 24 Jun 2018
- 8
- 15
I find bug if use screen off button at game space, aod and lockscreen get weird wallpaper like this
Attachments
Last edited by a moderator:
Unable to find any mirror information for the "/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/xiaomi.eu_multi_THOR_V14.0.22.12.16.DEV_v14-13-fastboot.zip" file. Please select another file.
I cannot download the 12s Ultra build, Thank you.
///
Sorry and Thank you.
I cannot download the 12s Ultra build, Thank you.
///
Sorry and Thank you.
Last edited:
It's "suspended" due to some bootloop issues, be patient!!!!
Mr.Curse
Members
- 14 Nov 2020
- 57
- 30
Will there be any issues if I update from Stable MIUI 13 to Weekly MIUI 14 on XM12(cupid)?
Superwitschi
Members
- 24 Mar 2012
- 958
- 162
pjgoncalves
Members
- 10 Jun 2014
- 290
- 67
I think the team is working on the bugs now. I could not install this firmware on 12su
immerzu
Members
- 14 Jun 2018
- 97
- 30
- 18 Mar 2017
- 782
- 257
Uploaded V14.0.22.12.8.DEV for 12S Ultra. We're still investigating the bootloop issue on V14.0.22.12.16.DEV.
- 11 Feb 2012
- 11,607
- 322
Last edited:
Marblehead
Members
- 3 Jan 2022
- 17
- 15
Yes, I also did exactly this (of course after 2./ I unzipped the file in the comp) and I succeeded by installing on Mi 11 Ultra for a first attempt.
Reekax
Members
- 22 Dec 2021
- 67
- 20
Birraque
Members
- 12 Nov 2018
- 954
- 257
Dirty update from .EU Weekly 22.10.26 throughout FASTBOOT method.
TaFNC
Members
- 2 Apr 2019
- 159
- 40
From step 11 the device boot only in twrp.Dirty flashed from MIUI 13 22.10.26. Flashed TWRP, flashed Magisk 25.2 - everything is working fine, banking apps as well. Didn't check for bugs that were not immediately obvious.
I know this might be pure superstition but when working with fastboot I prefer to only ever do hardware shutdowns / reboots instead of doing stuff like fastboot reboot or rebooting from TWRP. Was burned once or twice by ROMs that bootlooped when soft-rebooting.
So, my procedure, for anyone who is interested (it's SUPER conservative after years of experience with failing at various steps for certain ROMs, especially new ones):
I learned it's better to not rush things when working with Bootloader images. I mean, heck, the initial lack of a recovery ROM kept me from using the phone as a daily driver for like a year.
- Powered off phone
- Entered fastboot via Power Button + Volume Down
- Checked phone is detected via fastboot devices
- Flashed ROM via windows_fastboot_update_rom.bat in PowerShell
- Waited for reboot - entered system and waited for the update to finish - didn't do anything with the phone yet
- Powered off phone
- Entered fastboot via Power Button + Volume Down
- Booted into TWRP via fastboot boot twrp-3.7.0_12-v6.5_A12-haydn-skkk.img
- Flashed TWRP via Advanced -> Flash current TWRP
- Powered off phone
- Turned phone on again, waited to get back into system and checked everything is fine
- Powered off phone
- Entered recovery via Power Button + Volume Up
- Installed Magisk 25.2
- Powered off phone
- Turned phone on again - everything is fine as described above
Mi11i - haydn
- 6 Oct 2016
- 9,979
- 322
ROM for Redmi K40 / POCO F3 reuploaded to fix audio-related issues due to Voice Match / OK Google incompatibility.
Voice Match when screen is off will not be available, and the device will be identified as the Chinese Redmi K40 model.
When a Global Android 13 ROM is released for POCO F3, we'll be able to port it.
Voice Match when screen is off will not be available, and the device will be identified as the Chinese Redmi K40 model.
When a Global Android 13 ROM is released for POCO F3, we'll be able to port it.
Everything seems to be working, when you click on check update there is "New" update.
Attachments
- Status
