Database Info

Please help, volume and power buttons not working in fastboot.

My power button is broken so I need to take my phone in to get it replaced. Following the instructions to get it unrooted/return to stock, I need my phone to be recognized in fastboot. It's not happening; I've tried it on three PC's and none of them even see a device connected. It's not even a matter of drivers because when I'm in fastboot it's like nothing is connected at all.
I can't use my volume buttons in fastboot, basicaly I can't do anything at all in fastboot...no volume buttons, no power button and it can't be recognized.
Volume buttons work when phone is turned on. I can do anything I want in recovery or when the phone is up, but in fastboot I can't do anything.
Someone please help!!
By the way, ADB works perfectly but obviously fastboot does not because my PC thinks nothing is connected when fastboot is up on my phone and as I mentioned, my phone is completely unresponsive to anything that I do when I'm in fastboot. I can't use the "volume up/volume down" and tap the power button to get into downloading mode either because MY STUPID POWER BUTTON IS BROKEN!!!
Thank you again in advance....you will be my hero if you can help me with this!!!

forumsid987 said:
My power button is broken so I need to take my phone in to get it replaced. Following the instructions to get it unrooted/return to stock, I need my phone to be recognized in fastboot. It's not happening. I also can't use my volume buttons in fastboot, basicaly I can't do anything at all in fastboot...no volume buttons, no power button and it can't be recognized.
Volume buttons work when phone is turned on.
Someone please help!!
Click to expand...
Click to collapse
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.

delete pls , my mistake sry

simms22 said:
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
Click to expand...
Click to collapse
I have tried that so much I think I'm going to break my phone.
I just need someway to return this phone to stock without expecting fastboot to work because it seems like it is unresponsive since the power button is not working. I know this sounds weird as heck but I have all the correct drivers installed but three different computers don't see any kind of usb device connected when the phone is in fastboot. I sincerely believe it's because while in fastboot my messed up powerbutton is screwing it up because it's thinking that the power button is held down the entire time.
If anyone has any ideas on how I can get back to stock please tell me. I have 100% access on my phone when it's in recovery because I can use the buttons at the bottom and I have 100% access when it's fully booted up but when it's in fastboot I can't do anything and no computer even sees a USB device connected to it.
Pleaseeee help!!

forumsid987 said:
I have tried that so much I think I'm going to break my phone.
I just need someway to return this phone to stock without expecting fastboot to work because it seems like it is unresponsive since the power button is not working. I know this sounds weird as heck but I have all the correct drivers installed but three different computers don't see any kind of usb device connected when the phone is in fastboot. I sincerely believe it's because while in fastboot my messed up powerbutton is screwing it up because it's thinking that the power button is held down the entire time.
If anyone has any ideas on how I can get back to stock please tell me. I have 100% access on my phone when it's in recovery because I can use the buttons at the bottom and I have 100% access when it's fully booted up but when it's in fastboot I can't do anything and no computer even sees a USB device connected to it.
Pleaseeee help!!
Click to expand...
Click to collapse
i believe that my phone thinks my power button is always pressed down too, but fastboot works here. my suggestion is that you try a different usb chord. i had an usb chord that i could charge with fine, but nothing else worked. i thought my nexus one was messed up until i tried another usb chord.

simms22 said:
i believe that my phone thinks my power button is always pressed down too, but fastboot works here. my suggestion is that you try a different usb chord. i had an usb chord that i could charge with fine, but nothing else worked. i thought my nexus one was messed up until i tried another usb chord.
Click to expand...
Click to collapse
I tried 3 cords, I'm going crazy here! USB works perfect everywhere but both fastboot and recovery don't let me use my volume or power buttons...at least I can get by in recovery because of the capacitve buttons but I need fastboot to return to stock to get a new phone. I am so frustrated!!!!

forumsid987 said:
I tried 3 cords, I'm going crazy here! USB works perfect everywhere but both fastboot and recovery don't let me use my volume or power buttons...at least I can get by in recovery because of the capacitve buttons but I need fastboot to return to stock to get a new phone. I am so frustrated!!!!
Click to expand...
Click to collapse
have you tried pdanets website? http://junefabrics.com/android/
go there, download the free download and install it to youre computer. its tethering software. but thats not why you should try it. follow the on screen instructions after its installed and itll install the proper latest drivers for your phone. theres a chance your drivers might be out of date.

