So I just got my Mi Pad in the mail and I want to install the global ROM for it, but it's not showing up in either of the unlocking tools. I got all the drivers installed including the google dev stuff. If I open the program and log into my account it says it's not connected, if I use the batch unlock tool it doesn't show up. It goes into Fastboot just fine and it's connecting to my PC without issue. USB debugging is on, device is linked to my account etc...
Not sure what i'm doing wrong.
Found a solution. I downloaded this tool https://www.xiaomitool.com/V2/
I ran it, and tried to unlock it through the V2 program, didn't work - I got an error. But when I went to the regular MiUnlock tool it FINALLY saw my device and started the process. Not I just gotta wait 196 hours.
Related
Hi Guys so I received my mi mix 2, more than 72 hours ago, bound my account to the phone in dev options, logged in online to miui, cloud etc and on the phone , enabled usb debuging
Used MiFlash latest version 2.x - Then i saw theres a new 3.3.4 Version - Signed in Clicked unlock went all the way to 100% then said wait 72 Hours...... Ok now ive waited
Been trying and 20 times im getting " Couldn't Verify Device' Unknown Error (-1) "
Im used to flashing and unlocked and this is first time a xiaomi device has done this, Ive checked and adb devices are working.... BUT when i boot to fastboot and fastboot devices its blank , ive installed the ADB drivers and the xiaomi usb drivers over and over again... Windows is in test mode, Windows 10 64bit test mode.
Fast boot devices is always blank...... Any Ideas.........Oh and i was on global stable, now ive updated to the latest global Dev 8.0 rom from miui website - Still no luck
Ok so ive narrowed it down to the USB-C cable, is not keeping fastboot active
Ive just tried it with a redmi 5 device with old micro usb and fastboot devces gets picked up every attempt....
My mi mix 2 detects fastboot for a few seconds then seems to go off..... Very strange and also annoying - Any Hel would be most appreciated.. Ive posted on senerex thread sorry but thought have more chance of help if i started a new thread here:fingers-crossed:
The same is happening to me, anyone nows how to fix this?
Having the same problem here with this device.
Fastboot seems to be working for the first couple of seconds after device is being connected via USB. I'm even able to get output for "fastboot oem device info". But after 2-5 seconds any fastboot command stucks and outputs either nothing or "<waiting for device>" until device is being unconnected. When device is unconnected, fastboot outputs error "no such device" and exits with status code 1.
Tried Ubuntu Linux with the latest version of sdk-tools installed. Also tried Windows 8 in Virtualbox with Google drivers and Mi PC Suite. Tried to connect Huawei P20 to the same PC and using the same cable and it worked.
Did you find any solution? Could it be so that fastboot is somewhat broken on my device?
zerodi said:
Hi Guys so I received my mi mix 2, more than 72 hours ago, bound my account to the phone in dev options, logged in online to miui, cloud etc and on the phone , enabled usb debuging
Used MiFlash latest version 2.x - Then i saw theres a new 3.3.4 Version - Signed in Clicked unlock went all the way to 100% then said wait 72 Hours...... Ok now ive waited
Been trying and 20 times im getting " Couldn't Verify Device' Unknown Error (-1) "
Im used to flashing and unlocked and this is first time a xiaomi device has done this, Ive checked and adb devices are working.... BUT when i boot to fastboot and fastboot devices its blank , ive installed the ADB drivers and the xiaomi usb drivers over and over again... Windows is in test mode, Windows 10 64bit test mode.
Fast boot devices is always blank...... Any Ideas.........Oh and i was on global stable, now ive updated to the latest global Dev 8.0 rom from miui website - Still no luck
Ok so ive narrowed it down to the USB-C cable, is not keeping fastboot active
Ive just tried it with a redmi 5 device with old micro usb and fastboot devces gets picked up every attempt....
My mi mix 2 detects fastboot for a few seconds then seems to go off..... Very strange and also annoying - Any Hel would be most appreciated.. Ive posted on senerex thread sorry but thought have more chance of help if i started a new thread here:fingers-crossed:
Click to expand...
Click to collapse
Is your bootloader unlocked ? Usb debugging enabled? Nothing is wrong with your usb cable. Check your bootloader. If it's still locked download Xioami Tool, not MiFlash. Don't ever use MiFlash, Google and download XioamiTool. It can do everything and bring your phone back to life if you brick it. Make sure to buy the developer a coffee if it works.
---------- Post added at 09:35 AM ---------- Previous post was at 09:32 AM ----------
Use this to fix the problem.
http://www.xiaomitool.com/
zerodi said:
Hi Guys ..........
Been trying and 20 times im getting " Couldn't Verify Device' Unknown Error (-1):
Click to expand...
Click to collapse
Probably a stupid comment but have tried connectng to USB 2.0? I have with other devices earlier had problems when connecting to USB 3.0.
Sorry if this is the wrong thread.
Hello guys, I have a Redmi Note 5 (Global Version) with Snapdragon 636, and this phone is really amazing. I'd like however to unlock its booloader so I can install Pixel Experience on it, as I'd like to use other roms than MIUI. The issue is, well, I can't.
Something really strange happens: if I connect my phone via USB 2.0 to my computer, it is recognized as usual. It appears in Device Manager, is recognized by ADB, no problem. Then I reboot in fastboot mode and the device is still there. However, the EXACT moment I open Mi Unlock Tool, without clicking anything (Agree or logging in to my mi account) the phone is instantly disconnected and the "Press any key to shutdown" message appears on the top-left of my phone's screen.
Stuff I've tried:
- made sure OEM unlocking and USB debugging are on
- installed Mi Unlock tool in C:
- installed the ADB drivers in C:/Program Files
- disabled integrity checks from CMD
- installed and checked the MiUSBDriver umpteen times
- used 4 different versions of Mi Unlock Tool (1.0, 2.2, 2.3, and 3.3 - 1.0 halts at 50%, the other 3 won't detect my phone at all)
- made sure the device is bound to my Mi Account
I've tried using Hexerus' guide here (post #18) and everything seems to work fine, until step 6 when my phone instantly disconnects when opening Mi Unlock Tool.
Do you guys have any ideas? Thanks.
use usb 2.0 cable and port
devcon69 said:
use usb 2.0 cable and port
Click to expand...
Click to collapse
Used USB 2.0, didn't work
Happened with me before, and I looked Google and found some solutions like installing the drivers again and using old miunlock tool and using different USB Socket however, none of theme worked,
Next day I opened the laptop to try again and suddenly it worked!
I didn't know what exactly fixed it
After the 720 hours period, I have spent literally weeks of trying to unlock my device's bootloader and what I would add is to switch between computers. I'm running Windows 10 on my room computer and all I had with MiUnlock were errors such as device disconnecting once in fastboot, "Couldn't unlock" messages, chinese characters... Until I decided to use my 2005 Windows 7 desktop and wow !, device unlocked at first try ! No need any other trick
just uninstall Previous drivers or use Windows 7 PC,with latest drivers of ADB ,i also faced same problem:angel:
Hello guys, I have a Redmi Note 5 (Global Version) with Snapdragon 636, and this phone is really amazing. I'd like however to unlock its booloader so I can install Pixel Experience on it, as I'd like to use other roms than MIUI. The issue is, well, I can't.
Something really strange happens: if I connect my phone via USB 2.0 to my computer, it is recognized as usual. It appears in Device Manager, is recognized by ADB, no problem. Then I reboot in fastboot mode and the device is still there. However, the EXACT moment I open Mi Unlock Tool, without clicking anything (Agree or logging in to my mi account) the phone is instantly disconnected and the "Press any key to shutdown" message appears on the top-left of my phone's screen.
Stuff I've tried:
- made sure OEM unlocking and USB debugging are on
- installed Mi Unlock tool in C:
- installed the ADB drivers in C:/Program Files
- disabled integrity checks from CMD
- installed and checked the MiUSBDriver umpteen times
- used 4 different versions of Mi Unlock Tool (1.0, 2.2, 2.3, and 3.3 - 1.0 halts at 50%, the other 3 won't detect my phone at all)
- made sure the device is bound to my Mi Account
I've tried using Hexerus' guide and everything seems to work fine, until step 6 when my phone instantly disconnects when opening Mi Unlock Tool.
Do you guys have any ideas? Thanks.
Maybe something with Windows?
I wondered if the laptop could be indeed the problem... I do have another laptop (for now), should I try using it tomorrow?
Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
"I know that I won't get any unlock at the moment as the wait period is not over. "
You managed to start the unlock timer using the tool though?
I think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after. (you load fastboot with power - & volume?)
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
sathariel74 said:
Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
Click to expand...
Click to collapse
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google... Then click on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Mother_Teresa said:
You managed to start the unlock timer using the tool though?
Click to expand...
Click to collapse
Well, I don't see any timer in the tool. However the new flash tool doesn't seem to promising (that batch one). Also in XiaomMiTool I don't see any timer. So maybe the registration is already messed up?
Mother_Teresa said:
think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after.
Click to expand...
Click to collapse
Well, this one does not work for me as it is locked...so I suppose this is a dead end at the moment. Tried this in Linux (I am more comfortable with).
Mother_Teresa said:
(you load fastboot with power - & volume?)
Click to expand...
Click to collapse
Yes, I actually do that usually (besides of the automatic Fastboot loading from XiaoMiTool).
Mother_Teresa said:
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
Click to expand...
Click to collapse
Yes, it gives some connected sound in both modes (normally booted - can even mount the phone storage - and in fastboot). Not sure about the device correctly installed when in fastboot - I tried to follow some threads/videos on that but somehow it looked different for me.
X0PIRAT3 said:
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google..; Clique on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
sathariel74 said:
...
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
Click to expand...
Click to collapse
Yay, well done.
I kept default MIUI and rooted with Magisk (install this in Magisk app to fix safetynet pass).
More details here.
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
sathariel74 said:
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
Click to expand...
Click to collapse
Not to bash etc but what is so bad?
I installed my preferred launcher (Nova) and it works for being a familiar front-end.
Options and tweaks are mostly there these days in the settings (fe. flashlight on double-press) and if not there is root.
is it bloatware? (if so, can we fix it? )
Lineage is of course a safe bet and I probably end up trying some but I need some encouragement .
BTW: beware the Miu Flash tool not enabling 'lock device' when flashing.
edit: how to use smileys. Now it seems super happy but without it seems so serious....
Well, besides of lack of trust (which is most likely just my issue), I really dislike that "all at startscreen" quite a lot. And yes, those 20-30 apps that I was able to delete plus the 20 apps I would like to delete are another thing showing me that this ROM is not for me. Especially that memory manager stuff that enables your "high performance game experience" is a sign to better stop using MIUI. There are also some bugs (strange behaviour I saw/felt - can't even really describe) I didn't like.
I like to manage my stuff myself, even if this is more work. But I somehow know how its "glued" together. So LineageOS is what I like. Or some of the other AOSP ROMs available.
Hi , Recently I purchased a Poco f3 and I am extremely Frustrated about to unlocking its bootloader. I will tell you Step By step what I did,
1. Mi Unlock Status (account added)
2. OEM unlocked checked/turned on
3. USB debugging checked /turned on
4. Waited more than 8 days
Problem started now!!
5. After waited 8 days, I Connect it with my computer
6. Software use to unlock it was official unlocking software
7. send me verification code after log in , tried 3 times , never show up any text's from xiaomi what so ever. Can not do unlocking until 24 hours again as already tried 3 times a day and no text messages.
8. Tried many ways , no result to get that code (extremely frustrating)
Very strange part:
9. Next day tried with 3rd party / official old version of "FASTBOOT to EDL Tool" , it taken my ID and password and logged in directly without verification OTP/ phone number verification.
10. I was so happy to saw that at least it is detected by my computer
11. Tried to bootloader unlock, "I have to wait another 148hours" Damn it already waited more than that.
12. Now , after that I tried to connected with my computer , but each time I am connected with USB cable (tried several cable both type C and 2.0 port) , it does not show up any phone on "Fastboot to EDL tool" anymore. Doesnt matter official or non official tool.
13. At least I want to see My phone is connecting with my computer properly and after waiting days and days, I dont want to mess these things again.
14. Xiaomi Mi Tool V2 (by Francesco Tescari) is detecting my phone.
MY QUESTION IS What I am missing here that is now allowing me or doesnt show up on the official unlocker tool ?? I tried every possible driver. This is the exact problem I faced last year and could not fixed. Did not have time to look in to it then.
Please help me to unlock my Bootloader. its a humble request.
Install all drivers until it detects your phone on v2 unlock tool.
Then use the official mi unlock tool and then unlock it.
Heaps of YouTube video
xijaw said:
Install all drivers until it detects your phone on v2 unlock tool.
Then use the official mi unlock tool and then unlock it.
Heaps of YouTube video
Click to expand...
Click to collapse
Thank you for your help my Dear. I already did that. believe it or not, it showed me 1 time Unlock tool but after that it doesnt showing me anything. Do you have any recommendation like specific software or YouTube video ?
droptech75 said:
Thank you for your help my Dear. I already did that. believe it or not, it showed me 1 time Unlock tool but after that it doesnt showing me anything. Do you have any recommendation like specific software or YouTube video ?
Click to expand...
Click to collapse
Picture guide for unlock bootloader:
https://forum.xda-developers.com/t/4288121/post-85137959
Windows Driver issue is mentioned in Section 1 step 17.
Use official USB cable.
While your phone is under Fastboot mode, connect to PC with official USB cable and reboot your PC.
Make sure to login to your Xiamoi account on your phone and in the unlock tool.
More info (quick google) -> https://androidbiits.com/unlock-bootloader-poco-f3-m2012k11ag-easily/
and on your waiting periods time, dont re connect your mi account (at developers menu).
you press connect mi account, then it will reset your waiting time back to 168 hrs