Redmi 3S Bootlader Unlocking (Stuck @ 50%) - Xiaomi Redmi 3 Questions & Answers

I got permission from MI through SMS. Now I can unlock my redmi 3s. Problem is Miflash gets stucked at 50%. I get error "couldn't verify device, current account is different from the account different info on the device".
I am using same account in both mobile and MiFlash.
I tried different version of Mi Flash but gets same error.
Anyone who had successfully unlocked BL, Pls share your method.

O pen Miflash by administrator
Enviado do meu SM-G310HN através de Tapatalk

Could be a vendor rom, as in not genuine xiaomi so will have to flash proper rom before you can unlock bootloader.
There are risks but I had no problems.
http://en.miui.com/thread-254606-1-1.html
Just check you get the right rom to flash your device. It's the same for all xiaomi phones double check the rom you want or you will brick it.

I had the same issue. I flashed the developer ROM(also known as global beta). Then the unlock procedure was successfully done on that ROM.

Related

couldn't verify device Error with mi flash

Hi guys, my redmi note 4 arrived yesterday. I do the procedure to unlock the bootloader and today I've received the SMS from xiaomi that allows me to unlock it. But when I set the phone in fastboot and I log in in Miui. Com, the procedure arrives until 50%,then I have this message of error :" Current account is different from the account info on the device."
I don't find anything for redmi note 4,but only how yo fix the same error in note 3.can anyone help me please?
I need to install the global rom, I'm Italian and now there's the china/English rom. Thanks and I apologize for my bad English
You need to flash Chinese developer version to unlock bootloader. Flash with sp_flash_tool
SOLVED :I updated to latest Chinese Rom, then I have sign up in my account and i got unlock!!!!!
peshkoff said:
You need to flash Chinese developer version to unlock bootloader. Flash with sp_flash_tool
Click to expand...
Click to collapse
This is interesting. I have the global ROM and get the same message after 50%. . . couldn't verify. . . when trying to unlock the bootloader. What would you suggest for me. . . get the Global Developer ROM?
The Xiaomi solution is: if it doesn't work the first time, wait a week, then it will!
@doktorspin, here what I've done:
1)My phone asks me to make an update to the latest version, so I did
2)Then I signed up in MI account in the phone [settings =>account =>mi account]
3)boot on fastboot, opened mi flash, and then it works over 50%, and didn't give me any more the error '' couldnt verify device.... "
So it works for me, but I don't know if I only was Lucky
Your O.P. indicates you have the Chinese stable ROM and Peshkoff recommended that you flash the Chinese developer ROM to fix the "couldn't verify device" problem. I wondered if he'd recommend the Global developer ROM for someone with the same "couldn't verify device" problem but with the Global stable ROM.
sirsandrone said:
@doktorspin, here what I've done:
1)My phone asks me to make an update to the latest version, so I did
2)Then I signed up in MI account in the phone [settings =>account =>mi account]
3)boot on fastboot, opened mi flash, and then it works over 50%, and didn't give me any more the error '' couldnt verify device.... "
So it works for me, but I don't know if I only was Lucky
Click to expand...
Click to collapse
Maccome mai si deve chiedere permesso di sbloccare il bootloader??
doktorspin said:
Your O.P. indicates you have the Chinese stable ROM and Peshkoff recommended that you flash the Chinese developer ROM to fix the "couldn't verify device" problem. I wondered if he'd recommend the Global developer ROM for someone with the same "couldn't verify device" problem but with the Global stable ROM.
Maccome mai si deve chiedere permesso di sbloccare il bootloader??
Click to expand...
Click to collapse
Because xiaomi phones are locked, if you wanna unlock them you must do a procedure, after it you must wait an SMS from xiaomi that allows you to unlock bootloader with mi flash
sirsandrone said:
Because xiaomi phones are locked, if you wanna unlock them you must do a procedure, after it you must wait an SMS from xiaomi that allows you to unlock bootloader with mi flash
Click to expand...
Click to collapse
That's not an explanation: it's a rehearsal of Xiaomi policy. Locking the bootloader is definitely not modification friendly.
And I have the SMS. It is useless when the Xiaomi servers are incapable of verifying my data in order to unlock the bootloader. There is no explanation. Locking the bootloader with a hopeless system to unlock it is needless stupidity.
@doktorspin this xiaomi service sucks. They should not unlock bootloader so there were no problems.
sirsandrone said:
@doktorspin this xiaomi service sucks.
Click to expand...
Click to collapse
Yes, the service sucks.
sirsandrone said:
They should not unlock bootloader so there were no problems.
Click to expand...
Click to collapse
No, there are sufficient problems either way.
I want to control my fonts, not use the rubbish someone else packages. I want to monitor my Wi-fi and internet, not live in the hope that Xiaomi is able to protect the phone. I want to be able to change the look and feel of my phone. I want to use CyanogenMod as the operating system: Xiaomi will continue to fiddle with a closed system and won't be able to provide longterm updates.
I set the phone in fastboot and I log in in Miui. Com, the procedure arrives until 50%,then I have this message of error :" Current account is different from the account info on the device."
I have MIUI Global 8.0 Stabil 8.0.4.0( MBFMIDG)
Please help.
moremih said:
I set the phone in fastboot and I log in in Miui. Com, the procedure arrives until 50%,then I have this message of error :" Current account is different from the account info on the device."
I have MIUI Global 8.0 Stabil 8.0.4.0( MBFMIDG)
Please help.
Click to expand...
Click to collapse
There could be a couple of things wrong, are you not following the procedure correctly? You must flash the China Dev fastboot rom to unlock your bootloader. Once you do that you need to log in on the phone to the mi account that you requested the unlock permission for. You need to switch the OEM unlock option on under developer settings and then log into your mi account (has to be the same as on your phone) on the Xiaomi unlocker tool on your PC.
couldn"t verify
Hooray! I managed to unlock the bootloader after 10 days.
SOLVED: I updated to latest Chinese Rom
I solved the problem by following the instructions from this forum here : http://en.miui.com/thread-257729-1-1.html
In fact, my MI MIX was already unlocked for some reasons but I would not know if I did not check. I was getting the same error "Couldn't verify device" stuck at 50%.
gsmyth said:
There could be a couple of things wrong, are you not following the procedure correctly? You must flash the China Dev fastboot rom to unlock your bootloader. Once you do that you need to log in on the phone to the mi account that you requested the unlock permission for. You need to switch the OEM unlock option on under developer settings and then log into your mi account (has to be the same as on your phone) on the Xiaomi unlocker tool on your PC.
Click to expand...
Click to collapse
Is there any way to switch to china developer rom from Global Dev 7.2.23? Updater won't let me. Or is there a specific chinese rom version that is allowed to flash via updater? Thanks!

