Database Users

I'm stumped

I just got the NS, coming from the Vibrant. I installed the sdk and drivers. Adb see's my device because I get a serial # when I "adb devices" but when I go to fastboot oem unlock I get "waiting on device".

Do you have the phone in fastboot mode? Turn phone off hold volume up and power on...
Sent from my Nexus S using XDA App

make sure you have the fastboot file in your tools directory and that you are in the tools directory while trying to give the command. that is all I know to try.

I do have a fastboot file in the tools and I do have the phone in fastboot mode. Could the "path" have anything to do with it? For some reason I didnt have a path file under variables so I just created one. I'm assuming since I get a serial # that the drivers and path are correct.

Yeah not sure since it recognized device...
Sent from my Nexus S using XDA App

debug mode?

I'm on windows 7, not sure if that has anything to do with it or not. For the life of me I cant figure out what is going on. I've used adb extensively only g1, never needed it on my vibrant but it has something to do with the drivers I think.

I'm in debug mode

did you update your SDK?
and is your enviorment variable PATH along the lines of
C:\...\...\AndroidSDK\platform-tools
Click to expand...
Click to collapse

If you think you may be having trouble with your path, just cd to the folder where you have fastboot and try it there.
EDIT: I just ran into the same problem when trying to flash the cm7 boot image with ext4 hack. I had booted into bootloader using quick boot. I rebooted, powered off, and powered on with volume up button and everything worked fine. Not sure why this happened but I got the same "waiting" issue you had.

I got it to work. I uninstalled the drivers, put the device in download mode then plugged it in THEN installed the drivers. All is well, root, superuser and 2.3.1. Thanks to everyone who posted to help out.

If your phone is in fastboot mode, you will NOT get your serial number when you do a "adb devices".
So there you go, you're not in fastboot mode.
Turn the phone off.
HOLD volume up and then HOLD power.
You'll get to the bootloader. THAT is fastboot mode.
Now type "fastboot devices" and you'll see your serial number come up, then you can do "fastboot oem unlock".
FYI: adb command ONLY works when your phone is on and booted up OR in recovery.
fastboot command ONLY works in Bootloader.

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] Stuck in endless bootup logo - unable to stock flash

Hi Guys,
I'm stuck in the endless boot logo problem, I installed google drivers, I'm able to get into recovery mode.
the device manager in win7 reports a "android ADB Device" connected.
but when I issues some of the commands in this guide http://forum.xda-developers.com/showthread.php?t=1907796 (like adb devices) it doesn't show anything...
What I've to do?? Am I doing something wrong?
thanks

Can you restore your nandroid/twrp backup? If not, fastboot back to stock and start over.
Sent from my Nexus 7 using XDA Premium HD app

peneoark said:
Can you restore your nandroid/twrp backup? If not, fastboot back to stock and start over.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Already did that with no success... .

If your device is rooted, installed a custom recovery and you're able to get into recovery mode Windows should be able identify your device without asking for RSA fingerprint or something.
Get into recovery mode and try "adb devices" from cmd after connecting your device to pc. What do you see?

Djabolic said:
If are rooted, installed a custom recovery and you're able to get into recovery mode Windows should be able identify your device without asking for RSA fingerprint or something.
Get into recovery mode and try "adb devices" from cmd after connecting your device to pc. What do you see?
Click to expand...
Click to collapse
I'm not rooted,
when rebooting with power and vol- windows recognize the device but "adb devices" gives nothing"
If I select recovery mode the nexus disappears from windows device manager

Check windows device manager to see if you can find any devices without drivers especially something about ADB or Android.

Djabolic said:
Check windows device manager to see if you can find any devices without drivers especially something about ADB or Android.
Click to expand...
Click to collapse
Nothing, when in bootloader (the one with the green robot win belly open) it gets recognized as "bootloader adb interface"; when in recovery (green robot with red exclamation mark) there is nothing in device manager

lmalossi said:
Nothing, when in bootloader (the one with the green robot win belly open) it gets recognized as "bootloader adb interface"; when in recovery (green robot with red exclamation mark) there is nothing in device manager
Click to expand...
Click to collapse
So you can issue commands over fastboot then? You can flash stock firmware images over fastboot to get everything working again.

Djabolic said:
So you can issue commands over fastboot then? You can flash stock firmware images over fastboot to get everything working again.
Click to expand...
Click to collapse
but when if fastboot the command "adb devices" return nothing...

