Bootloader not responding - Samsung Galaxy Nexus

This morning the phone was running sluggish and restarted several times, then finally got stuck on the boot logo (after the Google logo). I can Power + Volume Down into the bootloader, but the volume keys DO NOT work to access CWM Recovery. The power button seems to respond, but it only reboots the device and gets stuck again when the OS tries to load.
Finally got home today and install all the drivers into my new Windows 8 machine. Unfortunately, fastboot is not recognizing the device while on the bootloader screen. I even disabled Device Driver Authentication on my PC, but no luck. Why doesn't fastboot recognize the phone, and how could the phone be dead to the point the volume keys don't work in the bootloader? This is beyond frustrating...
EDIT: At the top of the bootloader, the device says "ODIN MODE". I am now trying ADB, but still not recognizing the device. Should the device be in a different bootloader state? Quite confused and over my head at the moment!
Verizon GNex running AOKP milestone 2 with CW mod recovery. Thanks in advance...

Well if only I'd have held Power+Volume Up+Down before! Got into recovery doing it that way, as embarrassing as this is.
Phone still getting stuck at the boot screen after reflashing the ROM. I'll try next wiping data and starting fresh, or dump AOKP completely.

ClAlpha said:
Why doesn't fastboot recognize the phone, and how could the phone be dead to the point the volume keys don't work in the bootloader? This is beyond frustrating...
EDIT: At the top of the bootloader, the device says "ODIN MODE"
Click to expand...
Click to collapse
ClAlpha said:
Well if only I'd have held Power+Volume Up+Down before! Got into recovery doing it that way, as embarrassing as this is.
Click to expand...
Click to collapse
Fastboot interface (vol up+vol down+power) is not the same as Odin mode (vol up+power).
ADB won't ever work on those two interfaces, don't even try. It only works on a stock recovery (partially; very limited i.e. sideload), on a custom recovery (full root access), or on Android OS (as long as USB debugging is on).

Related

[Q] I'm stuck in a bootloop

Need some help please !
First of all I'm stuck in bootloop with my nexus 7 2013 (not unlocked). So I pluged my N7 in my computer (windows 7) to flash the Rom. I also have a problem with the driver when I connect my N7 to the computer and I get the message (MTP device failed ). So I've tried to install manually new drivers from Google but it says that my drivers are up to date ??? Now It seems that it's impossible to flash my N7 if my computer doesn't recognize my device.
What is the best thing to do now
thanks in advance
claude
Clodio69 said:
Need some help please !
First of all I'm stuck in bootloop with my nexus 7 2013 (not unlocked). So I pluged my N7 in my computer (windows 7) to flash the Rom. I also have a problem with the driver when I connect my N7 to the computer and I get the message (MTP device failed ). So I've tried to install manually new drivers from Google but it says that my drivers are up to date ??? Now It seems that it's impossible to flash my N7 if my computer doesn't recognize my device.
What is the best thing to do now
thanks in advance
claude
Click to expand...
Click to collapse
Well, it looks like you have a couple of things going on. I can't remember how I got windoze to recognize the n7, but it had something to do with deleting the driver then plugging the n7 back in and letting it install the driver again. I remember I had to play around with the thing for a little while. Trying to update the driver wouldn't work for me either. As, far as the bootloop, you could try this one click tool: http://forum.xda-developers.com/showthread.php?t=2381582 Finally, you could try wugfresh's toolkit if you want to take the lazy route. It actually works pretty well. It might even help with that driver issue. http://forum.xda-developers.com/showthread.php?t=2389107 you don't use it to install a rom, but you do need to install a custom recovery and the toolkit could help with things like that. I personally use the toolkit to return a tablet or phone back to factory condition, lock the bootloader, etc...
You could also try to do a factory reset from the stock recovery. That fixed a boot loop for me after unlocking my bootloader.
Problem solved
I finally contacted Google Canada Monday morning and spoke with with a tech. Wow...very impressed by the service and my problems are now solved. First we went to Recovery mode ( Power and volume down) in that mode you then press again power and volume up and release at the same time. Then,from that menu you can now swipe all data and it solves the Bootloop problem. Finally I reinstalled all my app and back to normal. I pluged my N7 to my computer and now no more driver problem....
Thanks
Claude:laugh:
Clodio69 said:
I finally contacted Google Canada Monday morning and spoke with with a tech. Wow...very impressed by the service and my problems are now solved. First we went to Recovery mode ( Power and volume down) in that mode you then press again power and volume up and release at the same time. Then,from that menu you can now swipe all data and it solves the Bootloop problem. Finally I reinstalled all my app and back to normal. I pluged my N7 to my computer and now no more driver problem....
Click to expand...
Click to collapse
That's what I was referring to in my post, sorry for not giving a more detailed explanation.
Glad to hear you that you had a good experience with Google support and that you solved your problem. :good:
Thanks for giving feedback and have lots of fun with your N7!
Hello!
I'm stuck in a loop boot too. I flashed without wiping... I try to boot in recovery mode but it's impossible. The combination vol up, down and power doesn't work. It tries to boot as usual so starts in a loop again.
Sent from my Nexus 4 using Tapatalk now Free
frozst said:
Hello!
I'm stuck in a loop boot too. I flashed without wiping... I try to boot in recovery mode but it's impossible. The combination vol up, down and power doesn't work. It tries to boot as usual so starts in a loop again.
Sent from my Nexus 4 using Tapatalk now Free
Click to expand...
Click to collapse
Let me get this straight....are you trying to hold volume up & down at the same time? If so, you cannot please both volumes at the same time. Also, to boot into the bootloader (same as fastboot, not recovery) is power + volume down. The easiest way to do this is to hold volume down, then press and hold the power button. If the tab was on, and the screen goes black, let go of the power button, but keep holding the volume down button. It should boot into the bootloader soon enough.
1. Push volume up and power button for 5 seconds then release the power button.
2. Do a complete wipe of the system and reinstall the system.zip again and reboot.
If it doesnt load the recovery do this.:
1. Hold volume down and power button for 5 sec. Release the power button and volume once you enter the download screen.
2. Use odin in your Pc to install the rom you want or stock rom.
(3. If you installed stock rom go back to the steps I wrote at the top and flash a new rom)
Remember that you need to be rooted.
OK so I was trying with the wrong combination.
With both vol up/down + power worked.
I restored and it's up and running again.
Thanks!
Sent from my Nexus 4 using Tapatalk now Free

[Q] Bricked Samsung Galaxy Nexus I9250

i seem to have hard bricked the device and i have been attempting to find a way i can fix it for hours.. i seem to be stuck. Its stuck on the boot animation cyanogenMod logo. I am unable to get into the recovery mode, as well as fast boot mode. i let it sit on that boot logo for hours without anything at all happening. No progress what so ever. Now the biggest thing i am trying to figure out is how i even managed to get this to happen. there was a software update notification that i received, so i figured it may have been the Android L update or something, so without taking into considering what exactly i was agreeing to i accepted, and continued. Let it reboot, and thats how i got to come across this issue. Any suggestions.
So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.
efrant said:
So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.
Click to expand...
Click to collapse
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.
Jewelzxo said:
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.
Click to expand...
Click to collapse
What I find strange is that it boots to the boot animation -- that means the bootloader has loaded up the kernel and Android is attempting to start. The bootloader loads up before anything, so it is obviously working. Don't know why you can't access its menu though with the 3-key press. Maybe one of your volumes keys is not working properly? By holding those three keys down, it should not boot to the boot animation...
Can you get into download mode? Hold only volume down and press and hold power. If so, then you can use Odin and flash a stock ROM as per this thread.
In any case, if you can't get into the bootloader or download mode, then your only option is using OMAPFlash (as per this thread). That will re-flash your bootloader. If you still can't get into the bootloader menu after that, then there is a hardware issue.

Possibly bricked HTC One M8

Ok,
Was installing the viper rom on my M8, and for some reason, now my phone is stuck in a boot loop. Obviously the install went pear shaped. But now I cant even boot the phone into recovery mode.
Boot sequence now is: Google lettering appears on screen, followed by green android with the blue spinning shape in its chest, then the green android with the red triangle and black exclamation mark appears and the whole thing loops again.
When plugged into the PC its not recognized so I cant use adb to boot into recovery or try load another rom/wipe cache etc.
I've tried all combinations of power button & volume up/down to break the boot sequence, no joy.
Any ideas how to resolve, or do I have a very expensive paper-weight?
Cheers,
sombaht
Rest assured, if the screen comes on, the phone isn't bricked.
Red triangle with exclamation point is stock recovery.
What was your exact sequence, in detail? From bootloader unlock, install custom recovery, etc.
Was the phone on Lollipop when you unlocked the bootloader?
To reboot into bootloader (not recovery, there is no button sequence to boot directly into recovery on this device):
1) Hold power and vol up for several seconds to force a reboot
2) The moment the screen goes black to reboot, let go of the buttons, and only hold vol down
3) Don't let go of vol down until you are on the bootloader screen
4) Failure to get into bootloader is virtually always user error. You either started pressing vol down too late, or let go of it too early. Just repeat until you get it right.
But from there, as mentioned it sounds like you are on stock recovery. You will probably need to flash TWRP again via fastboot in order to do much more.
Did you flash a custom recovery before you flashed the rom?? Can you boot in the bootloader mode (turn of Device completely- turn on again and hold volume down all the time.. then you should be in the bootloader)?
And your phone is not really bricked
Edit: damn to slow should not write on the phone
sombaht said:
Ok,
Was installing the viper rom on my M8, and for some reason, now my phone is stuck in a boot loop. Obviously the install went pear shaped. But now I cant even boot the phone into recovery mode.
Boot sequence now is: Google lettering appears on screen, followed by green android with the blue spinning shape in its chest, then the green android with the red triangle and black exclamation mark appears and the whole thing loops again.
When plugged into the PC its not recognized so I cant use adb to boot into recovery or try load another rom/wipe cache etc.
I've tried all combinations of power button & volume up/down to break the boot sequence, no joy.
Any ideas how to resolve, or do I have a very expensive paper-weight?
Cheers,
sombaht
Click to expand...
Click to collapse
My friend, did you flash it using stock recovery or custom recovery? if you did flash it using stock recovery you will meet this kind of problems. I suggest you try power button and down if im not mistaken and go to hboot and fastboot usb and connect to adb, type fastboot devices in cmd if it detects your device then you can flash TWRP , find any kind of custom rom for M8 and flash it. I also assume your bootloader is unlocked and driver is installed in your PC.
Problem solved. Redpoint73's key press combination worked!
Cheers,
sombaht

phone factory reset

Hello All,
my phone was bootloader unlocked, rooted, installed with custom ROM and custom recovery.
Selling it to my friend, I did a phone reset in the phone setting menu.
Seems like I have done the wrong way? should have done in the custom recovery menu (TWRP)?
Now seems like I can not boot up to recovery mode anymore, by pressing power & volume down button, it always boot up straight to normal state.
Questions:
Have I lost the custom recovery?
How do I re-install? go thru ADB mode?
Thanks!
That button combo reboots to bootloader, not recovery (which doesn't have a button combo to boot directly to). Its a subtle difference (recovery vs. bootloader), but important. Its nearly impossible for the phone to not be able to boot into bootloader (if the bootloader was damaged, you wouldn't even have the screen coming on). If that is what you are experiencing (can't get into bootloader), you are probably just doing the button combo incorrectly: Hold vol up and power buttons until the phone reboots. When the screen goes black, but before the white HTC logo screen appears, let go of those buttons, and only hold vol down. Don't let go of vol down until you see the bootloader screen. If the phone boots normally, you likely just got the timing wrong, either started pressing vol down too late, or let go of it too early. Just repeat until you get into bootloader.
Alternately, within OS (and debugging enabled) you can do:
adb reboot-bootloader
or
adb reboot recovery
Now, if you get into bootloader, select recovery, and TWRP still doesn't boot. Then yes I'd recommend fastboot erase cache, and re-install TWRP by fastboot.
Pardon me,
I used the wrong term, I mean boot to bootloader.
I also pressed the wrong buttons, vol down and power instead of vol UP and power.
Many thanks for your advise.

I messed up and my phone is stuck in the boot screen but I cant access the bootloader

(TL: DR below)So there's a bit of a story here, I installed cyanogenmod 13 iirc on my phone a while ago and none of the google services would work, so I used TWRP to flash SuperSU and another version of Open Gapps on my phone. The phone got stuck on the application initialization thing for when android updates apps for a new version. After 30 minutes, I restarted my phone like a moron and it wouldn't go past the boot screen. I can't even access the bootloader anymore, holding down the buttons doesn't do anything. I've tried using the android tools and adb sees the phone but it's unauthorized and I don't know how to authorize it without using my phone.
TL: DR: flashed supersu and gapps on cm13 and its in an infinite boot screen, cant get to bootloader either. only thing i managed to do is get the phone to show up with "adb devies" as unauthorized. plz help ;(
Why can't you access the bootloader? Can't you just turn the phone off and hold the volume button down and power button on?
OhioYJ said:
Why can't you access the bootloader? Can't you just turn the phone off and hold the volume button down and power button on?
Click to expand...
Click to collapse
No, I get the "Can't check device for corruption" screen then the "Android" screen also shows your bootloader is unlocked and holding down the buttons does absolutely nothing.
IHaveNoImagination said:
"Can't check device for corruption"
Click to expand...
Click to collapse
It will only pop up when your booting sequence goes beyond boot-loader. Trying holding power+vol down till you get bootloader or 1 min whichever is minimum.

Categories

Resources