im trying to load into adb but it won't find the device, usb not reading. can anyone help?
the_rorshach said:
im trying to load into adb but it won't find the device, usb not reading. can anyone help?
Click to expand...
Click to collapse
You need the Samsung USB drivers installed first and the adb binaries on your PC.
Can you link me somehow to enable ADB? I keep having issues with that even though i have android studio and the SDK installed.
the_rorshach said:
Can you link me somehow to enable ADB? I keep having issues with that even though i have android studio and the SDK installed.
Click to expand...
Click to collapse
You can download the adb binaries as part of the Google platform tools package.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Open a command prompt from within the folder where the adb binaries are.
Gotcha, just got issues on win 7
Related
Hi all,
I've searched the forums (honestly), but I can't find an answer to my problem.
I have a Vodafone branded 32B phone.
I installed the AndroidSDK as supposed to, added the path, made the phone root, booted into the recovery console using fastboot and flashed my phone with different operating systems... but during all this time I hever got ADB to work.
Whatever I do, adb never finds the phone. Fastboot works and finds it, when it's in fastboot mode, but ADB never. So, I can't permanently install the recovery console nor do any of the other funky stuff.
ADB doesn't work when the phone is in fastboot mode nor normally operating. I have USB Debugging turned on. The phone works normally and I can access the SDCard just fine.
Any help?
Suggestion.
Look into purchasing a G1 to be kept as a spare and used for development. That's what I've done with my G1. GParted is within most recovery images nowadays, therefore you can do most anything there, well...important functions that is. Keep that in mind.
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Reignzone said:
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Click to expand...
Click to collapse
that's what i had to do to get it to recognise my phone.
i'm pretty sure the driver came with SDK. either way i've attached the one i used.
go into device manager and update the driver it's currently using with the attached one.
Incorrect driver.
It should be the 1st driver listed in the Android SDK file.
As far as I know, you could also choose to push ADB to your system32 file folder under the C: drive in your computer. That is if you're using a Windows machine.
just a thought
Are you on windows or linux? If you're in ubuntu try sudo adb ... the default unprivilaged user doesnt automatically have access to the device.
If you're in Windows I would uninstall the Android Phone device in device manager and reboot with the phone disconnected. Then connect it and install the usb driver from the sdk when prompted. Might also pay to download the sdk again.
Install HTC Sync
Another known way to fix the issue is to download and install HTC Sync http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
This seems to install the correct drivers
For more info check the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec02
Hey Guys,
Forgot to mention I'm on Windows Vista 64 bits.
That last suggestion did the trick. I went to the site and downloaded the HTCDriverUpdate_Vista_64bits.exe, and within seconds I had an ADB connection.
Thanks for your help!
BUT I've forgotten how. And I'm doing the best I can from memory. (Trying to do on windows XP and 7)
Now if I recall, the only way to install the drivers for the n1 to be used for ADB is when it's in "fastboot" mode and you have the Google USB packages correct?
Well I open up the SDK package list and there is no Google USB package to download. Did I forget something?
Thanks for your help guys I've looked as hard as I can for these answers to no avail.
Shameless bump
http://forum.xda-developers.com/showthread.php?t=879701
I have fresh installed N7 3g 4.2.2
adb devices show me "device offline" on Linux.
Do anybody help me solve?
AW: 4.2.2 adb device offline
It's a New security feature: in your device a popup with a hash key should be shown asking you whether you would allow the PC to connect to your device. After accepting that, the device can be accessed from the PC.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
It's a New security feature: in your device a popup with a hash key should be shown asking you whether you would allow the PC to connect to your device. After accepting that, the device can be accessed from the PC.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you for answer. But I don't see popup window.
I install TWRP. Then in recovery mode install root access.
Now I can use local shell via android terminal with su.
Code:
setprop ro.adb.secure 0
getprop ro.adb.secure
1
How to change this property?
seting in /system/build.prop didn't help
Solved. Latest adb installed. Popup fingerprint window appeared.
svs57 said:
Solved. Latest adb installed. Popup fingerprint window appeared.
Click to expand...
Click to collapse
sorry for noob question but how you update your adb?
Yeh how do you update adb, is it through sdk manager
Sent from my Nexus 7 using XDA Premium HD app
azfarmiera said:
sorry for noob question but how you update your adb?
Click to expand...
Click to collapse
Download the android adb fastboot files in this thread link and if usb debugging is enabled and you connect your phone to you computer you should get a pop-up on your phone. It worked for me
http://forum.xda-developers.com/showthread.php?t=2144709
Also I think I opened the fastboot.exe and adb.exe files too
I couldn't update through SDK manager, t just kept popping alert that I need dependant lib, so I just uninstalled whole SDK and installed again, worked like a charm.
azfarmiera said:
sorry for noob question but how you update your adb?
Click to expand...
Click to collapse
To update ADB use SDK Manager.
For some reason the SDK Manager does not automatically show the new release versions of Android SDK Tools and Android Platform-Tools, so if the versions of your Android SDK Tools and/or Android Platform-Tools are respectively older than 21.1 and 16.0.1, you will need to first delete them then reload the SDK Manager to get their new release versions to be displayed and available for installation.
Also, it appears that Android Support Libraries (under Extra) is also required for ADB to work, so you should install it as well.
Also, to get ADB-over-WiFi to work, first use ADB-over-USB to the same given PC/Laptop and grant access with "always" box checked.
digixmax said:
To update ADB use SDK Manager.
For some reason the SDK Manager does not automatically show the new release versions of Android SDK Tools and Android Platform-Tools, so if the versions of your Android SDK Tools and/or Android Platform-Tools are respectively older than 21.1 and 16.0.1, you will need to first delete them then reload the SDK Manager to get their new release versions to be displayed and available for installation.
Also, it appears that Android Support Libraries (under Extra) is also required for ADB to work, so you should install it as well.
Also, to get ADB-over-WiFi to work, first use ADB-over-USB to the same given PC/Laptop and grant access with "always" box checked.
Click to expand...
Click to collapse
So is version 21.1 and 16.0.1 the latest of their builds? And if I install those, I will not have a problem with the adb being offline?
Leonhan said:
So is version 21.1 and 16.0.1 the latest of their builds? And if I install those, I will not have a problem with the adb being offline?
Click to expand...
Click to collapse
I use Android Debug Bridge version 1.0.31.
http://developer.android.com/sdk/index.html
http://dl.google.com/android/adt/adt-bundle-linux-x86.zip
Leonhan said:
So is version 21.1 and 16.0.1 the latest of their builds? And if I install those, I will not have a problem with the adb being offline?
Click to expand...
Click to collapse
They are the latest version and solved the problem for me.
Sent from my Nexus 7 using XDA Premium HD app
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?
Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!
feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly
Can someone guide me how to get ADB working on OnePlus 5?
stalvekio said:
Can someone guide me how to get ADB working on OnePlus 5?
Click to expand...
Click to collapse
i'm using 'block this!'
What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options
colin.pohle said:
What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options
Click to expand...
Click to collapse
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers
stalvekio said:
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers
Click to expand...
Click to collapse
Try these.
I had driver issue for side loading even after Installing OnePlus drivers windows wanted to use standard ADB drivers
Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!
What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.
ddaharu said:
What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.
Click to expand...
Click to collapse
Adb still somehow has to work... The drivers are there (although all my win 10 devices installed the correct ones automatically) and it doesn't even really matter which adb he is using
shadowstep said:
Try these.
Click to expand...
Click to collapse
I tried. Device manager still shows adb interface yellow.
d0nsman said:
Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!
Click to expand...
Click to collapse
I did that. ADB devices gives me empty list.
stalvekio said:
I tried. Device manager still shows adb interface yellow.
Click to expand...
Click to collapse
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.
shadowstep said:
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.
Click to expand...
Click to collapse
win 8.1.
Did as you sugsested but no change .... adb interface is yellow
stalvekio said:
win 8.1. Did as you sugsested but no change .... adb interface is yellow
Click to expand...
Click to collapse
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:
shadowstep said:
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:
Click to expand...
Click to collapse
Nope. No help.
I think it´s something very easy i have missed
Finaly - got it working.
This guide helped:
http://www.asunsoft.com/android/how-to-manually-install-usb-driver-for-android-phone.html