Develop Bugs

[Q] Can't get ADB to work, have tried everything

Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies

expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.

Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Hi Dave, thanks for the reply.
I definitely have USB Debugging enabled - I also am 100% sure that I have installed the hboot driver before (I did it when rooting for the first time ages ago), and can confirm this by booting into Bootloader and having "Android Bootloader Interface" appear as a known device.
Also, with the HBOOT-Driver, it lists the phone as "Android 1.0" when Unknown, whereas my situation lists "Android Phone" as the unknown device.

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Click to expand...
Click to collapse
Same here.

Have you added the environment variable for the sdk directory? It won't work if you don't.

Also.. install .. HTC Sync.. .and try.. and again uninstall only HTC sync.. and leave the HTC driver and try

I've had issues getting it working too and haven't quite figured out the sequence to get it to work. All I remember is the Android SDK drivers don't work, you need to use the HTC ones. You don't need to uninstall HTC Sync (try re-installing it though). You might then need to run update drivers on the unknown device for it to find them.
I can confirm that it does work with HTC Sync still installed. I sometimes find ADB devices takes a few attempts or restarting ADB to actually work.

vnvman said:
Have you added the environment variable for the sdk directory? It won't work if you don't.
Click to expand...
Click to collapse
Hi vnvman.
Thanks for the reply - I have indeed, my "PATH" value is as below:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\XviD MPEG-4 Video Codec 1.2.2 64-BIT;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools
Click to expand...
Click to collapse
However, even if I cd in CMD to the platform-tools folder and run adb from there, no luck. ADB itself works perfectly, but it just doesn't recognize my phone.

bobsie41 said:
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Click to expand...
Click to collapse
Like some others users posted here, win 7 x64 is working for me without any problems.
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
Try to reinstall android sdk completely following this guide:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

Hi MatDrOiD.
Thanks for the reply, I'll give that a shot as well as try jhonybravo4u and Antcodd's ideas.
Appreciate all input. If I get it working, I'll be sure to update this post so that anyone else who might have this problem has a solution

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
What i meant is that windows 7 seems 64bit seems to cause more problems than any other windows os. I had a windows 7 64bit computer and after days of pratting about i managed to get it working now, further down the road, and a bit more knowledgable(i think!) i have a new more powerful windows 7 64bit machine and i can't for the life of me get it working.
I know run adb from my wifes vista laptop and had no trouble whatsoever in setting this up.

If u tried "everything", u better don't ask for more ;-p
Sent from my HTC Desire using XDA Premium App

It worked for me last time, but then I formatted my drive, and now can't get it to work for the love of god. Actually I can, but I have to change the driver every time Android phone pops up in the device manager using have disk.

[Q] HTC One X Driver for Android 4.2.2

Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.

Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?

Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface

Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?

Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed

I was having issues with adb not finding my device. These drivers worked for me...

crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app

Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all

confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless

If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2

ADB Drivers

I don't see any other threads, so is it just me struggling to install working ADB drivers?
The zip file I found in another thread made out like it was installed, but apparently not...
Any tips?

Windows 7/8? The drivers that I posted in the dev thread should work.
If you're on Windows 8 though, you'll have to reboot in that insecure driver installation mode thing.
Sent from my HTCONE using Tapatalk

Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.

AndyCr15 said:
Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.
Click to expand...
Click to collapse
You try "ADB Composite Device" or something along those lines? When you run that one it should be good.
When you download the zip, you should just extract the whole thing. Then after that I find the driver manually instead of having it search the folders. Are you selecting the android_winusb.inf for the driver?
I'm on the same OS for my main desktop and I do a lot of my work with the N1 on there using those drivers. Are you using normal command prompt in the platform-tools folder? I don't use anything other than command prompt for adb, so I'm not sure about those picking it up.
Sorry if that isn't any help, but I'm not sure what would stop it from picking it up after you use those drivers.

the other threads zip file works fine with my win 64. Are you going through a usb hub? That can mess it up
Sent from my N1 using XDA Premium 4 mobile app

No, no hub. Yep, doing all as I should. I'll try a different cable and different port though.

Linux
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.

mybrotherischad said:
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.
Click to expand...
Click to collapse
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.

ChodTheWacko said:
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.
Click to expand...
Click to collapse
Running natively. No luck doing it as root.

[Q] Driver install problem w/ Mac

I'm having some trouble and I think it might be related to drivers. I'm on Mac OSX 10.8.5 so I downloaded the LGUnitedMobile_Mac_Driver_Ver_4.22 from here:
http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
I installed, restarted computer. When I plug in the G4 via USB I don't get the popup requesting ADB access. (I've got USB debugging on in Developer Options and it shows as on in Developer Options as well as a notification in the pulldown menu). If I tap on the notification from the pulldown for MTP options I'm asked if I want to install the drivers. So, I do that too and wait for it to complete. Still no ADB popup. If I open the Debloater tool, no welcome popup and the "device connected" light is red.
I tried toggling between MTP and PTP and still nothing. Tried unauthorizing my computer in Developer Options, unplugging, and waiting. Tried restarting phone.
Further, if I open Android File Transfer I get a message "No Android device found" whereas before trying to install the driver it found the G4 just fine. Ran the uninstall script from the LG driver software and Android File Transfer then CAN see the phone.
Any ideas? Any help would be appreciated - I'm trying to run the Debloater tool (which can't see the G4 either no matter what I try).

