[Q] "adb devices" command not listing my Nexus 7 (2013) ! - Nexus 7 (2013) Q&A

When I try to run the "adb devices" command in the cmd prompt, its is just saying "List of devices attached", but the device Nexus 7 (2013) itself is not been listed. I am able to Kill and start the server. "adb reboot" command not working.
I checked the Device manger; It is listing the device as "Google Nexus ADB Interface" !
Also the "USB Debugging" is checked along with "MTP Device"
What could be the problem?? Any issue with drivers. I have already downloaded the adb and fastboot tools in the drive and running the cmd prompt from that path.
??

Tech2Yantra said:
When I try to run the "adb devices" command in the cmd prompt, its is just saying "List of devices attached", but the device Nexus 7 (2013) itself is not been listed. I am able to Kill and start the server. "adb reboot" command not working.
I checked the Device manger; It is listing the device as "Google Nexus ADB Interface" !
Also the "USB Debugging" is checked along with "MTP Device"
What could be the problem?? Any issue with drivers. I have already downloaded the adb and fastboot tools in the drive and running the cmd prompt from that path.
??
Click to expand...
Click to collapse
It's driver related, install these, then reboot the PC, then with the device plugged in, delete the Google Nexus ADB Interface from within device manager, delete the driver from system if prompted, and leaving the device plugged in, reboot the device, it should redetect the device properly, wait for it to boot up all the way, then unplug the device and plug it back in, and test, you will want to do this for every mode combination, as per my post found here: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
The important part is making sure the device is plugged into your PC and set to the mtp/ptp/debug mode you want detected when you reboot the device after deleting the driver from device manager.

mdamaged said:
It's driver related, install these, then reboot the PC, then with the device plugged in, delete the Google Nexus ADB Interface from within device manager, delete the driver from system if prompted, and leaving the device plugged in, reboot the device, it should redetect the device properly, wait for it to boot up all the way, then unplug the device and plug it back in, and test, you will want to do this for every mode combination, as per my post found here: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
The important part is making sure the device is plugged into your PC and set to the mtp/ptp/debug mode you want detected when you reboot the device after deleting the driver from device manager.
Click to expand...
Click to collapse
Thank you for helping out. I found what was wrong. The drivers were ok. I had ticked the MTP device option earlier. When I ticked the Camera (PTP) instead, the ADB commands started working. I even rooted and installed custom recovery through adb interface.
Thank u once again.

Tech2Yantra said:
Thank you for helping out. I found what was wrong. The drivers were ok. I had ticked the MTP device option earlier. When I ticked the Camera (PTP) instead, the ADB commands started working. I even rooted and installed custom recovery through adb interface.
Thank u once again.
Click to expand...
Click to collapse
You're welcome, fwiw, if you follow my suggestions, you can make it so adb works in ptp and mtp, but if it's not important to you, then it's not dire.

Related

[Q] Phone not being recognized by computer in bootloader?

So I've been trying to root/unlock my CDMA nexus and I'm having a very frustrating problem that's preventing me from doing it with any of the toolkits available OR the manual method. I have the android SDK installed, samsung's USB drivers, and everything else I've been told to get. I can detect my phone when it's connected (and USB debugging is on) using adb commands but ONLY when the phone is booted as normal. If I reboot into the bootloader, my computer no longer detects it, and I can no longer act upon it via adb. This, of course, is preventing me from getting anywhere on the unlocking/root front. Anyone have any ideas? I'm fresh out.
ADB doesn't work in boot loader/fastboot. Adb only works in recovery or when Android is fully running.
You need to use fastboot commands in bootloader/fastboot.
"Fastboot devices" to see if it's detected.
Sent from my Galaxy Nexus
have you installed the hboot drivers?
As above, you have to use fastboot commands when the phone is in bootloader. Try "Fastboot devices" to see if your computer sees the phone.
Fastboot commands don't detect the phone either. Fastboot is installed, as I can get it via command prompt to show available commands and whatnot, it just does not detect a device to work on.
I am also having this exact problem when i try to install the new touch cwm beta that was just released. Its not detecting the device while in the bootloader, and when i try to fastboot flash recovery it just says <waiting for device> and does nothing.
I know this is a little late, but I figured I’d post here to help anyone else out that is having this problem. I was trying to update my Galaxy Nexus from 4.0.2 to 4.0.4 using fastboot when I ran into the problem you’re having. I did this from a Windows 7 machine, and the fix for me was as follows:
1. After booting into the bootloader and having your phone plugged into your computer, open Computer Management.
2. Under Device Manager, in Computer Management, you should see a listing for a device called “Android 1.0” and it’ll have the little yellow triangle with the exclamation point on it.
3. Right click on the Android 1.0 device and select “Update Driver Software…”
4. Click “Browse my computer for driver software”
5. Click “Let me pick from a list of device drivers on my computer”
6. If you installed the Samsung drivers for the phone, scroll down until you see a device listed as “SAMSUNG Android Phone”
7. Select it and click next
8. It should auto populate the driver information. Click next and it will install the device
9. Go back to your CMD prompt and fastboot devices should now list the phone.
Hope this helps!
Quicks man your the best!
...or use Linux #trolling
Sent from my Galaxy Nexus using xda app-developers app

[Q] adb driver not working

I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>
rbmako69 said:
I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>
Click to expand...
Click to collapse
After 'adb reboot bootloader', and device being recognized as "Android 1.0", just manually update the driver: its the same driver that you used for adb. Windows is dumb.
Use search or browse the forums, read the stickies, this has been covered over and over again.
Sent from my i9250
If all else fails get mskips galaxy nexus toolkit v10.x, see xda thread or google skipsoft, and let it sort out drivers and adb, it has easy options and a good help section, should get the job done.
Btw if you are having driver issues you should try the driver download pack from samsung official website's manuals and downloads, its a tad under 30mb, run it then reboot computer then plug in gnex and any missing drivers should auto install, be patient, windows is a retard so it may take a coupla minutes
sent via xda premium from starkissed noozxoide maguro gnex paranoid beta9.5
This worked for me:
rootzwiki -> Google/Nexus Devices -> Galaxy Nexus -> "Galaxy Nexus Root Procedure - (broken) ADB Method Dont USE" -> page 3, second to last post on the page (by litso):
"EDIT: Scratch that, was able to use the PDANet drivers. Install PDA Net, reboot into bootloader, open device manager, manually select the directory "C:\Program Files (x86)\PdaNet for Android\usbwin". Fastboot will then recognize the device and allow you to unlock."
I can't post a link because I am a 'new user' due to low number of posts, but that is the path to your solution. I literally just went through this yesterday.
It's basically what bk201doesntexist said in the above post. I used the pdanet driver, but I'm sure the normal Samsung driver should work.

adb/fastboot ??

Is there any reason that I can't get fastboot commands to work with W7 64bit ?
I've been using them fine for about 2 years but I think it was on a 32bit system.
Just got a new pc which is 64bit.
The drivers install but when I open a command box, in "platform tools", and type "fastboot devices" I don't get the serial number.
It's not the phone that's at fault because I get the serial number when I use a laptop running xp.
Cheers
Check your setup and ADB drivers. Also, when you run an adb command for the first time, you should see it starting the adb daemon. Make sure it is starting correctly, and that it is in the process list.
I will say that it works, because I just got my phone's serial number on my work machine, and last night I updated my N7 and old Galaxy S2, from a Windows 7 64-bit system.
jshamlet said:
Check your setup and ADB drivers. Also, when you run an adb command for the first time, you should see it starting the adb daemon. Make sure it is starting correctly, and that it is in the process list.
I will say that it works, because I just got my phone's serial number on my work machine, and last night I updated my N7 and old Galaxy S2, from a Windows 7 64-bit system.
Click to expand...
Click to collapse
Thanks for your reply but I can't work out what you mean in top paragraph. My fault, NOT yours.
Cheers
Edit... I've just remembered in the past seeing the "daemon starting" prompt, but didn't see it tonight.
10rdan said:
Thanks for your reply but I can't work out what you mean in top paragraph. My fault, NOT yours.
Cheers
Edit... I've just remembered in the past seeing the "daemon starting" prompt, but didn't see it tonight.
Click to expand...
Click to collapse
Depending on how you installed the adb driver and tools, you may need to ensure that the PATH is correct. For example, I installed my adb tools in the (unimaginatively named) c:\adb folder. I put that in the PATH by adding it to the Path line (My Computer -> Properties -> Advanced System Settings -> Advanced (tab) -> Environment Variables -> Path). If this is correct, you can run adb/fastboot from anywhere, which is helpful if you have multiple devices and keep all of their files in separate folders. I am using the "kit" adb file set, not the full developer version, so the only files in the folder are adb.exe, fastboot.exe, and a couple of adb DLLs.
The first time you run adb/fastboot, your system will check to see if the daemon is running. If it isn't, it will start it. If it starts it, you should see a line with the assigned port number. It varies, but is usually ~5000 (Mine was 5037 earlier). After that, it will just return the output of the command. You should be able to launch Task Manager and see adb.exe in the process list if everything is working.
Hi, i have acer e600 i nid help using fastboot ive read that if you try to hard reset using fastboot with command "fastboot -w" or "fastboot erase userdata" it will wipe ur internal storage.. The problem is the system is installed on my internal storage (2.50gb) idk if its the one they called emulated storage but is it safe to wipe my data because i forgot my password and i think it dont have recovery mode partition and usb debugging is unchecked.
Got ONE of the M8s to take fastboot commands.
Windows 7 64bit will only install "Microsoft approved drivers".
Got into "advanced settings" by constantly pressing f8 while pc boots. Selected "install unsigned drivers" or words to that effect.
Connected phone via usb, restarted into bootloader then fastboot. PC installed drivers from phone and got the "fastboot usb" flag.
Could then run fastboot commands and got phones serial number.
The pc will revert back to NOT installing drivers not approved by Microsoft after a reboot.
Problem I have now is that only one of the m8s "can be found", strange.
Edit....constantly pressing f8 on pc reboot takes you to "advanced options". That's where the option to install unsigned drivers is.

RSA fingerprint

Hello all,
I have tried on different laptops, with different cables but my pixel c will not show the rsa dialog to allow access for adb/fastboot. I have tried NRT as well but the device cannot be found. The device is running the lastest software version as of 9/18/16
jasonc7649 said:
Hello all,
I have tried on different laptops, with different cables but my pixel c will not show the rsa dialog to allow access for adb/fastboot. I have tried NRT as well but the device cannot be found. The device is running the lastest software version as of 9/18/16
Click to expand...
Click to collapse
I think more detail is required. Device configured correctly? - Developer options - usb debugging enabled (also revoke debugging authorisations causes a request for RSA confirmation on a previously "connected perfectly" device). Guessing you're using Windows - what "adb" driver (if any) is shown in Device Manager
I've tried to revoke authorizations but nothing happens, and I can access the devices internal storage. However, when I plug the pixel c in, it immediately goes to charging mode and there isn't an mtp button in the storage settings in 7.0 so I can't toggle it on/off. I've also tried enabling/disabling debugging while connected and nothing happens.
I'll assume you have an "adb" driver of some form showing in Device Manager and adb.exe and fastboot.exe in a directory that I'll call "ADB".
Connect the Pixel C and unlock. By default it should have notifications for USB debugging enabled and "USB charging". Adb will work at this stage.
Open a command prompt and change to "ADB" Try the command "adb devices" and it should show your tablet.
Try "adb reboot bootloader" . I expect this command on your PC to fail because it holds no authorisation. But it should trigger:
a) get your tablet to request RSA authorisation
b) start the process of installing the "Android Composite ADB Interface" device driver (under "Android Device" in Device Manager.)
Repeat "adb reboot bootloader" and your tablet should reboot into a "waiting for fastboot command" screen
Try "fastboot devices" should show the tablet and then "fastboot reboot" will restart your tablet.
Pixel c not show up on adb devices list

[HELP] MI a2 lite Fastboot Exits aAutomatically

I have a mi a2 lite and i want to unlock its bootloader, i have alrready enabled oem unlocking on developer options, when i boot my device in fastboot and connect to computer, command window says waiting for device and after 15-20 seconds of connecting my device to my pc, fastboot mode automatically exits and shows charging animation. Please anyone can help?
My device is in andoid pie (stable).
Check if you have installed drivers and run "fastboot devices" to see if device is recognised.
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
hossman said:
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
Click to expand...
Click to collapse
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
I've tried restarting my pc as well as my phone and after 5-6 attempts it is now unlocked.
Thanks guys for supporting and giving response to my post
Love ya'll
CherryFarmer8 said:
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
Click to expand...
Click to collapse
same problem boss, did you already solved this? please help me out
Andrew.kathy said:
same problem boss, did you already solved this? please help me out
Click to expand...
Click to collapse
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
capajga said:
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
Click to expand...
Click to collapse
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
CherryFarmer8 said:
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
Click to expand...
Click to collapse
I also have this problem drivers are installed and fine but when I go to fastboot within like 15 sec it automatically turns off.
I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/

Categories

Resources