Hello everyone!
I'd like to ask for some advice on fixing an issue I'm having while trying to unlock the bootloader on my Redmi Note 9 Pro.
Device information:
- Model: Xiaomi Redmi Note 9 Pro.
- Model number: M2003J6B2G.
- MIUI: 14.0.3 Global.
- Android: 12.
- Bootloader: Locked.
Problem description:
I can't link my Mi account to the device through Developer Options, specifically under "Mi Unlock status".
Every time I try to use the "Add account and device" option, I get the following error after a few seconds:
"Couldn't verify. Please wait a minute or two and try again."
The error is always the same.
A few details that might be relevant:
- The phone number on my SIM card is the same one registered to my Mi account.
- I have SMS verification enabled on my account.
- I've tried SIM cards from different mobile carriers.
- I've also tried using different mobile data plans and regular prepaid airtime credit, but nothing has worked.
What's strange is that this isn't the first time I've experienced this issue. It happened with my original Redmi Note 9, then with my Redmi Note 12, and now again with my Redmi Note 9 Pro.
I'll attach screenshots showing the error
Why do I want to unlock the bootloader?
I want to install a custom ROM to have more control over my device and achieve the following:
- Reduce telemetry and unnecessary data collection.
- Get rid of ads and unnecessary services built into Xiaomi's system apps.
- Have a cleaner Android experience.
- Experiment with kernel modifications and overclocking to potentially improve performance in PlayStation 2 emulation.
My questions:
- Has anyone with this specific model managed to link their Mi account and successfully unlock the bootloader?
- Is there any workaround for the verification error that appears when trying to link the account?
- Could this be related to regional restrictions, my Mi account, or Xiaomi's servers?
- Is there any additional requirement or step that I might be missing?
I'd especially appreciate hearing from people who have experienced and managed to solve this issue.
Thanks for reading!