Develop Bugs

[Q] Phone not being recognized by computer in bootloader?

So I've been trying to root/unlock my CDMA nexus and I'm having a very frustrating problem that's preventing me from doing it with any of the toolkits available OR the manual method. I have the android SDK installed, samsung's USB drivers, and everything else I've been told to get. I can detect my phone when it's connected (and USB debugging is on) using adb commands but ONLY when the phone is booted as normal. If I reboot into the bootloader, my computer no longer detects it, and I can no longer act upon it via adb. This, of course, is preventing me from getting anywhere on the unlocking/root front. Anyone have any ideas? I'm fresh out.

ADB doesn't work in boot loader/fastboot. Adb only works in recovery or when Android is fully running.
You need to use fastboot commands in bootloader/fastboot.
"Fastboot devices" to see if it's detected.
Sent from my Galaxy Nexus

have you installed the hboot drivers?

As above, you have to use fastboot commands when the phone is in bootloader. Try "Fastboot devices" to see if your computer sees the phone.

Fastboot commands don't detect the phone either. Fastboot is installed, as I can get it via command prompt to show available commands and whatnot, it just does not detect a device to work on.

I am also having this exact problem when i try to install the new touch cwm beta that was just released. Its not detecting the device while in the bootloader, and when i try to fastboot flash recovery it just says <waiting for device> and does nothing.

I know this is a little late, but I figured I’d post here to help anyone else out that is having this problem. I was trying to update my Galaxy Nexus from 4.0.2 to 4.0.4 using fastboot when I ran into the problem you’re having. I did this from a Windows 7 machine, and the fix for me was as follows:
1. After booting into the bootloader and having your phone plugged into your computer, open Computer Management.
2. Under Device Manager, in Computer Management, you should see a listing for a device called “Android 1.0” and it’ll have the little yellow triangle with the exclamation point on it.
3. Right click on the Android 1.0 device and select “Update Driver Software…”
4. Click “Browse my computer for driver software”
5. Click “Let me pick from a list of device drivers on my computer”
6. If you installed the Samsung drivers for the phone, scroll down until you see a device listed as “SAMSUNG Android Phone”
7. Select it and click next
8. It should auto populate the driver information. Click next and it will install the device
9. Go back to your CMD prompt and fastboot devices should now list the phone.
Hope this helps!

Quicks man your the best!

...or use Linux #trolling
Sent from my Galaxy Nexus using xda app-developers app

fastboot mode not working

hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers

WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.

Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie

WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/

Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse

[Q] adb driver not working

I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>

rbmako69 said:
I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>
Click to expand...
Click to collapse
After 'adb reboot bootloader', and device being recognized as "Android 1.0", just manually update the driver: its the same driver that you used for adb. Windows is dumb.
Use search or browse the forums, read the stickies, this has been covered over and over again.
Sent from my i9250

If all else fails get mskips galaxy nexus toolkit v10.x, see xda thread or google skipsoft, and let it sort out drivers and adb, it has easy options and a good help section, should get the job done.
Btw if you are having driver issues you should try the driver download pack from samsung official website's manuals and downloads, its a tad under 30mb, run it then reboot computer then plug in gnex and any missing drivers should auto install, be patient, windows is a retard so it may take a coupla minutes
sent via xda premium from starkissed noozxoide maguro gnex paranoid beta9.5

This worked for me:
rootzwiki -> Google/Nexus Devices -> Galaxy Nexus -> "Galaxy Nexus Root Procedure - (broken) ADB Method Dont USE" -> page 3, second to last post on the page (by litso):
"EDIT: Scratch that, was able to use the PDANet drivers. Install PDA Net, reboot into bootloader, open device manager, manually select the directory "C:\Program Files (x86)\PdaNet for Android\usbwin". Fastboot will then recognize the device and allow you to unlock."
I can't post a link because I am a 'new user' due to low number of posts, but that is the path to your solution. I literally just went through this yesterday.
It's basically what bk201doesntexist said in the above post. I used the pdanet driver, but I'm sure the normal Samsung driver should work.

[Q] Can Not get ADB and Fastboot drivers to install

Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm

USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.

beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.

_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959

Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.

Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.

beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.

Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus

W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.

Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.

beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.

_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus

Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.

I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks

HELP!!! Why Can't I unlock my device {Fixed}

I have spent 2 days trying to unlock my new Nexus 7 HD. I'm not a noob, my last 7 phones I have rooted, flashed, unlocked and messed around with, my last 3 tablets I've unlocked and rooted including my 2012 Nexus 7.
Everytime I try to unlock it says fastboot not found. I'm using Nexus Root Toolkit 1.7.1. I can boot into the bootloader using the toolkit, and when it's in bootloader mode, I can also reboot the bootloader using the toolkit. When I click unlock, i get the fastboot device no found. When the Nexus 7 is turned on, my device manager shows "Android Composite ADB device" when the Nexus is in bootloader mode my devices show "Android bootload interface" USB debugging is enabled which don't effect fastboot anyways.
I've tried all 4 of my USB ports, I've followed the driver instructions to a "T", I've uninstalled all the
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- or ANYTHING else you see that resembles your Nexus.

budco2000 said:
I have spent 2 days trying to unlock my new Nexus 7 HD. I'm not a noob, my last 7 phones I have rooted, flashed, unlocked and messed around with, my last 3 tablets I've unlocked and rooted including my 2012 Nexus 7.
Everytime I try to unlock it says fastboot not found. I'm using Nexus Root Toolkit 1.7.1. I can boot into the bootloader using the toolkit, and when it's in bootloader mode, I can also reboot the bootloader using the toolkit. When I click unlock, i get the fastboot device no found. When the Nexus 7 is turned on, my device manager shows "Android Composite ADB device" when the Nexus is in bootloader mode my devices show "Android bootload interface" USB debugging is enabled which don't effect fastboot anyways.
I've tried all 4 of my USB ports, I've followed the driver instructions to a "T", I've uninstalled all the
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- or ANYTHING else you see that resembles your Nexus.
Click to expand...
Click to collapse
Is the fastboot command not found or the device is the one not found? Unlocking the bootloader is very easy using fastboot. I've never run any of the toolkits.
Once the device is connected to your computer and in bootloader mode (vol+down and power), you should get the device id returned if you run "fastboot devices". Then it is a simply matter of just running "fastboot oem unlock", use the vol to scroll to yes, and press the power to select. That is pretty much there is to it.

cowabunga said:
Is the fastboot command not found or the device is the one not found? Unlocking the bootloader is very easy using fastboot. I've never run any of the toolkits.
Once the device is connected to your computer and in bootloader mode (vol+down and power), you should get the device id returned if you run "fastboot devices". Then it is a simply matter of just running "fastboot oem unlock", use the vol to scroll to yes, and press the power to select. That is pretty much there is to it.
Click to expand...
Click to collapse
It says fastboot device not found. I know this is a driver issue, and I've tried different drivers. I unlocked my 2012 nexus 7 in under 3 minutes, but this is not going to smoothy lol

budco2000 said:
It says fastboot device not found. I know this is a driver issue, and I've tried different drivers. I unlocked my 2012 nexus 7 in under 3 minutes, but this is not going to smoothy lol
Click to expand...
Click to collapse
And you are booted to the bootloader, right?
I use a mac. No crazy drivers to deal with. Just plug and go.

cowabunga said:
And you are booted to the bootloader, right?
I use a mac. No crazy drivers to deal with. Just plug and go.
Click to expand...
Click to collapse
I got my bootloader unlocked. Now I can't root it. I downloaded like 3 toolkits, all of them are failing. I've never had so many problems with one device as this one. Wug's toolkit didn't see the device in bootloader, but N-cry toolkit had no problem seeing the device in bootloader mode, which unlocked bootloader, but it wont flash recovery or root. Wug's tool kit will push the files for recovery and root, but then when the Nexus goes into bootloader wug's toolkit fails because it don't see the device in bootloader mode. The quick root tool doesn't do anything at all. The problem here is I'm using windows 8 and I just read that android SDK drivers have to be manually installed, but even that is giving me problems. I have a bad ass laptop, A dell alienware that's never gave me a problem. It came with windows 7, and i put windows 8 on it about 8 months ago, thinking about running the restore CD's and downgrading back to windows 7. ADB commands aren't responding from a command promt. I just want root, and its being a real pain in the ass.

budco2000 said:
I got my bootloader unlocked. Now I can't root it. I downloaded like 3 toolkits, all of them are failing. I've never had so many problems with one device as this one. Wug's toolkit didn't see the device in bootloader, but N-cry toolkit had no problem seeing the device in bootloader mode, which unlocked bootloader, but it wont flash recovery or root. Wug's tool kit will push the files for recovery and root, but then when the Nexus goes into bootloader wug's toolkit fails because it don't see the device in bootloader mode. The quick root tool doesn't do anything at all. The problem here is I'm using windows 8 and I just read that android SDK drivers have to be manually installed, but even that is giving me problems. I have a bad ass laptop, A dell alienware that's never gave me a problem. It came with windows 7, and i put windows 8 on it about 8 months ago, thinking about running the restore CD's and downgrading back to windows 7. ADB commands aren't responding from a command promt. I just want root, and its being a real pain in the ass.
Click to expand...
Click to collapse
Now that I think about it, I don't think I had to even deal with installing a root. I installed twrp2 for recovery and it automatically detected that I did not have root as I was rebooting and it prompted me if I wanted to install root. I remember select yes and after it rebooted, I had root.
Make sure you enable root access for "Apps and ADB" in developer options. You may find you already have root.

cowabunga said:
Now that I think about it, I don't think I had to even deal with installing a root. I installed twrp2 for recovery and it automatically detected that I did not have root as I was rebooting and it prompted me if I wanted to install root. I remember select yes and after it rebooted, I had root.
Make sure you enable root access for "Apps and ADB" in developer options. You may find you already have root.
Click to expand...
Click to collapse
I got it. I ended up using the rootkit for the 2012 nexus 7, i remembered it had an option to push image files, I push the recovery file, then flashed super user. all is good