Develop Bugs

AT&T S3 not seen by ADB

Ok... i've gone through the steps in the one thread to get the phone rooted and everything without tripping the flash counter. At least the rooting with ODIN part. Been trying to flash CWM Touch for it, but for the life of me can't get the S3 to enter debugging mode over USB so that it can be seen by ADB to do so. I have Debugging over USB checked in the settings on the phone, i've rebooted the phone several times... it just never seems to enter debugging mode (or at least not like on my old Atrix 4G, where it actually told you in the notification bar that debugging was enabled).

It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.

gunnyman said:
It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.
Click to expand...
Click to collapse
I had installed Kies... tried hooking it up, still wouldn't list in ADB. uninstalled Kies, but kept the drivers installed. And i only mentioned the idea of it saying Debugging enabled when you connect the USB cable because my Atrix 4G said that every time from the get-go.

Also odd.... looked into the SuperUser app... and the log shows several allowed access attempts from "shell"... yet never seemed that way in ADB.

I had the same problem... try going in to the "services" settings and update the driver to Android ADB composite. Other than that, my suggestion is to make sure Kies finds the drivers for both Camera mode and USB mode by toggling the selection while plugged in to Kies.
Sent from my SGH-I747M using xda app-developers app

Your last resort would be to remove the drivers and reinstall them... Don't install Kies...

Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.

elementaldragon said:
Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
Click to expand...
Click to collapse
It seems to be a driver issue, kies interfering, or a component is missing, or all of that, so I'd start your windows driver and software over fresh...
Uninstall Kies
Uninstall the drivers
Reboot
Install the drivers
Install the Java JDK (64bit has never worked for me, even though the drivers are 64bit)
Install the Android SDK
Use the Android SDK to get the Platform Tools and the Google USB Driver
than adb devices should show a phone
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
elementaldragon said:
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.
Click to expand...
Click to collapse
sometimes ADB Devices returns nothing for me, but theres a phone there, it would say nothing connected or to some effect if it didn't find anything...

Yea... every time i entered "adb devices" in the Windows command prompt, it always said "List of detected devices" or whatever it says, but nothing would be there, and if i tried the command to install the recovery it would say it was not a valid directory or whatever. Didn't show up on Ubuntu either, but it still worked...

EDIT/UPDATE: I was using a USB 3.0 port which apparently ADB didn't like (though ODIN rooting on that USB port worked fine...). I switched to another USB port and suddenly it worked!
Sorry to resurrect an old thread but I guess it's better than creating a new one for the same purpose...
Doesn't seem like this was resolved and I haven't been able to get my S3 to connect to ADB. I'm running Windows 7 Ultimate 64 Bit.
I had this driver already installed:
ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0
I enabled USB debugging and it wouldn't connect. I installed Kies, still wouldn't connect. I uninstalled the driver and Kies and rebooted. Reinstalled "ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0", installed the Google USB driver, still won't connect.
I'm still not sure if I'm supposed to see any sort of notification in my bar showing that USB debugging mode has been executed but I'm definitely not getting anything like that.
Code:
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
891b0876 offline
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
List of devices attached

Yea, when i finally was able to use ADB to push a recovery onto my S3, it never actually showed up if i checked the devices in ADB Shell. Well... it DID, but not if i already typed the SU command before "adb devices".

hey guys
i have same problem i wanna adb my galaxy s3 rogers (att) i am trying to do the root no tripping flash counter so i got to the adb shell part
i dont know what else to do to make my computer recognize my phone ??
i installed sdk and extract/installed it in the c:\android folder of my comp i let sdk installed all the things it needs to took a while
so whats left? i have my phone usb connected to comp and debuging on i type adb shell it says adb is not recognized internal or external command???
do i need to have somthing open on the phone b4 openning command?
pleaaase help lol
thanks

You need to navigate to the folder where adb is actually located (platform-tools)

You don't have to use adb, you can use the same commands on terminal emulator

[Q] Kindle CM10.1 not connecting to PC