When you're in fastboot mode you don't see your device online over adb, you can freely issue any commands from fastboot if your computer recognizes the bootloader interface.
Follow this guide to flash nexus 7 stock firmware;
http://forum.xda-developers.com/showthread.php?t=1907796

Djabolic said:
When you're in fastboot mode you don't see your device online over adb, you can freely issue any commands from fastboot if your computer recognizes the bootloader interface.
Follow this guide to flash nexus 7 stock firmware;
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I was already following your guide....
Didn't know that if I was already in fastboot mode I could issue fastboot commands even if adb devices didn't show anything...
N00b Error!! Now the thing is clearer to me
Flashed image, and the tablet appears to be working :fingers-crossed:
Thank you very much!!
Luca

[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

Nexus 4 (4.4.2) not mounting after unlocking bootloader

Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!

go to settings/storage open 3dots menu /usb computer connection. if nothing is selected that is why your phone doesn't connect. select mtp an problem solved.
if it's not that i cannot help you except suggesting to reinstall android from scratch using wug toolkit.

wasabitobiko said:
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
Click to expand...
Click to collapse
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?

acejavelin said:
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
Click to expand...
Click to collapse
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..

wasabitobiko said:
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
Click to expand...
Click to collapse
OK, so your fastboot commands are not working, that would likely be a driver issue? If you do
Code:
fastboot devices
and get a result, then keep going, if you don't, use one of the driver options in Wugfresh's toolkit, follow the instructions TO THE LETTER...
If you are just trying to get root and are unlocked, download the latest SuperSU.zip (to your phone preferably) from http://download.chainfire.eu/supersu and openrecovery-twrp-2.7.0.0-mako.img then start phone in Fastboot mode and enter:
Code:
fastboot boot openrecovery-twrp-2.7.0.0-mako.img
this will start TWRP on your device WITHOUT flashing it.
If the SuperSU zip file is on your phone, just use TWRP's Install button and navigate the file and flash it, then reboot and enjoy.
If the SuperSU zip is on your PC, then in TWRP go to Advanced, and start ADB Sideload, give it a few seconds for it to be recognized by your PC, you should be able to enter
Code:
adb devices
and get a result of SIDELOAD back, then enter:
Code:
adb sideload UPDATE-SuperSU-v1.94.zip
Or whatever the current SuperSU zip file is named. Then reboot and enjoy, your rooted!

Remember that adb commands only work in android and custom recovery NOT in fastboot mode.
Sent from my Nexus 4 using XDA Free mobile app

Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload is a special mode that recovery can be placed into, it only allows the "sideload" command to be used. Fastboot is different, it uses the fastboot.exe program and fastboot mode on the android device to allow a limited list of features to be used.
I don't know what you are using for a rooting guide, but basically the end result is to flash SuperSU via recovery, that is all that is really needed.
Sent from my Nexus 4 using Tapatalk

Well, basically if your boot loader is unlocked and you have a custom recovery installed just download the latest superSU zip to your SD card. Reboot into recovery, install SuperSU, reboot. Alas, you're rooted.
Sent from my Nexus 4 using XDA Free mobile app

That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If you unlocked your bootloader your drivers should be working fine. If you rebooted your phone now you'd see it works fine. Next step in rooting is to flash custom recovery. Download a custom recovery, I recommend latest version of TWRP, then flash the recovery image. 'fastboot flash recovery recovery.img' (replace recovery.img with whatever .img file you are flashing.
Once custom recovery is installed you can boot into it to flash supersu. If using TWRP it will prompt you to root when you reboot it.

Thanks.. And please don't take offense to this but re-read the thread. Ever since I used wug's rootkit to unlock the bootloader, neither my pc nor linux machine will recognize the Nexus 4. When I plug it in I get a usb error "device failed to load".. When I look at the device mgr it's listed as unknown device. Btw.. I've restarted both my phone and machine multiple times to no avail.
Sent from my Nexus 4 using XDA Free mobile app

Unknown device? Youve probably installed no or wrong fastboot drivers.
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Google tool 15 second adb xda
Sent from my Nexus 5 using XDA Free mobile app

UPDATE: It looks like the micro usb port on the phone is fried... had been charging fine until today. I'll keep you posted. Thanks for all the help. Does anyone know if this is a relatively easy fix?

Update: Fixed..
Replacing the usb port on the Nexus 4 is super easy. Thanks for the help guys. Everything's working and root has been achieved.