Related
Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
criccio said:
Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
Click to expand...
Click to collapse
Does it have anything there when you type adb devices? Should come up with a HT and some numbers after it....being your device, EVO.
Actually, there is a step by step Guide for EVO root, and a ADB Guide for Beginners
Your device isn't being recoginized check the driver if u r in windows.
Ok, I managed to figure out the cryptic SDK installer and download the USB driver package to android-sdk-windows\usb_driver. I used Device Manager to install the driver and I pointed it to that folder and I get the "Windows was unable to install your ADB".
Are you already Rooted? as for the Drivers, when I plugged in my EVO via USB, it installed drivers...I also copied the HTC Sync that came on the SDCard w/phone, onto my pc. But I did not have to do anything further.
Can I ask what you are trying to do in adb? and is this for the EVO?
use the cd command to make sure you are in the android sdk tools folder
if you want adb to work
what i do
1. use the cd command to go to the directory where my sdk is located which for example is c:\androidsdk\tools
2. there you go
3. if you want shell make sure your device is connected
"adb shell"
and have htc sync from evo's sd card installed
http://myevo4g.net/main/?p=83
Sent from my HTC EVO
download htc sync and install that. i was having the same problems and apparently the usb drivers that get installed with that app are the ones that worked like a charm for me.
Try
Code:
./adb devices
Instead.
--> try" adb start-server "
If your HTC dont show up, it's usually because the ADB server isnt running. Hope this helps =]
I've rooted a hero before and felt pretty confident with android sdk, usb drivers, etc. After spending an hour trying to get it to work on my win 7 64 bit system, I thought it might save someone some time if I posted what finally allowed me to get adb to work.
My problem was the computer wouldn't recognize the EVO as a device. Even after I installed the usb drivers through android sdk. I tried to manually update them through device manager (pointing it to the usb drivers directory) and still no luck.
As the video linked above showed, the missing piece for me was installing htc sync. use the version that comes on the phone. So connect the phone to the computer, mount it as a drive from the phone menu, then copy over the htc sync directory to your computer, then run it. The version on my phone was 2.031. THEN the computer will recognize it with usb debugging turned on and I'm able to adb to the phone through the command prompt.
Hope that helps someone. Sean
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
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
http://www.mylgphones.com/tag/usb-drivers try these drivers
That's the ones that didn't work.
Same problem here... Any luck?
Change the USB mode to PTP and you should get the RSA prompt.
anod said:
Same problem here... Any luck?
Click to expand...
Click to collapse
Yes I have install Google universal usb drivers worked for me search on Google for them
PTP worked for me, no LG driver installed.
Just got my G3 on Verizon, cannot see the device over ADB either on Mac OSX
I tried MTP, PTP, and Charge only both with and without LG drivers installed. Since it's OSX, there are no Google Universal USB drivers.
Android File Transfer opens up fine, but ADB doesn't show the device. Quite fishy indeed.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
May I ask how you managed to connect your phone to your mac via MTP? I am unable to get any kind of connection to my mac.
On windows it works finde, I can open the internal and external sd card and copy files from and to the device, I would be more than happy to achive the same on my mac.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
Hi there, you will first need to enable USB Debugging. Head over to Settings > General > About Phone > Software Information. Tap Build Number 5 times, and you'll unlock the Developer options.
Go to Settings > Developer options, and check USB Debugging. From there, ADB should work. Good luck!
OK, so I installed the new drivers, rebooted, and got ADB to recognize my LG, and was able to debug successfully. Now Android File Transfer doesn't see it, nor does Finder show the device. What am I missing?
It's broken, I saw a tweet from jcase regarding the issue. I have the same problem. I just adb push/pull when necessary for now.
Sent from my LGLS990 using XDA Free mobile app
EDIT - It wasn't jcase, it was @utoprime
Mine works fine on my Mac
faded03cobra said:
Mine works fine on my Mac
Click to expand...
Click to collapse
You have adb and MTP works? What OSX version?
Sent from my LGLS990 using XDA Free mobile app
Solution
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
KAR0SH1 said:
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
Click to expand...
Click to collapse
Seriously old, and seriously unresolved (for me and a few people on reddit, at least). Still have not succeeded at getting ADB to detect G3 on USB, tried running the -usb flag on the cli and everything. Is there a working process yet? Verizon seems to be the outlier here as well...
Just worked for me on OSX Yosemite with a D855 on V10l:
- Update ADB (android platform tools)
- Install LG Driver (link is in this thread)
- Reboot
- run "rm ~/.android/adbkey" and "rm ~/.android/adbkey.pub"
- run "adb devices" (you should now see your G3)
- run "adb kill-server" (just to make sure there is no interference)
- quit all applications on your phone and go to home screen
- run "purpledrake_osx.command" which should now work
Inbetween (guess it was directly after running "purpledrake_osx.command") you should get a permission request on your phone which you should allow
Thanks
_ranch said:
Change the USB mode to PTP and you should get the RSA prompt.
Click to expand...
Click to collapse
Thanks, this works for me on El Captain
Also on El Capitan:
After enabling developer settings + USB debugging on phone (see earlier in thread),
Removing the adbkey + pub from the users .android folder (see earlier in thread),
and connecting with PTP,
It finally works
Has anyone gotten their computer find their G4 through cmd (adb devices). I cant get the adb message on my phone to allow access to my computer. I turned on and off usb debugging several times but i still don't see the message on my phone to allow access. I let me computer download the drivers when plugging up my G4 as well as allowing the install of PC drivers.
yes, working great for me. Do u have updated and right drivers? u find tread here with right drivers..
Sent from my unlocked and rooted LG-H815
I was having the same problem..
You need to install the LG Drivers and then your phone will connect via adb..you will be asked on your phone to allow the port connection after installing the proper LG drivers. Verify and you will be good to go..
I used these ones below in the attatchment or you can grab them from.....
http://www.theandroidsoul.com/download-lg-g4-driver-for-windows-and-mac-mtp-adb-download-mode-77723/
I think I found the issue. I had Note 3, 4, Nexus 6, S6 edge, and G4 all still on my computer in the device manager. I uninstalled all of them plus I uninstalled the adb driver in device manager. Plugged my G4 back in and ran the PC driver update via G4 and it worked. I can now see my G4. Don't know if I had to do all that to get it working but hey it worked for me.
I was having issues with this myself and didn't find a solution. I found out that I was having better luck switching it to Camera PTP from the notification dropdown. Sometimes I have to toggle to MTP back to PTP, The dev notifcation should appear when it is actually connected.
1. PTP
(1a. switch to MTP back to PTP if it doesn't work)
2. 'adb kill-server'
3. 'adb devices'
-If you see your device, you can try to 'adb connect **IP**' but it will most likely say it was unable to connect
4. give it your adb commands you want
It's the only way I've been able to get adb, hope this helps!
I was having this issue also. After install win10 then adb connection to my LG G4 (h818) was not detected. Back to android.com, it said that if general USB driver doesn't work then we must find OEM driver to the producer web. LG ADB Driver was about 17MB. After installed the driver then it was immediately detected. Thank God, finally.
I have silly problem. I bought used G4 LG from someone found in online forum. Checked all series on phone (sticker), on software "about phone" all showing LG H815 software version H81510H, but by adb ( linux machine ) showed H812xxxxxx .... set on developer option debugging the command "adb reboot bootloader" just send device into android boot ( device boot ). I wish to unlock the bootloader and put CM. Hard button option > pushing vol up + power button simultaneously did nothing, vol up + power button then > connect to PC via usb, did nothing ( just send phone to device boot ) ..... I have no windows machine
Hello people of the tech world,
Im going spastic over here trying to install Lineage OS on my Xperia.
I looked into 'wiki.lineageos' and 'android geek' and followed the steps....
I have unlocked bootloader, got the code, unlocked oem, downloaded ADB fastboot package (platform tools) from lineage website and (two other websites later on just in case there was a difference), I opened PowerShell from the folder where I unziped the platform tools and powershell says instead of "adb" I gotta write .\adb.... after that a whole buncha text comes out. I typed .\adb devices and it showed me a device. However after going into 'adb reboot bootloader' nothing else works, when I type 'fastboot devices' it says its waiting. When I try to add the code, it doesnt recognize anything.
My computer cmd doesnt register adb at all nor anything after that.
At this point I also have minimal a&f and I tried 15sec ADB which did nothing because it says it cannot find the path. So I tried going into Environment Variables and creating path with the copy/paste technique to the "user variable" AND "system variable" AND creating new paths in each and also paste into existing paths in each. Only thing I didnt try is to put paths everywhere in the same time! and each time I created a path I tried the 15sec adb and it kept saying theres no path.
Minimal ADB works nearly the same as PowerShell and it says the same thing.
Also in the meantime I downloaded Xperia Usb drivers and tried to install it but it has exclamation marks and atm I have no mental capacity to deal with it. It says code 10. and Im in code red >_<" .
In the device manager I see my Xperia under portable devices, and the connection between my phone and laptop works fine, even the Companion works.
Im using HP laptop, win 10 and my Xperia version is 9. Help pls.