I've installed 2nd bootloader + TWRP + cyanogenmod for my kindle fire 8.9 hd, but now the device isn't showing up on my computer (windows 7 64bit.) It starts to install drivers but says "unidentified device" and fails. I looked around in settings on the actual tablet and couldnt find anything relevant. Is it possible I need to turn on adb debugging on the tablet again, and if so, where is it located in CM10.1?
I've tried rebooting and reinstalling adb drivers on my computer, but no dice.
It detects as a PTP device, but doesn't show up when I change it to MTP. adb devices doesn't list anything.
Any help would be greatly appreciated.

konasus said:
I've installed 2nd bootloader + TWRP + cyanogenmod for my kindle fire 8.9 hd, but now the device isn't showing up on my computer (windows 7 64bit.) It starts to install drivers but says "unidentified device" and fails. I looked around in settings on the actual tablet and couldnt find anything relevant. Is it possible I need to turn on adb debugging on the tablet again, and if so, where is it located in CM10.1?
I've tried rebooting and reinstalling adb drivers on my computer, but no dice.
It detects as a PTP device, but doesn't show up when I change it to MTP. adb devices doesn't list anything.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Yeah I had that problem just a few days ago. Turns out you just go to the setting and about section and tap the build number a few times to enable the developers options in setting. Then you will be able to select adb debugging.

AlexAquarium said:
Yeah I had that problem just a few days ago. Turns out you just go to the setting and about section and tap the build number a few times to enable the developers options in setting. Then you will be able to select adb debugging.
Click to expand...
Click to collapse
Sweet, that was really helpful. Now the device shows up in adb devices, but not in windows. I can't send or receive files.

This is really frustrating. You'd something something as simple as "how to connect cm10.1 kindle to computer" would be documented somewhere, but I cant seem to find it.

konasus said:
Sweet, that was really helpful. Now the device shows up in adb devices, but not in windows. I can't send or receive files.
Click to expand...
Click to collapse
Never had an issue not showing up in windows especially if the "adb devices" cmd now works in your windows. That seems odd. Maybe you should connect your kindle to pc and enter windows device manager under portable drivers and uninstall the kindle driver. Window will reinstall the driver once you disconnect and reconnect the kindle.

I have the exact same problem with my KFHD8.9 since I rooted and installed CM10 two days ago.
I also have Win 7 64, and I also can use it as PTP but not as an MTP (USB debugging is on).
I've tried installing and re-installing both ADB drivers provided here. Countless times I've tried to: reboot Kindle, restart my PC, removing unrecognized drivers in device manager and then reinstalling them when the Kidnle connects via USB.
I've even tried installing the Android SDK files with no success.
So far, I've spent more than 7 hours trying to fix this.
The closest I've gotton, was to manually direct the broken Kindle Fire HD driver in device manager to update via the ADB driver located in Program files (x86) folder- then it showed the kindle as being connected under the "safely remove hardware" icon in the notification area and showed as a working driver in device manager, but even then, the MTP won't work and won't show the Kidnle in my computer.
One of the most frustrating things about it is that I connected the Kindle to a 7 year old laptop we have and it was
recognized immediately in "my computer". So I know this means something is wrong with my laptop that
prevents it from being recognized.
Anyone have a suggestions? A solution?
After more than 7 hours trying to figure this out, I would really appreciate your help!

did you solve this?
I just flashed CM10.1 and have the same problem

Try this:
Disconnect kindle
Go to device manager
look for kindle
uninstall
connect kindle
I see that a1745 has tried something like this, but these USB drivers are really flaky. Worth a try.
You can also try toggling MTP mode.
Settings -> storage -> the 3 cube icon on the upper right -> USB computer connection -> and try toggling MTP.

Cronoss said:
Try this:
Disconnect kindle
Go to device manager
look for kindle
uninstall
connect kindle
I see that a1745 has tried something like this, but these USB drivers are really flaky. Worth a try.
You can also try toggling MTP mode.
Settings -> storage -> the 3 cube icon on the upper right -> USB computer connection -> and try toggling MTP.
Click to expand...
Click to collapse
thanks, it works now

Cant access USB debugging

As stated, I cant acess usb debugging.. I've already connect my phone to pc but it just only show charging.. I also cant copy file to my pc.. what is the problem here? :crying::crying::crying:

