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
Related
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.
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
pjrj said:
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
Click to expand...
Click to collapse
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
SteadyQuad said:
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
Click to expand...
Click to collapse
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
pjrj said:
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
Click to expand...
Click to collapse
Maybe I should rephrase: the vol-up should already be pressed once the vibrate starts. For a timing-insensitive, fool-proof (no pun intended) way you can enable bootloader (like you did before: you get the Downloading... screen). Then keep vol-up and power pressed together, after 15 seconds the device reboots hard, keep both keys pressed until you see TWRP 'curtain' screen, then release.
Did you try to use the YotaFlasher Windows application to reinstall an official ROM and restore factory defaults? You can get it from here, also download a ROM for your region here.
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
Hi all!
After a complete restore trough the factory image flash, I can't access in the fastboot mode through the vol+ and power key combination.
In any case, I can access in the fastboot mode through the advanced reboot menu in the developer option.
Really strange!
So, if I will incur in a system bootloop or something, I'm a bit f**ked.
Any ideas?
I've seen many people having this issue generally they just haven't been holding the keys long enough. It appears sometimes it takes an extremely long time to boot with the keys.
bladestonez said:
I've seen many people having this issue generally they just haven't been holding the keys long enough. It appears sometimes it takes an extremely long time to boot with the keys.
Click to expand...
Click to collapse
Hi man, thanks for your reply!
I hold the buttons very well, simply my phone "skips" the fastboot and goes straight to normal system boot.
In order I do the following steps:
- shut down the phone
- press vol+ and power on keys
- "your bootloader is unlocked bla bla" message appears
- system boot
WHAT THE HECK?
Hi !
I've got exactly the same prob... Must be using the advanced reboot menu to access fastboot ...
Hateware said:
Hi man, thanks for your reply!
I hold the buttons very well, simply my phone "skips" the fastboot and goes straight to normal system boot.
In order I do the following steps:
- shut down the phone
- press vol+ and power on keys
- "your bootloader is unlocked bla bla" message appears
- system boot
WHAT THE HECK?
Click to expand...
Click to collapse
Try holding volume button then power, release power when phone starts to boot but continue holding volume. I have had phones in the past that we're just picky to get into recovery or fastboot. Might just take a little experimenting with when to release the buttons. All I can think of but I know I have had difficulty on other devices.
lejailleur said:
Hi !
I've got exactly the same prob... Must be using the advanced reboot menu to access fastboot ...
Click to expand...
Click to collapse
Glad I'm not alone in this problem!
Did you perform some operation like hard reset, reflash? Can you define when the problem appeared?
I was on Beta3, and I wanted to unlock my bootloader ... I couldn't do it with the hardkeys ... It was 2 days ago... Now, I'm in 9.0.11 and still the same prob ...
Uh, very strange.
Any ideas on how to resolve this issue? Because if something goes wrong like system boot failure or recovery partition corruption we are in a big trouble, since the only method to get fastboot mode is through the system...
Try holding volume up, volume down and power at the same time. I think that was it.
@trinidude4 : Thank you so much, It was that !!