Xiaomi different versions LOL + "current account is not bound to this device!' error

Xiaomi different versions LOL + "current account is not bound to this device!' error
I finally found out there are looooooooooads of Redmi types, unbelievable!
Maybe Xiaomi should minimize their offer, I thought I had a Redmi Note 3, but I finally found out it's a
Xiaomi Redmi 3 IDO (3A) Snapdragon LOL
I ordered one for my daughter, and now I see it's actually a Redmi Note 3 (bit more expensive and different at the back).
==> So i'm busy checking out how to flash, I got the official sms to unlock the locked bootloader and the first part goes to 100%, but theb I have another error : "Current account is not bound to this device!"
I'll guess some more errors will follow seen this long & difficult process
I dowloaded the latest miui_MI6Global_7.8.10_024aaf1afd_7.1 of this week, but now I need to get rid of that error & locked bootloader.
Do I need to flash an old beta rom first or something to get rid if this error message ?
Nice to see a fellow Belgian here
I am a bit confused. You are trying to flash your Redmi 3 (ido)?
Because the ROM you say you've downloaded is one for Xiaomi Mi 6...
Could you provide some information (screenshot of your 'about phone' with the current installed MIUI ROM etc?)
When I unlocked my ido's bootloader last year, I flashed the Chinese developer ROM using MiFlash, coming from a fake vendor ROM via EDL mode. Then in China dev ROM I unlocked the bootloader using MiUnlock.
After that I flashed TWRP (flash lazyscript before booting into the system or change to custom ROM immediatly because dm-verity is a b****).
I believe in recent ROMs, EDL mode was blocked by Xiaomi.
About the error: make sure you log in to the unlock tool with the same account as you are logged in to on your phone (the account with unlock permission). Then go to "developer options - Mi Unlock status" and make sure your account has been bound to the device there.
USB-debugging should be enabled, as well as OEM-unlock.
I do not know when you received the unlock code, but it is possible you'll have to wait a week or so. A lot of people have found that it suddenly works after a few days of waiting.
If you cannot switch to a developer ROM due to locked EDL mode, you should be able to flash your ido with locked bootloader using xiaomitool. http://en.miui.com/thread-835254-1-1.html
With this tool you can switch between MIUI ROMs on a locked bootloader.
I don't see any reason on why you download Mi 6 (sagit) recovery ROM instead of Redmi 3 (or Redmi Note 3 if it's what you're talking about) one. For "Current account is not bound to this device" error, wait for at least a week after you bind your Mi account with your phone before unlocking.
Good luck.
Sent from my Redmi 3 using XDA Labs
Haha greetz to Belgium too Yes I was a long time since I checked the latest roms / Xiaomi phone versions
Now I have a rooted stable MIU9 V9.2.2.0 Laicnek and looking for the best battery saving Kernell, hope I can flash this simply with TWRP as everything is installed allready
What do I need to choose again in the options to flash a Kernell only ?
Otherwise the Lineos 15 with the latest Oreo (if there is an official version 15 already, as I see only a beta 2)