oh yeah. Used pdanet drivers and Google drivers. No luck with either. I can adb with both but like I said the deicer is not the issue it's that fastboot is totally unresponsive so it looks like nothing is connected to the pc
Sent from my Nexus S 4G using XDA App

anyone have any other options/ideas for me?? It would be greatly appreciated

Find an Odin package. Put phone into download mode by installing battery, holding volume buttons while connected to USB.
Does anyone know if the 301k ohm resistor jig works for ns?
Sent from my Nexus S 4G using xda premium

ODIN doesn't work because of the gosh darn power button being broken.
I went kinda crazy and erased everything in recovery so now all the phone does is boot straight into fast boot. I deleted the boot.img recovery everything, hahahaha (I laugh but really I'm crying inside).
I need a fix ASAP, I'm officially out of a phone.

simms22 said:
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
Click to expand...
Click to collapse
Wow, this actually worked for me Thanks Simms!
I just got stuck in the same situation (http://forum.xda-developers.com/showpost.php?p=22884288&postcount=24) so I kept tapping the back of my phone (with the back cover off). Fastboot kept restarting at first, but then my volume keys started allowing me to change options. I selected recovery and nandroid restored my phone. Now all is well *wipes brow*
Funny thing is, my power button now works properly again (it hasn't been working for the past week)

forumsid987 said:
oh yeah. Used pdanet drivers and Google drivers. No luck with either. I can adb with both but like I said the deicer is not the issue it's that fastboot is totally unresponsive so it looks like nothing is connected to the pc
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
have you found any solution? I have the exact same problem here: powerbutton stucks and no usb-recognition in fastboot (no luck with the tapping either) but no problem with adb in normal mode.
would be great to know if you found a way to deal with this. Thanks!

kajik123 said:
have you found any solution? I have the exact same problem here: powerbutton stucks and no usb-recognition in fastboot (no luck with the tapping either) but no problem with adb in normal mode.
would be great to know if you found a way to deal with this. Thanks!
Click to expand...
Click to collapse
Same problem here.... going crazy since the power button just died on me. I think the device thinks the button is pressed all the time, which makes it a hw issue.. any help to retrieve data on phone would be great!

Having the same problem as the OP...
Pls can someone find us guys a solution.:crying:
Thanks

I had a broken power button and had the same problem. I just sent it back to Samsung with no ROM on it and they fixed the power button and put Gingerbread back on it even though I had voided my warranty by unlocking the bootloader ;')

MistaJae said:
Funny thing is, my power button now works properly again (it hasn't been working for the past week)
Click to expand...
Click to collapse
yeah. mine started workin again after installing jb... almost made me believe it was software problem
Sent from my Nexus S using xda app-developers app

caleb1783 said:
yeah. mine started workin again after installing jb... almost made me believe it was software problem
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Mine broke when I installed Jelly Bean. Something fishy is going on. Now I have the same issue as OP.

[Q] Stuck with bootloop no bootloader access :/

Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:

First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita

timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.

if you are SOFF u can go for RUU?

Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:

sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!

Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.

Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita

timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.

I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita

timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really

Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita

Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL

You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita

timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help

If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app

exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.

sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone

Bricked Phone?

I went out partying last night, woke up to a crack on my nexus 5 and wouldnt turn on but the led would flash red. I figured it lost its charge. Charge the phone for few hours, phone would turn on and off right away as if it still were not charged. It would than shut off but restart to a screen that said Firmware Update- Please wait while it installs- B100. Nothing would install, it would stay at 0%. So I held the power button and now, it only turns on to the google sign and keeps looping from there. I tried to turn it on in recovery mode but that doesnt work either. My phone was never rooted, bootloader never unlocked and I never put it in debugging. I dont know what to do!

so the ol' 3-button combo doesn't get you to the bootloader?

Yes, it does. Forgot to mention that.

tonytouch311 said:
Yes, it does. Forgot to mention that.
Click to expand...
Click to collapse
I don't know what you did, but your phone is not bricked. Hope you have a recent backup. If you can get into the bootloader I'd try a factory reset in recovery. If that doesn't work then you're going to have to unlock the bootloader and try to flash the factory image. None of this may work as idk what you did to your phone, but this is what I'd do.

Is flashing a factory image/unlocking bootloader possible even tho I can't get into the settings menu to turn on debugging option?

tonytouch311 said:
Is flashing a factory image/unlocking bootloader possible even tho I can't get into the settings menu to turn on debugging option?
Click to expand...
Click to collapse
Yes, adb and fastboot are not related.
Sent from my Nexus 10 using Tapatalk 4

Are there any guides you all might suggest that are easy to understand?

Ask your friends what happened last night. Sounds like a good party
==**Team Nexus 5 sucks.**==
-Underpowered battery for a 5inch 1080p screen that is non-removable. Weak generic antenna that drops signal. Worst speaker of any device on the market. Cheap plastic build

tonytouch311 said:
Are there any guides you all might suggest that are easy to understand?
Click to expand...
Click to collapse
Alright, here. The catch-all solution: flash the factory image as in this thread http://forum.xda-developers.com/showthread.php?t=2513701.
Just remember to cd to your adb directory, I made that mistake and almost fainted because I thought my device was totally broken when fastboot devices listed nothing.
dicecuber said:
Ask your friends what happened last night. Sounds like a good party
==**Team Nexus 5 sucks.**==
-Underpowered battery for a 5inch 1080p screen that is non-removable. Weak generic antenna that drops signal. Worst speaker of any device on the market. Cheap plastic build
Click to expand...
Click to collapse
Really?? Is this your sig or just something totally irrelevant that you decided to insert into your reply? Do you even own one?

droid_<3er said:
Really?? Is this your sig or just something totally irrelevant that you decided to insert into your reply? Do you even own one?
Click to expand...
Click to collapse
It's his sig. Just ignore him.

I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.

tonytouch311 said:
I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.
Click to expand...
Click to collapse
If that's the case it sounds like you may have knocked something loose internally when whatever happened that caused the damage to your screen. Possibly a solder point or a cable coming loose.

Opened up the back cover, looks like condensation.....ill leave it alone for a few days and try again.

Reset
tonytouch311 said:
I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.
Click to expand...
Click to collapse
Did u do another factory reset after last flash as this may need doing on some phones from what I've watched on good old YouTube...Good luck..

^Why would he factory reset when the phone is wet? You'll short circuit it that way..

The only method of a factory reset I've read about was turning on in Recovery, waiting for the little android, and holding Vol + and Power. Thing is my phone would never get to the little android, just loop on the GOOGLE introduction. Is there another method to factory reset?

tonytouch311 said:
The only method of a factory reset I've read about was turning on in Recovery, waiting for the little android, and holding Vol + and Power. Thing is my phone would never get to the little android, just loop on the GOOGLE introduction. Is there another method to factory reset?
Click to expand...
Click to collapse
Turn your phone off. Then hold power + vol down. It should boot into the boot loader. You'll see a "start" Then use the vol rocker to toggle to recovery. Once there push the power button. You should be in recovery. Then use the vol rocker to toggle to factory reset. Then use power to select it.

jd1639 said:
Turn your phone off. Then hold power + vol down. It should boot into the boot loader. You'll see a "start" Then use the vol rocker to toggle to recovery. Once there push the power button. You should be in recovery. Then use the vol rocker to toggle to factory reset. Then use power to select it.
Click to expand...
Click to collapse
Thats the method I'm unable to use...I was hoping there might be a string of code I could type into a command prompt being that I can only turn on the phone into the boot loader.

tonytouch311 said:
Thats the method I'm unable to use...I was hoping there might be a string of code I could type into a command prompt being that I can only turn on the phone into the boot loader.
Click to expand...
Click to collapse
Try
fastboot reboot recovery
Edit, sorry that's not going to work. Find the stock recovery image. Then try
fastboot boot recovery.img

So I was able to boot in recovery and factory reset, although the problem still persists. I will try and flash all images tomorrow. Thanks for all the help! Happy holidays!

[Q] Hard brick?

Hey Guys,
so ive been messing around with this little phone and think i might have managed a hard brick. Any thoughts or advice would be appreciated.
was attempting to relock the bootloader and flashing my local 4.4.2 rom and on the command prompt when i reached flash system.img parsechunk lines, they failed. as it said permission denied.
Tried to continue with no luck. Restarted my phone and now cant get into recovery and no boot, the only screen i see is the white warning bootloader locked screen, get a vibrate and then it turns off again. Any ways to flash without Recovery or Fastboot or am i completely out of luck?
Sorry im new to motorolas, had no problems messing around with my old SGS2
Thanks in advance everybody.

did you try this ?
http://forum.xda-developers.com/showthread.php?t=2542219

the only problem is cant get the phone into fastboot mode. Thanks for the input though!

mackb44 said:
the only problem is cant get the phone into fastboot mode. Thanks for the input though!
Click to expand...
Click to collapse
I've been in a few situations where I thought I had 'bricked' my phone. One way that worked (sometimes) was to long press the POWER button for a very long time(minutes), then release and (sometimes) it would reboot.
The usual way to the fastboot menu is - power off (which yours probably is), then hold vol. down and press power button for 5/10 seconds and release both.
Good luck!

jamsh said:
I've been in a few situations where I thought I had 'bricked' my phone. One way that worked (sometimes) was to long press the POWER button for a very long time(minutes), then release and (sometimes) it would reboot.
The usual way to the fastboot menu is - power off (which yours probably is), then hold vol. down and press power button for 5/10 seconds and release both.
Good luck!
Click to expand...
Click to collapse
Yea tried both options, no luck!
The only screen i can get now is the bootloader unlocked screen or the white charging screen when plugged in. After that the screen will stay on but is completely black.

Success I can get into fastboot now!!!! not sure why i could not before

mackb44 said:
Success I can get into fastboot now!!!! not sure why i could not before
Click to expand...
Click to collapse
yes i had something similar,bootlocker warning and then the screen going dark. i just ended up using fastboot and flashing a stock rom and went from there.
glad your panic is over .

quizmaniac said:
yes i had something similar,bootlocker warning and then the screen going dark. i just ended up using fastboot and flashing a stock rom and went from there.
glad your panic is over .
Click to expand...
Click to collapse
Yea thanks buddy!
just have to wait for it to charge up before it will let me flash using adb, oddly its only showing that it is charging while plugged into usb and not the wall socket

[Q] Did i just brick my first phone.......?

was installing ARHD 7.0, which ive done several times and now the phone wont boot after a reboot. i can vol/pwr up to get to the splash screen, but cannot get into fastboot/hboot or back into twrp. any ideas?

Belay my Last!
Fortunately I found a post from the M8 thread and was more or less, a timing issue on my part. Thanks to Tikerz for his post/reply
Quote below:
"When you plug it into the computer does the computer make a ding sound that it's connected? If so, then press power and volume up until the disconnect ding sound which indicates it's rebooting and then immediately press volume down and see if you can get into fastboot. The timing is tricky so I've found using audio cues from computer can help if the phone is messed up."

I had to do this also. It will work. I thought for sure I had bricked my M8. But if u hold power and volume up at same time time screen goes black..then let go of power and volume up and hold volume down till u see fastboot. From there u can fastboot flash RUU package. I say that cause I personally found that restoring a backup of re-flashing ROM didnt work..at least for me.
http://forum.xda-developers.com/showthread.php?t=2727831

donlu30 said:
was installing ARHD 7.0, which ive done several times and now the phone wont boot after a reboot. i can vol/pwr up to get to the splash screen, but cannot get into fastboot/hboot or back into twrp. any ideas?
Click to expand...
Click to collapse
A brick refers to a phone that is essentially a .. brick. Won't power on, no charge light, 100% dead.