Database Users

ADB recognizing issue

So I am having a lot of problems with trying to root my nexus 7. I'm pretty sure it boils down to a driver issue but I'm not sure. I have tried installing the correct drivers over and over again also uninstalling other hardware manufacturers drivers and I cannot get adb to recognize my device when it is shut off and in the boot loader.
When the tablet is on and I have debugging on, adb shows up and is recognized, however my problem is that whenever I reboot into the boot loader I lose adb recognition. So therefore I can't root or do anything else. Fast boot commands work fine its only the issue with adb.
If anyone has any suggestions as to what I can do I would really appreciate it. I don't know if its just a hardware issue or something I am doing wrong on my end.
This is also not my first time manually unlocking/rooting a device

When you initially connect, the device shows up as a "Nexus 7".
When you reboot into the boot loader, the device name changes, and there is no driver for that device.
As far as I could tell, I would have to do the root process under Linux to avoid this issue.
As for me, I just ignored the issue. By the time you reboot the bootloader, you are already rooted.
The only thing you do after the reboot is rename a file. For now I am missing that step...

Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.

kevlars9 said:
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
Click to expand...
Click to collapse
Like I said - I think you are done...
Install a terminal on the Nexus and see what it says to "su". I use one called "terminal emulator". Works fine.
I think fastboot uses adb.
If you connect your Nexus, and type "adb devices" in a command window what does it say?

I believe it says devices attached or something like that. (Not at my computer) but doesn't give me a serial # like I think it should.

If you do not have USB Debugging checked, "adb devices" will just show the List of devices line.
If I set USB debugging on, "adb devices" also shows the Nexus serial number.
If you don't see that, I would double check the device driver you are using.
Under Device Manager, Android Phone, Android Composite ADB Interface it shows:
Driver: Google Inc.
Date: 5/24/2012
Version: 6.0.0.0
Digital Signer: google inc.

Well if I have USB debugging on and tablet on and do adb devices I get the serial # but once I go into boot loader and do adb devices I don't get the serial #.
For device manager I can choose adb interface or adb original interface. I'll have more info when I get out of work and at my computer. Do you have a link to the drivers you used? Or where to find them. Because I have tried a couple of different drivers posted around to no avail.
BTW thanks for helping me out.

I would not use any posted driver - you don't know where that thing has been.
Download the SDK from Google; the correct driver is in there.
Just point the device manager to it when you install drivers.
There are a lot of good descriptions on installing drivers in the other nexus forums
But - again - I think your device driver is fine. You will not be able to talk to the Nexus from ADB after you boot the bootloader
Bootloader has a different device name which ADB can't use under Windows.
Use Linux if you want to do that.

ok, so pretty much what happens is when my tablet is powered on with usb debugging everything is fine and ADB is recognized. Now my problem seems to be when i reboot into the bootloader it seems as though the drivers dont stick and it asks me to install the drivers again and this is where i have had all of my issues. When i type in adb devices in, it just tells me "list of devices attached" and wont let me do anything else (fastboot works). Like i said i was able to unlock my bootloader but i cant flash recovery or do anything else.
When i go into device manage to select the drivers it gives me the option of choosing between adb interface, adb bootloader interface, adb orignal interface and nexus 7 bootloader interface. I have tried all options and nothing seems to work. I have tried multiple usb cords and ports.
If anyone else has any suggestions it would be much appreciated.

I didn't read through everything but your initial problem is adb doesn't work in the bootloader that's where you use fastboot commands either boot into a custom recovery or just boot up normal and make sure debugging is checked.
Try running fastboot devices and see if it shows up. What you need to do is have bootloader unlocked and dismiss the super user zip floating around here pot that on sd card download cwm recovery image floating around boot into bootloader then
fastboot devices
fastboot flash recovery name_of_file.img
fastboot reboot bootloader
select recovery from the menu
Flash the super user zip
Or download a rom that has root and put that on sd card instead of super user zip and after doing the steps above then selecting super user zip select the rom you downloaded and flash. If you're on Linux run sudo first.
Sent from my Galaxy Nexus using xda premium

Delete

[Q] Device not found in ADB

I am trying to do a full reset in ADB which I have done a few times before. However, when I connect my nexus 4 in fastboot mode to my laptop and open command prompt it says 'device not found'. I have USB debugging enabled and the right drivers but it still won't let me do any adb commands. I am using the fastboot and adb files from the latest SDK but its not working. I have tried reinstalling drivers and rebooting my laptop but it still won't work. If it matters I am running android 4.3, on the latest PA 3.99.

Try clearing your RSA keys from the developer menu, unplug and plug a few times till the phone asks to 'remember this computer' again, try reinstall the ADB driver also

apopberz said:
Try clearing your RSA keys from the developer menu, unplug and plug a few times till the phone asks to 'remember this computer' again, try reinstall the ADB driver also
Click to expand...
Click to collapse
How do you clear RSA keys? I can't see it in developer options

I have attached a screenshot, as you can see, fastboot devices shows but no adb

Anyone??

Not sure if you know, but ADB commands are only allowed when android itself is running, thus the name "Android Debug Bridge".
If your fastboot is working, you should be in bootloader. How are you going to ADB in the bootloader?

Help. Unbootable N4

I accidently formatted my internal storage and system partision through TWRP recovery. Now im stuck with an unbootable Nexus 4 since there is no rom installed. How can i push a zip into my device? I can only access TWRP and Fastboot. and never really used ADB. I used a Toolkit to Root my phone (WugFresh's Toolkit) cant really use that since i cant boot my device to turn on USB Debugging. Any help?
Update: Searched several hours on xda, i cant manage to set up adb. Redownloaded Android SDK. Installed/updated adb (v). Tried multiple drivers (from official google usb drivers to univeral usb driver from Koush). Every time i open cmd and type "adb device" and long list of adb commands and other stuff appear. every time i type adb and any word infront of it, that happens. adb doesnt want to run or something. This is getting fustrating. and when i run adb.exe (from toolkit folder) it closes really quickly. only odd thing i see is under device manager my Nexus 4 is being displayed as Google Galaxy Nexus ADB Interface???

What operating system you're using?

Look here: http://forum.xda-developers.com/showthread.php?t=2010312

only this drivers worked for me
http://forum.xda-developers.com/showthread.php?t=1992345

Threadz said:
I accidently formatted my internal storage and system partision through TWRP recovery. Now im stuck with an unbootable Nexus 4 since there is no rom installed. How can i push a zip into my device? I can only access TWRP and Fastboot. and never really used ADB. I used a Toolkit to Root my phone (WugFresh's Toolkit) cant really use that since i cant boot my device to turn on USB Debugging. Any help?
Update: Searched several hours on xda, i cant manage to set up adb. Redownloaded Android SDK. Installed/updated adb (v). Tried multiple drivers (from official google usb drivers to univeral usb driver from Koush). Every time i open cmd and type "adb device" and long list of adb commands and other stuff appear. every time i type adb and any word infront of it, that happens. adb doesnt want to run or something. This is getting fustrating. and when i run adb.exe (from toolkit folder) it closes really quickly. only odd thing i see is under device manager my Nexus 4 is being displayed as Google Galaxy Nexus ADB Interface???
Click to expand...
Click to collapse
Hi the command is 'adb devices' if it's showing you the commands adb is set up correct. You don't actually need adb for this though, get your phone in fastboot mode and type 'fastboot devices' with your phone connected. If it outputs anything you're ready to flash a factory rom and fix your phone.

[Q] Another way to push root?

I have taken the OTA to KK. I have read how to fastboot the CWM recovery file to get the custom recovery to then flash the SuperSU file. I still can't get my Windows 7 Home Premium 64-bit to recognize my phone to ADB. Here is what I have done so far: (this is not an order what I have done, just steps I did in general)
1. Downloaded an ADB package file I found in another topic/thread on XDA that had everything built in to get adb to work including the 64 bit driver from google. This didn't work.
2. Downloaded the newest Motorola drivers from their website.
3. Downloaded the Universal ADB USB driver files from Koush's website. Still didn't work.
4. Found a thread on XDA that says to download the older Motorola drivers as the new ones from Motorola suck. I did that, still nothing.
I boot my phone into AP Fastboot, and connect the USB cable. It says on the phone that I'm connected. I have made sure USB debugging was checked. In Device Manager, it says MOT ADB interface when I have the phone connected. When I try "adb devices", nothing pops up. I try "adb reboot bootloader", says error: device not found. I made sure to install the ADB installers as an Administrator. Any other way to push the recovery file to the phone?
Thanks for any help!

I also searched and tried to install PDAnet for the adb drivers and that didn't work either
Sent from my XT907 using XDA Free mobile app

Anyone?
Sent from my XT907 using XDA Free mobile app

I had the same problem with the drivers after updating to 4.4.2. This is what I did to solve the problem.
1. Uninstall all Motorola drivers and Device Manager
2. Reboot PC
3. Install Motorola Device Manger (Latest Version)
4. Connect Phone and let Device Manager re-install the drivers

turns out i didn't need to use the command "adb reboot bootloader". i just did the fastboot command and it flashed instantly. Never knew why I didn't try that in the first place.../thread closed

Windows 10 laptop can't detect softbricked Nexus 4, TWRP, no OS

I've checked other threads but other similar threads were able to get the phone detected in Device Manager so...
I went to factory reset my old Nexus 4 after using it whilst my LG G4 was being repaired. Instead of wiping the data, I accidentally wiped the entire phone, OS included. I wasn't paying attention to what i was doing due to working at the same time and as a result the phone now only boots into TWRP and fastboot mode, but nothing else.
I tried to connect it to my windows 10 laptop so I could flash a new ROM but my laptop can't find the nexus 4 at all. Not when in recovery or when in fastboot.
Opening device manager shows that it is not there at all. There is no ACER usb device driver, nothing that resembles the nexus 4 at all. I've attached an image showing what device manager shows when the nexus 4 is connected and in recovery mode.
As you can see, there are no drivers I can uninstall. I have installed the google USB drivers from Android SDK manager. Still doesn't show. ADB doesn't work either.
I have tried multiple USB cables and every USB port. The phone charges when using an AC adaptor and charges when connected to the laptop. I can't try a different computer because I do not have access to one. Frankly I'm at a loss as to what to do.
When my nexus 4 was previously unable to connect I was able to see the device and just had to uninstall/reinstall/update drivers to get it working. This time, I can't seem to do anything. My LG G4 connects fine and without issue.
Anyone able to help?

The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.

I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.

first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/

For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.

i_need_some_help said:
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
Click to expand...
Click to collapse
Thanks, I will give this a try!

elad.g said:
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
Click to expand...
Click to collapse
I tried removing all USB drivers and then using the toolkit and tried installing each driver. None of them allowed my PC to detect the nexus 4. As you can see in the attachment, nothing in device manager remotely resembling my nexus 4. This is after uninstalling and reinstalling and also updateing the LG G4 drivers (it makes no difference).
i_need_some_help said:
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
Click to expand...
Click to collapse
Alas, this did not work.
audit13 said:
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
Click to expand...
Click to collapse
Unfortunately I don't have access to any other PC for this purpose. I can't connect download software or connect USB devices to the PCs at work due to security. I tried an OTG drive but TWRP wouldn't let me mount it, apparently OTG is not enabled by default for the nexus 4.
I've tried all 3 USB ports, several different cables but no luck. I guess that's it for this nexus 4 then?

If the phone is not booted into its ROM, ADB commands won't work. You need to use "fastboot devices" with the phone in bootloader mode.

You android device will reboot in several different boot modes (fastboot, recovery, normal). For each of these boot modes a separate device drive might be installed on your Windows. So check the device drive after each change of boot mode. If needed uninstall and reinstall the correct device driver.