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
i cant seem to connect thru adb or fastboot usb. adb doesnt show anything under "adb devices" and fastboot doesnt give me "USB" icon if i plug it in to a usb. i've tried multiple wires. i tried on my macbook and on a windows 7 machine. played around with htc drivers. cant seem to make it work. tried unmounting and remounting the sdcard and rebooting all devices.
i was going to try adb over wifi but you need to root for that. without adb or fastboot, i cant even htcdev unlock.
any other ideas? i plug it in and it shows a charging icon in the batter bar but no mounting options show up in the notification bar. usb debug is enabled. i tried the different "mount as" options in the settings menu. i've read countless web pages to try to get this to mount to any computer so i can mod it a little but nothing seems to work.
Revoke the USB debugging authorizations and then connect to the computer?
Sent from my Nexus 7 using xda app-developers app
Also make sure Fastboot is unchecked under power settings.
havikx said:
i cant seem to connect thru adb or fastboot usb. adb doesnt show anything under "adb devices" and fastboot doesnt give me "USB" icon if i plug it in to a usb. i've tried multiple wires. i tried on my macbook and on a windows 7 machine. played around with htc drivers. cant seem to make it work. tried unmounting and remounting the sdcard and rebooting all devices.
i was going to try adb over wifi but you need to root for that. without adb or fastboot, i cant even htcdev unlock.
any other ideas? i plug it in and it shows a charging icon in the batter bar but no mounting options show up in the notification bar. usb debug is enabled. i tried the different "mount as" options in the settings menu. i've read countless web pages to try to get this to mount to any computer so i can mod it a little but nothing seems to work.
Click to expand...
Click to collapse
have you downloaded sdk manager and put the path of platforms tools folder in path on the environment variables?
atticustcx said:
have you downloaded sdk manager and put the path of platforms tools folder in path on the environment variables?
Click to expand...
Click to collapse
I have the same problem with my HTC One.
nasvi said:
I have the same problem with my HTC One.
Click to expand...
Click to collapse
i think is same here, i dont have any system in my htc one, only recovery, and cannot push file from anyway
bump
been having same problem, no menus or anything when plugged into usb just charging
try reinstalling your device drivers and make sure you have android sdk installed. ive had this issue before and all i had to do was reinstall the drivers. and make sure you have fastboot for the htc bec using other fastboot can cause issures with recognition of your phone.
I seem to run into this problem quite a bit, and am seeing it again trying to sideload 4.4.4. Device manager shows the g pad connected with no !, and shows the driver as being the LG driver from 2014. Debugging mode is active on the tablet. Ive tried multiple cables and multiple ports. Ive tried disconnecting, killing the adb process, and trying again.
What am I missing?
It sure is much easier in Ubuntu. The drivers are already built in and all you need to do is install the android sdk to get adb. The only thing that needs to be changed on the tablet is enabling usb debugging.
Use internet connection instead of mtp
mcerk02 said:
Use internet connection instead of mtp
Click to expand...
Click to collapse
Just tried that with the same results. Thank you for the suggestion, though.
Edit - It worked. The first adb devices command did not return anything. A few minutes later I noticed a pop-up on the device asking me to approve debug access for the connected device. After that it worked. I was not previously receiving the access notification request.
Hello everyone!
I recently decided to root my G4 (h815) and have downloaded the ADB drivers and have the drivers needed for the G4 however when I plug the phone into the PC ADB doesn't recognise the device is connected, even though the PC does know the phone is plugged in.
I have the phone set up correctly for debugging, and when I change to USB tethering the PC does make the little noise when a device is plugged in. I have tried in both USB 2 and USB 3 ports on two computers.
If it makes any difference the commands I used to try and get ADB to do something are:
ADB USB
ADB devices
Both say thre is no device connected.
Thanks in advance, sorry if this is in the wrong place.
Had the problem too, used WIN10, WIN 7, WIN XP. So i switched to Ubuntu.....that did the trick
are you enabled USB debugging in developers options?
Yes ADB is enabled.
I might try dualbooting with Ubuntu then. Seems odd that it doesn't work with Windows.
Fixed- ran the 15 second ADB and fastboot installer
I updated to the latest verion of windows and now ADB and fastboot do not recognize device. I dowloded the phone drivers updated to a current version of ADB and fastboot from google. I have have developer options on and USB debugging. I also tried on another computer and same issue. I'm not getting the pop-up that says allow this computer to use USB debugging which I think might be the problem. Any ideas?
jdh10475 said:
Fixed- ran the 15 second ADB and fastboot installer
I updated to the latest verion of windows and now ADB and fastboot do not recognize device. I dowloded the phone drivers updated to a current version of ADB and fastboot from google. I have have developer options on and USB debugging. I also tried on another computer and same issue. I'm not getting the pop-up that says allow this computer to use USB debugging which I think might be the problem. Any ideas?
Click to expand...
Click to collapse
Might be a little overkill here but unplug your phone from your pc, uninstall moto drivers, reboot, reinstall moto drivers and reboot. Meanwhile in developer settings in your phone, revoke usb debugging authorization and turn usb debugging off.
Once all that is done replug your phone let the drivers install, then toggle usb debugging back on. Hopefully it'll reinstall a fresh adb driver and prompt for authorization.