The most simple way is this thread. I've done all the editing work for you.
This guide is based on Windows 7 Home Premium. It may be different on your computer. If you are on a Linux build or Mac, you don't need this
Steps: Difficulty: Easy/Medium
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
-Note: If it says not signed, just click next anyway
13. Wait and if it says not signed, click install drivers anyway
14. Wait until it's done, then close all of your programs
15. Press the windows key and R at the same time on your keyboard
16. Type cmd and hit enter (Command prompt will appear)
17. Copy and paste the following code into it:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini
18. Type adb kill-server
19. Type adb devices, and your device should now show up
20. Hit the thanks button below
Thanks to cajl-jbmm from MoDaCo for posting the modification required for the drivers to work
adb devices isn't saying anything.
Good day. I followed your previous steps but when I do "adb devices" I get no response. That is, no message back. When I try it once more this is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Dell>"C:\Program Files\Android\android-sdk\platform-tools\adb.exe">adb
devices
C:\Users\Dell>"C:\Program Files\Android\android-sdk\platform-tools\adb.exe">adb
devices
The process cannot access the file because it is being used by another process.
C:\Users\Dell>
Any help you have is welcomed.
I am having a similar problem.
When I type "adb devices" in command prompt, it returns with:
'adb' is not recognized as an internal or external command, operable program or batch file.
Not sure how to access adb in command prompt.
You need first to install:
Android SDK Tools (can download from archos)
I have sdk installed already
I have sdk installed already. Anymore suggestions? Thanks
baari21 said:
I have sdk installed already. Anymore suggestions? Thanks
Click to expand...
Click to collapse
Is it in your path?
Sent from my ARCHOS 80G9 using XDA Premium HD app
I got it to work. Even though there was no response stating the device was connected I tried "adb reboot" to check if the device was infact working with the adb and it was. So i got it working but perfectly. Only thing is there is no response stating the device is connected but i can live without that. Thanks for the help guys.
adb tool has moved
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK, launch the SDK and AVD Manager (execute the android tool) and install "Android SDK Platform-tools"
Please also update your PATH environment variable to include the platform-tools/ directory, so you can execute adb from any location.
I hope someone is on to help me here, i've done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
BUT... when i click next, it comes up saying....
'the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.
SO WHAT NOW????
MrLarner said:
I hope someone is on to help me here, i've done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
BUT... when i click next, it comes up saying....
'the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.
SO WHAT NOW????
Click to expand...
Click to collapse
You have a 64 bit version of Windows so it's not compatible, sorry
Sent from my HTC Desire HD using XDA
Is there anything i can do about it?
is there something else i can download instead?
or is the only option to use another computer?
MrLarner said:
Is there anything i can do about it?
is there something else i can download instead?
or is the only option to use another computer?
Click to expand...
Click to collapse
adb should perfectly work on 64 bit windows 7. I used it in the past, now I mainly use linux.
Just download the driver from ftp://support.archos.com/ARCHOS it/ADB/adb_winusb_driver.zip
Edit: also look here http://www.archos.com/support/support_tech/updates_adb.html?country=nl&lang=en
divx118
divx118 said:
adb should perfectly work on 64 bit windows 7. I used it in the past, now I mainly use linux.
Just download the driver from ftp://support.archos.com/ARCHOS it/ADB/adb_winusb_driver.zip
Edit: also look here http://www.archos.com/support/support_tech/updates_adb.html?country=nl&lang=en
divx118
Click to expand...
Click to collapse
Is that link for the driver different to the 1 i got from the opening post?
will this 1 work on windows x64?
---------- Post added at 04:20 PM ---------- Previous post was at 04:16 PM ----------
Ignore that last post, i checked it and its exactly the same as the file in the opening post.
I need a file which will work on windows x64
MrLarner said:
Is that link for the driver different to the 1 i got from the opening post?
will this 1 work on windows x64?
Click to expand...
Click to collapse
The link I posted is the original driver provided by archos and works with windows x64. Where the one in the opening post comes from I don't know.
divx118
I'm not to sure why im getting the problem then?
any idea's?
MrLarner said:
I'm not to sure why im getting the problem then?
any idea's?
Click to expand...
Click to collapse
Sorry no idea, I used that driver without problems on windows 7 64 bit.
divx118
Something else i noticed,
when i done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
all went well until i got to 5, it didnt show up unknown devices, it showed up at portable devices and it did not have a yellow ! next to it????
does it mean anything?
Yes, that means you haven't checked USB - Debugging on the device or selected MassStorage in the dropdown.
Sometimes it's not enough that it is selected, so deselect it, leave the menu, get in again and select it.
fzelle said:
Yes, that means you haven't checked USB - Debugging on the device or selected MassStorage in the dropdown.
Click to expand...
Click to collapse
I have, 100% checked usb debugging on.
and where would this mass storage be? i cant find it.
also, for me to enable usb debugging, i have to go to...
{ } Developer options.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
ok think i solved it, i managed to go to storage settings and then had the option once the usb was connected to chose between MTP - Media Device, or, PTP - Camera,
so i changed it from MTP to PTP and now when i go to device manager, its showing up as other devices and then archos has the yellow ! next to it.
does this mean i can continue now?
---------- Post added at 06:37 PM ---------- Previous post was at 06:29 PM ----------
Blimey im hitting problems at every step
i've now got to here...
17. Copy and paste the following code into it:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini
18. Type adb kill-server
19. Type adb devices, and your device should now show up
20. Hit the thanks button below
But when i type adb kill-server it comes up saying....
'adb' is not recognized as an internal or external command, operable program or batch file.
what now???
I've looked into it and everyone says i need to change the path???
i cant find out how to do this, or what to change the path to, someone please help!
Hello Everyone,
----------------------------
Nexus 7 Driver Fail
----------------------------
I was Unable to install drivers on Windows XP (ADB and Fastboot Drivers do not load). Every step has failed and multiple drivers fail to install with Code 18 and 28. I’ve tried just about EVERY Tool Kit available out there and searched fourms, still no positive results. If anyone out there may have an answer please feel free to drop it in here, I greatly appreciate all your help. Thank you.
Here is a list of what I have done thus far:
- Rebooted the computer after uninstalling devices with USB Deview before
continuing on to the other steps
- Uninstalling and manually deleting driver from the registry
- Unplugging and repluging the device while watching
the device manager (The device shows up as other devices, Example: nexus and MTP)
- I tried disabling auto driver configuration by Simply pressing the "Disable Auto Driver Config" button and then
changing the settings accordingly
- Registry cleaning
- Removing and manually adding to windows driver folder
- Trying on different User accounts from Admin to guest
- Used Android SDK manual driver installation
- Unplugged the device and Launched USBDevice
- Used USBDeview to uninstall any;
- Android ADB Interface device's
- Samsung USB devices
- Google USB drivers
- ANYTHING else you see that resembles your Nexus.
- Looked for devices with Vendor ID's:"18d1"or"04e8"
I then right clicked these devices, and selected the option to” Uninstall Selected Devices"
-Downloaded The official Asus USB driver off of Asus actual support base
And it said the following: an error occurred during the installation of this device The Parameter is incorrect.
Have I missed this action:
Download the drivers from Asus and unpack them to their own directory.
Connect the N7 with USB debugging enabled in "developer options"
Open Device Manager
Locate the N7
(from here my xp knowledge is rusty)
Right click on the N7 and select properties
Find the option to install/update drivers, Take the option to specify the driver directory where you unpacked the download, ensure that include sub directories is ticked and that should install
peterk-1 said:
Have I missed this action:
Download the drivers from Asus and unpack them to their own directory.
Connect the N7 with USB debugging enabled in "developer options"
Open Device Manager
Locate the N7
(from here my xp knowledge is rusty)
Right click on the N7 and select properties
Find the option to install/update drivers, Take the option to specify the driver directory where you unpacked the download, ensure that include sub directories is ticked and that should install
Click to expand...
Click to collapse
I tried the same steps.
I even tried using Android SDK, Universal Naked driver
Still no luck
N7 running 4.2.1 stock
After many hours googling and searching here, I have finally successfully rooted my new Verizon Galaxy S4 (SGH-i545), and it had nothing to do with the root process itself, but it was the basic setup that was giving me fits.
Googling and searching has shown that this is actually a common enough problem with some Samsung devices, and there is a fix for it. Since I had to combine several different processes, I thought I would add a note here on how to get the device connected. I will leave the rooting and other discussions to the others. I am also going to give credit to arpruss, most of the steps here come from his work on the Epic. I have trimmed down to only what is necessary to get ADB working properly.
This assumes that you have already tried the various processes to install or update drivers, and that has not worked. Also assumes mid- to advanced user skills:
1. Install KIES. (Downloading the separate driver package didn't work--the driver package refused to install.)
2. Set device in USB Debug mode (Settings | Applications | Development | USB debugging(x)).
3. Plug device into computer.
4. Run Device Manager
5. Look for SAMSUNG_Android. You shoud see it in the Other devices section.
6. Right-click on "SAMSUNG_Android".
7. Choose "Update driver software" | "Browse my computer for driver software" | "Let me pick from a list".
8. Make sure "Show All Devices" is selected and click on "Next".
9. Click on "Have Disk" and type in "C:\Program Files (x86)\Samsung\USB Drivers\25_escape" (auto complete made it easier to type; if you have 32-bit windows, the " (x86)" should be omitted).
10. You will get a two-pane selection of the drivers. Selecting one of the two "SAMSUNG Electronics Co., Ltd." listings (you may need to look through both) in the left pane gives an option list on the right that includes two "SAMSUNG Android ADB Interface".
11. Choose the first "SAMSUNG Android ADB Interface" and click on "Next". You will get a warning that Windows cannot verify compatibility. Accept this. Windows will install the driver and once it's done you'll click on "Close".
12. Windows installed the driver and ADB started working. (If it didn't start working, I would now have gone back to the Device Manager, right clicked on "SAMSUNG Android ADB Interface", and then redid steps 7-11, but this time with the other "SAMSUNG Android ADB Interface" driver.)
This is enough to get adb working. But it's still probably worth fixing the CDC Serial device.
13. Repeat steps 7-11 in the Device Manager with the "CDC Serial" device now, except that instead of the ADB driver you will look for and install "Samsung Mobile USB CDC Composite Device" in the right pane in steps 10-11.
If all goes well, you will get more spinning stuff in the task bar, and eventually Device Manager doesn't show any devices in "Other devices" with yellow triangles. But if things go for you like they did for me, you'll have "CDC Abstract Control Model (ACM) in "Other devices".
14. Repeat steps 7-9 in the Device Manager with the "CDC Abstract Control Model (ACM)" device now. (You may have some USB Modem options showing up in some places, but I ignored those, and did the same "Have Disk" move as before.)
15. I got a single-pane display showing only "SAMSUNG Mobile USB Modem". (Maybe you'll have two-pane display and you'll have to find it as in steps 10-11.) Select it and click "Next". I didn't get any warnings. Windows will install the driver and once it's done you'll click on "Close".
At this point, Device Manager showed all devices correctly functioning. And "adb shell" worked fine.
16. If you don't want KIES, just uninstall it, but make sure not to uninstall the drivers (the KIES uninstaller will ask).
Since I bought the Lenovo IdeaPad S2110AF from NY, I was searching for how to root the device and I found this thread http://forum.xda-developers.com/showthread.php?t=1896899.
But I was unable to get the ADB interface on Windows 7 x64 laptop and I found the same problem is there for most of the users. Finally last night, I could fix this issue and root my tablet. How I did it:
Download the "S2110-Root.zip" file through the above URL. and extract it to a folder.
1. Enable USB debugging under Settings-> Developer options.
2. Connect tab to computer using the provided data cable.
3. The driver for OTP will be installed in Windows. But the ADB interface may not be installed automatically.
4. Go to Device Manager (Right click My Computer and Properties, the click Device Manager).
5. You can see Other Devices-> Android
6. Right click on that and click Update driver software.
7. Click "browse my computer for driver software"
8. Click "Let me pick from a list of device drivers on my computer" rather than browsing and selecting the driver folder.
9. Click Next and then click "Have Disk" .
10. Then choose the drivers folder and the inf file (in extracted files) - \S2110-Root\Drivers\android_winusb.inf
11. Then select the ADB interface and click OK.
12. Ignore any warning message (like not signed)
That is it. Now you got an ADB interface. You will see as Samsung device on the device manager, never mind it.
Now you got the ADB interface and follow instruction to root through the URL.
Note: I am not sure is this a right place, but I just wanted to post this, it may help someone
I had some problems getting root to work.
I found out to use root with adb the display must be on and unlocked.
I started to work on recovery.img, finally I extracted it and took a look on it. Seems not too hard to get it modified and after do some play with custom roms.
Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"
You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging
Bootloader LOCKED .. and asking for gmail ID ??