[Q] Stuck in bootloader - Nexus 7 Q&A, Help & Troubleshooting

Okay so my brother got an update for his nexus 7 to 5.1 I believe it was. Anyways for whatever reason the update has failed and the tablet will no longer load up to android. Just gets stuck on the boot up screen. I can access fastboot and recovery mode but recovery is saying no command and my pc doesn't recognize the nexus 7 so using adb doesn't seem to be an option. I've gone through and updated all the drivers needed to see the tablet. I'm wondering how in the world do I factory reset this thing? I'm like at a loss so if you can help much thanks to you.

Related

[Q] Stuck on fastboot, unlocked bootloader, no adb mode

Dear XDA Geniuses,
I have a 16gb Nexus 7 WI-Fi. I was using Nexus 7 toolkit 2.0.0 to try and flash my nexus 7 back to the the stock google rom (option 9 in the toolkit.) It seems as if it wiped out cyanogen mod 10, which i had been using, as well as clockwork recovery. My nexus 7 now boot up with the google logo and the unlocked padlock on the bootom. using the volume rocker i can select the bootloader option and get an android figure with his chest open.
this is the only option i can select. my attempts have been:
1)connect it to computer. Windows 7 and Windows 8 will not recognize it, nor let me access it from the command line.
2. Use nexus 7 toolkit, which DOES recognize it in fastboot mode, to flash a new recovery on there. it says that a command failed, and won't let it write to it.
3) install adb and android sdk tools. my tablet won't show up under devices, and I am not sure if it is still in usb debugging mode. command line will not recognize it as an adb device and will not control tablet.
when i looked at this thread it was dealing with a locked bootloader, while mine is unlocked. it also wanted command line operations from the computer, which does not seem to work for me.
i was attempting to do something like this (laptop mag blog how to hard reset a bricked nexus 7) but without my nexus 7 showing up under devices I am not sure what my options are.
TLDR: Nexus 7 16gb WIFI only boots into boot recovery. Using nexus 7 toolkit to recognize as fastboot. otherwise will not show up on computer. no recovery, no boot image.
Thank you for reading.
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
JerryMc88 said:
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
Click to expand...
Click to collapse
latest progress can be found at imgur slash TAikq
now it is say data transfer failure - too many links. 146.84 seconds.
it was my cable. the cable mounted it in fastboot mode, but would not allow writing. switched out the cable, and we are up and running again. thanks!
Um.... Glad we could help?
Sent from my Nexus 7 using xda app-developers app
Sticky?
Man, I would love to see this sticky posted, or at least a list of errors and fixes stickied. I have been looking for an answer to the same issue for two days. Finding out it was just a lousy cable really really really pissed me off... I'm glad someone figured it out and actually posted their solution, most of these wind up with nothing.
OMG, I've tried to flash my N7 with a new lollipop 5.1 today and got the same issue as described here http://forum.xda-developers.com/showthread.php?t=2724273 then, after 5 or 6 hours of thinking what is going on, I finally found this very old thread and guess what? Changing this sh***ty cable I was using solved the problem.
Use USB ports on the back of your computer, not the front.

[Q] NO OS Installed on Nexus 7

i try rooting my N7 but wiped all data on in so i have no os and im stuck in the google screen and cant do anything. i tried anything that i understood on forums, my pc wont recognize it. nexus root kit doesnt seem to work cause it say adb device not found and fastboot cant find it either. so am stuck with a n7 with no os, have tried reinstalling the stock os image from google but i cant boot the tablet at all it just stays in that google screen.
so if anyone can help me atleast try to reinstall the stock os ......because i am a noob
You have to be in boot loader mode.
Sent from my Nexus 7 using Tapatalk 2
Adb has to find the device before the adb and fastboot commands will work
Sent from my Nexus 7 using xda app-developers app
I did the same thing to my 7 the second day after I bought it. What you described is exactly what I had experienced. This is what I did to restore my 7. I kept holding the power button until it turned off. Afterwards, I charged it for a while cause the battery was low.Then I got the tablet to go into fastboot mode by holding volume down 1st and then the power button. After that, I flashed using the Nexus 7 toolkit. Upon flashing, download 4.1.2 firmware using the toolkit and flash that to your tablet. 4.2.1wouldn't work for me. That brought my 7 back to life in new stock form.
In conclusion, I re-rooted using the toolkit and flashed a custom 4.2.1 rom using TWRP recovery.
If you can get your 7 into fastboot and your computer still will not recognize your 7, reinstall the drivers to your computer. I used PDA drivers. That worked for me.
I hope this works for you.
Is OK guys just use this http://forum.xda-developers.com/showthread.php?t=:D
Sent from my Nexus 7 using xda premium
try this
SiLeNtZoR said:
i try rooting my N7 but wiped all data on in so i have no os and im stuck in the google screen and cant do anything. i tried anything that i understood on forums, my pc wont recognize it. nexus root kit doesnt seem to work cause it say adb device not found and fastboot cant find it either. so am stuck with a n7 with no os, have tried reinstalling the stock os image from google but i cant boot the tablet at all it just stays in that google screen.
so if anyone can help me atleast try to reinstall the stock os ......because i am a noob
Click to expand...
Click to collapse
try this
try the site priyanairmumbai.blogspot.in/2014/01/to-upgrade-nexus-7-and-2013-models-to.html
SiLeNtZoR said:
i try rooting my N7 but wiped all data on in so i have no os and im stuck in the google screen and cant do anything. i tried anything that i understood on forums, my pc wont recognize it. nexus root kit doesnt seem to work cause it say adb device not found and fastboot cant find it either. so am stuck with a n7 with no os, have tried reinstalling the stock os image from google but i cant boot the tablet at all it just stays in that google screen.
so if anyone can help me atleast try to reinstall the stock os ......because i am a noob
Click to expand...
Click to collapse
I DID THE SAME THING
our devices are not "bricked", just screwed really bad...
did you manage to fix it?
.
..

