u can dirty flash to the dev miui14 version but u cant downgrade back to the stable ver later without clean install.Excuse me, my mobile phone is Xiaomi 11ultra, and the mobile phone system is the stable version of miui13 eu, can I directly fastboot it to the development version of miui14 eu?
I don't know yet how to do it.do you know how can i solve it. I guess if i stop or delete google pay for second apps it can be solve but i don't know how can i change second app things they are very secret
I have the same issue here on my Mi 11 Ultra. All necessary permissions were provided. However, I'm still facing this problem. I also cleaned the Dalvik cache after the update from MIUI 13 to 14.Having Whatsapp issue after the update on my 12x
Contacts disappear and only show numbers. I have to re-sync in order for it to show up with names. This keeps happening.
Have tried clearing cache as well as uninstalling and re-installing. Issue still not going away.
Anyone having a similar problem?
Please share the download link for the updated xiaomi-app-vaultJust found a way to get hundreds of MIUI widgets from app vault. Updated xiaomi-app-vault-5-5-55-1207 (same version number) via apk and I get a pletora of working widgets, someone also in English.
But the small widgets do not work on the original app vaults ( like weather widget )Just found a way to get hundreds of MIUI widgets from app vault. Updated xiaomi-app-vault-5-5-55-1207 (same version number) via apk and I get a pletora of working widgets, someone also in English.
Hallo, So i followed these steps. However I get attached error when trying to install TWRP on step number 8. Any ideas, why this is happening? Device XM 12 Pro, after that got stuck on Fastboot. I had to redo the steps again from 1 to boot into system? Thanks.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.
- Powered off phone completely
- Entered fastboot via Power Button + Volume Down
- Checked phone is detected with
Code:fastboot devices
- Flashed ROM via PowerShell with
Code:.\windows_fastboot_update_rom.bat
- Waited for reboot - entered system and waited for the update to finish - didn't do anything with the phone yet
- Powered off phone completely
- Entered fastboot via Power Button + Volume Down
- Booted into TWRP with
Code:fastboot boot twrp-3.7.0_12-v6.5_A12-haydn-skkk.img
- Flashed TWRP via Advanced -> Flash current TWRP
- Powered off phone completely
- Turned phone on again, waited to get back into system and checked everything is fine
--- STOP HERE IF YOU DON'T WANT/NEED ROOT ---
- Powered off phone completely
- Entered recovery via Power Button + Volume Up
- Installed Magisk-v25.2.apk via TWRP (changed the extension from .apk to .zip, resulting in Magisk-v25.2.zip)
- Powered off phone completely
- Turned phone on again
Dude unplug the cable and reboot the phone in fastboot mode. And try again. You may need to do this a few timesHallo, So i followed these steps. However I get attached error when trying to install TWRP on step number 8. Any ideas, why this is happening? Device XM 12 Pro, after that got stuck on Fastboot. I had to redo the steps again from 1 to boot into system? Thanks.
You are using instructions that are not suitable for your model. Inappropriate fastboot command.Hallo, So i followed these steps. However I get attached error when trying to install TWRP on step number 8. Any ideas, why this is happening? Device XM 12 Pro, after that got stuck on Fastboot. I had to redo the steps again from 1 to boot into system? Thanks.
fastboot flash recovery_ab twrp.img
Wich version did you download? Thanks!Just found a way to get hundreds of MIUI widgets from app vault. Updated xiaomi-app-vault-5-5-55-1207 (same version number) via apk and I get a pletora of working widgets, someone also in English.
If I first flash it to recovery_ab using your command and then do "fastboot boot twrp.img", it won't boot to twrp and stays in fastboot.You are using instructions that are not suitable for your model. Inappropriate fastboot command.
To install TWRP:
Rename the downloaded TWRP to twrp.img
Use the fastboot command:
Then manually boot into TWRPCode:fastboot flash recovery_ab twrp.img
[HowTo] Install Recovery image
How to install a xiaomi.eu recovery image Because of more and more working TWRP or OrangeFox on MIUI13 Android12 a little How To and here we go .... Unlock your device (only once) - you need to unlock bootloader -> a small [howto] to unlock bootloader Install Tools and Drivers - install USB...xiaomi.eu
D:\Downloads\xiaomi.eu_multi_XM12Pro_V14.0.22.12.19.DEV_v14-13-fastboot>fastboot flash recovery_ab twrp.img
target reported max download size of 805306368 bytes
sending 'recovery_ab' (102400 KB)...
OKAY [ 2.187s]
writing 'recovery_ab'...
(bootloader) Partition recovery_a flashed successfully
(bootloader) Partition recovery_b flashed successfully
OKAY [ 0.363s]
finished. total time: 2.559s
D:\Downloads\xiaomi.eu_multi_XM12Pro_V14.0.22.12.19.DEV_v14-13-fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.168s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Bad Buffer Size)
finished. total time: 2.284s
Dude this is just due to usb connection problem. Retrying is always effectiveIf I first flash it to recovery_ab using your command and then do "fastboot boot twrp.img", it won't boot to twrp and stays in fastboot.
Here is the code from cmd:
Code:D:\Downloads\xiaomi.eu_multi_XM12Pro_V14.0.22.12.19.DEV_v14-13-fastboot>fastboot flash recovery_ab twrp.img target reported max download size of 805306368 bytes sending 'recovery_ab' (102400 KB)... OKAY [ 2.187s] writing 'recovery_ab'... (bootloader) Partition recovery_a flashed successfully (bootloader) Partition recovery_b flashed successfully OKAY [ 0.363s] finished. total time: 2.559s D:\Downloads\xiaomi.eu_multi_XM12Pro_V14.0.22.12.19.DEV_v14-13-fastboot>fastboot boot twrp.img downloading 'boot.img'... OKAY [ 2.168s] booting... FAILED (remote: Failed to load/authenticate boot image: Bad Buffer Size) finished. total time: 2.284s
If I try to boot to recovery using hardware keys, it will still stay in fastboot.
Edit: I need to flash boot.img or patched boot.img to reboot into system
Edit 2: After I rebooted to system, I was sucessfull in booting to TWRP using harware keys
Dude it's probably because of the dirty flash. Since it was not installed correctly, he threw the phone into the recovery partition. Put the phone in fastboot mode and install the rom with the data format.bat fileHello guys and Merry Christmas ! I have xiaomi 12s ultra with global version 13.0.5 , i download xiaomi.eu_multi_THOR_V14.0.22.12.19.DEV_v14-13-fastboot.zip this version and started fast boot, after finishing miui recovery 5.0 on chinese language popped up.Can any one help me with this ?
Xiaomi 12S Ultra doesn't have any Global versions.... I have xiaomi 12s ultra with global version 13.0.5 ...
It shouldn't, if patching works properly. I can't confirm it as I notice no difference.Does the choice of region still affect the volume of the headphones in the MIUI 14 from the Eu team ???
thank you very match!!!!!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.
- Powered off phone completely
- Entered fastboot via Power Button + Volume Down
- Checked phone is detected with
Code:fastboot devices
- Flashed ROM via PowerShell with
Code:.\windows_fastboot_update_rom.bat
- Waited for reboot - entered system and waited for the update to finish - didn't do anything with the phone yet
- Powered off phone completely
- Entered fastboot via Power Button + Volume Down
- Booted into TWRP with
Code:fastboot boot twrp-3.7.0_12-v6.5_A12-haydn-skkk.img
- Flashed TWRP via Advanced -> Flash current TWRP
- Powered off phone completely
- Turned phone on again, waited to get back into system and checked everything is fine
--- STOP HERE IF YOU DON'T WANT/NEED ROOT ---
- Powered off phone completely
- Entered recovery via Power Button + Volume Up
- Installed Magisk-v25.2.apk via TWRP (changed the extension from .apk to .zip, resulting in Magisk-v25.2.zip)
- Powered off phone completely
- Turned phone on again
well on about phone i could read 13.0.5 global version. I managed to turn it on clicked every possible thing in miui recovery 5.0 chinese version. Now when i go to recovery menu its still on chineseXiaomi 12S Ultra doesn't have any Global versions.
It shouldn't, if patching works properly. I can't confirm it as I notice no difference.
dude install twrpwell on about phone i could read 13.0.5 global version. I managed to turn it on clicked every possible thing in miui recovery 5.0 chinese version. Now when i go to recovery menu its still on chinese
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation