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] Fastboot on Stock 4.4.2?

I got an N7 about a month ago on sale and the first thing I did was unlock the bootloader. I decided I was going to use it as a "learning" tablet. (I'm still in learning mode, with aspirations of dipping my toes into development - that's a ways away, though.) I flashed TWRP followed by a couple of roms, and then I decided I was going to test my ability to flash a factory image. So I flashed 4.4 (this was last week before the 4.4.2 images went up). And since I was on the back on the OTA path, I figured, "I have an unlocked bootloader. What's the worst thing that could happen if I took this update?" So I did.
And now I'm confused. If I remember correctly, with 4.2.2 (what it came with out of the box), the bootloader had an option to run in "fastboot mode." In 4.4.2, my options are basically Dead Android screen or (if I power+vol up):
Reboot system now
Apply update from ADB
Wipe data/factory reset
Wipe cache partition
Fastboot stopped recognizing my tablet (adb still works, though not in recovery - I didn't think it was supposed to, so I'm surprised to see it as an option). I know there were issues in the past with the USB drivers on x64 machines, but I've tried on both 32-bit XP and 64-bit Win 7 and both machines will recognize that there is an N7 when booted normally, but say there are issues with the drivers when booted into recovery. I searched and saw people using pdanet as a workaround for installing the USB drivers, but those posts were largely from 2011/2012 timeframe - I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat? Even so, ADB doesn't recognize my tablet in recovery, so even if I wanted to sideload something I can't - did Asus release newer USB drivers that I should be using?
Any help anyone can provide would be greatly appreciated.
Thanks!
miss_sticks

miss_sticks said:
I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat?
Click to expand...
Click to collapse
Are you sure to have updated all the drivers for your N7 after update of your SDK?
Weird thing about N7 is that one sometimes needs to re-installi all the drivers after flashing of another firmware. I've flashed a factory image (4.3) via fastboot on two N7s within the same hour. First N7 had 4.2.2 before, After flashing 4.3 on it, I took another N7 with 4.2.0 and- I had to re-install the drivers.
I never had such a situation with Samsung devices.
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.

tetakpatak said:
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.
Click to expand...
Click to collapse
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)

miss_sticks said:
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)
Click to expand...
Click to collapse
OK, cool. Don't be ashamed, one just has to learn it
From that point on, (as you are in fastboot mode) your each prompt must begin with
Code:
fastboot (.....)
instead of "adb"

NVIDIA shield tv 2015 stuck after flash-all.bat

After updating my shield tv to Oreo I successfully downgraded to 6.3.0 so that I could play PUBG mobile using octopus app. Well now that PUBG mobile detects the octopus app and bans players for using the app I wanted to go back to Oreo. I downloaded the recovery image 7.1.0 and got my device recognized by my pc windows 10. Ran the command adb devices and my device was recognized. I proceeded to run the adb Fastboot devices and my pc recognized my device. I then ran the adb reboot bootloader command. Then I ran the flash-all.bat command. This is where I’m stuck. My device is stuck in bootloader. My pc no longer detects my device when I run the adb devices or Fastboot. I am able to boot to recovery kernel on the shield. I have tried to apply update from adb but I think I’m not getting the correct files. If I select apply update from adb My PC does recognize my device as sideload. No Fastboot devices found. Please help me get my device back to Oreo or just operating.

Fix it
Hi did you manage to fix your shield as I have the same problem

I bricked my shield tv
I bricked my 2015 16gb shield tv. Powers up then turns off immediately

You must install the USB Drivers from NVIDIA, there is a separate driver that your computer needs to communicate while in fastboot/bootloader. So just because ADB works, does not mean Fastboot will work.

I have repaired several SHIELD TV 2015,And I can add shield TV 2015 storage。32G /64G /128G。Just need to replace EMMC.
https://item.taobao.com/item.htm?spm=a1z38n.10677092.0.0.594c1debq5W8P3&id=576292085112
The link above is to buy the chip and repair the machine by oneself.
https://item.taobao.com/item.htm?spm=a1z38n.10677092.0.0.594c1debq5W8P3&id=576414610358
This link needs to be sent to China to replace FLASH chips.

My NVIDIA is dead ?no os no fastboot mod no adb and no recognize by my PC for install the drivers i have just the NVIDIA boot logo who freeze after booting

Not able to get to the boot menu

Device LG G6
Model : G600LR30c
I was thinking of installing a custom os which requires TWRP recovery installed in the device which recuires the device to be bootloader unlocked. But when I use the command "adb reboot bootloader" in minimal adb the device never goes to boot menu, instead it simply restarts and then if I put the command "fastboot oem device-id", it never shows the id and keeps showing "waiting for a device" instead. Please help me resolve this.
P.S: I also tried to access boot menu using key combo. but in vain

If you can put the phone in Fastboot mode during powerup or restart, it's a Windows issue if it don't work. Windows must recognize the device via PnP and install a different set of drivers each time the usb mode changes. If it don't work when the phone is already in Fastboot mode, try different drivers.
I once had two sets installed, that from the device manufacturer and that ripped from the Google SDK(on XDA). This way all usb modes worked, but Windows couldn't perform the Reboot Fastboot/Recovery commands fom ADB like is the case here and the Windows software had, suitable drivers installed, to be able to access the phone if it was already set to Fastboot/Download etc mode.
That was a TI OMAP based LG L9 under Win7. Starting with Windows 8.1, Fastboot was no longer working at all, you could only perform disaster recovery via D/L mode with a stock image and then root the thing with a one-click rooter to be able to install a recovery from Android etc etc, but that was due to the no longer supported TI SoC. But Qualcomm also tends to completely abandon older SoCs.