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

Did I brick my N7?

My rooted N7 has stopped starting on. It will stay stuck on the Google screen with the unlocked icon and remain so until the battery dies. My only option is hard reset and choose recovery. Any other option will bring me back to the Google screen. The recovery will allow me to be in the ClockworkMod. When I went to the "apply update from sdcard" option, there are no more root folders. The N7 has been wiped. This causes it to not connect to the computer, Mac or PC. PC will detect a device, but it will list it as Grouper and not finish the installation of the drivers. I cannot push recovery images into the device because I cannot connect to the device. I tried pushing images using ADB, but my terminal states that there are no devices. I tried using Wug's toolkit, but it cannot connect to the device to reboot it or carry on to any steps.
I am stuck. What can I do to fix this? How can I just get it to just start up?

Download the drivers (link is somewhere around here, don't have it ATM) if it only shows up as grouper.
And/Or go to bootloader/fastboot mode and flash a factory image via fastboot.

Download drivers as above mentioned then use Odin or fastboot method to flash stock (now available on Google devs). I recommend Odin just because that method has worked for me before when my device wouldn't even turn on. It also also possible to use wugs "flash stock+unroot" button in his toolkit after installing the drivers, just boot into boot loader from powered off state and press flash stock and unroot with the soft brick option selected. This method is my usual unbrick method.
Sent from my Nexus 7 using xda app-developers app

[Q] Nexus 4 factory rom deleted

Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:

alhawi6 said:
Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:
Click to expand...
Click to collapse
In cwm there should be an option to mount the device as usb storage. Try that. It should let you plug the phone into the pc and simply copy the zip onto the phones internal sd.
If thats not working try this to set up the drivers. Then plug the phone in and boot into the bootloader/fastboot mode. The open command prompt and cd to the android-sdk/platform-tools directory. Then run the following command:
Code:
adb push /path/to/rom/on/pc/ /mnt/sdcard/

still not working
Still not connected to windows, I cannot do any thing with my device

Download any ROM and do the following:
1. Connect phone to PC when in fastboot
2. Install drivers (if required)
3. Flash latest version of CWM using fastboot flash recovery name_of_recovery.img
4. Reboot phone into fastboot using fastboot reboot-bootloader
5. Boot into CWM
6. Install drivers (if required)
7. Select 'Install via sideload'
8. Flash ROM using adb sideload name_of_rom.zip
9. Follow instructions in CWM
If that still doesn't work, go back to stock using this guide (and read ALL of it):
http://forum.xda-developers.com/showthread.php?t=2010312

EddyOS said:
Download any ROM and do the following:
1. Connect phone to PC when in fastboot
2. Install drivers (if required)
3. Flash latest version of CWM using fastboot flash recovery name_of_recovery.img
4. Reboot phone into fastboot using fastboot reboot-bootloader
5. Boot into CWM
6. Install drivers (if required)
7. Select 'Install via sideload'
8. Flash ROM using adb sideload name_of_rom.zip
9. Follow instructions in CWM
If that still doesn't work, go back to stock using this guide (and read ALL of it):
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.

don't worry! the biggest problem would be that you had no drivers installed!
nexus are super easy to recover and you can play with them safely (except if you flash wrongs kernels from other devices haha)
do what my mate gets up in the post! and it will fixed it.

alhawi6 said:
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.
Click to expand...
Click to collapse
It's not that it's not showing, it might already be installed correctly. When you have the Nexus 4 connect in fastboot it will show in Device Manager as 'Android Bootloader Interface' under the heading of 'Android Phone (see attached)

alhawi6 said:
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.
Click to expand...
Click to collapse
Try with a different USB cable also could be your USB port on your computer
Sent from my Nexus 4

spaceman860 said:
Try with a different USB cable also could be your USB port on your computer
Sent from my Nexus 4
Click to expand...
Click to collapse
It seems that it will never works. I tried all the recommendations given but still device not detected by PC.

same problem for me.. help me
alhawi6 said:
Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:
Click to expand...
Click to collapse
i've the same problem in my nexus 4.. Could u recover from that?

Nexus 7 Stuck in Boot Loop After Font change

So to make a long story short, I've been stuck on android 4.2.2 for a while now because I changed the Roboto fonts (Roboto Bold, Roboto Italic, and Roboto) After discovering this I went and re-rooted my tablet to put the fonts back on so I could OTA update. I couldn't find the fonts on any font applications that matched the SHA1 checksum, so I plugged my device into the computer to put the files on manually I downloaded earlier. This is where some problems arise. My computer has having some problems with the drivers for some reason, so the only way to move the files on was if I turned USB debugging off. So thats off, and my computer won't register that the device is plugged in. Well now we get to the part of the story where I was using ROM toolbox lite and tried installing all three of the new fonts all at once. Bad idea, I now know. So my device is stuck in a bootloop, and when I try to go into recovery mode it gives me the error: No command set. I have no idea what to do guys. Any help is very much appreciated. It is kind of upsetting how a change in fonts can brick your device.

1. Download and install Nexus Root Toolkit v1.8.0: Nexus Root Toolkit v1.8.0 | WugFresh
2.. Connect to PC and Boot in Fastboot Mode: VOL DOWN + POWER ON
3. In the toolkit, under "Back to stock" tick "Soft-Bricked/Bootloop"
4. Click "Flash Stock + Unroot"
5. When done you will (should) have a working Nexus again.

jase33 said:
1. Download and install Nexus Root Toolkit v1.8.0: Nexus Root Toolkit v1.8.0 | WugFresh[/URL]
2.. Connect to PC and Boot in Fastboot Mode: VOL DOWN + POWER ON
3. In the toolkit, under "Back to stock" tick "Soft-Bricked/Bootloop"
4. Click "Flash Stock + Unroot"
5. When done you will (should) have a working Nexus again.
Click to expand...
Click to collapse
Hello, Thank you for the helpful tip on how to fix this. I tried what you said but a problem appeared making the device fail to apply the factory image. What I am assuming is it was because the root that I used did not make me unlock the bootloader. so i'm doing that now. It should let me flash a factory image after that, right?
UPDATE: I tried unlocking the bootloader, but it didn't work. my device is not being recognized via ADB because I think the drivers are not properly installed, or it could be because USB debugging is not on. So I cannot get to the point where I can unlock my device.

JakeTheOneDude said:
Hello, Thank you for the helpful tip on how to fix this. I tried what you said but a problem appeared making the device fail to apply the factory image. What I am assuming is it was because the root that I used did not make me unlock the bootloader. so i'm doing that now. It should let me flash a factory image after that, right?
UPDATE: I tried unlocking the bootloader, but it didn't work. my device is not being recognized via ADB because I think the drivers are not properly installed, or it could be because USB debugging is not on. So I cannot get to the point where I can unlock my device.
Click to expand...
Click to collapse
I have the same kind of problem. Did you manage to unlock it?

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.