Database Info

[SOLVED] USB still not recognized (ICS Leak)

Edit:
This problem has been solved. For any of you that are having issues with ADB recognizing your phone, even after you have uninstalled and reinstalled the correct drivers (As I had done several times on 2 computers), a factory reset might be your answer. So, if you are on ICS leak, and the last thing you want to do is try to FXZ back to 2.3.6...Try wiping data/factory reset first. It solved my problem once and for all.
------------------------------------------------------------------------------------------------
First, I must say that I have already found similar threads of this type, and some even with solutions, but I still cannot fix this problem.
I am on ICS Leak on my AT&T Atrix 2 and everything is running great, aside from one thing. I cannot get my computer to recognize my device. When I plug it in, it will charge, but I get no USB options in my notification bar on my phone. I have tried other solutions, and I have installed the necessary drivers, (Windows 7), I have uninstalled and reinstalled, and rebooted with no luck. If anyone could help me, that would be great! Let me know if any more details are needed...

Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?

I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Sent from my phone's mind

Drgravy said:
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done
Click to expand...
Click to collapse
Sorry about the new thread. Blame it on the n00b status. I have rooted with this method before on the same model phone with ICS leak and it worked after a few unsuccessful tries. It usually shows some activity in the command prompt, but this time it is hanging at *daemon started successfully*
alteredlikeness said:
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Click to expand...
Click to collapse
I've tried in every connection mode, and I have the drivers installed. I've been trying every way possible. Also, for simplicity sake, could you tell me how to use the adb devices command? I'm tech savvy but pretty green to the development/programming side of things.

leifemagnuson said:
I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Also, once i uninstall Motorola Device Manager, do I have to manually uninstall more drivers, or does that get them all? If not, how do I manually uninstall the drivers?

http://forum.xda-developers.com/showthread.php?p=29609879
I was having the exact same issue where it was hanging at daemon started successfully. Was totally a driver issue. Follow the link in my link...
I would suggest completely uninstalling everything Moto from your PC, rebooting and then follow the steps again, being sure to install those new drivers that are linked in that post.
Edit: I'm trying to remember when I did it....but I seem to recall having a bit of weirdness when I installed the new drivers. I had the install driver wizard pop up while I was installing the drivers from the moto driver executable. I just let the wizard sit there and wait while the moto driver installer did its thing.

