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

Root Toolkit Wont Recognize N7

After about 10 tries I still cant get this damn tablet to work with the toolkit. I screwed up while updating and lost root, now I cant get the root toolkit to recognize my device after installing the drivers on any pc (tried win two with 8 and two with 7). I have no clue what to do as I was able to unlock and root it initially but now I cant redo it to get my device back and in working order. This is driving me insane!!!!!!!!! I am using the most recent toolkit, and my tablet is on 4.2.2 unlocked but no longer rooted.

Another satisfied toolkit customer. Did you pay for the privilege? If yes, I suppose you should call their support department during normal business hours.
It's a little surprising. I can see that the behavior of ADB might have changed - when the regular OS is booted. (This is a new security feature of 4.2.2 adb - you need the latest SDK version of the "adb" program)
And if you used the OTA, then the custom recovery was replaced by the 4.2.2 stock recovery, so ADB won't even show up there (stock recoveries don't run the "adbd" daemon).
But I would think that you should be able to use fastboot, even if the bootloader was also upgraded.
So, a couple of questions.
A) Can you get the tab into bootloader mode?
B) Does it show version 4.18 on that screen?
C) Does the recovery appear to have been replaced by a stock recovery?
D) Does your PC (pick one and stick with it) show an Unknown Device, or something else when you plug the tab in whilst it is in bootloader/fastboot mode?
E) From the command line, what happens when you run "fastboot devices" either from the command line or from the toolkit when the device is plugged to the PC and in bootloader/fastboot mode?

Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet

lamboboy732 said:
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
Click to expand...
Click to collapse
This
>> E: in the comand line I get the serial of my tablet
is good.
the droid dude is the stock recovery. It actually sounds to me like the OTA succeeded for you - as you are showing both stock recovery and the 4.18 bootloader.
With the tablet in fastboot mode, just flash a custom recovery and you are good to go. You can either use "fastboot flash recovery name-of-recovery-image-file.img", or the equivalent operation in the toolkit.
Then, boot into recovery, and see if
A) the custom recovery appears correctly, and
B) if ADB now shows up either via command line or the toolkit (with the device in custom recovery).
If you got your adb & fastboot tools via installation of the Android SDK, make sure it is updated to the latest version
adb version
should report something like 1.0.31 (iirc)
good luck

[Q] Nexus 4 can get to TWRP, but no image/not able to communicate with PC

OK. I have spent the last 8 hours reading and trying my darnedest to get my phone up and running.
I wiped everything, and formatted data accidentally.
Now the phone wont mount the USB so I can put a ROM on it. I cannot get drivers to make either the skipsoft toolkit or the WugFresh tool kit to work.
I have read on ADB side loading, but cannot figure out how to get the phone to get recognized in order to connect with it. As it sets right now, I am stuck at the bootloader image, or TWRP recovery. No image on the phone, and I cant seem to get the drivers to allow my PC to see the phone. (Ive used WugFresh drivers, naked drivers)
Any help you guys can give me would be awesome.
Thank you
Mark

Hey there,
Our phones are MTP devices and because of that (I think) we can't mount them as a usb drive. But yea you can use adb sideload to get yourself up and running again.
For the drivers try this: http://forum.xda-developers.com/nexus-4/orig-development/toolkit-skipsoft-android-toolkit-nexus-t1995688
On your Phone:
1. Boot into TWRP,
2. Tap advanced,
3. Tap adb sideload,
4. Swipe to start sideload.
Once it says its waiting or something like that, it's ready to sideload from the PC.
On your PC:
Put the rom you wanna flash in the same folder as adb. So if adb is in C:\adb\ then put the file there.
In CMD type in adb sideload filename.zip (filename.zip is the name of your file you want to flash)
So an example would be:
Code:
c:\adb>adb sideload CARBON-JB-NIGHTLY-20131117-1149-mako.zip
It'll take a bit to transfer the file, but once it finishes you should be able to boot into the rom and use it normally again.
Hope it works for you, regards...

You can use Wugfresh to restore to stock and start over.

problem unlocking/rooting

Went through the Guide, however i've run into roadblocks.
i've installed all sdk packages, adb commands work, and fastboot commands return serial numbers. however once i run fastboot flashing unlock, there is a thread run in command promp window, with no change in the device's bootloader screen.
i've done the 6.0.1 update, the bootloader screen reads (some important ?) console NULL; device is LOCKED; download mode DISABLED; CONNECT USB DATA CABLE (while plugged in)
usb debugging is enabled, and the OEM unlock option is checked.
Any advice is appreciated.

Is it necessary to use this method? Won't something like Nexus Root Toolkit work too? Just a thought, I may be way off

gman88667733 said:
Is it necessary to use this method? Won't something like Nexus Root Toolkit work too? Just a thought, I may be way off
Click to expand...
Click to collapse
Haven't seen this mentioned before, but im new to this forum. Will defiantly try later if nothing else works

well it worked with unlocking, when rooting flashing twrp, i sucesfully flashed .zips in twrp, then stuck in bootloop. downlownloading the recovery to fix bootloop, any suggestions on how to succesfully root without BL using nexus root toolkit?

AlPoo said:
Went through the Guide, however i've run into roadblocks.
i've installed all sdk packages, adb commands work, and fastboot commands return serial numbers. however once i run fastboot flashing unlock, there is a thread run in command promp window, with no change in the device's bootloader screen.
i've done the 6.0.1 update, the bootloader screen reads (some important ?) console NULL; device is LOCKED; download mode DISABLED; CONNECT USB DATA CABLE (while plugged in)
usb debugging is enabled, and the OEM unlock option is checked.
Any advice is appreciated.
Click to expand...
Click to collapse
When you issue the "fastboot flashing unlock" command does it return a huge list of compatible commands? If so, your adb/fastboot is out of date.

Have you enabled bootloader unlocking in developer options?

Fastboot doesn't detect my phone, please help

I want to install LineageOS so I closely followed the fastboot and adb instructions on the official site. During my first (failed) attempt, there were some old Google USB and ADB things on my PC, so I deleted everything and started again with a clean slate.
I managed to make ADB work (adb devices detects my device, could authenticate the computer, all seems good there). But if I start the phone in fastboot mode, connect and run fastboot devices, I get nothing back. It doesn't give any sign of the connected device. Windows's "Devices" window lists a device called "Android", but it's under "Unspecified" and has the yellow triangle/exclamation mark on the icon.
1. Am I right to assume that this will stop me from unlocking the bootloader (if I will use the unofficial method) and flashing TWRP and a custom ROM on the device?
2. More importantly: What could be wrong, how can I make fastboot see my phone?
Many thanks for the suggestions!

hi,
first do you have latest ADB and Fastboot
then connect your device and run adb devices. check if it detect the device means from the command prompt run "adb reboot bootloader" (without quotes)
now once after device reboots to bootloader check fastboot devices it will detect now
if not then goto device manager,right click on the device and click on update driver software and choose android fastboot interface
you are done now run fatboot devices,it will detect the device

Solved!
adbdriver com/downloads/