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
Related
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Install HTC Sync, then reboot your computer
JvIo55iBl3r said:
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Click to expand...
Click to collapse
I did, actually. As a matter of fact, i do have that sync icon in my task bar
I am not sure, but i was wondering if the adb driver is necessary to be installed?
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
adseguy said:
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
Click to expand...
Click to collapse
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
JvIo55iBl3r said:
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
Click to expand...
Click to collapse
this should definitely be in the Q&A board, not the developers board.
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Exit HTC sync first on your computer so it is not running or just uninstall it. It should find it after that.
joeykrim said:
this should definitely be in the Q&A board, not the developers board.
Click to expand...
Click to collapse
Sorry about that, will do next time
joeykrim said:
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Click to expand...
Click to collapse
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
JvIo55iBl3r said:
Sorry about that, will do next time
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
Click to expand...
Click to collapse
any help? anyone?
Originally Posted by nicbennett
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
Originally Posted by snovvman
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
Click to expand...
Click to collapse
I originally added my post to this thread in the Nook forum. I don't think there is enough expertise in that forum to help with this problem.
The bottom line is that ADB no longer works and I can't figure out why (see quoted text above). I would imagine that someone here would have an answer for this. Please help!
Thanks.
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
DGreen1 said:
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
Click to expand...
Click to collapse
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
snovvman said:
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
Click to expand...
Click to collapse
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
My problem was Windows
snovvman said:
The error occurs when no device device connected. Same error when device IS connected.
. . .
I am really interested in a solution and would like to understand what is causing the problem.
Click to expand...
Click to collapse
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Yellowcard8992 said:
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
Click to expand...
Click to collapse
Interesting, but I haven't been able to find any other service that is bound to adb and I have no other USB devices connected. Thanks for chiming in though.
tgi007 said:
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Click to expand...
Click to collapse
For me, I have been able to get two Vista and one Windows 7 computer to work with ADB and HTC drivers the first time. I also have an Epic, and the Samsung drivers installed fine as well (even though they are known to have issues).
Unfortunately, ADB just "broke" one day.
I keep thinking that the Evo community has enough brains and knowledge to sort this out quickly...
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
lovethyEVO said:
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
Click to expand...
Click to collapse
Thanks for replying. I had already updated ADB (in platform-tools) before started having this problem. I had also uninstalled HTC sync (reboot, launch ADB w/o HTC sync, same problem) and reinstalled HTC sync, same problem. I updated Java JVM, no change. I then re-downloaded the SDK to a different directory, no dice.
I usually open a command prompt "as Administrator" and run ADB from the directory. Even with a device disconnected, I get the same error. I test this way because if I issued "ADB devices" and it returns nothing, I know it's working. It appears that ADB doesn't even start to the point to poll for devices.
I have, just for laughs, connected my device (USB debugging/charge only), but no joy.
I won't have much time to poke around more until the weekend. If I don't come up with anything, I will take you up on the gtalk. Thanks again.
Windows Vista just makes it all that much harder to fix things...
lovethyEVO said:
If you have installed htc sync before uninstall it and the htc driver installer.
. . .
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
. . .
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
Click to expand...
Click to collapse
In my case, I tried all these things and many more (lived with this problem since first getting my EVO on release date in June). No dice, as Windows Vista, once it installs a device driver, doesn't give the user the option to uninstall it (by Microsoft's expressly-stated intent -- a design decision I vehemently disagree with). At least the user could repair such problems in prior versions of Windows by simply uninstalling a device, choosing "yes" to the "remove driver files from the disk" question, and (after the obligatory and ubiquitous Windows reboot) re-connect the USB device. That would start fresh with that device's driver.
I never invested the time to learn how the USB subsystem registers devices and their drivers (in Windows Vista) in order to determine how to manually remove a driver from the Windows Registry adequately that it would treat the device as "new hardware detected" upon the next connection.
Once Windows Vista has scrambled some internals in the database/registry controlling the USB subsystem's driver knowledge, you're toast. Nothing I could find in Microsoft's Knowledge Base nor MSDN shed any light on how to tackle the removal-and-recreation-from-scratch of the USB system configuration.
Microsoft's stock answer was invariably "re-install Windows". Yeah, thanks for that. Windows, even more than 26 years later, is still not a real operating system, and still has bugs dating back to Windows 3.1.
Sigh.
Check Windows Firewall service.
In my case I just turned off the Windows Firewall and it started working.
regards
Gaurav
i had this problem.
disable any program like Proxifier and firewall
I accidently figured it out
so i was trying to find my cid number because i was flashing ICS firmware and stuff, and the adb deal in the prompt kept giving me the exact same error, and thus would'nt work. after trying everything (such as: installing drivers, killing the process, restarting my comp, reinstalling adb, etc.) for about an hour and a half, i just stumbled upon a page that was linked to in the ICS flash guide, that had a different adb folder download. this download has an entirely different effect on the command prompt and worked so i could get my cid number and rewrite superCid. here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=872134&d=1327512033
Download it, click "start here", then treat it like normal
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
orangeipod1gb said:
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
Click to expand...
Click to collapse
your solution is
netsh advfirewall set currentprofile firewallpolicy allowinbound,allowoutbound
what does our phone have to be in to use adb? ive never used it before but want to to obtain root without unlocking the bootloader and losing my info. is it rebooted in adx mode? just turned on normally? off?
thanks!
You cannot root without unlocking the bootloader! To access adb you need to be in OS and have debugging enabled under Developer options in the settings.
RTContent said:
You cannot root without unlocking the bootloader! To access adb you need to be in OS and have debugging enabled under Developer options in the settings.
Click to expand...
Click to collapse
i was directed here
http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
for a workaround to rooting without unlocking the bootloader
Wow, I must have missed that news. Apologies! Have you tried replying in that thread then?
RTContent said:
Wow, I must have missed that news. Apologies! Have you tried replying in that thread then?
Click to expand...
Click to collapse
you already answered my question to be in the OS with debugging enabled! thanks!
You could re-lock the bootloader though if you ever wish to unroot your phone...
my computer wont allow me to recognize my gnexus using adb. im following these steps - http://droidmodderx.com/galaxynexus/how-to-set-up-the-sdk-for-galaxy-nexus
and i know i have already installed the dirvers previously, but when i use the cmd prompt, my computer does not find my device whatsovever. tried uninstalling it from device manager, but it just reinstalled it when i plugged it in with the MTP drivers already on my computer.
does anyone have any suggestions? i did remember to leave usb debugging on.
thanks!
after rebooting, i tried this in cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Josh Bucher>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
************** offline
C:\Users\Josh Bucher>adb devices
List of devices attached
C:\Users\Josh Bucher>
so it looks like it detected it as offline, then it doesnt. any thoughts? i **ed my phones serial #
ive managed to get the toolkit to install fastboot drivers, but ADB drivers still are not installed and adb does not recognize my phone. fastboot does see it but adb doesnt. ive uninstalled all the drivers and tried the nexus toolkit, pdanet and manual installation but for some reason, i cannot get it to install adb drivers or even recognize that it is an option. does anyone have any suggestions?
joshtb86 said:
ive managed to get the toolkit to install fastboot drivers, but ADB drivers still are not installed and adb does not recognize my phone. fastboot does see it but adb doesnt. ive uninstalled all the drivers and tried the nexus toolkit, pdanet and manual installation but for some reason, i cannot get it to install adb drivers or even recognize that it is an option. does anyone have any suggestions?
Click to expand...
Click to collapse
So there's nothing listed if you input :
adb devices
You are connected via usb with debugging enabled?
Edit: could you also open up device manager in windows and have a look if the device is listed
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
So there's nothing listed if you input :
adb devices
You are connected via usb with debugging enabled?
Edit: could you also open up device manager in windows and have a look if the device is listed
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
usb is enabled.
nothing is listed under ADB, but there is my serial number listed under fastboot. I uninstalled all drivers the toolkit and the SDK. I am going to try the toolkit again now that everything is been uninstalled. The device will be listed in Windows but usually without the ADB driver listed, however the fastboot driver is listed.
now that I tried using the toolkit,
I still had the same problem with no ADB but fastboot was the listed. Then I went to uninstall the drivers through the toolkit and I got an error message saying that they remove failed three times and that no device was removed. However the device still exists under portable devices in the device manager. I am going to uninstall the toolkit after removing the drivers and remove all the drivers from the device manager and then try using just the SDK to route the phone.
after using the toolkit, I am now getting Samsung ADB interface driver installed on my computer. However the toolkit cannot access or realize that ADB is connecting to my phone. I do have USB debuggingenabled. I might try using the SDK to manuallyto connect to it.
fixed the problem. i plugged my phone in directly to the computer instead of through a usb splitter. got it rooted via this post
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
thanks for everyoines help! everyone is tahnked!
joshtb86 said:
fixed the problem. i plugged my phone in directly to the computer instead of through a usb splitter. got it rooted via this post
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
Glad you got it fixed. If I knew I could have told you the usb hub would have been the problem (they always are)
thanks for everyoines help! everyone is tahnked!
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using Tapatalk
New device. Odin works, USB storage works, TCP adb works, charging works. Have the latest drivers, which worked fine on the previous device (new device is a closed box warranty replacement). Device shows up in adb devices as "device", but adb freezes when attempting to push or shell. On super rare occasion, I get a shell prompt, but adb freezes immediately. Oftentimes, it shows up as "offline" instead. Have tested numerous cables, numerous USB ports. Reinstalled drivers, reflashed device in odin, reinstalled adb, redownloaded oneclick. Nothing works. Already went through other threads covering the same topic for numerous other devices. What am I overlooking?
Oneclick does not work anymore, not for Gingerbread. Other than that....try and let Windows find and install the drivers from Windows Update.
Sent from my SPH-D700 using xda premium
Meant the tweaked adb in oneclick. I tried to remove the drivers, and let windows search through update, but still no dice. The phone shows up in device manager, is recognized by odin for download mode, and windows as a storage device. However, adb still won't recognize it other than in an offline state.
Sorry if this is a stupid question but you have USB debugging on right?
Sent from my SPH-D700 using xda premium
Launch ddms.bat from \android-sdk-windows\tools
See if the DDMS application recognizes the device there. If not, then you need to enable USB-debugging and/or try different USB ports (but you said you did the latter already). I found that I must use USB ports directly attached to the motherboard for doing anything with my phone.
@kenny: Yup, USB debugging is enabled.
@nikon120: There's no tool dir, but there is platform-tools. There's no ddms in it.
wingbat said:
@kenny: Yup, USB debugging is enabled.
@nikon120: There's no tool dir, but there is platform-tools. There's no ddms in it.
Click to expand...
Click to collapse
Hmm, then I gather you don't have the SDK installed. I was just on SDK revision 10 and the folder was there. I also just uninstalled revision 10 and my older JDK installation to do a fresh install of the latest JDK and Android SDK. The tools folder is in this latest install too.
If odin works, just odin cwm 5.0.2.7, then flash su.zip which roots you.
Sent from my SPH-D700 using Tapatalk 2
nikon120 said:
Hmm, then I gather you don't have the SDK installed. I was just on SDK revision 10 and the folder was there. I also just uninstalled revision 10 and my older JDK installation to do a fresh install of the latest JDK and Android SDK. The tools folder is in this latest install too.
Click to expand...
Click to collapse
My apologies. "tools" was marked as hidden, and not showing during "dir" in command prompt. I did locate and launch ddms.bat. It shows the device as online, but unresponsive. If I close it, and kill-server, and relaunch, it shows the device as offline.
xboxfanj, I already have CWM flashed, and the device rooted, via Odin. What I'm trying to do is use shell/push.
wingbat said:
My apologies. "tools" was marked as hidden, and not showing during "dir" in command prompt. I did locate and launch ddms.bat. It shows the device as online, but unresponsive. If I close it, and kill-server, and relaunch, it shows the device as offline.
xboxfanj, I already have CWM flashed, and the device rooted, via Odin. What I'm trying to do is use shell/push.
Click to expand...
Click to collapse
Oh I see. Reinstall the drivers from samsungs website.
Sent from my GT-P7510 using Tapatalk 2
Why not use adb from the sdk?
Sent from my SPH-D700 using Tapatalk 2
MДЯCЦSДИT said:
Why not use adb from the sdk?
Click to expand...
Click to collapse
I did, it didn't work.
wingbat said:
I did, it didn't work.
Click to expand...
Click to collapse
That's why I inquired whether or not DDMS was recognizing your phone or not. Your reply was that it showed as offline, and that is a good indication as to why adb isn't working for you.
Outside of the phone not having USB debugging enabled, the only other reason I can think of your cause is device drivers for the phone. You said you've already reinstalled the phone drivers and no difference, so you may want to try on another computer or maybe a virtual machine.
1)Unplug the usb and plug it back again.
2)Go to the Settings -> Applications -> Development of your device and uncheck the USB debugging mode and then check it again back!
3)Restart the adb on your PC. adb kill-server and then adb start-server
4)Restart your device and try again.
Hi All,
There are lots of threads about adb issues, but can't find any solutions.
My issue:
AF2 connected, windows load it as "ASUS_Z00AD" in the devices list, windows file transfer is ok, but "ADB list of devices attached" empty.
AF2 connected in recovery, "ADB list of devices attached" is ok, and adb sideload is working fine.
What I suppose:
It already worked, with android Studio, sending my first Apk to the Fone. Then I played with "Unlock bootloader", and "Wipe with TWRP", and ... finally got the Fone Bricked. Thanks to this forum, I unbricked all, but now, can't do ADB in normal connected mode.
Everything is Ok with my Samsung GS4 mini.
It seems something change in the AFone2.
What I tried:
UnInstall (with powershell pnputil)/ Re-Install Android-SDK Google USB drivers
UnInstall (with powershell pnputil)/ Re-Install last Intel USB Drivers
Tried different releases of ADB, ADBDriver, ADBMaster, ADB-Setup, and so on
I'm blocked, thank's for helping.
Windows 8.1
MODEL: ZE551ML, ASUS_Z00AD
FIRMWARE : UL-Z00A-WW-4.21.40.184-user
AlainDex said:
Hi All,
There are lots of threads about adb issues, but can't find any solutions.
My issue:
AF2 connected, windows load it as "ASUS_Z00AD" in the devices list, windows file transfer is ok, but "ADB list of devices attached" empty.
AF2 connected in recovery, "ADB list of devices attached" is ok, and adb sideload is working fine.
What I suppose:
It already worked, with android Studio, sending my first Apk to the Fone. Then I played with "Unlock bootloader", and "Wipe with TWRP", and ... finally got the Fone Bricked. Thanks to this forum, I unbricked all, but now, can't do ADB in normal connected mode.
Everything is Ok with my Samsung GS4 mini.
It seems something change in the AFone2.
What I tried:
UnInstall (with powershell pnputil)/ Re-Install Android-SDK Google USB drivers
UnInstall (with powershell pnputil)/ Re-Install last Intel USB Drivers
Tried different releases of ADB, ADBDriver, ADBMaster, ADB-Setup, and so on
I'm blocked, thank's for helping.
Windows 8.1
MODEL: ZE551ML, ASUS_Z00AD
FIRMWARE : UL-Z00A-WW-4.21.40.184-user
Click to expand...
Click to collapse
Do you have USB debugging on? Do you have root set for apps AND adb?
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Do you have USB debugging on? Do you have root set for apps AND adb?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Two days fighting with these f**** drivers ! I'm really a zero :crying::crying::crying:
I activated "programming" mode, but didn't go to options to activate "debugging" mode ...
Thank you so much :good: