I have installed the moto drivers and then connect my Xoom to the B port. I have debugging turned on.
Here's what I get:
E:\xoom>adb devices
List of devices attached
161c110242c015d7 offline
E:\xoom>adb shell
error: device offline
I have run clean and reinstall on the installer without any change.
Any advice?
You need to be in the folder on your computer with adb in it.
Sent from my Xoom using Tapatalk
I am in that folder.
Is your device locked? As in, do you have a lock password/PIN that you need to input first?
Try a different cable.
Different cable no help. Any other ideas?
Just an idea... are you using a USB hub or one of the USB ports from the front of your PC? Sometimes these ports don't provide enough power to communicate with certain devices. Try one of the ports on the back of the PC.
Other than that, reboot your PC and the Xoom and try again
I'll be darned! I plugged it into the back (USB port on motherboard) instead of the front and voila!
You are the man!
Now that you have answered that question so well, please answer this one!
I am trying to run adb install xxxx.apk but it just hangs. I have the Xoom set to allow installation of non-market applications.
Any ideas?
Never mind - a reboot all around fixed that. Thanks for everyone's help.
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
UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/
well I see you fixed it. did you get adb going?
Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk
are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.
Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone
Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???
joevirus563 said:
Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???
Click to expand...
Click to collapse
Go to Settings - Storage - USB computer connection - tick Media device (MTP)
hapahopi said:
Go to Settings - Storage - USB computer connection - tick Media device (MTP)
Click to expand...
Click to collapse
Its already at MTP...
Any way to root without computer?
I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .
Happydondavid said:
I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .
Click to expand...
Click to collapse
Ok and whant have you done to fix it?
New usb cable?
I've not managed to fix it yet . When i plug my TF into my pc it seems to think its charging but the pc doesn't register it at all , if i get a new usb cable and it works i'll report back .
Well does anyone know if this is a problem with the cable or not ?
Happydondavid said:
Well does anyone know if this is a problem with the cable or not ?
Click to expand...
Click to collapse
I have the same problem. I sent my tf101 to the Asus service center to have it repaired. When it came back it would connect to the PC. After a few months it would not connect. Same problem. It appears to me to be software related somehow. In my case the cable has nothing to do with it. None of the suggestions on this or other forums work. Asus does not respond. Maybe Jelly Bean will fix it. Or maybe not.
are you able to ./adb connect to the asus via usb? if so then that will tell you that the problem is not the cable, it's not the usb version, it's not the device hardware. its likely a driver install issue in windows. i would boot into android and make sure that android debugging is selected in the developer settings menu. then try an adb connection. im not sure about how to install all the stupid drivers in windows because i do everything in linux and its soooooo much simpler.
f it is in fact the hardware cable or port that is not working properly then you can always move files to and from the device over wlan connection, with either adb tcp connection, or using some file manager such as es file explorer. just remember as long as you can get an
./adb connection to your android then anything is fixable. ADB IS YOUR FRIEND. get to know it well.
same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?
qandrav said:
same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?
Click to expand...
Click to collapse
I dont ever connect my devices as mass storage to he computers at all. i just do everything via ./adb usb or ./adb tcp connections over wifi. or i use es file explorer setup as an ftp server on my devices and move files around that way if i need to. but i went ahead and pulled out my windows asus tf101 drivers and sync app and linked them for you at the bottom. my advice really is to lose windows and stick with doing everything on android with linux. soooo much better.
https://www.box.com/s/q2j8n7h8xi5o3ld2bt5z
thank you for your long reply! and obv for the files, I'll give it a try!
I admit that sometimes I used swiftp (over wifi) but every time I have to disconnect pc & tablet from the modem...Sometimes use bluetooth but it's too too slow!!! thank you again!!!
I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk
when I rooted moths ago I used "razorclaw" (and my tf101 is a b70). I use adb with other devices and is very cool but I never need to use with the tf101...
joevirus563 said:
I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk
Click to expand...
Click to collapse
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.
The Real Question when USB does not connect.
haxin said:
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.
Click to expand...
Click to collapse
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.
beware of usb cable
Hi,I personnally own a TF101 sb50.
I had some trouble with usb. Tha cable was ok for charging but didn t register correctly under an usb connection ( it showed up and got kicked out in windows didn t register in lsusb on linux)
If you check the diagram for the cable, it s well endowed there 's resistance inside the cable, and multiple connection.
Depending on your version it doesn t use the same pin, even if it's the same cable.
You can buy a cable on ebay for around 10 euro in europe ( i did it s ok) or buy it cheaper from china(no idea about quality).
to sum it up even if your cable work with another TF, it doesn t mean your cable is not faulty ( i have bounce a nano osci on the faulty cable , and it showed no apparent flaw.) and buying a new one was the solution for me.
good luck for rooting (sb50 :: no need to adb)
The ADB thru WiFi solution worked perfectly for me thankfully, and I am one of the many others who have been having major trouble getting Windows and Linux to recognize the Intercept.
Not sure if this is a duplicate post somewhere, but here's my version using Linux:
1. Go to the Play Store and download the 'ADB over Wifi Widget' app.
2. After installed on your device, the app should be on your home screen. Tap it once to toggle on. You should see an IP address and a port #.
Note the IP address, as this is the address of your device.
3. Open a terminal in Linux.
4. CD to the folder that contains your ADB files. (example: cd /androidsdk/platform-tools)
5. Enter the following code:
chmod 755 ./adb
./adb connect <enter IP address here without brackets of course>
6. You should now be connected to your phone.
Hope this helps...
pm124493 said:
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.
Click to expand...
Click to collapse
ok when you say that the tf101 doesnt connect in either your windows or linux machine, what do you mean exactly? you mean it doesnt show up as a mass storage device or an MTP device? and have you downloaded and installed the android-sdk in linux? and when you connect the tf101 to your linux machine, do yo uhave usb debugging enabled in the developer settings menu, and are you using the "./adb devices" command in the linux terminal from your /android-sdk/platform-tools/ directory?
also you should be able to flash a custom recovery which will enable you to flash custom rom without using the usb cable. theres a couple files that you need to put on your tf101 in the /sdcard/ directory first.
one is the recovery blob and if you want to keep the stock rom and kernel but just root it then youll need the superuser zip i have included both of them at the bottom.
for starters you need to install a terminal emulator app on the tf101 from the play store.
then once you have the recovery blob on your device in /sdcard/ you can continue. (remember /sdcard/ is the internal memory not the micro sd card)
start the terminal emulator on the tf101 and enter these commands.
mv /data/local/tmp /data/local/tmp.bak
exit
(open another terminal window on the tf101 and enter these commands)
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
(now reboot the tf101 when it boots into android start the terminal emulator app again then enter these comands)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
exit
(now you should have a team rogue recovery flashed to your tf101)
reboot your tf101.
now you can hold the vol -down button while you power on the tf101 you will see a message at the top of the screen that says soomething like "Checking for RCK" when you see that press the vol- up button right away, this should boot you into the team rogue recovery where you can flash custom roms or just flash your superuser.zip to get root.
hopefully this makes sense and hopefully it works for you.
remember you have to extract the recoveryblob from the zip folder before you move it to the /sdcard/ on your asus. the superuser.zip can remain zipped though.
I had the same problem:
windows will not notice my transformer (rooted).
( usb debugging is on, android 4.0.3 with Android Revolution HD 3.5.1.)
i know in the past it works.
adb list ( of devices) ist empty also. Same Problem with the two cables i have.
can you give me a help what i can do?
Sorry for my poor english
kind regards
gandalf
Hello Helpers, I shattered my Nexus 4 screen, and the phone has a Pin lock, and is currently in Airplane Mode with BlueTooth enabled. It does Not have USB debugging enabled.
My objective is just to pull out the video, audio, and pictures files, after which I would throw the phone away. I appreciate any feedback, or if someone can help me post a reply to "k.janku1" at the post here http://forum.xda-developers.com/showthread.php?t=2786395 Please refer to point (4) below.
So is there a way I can enabled USB debugging or pull my files out? Following are what I have done, and none are successful in accessing the phone:
1) I have an OTG cable with a mouse. Nexus 4 would not recognize it. I did try to have this OTG Cable + Mouse plug into another Motorola phone and it worked, just not Nexus 4.
2) I plug my Nexus 4 into the PC through the USB cable, the Windows 10 recognize it but when I try to browse that Nexus 4, no files show up.
3) I installed the Android Studio 2.2.2, with various SDK (5.0 and 5.1 SDK) + Google USB driver. And then proceed to run the ADB "shell" or "devices" command located in folder "platform-tools", and the command line would tell me -- "error: no devices/emulators found", or "List of Devices attached" but with NO list of devices displayed. I even boot into Recovery Mode and the ADB command still not seeing any phone.
4) I even try the post here, and I could not get it working either -- http://forum.xda-developers.com/showthread.php?t=2786395
i) I tried the steps listed here http://forum.xda-developers.com/showpost.php?p=66731042&postcount=260 but it does not work for me. The step (2) here returned me "No devices", while step (3) is sort of confusing as it involves TWRP (??) and it said BootLoader would erase all my data files!
ii) Another post here in the same thread -- http://forum.xda-developers.com/showthread.php?p=62398797#post62398797 which mentions the use of "Flash through ADB". But then my phone does not have USB Debugging enabled, so how can ADB talk to the phone in the 1st place? And compile his codes in Android Studio perhaps?
iii) Another post of same thread -- http://forum.xda-developers.com/showthread.php?p=61792353#post61792353 which is lengthy and involves self-custom kernel + compile using Kernel Kitchen. Would this really work?
Thanks
Sean
I had the same of your situation i search and tried a lot of things even show the phone screen in pc but me too i didn't have usb debugging enabled, so what i did is :
Flash the stock ROM for my phone by Odin (it don't need usb Debugging enabled it is for Samsung phones) and by flashing new ROM all your files will be stay in the internal storage, after that the files will be showed in the PC, i don't know if u try that before so that is my solution
Sent from my GT-I9300 using Tapatalk
Xkirnel99 said:
...
Flash the stock ROM for my phone by Odin (it don't need usb Debugging enabled it is for Samsung phones) and by flashing new ROM all your files will be stay in the internal storage, after that the files will be showed in the PC, i don't know if u try that before so that is my solution
Click to expand...
Click to collapse
Thank you for the hint. But I doubt if this approach would work for Nexus 4. I searched online for Odin + Samsung, seems like Samsung phone has a Download mode where the phone would accept the new image file put to it. There is no such mode for Nexus 4, so the phone would not read anything in easy steps like Download mode.
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