Search results

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...

ok.

Where to place my question, as the original thread was closed?

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...

The credits for the Modem Patch mentioned are at Kacper, btw. @Kacper Skrzypek , I just realized that you updated the linked modem patch by leaving out "modem.img". May I ask for the reason behind, why "modem.img" obviously appeared as obsolete for updating w.r.t. global eSIM support? From...

Your application for unlock has to be placed at 00:00 China mainland time, sharply! If your time zone is CEST for example, you should transmit your application at 06:01 CEST. 08:22 CEST would be far too late... https://www.worldtimebuddy.com/cet-to-china-beijing

I don't expect flashing a custom ROM will solve any issue. The steps mentioned above are related to missing eSIM support AFTER switching to EU custom ROM. As stated above, for devices with original global Stock ROM I have no clue. There are quite a lot of very good tutorials of flashing a...

This worked for me on Xiaomi.eu: You have to ensure to download/replace the correct basebands modem.img modemfirmware.img from the resource provided above #2. I'm my point of view the Global OS1.0.6.0.UNRMIXM dtd. 2024-04-09 should match your device. But no guarantee, of course, as I don't know...

...for original Stock ROM I have no clue, sry!

Which ROM are you using on your global device, stock or Xiaomi.eu? If Xiaomi.eu on a global eSIM device, the solution which worked in my case was reflashing the modem baseband back to global, see post #2.

If you're not fast enough, the 10 days is the unavoidable waiting time, IIRC. As said above, put a reminder on 00:00 China, and you will succeed (at my case)

Xiaomi.eu in general bases on China ROM, which could lead to the effect, that your global modem baseband will be overwritten by the China ones, when flashing Xiaomi.eu. (AFAIK most chinese Xiaomi devices don't support eSIM, but two hardware SIM Slots only.) To solve this, you have to reflash...

Btw, if you are wondering on which region or firmware version your Xiaomi device is running, you can read from the (meaningful) firmware version number. A very helpful guide on how to decode Xiaomi's version numbers can be found here.

If you followed Dash A. Above (especially No. 4.-6. "community unlock") and the advices linked below, I have no further clue: :emoji_shrug: https://xiaomi.eu/community/threads/unlock-by-xiaomi-community.71321/...

You have been faster... :emoji_grin:

Have you tried the "Global Modem patch"? You can replace the contained modem.img + modemfirmware.img by the ones matching your device e.g. found here.