So, instead of uninstalling all that is Moto on my laptop, I moved the Moto Device Driver executable and the batch files (with Su and Superuser.apk and all the extras to my desktop. Ran the moto executable and plugged my phone in to install the drivers and rebooted the computer. Still nothing. Do i need adb on my desktop to root my phone? I'm getting flustered with this. It really should be working one way or the other....

Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app

devilhunter47 said:
Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I tried and tried to reinstall the drivers, and even installing them on a different PC didn't work. Finally, I did a factory reset, and the phone was recognized by ADB. Thankfully, I am now rooted and on SCv7!! (Thanks to Jimbridgman, Ikrasner, and a couple other devs.) Thank you all.

[Q] Unbricked successfully, ADB broken?

Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.

Does usb debugging is on?

Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?

If You use asus drivers it worth to try universal naked driver.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.

Hmm... How windows show tablet when You connect it to PC?

Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?

It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?

Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.

Try first remove all drivers and software for tablet. Then install universal naked driver.

Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.

[Help] Google Nexus 5 might be bricked

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.

Moto G USB Problem

Greetings, everyone!
Okay so a few days ago I fell asleep while using my phone, a Moto G 2014 (XT1068). At one point I wake up to see a window saying something along the lines of 'Updating X of X Apps" on a black screen. I put my phone on my bedside table and fall asleep again. When I wake up, the phone's off so I assumed it was done doing whatever it was doing (which I now think it was some sort of system update), so I turn it on only to find out it gets stuck in the Motorola logo loading screen. I've left it like that for maybe an hour and it's just stuck there. I've accessed Fastboot to try the Recovery option but it just returns a 'Boot Up Failed' message and if I choose the 'Factory' option (which I assume is a factory reset), it also gets stuck in the Motorola logo loading screen. The other options are 'Normal PowerUp', 'Barcodes' & 'BP Tools', none of them doing anything either. Upon some research, I figured it was probably some sort of update that crashed down the whole thing and that apparently a way to solve this would be to flash the phone with the Stock ROM, which I've already acquired (and hopefully it's the right one). Now, thing is, I need to connect my phone to the computer, which is running Windows 10, while on the Fastboot menu. This is where the problem comes in. I never enabled USB Debugging in the settings. I've also installed the Motorola Device Manager from the Motorola website because apparently it installs the drivers for the phone, but after installing the MDM countless times, I just don't see drivers anywhere. I've checked the Device Manager on Windows and there's no track of my phone's drivers in there whatsoever. There's no 'Other Devices' tab anywhere and my PC doesn't do that "device was plugged in" sound effect when you connect something through USB. I've downloaded ADB Drivers and different versions of Motorola Drivers but nothing seems to work. I've tried 6 different cables in 10 different ports, still nothing. The phone charges but it's like the PC doesn't detect it. While on the Fastboot menu, according to a few videos I've watched, it is also supposed to say a USB Cable is connected when you connect the phone to the computer, but even though my phone is connected to my PC, that never shows up. I don't know if this is because the drivers might not be installing on my computer or if it's because I never enabled USB Debugging in the settings. I've seen some people say it doesn't need to be enabled while in Fastboot but I don't know if that's true or not. So I'm pretty much out of ideas at this point, do you think something might be done?
Thank you in advance,
- Nervly

Hello, did you try typing in `fastboot devices` while in fastboot ?

-Hope- said:
Hello, did you try typing in `fastboot devices` while in fastboot ?
Click to expand...
Click to collapse
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).

Nervly said:
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Click to expand...
Click to collapse
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:

-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
<link>
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
I'm off to a job interview right now but I will try the disabling drivers signature method you suggested once I get back.
As for the device manager, showing hidden drivers still doesn't list the phone's drivers or the 'Other Devices' tab, sadly. Perhaps after I disable the drivers signature enforcement and try to install the phone's drivers again it will work. I'll keep you updated!
Thank you for the help thus far!

-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.

Nervly said:
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Click to expand...
Click to collapse
Fastboot drivers aren't same as USB drivers
They differ so if you want to work with fastboot you need fastboot drivers

Bricked OP7P USB Issues

Hi all,
I am have bricked my device, its in fastboot mode but wont do anything anymore.
Ive tried literally everything possible, ive read numerous manuals, seen tons of video tutorials but nothing works.
The main issue I am facing now is that MSMDownloader tool does not recognize my phone because of an Driver issue.
However, whatever I am doing I cant get the correct driver to function on my Windows 10 machine.
Whatever I do, it either does not recognize the device, or shows it as Kedacom USB Device / Android Bootloader Interface.
I have manually removed the drivers from the device manager as well as removing them manually with pnputils, it does remove the driver and then shows it as Android Device.
If i then scan the folders (whole windows is in testing mode like many manuals tell me to) it just wont install the driver and if i do that manually using pnputils it changes nothing.
The only moment it changes is when I connect to the internet and search for a driver and the old samer driver will be installed.
I have tried the OnePlus driver installer, I have tried the All In One tool, I tried the Qualcomm QDLoader HS USB Driver, I tried it totally disconnected, i rechecked if i was running cmd and the msmdownload tool as administrator, i have rebooted and updated my pc, rebooted and tried again.
I am pretty sure its an driver issue, but apparently whatever I do i cant seem to be able to fix it, and another way of fixing this phone is probably not gonna work as whatever I do with the volume, power buttons, how many times i reboot i just keep getting the same Fastboot/Download screen.
Does anyone have any other idea, am i missing something? I really have no idea. I have followed several manuals step by step, googled and found people with similar issues tried those solutions, i am now busy for like over 12 hours and am really getting the idea that i cant fix it

This can be closed, I have used the info from this thread:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It helped me revive my phone without having to deal with the USB issues and MSMDownloader.

schorrie said:
This can be closed, I have used the info from this thread:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It helped me revive my phone without having to deal with the USB issues and MSMDownloader.
Click to expand...
Click to collapse
THREAD CLOSED on request of OP!