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
So first off i have sdk tools installed as well as the motorola phone drivers. The trouble im having is when trying to root my phone i cant seem to flash twrp in adb. With the phone powered on i type "adb devices" and see my phone listed from there i type "adb reboot bootloader" the phone boots to the bootloader then adb can not seem to find my phone when trying to flash twrp. Not sure what happened it was working fine couple weeks ago and now all the sudden it does not want to work. I have tried reinstalling sdk tools and motorola drivers and has not seemed to work.
figured it out delete this post!
I am hoping someone can give me some pointers on what to look at... I have two Macs where I have encountered this problem. When in recovery, I type
Code:
adb devices
into the terminal and I get no devices found. When my Nexus 6p is booted into full OS mode I can see the device serial number reported, and I can even issue
Code:
adb reboot recovery
commands.
Any ideas what needs to happen to get the device to work properly in recovery mode with adb? I've gone through several of the tutorials and haven't found any smoking guns. I do NOT have adb in my path, but I do change to that folder and run ./adb to execute.
Some background
Both Macs run OS X 10.11, El Capitan
The Nexus 6p is on 6.0.1, MMB29Q, stock recovery and ROM, not rooted
ADB/Fastboot were installed via the Google Android SDK
Idk how different it is, but I use OSX 10.10.5. I type: ./adb or ./fastboot before commands. With the phone in the bootloader, do you have an issue when you run:
./fastboot devices
Sent from my Nexus 5X using Tapatalk
I used both on my Macbook Pro last night on 10.11.
When you plug the phone in, is it being recognized by the OS? (Or, if you have Android File Transfer installed, does it pop open immediately?)
Follow this tutorial, it will fix your ills.
http://forum.xda-developers.com/showthread.php?t=1917237
gewecht said:
I am hoping someone can give me some pointers on what to look at... I have two Macs where I have encountered this problem. When in recovery, I type
Code:
adb devices
into the terminal and I get no devices found. When my Nexus 6p is booted into full OS mode I can see the device serial number reported, and I can even issue
Code:
adb reboot recovery
commands.
Any ideas what needs to happen to get the device to work properly in recovery mode with adb? I've gone through several of the tutorials and haven't found any smoking guns. I do NOT have adb in my path, but I do change to that folder and run ./adb to execute.
Some background
Both Macs run OS X 10.11, El Capitan
The Nexus 6p is on 6.0.1, MMB29Q, stock recovery and ROM, not rooted
ADB/Fastboot were installed via the Google Android SDK
Click to expand...
Click to collapse
See here.
And here for issues with El Cap.
Thanks for the pointer... However, the problem persists.
I ran the installer after disabling System Integrity Protection (done in Recovery) and rebooted into OS X
I was able to detect the Nexus when the Android OS was running, but not in recovery (same behavior).
I rebooted to recovery and re-enabled System Integrity Protection. Rebooted again. No change in behavior.
So I'm really not what else I could or should be looking at.
BTW, it looks like the only benefit of disabling SIP is allowing the installation of the files into /usr/local/bin. Once it is installed I'm thinking you can re-enable SIP.
Any other thoughts?
uicnren said:
See here.
And here for issues with El Cap.
Click to expand...
Click to collapse
gewecht said:
Thanks for the pointer... However, the problem persists.
I ran the installer after disabling System Integrity Protection (done in Recovery) and rebooted into OS X
I was able to detect the Nexus when the Android OS was running, but not in recovery (same behavior).
I rebooted to recovery and re-enabled System Integrity Protection. Rebooted again. No change in behavior.
So I'm really not what else I could or should be looking at.
BTW, it looks like the only benefit of disabling SIP is allowing the installation of the files into /usr/local/bin. Once it is installed I'm thinking you can re-enable SIP.
Any other thoughts?
Click to expand...
Click to collapse
I did some further digging... When the Nexus is booted into Android I can see the device (identified as "Nexus 6p") in the USB chain in OS X's "System Information" tool. In the bootloader screen, OS X shows "Android" and fastboot does detect the device.
However, when I've rebooted into recovery I cannot see anything connected - not a device in recovery, not a Nexus 6p. Nothing!
gewecht said:
I did some further digging... When the Nexus is booted into Android I can see the device (identified as "Nexus 6p") in the USB chain in OS X's "System Information" tool. In the bootloader screen, OS X shows "Android" and fastboot does detect the device.
However, when I've rebooted into recovery I cannot see anything connected - not a device in recovery, not a Nexus 6p. Nothing!
Click to expand...
Click to collapse
Mind if I ask, what are you trying to do in recovery?
have you tried unplugging and replugging the usb type c while you were on adb/recovery screen? i had the same problem but unplug and replug worked for me.
bluwavemarshall said:
have you tried unplugging and replugging the usb type c while you were on adb/recovery screen? i had the same problem but unplug and replug worked for me.
Click to expand...
Click to collapse
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
gewecht said:
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
Click to expand...
Click to collapse
ADB works in OS mode, while USB debugging is enabled. Where stock recovery is concerned, only sideload mode will be available, since it doesn't require ADB access for anything else.
EDIT: And yes. It is expected behaviour of the stock recovery.
Glad you figured it out! Cool
I had the same problem, how did you "enable the sideload ZIP with ADB option "?
I'm having the same issue on my Pixel. How did you "enabled the sideload ZIP with ADB option (this is stock recovery)"??
---------- Post added at 11:54 PM ---------- Previous post was at 11:50 PM ----------
How do I "enabled the sideload ZIP with ADB option"?
gewecht said:
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
Click to expand...
Click to collapse
So recently I did nothing with my Nexus 4 and can not boot up. I have tried everything to go back to sock but my PC does not detect the phone anymore. I do not remember having USB debugging on but even if I did not I can't make the change now. I can boot to custom recovery but that does not help. I though It was the USB port so I got a new one and that still did not help.
Boot into fastboot mode to see if it is detected using "fastboot devices" in a command prompt window.
audit13 said:
Boot into fastboot mode to see if it is detected using "fastboot devices" in a command prompt window.
Click to expand...
Click to collapse
Yeah thats my problem. No fastboot. My PC does not see ADB device at all so I cant even Install the drivers. I even changed the USB port to make sure that was not the problem. Before this I could not get my PC to even see the internal SD card. Though It was the OS so I reset it but somehow lost it completely.
You're running adb commands from command prompt? They may not work unless the phone is running in recovery or the phone is booted into the rom.
I hope someone in here can help me with the following problem:
I had an old Android version on my X720, which I wanted to update/install LineAge custom ROM with Android 10 on. Since the old Android was acting weird and USB debugging couldnt be enabled for some reason, I decided to wipe the System/Cache on it using TWRP recovery BECAUSE the device wasnt found on Windows 7 when plugging in via USB. Previously I installed ADB drivers and everything needed, but still Windows couldnt find the device and I was unable to move the Lineage ROM (plus GApps) to the device to be able to install it via TWRP. Anyway, now there is no OS installed and I can only boot into TWRP. I tried to ADB sideload the Lineage ROM via TWRP (via connected USB to my Notebook), but after typing "adb devices" and "adb sideload path...." etc. in Windows Terminal as Admin I always get "no devices found". So, when connecting the device to my Notebook, nothing is shown and the device doesnt appear under "Device Manager" and I think that's the main problem.
Does anyone have any solution or idea? Thanks a lot in advance!
try reading this useful thread:
https://forum.xda-developers.com/le-pro3/how-to/unbrick-leeco-phones-leeco-variants-t3847220
good luck!