Hi,
I'm running a GOCLEVER R75 tablet.
I succeeded in installing the USB drivers to Windows XP pro from the last SDK I downloaded previously.
But I can't install other drivers:
C:\> c:\AndroidSDK\adt-bundle-windows-x86\sdk\platform-tools\adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
Although I can see in Windows Device manager Android Phone - Android ADB Interface, some applications still write they can't see
my Android device. I also can't see the tablet number.
Please, how should I proceed further? THX
AW: [Q] Can't Install ADB drivers from SDK
If you're using a firewall make sure that the adb is not blocked. Is debug mode ticked?
Sent from my Nexus 7
-star- said:
If you're using a firewall make sure that the adb is not blocked. Is debug mode ticked?
Sent from my Nexus 7
Click to expand...
Click to collapse
Sure, I met these provisions..
More severe is the fact I cannot start the SDK Manager in the bundle!
It merely will not start while I'm double-clicking it in order to proceed further. It's just blinking.
Running Win XP Pro SP3. Suppose, it may have something to do with JAVA?
AW: [Q] Can't Install ADB drivers from SDK
cuneiform said:
Sure, I met these provisions..
More severe is the fact I cannot start the SDK Manager in the bundle!
It merely will not start while I'm double-clicking it in order to proceed further. It's just blinking.
Running Win XP Pro SP3. Suppose, it may have something to do with JAVA?
Click to expand...
Click to collapse
You need the java sdk (6?). Tried to launch the manager as administrator? Mhhh... The only thing I additionally installed was the adt plug in for eclipse when I used windows.
Sent from my Nexus 7
-star- said:
You need the java sdk (6?). Tried to launch the manager as administrator? Mhhh... The only thing I additionally installed was the adt plug in for eclipse when I used windows.
Sent from my Nexus 7
Click to expand...
Click to collapse
True, as Administrator...
Well, meanwhile I was able to root my tab GOCLEVER R75, as I had applied UnlockRoot 3.1, a couple of Superusers got installed at the same time:
UnlockRoot ver. 3.1:
Kill adb server
Starting adb server...
Get online devices
Starting adb server...
Get online devices
chmod file 777 /data/local/tmp
push file to device : rootutility
chmod file 755 rootutility
push file to device : busybox
push file to device : su
chmod file 755 busybox
push file to device : su
Rooting, please wait...
Root Succeed!
Root finished!
How come when I write
C:\adb\adb devices
I'm still getting the same
C:\List of devices attached
plus only some empty space - No devices detected!
There are no question signs in Device Manager in Windows around Android Phone, Android Composite ADB Interface. So, some drivers have been installed.
The procedures described in the following did not work for me:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Related
Howdy everyone!
Without further ado, I humbly present my gift to the community (and the #nookcolor irc channel )
This collection of scripts will automagically install:
NookColor USB ADB Drivers
The necessary adb_usb.ini file for adb to recognize the NookColor
A stripped-down copy of the Android SDK, with just the requirements for adb.exe
adb.exe is added to your %PATH% variable.
Tested on Windows 7 32/64, Windows Vista 32, Windows XP SP2/SP3
Now I realize not everyone wants the do-all end-all script, so there's two versions: one that contains the drivers AND a cut down Android SDK, or the version that only installs the ADB driver and the proper adb_usb.ini file.
Instructions for use with combo pack (please read!):
Download the combo pack
With your NookColor unplugged from your PC, run the nookcolor-easyADB.exe file and allow it to extract to c:\
Follow the on-screen instructions and wait until you see "All done!"
Plug in your NookColor, tell Windows not to use Windows Update, and let it search your computer for the proper drivers.
Once the package has finished installing, and the drivers are installed, you can just open a command prompt window and type:
Code:
adb devices
If you see your device's serial number listed, you're good to go!
Instructions for the driver-only pack:
Download the driver-only pack
Extract it somewhere on your PC (may I recommend c:\android-sdk-windows\usb_driver ?)
Run install.exe in the extracted folder and follow the onscreen prompts.
For those of you that would like, the source of the driver installer is contained in both downloads as install.au3. Driver installation is accomplished using dpinst.exe from the Windows Driver Development Kit.
Also, to avoid any confusion, I am also known as IOMonster on IRC.
Okay now for the good stuff...
DOWNLOADS:
Combo Pack (all in one!): http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
Driver only pack: http://legacyschool.us.to/nookdev/nook-usb-installer.rar
Update: 0.2 version has been released. Should fix CPU architecture errors when installing. I have also changed the download protection on my server, you should be able to use download managers now.. just keep it to a sane number of concurrent downloads by IP.
Troubleshooting:
Make sure you're rooted
Sounds dumb, but trust me, it's happened.
Make sure you haven't used ADBWireless and forgotten to disable it
Guilty here. I spent a good half hour trying to figure out why it didn't work on one of my Nooks until I realized that I had left ADBWireless on.
Check device manager for a "Nook" device, you may just have to do an "update driver" on it
Just like it says, check for any devices labeled "Nook" or "USB Composite Device" with a VID of 2080
Uninstall ALL Nook-related devices in device manager
Check device manager for any USB devices (usually USB Composite Device or USB Mass Storage) with a VID of 2080 and PID of 0002, uninstall 'em and unplug/replug your Nook.
Please note that this is a VERY initial build. It may not work for you under some circumstances, but on the few machines I've tried it on, it seemed to work for me. If you encounter any weird bugs, please let me know- I'd love to know so I can fix it.
(As a side note, I really need to standardize my nomenclature for my driver pack..)
excellent work, thank you
This is awesome! Thanks!
nice job...I had helped test it in the irc channel for ya. I def think this will be great for the community now we just need something to root and and superuser. Anyway good job
First post. Wanted to let you know it worked on my windows7 x64 machine perfectly fine. so much easier than the long way.
I'm using Windows 7 32bit. I unzipped the driver pack, clicked install.exe, then it said something about not having a correct version of windows and to get windows 7 x86 or x64, then a window popped up saying it successfully installed. Assuming that it didn't and using my extreme deduction skills, I opened DPInst.exe and it did it's thing and installed fine. Don't know what happened with install.exe but it works now. Thanks!
Strange... do you remember the exact text of the error?
My install.exe runs DPInst.exe with the /q (quiet) switch, so it shouldn't have even given an error (even if there was a legit error message thrown by DPInst.exe).
Do you think you had install.exe set for compatibility mode? (check the properties for install.exe and possibly DPInst.exe)
Thanks for the feedback! I sure hope this alleviates most of the headaches associated with installing ADB on Windows.
The links are dead, can someone post them somewhere else?
Fault when I install but it installs fine.
It installed fine even though I got this message.
EDIT::::
Ignore me - I missed uninstalling the USB device...
Worked perfectly THANK YOU!
Rylynmila said:
It installed fine even though I got this message.
Click to expand...
Click to collapse
Are you by chance running Windows 7 32-bit?
And as for the links being dead, try disabling your download manager. I see people's download managers trying to do something like 20 concurrent downloads, and my server disallows that.
Rylynmila said:
It installed fine even though I got this message.
Click to expand...
Click to collapse
Hi, I did encounter this similar error as Rylynmila.
BTW, I am running WinXP SP2.
Hm, that's strange.. this worked on my XP SP2 machine, I wonder if it's possible that some machines report the architecture differently..
I'll make a quick script that should let me figure this out easier. It's probably just an error in my script's logic for deciding which version to use.
EDIT: Newly released version has been uploaded. This should fix the CPU architecture problems.
Ah, well, just found the culprit! My AutoIT script checks the architecture of the CPU itself, not the OS you're running.
On the Windows XP machine I tried it on, the CPU itself is only a 32-bit cpu (Athlon XP 3200+), therefore it reported it right.
I should have used @OSArch rather than @CPUArch in AutoIT. Oops.
I'll make an updated version and release it later today.
cant seem to get this working on my 64 bit vista machine.
installed fine, but adb devices shows nothing
DrewLGT said:
cant seem to get this working on my 64 bit vista machine.
installed fine, but adb devices shows nothing
Click to expand...
Click to collapse
When the installer came up, did it give you any errors? Check the device manager- you should have an entry for Android Phone -> Android Composite ADB Device.
If you do have that entry, try running
Code:
adb kill-server
then
adb devices
and see what you get.
thecubed said:
When the installer came up, did it give you any errors? Check the device manager- you should have an entry for Android Phone -> Android Composite ADB Device.
If you do have that entry, try running
Code:
adb kill-server
then
adb devices
and see what you get.
Click to expand...
Click to collapse
my wife is using the NC right now, so i'll give that a try when shes done.
i have another question though. i already had adb installed for my phone, now i have it twice. can i combine the two?
If you just want the ADB driver, just download the driver only pack.
If you had adb installed already, this will overwrite it if it's installed to c:\android-sdk-windows.
no luck with easy adb
I have xp and followed the directions given in the first post in this thread for the combo pack. I now have a lot of files in c:\android-sdk-windows\ but when I follow these directions (from Nook Devs) I do not get the proper output...
"Start > Run > cmd > Enter
* cd\
* cd android-sdk-windows\platform-tools
* adb kill-server
* adb devices
If you get output that looks like the following you have succeeded:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[YOUR NOOKCOLOR SN] device"
For my output, I get the first three lines but not the
[YOUR NOOKCOLOR SN] device
I looked in Device manager and do not see anything about Android in there. I am obviously an android noob - can anyone help me? Thanks
Can't wait to try this. Thanks!
I consider myself pretty proficient with electronics and computers but I could never get ADB working on my Win7 64 PC no matter which set of instructions I followed. The benefit of this is that I've learned how to use Root Explorer to accomplish a lot of things.
EDIT: This worked perfectly on my PC, although I wasn't prompted to install any drivers. Guessing I had already done so previously trying to get this to work. Thanks much!!
im using windows 7 64bit and trying to learn adb and cmd
i was watch how to install adb and following..
after installing adb and drivers and added adb on system variables
i type cmd and then typed C:\android-sdk-windows\platform-tools
after that i typed adb devices but got an error
C:\android-sdk-windows\platform-tools\adb.exe is not a valid Win32 application.
what do i have to do here?? T.T
If I'm not mistaken in Win7 64, the Android SDK installs ADB to c:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe
feedhead said:
If I'm not mistaken in Win7 64, the Android SDK installs ADB to c:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe
Click to expand...
Click to collapse
that is correct. i'm on win 7 x64 and its there.
Type cd then space in front of C:\....
That changes directories.
Sent from my ADR6400L using XDA Premium App
qudwis said:
im using windows 7 64bit and trying to learn adb and cmd
i was watch how to install adb and following..
after installing adb and drivers and added adb on system variables
i type cmd and then typed C:\android-sdk-windows\platform-tools
after that i typed adb devices but got an error
C:\android-sdk-windows\platform-tools\adb.exe is not a valid Win32 application.
what do i have to do here?? T.T
Click to expand...
Click to collapse
First confirm that adb installed where you think it did.
Code:
C:\android-sdk-windows\platform-tools
Hit the start button in Windows and copy and paste your path from above into the Search programs and files box. If the path is valid, Windows Explorer will open to that directory.
If the path is not valid, try typing adb.exe in the search box to see if Windows knows where it is. If it comes up in the search results, right click on it and select "Open file location" and Explorer will open to where it is installed.
Once you have verified where adb is, you should be able to pick up from where you ran into a problem.
I attached the .pdf that I followed when I first installed adb ... I wish I remembered where I got it so I could credit them appropriately. The screen-shots might be helpful to you.
(Note: there is a typo on page 8 where the System Variables are setup paltform should be platform)
Oops the file was too big.
It is zipped and attached to this post.
Edit: I found where I got the document from. http://forum.xda-developers.com/showthread.php?t=1009419
http://forum.xda-developers.com/showthread.php?p=9959449
Hi,
i have the latest android sdk installed on my pc. If i try to connect my new Yuandao N101 tablet it is not recognized by adb.exe devices. adb.exe is version 1.0.29.
If i kill the adb service and start adb 1.0.26 from SuperOnClick rooter it recognizes the device and rooting works without problems.
As device driver for adb i am using the one included in PDAnet.
I tried to exchange the adb.exe in the android sdk with the 1.0.26 version. After this eclipse/adb recognize the device and are able to install apk files and start them. But after this the connection breaks. Seems that current sdk is unable to work with adb 1.0.26.
Any idea how i can make it for adb 1.0.29 to work with my tablet?
Best regards, Udo
Hi,
no one an idea? I tried a lot today but still am unable to get the yuandao n101 to work with adb 1.0.29. It just did not recognize the tablet.
With adb 1.0.26 everything seems fine - but i have to use the current android sdk. Someon an alternative driver out there?
BTW: I am using Windows Vista x64
Ciao, Udo
Thanks so much for posting this.
likal said:
Thanks so much for posting this.
Click to expand...
Click to collapse
I have the exact same problem with a YuanDao N90FHD in win7 x86. it gets detected in adb 1.0.26 but not in 1.0.29. any solutions? (also tried instaling htc sync but no luck)
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Thanks. Very useful! :good:
for me and the HTC One X it wont work.....
-Happy Feet- said:
for me and the HTC One X it wont work.....
Click to expand...
Click to collapse
Did work previously?
maybe restart the adbd on the phone.
Can you test in Recovery, Cwm has an extra button for restarting.
Maybe Stock too.
Illidan Pornrage said:
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Click to expand...
Click to collapse
Fraid it didn't work. End up with various errors and randomly appearing devices. Plus, the original error reappears eventually. Please help!
If you give me some Info around the issue, like what you intended to do and if it worked previously, I could help you.
FIX adb offline problem
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window
------------------------------------
After that you every thing will be OK
this solved my problem
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
ciano865 said:
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
Click to expand...
Click to collapse
as far as I know adb doesn't work in bootloader mode.
MadMan29729 said:
as far as I know adb doesn't work in bootloader mode.
Click to expand...
Click to collapse
How can I push file to phone it doesn't boot ?
I think thats intentional, bootloader mode is the mode corresponding to fastboot for directly flashing, deleting, formatting, stuff like that in the most basic environment. Try recovery or normal boot for adb, which is for debugging, shell access, backup, filetransfer and so on.
(More info for more specifics)
Thanks, my mistake not using recovery
from Nexus 4 with Tapatalk
took me a bit to get into the thing myself after > 4.2 update
i'm on ubuntu
i had to use the terminal command
Code:
android update sdk --no-ui
a couple of times to get the thing actually updated. using just
Code:
android update sdk
wasn't cutting it for some reason. probably because i'm stupid and didn't fiddle with it enough.
then, realized when i STILL couldn't access the device (even after accepting the computer's RSA key on my n7),
it was because i had previously put a now deteriorated version of adb in /usr/bin. so, i rm'd it (navigate to /usr/bin and
Code:
sudo rm adb
then navigate over the folder whereeveryouputyoursdk/platform-tools/ and
Code:
sudo cp adb /usr/bin
that should be the new version of adb into /usr/bin. remember, do all that after running the
Code:
android update sdk --no-ui
a few times
peace
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
ah great i thought there was an issue with my adb and you wrote the solution
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
Thanx man you saved me !!!
Sent from my Micromax A57 using xda app-developers app
Thanks
I still had this problem on OSx and Ubuntu in cli.
what i've done on both to address it is, update the SDK to get the newest adb. (i'm suing 1.0.31)
killall adb
then turn off USB debugging on device.
start new adb (doesn't work nothing to connect to)
then turn on USB debugging and suddenly you get the pop up on the android device that says "always allow this computer at xxx"
test adb devices and should show 'device' instead of 'offline'
or try sudo, unplug the device, run adb under sudo on the desktop (sudo adb kill-server; sudo adb start-server), then plug the device back in.
yay!
svs57 said:
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
Click to expand...
Click to collapse
When it does that, go to Developer Options and Revoke Permissions and replug it back in. If that isn't it, then make sure you have the newest version of adb. Have had that happen on a couple of times on newer Samsungs.
Is there any signed adb driver for GT2 Pro for Windows 10? I can see only WinUsb device "ADB Interface" after connection but empty adb devices list. On Windows 7 I can use legacy method but it doesn't work on W10. Thanks.
Go to Windows update and check for updates. It should show compatible adb driver. Manual adb driver install did not work for me. Also make sure to use up to date platform-tools.
I have no problems with windows 11 everything works, before I had win 10 and also no problems
I found a Driver setup file in Android 13 image. I have installed it and restarted the pc. After connecting the phone I can see signed Android Composite ADB Interface (made by Oppo) in the Device Manager but still after executing adb devices there is no device in the list.
OK, found the root cause, if somebody has a similar issue, it works with minimal adb fastboot v1.4.3 from here