Database Users

[Q] Nexus 7 Fastboot Does Not Work

I am sorry if this topic is covered in other threads. I search around and could only find the developer thread and I am not yet allowed to post there.
--------------------------------------------------------------
I have a new Nexus 7 running Jelly Bean 4.2.1. I have activated developer mode and checked the "USB Debugging" box. Other than that, it is in the default configuration.
I want to root it, so I went to http://forum.xda-developers.com/showthread.php?t=1809195 and downloaded the Google Nexus Toolkit.
After identifying my device (Android 4.2.1 (Build JPP40D) for Wi-Fi Only 32GB), the first option was the install drivers. I did that. The 2nd step was to backup the device and I did that with no problems.
The 3rd step was to Unlock the Bootloader (requires Fastboot Mode). When I try to do this, it says that a Fastboot Device was not found.
I am at a loss here as to what to do?
I have some screencaps. I hope this helps.
Ideas?

http://forum.xda-developers.com/showthread.php?t=1741395

simms22 said:
http://forum.xda-developers.com/showthread.php?t=1741395
Click to expand...
Click to collapse
TY, this says I need to be able to use "adb and fastboot". That is the problem. I do NOT know anything about fastboot. I turn off my nexus and then hold the volume up and volume down buttons then turn it on. I get a screen that looks like the image I have attached.
However, I do not know what to do from here. I press the volume up and down keys to change "Start" other options, but Fastboot is not one of the options.
Ideas?

You don't have the right drivers installed. When you see the boot loader screen, you should see 'android fast boot interface' or similar in your device manager.
Sent from my Nexus 7 using xda app-developers app

Unfortunatly no one will help you here, they will just give you links to docs you have already read.
Keep clicking OK a few times, it might find it.
if not, then, press the volume down button until it says reboot bootloader or reboot recovery, sorry i can not remember 100% right now,
press ok a few times more, well keep pressing it and it will find it

adamz2013 said:
Unfortunatly no one will help you here, they will just give you links to docs you have already read.
Click to expand...
Click to collapse
You are replying to a post from December 16th. Doubtful that the OP is still waiting on an answer.
Nice pot shot at people that do try to help, though. Either that or an unmet entitlement issue. No one in here is entitled to an answer for anything. Anything you or others provide in response to an inquiry is a gift, plain and simple. The answers might even be completely wrong or crap; but they are still a gift.
If the OP is still waiting, then they should know that all the detail that they showed (screenshots) are immaterial as they were taken with the device booted into the OS (composite ADB + MTP/PTP showing in Device Manager) instead of the mode that was having communication difficulties - fastboot/bootloader mode.
Immaterial information does not imply that the wrong driver is installed for a different operating mode for which similar information was not provided.
Most of the trouble in these types of post are due to the fact that the posters have no clue how WINDOWS drivers are managed/installed/ etc. That has everything to do with WINDOWS and user skills, and almost nothing to do with the device on the other end of the cable.
Having said that, the principal reason there is confusion is due to the following set of circumstances:
- Casual Windows users are "accustomed to" doing a single install of a driver package when they buy a new device. Even when that device might have many logical endpoints across the USB bus. (Think of a multi-function printer - it might have an SD card slot on it, the printer, a scanner function, etc). When that multifunction behavior exists, usually the OEM provides a "driver installer" package which will actually install multiple drivers, depending on the plurality of USB endpoints in the device.
- Unfortunately, if you carefully inspect any of these three driver bundles:
- Google (SDK) USB Driver
- Asus Nexus 7 USB Driver
- XDA "Universal Naked Driver"
you will find that (as shipped) NONE OF THEM will work for all of the following modes of the Nexus 7:
- Fastboot mode
- ADB Mode, OS (Single or Composite)
- ADB Mode, Custom Recovery
- APX Mode
- PTP Mode*
- MTP Mode*
That's right. As shipped NONE OF THEM will handle all of these cases. The "as shipped" part is a reference to the fact that a trivial edit of the "android_winusb.inf" file for any of them will allow a single driver to handle all fastboot and ADB modes.*
* The MTP/PTP drivers are meant to be handled by MS Windows generic class drivers; in the case of Windows XP you might need to install a Windows Media package to get the MTP driver - I'm not sure that it is part of Vanilla XP SP3
So, anyhow - people get confused because they "install the driver" for one mode (usually ADB), and then are surprised when they boot the device into a different mode (fastboot or ADB running under custom recovery) and surprise, surprise - their PC says "unknown device".
My advice?
Install the Asus Nexus 7 Driver for everything but the Custom Recovery ADB mode, and then install the Universal Naked Driver for that.
Or, prior to installation fix up the android_winusb.inf file that comes with the Asus driver so that it also supports
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
Then a single driver will support everything but APX, MTP, and PTP. The latter two of which are provided by Mister$oftie, and the first of which is currently of unknown value to Nexus 7 rooters.
cheers

