unnamed777
Members
- Nov 29, 2018
- 4
- 13
I had the same problem with this version. Couldn't wipe the phone before installing firmware ("Unable to locate /data"). I flashed twrp v7.9 and everything is working now.
MIUI 14 MIUI 14 STABLE RELEASE
- Thread starter ingbrzy
- Start date
- Status
Does someone knows if in Xiaomi 13 fuxi Xiaomi.eu 14.0.31 local mp3 ringtones works? And local notification sounds? Do you have Music app working with local mp3 files?
Cyirus
Members
- Dec 22, 2017
- 13
- 15
gogocar62
XM12 Tester
- Apr 22, 2021
- 4,977
- 322
There is nothing to fix. That designation is correct.
device name (Xiaomi 11 Ultra) = codename (star) = model name (M2102K1G)
device name (Xiaomi 11 Ultra) = codename (star) = model name (M2102K1G)
Last edited:
I am also not able to change phone or WhatsApp ringtones from default. So many niggles with Xiaomi.
Hello everyone........i 'm new in this eu stabile.
I use weekley on fuxi mi 13.
Can i know if there are bug ?Is It Better eu or weekley on fuxi?
I use weekley on fuxi mi 13.
Can i know if there are bug ?Is It Better eu or weekley on fuxi?
Hi, I'm running into some weird problems with the latest stable for Redmi 9T (pomelo). I installed this ROM, but now I can't get the phone to detect my SIM. If I eject it and insert it again, sometimes nothing happens, sometimes a spinning circle appears, and the phone reboots straight into recovery. Sometimes before the spinning circle, an error message appears saying "com.android.phone... has stopped", and I can't even get the log because the spinning circle appears and then the phone reboots straigth into recovery. And yes, I've already tried to delete cache and data of com.android.phone, but there's no data to delete. There's been times where I get signal but no mobile data, and sometimes I get signal and mobile data, but I don't know how to trigger this events, they just seem completely random.
Does anyone know how to fix this?
Does anyone know how to fix this?
mankokoma
Members
- Aug 5, 2019
- 189
- 55
Done that already, the SIM works and the phone worked flawlessly before I installed this ROM (except for the mobile carrier bloatware). Never had a similar issue on my Mi 11 Lite 5G (Renoir) and Mix 2S (Polaris), their ROMs just worked perfectly at the first boot, that's why I don't even know where to begin.
May be something regarding to baseband? As Redmi 9T has different model names and mine is the Latin America variant, Pomelo, there might be some interference or something.
Also I found how to get signal just for a couple of minutes or until the next reboot. When I get through the initial setup, the phone tells me there's no SIM, so I eject and insert again, and it works but it's super unstable. BUT this just works at the initial setup, because if I eject and insert the SIM after all of this, the phone either enters a recovery bootloop (as explained in my first post) or nothing happens.
I'm facing a lot of these warnings when trying to install xiaomi.eu rom on my F3 with fastboot method, is something wrong with my device?
Code:
Warning: skip copying abl_ab image avb footer (abl_ab partition size: 0, abl_ab image size: 208896).
Warning: skip copying aop_ab image avb footer (aop_ab partition size: 0, aop_ab image size: 204800).
Warning: skip copying bluetooth_ab image avb footer (bluetooth_ab partition size: 0, bluetooth_ab image size: 421888).
Warning: skip copying cmnlib_ab image avb footer (cmnlib_ab partition size: 0, cmnlib_ab image size: 397312).
Warning: skip copying cmnlib64_ab image avb footer (cmnlib64_ab partition size: 0, cmnlib64_ab image size: 516096).
Warning: skip copying devcfg_ab image avb footer (devcfg_ab partition size: 0, devcfg_ab image size: 57344).
Warning: skip copying dsp_ab image avb footer (dsp_ab partition size: 0, dsp_ab image size: 67108864).
Warning: skip copying dtbo_ab image avb footer (dtbo_ab partition size: 0, dtbo_ab image size: 33554432).
Warning: skip copying featenabler_ab image avb footer (featenabler_ab partition size: 0, featenabler_ab image size: 90112).
Warning: skip copying hyp_ab image avb footer (hyp_ab partition size: 0, hyp_ab image size: 446464).
Warning: skip copying imagefv_ab image avb footer (imagefv_ab partition size: 0, imagefv_ab image size: 2097152).
Warning: skip copying keymaster_ab image avb footer (keymaster_ab partition size: 0, keymaster_ab image size: 282624).
...
Last edited by a moderator:
- Oct 6, 2016
- 9,898
- 322
All is fine, the latest fastboot tool is being too talkative.
Could someone tell me if the certification has already passed? thank youPOCO F5 PRO
CTS does not pass in the latest version 14.0.28
I installed it through fastboot and twrp skkk and in both without certification
Same here on my Poco F5. Made a post here: https://xiaomi.eu/community/threads...fetynet-fail-with-cts-profile-mismatch.70366/POCO F5 PRO
CTS does not pass in the latest version 14.0.28
I installed it through fastboot and twrp skkk and in both without certification
Netzjunkey
Members
- Dec 30, 2019
- 19
- 15
I install for 3 times in with diferent original rom and twrp and work very good but I can´t call any one, the phone said "there is not phone network", data work perfectly but not the calls. The sim work ok in other phone without call errors, The xiaomi original roms works good with all, including calls, but xiaomi.eu not. I have a poco f5 pro mondrian. Can you help me? thanks in advance.
I have a Poco f3 with the last xiaomi.eu rom and work perfectly in all, calls, including with the same sim card
I have a Poco f3 with the last xiaomi.eu rom and work perfectly in all, calls, including with the same sim card
I probed with global and eu rom and calls work too. So I think it´s something about china rom, perhaps k60 and poco f5 pro have diferent network band. I probed older xiaomi.eu rom too and the same network problem. I´m frustated. I forgot to say that I´m from Spain.
Last edited:
I give me my own respond, this is the solution, tomorrow I´ll probe. https://xiaomi.eu/community/threads/poco-f5-pro-call-problems.69144/page-6
buralardayim
Members
- Oct 3, 2023
- 22
- 15
The date of all the videos I shot from the original camera application appears as 1970, the duration is 0 seconds, and when sharing via WhatsApp, it gives an incorrect file type error.
I got this error after google system update. I applied the suggested solution. (data/apex file) problem still persists. what should I do?
xiaomi 13 fuxi eu stable latest version.
I got this error after google system update. I applied the suggested solution. (data/apex file) problem still persists. what should I do?
xiaomi 13 fuxi eu stable latest version.
Attachments
It's a known problem, you need to use the global modem as the one from the China rom (k60) is not compatible. The linked flashable zip with the global modem image fixes that.
- Feb 11, 2012
- 11,601
- 322
- Status
