Can someone explain me how to get ADB working on my SGS8? I've tried everything: installing drivers, Java, Android SDK, 15 sec adb driver, universal ADB driver, minimal adb. I can't figure out how to do that.
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
jaannnis said:
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
Click to expand...
Click to collapse
Thanks, will try that
i was having one hell of a time as well. I tried everything on my laptop to no success. So i actually gave up. Than i thought well maybe its my laptop. So i ended up trying another one i had in the house and viola it worked like a charm. It seems like certain pc are just unable to connect to the samsung s8 via adb mode. Which is totally weird because I had been using adb mode on my pixel xl with no issues what-so-ever. So try a different pc if you can, it worked for me flawlessly.
Might be the USB port.
I had a similar problem connecting my Lenovo laptop to a Kindle Fire. I used a different USB port and everything worked.
9 bin
Related
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "ADB devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
shouldnt it be adb devices instead of dab ?
I wanna try this ABD but there no link?!!
Shouldn't this ABC post be somewhere else?
you guys should quit cluttering this thread and help him figure this whole KFC thing out....
sheetmetalninja said:
you guys should quit cluttering this thread and help him figure this whole KFC thing out....
Click to expand...
Click to collapse
You're right.
But I also don't know anything about BAD or FASTBOOB or anything like that. I don't like reading. :[
yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.
Check the drivers, you may need to update them
Sent from my Desire HD using XDA App
taney said:
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.
Click to expand...
Click to collapse
how 2 do that? i mean what do you mean with devmgmt.msc(device management...?)
1) usb cable is good, the original one. also tried different usb cables, it doesn't matter.
2) usb port is also ok, other devices running out of the box (f.e. dvd drive oder dslr)
3) adb driver already updated via "Android SDK and AVD Manager".
i installed Android SDK tools, SDK Platform tools, sdk platform (--> is there sth. missing?)
Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again
Romanbb said:
Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again
Click to expand...
Click to collapse
no sorry...won't work..
getting the same:
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
also tried without fastboot rebooting.
there are news guys:
just got an windows 7 personal computer for a couple of days.
installing the sdk and usb driver just worked fine.
why it doesn't work for mac?
already installed all new...
You may also check the cable you're using to connect the phone to your Mac. I was getting the same problem when trying to use the cable from my car charger - the phone was not even visible on the system list of USB devices. Using the cable that came with the phone did the trick.
(although if you used the same cable with Windows and it worked, my hint won't be of much help)
Do you got HTC sync installed on your PC?
TheStigx said:
Do you got HTC sync installed on your PC?
Click to expand...
Click to collapse
please remember - i'm using a MAC!
so finally i tested my device with several computers at the university.
i just found out, that the problem may been caused of my installed mac osx lion - but don't ask me why!
on the mac of my prof (also osx lion with latest updates) it worked out of the box...
--> so i'm gonna making backups now and will format my hard disk and reinstall lion again.
i'll give u feedback again ;-)
Have you closed the htc-sync application? solved the connection-error for me...
Maeffjus said:
Have you closed the htc-sync application? solved the connection-error for me...
Click to expand...
Click to collapse
again guys:
I'm using a MAC!
is there any official sync app for mac i don't know about??
ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.
yasinis said:
ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.
Click to expand...
Click to collapse
ok, just found out where the problem was caused. it was EasyTether!
this will help:
Code:
If you have installed EasyTether on OS X, the EasyTetherUSBEthernet.kext can prevent adb from communicating with your mobile device.
If you use Easy Tether, BEFORE you plug in your phone run:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
(or unplug/plug your phone in after)
If you are done debugging and want to use EasyTether again, either restart or:
sudo kextload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If you want to remove the EasyTether kext so it never hassels you again:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
I believe you need the android usb drivers supplied by google to get it to connect. They can be downloaded using the sdk package manager. Also I'm not sure it will work having the Samsung drivers installed and you may have to uninstall them first.
they are installed already since i installed the whole sdk manager pack
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
ringnutz said:
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
thx for answer but I already done that..any other suggestions?
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
What drivers are showing up when you plug in the device? If it says Samsung then you don't have the android drivers installed. And I believe you can't have both installed only one or the other as only one will load when you plug in the device not both.
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
tzacapaca said:
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
Click to expand...
Click to collapse
When you plug the device in, under Device Manager in Windows, there should be listed Android Composite ADB Interface under the device. If not the Google USB drivers were not installed properly.
yeah I dont think my theme is the culprit, there are many reasons why ADB wouldnt show devices. Also Heimdall>Zadig is good for drivers.
run sdk manager and install latest google drivers as well.
are you on Windows OS?
nope,not your theme its the culprit..cuz i didnt install it and i cant install it cuz of no adb connection which is required by a tool named AutoDEOTool1.0.3
I installed latest google driver via sdk manager too..
yes,on Win 7 64 bits
*pulling hair*
I didn't have my usb cable yesterday to check it out but adb actually works with the Samsung drivers. Device Manager>Android Phone>SAMSUNG Android ADB Interface. And when I type the command "adb devices" it shows up. This works both if you plug the tablet in wihtout powering it up and when its turned on so I'm not sure what your problem is. I do have Kies installed on the laptop too so yours should be working if you installed the sdk and drivers correctly.
Which Tab do you have? I have the 6210 unlocked wifi only, it could be other models work differently. Not sure if you have a locked bootloader that you can access the tab through adb.
GT P6200 European
and here is what i get on cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tavi>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
C:\Users\Tavi>adb devices
List of devices attached
C:\Users\Tavi>
EDIT:SOLVED!
Thank you all for answers
How did you solve this?
I input in cmd adb fastboot reboot and suddenly the device got the command and then recognized my tab..(pretty strange i know)
make it done
tzacapaca said:
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
Click to expand...
Click to collapse
do this steps:
1) remove battery
2)insert battery
3) connect the phone via usb will turned off and leave it till usb android phone installed
4) turn ur android phone on
5) wait for full boot
6) install Motorola usb driver .zip attached down there
7)select charge only mode
8) then write the commands of tacoroot.bin
9) when all is done hit the thanx button
ADB wireless
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Unitedforlife said:
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Click to expand...
Click to collapse
What do u mean adb wireless?
adb devices doesn't show anything. I have tried it with linux and windows (with Motorola drivers installed), it doesn't work. I can access the phone when I have enabled MTP, but it just won't show in adb. I have killed and started adb server so many times, it's frustrating.
The thing is, the first time (yesterday) it worked! I could reboot into fastboot with adb but then nothing worked anymore.
Any ideas?
Maybe silly question, but: is USB debugging activated on the phone? If yes, try to switch between MTP and Camera (PTP) under "USB computer connection" option. You should get the authorization prompt on your phone when everything is fine.
Yes, USB debugging is activated. I already tried both MTP, PTP, and neither, but I don't get any authorzation prompts. I revoked all previos prompts, but still nothing. Thanks for the suggestion though!
Are you on bootloader or recovery or normally on os
I tried all three.
Try playing with the USB cable - change it, change the USB slot on the PC that it's connected to, etc.
I only have one USB cable, but I already tried it on several USB slots.
It worked! I had to put sudo in front of my adb commands! Yay! :victory:
I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.
Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk
Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!
Hello all,
My OnePlus 7 Pro, can't recognize USB through my Windows PC, I don't get the prompt to connect to my Win PC.
Also I enabled ADB with Developter Options. I go to fastboot and also after adb devices and fastboot devices command, he can't recognize my device.
My OnePlus 5T is working with ADB and normal USB Win PC, tried two cables and laptops.
I did an run Android 10, now 11, beta etc nothing works! The phone can charge etc.
Please help. Reset etc tried also.
it is known issue ADB don't work on USB 3.0 ports
just goto BIOS > Advanced > USB > XHCI and change the setting to Disabled.
This will make the ports run in USB 2 mode, and fastboot and ADB works as usual.
ineedroot69 said:
it is known issue ADB don't work on USB 3.0 ports
Click to expand...
Click to collapse
Can't confirm this. At least latest version of ADB works at me with USB 3.x ports.
Nvm I didn't read the thread well if the PC can detect the other phone on ADB perhaps you can try "revoking USB debugging authorization" so it would ask for permission again