creaky said:
I'm having some trouble and I think it might be related to drivers. I'm on Mac OSX 10.8.5 so I downloaded the LGUnitedMobile_Mac_Driver_Ver_4.22 from here:
http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
I installed, restarted computer. When I plug in the G4 via USB I don't get the popup requesting ADB access. (I've got USB debugging on in Developer Options and it shows as on in Developer Options as well as a notification in the pulldown menu). If I tap on the notification from the pulldown for MTP options I'm asked if I want to install the drivers. So, I do that too and wait for it to complete. Still no ADB popup. If I open the Debloater tool, no welcome popup and the "device connected" light is red.
I tried toggling between MTP and PTP and still nothing. Tried unauthorizing my computer in Developer Options, unplugging, and waiting. Tried restarting phone.
Further, if I open Android File Transfer I get a message "No Android device found" whereas before trying to install the driver it found the G4 just fine. Ran the uninstall script from the LG driver software and Android File Transfer then CAN see the phone.
Any ideas? Any help would be appreciated - I'm trying to run the Debloater tool (which can't see the G4 either no matter what I try).
Click to expand...
Click to collapse
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.

uly609 said:
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
Click to expand...
Click to collapse
Thanks for the response. Tried that (typed adb devices in Terminal) and got this: -bash: adb: command not found
Not sure what I'm doing wrong here.

Do you have installed the android sdk?

creaky said:
Thanks for the response. Tried that (typed adb devices in Terminal) and got this: -bash: adb: command not found
Not sure what I'm doing wrong here.
Click to expand...
Click to collapse
If I remember correctly you need to download the android sdk and install the sdk and platform tools. When you do this make sure you make a folder on your desktop and name it whatever you want, and when you install the sdk make sure the install path goes to the folder you made. Then open a terminal window and navigate to the folder you installed the sdk to.
Then run the adb command, but it will be slightly different:
./adb devices

uly609 said:
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
Click to expand...
Click to collapse
wadamean said:
Do you have installed the android sdk?
Click to expand...
Click to collapse
I had to reinstall - that was the problem. Thanks!
uly609 said:
If I remember correctly you need to download the android sdk and install the sdk and platform tools. When you do this make sure you make a folder on your desktop and name it whatever you want, and when you install the sdk make sure the install path goes to the folder you made. Then open a terminal window and navigate to the folder you installed the sdk to.
Then run the adb command, but it will be slightly different:
./adb devices
Click to expand...
Click to collapse
Thanks again for the help. Problem solved.

Hey so then you were able to root using your mac? what variant g4 do you have? Could you please message me what steps you did to get successful root? i would really really appreciate it. its very rare to find mac users.

wadamean said:
Hey so then you were able to root using your mac? what variant g4 do you have? Could you please message me what steps you did to get successful root? i would really really appreciate it. its very rare to find mac users.
Click to expand...
Click to collapse
Not root, used Debloater tool to block updates. Would love to see a Mac root method released.

oh i see then. i will keep patiently waiting for a simpler root method. this one is already but for sure there has always been even more simpler methods surfaced.

Is adb bugs on model SMJ200G (j2) common?

I investigated the ADB program. At How to Install ADB on Windows, macOS, and Linux, I am stuck at step 7 of the instructions for windows. I do not receive any kind of pop up in my SMJ200G phone (j2).
This step:
7. On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).
Click to expand...
Click to collapse
Perhaps my PC's connection to the phone is buggy, not the cable, but the software? by software I mean Windows/PC not my phone.
btw does file AdbWinUsbApi.dll need to be installed?
Are the following applicable for a official device that have never been rooted:
NVCore said:
-Missing ADB Confirmation Dialog(can be bypass by placing adb_keys(from PC/Laptop that has platform-tools and the file name is adbkey.pub, rename it to adb_keys) move the file to device (/data/misc/adb)
Click to expand...
Click to collapse
mbalino said:
Unable to detect the phone -win nor Lin
Hello guys
Something really extrange is happening.
My j2 prime -532G- can't be detected by Windows nor Linux.
The usb is working because it charges the phone, but I can't access the phone at all. I checked all the drivers in Win -google/adb and samsung- and in Linux libmtp/heimdall/etc.
I have tryed different usb -not the original one since i lost it-
Even when i start the download mode, nothing happens.
it there a way to root the phone without a PC? i have tryed also kingroot apk but it is useless.
Thanks
Click to expand...
Click to collapse
citation