Hello all:
I'm having a strange issue here. I have a Nexus 7 that won't boot past the X screen. I've managed to get it into recovery mode following the steps laid out everywhere on the internet, but the next step; using the volume rocker to select factory restore is not working. The screen has the word Start enclosed in an arrow, it has a little up arrow and a little down arrow, and information about bootloader version, fastboot, and its locked locked state. There are no other visible options, and nothing changes when the volume control is pressed or held.
Is there an easy solution here I'm not seeing? The only thing that works is holding the power button down to shut it off.
Have you tried "adb reboot recovery"?
Fixed
bobbytomorow said:
Have you tried "adb reboot recovery"?
Click to expand...
Click to collapse
Thanks for the reply. Adb was not an option, sadly as usb debugging was not enabled when the problems started. I did get it working however, based off that, and to explain for those who'll stumble on this with the same issue:
1. Boot into the fastboot screen (the place where you'd normally choose recovery mode)
2. Plug the Nexus 7 into your computer.
3. Enter device manager and see if you have an unknown android device.
4. Right click it and install the Google usb driver that you can find through the sdk manager part of the android sdk.
5. Try the volume keys again. Here's where it started working for me.
I hadn't realized that your computer treats fastboot mode as a separate device. It needed the same process you'd use to install the adb driver, but to be done from fastboot.
My N7 (grouper) tablet sometimes exhibits an inexplicable delay in the responsiveness of the volume rocker keys immediately after re-starting the tablet into fastboot mode. (That is, the fastboot screen is displayed exactly as you describe, but the volume rocker buttons are non-responsive).
If I wait 5 or 10 seconds, the volume rocker keys (up or down) seem to come alive after that little wait and I can use them as expected to select a recovery boot, followed by pressing the power button.
I don't have any idea what causes this delay to happen - it is odd as sometimes the delay is there, and other times the volume rocker keys are responsive immediately after the fastboot screen appears.
Maybe you have this going on, or the delay on your tablet is a little longer? Just a thought, anyway.
Glad you got it sorted out.
bftb0 said:
My N7 (grouper) tablet sometimes exhibits an inexplicable delay in the responsiveness of the volume rocker keys immediately after re-starting the tablet into fastboot mode. (That is, the fastboot screen is displayed exactly as you describe, but the volume rocker buttons are non-responsive).
If I wait 5 or 10 seconds, the volume rocker keys (up or down) seem to come alive after that little wait and I can use them as expected to select a recovery boot, followed by pressing the power button.
I don't have any idea what causes this delay to happen - it is odd as sometimes the delay is there, and other times the volume rocker keys are responsive immediately after the fastboot screen appears.
Maybe you have this going on, or the delay on your tablet is a little longer? Just a thought, anyway.
Glad you got it sorted out.
Click to expand...
Click to collapse
Interesting you should mention that @bftb0... when in the bootoader, if my Nexus 7 is USB connected to my laptop, the volume keys can (but not always) be completely non-responsive.
I've just attempted to replicate the problem... but with no success...
It last occurred after fastboot flashing TWRP with the intention of flashing Chainfire, as was recently required to re-root after the 4.4.2 OTA. With Chainfire's .zip already stored on my Nexus 7, and having successfully flashed TWRP... my next move was to use the vol keys to access recovery. The vol keys didn't work... UNTIL I DISCONECTED FROM MY LAPTOP... when they worked again. I was then able to flash Chainfire, and reacquire root without problems.
As I say, I've noticed this problem before... both with bootloader v4.23 and it's predecessor, v4.18. And you just sort of ignore it...
"oh, the volume keys are dead again - damn, forgotten to disconnect from the laptop!".
It just becomes one of those bizarre minor irritants that seem to bedevil all technology... you know how to fix it (pull the USB cable out), but you don't know what the cause is.
I suspect some bug in the bootloader itself... that is so innocuous and harmless and only occurs when the "stars-are-in-the-right-alignment", that digging it out and fixing it would just be more trouble than it's worth. Still a damned nuisance though.
I guess I'll just have to get into the habit of remembering to disconnect from my laptop after I've fastboot flashed something... if I want to access recovery afterwards.
Rgrds,
Ged.
Related
I unlocked the bootloader and flashed a custom recovery. I then rebooted the device. Now it is stuck at the bootloader (white Google logo on black background) and I can't get it to do anything else. I've rebooted it a bunch of times including with the vol + and vol - buttons held down to no avail. I've also let the battery run out and then tried to boot it up again and the same thing happens. adb nor fastboot see the device and it doesn't show up in the logs on my machine (Mint 13) as coming online at any time.
Most of the times I reboot it with the power switch it reboots to the Google logo even without me letting go of the power button. Sometimes I can get it to fully power off but I haven't figured out what combination of vol keys and reboot does that.
Anyone have any ideas what could be wrong? Any help would be much appreciated!
You are not bricked if you can still get into the bootloader.
Download the factory image from here, and flash it with fastboot. If you don't know how to do that, read this thread.
I wish I could get fastboot to see it then I could definitively flash that img.
I can't get into the bootloader and can't get fastboot or adb to see it. It's stuck at the Google logo now and when i hold the power key it reboots back to the Google logo with the unlock logo at the bottom.
Thanks for the help
You've tried holding volume down+power for 10+ seconds? That should power off the device, then hold both vol up+down down and power up
Ya I've tried to hold vol + and power for 10+ seconds and it reboots back to the Google logo even if I don't off the power key. Same happens with all the other combinations of keys being held with the power button. I can't get it to turn off now unless I let the battery die
Press and hold power till screen goes black. Then quickly press power+volume down and HOLD.
Sent from my Nexus 7
Tried that and still stuck at the Google logo. I have to go to work for a couple hours and then will hack on it when I'm back. Hope I don't have to deal with Googles rma process seeing how disorganized the rest of that company is
Sent from my HTC one s
No luck with any button combos but the vol + and power actually turned it off. All out of ideas over here. I'm thinking it really is bricked
I'm in the same spot. I can get it into recovery occasionally but once there it locks up after trying to flash or clear the cache.
I'm wondering if a contributing issue is CMR v6.0.0.6? I updated it from 6.0.0.4 that was running fine. But no fastboot or adb so that is doubtful.
This is frustrating and not a great start with this N7.
thank you
giveen said:
Press and hold power till screen goes black. Then quickly press power+volume down and HOLD.
Sent from my Nexus 7
Click to expand...
Click to collapse
this worked. you have to be fast. as soon as screen goes black release power button then quickly, very quickly repress along with vol up and down.
You will still be able to get into the bootloader! Force kill the tablet by holding the power button for ages. Then hold volume up and volume down and the power button together, which will boot to fastboot.
It looks like a CWM bug as I feared. Anyone in the same boat try here - http://forum.xda-developers.com/showthread.php?t=1782932
Nothing has worked and I've literally tried everything that those three buttons can do. Thanks again for all the help guys. Had a great time trying to resurrect it but guess it's time for it to go back home
Just as I suspected. Google puts out buggy junk once again.
I just wanted to report a similarly event. I have a rooted, unlocked Nexus 7, with TWRP recovery. I have previously rebooted without issue. Tonight I booted into bootloader mode to check something and the hit power button to choose start. I got stuck on the boot logo. After finding this thread, I started with the simplest combination and held power button until screen went dark, then added volume down and once again in bootloader. This time choosing start led to a regular system boot. It's as if the device froze and needed a hard reboot.
Sent from my SCH-I535 using Tapatalk 2
I was attempting to boot into recovery and kept getting the 'Google' logo (I am unlocked/rooted with twrp recovery). I wasn't aware that one had to be plugged in via usb in order to *not* hang....
Any way around this?
Once I plugged it in and attempted to boot into recovery it worked fine.
I had a similar issue after using the Nexus Root Toolkit to flash to nakasi 4.2 with CWM recovery - just got stuck on the nexus boot screen, flashing in a loop for over 15 minutes.
I ended up powering down the device, holding power for about 5-10 seconds - then QUICKLY holding both the power and volume up+down keys, it then went into the fastboot screen.
After it was there, plugged it into my PC.
Now, this should work for you - assuming you have all the fastboot/usb driver stuff installed.
I extracted the contents of nakasi-jop40c-factory-6aabb391.tgz into the same directory as the fastboot.exe provided by WugFresh with his Nexus Root Toolkit (google search or xda search for this if you dont have it, i dont think i can post links due to my low postcount) - typical filepath: C:\Program Files (x86)\WugFresh Development\data
By the files in there, I mean drilling down inside the tgz to where the image files were inside so that files like bootloader-grouper-4.13.img, image-nakasi-jop40c.zip etc were extracted into the directory and sitting alongside the fastboot.exe - NOT in a subfolder.
Once its all here, running flash-all.bat (this is provided by google in the nakasi-jop40c-factory-6aabb391.tgz) from the command line or by double clicking on it from explorer should kick off the process. After about 2-3 minutes, it was complete, and my Nexus then booted up within about 3 minutes after that.
Also worth noting, device remained unlocked, but I lost root/root binary
Hi
The Volume Down button is jammed (the phone fell and landed on its edge slightly crushing the frame where the volume down is). Curiously the Volume Up button still increased the volume.
After turning the phone off the problem came when turning on the phone as it now only boots into the bootloader as a result of the jammed Volume Down button.
Once in bootloader mode, the volume up/down buttons do not change the reboot options - it appears the stuck Volume Down button is causing this.
The way to fix this is to take the phone apart (as per the Youtube clips) and physically straighten the frame.
This is no easy task, so the question: is there a way around this so that the phone can boot?
It's rooted and fastboot commands work. (I installed TWRP but can only boot to recovery with adb).
Any help will be appreciated. Thank you.
fastboot reboot system?
fury683 said:
fastboot reboot system?
Click to expand...
Click to collapse
No, the device is reading the hardware correctly and booting to bootloader. The only way to fix this is to fix your device.
akellar said:
No, the device is reading the hardware correctly and booting to bootloader. The only way to fix this is to fix your device.
Click to expand...
Click to collapse
He said he could still issue fastboot commands. If the device is OFF and he has to press the POWER button to turn it on, it is reading the VOL DOWN as being pressed as well. If he issues the reboot command in Fastboot, it should boot into system because he won't need to press the POWER button and VOL DOWN (being pressed by the bent frame) at the same time, right?
OP also said he could get to recovery from ADB, but I think he meant Fastboot because ADB is only available when you are booted to Android.
Clarification
"I installed TWRP but can only boot to recovery with adb" is unclear.
I was meaning that one can only boot directly to recovery using adb. In fastboot, one can't get to recovery.
At the moment adb can't be used - only fastboot.
When I issue the fastboot reboot command, it just returns to the bootloader. I was hoping it would bypass the Volume Down state, but sadly no.
Thanks for your input though - I knew it was a longshot.
By the way, the phone wasn't dropped, but came out of my pocket going up some stairs - the bigger size makes it not as stable!
A bit late to reply, but for the sake of the next guy that comes looking, the command you were looking for is:
Code:
fastboot continue
This should tell the bootloader to boot into system.
You are still right about not being able to boot into recovery from bootloader (that's the headache I am currently having)
Any way of disabling the volume key altogether without doing anything physical to the phone?
I tried editing Generic.kl from /system/usr/keylayout/, but that only makes a difference when the phone is booted, not before that. Any way to disable the key before the phone has booted?
Cuz this is my mum's phone and she will have no idea what "fastboot" is
I went to factory reset my completely stock and never rooted Nexus 10. It rebooted in to recovery and started "Erasing". It did this for a few hours. If I power it down, it will power back up and go right back to "Erasing" and never erase. If I hold power and volume up on this Erasing screen, I can see "Erasing /data", but it never shows any other status. I cannot boot in to recovery, it will only go to the Erasing screen - I never get the recovery menu. I can boot in to fastboot, but I cannot get the fastboot cli program to recognize the device. I've tried installing drivers for it multiple ways with no success. I figure if I can get in to fastboot I should be able to fix this device, but I'm stuck. Can anyone help?
No one can help here?
ganiman said:
I went to factory reset my completely stock and never rooted Nexus 10. It rebooted in to recovery and started "Erasing". It did this for a few hours. If I power it down, it will power back up and go right back to "Erasing" and never erase. If I hold power and volume up on this Erasing screen, I can see "Erasing /data", but it never shows any other status. I cannot boot in to recovery, it will only go to the Erasing screen - I never get the recovery menu. I can boot in to fastboot, but I cannot get the fastboot cli program to recognize the device. I've tried installing drivers for it multiple ways with no success. I figure if I can get in to fastboot I should be able to fix this device, but I'm stuck. Can anyone help?
Click to expand...
Click to collapse
I know the Nexus 10 takes longer to do stuff like that than other devices but I have never had it stuck on erasing for hours. If you hold down the power button long enough, will it reboot? If you can time it right, you should be able to hold the Power + Volume up + Volume down and hopefully get into the recovery. I think it has to be all three buttons. Not just Volume up. At least that takes me to the bootloader screen.
jsgraphicart said:
I know the Nexus 10 takes longer to do stuff like that than other devices but I have never had it stuck on erasing for hours. If you hold down the power button long enough, will it reboot? If you can time it right, you should be able to hold the Power + Volume up + Volume down and hopefully get into the recovery. I think it has to be all three buttons. Not just Volume up. At least that takes me to the bootloader screen.
Click to expand...
Click to collapse
If I hold in power, it will reboot. It does not stay powered down. And when it comes up, it goes right in to "Erasing" again. I thought volume down as Fastboot and Up was Recovery (or maybe the other way around). I will try holding in both volume up/down at the same time instead. I might have tried it in my rage when this happened, but can't remember, so will try it for sure when I charge it back up again (it eventually stops because the battery just dies).
ganiman said:
If I hold in power, it will reboot. It does not stay powered down. And when it comes up, it goes right in to "Erasing" again. I thought volume down as Fastboot and Up was Recovery (or maybe the other way around). I will try holding in both volume up/down at the same time instead. I might have tried it in my rage when this happened, but can't remember, so will try it for sure when I charge it back up again (it eventually stops because the battery just dies).
Click to expand...
Click to collapse
I've always held all three buttons with my Nexus devices and it takes me to the bootloader. You could be right about volume down being Fastboot and Up being Recovery but I'm not 100% sure. There should be a way of getting out of that though. If you just did a factory reset, I don't think it would have messed with recovery or anything.
jsgraphicart said:
I've always held all three buttons with my Nexus devices and it takes me to the bootloader. You could be right about volume down being Fastboot and Up being Recovery but I'm not 100% sure. There should be a way of getting out of that though. If you just did a factory reset, I don't think it would have messed with recovery or anything.
Click to expand...
Click to collapse
From https://source.android.com/source/running.html#booting-into-fastboot-mode
Booting into fastboot mode
During a cold boot, the following key combinations can be used to boot into fastboot mode, which is a mode in the bootloader that can be used to flash the devices:
manta Press and hold both Volume Up and Volume Down, then press and hold Power
Hopefully, this thread is still followed....
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Hey guys. I just got LG G6 H870 model. Unlocked bootloader without much problems, but issues came later. While being in bootloader I can't do anything, hardware buttons seem to not work. The only way to get out of bootloader is to use "fastboot reboot" command, but that prevents me from getting into custom recovery after flashing it. Only entering download mode works (holding volume up and plugin in usb cable). Non other key combination work until I boot into system.
Can this issue be somehow resolved?
I had similar problem myself with entering recovery more and the reason behind it was that I didn't press the button combo in proper way. what you actually have to do is while you in fastboot mode you press down and hold power button and volume down button. phone reboots after a moment and you should still be holding these keys and when lg logo appears you let go of power button for brief second and then press it back again and then when a prompt on white screen appears just go yes two times and phone shall boot in recovery mode . I had watch a tutorial movie to figure that out. other easy way is just to have adb enabled and reboot it with adb reboot recovery command via USB cable
non.verbal said:
I had similar problem myself with entering recovery more and the reason behind it was that I didn't press the button combo in proper way. what you actually have to do is while you in fastboot mode you press down and hold power button and volume down button. phone reboots after a moment and you should still be holding these keys and when lg logo appears you let go of power button for brief second and then press it back again and then when a prompt on white screen appears just go yes two times and phone shall boot in recovery mode . I had watch a tutorial movie to figure that out. other easy way is just to have adb enabled and reboot it with adb reboot recovery command via USB cable
Click to expand...
Click to collapse
No, because I had G5 and I know the proper way to do that. Problem is I can hold the power button as long as I live and the phone won't reboot, regardless of pressed combination or power button solo.
and the adb command way ?
Well... Nevermind, turns out vol down button isn't working at all.
still good way around is adb reboot recovery
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.
Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad
Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.
Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight