Solution see below:
Hello all,
Is anyone facing this Chrome/WhatsApp issue after upgrading Xiaomi 14 HOUJI to OS2.0.6.0.VNCCNXM (A15)?
- Chrome freezes when clicking a internet link within WhatsApp => black chrome screen & rotating"donut".
- e.g., YouTube opens fine, when clicked from WhatsApp...
I'm using Android Auto on my Xiaomi 14 with no issues. Nevertheless I updated to the most recent version of AA, downloaded from here, fyi:
https://www.apkmirror.com/apk/google-inc/android-auto/#all_versions
Hi,
as gogocar62 said, a global houji is mandatory for applying his linked patch (recommended).
Decompress the zip file and, in case of Windows OS, run the "windows_modem.bat"-file by double clicking, that's it.
Btw, this link still works...
Are you really sure of having a global device including eSIM support?
If yes, I've no more clue as to refer to gogocar62's first post on this thread, I'm sorry.
Assuming that you have global XM14 - in principle, yes.
However, my recommendation is to download and extract the latest modemfirmware.img from here:
https://xmfirmwareupdater.com/firmware/houji/
(Use the latest version available, except the Chinese one)
Oh okay, I'm also receiving the recurring notification about the latest pay fix myself. The only solution I know is to tick "don't show again" box for stopping regarding notifications...
Google Pay will stop working if the "device integrity" isn't valid anymore. This can be checked in the developer options of the Google Play Store app, btw:
This is not about the ROM, but about a missing/invalid device's fingerprint, which must be met in order to use Google Pay.
If the said...
No, there's no eSIM support of the hardware of chinese houji, which is why the chinese firmware doesn't support this either. see:
https://xiaomi.eu/community/threads/enable-isim-esim-on-xiaomi-14-pro.70900/post-712036
I'm not aware that Google Pixel allows some software based kind of hardware features "unlock"?! :emoji_thinking:
However, I'm not familiar with the hardware specs of 14's Pro & Ultra versions, tbh.
But in fact even houji has two different hardware setups, as the basebands differs between China...
Seriously? eSIM functionality is a hardware feature. There's no point in updating the software, even less if it is from a completely different phone model?
In my opinion: NO!
I assume that only very few of the ever increasing number of global newcomers are really aware of this statement of Igor Eisberg.
This general policy should be part of the FAQ, as probably every newcomer with a global device will ask exactly the same questions about the eSIM basebands here...
The thread mentioned asked about the dual eSIM support of the Global Houji, i.e. two active eSIMs at the same time (the answer is no, btw).
There is of course no question that the global Xiaomi 14 supports eSIM in principle.
Thanks for that, I'll try to test them too.
Is there a general rule for when a ROM is called "global", in order that their modemfirmware.img should fit?
Or do we have to test different ROMs one by one, by try and error? :emoji_thinking:
Thanks for the clarification. Actually I wasn't aware of any additional SIM issue, as I was obviously falsely convinced that the missing eSIM feature was the only difference in modem baseband's hard-/software of the region versions...
What should be correct is, that the "modemfirmware.img" of...
The solution described should not related to SIM, but to eSIM only, which should be amended accordingly?
Some details regarding the regions differences can be found here, see "Bonus:" below.
Which ROM's/region's "modemfirmware.img": should be capable of supporting eSIM on global (hardware) houji?
Seems to be Global, EEA, Russia, and...?
...or all other regions except China and India?
Deeper dive:
My assumption for hardware regions & software regions supporting eSIM for houji is...
Thanks for the info.
I'm asking because the modemfirmware.img included in the patch is reading md5: 1b9a133c946d5bd30b71e98e5fc01169
...while the modemfirmware.img which can be downloaded from xiaomifirmwareupdater.com is reading:
OS1.0.6.0.UNCMIXM md5:
e8b69a9bf5f77f38ff84c58cfa68813f...