panha510 said:
As stated, I cant acess usb debugging.. I've already connect my phone to pc but it just only show charging.. I also cant copy file to my pc.. what is the problem here? :crying::crying::crying:
Click to expand...
Click to collapse
HTC manager also wont recognize my phone..

panha510 said:
HTC manager also wont recognize my phone..
Click to expand...
Click to collapse
It was written so many times on XDA Forums, that your question is quite a surprise:
Open Settings, then go to phone details (where u can see kernel, Android-version etc) then just tap your Build number enough times until you're developer! Then enable USB Debugging...

bratusm said:
It was written so many times on XDA Forums, that your question is quite a surprise:
Open Settings, then go to phone details (where u can see kernel, Android-version etc) then just tap your Build number enough times until you're developer! Then enable USB Debugging...
Click to expand...
Click to collapse
I've already know that, it is when I plugged my phone into the computer, the battery indicator is charging, but the USB connection never happens.

panha510 said:
I've already know that, it is when I plugged my phone into the computer, the battery indicator is charging, but the USB connection never happens.
Click to expand...
Click to collapse
System? Win XXX, Linux...
HTC Drivers?

bratusm said:
System? Win XXX, Linux...
HTC Drivers?
Click to expand...
Click to collapse
windows 7, i already installed the htc driver..

