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
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
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Unable to connect to usb
I installed Carbon-cr-5.1-moo-release-bacon-20180202-1444.
I am unable to get usb connection working and having tried many different things...
-I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
-In Android Studio SDK Tools I have installed Google USB Driver v12.
-I have developer options turned on and Android Debugging turned on.
-When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
- when I go into developer options and hit 'select usb configuration' my selection of mtp or whatever is always ignored and charging selectiomn remains
-Device Manager / Portable or Other devices does not have the phone beneathn it.
-When I run adb devices in cmd there are no devices attached.
-I cannot find a OnePlus One adb usb driver. I thought I found one but I have no way to verify and after installing it made no difference
I want to update to the latest rom in case this may be the cause, but after I download it to the phone and click flash
I just get the oneplus icon forever and the recover app twrp does not come up. It used to be there but then after I installed
the first rom after a couple of uses it disappeared for some reason or at least will not boot to it.
When I installed that first custom rom I folowed instructions for rooting and on completion it says to open up the installed
su app but when you open it it says there is a more up to date version but when you try to install that it fails.
Now all the apps that will not run if your app is rooted say it is rooted and all the apps that will not run unless it is rooted
say it is not rooted.
I think I need connection via usb in order to reinstall the twrp recovery app in order to install an up to date rom, hoping this may help
me solve the usb issue, but I cannot get the usb connection working as described above,
any hehlop would be appreciated.
Same Situation
hardya said:
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Click to expand...
Click to collapse
but my phone connects in edl mode just for 10 seconds and then automatic
windows 10 is showing
Unknown USB Device (Device Descriptor Request Failed ) in device manager​when I connect windows prompts this message -"the last usb device you connected to this computer malfunctioned and windows does not recognize it"
I enabled USB debugging and changed default USB config to MTP
installed drivers again and again in both Linux and windows
I switched operating systems (windows, ubuntu and kali )
I switched laptops and tried every single port of both laptops
I tried miui USB settings app from playstore
I tried using ADB commands from the terminal but no device detected
I entered fastboot mode on phone and then run fastboot devices but still no device found
I used GMTP in ubuntu which worked fine on another phone having somewhat similar issue but it also didn't work
I changed 4 USB cables (3 of them were original mi cables )
I tried using Pendrive using otg but it also didn't work
My laptop worked fine with other phone
I also hard reset my RN5 Pro
I basically tried every fix shown on youtube and XDA threads as well as random google search websites
Please help me what should I do ..
please ....
Download Miflash 2021 version.
Run it and install driver.
Then reboot PC.
pl1992aw said:
Download Miflash 2021 version.
Run it and install driver.
Then reboot PC.
Click to expand...
Click to collapse
are u saying should I flash the stock miui again in my phone using mi flash ??
shaurya_needs_help said:
are u saying should I flash the stock miui again in my phone using mi flash ??
Click to expand...
Click to collapse
No, the driver probably did not installed correctly.
Install the driver. Miflash has the driver needed.
shaurya_needs_help said:
windows 10 is showing
Unknown USB Device (Device Descriptor Request Failed ) in device manager​when I connect windows prompts this message -"the last usb device you connected to this computer malfunctioned and windows does not recognize it"
I enabled USB debugging and changed default USB config to MTP
installed drivers again and again in both Linux and windows
I switched operating systems (windows, ubuntu and kali )
I switched laptops and tried every single port of both laptops
I tried miui USB settings app from playstore
I tried using ADB commands from the terminal but no device detected
I entered fastboot mode on phone and then run fastboot devices but still no device found
I used GMTP in ubuntu which worked fine on another phone having somewhat similar issue but it also didn't work
I changed 4 USB cables (3 of them were original mi cables )
I tried using Pendrive using otg but it also didn't work
My laptop worked fine with other phone
I also hard reset my RN5 Pro
I basically tried every fix shown on youtube and XDA threads as well as random google search websites
Please help me what should I do ..
please ....
Click to expand...
Click to collapse
hi, @shaurya_needs_help, did you solve the issue?.
Hi,
I cannot connect to my Pixel 3 via adb any more. I last tried when I installed the system a year or so ago, and was able to. I am using a linux machine, and have tried the following:
- Two different computers
- Two different linux distros
- Many, many (new, high-quality) USB cables, both USB-C and USB-A/B
- Developer mode enabled
- USB debugging enabled, authorizations revoked and re-enabled
- Setting default USB configuration to File Transfer/USB tethering/MIDI/PTP/No data transfer
- Airplane mode
- Connecting over a USB-2.0 hub
- Booting the device to recovery mode, enabling adb
Regardless, I have the same outcome. The phone charges but no other recognition of being plugged in is made. That is, the computer cannot see the phone in 'adb devices', 'lsusb' or 'dmesg'. The phone doesn't see the computer either, in that it doesn't bring up the USB notification.
Any thoughts would be much appreciated. I am running lineageos 18.1, and the reason I wanted to connect via adb is to upgrade to 19.1.
Thanks in advance!
furrymonster said:
Hi,
I cannot connect to my Pixel 3 via adb any more. I last tried when I installed the system a year or so ago, and was able to. I am using a linux machine, and have tried the following:
- Two different computers
- Two different linux distros
- Many, many (new, high-quality) USB cables, both USB-C and USB-A/B
- Developer mode enabled
- USB debugging enabled, authorizations revoked and re-enabled
- Setting default USB configuration to File Transfer/USB tethering/MIDI/PTP/No data transfer
- Airplane mode
- Connecting over a USB-2.0 hub
- Booting the device to recovery mode, enabling adb
Regardless, I have the same outcome. The phone charges but no other recognition of being plugged in is made. That is, the computer cannot see the phone in 'adb devices', 'lsusb' or 'dmesg'. The phone doesn't see the computer either, in that it doesn't bring up the USB notification.
Any thoughts would be much appreciated. I am running lineageos 18.1, and the reason I wanted to connect via adb is to upgrade to 19.1.
Thanks in advance!
Click to expand...
Click to collapse
What version of platform-tools (adb) are you running?
I installed LineageOS 18.1 on my Pixel 3 back in April of this year.
I grabbed the latest platform-tools (33.0.1) for Linux at the time and I am able to connect, transfer files, etc. with no issues.
Below is the version I have installed on my Linux desktop . Hope this helps.
$adb --version
Android Debug Bridge version 1.0.41
Version 33.0.1-8253317
Installed as ~/bin/platform-tools-r33.0.1/adb