That is actually a nice clear description, worthy of a wikipedia entry Seriously though the driver situation with Android gives me the sh17s sometimes.

juicejuice said:
That is actually a nice clear description, worthy of a wikipedia entry Seriously though the driver situation with Android gives me the sh17s sometimes.
Click to expand...
Click to collapse
Neither Linux nor OS/X require any drivers to use either ADB or fastboot.
It's a Windows problem, not an Android problem.

bftb0 said:
Neither Linux nor OS/X require any drivers to use either ADB or fastboot.
It's a Windows problem, not an Android problem.
Click to expand...
Click to collapse
I am a Mac user, and I'm having problems with fastboot. My nexus is unlocked, and I'm trying to flash the lastest 5.1 factory image. I was rooted long ago, but really have no need for root, and lost it during one of the OTA's. I'm not a noob by any means, but none of my terminal commands are working, because fastboot has decided to disappear on me. Any suggestions would be appreciated.
I can't even get TWRP because I don't have root, and I can't get into fastboot.
Edit.....I'm an idiot....I figured it out. On top of it all, my USB cable sucks too so that didn't help any.

Nexus 7 2012 - bricked, only show up with ADX

Hey,
my Nexus 7 turned off a while ago, I tried to load it overnight and also a reset via power / volume. Nothing worked so far. If connected to a Ubuntu computer, it does not show up in the adb devices list, but under "lsusb" as nvidia device (which makes sense, concidering the Tegra-processor). If connected to a Windows pc it tries to install a ADX driver. No idea what that means though, a google search did not bring up a thing, which is why I posted here.
Does anybody has an idea, what that driver is or if there is a possibility to bring the Nexus 7 back to life? Asus will not exchange the device since the one year warranty is over, and the second year is ignored somehow (I'm located in Germany).
Thanks for your help,
blckDTshadow

blckDTshadow said:
Hey,
my Nexus 7 turned off a while ago, I tried to load it overnight and also a reset via power / volume. Nothing worked so far. If connected to a Ubuntu computer, it does not show up in the adb devices list, but under "lsusb" as nvidia device (which makes sense, concidering the Tegra-processor). If connected to a Windows pc it tries to install a ADX driver. No idea what that means though, a google search did not bring up a thing, which is why I posted here.
Does anybody has an idea, what that driver is or if there is a possibility to bring the Nexus 7 back to life? Asus will not exchange the device since the one year warranty is over, and the second year is ignored somehow (I'm located in Germany).
Thanks for your help,
blckDTshadow
Click to expand...
Click to collapse
There is tons of stuff regarding 7s in ADX, much of it complicated. Do a search here on that topic. I do know that there is a first step that rew I ores you to have made a device-specific backup of certain files beforehand. There are a couple of easier fixes that involved a degree of luck.

Try This
blckDTshadow said:
Hey,
my Nexus 7 turned off a while ago, I tried to load it overnight and also a reset via power / volume. Nothing worked so far. If connected to a Ubuntu computer, it does not show up in the adb devices list, but under "lsusb" as nvidia device (which makes sense, concidering the Tegra-processor). If connected to a Windows pc it tries to install a ADX driver. No idea what that means though, a google search did not bring up a thing, which is why I posted here.
Does anybody has an idea, what that driver is or if there is a possibility to bring the Nexus 7 back to life? Asus will not exchange the device since the one year warranty is over, and the second year is ignored somehow (I'm located in Germany).
Thanks for your help,
blckDTshadow
Click to expand...
Click to collapse
First try following the instructions in the site located in the document below
If that doesn't work, try this. I have done it 2 times already and it worked twice
Here's what to do:
- Downloaded the file N7_restore.zip file before, now the link doesn't work so i'll upload it somewhere soon and give the link.
- Then extract the zip file you just downloaded and in that folder there is another zip called image-nakasi-jrn84d
- Extract that zip and Copy all the files in the newly extracted folder to the N7_restore folder
- in the N7_restore folder open a cmd by pressing shift and right clicking together and then clicking open command window here
- Then type/copy without the quotes "fastboot flash bootloader bootloader-grouper-3.34.img"
Do not go to the next step until it says the flashing is successful or it will be a waste of time.
- Next type/copy without the quotes "fastboot flash boot boot.img"
- Next type/copy without the quotes "fastboot flash recovery recovery.img"
- Next type/copy without the quotes "fastboot flash userdata userdata.img"
- Next type/copy without the quotes "fastboot flash system system.img"
If you want to Lock the bootloader
- type/copy without the quotes "fastboot oem lock"
That's it. It worked for me twice and should work for you
P:S: i am still looking for the link of the recovery so i don't have to upload it but if i don't find it i'll try to upload it by tomorrow.
This instruction works with windows 7/8/8.1. Should work with xp/vista and mac.

Hey John,
that might be a bit late, however thanks for your answer. I manged to get a refurbished device by Google. Was actually really surprised about it - did not really expect this
Have a nice weekend,
blckDTshadow

Fire HDX 7 password bypass

My daughter dropped her HDX 7 and the screen shattered. I was able to secure a new one for her but she had some serious sweat equity into a few games she was playing on the old one. I am trying to get the game files of the old one to move to the new one but the touch screen won't work and as such, will not take her password. (due to the drop).
Is there an easy way to bypass this? I am trying to access the kindle drive from my PC for purposes of copying the files (done a million times) but with the device technically locked, the device does not show in file explorer.
Any suggestions welcome.
Thank You!
Chris

Do you have Safestrap installed?

EncryptedCurse said:
Do you have Safestrap installed?
Click to expand...
Click to collapse
No I don't. The device is purely vanilla right as it came from the factory.

Chriss9, you should try to get adb working. That should allow you to pull data.

lekofraggle said:
Chriss9, you should try to get adb working. That should allow you to pull data.
Click to expand...
Click to collapse
Can you tell me where to get it and maybe some instructions? Thanks so much!!
Chris

Look into the rootkit in the dev section. That should install the drivers for you. Then, search for how to use adb. You may need to download the developer kit from Google as the toolkit is a little limited.
You need to pull the data to your computer then push it to the new Kindle.

ADB pull on locked phone? // Simulate input
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk

Grtschnk said:
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Click to expand...
Click to collapse
Thanks for the suggestion. I installed ADB on my PC and when I use "ADB DEVICES" my device does not show on the list though it does show in Windows explorer. Am I out of luck here?
Thank you again for your kind support.
Chris

Assuming you have the latest Fire OS 4.5.1 : (If you have the older version installed there may still be a glimpse of hope (see long answer))
Short answer: Sorry, looks grim.
Your ADB is switched off and there is no way I know of to switch it on.
I wanted to make sure it wasn't just a driver issue with your computer so I checked with my Kindle:
ADB set off: Kindle in Windows, but not detected by ADB-program
ADB set on: Kindle in Windows and detected by ADB-program
Long answer (may be frustrating to read because it states all the possibilities the Kindle lacks): On a nonlocked (in terms of bootloader, not screenlock) device there would have been some possibilities. Install a custom recovery that has ADB built in and pull the files or try to enable ADB from within recovery inside the ROM. If the device could act as a USB host a mouse or keyboard could have been hooked up. The Kindle supports Bluetooth input devices but they have to be set up first (from within the device, not possible without touch). If your device has older Fire OS you could try the mentioned steps, however that's beyond my expertise. So I don't know if it is possible/will work. You'd have to check other threads about flashing the device or hope that someone else posts advice in this thread.
I became a Kindle owner quite recently, so I can't guarantee everything I wrote is correct, but I believe as long as noone magically finds a way to unlock the bootloader the more experienced users will agree to my post.

Did you install the driver as well? I recommended the toolkit because comes with the driver and if you are not used to installing adb drivers on Windows, it can be a bear. But, Grtschnk may be right. I always enable it n all my devices. It is the first thing I do.

Just to be really sure about possible driver issue: You (chris) could try to connect an Android phone via ADB (I'm assuming you have one). Enable ADB on it and see if connects. Unfortunately this will only prove more that your Kindle turned into a piece of plastic :/

Grtschnk, unfortunately, that won't prove anything. ADB requires separate drivers for each device. Again, that is why I recommended the rootkit. It sets it up for you and can even test it.

That's why I compared with my Kindle, computer and S2 (CM11). Newly set up computer, no SDK, just Minimal ADB. Never installed special drivers for Kindle or S2. Newest Visual Studio (2013) runs on the machine, but without additional packages there is no Android support.
However if I was in the situation myself I would have also tried the full SDK.

Need to bypass lockscreen/gain access to adb - Broken screen

So I have a bit of an issue. Somehow last night, after trying to help my parents with our home theater system, with the device laying on a soft surface, the LCD (not the glass) somehow broke. I am really not sure how this happened, the phone itself didn't fall, it was laying on a bed the entire time. When I went to grab the phone and turn it on, I was pretty surprised. You can see what I mean in the attached file.
Now the problem with this is, while I would normally just walk into the Sprint Store, complain and get a new phone. I am not in the US for another 5 months. In the mean time of trying to figure out what to do, I would like to at the very least, grab any files off my phone, or back up my phones' file structure.
I am able to do a minimal amount of tapping on the phone, only on the upper half of the screen, but I can't see anything, nor does the device respond with any touch data from the bottom half.
I obviously can't access the files if the device is locked, which means I have to bypass the lock screen. I found this guide, but unfrotunately, Method 1 didn't work, and I can't get adb to recognize my phone for Method 2.
I also have tried using CWM (the non-touch version) to backup my data, but I let it sit there for 45 minutes and I couldn't tell if it was finished or not. It didn't appear to actually be doing anything.
Could someone help me navigate around this or provide some assistance in allowing me to just get the files off the phone while I search for a new one?
With that being said, does anyone have some recommendations? I was thinking of getting a Motorola X or Nexus 5.
EDIT: Update:
I have access to terminal via Cerberus shell. I was able to use Method 2 to disable the lock screen (or in this case set it to Swipe). It is still pretty difficult to use the phone but I can at least backup whatever data I still do have on the phone to my laptop.
Would anyone be able to give me some advice as to uninstall applications or XDA xposed modules via shell? Or perform a backup or enable ADB debugging?

You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.

Darnell0216 said:
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Click to expand...
Click to collapse
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?

slixzen said:
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
Click to expand...
Click to collapse
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.

Darnell0216 said:
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Click to expand...
Click to collapse
I have a sony xperia P that I am using right now until the replacement phone I got arrives. Any idea how I could use that? I have had minimal success with the phone so far in trying to get that phone to flash custom recoveries, to root the device (not sure why, but my laptop just doesn't want to seem to do it, even using automated tools).
Is it better to just wait for the replacement phone to arrive and grab what I need from that and push it? Could you link me to any guide or steps that you used with yours?
Thanks for such quick responses by the way!
EDIT:
Flashing TWRP and booting into recovery with command prompt open and running adb devices / fastboot devices does not show any devices available.
Is there a specific menu setting or other option I need to use to be able to run adb?

When you use TWRP, the phone will be recognized by the PC but the driver doesn't install correctly off the bat. Go to Device Manager and look for your phone. You may need to click the View -> Show Hidden Devices option. Update the driver manually by selecting the one provided by your manufacturer. Some have a dedicated ADB driver for specific functions (bootloader, etc).
The adb key is stored in data/misc/adb/adb.keys -You can pull this file from any other android connected to that PC (or just copy it if you have a root explorer) and push it to the broken one if necessary. This will bypass any ADB authorization issues while the phone is fully booted and let you see the screen.

[GUIDE] Bypass FRP Tested on 6.0

Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"

You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk

this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging

Bootloader LOCKED .. and asking for gmail ID ??