If you can't access it, go into your settings app on your phone
Open Developer Options and click the checkbox that says
Code:
USB Debugging
If it still doesn't work, install HTC Sync Manager (if not installed already)
Restart your phone into the bootloader (by holding [Vol Down] + pressing [Power] for a second, still holding [Vol Down]
Select 'Fastboot' at the menu that shows up
Plug in your phone, ignore HTC Sync Manager, open a command prompt (admin) by hitting [WIN] + [X], then select
Code:
Command Prompt (Admin)
Once you have done that, cd to your directory of the adb and fastboot executables, like this:
Code:
cd "C:/[your directory]/"
Then
Code:
adb devices
If adb detects that the service isn't running, it'll start it then search for your device. If it finds it, you're set to use the fastboot commands for whatever you want
Good luck guys!

[Q] Cannot Unlock Bootloader on Windows 8.1

Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.

killfire72 said:
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
Click to expand...
Click to collapse
Use another computer if you can.

I had similar problems until I used this version of adb
http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.

ashyx said:
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
Click to expand...
Click to collapse
That version of ADB didn't work for me either. Anyway I was able to get fastboot to work but not ADB so I was able to unlock and root and everything through a strange method using only fastboot.
Second question, if I am switching between AOSP roms, say for example CM to PA, can I dirty flash or do I have to reset?

ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8

xeron72548 said:
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
Click to expand...
Click to collapse
Not so, I and others have ADB working fine on USB 3.0 ports.
The problem is Windows 8 driver signing enforcement blocking the install of drivers. You need to go to advanced startup options to disable it.
Download these drivers first and extract: http://www.mediafire.com/download/i3lcm7dwl581518/ADB_Fastboot_Drivers_Win81.zip
Follow these instructions to disable driver signing enforcement: http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
Once fully booted go into device manager and you should see a device called 'Android 1.0' with an exclamation mark.
Right click 'Android 1.0' then 'update driver software' then 'Browse my computer for driver software'
Click the 'Browse' button and then browse to the driver folder 'ADB_Fastboot_Drivers_Win81' extracted earlier then click next to install the driver.
You will get a warning about unsigned drivers, just ignore and continue.
The drivers should install and you should see a new entry in device manager called 'Android phone' which means the ADB driver is installed.
ADB should now be working.

Thank you so much for this. Have been wondering for a very long time
Sent from my HTC One_M8 using XDA Free mobile app

It sounds like you've got plenty of technical help already, but I will say that I use ADB perfectly fine on my desktop with Win 8.1 so it's possible. I also use hassoon's toolkit occasionally with no issue.
Before I could get the desktop to recognize the M8 I had to completely uninstall all drivers related to my previous galaxy nexus as well as remove any mention of the device in Window's USBdeview. After a reboot, I just plugged in the M8 and windows automatically installed the necessary M8 drivers. I can then run fastboot and adb from the toolkit.

I ended up uninstalling the MSFT USB 3.0 drivers and use the Intel USB 3.0 drivers instead on my Win8.1 laptop that has only USB 3.0 ports. Works great.

USB error PLEASE HELP!

USB will not function with my OnePlus 3, I've loaded drivers and still no avail.

templarsniper said:
USB will not function with my OnePlus 3, I've loaded drivers and still no avail.
Click to expand...
Click to collapse
As regards the attaching of files, you have to have a minimum number of posts to be able to do that.
As regards the USB, be a little more specific like what you are trying to do, which ROM you are running, whether you are rooted, what happens when you connect the phone to PC etc which will enable the members to help you.

There could be several reasons for this, but lets start with the basics.
Have you tried a different cable?
Have you selected File Transfer (MTP) from usb options?

kenboyles72 said:
There could be several reasons for this, but lets start with the basics.
Have you tried a different cable?
Have you selected File Transfer (MTP) from usb options?
Click to expand...
Click to collapse
I get a windows sound like its connecting then in the bottom right where the time is next to that is a root sign then I get a pop up saying exactly.....The last USB device you connected to this computer malfunctioned and Windows does not recognize it. Recommendation.. Try reconnecting the device. If Windows still does not recognize it, your device may not be working properly. When I go to the Device Manager/Control Panel it doesnt do anything. I've tried to add adb to the path but maybe added it to wrong path now it won't come on. If there is a work around maybe to re-add to right path. Device Manager was fine before I added adb and added path as per internet search. Device Manager before would say something like error 39. I've tried MTP that doesn't get it to open up either.

TNSMANI said:
As regards the attaching of files, you have to have a minimum number of posts to be able to do that.
As regards the USB, be a little more specific like what you are trying to do, which ROM you are running, whether you are rooted, what happens when you connect the phone to PC etc which will enable the members to help you.
Click to expand...
Click to collapse
I cant even root for the life of me now, Im on 8.0, I'm trying to just root the phone and to start the computer has to recognize it I understand but it won't, with my Oneplus 2 was fine,(I'm thinking maybe phone doesnt have the drivers built in to the file system, you know when you plug in and turn on MTP it shows the drivers app for Windows?) the only thing it errors plugging in.
I get a windows sound like its connecting then in the bottom right where the time is next to that is a root sign then I get a pop up saying exactly.....The last USB device you connected to this computer malfunctioned and Windows does not recognize it. Recommendation.. Try reconnecting the device. If Windows still does not recognize it, your device may not be working properly. When I go to the Device Manager/Control Panel it doesnt do anything. I've tried to add adb to the path but maybe added it to wrong path now it won't come on. If there is a work around maybe to re-add to right path. Device Manager was fine before I added adb and added path as per internet search. Device Manager before would say something like error 39. I've tried MTP that doesn't get it to open up either.

On my son's pc running windows 10, I didn't have any issues connecting my OP3 to it and viewing files, nor did I have to install any drivers, same for Windows 7.
Hook phone to pc via usb cable.
Pull down notification bar and select "File Transfer" from usb options or go to Settings and search USB and select USB Preferences > File Transfer.
Browse phone from Window's file manager.
If still having issues, you can try and install Oneplus USB drivers, reboot pc and see if the phone can be recognized.
Oneplus USB drivers:
https://app.box.com/s/u47rur40qm5efly6pz41rbhagu5qvc80

Fixed USB problem
kenboyles72 said:
On my son's pc running windows 10, I didn't have any issues connecting my OP3 to it and viewing files, nor did I have to install any drivers, same for Windows 7.
Hook phone to pc via usb cable.
Pull down notification bar and select "File Transfer" from usb options or go to Settings and search USB and select USB Preferences > File Transfer.
Browse phone from Window's file manager.
If still having issues, you can try and install Oneplus USB drivers, reboot pc and see if the phone can be recognized.
Oneplus USB drivers:
https://app.box.com/s/u47rur40qm5efly6pz41rbhagu5qvc80
Click to expand...
Click to collapse
For some reason it's working now don't know what the problem was or even if it was something I did. Either way it's fixed.

templarsniper said:
For some reason it's working now don't know what the problem was or even if it was something I did. Either way it's fixed.
Click to expand...
Click to collapse
If you are running Win 10, you will have to disable driver signing before the correct drivers are installed. May be that was your issue.