Hi!
Yesterday I rooted my LG P500, then I wanted to make a backup from CWM from the phone. Now the I stucked in fastboot mode.
I have read many articles about this problem, and I could solve it, but my computer (win7 64 bit) cannot detect the phone correctly. I have tried with a lot of drivers, official ones, unofficial ones, but no connection can be made to the device.
In the device manager a single unknown device called "Android" can be found. Can anyone help me? Thanks.
Senki1988 said:
Hi!
Yesterday I rooted my LG P500, then I wanted to make a backup from CWM from the phone. Now the I stucked in fastboot mode.
I have read many articles about this problem, and I could solve it, but my computer (win7 64 bit) cannot detect the phone correctly. I have tried with a lot of drivers, official ones, unofficial ones, but no connection can be made to the device.
In the device manager a single unknown device called "Android" can be found. Can anyone help me? Thanks.
Click to expand...
Click to collapse
Fortunatelly I could unbrick the phone by using lgmdp. After I got recovery console and I could restore my rom.
Senki1988 said:
In the device manager a single unknown device called "Android" can be found. Can anyone help me? Thanks.
Click to expand...
Click to collapse
Force Windows to install the Android Single Sooner Interface by going thru the steps to manually update/install a driver.
Related
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html
doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow
Did you install those libraries properly?
Freshly baked from my Nexus 5
This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.
Hello, thanks for reading.
I want to start by saying I'm not asking how to fix my phone. All I need to know is how to make my computer recognize my phone so I can give it commands via adb/fastboot. And if you can help me I'd be happy to buy you a beer!
After that I think I can figure out the rest. I've been searching threads and trying things for weeks with no avail. My problem is similar to many, but slightly different so I really do need help. My LG G2 D801 is stuck in Fastboot Mode.
But my primary problem is that my computer doesn't recognize my phone in fastboot or adb, even with Official LG G2 D801 drivers.
I'll try to briefly and clearly describe my situation and what I've tried.
Long Story Short:
1. I rooted using TowelRoot method.
2. I broke my Recovery by trying to flash TWRP using an app called Flashify.
3. I attempted OTA update in spite of my broken Recovery and bricked my phone.
4. Now my phone only shows LG logo, then goes to Fastboot. (XXX = numbers change each time)
Fastboot Screen:
"[XXX] fastboot mode started
[XXX] udc_start ()"
5. Won't boot into Recovery or Download Mode.
6. So on my PC (Windows 8.1) I first cleared all Android drivers, then installed the official LG G2 D801 drivers, and Android Studio with ADB.exe and Fastboot.exe. I also tried different usb ports and cords.
7. But my PC doesn't recognize my phone, so when I run the command "list adb devices", my phone does not appear (However, my Brother's Kindle Fire, Galaxy Note 3, and Galaxy Note 2 show so it's just me). Perhaps this means I never checked USB debugging?
8. If someone can help me I'd be happy to buy them a beer:highfive:. Thanks for reading and I appreciate any help!
9. I should also mention that I also have access to a Linux computer running Ubuntu, although I'm not very familiar with that OS.
My Device's Information:
LG-D801 running LG's stock 4.2.2.
Software version D801V11b
Build Number JDQ39B
Kernel Version 3.4.0
I think I had your similar situation. Go here: http://www.koushikdutta.com/post/universal-adb-driver
Download and install that msi, it will install a universal driver that helped my PC see my phone when no other drivers could.
BrotherPanan said:
I'd be happy to buy you a beer!
Click to expand...
Click to collapse
If I helped you, I'm a Guinness type of girl
I happily accept donations
<--
Hello Friends,
Now i m going to tell you everything which everyone should keep in mind to avoid bricking our beloved Moto G.
I have unlocked my bootloader to enjoy full root features in my mobile.So rooted it on lollipop stock rom.
And found that some old Gameloft HD games like 9MM,tintin etc shows incompatible handset.So tried to change build.prop file in /system folder to convert my mobile name to Samsung Galaxy S2 to install the incompatible games and then messed up everything and my phone won't restart but however bootloader, recovery is working.
In this step I should have tried to restore my original build.prop file by using adb commands or fastboot commands.But I didn't knew this and tried factory reset in recovery menu which didn't help and adb commands failed to work.
Then I searched online and used fastboot commands to flash to 4.4.3 Stock Rom and it worked fine.
I should have left my mobile in this Rom.
But official 4.4.4 system OTA file didn't let me do that which in turn made my mind to download and install 4.4,4 OTA
and here goes my problem,Downloaded successfully and tried to intsall but it didn't
My phone won't boot,no recovery,no bootloader,no adb ,atleast no fastboot commands
except qhsusb_bulk shown in devices and sometimes usb input device or vmware usb device with white led light blinking
Anyone faced similar problem and got solution .Please Help
Reserved for any solutions
This could help
Hi!
I'm on the same problem but with a Moto X 2014. I've found this page (shown below). I tried the qboot program but I've got a fail while starting fastboot. I was thinking that the problem might have been windows 10. Now I'm back to windows 7 and I'm trying to get the qhsusb_bulk device detection.
allfreeperks.in/2015/01/unbrick-how-to-repair-and-recover-from_9.html
by the way, have you found any solution? I'm still trying to get the qhsusb_bulk device recognized by windows 7 and I don't know why I can't get there.
androidsatti said:
Hello Friends,
Now i m going to tell you everything which everyone should keep in mind to avoid bricking our beloved Moto G.
I have unlocked my bootloader to enjoy full root features in my mobile.So rooted it on lollipop stock rom.
And found that some old Gameloft HD games like 9MM,tintin etc shows incompatible handset.So tried to change build.prop file in /system folder to convert my mobile name to Samsung Galaxy S2 to install the incompatible games and then messed up everything and my phone won't restart but however bootloader, recovery is working.
In this step I should have tried to restore my original build.prop file by using adb commands or fastboot commands.But I didn't knew this and tried factory reset in recovery menu which didn't help and adb commands failed to work.
Then I searched online and used fastboot commands to flash to 4.4.3 Stock Rom and it worked fine.
I should have left my mobile in this Rom.
But official 4.4.4 system OTA file didn't let me do that which in turn made my mind to download and install 4.4,4 OTA
and here goes my problem,Downloaded successfully and tried to intsall but it didn't
My phone won't boot,no recovery,no bootloader,no adb ,atleast no fastboot commands
except qhsusb_bulk shown in devices and sometimes usb input device or vmware usb device with white led light blinking
Anyone faced similar problem and got solution .Please Help
Click to expand...
Click to collapse
langelog said:
Hi!
I'm on the same problem but with a Moto X 2014. I've found this page (shown below). I tried the qboot program but I've got a fail while starting fastboot. I was thinking that the problem might have been windows 10. Now I'm back to windows 7 and I'm trying to get the qhsusb_bulk device detection.
allfreeperks.in/2015/01/unbrick-how-to-repair-and-recover-from_9.html
by the way, have you found any solution? I'm still trying to get the qhsusb_bulk device recognized by windows 7 and I don't know why I can't get there.
Click to expand...
Click to collapse
Nope
No solution till now
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
gl411 said:
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
Click to expand...
Click to collapse
Have you installed the Qualcomm driver?Its very tricky,Windows wont allow to install it easily.
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
gl411 said:
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
Click to expand...
Click to collapse
It should be the driver problem,no other choice.
maskelisuvari said:
It should be the driver problem,no other choice.
Click to expand...
Click to collapse
The easiest way for unbricking oneplus (yes, I tried it): http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
ColourOS firmware has all needed files for proper flashnig, including right tool for doing that.
Only thing that didnt work on my Win 8.1 x64 was drivers mentioned in post above.
I had to use this QHSUSB_DLOAD drivers from member DallasCZ (that I used for unbricking ZTE v9180). Only with that drivers my Windows recognized bricked phone and Flash tool could find and flash it.
Flash tool in only on chinese, that is a bit problem, but instructions given in post I linked are more/less usefull.
This is a link to DallasCZ shared folder with qhsusb drivers:
https://drive.google.com/folderview...&usp=sharing&tid=0B1T7tp6tJ_3kQkZSWjNsazJZbGc
If you are sure the driver is okay,plug in the usb cable and out and in,until you see the green line on the tool.Also you can follow the guide as in below link:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
The same thing but this time you can flash CM11s instead of ColorOs.Also there is a video.Pls check it.
Ok so I did the process over and over again, the sixth computer did it right! I was back on ColorOS and now back to CM11S.
This thread can be closed, thanks for the help!
No problem,glad to hear you solved the problem
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
WhiteCoffeeCat said:
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
Click to expand...
Click to collapse
Thanks for the suggestion! I will attempt these. Fingers crossed
I have previously attempted to install adb driver but had some trouble. When installing using Device Manager, the locate .inf dialog refuses to accept my selection. I dont seem to be any error. When attempting to do so via the folder (and sub folders) it says no drivers found. Perhaps i'm doing this totally wrong?
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
eshlad said:
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
Click to expand...
Click to collapse
Put Windows into testing mode before installing drivers in Miflash, adb.. Run cmd prompt as admin and type bcdedit -set TESTSIGNING ON or bcdedit -set TESTSIGNING OFF for disabling testing mode.
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
how?
goila said:
how?
Click to expand...
Click to collapse
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
jholfran3 said:
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
Click to expand...
Click to collapse
Thanks, but that doesn't help, otherwise I've already done it. I had m1 mac and with parallel desktop only the possibility to install win 11.. win 11 sucks.. I installed win10 on an intel mac in parallel and that solved my problem
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
ItsmeeVishal said:
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
Click to expand...
Click to collapse
Have you tried to disable driver signature enforcement in windows 11.
istampal said:
Have you tried to disable driver signature enforcement in windows 11.
Click to expand...
Click to collapse
Yeah, i tried it.
Nothing happened.
ItsmeeVishal said:
Yeah, i tried it.
Nothing happened.
Click to expand...
Click to collapse
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
eshlad said:
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Click to expand...
Click to collapse
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
What VM were u using?
I'm using parallels Desktop 18
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
I tried to do what u said but don't know what to do next.
Plz see the attached video video and tell me what wrong I'm doing.
After clicking on legacy hardware, what are other steps......
And, thank you so much for reply!
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Titek said:
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Click to expand...
Click to collapse
Hi Tek,
I have had many issues with windows and fastboot,
some cables would work with some of the ports and then not.
My pc has 12 usb ports, yet it was still hit and miss whether fastboot would work on my Poco F3.
I tried your tip and after using a cheapy Targus 4 port usb adaptor, my "FASTBOOT PROBLEMS ARE NOW SOLVED"
now what am i going to do with my 7 surplus USB-C Cables
Many thanks for your TIP