EDL Authorization

Hello I need help with my Note 5. Downloaded latest global rom and mi flash tool.. entered edl mode with test point and i got a proplem saying "Only nop and sig tag can be recevied before authentication.".... now i assume i need authorized mi account to flash the rom but i dont have one and i see no way of getting one. I am currently on fake rom on a global version of the phone (the one with dual camera xiaomi note 5)
What i want right now is to flash any rom that can request for bootloader unlocking since in this fake rom that is disabled and my loader is locked..
any help?
This forum is for Redmi 5 Plus / Note 5 (India).
Please go there and ask for help for your problem:
https://forum.xda-developers.com/redmi-note-5-pro
Best regards,
skrubxgt
Use EDL mode if your device bricked and it works only with designated rom, china to china and global to global because in this case your bootloader is locked. And before proceeding flashing thru EDL, you have to prepare eveything properly, such as disabling driver signature enforcement and installing correct driver (QD Loader 900D)
So, have you prepared and done all those things properly? 2 days ago I just flashed my device thru EDL due to failure flashing and now my baby is waking up

Help on unlocking bootloader, RN4 Snapdragon

Hi there, so recently I bought a Redmi Note 4x from a Chinese seller in an online shopping store on our country.
I opened it up to see MIUI 8 but all in Chinese, though I managed to get it to English. Got it upgraded (OTA) to MIUI 9 and 10 global stable.
When I try to unlock the bootloader (new method), I always get error 20091 on Mi Unlock Status, even though my account has been binded to my phone.
I even tried Mi Unlock tool, but it returns an error after hitting 99% *see attachment (63)*.
I'm really puzzled by this since I just found out the phone wasn't an official global version. (Thru xiaomi product verification) so I decided to try and do something about it. I even tried shifting from Global stable to Global developer, still no luck, the same errors appear on Mi Unlock status and Mi Unlock app.
I even went as far as disassembling the phone and forcing it into EDL test point mode, and then flashing global developer fastboot rom via MiFlash as stated on this guide https://c.mi.com/thread-1479882-1-0.html but still I cant unlock my bootloader and the same problems appear.
UPDATE: I also tried using an unofficial unlock tool (which made my shift from global stable to global dev possible) but the xiaomi unlock server returns me error 20038 *see attachment (64)*
I really need some help since I want to unlock its bootloader and mod this phone.
Ps. btw, I even tried using different Mi Unlock tool version, but still got the same set of problems.
That link you shared is very good. I'm really surprised that it didn't work for you.
Sent from my Redmi Note 4 using Tapatalk
forgot to add the attached image with the chinese error
Spukey said:
That link you shared is very good. I'm really surprised that it didn't work for you.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I'm even surprised it didnt work....maybe it has something to do with my hardware itself. I do think my hardware isnt made by xiaomi, since when I opened it up, only thing I saw (that i think made by xiaomi) is the battery....does it ring any bells?
Did you solve the problem? I have a Redmi Note 8 and the xiaomi server is responding with the same code:/
idaxd said:
Did you solve the problem? I have a Redmi Note 8 and the xiaomi server is responding with the same code:/
Click to expand...
Click to collapse
Error 20091 on Mi Unlock Status was a cause of the situation that your phone was binded to another Mi Account (probably the first owner of your phone if you bought it on the cheap). This altogether explains why I have that weird chinese error with something like a Mi Account ID in the error message in Mi Unlock. Error 20038 is also the same problem in the case of the XiaoMi Unlock Tool unfortunately.
The only way to resolve this would be to ask the previous owner of the phone to unbind the phone from his/her Mi Account and then trying to bind again, at least that's what I read on Mi Community Forums (Reference: https://in.c.mi.com/thread-1731805-1-0.html)
I also have error 20091 on my phone now.... trying to unlock the bootloader.
Really hoping to see ways to solve it.
Hello. I have a Redmi Note 4 Snapdragon 64 GB which I bought used and the last user didn't log out before doing a fabric restoration and I cannot unlock the bootloader and I get an Error 20038 in XiaoMiTool-V9.11.10 (Error 20091 on Mi Unlock).
I have downloaded mido_global_images_8.12.20_20181220.0000.00_7.0_global_3947ba5143.tgz (mido_developer_fastboot), modded rawprogram0.xml, added persist.img, entered in EDL mode (with testpoint) and flashed and when starts for the first time i get a message that says "This device is locked" and "Activate this device" but I have not the original account used to bind it.
Then, now I am in a worst scenario because I didn't get to UBL and I cannot use it with MIUI. Now it is a bricked device.
Any idea of how I can get out of this situation?
Thank you very much
korolirio said:
Hello. I have a Redmi Note 4 Snapdragon 64 GB which I bought used and the last user didn't log out before doing a fabric restoration and I cannot unlock the bootloader and I get an Error 20038 in XiaoMiTool-V9.11.10 (Error 20091 on Mi Unlock).
I have downloaded mido_global_images_8.12.20_20181220.0000.00_7.0_global_3947ba5143.tgz (mido_developer_fastboot), modded rawprogram0.xml, added persist.img, entered in EDL mode (with testpoint) and flashed and when starts for the first time i get a message that says "This device is locked" and "Activate this device" but I have not the original account used to bind it.
Then, now I am in a worst scenario because I didn't get to UBL and I cannot use it with MIUI. Now it is a bricked device.
Any idea of how I can get out of this situation?
Thank you very much
Click to expand...
Click to collapse
I think the best course of action here is to ask the person whom you bought the phone from for help. If you are from Philippines and bought RN4X from Lazada on some cheap deals, then you've got a big problem returning it nor getting help from the seller.
techfreak9356 said:
I think the best course of action here is to ask the person whom you bought the phone from for help. If you are from Philippines and bought RN4X from Lazada on some cheap deals, then you've got a big problem returning it nor getting help from the seller.
Click to expand...
Click to collapse
The person who sold me the mobile says that he doesn't know who created this MI account and then is not possible to do the unlock in the proper way. I have a mobile phone that has a key to protect it but I have not the key and the person who sold me neither.
What about this? https://romprovider.com/bypass-mi-account/

Redmi note 5 MEE7S problem

Hi, I have a redmi note 5 MEE7S. It actualy is buggy running MIUI V9.5.19.0.OEIMIFA stable global. I am able to connect to the phone ADB, fastboot and EDL.
Problem is : MIUI tells me that bootloader is unlocked but fastboot and all the MI utilities tell me that the bootloader is locked. Therefor I can't go trough the bootloader unlock process from Xiaomi as for MIUI it is already unlocked ! So I'm stuck....
I can't upgrade the phone to any official ROM by selecting manualy the package, I get the message : "can't verify update. Current version is illegal, only allowed to flash stable version".
The upgrade package I tried is a stable version ...
Any help would be nice.
Thanks

Categories

Resources