I was looking at the [Newbie Guide] adb/fastboot/bootloader/android 101 and I am a bit confused on how to do adb. I am new to Android and Linux but am trying to learn. How do you really do the adb commands? I am running Windows and I do understand you have to mount the device through the USB cable. But I am not understanding how to do the commands after that.
phenixdragon said:
I was looking at the [Newbie Guide] adb/fastboot/bootloader/android 101 and I am a bit confused on how to do adb. I am new to Android and Linux but am trying to learn. How do you really do the adb commands? I am running Windows and I do understand you have to mount the device through the USB cable. But I am not understanding how to do the commands after that.
Click to expand...
Click to collapse
Once you have the usb drivers installed correctly, and have adb/fastboot/etc added to you system PATH, then in a command prompt type "adb devices". If it shows your device ID, then you have adb working correctly. Otherwise, you should check to make sure usb drivers are installed correctly. If it did work, then type "adb" and it should list most of the commands. Most common ones are: "adb remount", "adb shell", "adb lolcat", etc.
Also, for future reference, please post in the correct sub forum
hi guys ive installed driver for wildfire and ive downloaded sdk and and done the path needed but when i type in cmd adb or adb device it does not reconise the device any assistance welcome thanks
Do you have usb debugging on for your wildfire ? Just plug in the usb cable, don't mount your disk drive.
u need to migrate to the path where ADB is present.. it should be
C:\Android\AndroidSdk\tools something like this path
did u install and then uninstall HTC Sync...????
Set the java path as well in case it didn't get set when it was installed.
ive got the adb device connected now all working thanks guys for quick responce
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable
When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2
download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium
i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium
You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.
Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.
bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.
I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?
Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC
Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app
I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app
Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse
rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.
I'm using the Asus Google Nexus ToolKit V3.8.2 (donated version).
With my first N7 I was able to unlock and root.
Now I exchanged it against the N7 3G (HSPA+). I was able to unlock the device and able to install the bootloader 3.34. But root does not work. I think it is because ADB does not recognize the tablet.
What happens:
1.) the start screen of the ToolKit does not show the serial in the adb device list (If I restart the tablet in fastmode it list the serial in fastmode device list)
2.) if I start the Root and the ToolKit wants to reboot in Fastboot Mode it says "Waiting for adb Mode".
3.) If I restart on my own in Fastboot Mode and start the Root procedure then it reboots the device and says "Procedure will continue in 20 seconds Waiting for USB debugging to be enabled". It does not help to re-activate the usb debugging mode and it doesn't help to re-connect the usb cable.
4.) I started cmd and changed to the "Google Nexus 7 ToolKit" folder to call "adb-toolkit devices". But it does not show any device. adb-toolkit kill-server and start-server doesn't help. usb reconnect doesn't help.
P.S. As I'm a new member I'm not able to post inside the official support thread, sorry.
It could be a driver issue on the pc..
try this
download a pc app called usbdview . Do a google search to find it..
Run the program on the pc without the nexus plugged in. Delete all adb/ usb devices that you do not have physically plugged into your computer.
Plug in the nexus 7 refresh the list . Delete what ever comes up for the nexus 7..
Reboot the computer WITH the nexus not connected..
Install the NEXUS DRIVERS.. plug in the nexus and the computer should find the device as if its the first time used.
Try you tool kit again...
Sometimes when adb is started and stopped if there are several versions Windows can be confused and not stop the right driver but start a older version instead VERY Common windows usb issue. This works with any USB Trouble shooting for devices not just Android...
Good LUCK ..
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
The nexus drives are a One driver for all Nexus Devices... This should only be a issue if there are multiple copies of usb adb in the windows registry . The usb drivers need to be removed then re installed or will just create more conflict. Usb Is NOT SO PLUG AND PLAY as it was intended.. Sometimes just plugging a usb device from one usb port to another in some computers can cause windows to install another copy of the driver. This is mostly on systems with a usb hub then a usb 2.o hub on a different port.. and so on.
I Use my notebook with several android devices . I often have issues with
erica_renee said:
It could be a driver issue on the pc..
Click to expand...
Click to collapse
This could it be. But I found a very simple solution:
stackoverflow.com/a/11991653/318765
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus, or undoubtedly any other device. Not exactly obvious, but if you select the second option "Camera (PTP)" the device is available for debugging (the lesson is ignore the camera, and focus on the protocol PTP).
This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise.
Click to expand...
Click to collapse
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
maigre said:
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
Click to expand...
Click to collapse
Crazy as it sounds, try another USB cable. Reboot everything, plug in fresh, and try again. Failing that, use WUGS to reinstall all your USB drivers. Use the stock Google.
The cable was the culprit. I tried another and it worked. Thanks so much!
I'm having a similar problem that's driving me insane.
Nexus 7 wi-fi version
I've loaded every driver on the planet and in recovery mode it simply will not show up. And I'm not talking won't show up using ADB, I get absolutely nothing in device manager. So before anyone tells me to point to the device and manually change the driver, there is no device to try and point a driver to.
In "normal" mode, it shows up perfectly fine in Device Manager as Android ADB Composite Device. ADB will list it in devices with no problem. It will accept the "adv reboot recovery" command perfectly and reboot the tablet into stock recovery. The minute it does that, the device disappears from the Device Manager list and nothing takes it's place. I've tried to have it search for new hardware, I've tried the Google USB drivers kit, I've used Koush's Universal Driver install. I've used 3 different cables on 2 different USB ports.
This is a completely stock N7 running 4.4.4 plugged into a Windows 8.1 64 bit PC.
The last thing I'm wondering is do I have to unlock the bootloader at all? I don't want to because it'll wipe the tablet. If so I guess I'll just wait out the actual OTA rather than try to sideload it.
Any suggestions would be appreciated.
Yaz75 said:
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Any suggestions at all?
Ummm... does the Stock Recovery actually run "adbd" by default? If it doesn't (or it doesn't start adbd until you execute the sideload menu item), then you wouldn't normally see anything on the other side of the cable with a stock Recovery. (I don't have my tablet with me to check)
Here's an extra "any suggestion at all":
Get rid of Windows and use Linux; there are no drivers to screw with in the latter case.
No, seriously. But probably not what you are thinking.
If you can get a "live CD" to boot** on your PC, you can (as root) run the "lsusb" command to see what devices are enumerated on the USB bus, port by port.
In conjuction with the decoder ring at the end of this post, you can determine from inspection of the USB VID/PID identifiers whether or not all the hardware is behaving, and whether or not the tablet is in the mode you think it is supposed to be in.
The reason this is valuable is that it allows you to take drivers completely off the table; if everything is as it should be, then you know that all the hardware and cabling are functioning correctly, the tablet is behaving correctly, your PC hardware is behaving correctly, and that 100% of the problem is Windows driver issues.
If you want to go the extra 1/4 mile, you can put a copy of (Linux) fastboot & adb plus your flashables on a USB key, and run adb or fastboot from the Live CD boot. It won't matter that the live CD doesn't have them preinstalled, they will be on your USB key. It will be easier on you if you can find statically-linked fastboot and adb binaries; if not you will have to copy one or two supporting shared libs (.so files) along with the binaries, and find out what LD_LIBRARY_PATH is all about.
suppose the USB key mounts at /media/usb1; then
$ sudo /bin/bash
# mkdir /tmp/tools
# cp /media/usb1/fastboot /media/usb1/adb /media/usb1/*.so /tmp/tools/
# chmod 755 /tmp/tools/*
# export LD_LIBRARY_PATH='/lib:/usr/lib:/tmp/tools:.'
# cd /tmp/tools
# ./fastboot devices
OR
# ./adb devices
Good luck; as you are using Windows you are going to need it. Hahaha LOL
**depending on whether your BIOS on your win 8.x PC can be toggled between UEFI and Legacy modes or not, this can be either trivial (Legacy boot mode) or complicated (UEFI) requiring a "Trusted Computing" crypto boot shim from MisterSoftie.
Ok this works for me
Use USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
delete all the associated drivers like Google, Samsung, etc for ADB, etc
Restart Computer
Reconnect N7 without MTP and USB debugging
Wait for PC to recognise device and install driver
*If you see something like PC unable to recognise device, go into device and Update Driver and choose "Automatic....."
Disconnect and Reconnect with MTP and USB Debugging
Wait for PC to recognise device and install driver
Restart N7 in bootloader
Wait for PC to recognise device and install driver
Profit
* My PC OS is Win 8.1 Pro 64bit
make sure mtp is switched off, i couldnt get adb or fastboot on my nexus just now . switched off mtp and works fine