2012 N7 stuck in bootloop/bricked. Unlocked but can't recover/flash images

The title says most of my situation. I've had this since 2012 and some time early last year it just up and stopped booting into android. I have no idea what happened because my girlfriend was using it at the time and she swears she didn't change anything.
Anyways, the bootloader is locked and I have tried to go to recovery and factory reset with no luck. Wiped cache and did nothing as well. I am seeing that windows 7 is sort of recognizing the device. It shows up under device manager as "Android Bootloader Interface"
I've updated the USB drivers and installed ADB as well. When checking the command prompt for ADB Devices, it shows nothing.
I installed Wugs toolkit and it won't even find the nexus either. There has to be SOMETHING that can be done in this situation right?
:EDIT: I was able to unlock it using fastboot but I still can't get it to be found by anything else.
I can get it recognized using the fastboot command prompt, but I can't execute any commands in it. Everything like "fastboot flash boot boot.img" just returns a FAILED message with either invalid argument or no such address or device.
What I am trying to do is just recover it and start using it again. Of course I want to put Android 5.0 on it, but I would be okay with anything as long as it boots, really.
:EDIT: I was actually able to get it to work. I have no idea what specifically had fixed it, but I uninstalled and reinstalled the drivers a few times and ran fastboot and was able to wipe it and install Android 5.0! It was running great!

Stuck in Boot, fastboot locked, no adb sideload

Hello,
I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.
I have attempted a few solutions I have found either on xda or on other pages but the gist of what I’ve attempted so far is thus:
I have tried to reflash android stock after obtaining it from google : https://developers.google.com/android/images (MTC19T) but the oem option was unchecked so “fastboot flashing unlock” returns with an error.
I have tried to apply an OTA update, again I obtained the file from google (MTC19T) , via the recovery > apply update from adb . But it fails. The error from the phone is:
Code:
E: failed to verify whole file signature
E: signature verification failed
And on the pc side I believe that the failure comes from the fact that my pc has never been connected to the phone via ADB, so it’s unrecognized.
- I have also tried to bypass the adb pc signature issue by connecting a usb flashdrive to my phone via a usb-c adapter but the mount /sdcard command doesn’t work.
I’ve tried a few more esoteric solutions, like booting into Emergency Download (EDL) but my phone just boots into the google logo and stays there.
A few informations on my device (according to the fastboot/recovery screen)
Code:
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-WN1
6.0.1/MTC19T/2741993
Current Build Number: MTC19T
So, to summarize: Fastboot is locked and won’t work, ADB is unrecognized and using a usb drive pretending to be an sdcard doesn’t work and I’m working with a stock recovery.
I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Thank you!
Hipstronaute said:
Hello, I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.....I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Click to expand...
Click to collapse
Try again but you have to use an OTA that is newer than MTC19T. You still may be able to sideload when recovery is in ADB Sideload mode. There is no way to unlock your bootloader. Make sure you are using a recent, known working copy of ADB/Fastboot. The problem many people can't overcome is that they never set up ADB before or used it on a few occasions, so now the phone is dead they can't get it set up correctly. When the phone is connected in recovery>>ADB sideload update, what returns when you run "adb devices"? Do you have another phone you can use to confirm your ADB/fastboot setup is installed correctly?
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Sent from my Nexus 6P using Tapatalk
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Hipstronaute said:
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Click to expand...
Click to collapse
You have turn off your phone , press volume up and power key , then a menu will pop up , then plug in your phone with your PC
Sent from my Nexus 6P using Tapatalk
DavidSantos said:
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Click to expand...
Click to collapse
Best way to brick your phone if you don't know what kind of softbrick this tool has been made for... :good:
You have turn off your phone , press volume up and power key
Click to expand...
Click to collapse
Yes, I did that. The soft just makes my nexus reboot to the Google logo.
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Might be a special edition Nexus 6P , oh well. Mine had the same problem and it worked just fine
Sent from my Nexus 6P using Tapatalk
5.1 said:
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Click to expand...
Click to collapse
That's too bad. Sounds like the storage memory going bad and the write process is interrupted when it hits that area. Thing is, I've heard the same OTA write failure occurring several times at 47%. Wonder what that means? Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
@v12xke
Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
Click to expand...
Click to collapse
Gosh do I hope that won't be the last post on this topic.

Nexus 7 (2012) stuck on adb sideload update

Hello Everyone,
So I've got a friend's Nexus 7 (2012) that gets stuck at the google logo when booting up now.. I'm gonna go out on a limb and assume it's probably dead but I'm trying some things to see if I can get it to do anything.
The state of the Nexus:
Will Not Boot (Stuck on google logo)
USB debugging is //NOT// enabled
Bootloader is locked
OEM unlock is not enabled
Can get into bootloader and recovery options
Clearing /cache and /data just get stuck
Running KTU84P
My current line has been to try and update the OS through the recovery options adb sideload update with an OTA update from google, I've been using images from here https://forum.xda-developers.com/showthread.php?t=1745781 for KTU84P but when I run all of them they all just get stuck at
Code:
Verifying current system...
There are no error codes, no error messages and it stays there indefinitely.
I've looked around a bit and can't see anyone else having this issue (usually they at least get an error to help them along) if anyone has seen this issue happen before or has any ideas on anything I can do to try and get the nexus to be more than an expensive paperweight that'd be great. I have a feeling there's something wrong with the storage somewhere along the line but... No real idea.
Edit: Been running for about 6 hours now, still no change
Thanks,
P110

Categories

Resources