Search results

Indeed, reverse-engineering Qualcomm's bootloader to breach its security can easily be considered piracy. Whoever attempts this publicly is likely to get in legal trouble with Qualcomm, maybe also with Xiaomi.

It can't be restored.

Don't remember in which subforum you posted. It's not that talking about Pads isn't allowed, just do where it's relevant. If it's a question related to our ROM - "Questions & Answers", and if it has nothing to do with our ROM - "Mi General".

Well, I've been wrong. Been getting that quota error for over half a month, then when the phone arrived and I went to bind it, it just worked. Now waiting 72 hours to unlock. People, take notice. Their request system is a mess but you might still be able to unlock after all.

Old info from MIUI era. Don't get your info from some German site.

Do I need to answer twice? You'll need to flash an Android 15-compatible TWRP via fastboot after flashing the ROM. Or just replace recovery.img in the ROM's ZIP before flashing. Your choice.

That list is irrelevant anymore. Yes, you can update directly.

You're making 2 assumptions: 1. That I know anyone with the required skills to reverse-engineer and successfully find an exploit in a proprietary bootloader written by highly skilled engineers working for Qualcomm. 2. That a fundraiser would result in a success and not a disappointment, which...

We are not Xiaomi. https://c.mi.com/global/ Good luck.

I wouldn't know, I'm not using any kind of official ROM, and on our ROMs we only use a tiny bit of Mainline components, only one APEX.

Doubt anyone has any documentation about that, but definitely not in a partition that gets replaced every ROM update. In fact it's very likely not stored on any partition. Device information that you can see with "fastboot getvar all" could be stored somewhere else, somewhere persistent, might...

And where did you take that info from? Bootloader unlock state isn't stored on boot or vendor_boot. Those images are loaded by the bootloader.

See my reply above mate.

Typical APEX components on a Global ROM: com.android.apex.cts.shim.apex com.android.btservices.apex com.android.i18n.apex com.android.nfcservices.apex com.android.profiling.capex com.android.rkpd.apex com.android.runtime.apex com.android.uwb.capex com.android.virt.apex...

That's false. All variants of Global ROM (EEA, India, etc) come with full Google integration. On our ROMs, however, we use generic components, some of them were customized by Xiaomi to enable more features (like Wi-Fi optimization options).

There is no solution. https://xiaomi.eu/community/threads/the-xiaomi-unlock-scam.75099/

For me there was a simple fix for this - I uninstalled this piece of garbage relic of a software. Apps like Telegram and Signal are a whole generation above that junk.

Xiaomi 14 Civi (Indian variant of Xiaomi Civi 3 Pro) is not even one of the devices we support, which means you're not using our ROM, so I don't understand why you posted on our forum. And you're not alone with this problem. To me it seems like Whatsapp developers are incompetent. Shocking.

It's one of the scripts in the ROM's ZIP archive...

Not sure what we have to do with Google's backup.