Database Users

[Q] L01F no download mode, no usb reading.

Hello. Please help me. I have a Japanese version of G2 (L-01F - DoCoMo) and i tried to flash an european version of kitkat because i couldn't update in OTA. Now the phone is bricked, it is bootlooping, the Download Mode doesn't work, it shows a few of blue dots and it stays there (the phone can't be recognized on PC using the USB cable). I can enter the Recovery Mode (the grey screen with LG logo) where the phone can be read by PC and using ADB tool is shown as "recovery". I can't use fastboot.exe because the device is not being recognized. What can i do? Thank you very much. 

unkn0wn68 said:
Hello. Please help me. I have a Japanese version of G2 (L-01F - DoCoMo) and i tried to flash an european version of kitkat because i couldn't update in OTA. Now the phone is bricked, it is bootlooping, the Download Mode doesn't work, it shows a few of blue dots and it stays there (the phone can't be recognized on PC using the USB cable). I can enter the Recovery Mode (the grey screen with LG logo) where the phone can be read by PC and using ADB tool is shown as "recovery". I can't use fastboot.exe because the device is not being recognized. What can i do? Thank you very much. 
Click to expand...
Click to collapse
Can someone help me please ?

unkn0wn68 said:
Can someone help me please ?
Click to expand...
Click to collapse
I have the same problem. Please tell me if you can fix it.
http://forum.xda-developers.com/lg-g2/help/device-conecting-to-pc-download-mode-t2996249

ronen1n said:
I have the same problem. Please tell me if you can fix it.
http://forum.xda-developers.com/lg-g2/help/device-conecting-to-pc-download-mode-t2996249
Click to expand...
Click to collapse
Actually i'm trying to repair it since October 2014. No-one knows the solution. I went to 3 different GSM Services and they don't know what to do...
So...when i'm trying to put it in download mode it stays like this and the PC doesn't recognize it.
The only way to connect the phone to the computer is to put it in recovery mode (Backup & Restore) by holding Volume Up and Power Button at the same time with the phone turned off. It should appear something like this. The PC recognizes the phone but only in ADB. Look.
The third possible screen, which also is useless is this by typing in the CMD the following: "adb reboot recovery" (click). Here, the PC doesn't recognize the phone too.
Fastboot doesn't work.
And that's my problem. I don't know what to do.

unkn0wn68 said:
The PC recognizes the phone but only in ADB. Look.
Click to expand...
Click to collapse
If there are any custom roms that will run on your phone, adb push it to the sdcard and flash in TWRP.

iowabowtech said:
If there are any custom roms that will run on your phone, adb push it to the sdcard and flash in TWRP.
Click to expand...
Click to collapse
I have permission problems...

unkn0wn68 said:
I have permission problems...
Click to expand...
Click to collapse
?
Your screenshot above shows the device being recognized via adb in recovery. What permission problems?

[Q] Permanent problem with Unlocking Bootloader Nexus S

Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!

alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:

It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse

alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked

Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!

alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..

UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.

Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.

Q Mobile X 32
bootloader oem unlock problem
plz help

Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923

Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32

Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?

Here's what the guide says...

help! my g2 only boots into fastboot

I was trying to install a custom recovery (twrp) by several different methods, with absolutely no luck (but that's another secondary issue at this point) and i screwed something up. Not exactly sure but i think the last thing I did was:
using "Rashr - Flash Tool" i think i went to "flash kernel from storage" then flashed boot.img.
now the phone goes immediately, directly into fastboot even without being connected to computer.
so i tried getting into the stock recovery by holding "volume down" and "power" until lg logo, releasing the reholding until factory reset screen. after choosing yes 2 times i get a
"boot certicification verify" or something message for about a second then it goes to this screen (sorry but apparently i haven't had enough posts on the forums to include clickable links.)
h**ps://drive.google.com/file/d/0BwQdFsCQ9KZVaGM1eWdJb25WVVU/view?usp=sharing

slplsnphx said:
I was trying to install a custom recovery (twrp) by several different methods, with absolutely no luck (but that's another secondary issue at this point) and i screwed something up. Not exactly sure but i think the last thing I did was:
using "Rashr - Flash Tool" i think i went to "flash kernel from storage" then flashed boot.img.
now the phone goes immediately, directly into fastboot even without being connected to computer.
so i tried getting into the stock recovery by holding "volume down" and "power" until lg logo, releasing the reholding until factory reset screen. after choosing yes 2 times i get a
"boot certicification verify" or something message for about a second then it goes to this screen (sorry but apparently i haven't had enough posts on the forums to include clickable links.)
h**ps://drive.google.com/file/d/0BwQdFsCQ9KZVaGM1eWdJb25WVVU/view?usp=sharing
Click to expand...
Click to collapse
if u still have acces to fastboot use this or u see many disk at windows use srktool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076

amin44 said:
if u still have acces to fastboot use this or u see many disk at windows use srktool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Click to expand...
Click to collapse
ok, i do have access to fastboot (actually, as soon as i power it on, it immediately is in foastboot mode, even without being connected to computer). i tried using srktool's repair tools via fastboot. it seems like it's working (ie phone shows that it receives command) but that's it. does it take a loooooong time or something?
btw, i can also get into download mode by holding "vol up" while plugging into computer. so, i tried using srktool utilites via download mode and nothing.
also, i just noticed that while connected to computer in download mode, in device manager it shows G2 under "portable devices" with an exclamation point on it.

slplsnphx said:
ok, i do have access to fastboot (actually, as soon as i power it on, it immediately is in foastboot mode, even without being connected to computer). i tried using srktool's repair tools via fastboot. it seems like it's working (ie phone shows that it receives command) but that's it. does it take a loooooong time or something?
btw, i can also get into download mode by holding "vol up" while plugging into computer. so, i tried using srktool utilites via download mode and nothing.
also, i just noticed that while connected to computer in download mode, in device manager it shows G2 under "portable devices" with an exclamation point on it.
Click to expand...
Click to collapse
are u sure u do not have franken phone open battery cover and see model written inside motherbord

amin44 said:
are u sure u do not have franken phone open battery cover and see model written inside motherbord
Click to expand...
Click to collapse
I haven't taken the back off (yet) but all indications are that it's an AT&T (D800).
What part of my description makes you think that it might be a franken phone?

Did you try connecting the phone in download mode or fastboot to the LG Mobile Support Tool and performing an upgrade recovery?

audit13 said:
Did you try connecting the phone in download mode or fastboot to the LG Mobile Support Tool and performing an upgrade recovery?
Click to expand...
Click to collapse
not sure what you mean by "lg mobile support tool". i googled it and found and installed "lg pc suite". is that the same thing?
nevermind that last question. i found and installed and tried the upgrade recovery tool but for some reason the phone wont go into download mode anymore. when i power it up whith ""vol +" help down, it shows download mode for a second, but then goes right into fastboot mode.

Is it recognized by the program in fastboot mode?
Here's the program I was referring to: http://www.lg.com/ca_en/support-mobile/lg-LGD803
Even though the program says it is for the 803, I used it to recover my international d802.

slplsnphx said:
not sure what you mean by "lg mobile support tool". i googled it and found and installed "lg pc suite". is that the same thing?
nevermind that last question. i found and installed and tried the upgrade recovery tool but for some reason the phone wont go into download mode anymore. when i power it up whith ""vol +" help down, it shows download mode for a second, but then goes right into fastboot mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

amin44 said:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
Thanks for the reply! But when I have phone connected to USB in fastboot, it shows up in device manager as "android device > USB modem phone port". Is that method the right fix for my situation?

ok, so likei said my phone is indeed in fastboot mode, connected to computer via usb (shows up in device manager as "android device > USB modem phone port". using srktool, i can send commands to the phone (command shows up on phone but thats it.....doesnt matter what command, it just sticks there until i unplug the phone then srktool shows the operation competed and phone shows
https://drive.google.com/file/d/0BwQdFsCQ9KZVSVg3OTZLcXV0N0E/view?usp=sharing
but none of operations actually complete on the phone.

slplsnphx said:
Thanks for the reply! But when I have phone connected to USB in fastboot, it shows up in device manager as "android device > USB modem phone port". Is that method the right fix for my situation?
Click to expand...
Click to collapse
that method fix for all situation

amin44 said:
that method fix for all situation
Click to expand...
Click to collapse
ok i shorted the capacitors, and eventually have gotten to where i can get into twrp. i assume that is serious progress, but what do i need to do next?

slplsnphx said:
ok i shorted the capacitors, and eventually have gotten to where i can get into twrp. i assume that is serious progress, but what do i need to do next?
Click to expand...
Click to collapse
flash stock ROM via download mode or flash custom ROM via twrp.
the first choice (stock ROM) is better

thanks for the responses!!
before i saw your reply, i flashed the stock .tot firmware and now i have my phone back.
but, before all this started, it was lollipop(5.0.2) and now it's Jellybean(4.2.2). i bought phone on ebay, so im assuming that it got lollipop via an ota update. so now i'm looking into flashing it back to lollipop. what's the easiest method to install stock lollipop?

Moto G5 Plus "bricked" after update.

Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!

ZSparda said:
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
Click to expand...
Click to collapse
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?

Wolfcity said:
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Click to expand...
Click to collapse
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.

ZSparda said:
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
Click to expand...
Click to collapse
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?

PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.

Wolfcity said:
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
Click to expand...
Click to collapse
I tried to attach a couple of screenshots but I get the "bad request" message here. Anyways, when we do a normal boot we get the validation error message and we are sent directly to fastboot menu, but there we cannot choose any options because all of them lead to the error message again.
It's been a couple of weeks now but the last time we tried doing something, the device wasn't showing up in device administrator nor being recognized by adb.
As regards to the battery, we've left it charge up for some hours, so I guess that's not a problem, although we cannot see the percentage.

[email protected] said:
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Click to expand...
Click to collapse
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?

ZSparda said:
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
Click to expand...
Click to collapse
This thread is long, but alot of good info on hard bricked Moto G5 plus devices.
Code:
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
To get PC in test mode
Code:
Here is how to turn on or off the Test Mode feature in Windows 10.
IMPORTANT: Please remember that turning off the Test Mode feature may force the program/driver which is not digitally signed stop working.
Step 1: Open Command Prompt as administrator. To do so, type CMD in Start menu search to see Command Prompt in the search result. Right-click on Command Prompt entry and then click Run as administrator option. Click Yes button when you see the User Account Control screen.
Step 2: At the Command Prompt window, execute the following commands:
To enable the Test Mode:
Bcdedit.exe -set TESTSIGNING ON
To disable the Test Mode:
Bcdedit.exe -set TESTSIGNING OFF
If the above command didn’t work, this one must work:
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
You may exit the Command Prompt now.

[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Thanks! I'll send him all these so he can try. I'll update as soon as possible.

[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.

ZSparda said:
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
Click to expand...
Click to collapse
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about
Code:
fastboot devices
? It should show the device #. ADB doesn't always show devices.

[email protected] said:
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about ? It should show the device #. ADB doesn't always show devices.
Click to expand...
Click to collapse
Yes! Fastboot devices shows the device! So now we have to procede with the flashblank.zip and all that from the other post right? Also sorry for the late reply, I've been pretty busy these past days so I left him with all the work.

Ultra Bricked Mi 9t

Hi !
I need your help please, my phone doesn't want to enter in fastboot mode.
* Black Screen 100%
* If I press power button after 4 or 5 seconds it does a vibration
* Power button + Volume Up (looks llike it turn off the phone)
* Power button + Volume Down (looks like it want to enter in fastboot mode)
When my phone is connected to the PC it is recognized as: Unknown USB Device ( Device Descriptor Request Failed )
Blue LED always turned on (once the phone is recognized as Unknown)
The first that I tought when I saw the message ( Unknown USB Device ) was... ok this phone is really hard bricked and is needing a Test Point.
I did the Test point and my phone still giving the same message.
I tried different USB ports and same problem. (USB ports are ok)
I didn't tried a different USB cable and it has higher probabilities that my USB could be damaged. because (Device Descriptor Failed) is a problem from faulty USB ports or Cable.
But my USB Cable looks like new and it was used few times... also I tried moving a bit the connectors to see if it does something but no.. nothing happened.
The USB Port from the phone is like new. (I opened the phone)
If you have experience with the message: "Unknown USB Device (Descriptor Request Failed)
Please give me some help !

Hi !
Looks like the real problem was from drivers. Finally I installed the K20 drivers from this site : https://gsmusbdriver.com/xiaomi-redmi-k20
Then I did the test point
1) I Pressed power button with the test point
2) I heard a vibration
3) I released the power button but I continued with the test point
4) Voila the drivers were installed correctly and now my phone is recognized as: " Qualcomm HS-USB QDLoader 9008 "
EDITED:
If you are experiencing in device manager: USB Device Unknown Descriptor Request Failed maybe could be faulty USB port or cable. In my case was the cable. Now is working perfectly everything with a new USB Cable.

Now I'm trying to flash the phone using " Mi Flash Tool "
I downloaded the stock rom from Xiaomi site.. By the way my phone is with bootloader locked and is not rooted.
I pressed Flash button and the program asked for EDL Authentication. "I Created a new account" Logged suscessfull and then:
"Error" Root Element is missing.
WTF? why xiaomi is asking me for a rooted phone??
Please Help, any Idea about what I'm doing wrong?

romeosantos said:
Now I'm trying to flash the phone using " Mi Flash Tool "
I downloaded the stock rom from Xiaomi site.. By the way my phone is with bootloader locked and is not rooted.
I pressed Flash button and the program asked for EDL Authentication. "I Created a new account" Logged suscessfull and then:
"Error" Root Element is missing.
WTF? why xiaomi is asking me for a rooted phone??
Please Help, any Idea about what I'm doing wrong?
Click to expand...
Click to collapse
I think EDL is a special account authorised by Xiaomi.
Enviado do meu Mi 9T através do Tapatalk

Yeah u need a EDL Flash and for that an EDL verified Account, which u can't get anymore from xiaomi ..
you have to find someone who are willing to do it for you. Usually you have to pay for it .. around $50.
or try this
https://forum.xda-developers.com/showpost.php?p=79004670&postcount=82

solved said:
Yeah u need a EDL Flash and for that an EDL verified Account, which u can't get anymore from xiaomi ..
you have to find someone who are willing to do it for you. Usually you have to pay for it .. around $50.
or try this
https://forum.xda-developers.com/showpost.php?p=79004670&postcount=82
Click to expand...
Click to collapse
I went to S-Unlock and they said "Service offline" do you know or somebody know from other site? or someone that can help me?

romeosantos said:
I went to S-Unlock and they said "Service offline" do you know or somebody know from other site? or someone that can help me?
Click to expand...
Click to collapse
Did you try this :
- Download the stock ROM from xiaomi website, no tools needed, just adb and fastboot installed
- Extract the rom to a folder and launch "flash_all.bat" with admin.
- If you encounter an issue try it with another OS (try this if you don't want to install another OS : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755)
Tell us if it works.

Gimlouuuu said:
Did you try this :
- Download the stock ROM from xiaomi website, no tools needed, just adb and fastboot installed
- Extract the rom to a folder and launch "flash_all.bat" with admin.
- If you encounter an issue try it with another OS (try this if you don't want to install another OS : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755)
Tell us if it works.
Click to expand...
Click to collapse
Good news? I think that my phone now is booting on Fastboot mode? I don´t know how but today it was recognized by the PC as:
MTP USB Device
Please help What I can do to flash my phone¿? it is fastboot mode right? in fastboot mode I can do flash without an account authenticated righT?
Im trying to use Mi Flash TOOL again and Im getting this message:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Im using the latest rom for the K20 global phone but dont know why it is stuck with that message and STATUS: Flashing but it doesnt do any progress.
What Can I do?? is ok MTP USB Device? is that the correct drivers to do a flash in fastboot mode??
Thanks guys!

romeosantos said:
Good news? I think that my phone now is booting on Fastboot mode? I don´t know how but today it was recognized by the PC as:
MTP USB Device
Please help What I can do to flash my phone¿? it is fastboot mode right? in fastboot mode I can do flash without an account authenticated righT?
Im trying to use Mi Flash TOOL again and Im getting this message:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Im using the latest rom for the K20 global phone but dont know why it is stuck with that message and STATUS: Flashing but it doesnt do any progress.
What Can I do?? is ok MTP USB Device? is that the correct drivers to do a flash in fastboot mode??
Thanks guys!
Click to expand...
Click to collapse
Does the phone display the fastboot logo? If it does, then you have to remove some lines from the flash_all.bat file. The first ones where it says something about getvar product.

you can fastboot and just push it in cmd if fastboot active. I bever use bat files, because its only 2 lines to flash

yaro666 said:
you can fastboot and just push it in cmd if fastboot active. I bever use bat files, because its only 2 lines to flash
Click to expand...
Click to collapse
This is what happened:
I was watching my phone recognized as MTP USB Device and I tought yeah! my luck is from my side! now will be possible to flash my pohne in fastboot mode !!
I tried a lot of times with FLASH TOOL and it never passed from:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
then I tried in adb: "adb devices" but I never saw my device connected even with MTP USB Device driver activated in Device Manager.
so I tried anyway to use the flash_all.bat and same message received "getvar anti" bla bla..
I never deleted the lines about getvar from the file "flash_all.bat" because now my phone it is exactly as in the begin....
Now the PC doesn't want to recognize the phone... again the same ****.. " USB Device Unknown (Descriptor Request Failed) "
I did the test point and the same crap... the phone doesn't want to be recognized USB Unknown...
Come on... I can't believe it... I had decided to pay for the service flash with EDL authentication in the next week and now I can't even make it boot in EDL... exactly as in the begin I'm.... the phone it is with the same sympthoms.. :crying:
EDITED:
Now the Phone was recognized by the PC again as: MTP USB Device but with yellow sign..
I disconnected, reconnected the cable and nothing yellow sign.
I did the test point and boom Im back again into the same ****... USB UNknown (Descriptor Request Failed)
what the **** is happening?? Im not so sure how the phone can be recognized as MTP USB Device but i guess that it is fastboot mode. and that is what I want to try the solution from the first post of this threads.
or the second solution understand what I have to do to put the phone into EDL. Because I did a lot of times with sucess at the begin and now Im doing exactly the same and nothing. it doesnt want to work.
Looks like drivers problem?

romeosantos said:
This is what happened:
I was watching my phone recognized as MTP USB Device and I tought yeah! my luck is from my side! now will be possible to flash my pohne in fastboot mode !!
I tried a lot of times with FLASH TOOL and it never passed from:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
then I tried in adb: "adb devices" but I never saw my device connected even with MTP USB Device driver activated in Device Manager.
so I tried anyway to use the flash_all.bat and same message received "getvar anti" bla bla..
I never deleted the lines about getvar from the file "flash_all.bat" because now my phone it is exactly as in the begin....
Now the PC doesn't want to recognize the phone... again the same ****.. " USB Device Unknown (Descriptor Request Failed) "
I did the test point and the same crap... the phone doesn't want to be recognized USB Unknown...
Come on... I can't believe it... I had decided to pay for the service flash with EDL authentication in the next week and now I can't even make it boot in EDL... exactly as in the begin I'm.... the phone it is with the same sympthoms.. :crying:
EDITED:
Now the Phone was recognized by the PC again as: MTP USB Device but with yellow sign..
I disconnected, reconnected the cable and nothing yellow sign.
I did the test point and boom Im back again into the same ****... USB UNknown (Descriptor Request Failed)
what the **** is happening?? Im not so sure how the phone can be recognized as MTP USB Device but i guess that it is fastboot mode. and that is what I want to try the solution from the first post of this threads.
or the second solution understand what I have to do to put the phone into EDL. Because I did a lot of times with sucess at the begin and now Im doing exactly the same and nothing. it doesnt want to work.
Looks like drivers problem?
Click to expand...
Click to collapse
Most likely. I had similar issues with a rn7. Try it on another pc. I had issues getting the phone recognized in w10, then I switched to an old laptop I had with w7. Didn't install drivers, didn't do anything, windows installed it's driver and the phone was there. So it may be a issue with your OS. And again, delete the first two lines from the flash_all.bat to get over that error.
Edit: The flashing with MiFlash tool will only work if you see the fastboot logo on your phone. If the phone is seen in cmd after you type "fastboot devices".

attitude12 said:
Most likely. I had similar issues with a rn7. Try it on another pc. I had issues getting the phone recognized in w10, then I switched to an old laptop I had with w7. Didn't install drivers, didn't do anything, windows installed it's driver and the phone was there. So it may be a issue with your OS. And again, delete the first two lines from the flash_all.bat to get over that error.
Edit: The flashing with MiFlash tool will only work if you see the fastboot logo on your phone. If the phone is seen in cmd after you type "fastboot devices".
Click to expand...
Click to collapse
Thanks for the answer, I have the notebook with two windows.
W10 64 bits and W7 32 Bits.
Same problem in both, don't know how can be driver problem, because I installed exactly the correct versión. (I know that is the correct because I could do the test point correctly two days ago) and it was recognized as: "Qualcomm HS-USB QDloader 9008 (COM4)" But today it doesnt want to recognize anymore the phone. Only "USB Device Unknown (Descriptor Request Failed)"
So hard is to make it boot in EDL mode? i saw the picture for test point (k20 xiaomi) and it is really easy. but PC recognize the phone as Unkonwn after test point. The first day that I did the test point happened the same ****.. I was hours and hours trying to make it work.. till I installed the correct drivers. and now is happening the same.. hours and hours trying to boot in EDL and using the same drivers, same process, but nothing.
Except at 3:00 pm dont know how the phone was recognized as MTP USB Device (with yellow sign error in device manager) so i did again the test point and boom.. USB Unknown again...
If I press Power button + volume up the phone looks like turn off and instantly I do the connection from usb cable and nothing appears in device manager but 2 mins or 3 mins later the phone is recognized as unknown and blue led light start to blink every 1 second.
If i do the test point it is recognized instantly as Unknown but there isnt any blue led light blinking.
I tried test point without battery and same. problem.. I tried to do the test point without release the pins so fast.. and same problem I tried releasing fast.. slow... etc
I tried to removed the battery and press power button to drain all the energy from board.
I tried to charging battery with power supply and the blue led light is turned on after 2 mins and it continue on over 10 or 15 mins then it is off the blue light. I used a tester to see the voltage from battery and is ok looks like it is full of charge.
If I do the EDL Cable could it be different? or is the same as test point?
Thanks for your help guys you are good people!

Have you tried with Linux? With the distribution I mentioned?

Gimlouuuu said:
Have you tried with Linux? With the distribution I mentioned?
Click to expand...
Click to collapse
Hi! Thanks for your help.
The problem was the usb cable. Now works perfectly with a new cable. But now I have to unbrick it hahaha

romeosantos said:
Hi! Thanks for your help.
The problem was the usb cable. Now works perfectly with a new cable. But now I have to unbrick it hahaha
Click to expand...
Click to collapse
great, good news. To unlock it, go back at my first message.

Gimlouuuu said:
great, good news. To unlock it, go back at my first message.
Click to expand...
Click to collapse
Hi! Thanks! Yes I tried to flash in fastboot mode. I did adb devices command and it was recognized ok.
But when I tried to flash_all.bat it gave me error: "bootloader locked" looks like I need the bootloader unlocked to flash via ADB in fastboot mode.
what I want to try is like a bug in xiaomi mi flash tool. The first time that I tried to use it. I made a new account and I received a message like:
"Logged Suscessfull"
"Your Account was blind to this PC. Now you can start the process"
Then I received an error like "no root permission" or something like that (maybe was because the usb cable was bad)
Looks like the xiaomi flash tool passed the EDL Authentication. because now each time that Im trying to use MI TOOL this is the message that Im getting.
"Logged Sucessfull"
You are not authorized for this operation

romeosantos said:
Hi! Thanks! Yes I tried to flash in fastboot mode. I did adb devices command and it was recognized ok.
But when I tried to flash_all.bat it gave me error: "bootloader locked" looks like I need the bootloader unlocked to flash via ADB in fastboot mode.
what I want to try is like a bug in xiaomi mi flash tool. The first time that I tried to use it. I made a new account and I received a message like:
"Logged Suscessfull"
"Your Account was blind to this PC. Now you can start the process"
Then I received an error like "no root permission" or something like that (maybe was because the usb cable was bad)
Looks like the xiaomi flash tool passed the EDL Authentication. because now each time that Im trying to use MI TOOL this is the message that Im getting.
"Logged Sucessfull"
You are not authorized for this operation
Click to expand...
Click to collapse
Ok, suddenly you can not reinstall via all these methods because your bootloader is locked... Have you tried asking a member here if anyone has an EDL account (a real haha) ?