Develop Bugs

(Q) Phone stuck in bootloader, volume and power keys not working, cant connect to adb

Ok so the other day i turned my phone on and it went straight into the bootloader and the volume and power buttons arent responding. When i try to connect to adb it doesnt recognize that the phone is connected. I know i have adb set up right cause i can connaect my HD2 to it and it connects fine. I searched on here but couldnt find an answer and i dont wanna do anything that could make the situation worse. Does anyone know what i should do or is there a thread somewhere that would help me? Thanks

Anyone? I also have it rooted with eng-hboot and s-off and have been on CM7 for a while. I dont think its a prob with the wrong drivers either cause i have htc sync installed . I did try PDAnet but it fails at the last step and says something about failed to handshake.

Think i posted this in the wrong section.

Daryl Keith said:
Ok so the other day i turned my phone on and it went straight into the bootloader and the volume and power buttons arent responding. When i try to connect to adb it doesnt recognize that the phone is connected. I know i have adb set up right cause i can connaect my HD2 to it and it connects fine. I searched on here but couldnt find an answer and i dont wanna do anything that could make the situation worse. Does anyone know what i should do or is there a thread somewhere that would help me? Thanks
Click to expand...
Click to collapse
Are you s-off or s-on? If it's s-off try putting an ruu as a pc10img.zip on your sdcard and flashing it through bootloader.
if that dont work......
Try removing your SD card, then see if you can get to recovery through the BL.
if that dont work......
You need adb. I'm not saying it will work but its worth a shot. If you don't know adb there is a guide in the dev section.
If you can get adb connected to your device after you adb shell into phone you can run "adb reboot recovery".

If you have the fastboot binary, type this in your computer's Terminal:
fastboot reboot
Click to expand...
Click to collapse

blackknightavalon said:
If you have the fastboot binary, type this in your computer's Terminal:
Click to expand...
Click to collapse
I'm having the same darn issue...I tried the fastboot connect command "reboot recovery"and it does the reboot but comes right back to the boot loader screen no options to scroll and select anything...phone was fine until it froze and couldnt do no reboot power down or anything had no choice to pull the battery...theirs gotta be a work around on this...

im also having a problem, my phone has broken volume buttons, i can get to recovery but after that i dont know what to do since theres no volume buttons. i want to refllash cm7 but how?

stumpyz9 said:
im also having a problem, my phone has broken volume buttons, i can get to recovery but after that i dont know what to do since theres no volume buttons. i want to refllash cm7 but how?
Click to expand...
Click to collapse
Use the trackpad
Sent from my HTC Vision using xda premium

[Q] I think I messed up manual update, please help

Hi all,
My OTA update kept failing so I attempted a manual update to 4.04.
I missed updating the boot.img file. I did the system, recovery and radio then relocked the bootloader.
When I turn it on, it stays on the google splash screen. When I go into bootloader mode and try recovery mode, I get the red triangle. My computer does not seem to be recognizing the phone, I get the error: device not found.
Is there something I might try?
Thanks in advance

AV8ing said:
Hi all,
My OTA update kept failing so I attempted a manual update to 4.04.
I missed updating the boot.img file. I did the system, recovery and radio then relocked the bootloader.
When I turn it on, it stays on the google splash screen. When I go into bootloader mode and try recovery mode, I get the red triangle. My computer does not seem to be recognizing the phone, I get the error: device not found.
Is there something I might try?
Thanks in advance
Click to expand...
Click to collapse
In fastboot mode (obviously), unlock the bootloader, flash the boot image, and leave the bootloader unlocked. Done.

Thanks for the quick repy efrant! A big question is how do I unlock the bootloader if my computer doesn't recognize the phone. I am getting "device not found" so I seem to be unable to unlock the bootloader in the first place.

AV8ing said:
Thanks for the quick repy efrant! A big question is how do I unlock the bootloader if my computer doesn't recognize the phone. I am getting "device not found" so I seem to be unable to unlock the bootloader in the first place.
Click to expand...
Click to collapse
So your GNex is booted in fastboot mode and your computer does not recognize it? If this is the case, it is likely a driver issue, and you should re-install.
It is normal that your GNex is not recognized by your computer when booted not in fastboot mode, when you can't boot.

efrant said:
So your GNex is booted in fastboot mode and your computer does not recognize it? If this is the case, it is likely a driver issue, and you should re-install.
It is normal that your GNex is not recognized by your computer when booted not in fastboot mode, when you can't boot.
Click to expand...
Click to collapse
Hey efrant ^^ I'll sort it out ^^ (if you don't mind)
Dude, chec my sig, all the drivers and tutorials needed, can be found in the Win8 thread.
Follow that tut. then the phone should be recognized. Then erase the phone With:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
This ensures, that the flash is successful. If you don't erase first, it's likely, that the phone won't correctly write the files.
Then flash the files, with these codes:
Code:
fastboot flash boot (Always do this first) <Fille directory\file name.img>
fastboot flash system <Fille directory\file name.img>
fastboot flash recovery <Fille directory\file name.img>
DO NOT ERASE/FLASH userdata!! Do that, and you WILL lose ALL of your data!
If you want, I can help you, with tamviewer. I've helped a few people, this way It has always worked

Normally it does recognize the phone, but it doesn't seem to since I messed this up. I will try to re-install the drivers to see if that works. It is in fastboot mode, I hear the tone from the computer that something has connected when I reboot the fastboot, but it doesn't get recognized.

AV8ing said:
Normally it does recognize the phone, but it doesn't seem to since I messed this up. I will try to re-install the drivers to see if that works. It is in fastboot mode, I hear the tone from the computer that something has connected when I reboot the fastboot, but it doesn't get recognized.
Click to expand...
Click to collapse
Go into the dev manager, and look for: Android 1.0
If you see that, then Update devuice drivers -> Select from a list -> Samsung ADB Interface
That should do the trick

Thanks much, familyguy59. I'll try this now.

AV8ing said:
Thanks much, familyguy59. I'll try this now.
Click to expand...
Click to collapse
No prob. That's what some of us, have made to a "quest" Instead of flaming n00bs, help them, and make sure, they find their place, in this community

Thanks so much efrant and familyguy59! There were a couple of bumps in the road, but I flogged my way through them. I thought I had bricked my phone for sure. Once again, thanks so much.

AV8ing said:
Thanks so much efrant and familyguy59! There were a couple of bumps in the road, but I flogged my way through them. I thought I had bricked my phone for sure. Once again, thanks so much.
Click to expand...
Click to collapse
No prob, dude! That's what we're here for

familyguy59 said:
No prob. That's what some of us, have made to a "quest" Instead of flaming n00bs, help them, and make sure, they find their place, in this community
Click to expand...
Click to collapse
+1 to this guy XD
Sent from my Galaxy Nexus using XDA

jzero88 said:
+1 to this guy XD
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
And the "xD" was neccessary... in what way? ^^ It is true, though.
If you aren't feeling the same, then it's your thing. I'm here, to help others, and help them understand, what, what features do, and what is needed, to do what....

physically bricked?

phone stuck in bootloop. the kicker is my volume rocker is shot. and adb doesnt recognize while still in boot up. aaaaaaaaaaand the warranty is definetly not an option since i have had the inductive charge mod for quite some time now. if anyone knows of a way to go into recovery mode without turning the device on, OR pressing the volume buttons, please, come forth....

I think if all of those are true, you're SOL. In order for ADB or Fastboot commands from your PC to work, the phone must either be in the Bootloader or in Android with USB debugging on.
And to get into Bootloader, you must have a working volume rocker.... Are you sure you can't like hit it and it'll work or something like that?
Otherwise, your best bet is to send it in for warranty replacement and hope they won't notice, which might not be as much of a long shot as you think...

jimmyco2008 said:
I think if all of those are true, you're SOL. In order for ADB or Fastboot commands from your PC to work, the phone must either be in the Bootloader or in Android with USB debugging on.
And to get into Bootloader, you must have a working volume rocker.... Are you sure you can't like hit it and it'll work or something like that?
Otherwise, your best bet is to send it in for warranty replacement and hope they won't notice, which might not be as much of a long shot as you think...
Click to expand...
Click to collapse
Well if they turn it on wouldn't they notice the different bootup animation and the fact that it wont turn on? Who should I send it to? Google or Samsung? And how? Do u know of a best method?

bump for possible genius to know if theres a way to enter recovery without volume rocker or phone being on.

Are you stuck at the Google screen and when you use adb does it just say waiting for device?
Sent from my Galaxy Nexus using xda app-developers app

Andro X said:
Are you stuck at the Google screen and when you use adb does it just say waiting for device?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
no it goes past the google screen and gets stuck on the bootup image. it happened when i flashed superROM. it never went past the bootup image after that. and adb commands say "waiting for device" yes.

Ok. Are you using windows on your pc?
Sent from my Galaxy Nexus using xda app-developers app

Andro X said:
Ok. Are you using windows on your pc?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yeah. windows

Oh yeah what about ODIN? That might work for getting back to stock and a working Android OS that'll actually boot up.
That's probably why he's asking. Forgot all about ODIN. Although the fact that you can't boot up might be an issue... I'm gonna hand this over to Andro X.
I just meant hit like a light hit on the volume rocker to see if it'll knock something back into place...I don't think it'll really work though, I just gave out a sort of last resort option.

donavo said:
yeah. windows
Click to expand...
Click to collapse
Make a command prompt shortcut on your desktop. Right click and click new then shortcut then cmd for location and cmd for name. Once that's done right click on the cmd shortcut you made and run as administrator. Then adb kill-server and then adb start-server. Now try adb devices and see if your device is now recognized. If it is then awesome you can get to recovery by adb reboot recovery and bootloader by adb reboot bootloader.
Edit...
Just noticed I typed killer server lol by accident. It's adb kill-server. Now fixed above.

Andro X said:
Make a command prompt shortcut on your desktop. Right click and click new then shortcut then cmd for location and cmd for name. Once that's done right click on the cmd shortcut you made and run as administrator. Then adb kill-server and then adb start-server. Now try adb devices and see if your device is now recognized. If it is then awesome you can get to recovery by adb reboot recovery and bootloader by adb reboot bootloader.
Edit...
Just noticed I typed killer server lol by accident. It's adb kill-server. Now fixed above.
Click to expand...
Click to collapse
i type "adb kill-server" in the cdm prompt that opens after i run it as admin? cuz it dsnt look like that does anything...and it still says device not found

I'm new here, coming from another phone, a Galaxy S variant. There, we had a little contraption called a download jig. You put that thingie into a USB port, and a phone goes straight into the download mode. Don't know if such thing exists for Nexus. Does it?
Sent from my SGH-T959V using xda app-developers app

Hmm... That's something you could do. A jib..... I'd like to know more, perhaps it will work, they're both Samsung, after all.
Andro X, I was hoping you were leading to ODIN lol.
What about ODIN? Try getting that set up and hitting start on ODIN just as you power on your Galaxy Nexus. Don't hold your breath, though, it may fail like getting adb commands working, because you're not in bootloader or Android.
adb kill-server is instantaneous, you wouldn't see any real output on command prompt- that is normal.

jimmyco2008 said:
Hmm... That's something you could do. A jib..... I'd like to know more, perhaps it will work, they're both Samsung, after all.
Andro X, I was hoping you were leading to ODIN lol.
What about ODIN? Try getting that set up and hitting start on ODIN just as you power on your Galaxy Nexus. Don't hold your breath, though, it may fail like getting adb commands working, because you're not in bootloader or Android.
adb kill-server is instantaneous, you wouldn't see any real output on command prompt- that is normal.
Click to expand...
Click to collapse
yeah but making th enew shortcut didnt help. i went to program files/android master. shift right click and open a cmd window there. from there i did the commands. there was some response but still the phone was not found

okay here is what im coming up with. i can open the phone and find the contacts for where the volume attaches. does anyone know what i can do from there? soldering the volume button back on is not an option. ive been trying that all day. only thing left is shorting the contacts so the phone is fooled into a state where the buttons are held. there are 3 contacts. anyone know which ones i should be shorting? or if thats even workable? i may have completely screwed the contacts by now....ive tried maybe 40 times.

OMG!!!!!! i just did some soldering. pressed power button and now im in ODIN MODE. idk what this means.....all it says is "downloading do not turn off target. what do i do??????

Uh... Flash something
I777 gets it done, gnex just for fun

Cmoore0965 said:
Uh... Flash something
I777 gets it done, gnex just for fun
Click to expand...
Click to collapse
how?? it wont let me do anything. its in odin mode....cant do recovery with adb. not sure what odin mode even does

donavo said:
how?? it wont let me do anything. its in odin mode....cant do recovery with adb. not sure what odin mode even does
Click to expand...
Click to collapse
if you have correctly installed the samsung drivers, you can flash a rom via odin (proggram on your computer.)

thegtfusion said:
if you have correctly installed the samsung drivers, you can flash a rom via odin (proggram on your computer.)
Click to expand...
Click to collapse
oh man do i need ur help now. how do i do that? when i rooted the phone im sure all the drivers installed correctly. but where do i get the odin program??

Bootloop of horror

So I'm currently stuck in a horrible bootloop without the possibility of going in to hboot or recovery.
Was on ViperX 3.6.0 and on XM Kernel 300 when just out of the blue my phone restarted it self and went into a bootloop that i just don't seem to be able to get out of..
When I go in to hboot, it automatically goes to fastboot, then back to hboot, then bootloop (again).
Any suggestions?

How much time do you have to perform a command in the bootloader ?
When the phone hits the bootloader/fastboot usb you hit enter to clear the cache
Fastboot erase cache
Hopefully that solves the loop. Or try to power down

For some magical, mysterious reason, it booted normally - again, out of the blue!
Wth?!
Trying to get a last_kmsg, but ADB won't find my device - but fastboot does!

HoffaLompen said:
For some magical, mysterious reason, it booted normally - again, out of the blue!
Wth?!
Trying to get a last_kmsg, but ADB won't find my device - but fastboot does!
Click to expand...
Click to collapse
if you're using windows probably you're missing the drivers

Weird ! When the viper rom is booted you need to enable usb debugging......

matt95 said:
if you're using windows probably you're missing the drivers
Click to expand...
Click to collapse
Mr Hofs said:
Weird ! When the viper rom is booted you need to enable usb debugging......
Click to expand...
Click to collapse
Drivers are installed, trying to update them.
USB debugging is enabled.
Edit: Managed to get a last_kmsg, Here

Hmm i have no idea what to look at

Mr Hofs said:
Hmm i have no idea what to look at
Click to expand...
Click to collapse
That makes two of us!
Maybe I should post it in Xmister's thread?

Good idea. I may find something odd when i have loads of time. But i haven't

[Q] Please help me. [HTC ONE V]

I own a HTC One V. And I did something at the TWRP menu like installing this CARBON-JB-UNOFFICIAL-20131022-1552-primoc thing.. and ever since then the phone doesn't boot.. it won't even go to that menu where it says FASTBOOT{ I think it's called the recovery menu :3 }
But, I charge it.. And then I plug it into the comp, it just connects and disconnects, like it's giving a faint indicator of life :3
Please help. I was on Ignorance V5..

Installing a rom can't hard brick your device.
Try to shut it down by holding the power button and immediately press vol down + power to enter your bootloader. Then you can select recovery and install a backup of your ignorance rom or do whatever you want.
BTW: It looks like you forgot to install the kernel for the custom rom.

ManishByatroy said:
I own a HTC One V. And I did something at the TWRP menu like installing this CARBON-JB-UNOFFICIAL-20131022-1552-primoc thing.. and ever since then the phone doesn't boot.. it won't even go to that menu where it says FASTBOOT{ I think it's called the recovery menu :3 }
But, I charge it.. And then I plug it into the comp, it just connects and disconnects, like it's giving a faint indicator of life :3
Please help. I was on Ignorance V5..
Click to expand...
Click to collapse
Most likely you flashed the wrong ROM.
PrimoU <> PrimoC
Boot loader should still work as expected I guess:
<vol.down>+<power> should get you to the hboot menu.

kvestas said:
Most likely you flashed the wrong ROM.
PrimoU <> PrimoC
Boot loader should still work as expected I guess:
<vol.down>+<power> should get you to the hboot menu.
Click to expand...
Click to collapse
It's not going into Boot Loader. If it did, I would flash back Ignorance.
Please help

ManishByatroy said:
It's not going into Boot Loader. If it did, I would flash back Ignorance.
Please help
Click to expand...
Click to collapse
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.

jonas2790 said:
Installing a rom can't hard brick your device.
Try to shut it down by holding the power button and immediately press vol down + power to enter your bootloader. Then you can select recovery and install a backup of your ignorance rom or do whatever you want.
BTW: It looks like you forgot to install the kernel for the custom rom.
Click to expand...
Click to collapse
It isn't going to bootloader when i press power+volume down button.. :\
If I could enter the bootloader menu, I wouldn't have been this worried. :3

kvestas said:
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
Click to expand...
Click to collapse
Can you please tell me where to run this Command? I'm a noob sorry. :/

ManishByatroy said:
Can you please tell me where to run this Command? I'm a noob sorry. :/
Click to expand...
Click to collapse
This command has to be run on a computer.
Similar as you are running fastboot commands to root phone or install custom recovery.
Please google if you are not familiar with fastboot commands at all.
Make sure you have installed proper phone usb drivers to make your phone "visible" from computer.
Btw how did you get running Ignorance?

kvestas said:
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
Click to expand...
Click to collapse
kvestas said:
This command has to be run on a computer.
Similar as you are running fastboot commands to root phone or install custom recovery.
Please google if you are not familiar with fastboot commands at all.
Make sure you have installed proper phone usb drivers to make your phone "visible" from computer.
Btw how did you get running Ignorance?
Click to expand...
Click to collapse
My friend got ignorance running for me.. Like I don't know what and where to enter these fast boot commands.. Any link to learn or you explaining will be appreciated.

phone is blank. hasnt lighted a pixel in a week
phone is charged. how do i know this? because i charged it for 3 days :3
tried all combinations of buttons to get to bootloader. i just cant!!!
i connect it to a comp, it connects and disconnects simultaneously.. :/
pls tell me what to do

ManishByatroy said:
phone is blank. hasnt lighted a pixel in a week
phone is charged. how do i know this? because i charged it for 3 days :3
tried all combinations of buttons to get to bootloader. i just cant!!!
i connect it to a comp, it connects and disconnects simultaneously.. :/
pls tell me what to do
Click to expand...
Click to collapse
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.

kvestas said:
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
Click to expand...
Click to collapse
Just tried it. I selected device but stuck on downloading drivers
Thanks for the help tho mate

ManishByatroy said:
Just tried it. I selected device but stuck on downloading drivers
Thanks for the help tho mate
Click to expand...
Click to collapse
You can download HTC drivers from almost any other hOV thread.
Like this one in example:
http://forum.xda-developers.com/showthread.php?t=1996665
Basic Requirements. 4th item.
Remember, all you need to try with this tool is to reboot into bootloader. Try to click the tool button while your phone is starting to load.
By the way, you may find fastboot files in that thread as well (Basic Requirements. 5th item).

kvestas said:
You can download HTC drivers from almost any other hOV thread.
Like this one in example:
http://forum.xda-developers.com/showthread.php?t=1996665
Basic Requirements. 4th item.
Remember, all you need to try with this tool is to reboot into bootloader. Try to click the tool button while your phone is starting to load.
By the way, you may find fastboot files in that thread as well (Basic Requirements. 5th item).
Click to expand...
Click to collapse
Yes, I have the HTC Sync installed which gives the necessary drivers for the recognition of HTC phones.. ( My ONE V)
But, the computer just sounds that music when a USB device is connected, the phone is dead. Not even lighting up..
The WinDroid isn't recognizing my device as well..

ManishByatroy said:
Yes, I have the HTC Sync installed which gives the necessary drivers for the recognition of HTC phones.. ( My ONE V)
But, the computer just sounds that music when a USB device is connected, the phone is dead. Not even lighting up..
The WinDroid isn't recognizing my device as well..
Click to expand...
Click to collapse
The computer should not recognize your phone because it is not loaded completely (neither os, neither recovery).
But it might be recognized for a few seconds only while trying to load os. And you might be able to supply reboot command at that particular moment.
Just try what I said.

kvestas said:
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
Click to expand...
Click to collapse
kvestas said:
The computer should not recognize your phone because it is not loaded completely (neither os, neither recovery).
But it might be recognized for a few seconds only while trying to load os. And you might be able to supply reboot command at that particular moment.
Just try what I said.
Click to expand...
Click to collapse
Yeah.. I tried that.. But nothing is working.. The OS too isn't booting up. So I don't really know when my phone is on or off

ManishByatroy said:
Yeah.. I tried that.. But nothing is working.. The OS too isn't booting up. So I don't really know when my phone is on or off
Click to expand...
Click to collapse
Do you mean led is always off?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Try holding power button down for 30s.

kvestas said:
Do you mean led is always off?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Try holding power button down for 30s.
Click to expand...
Click to collapse
Tried. Ain't working. LED ain't even turning on while charging too.. So there's really no way to find out whether it's charging..

Update : Still haven't fixed my phone. Any help would be appreciated. Can't enter Bootloader menu. Phone when connected to computer, gives "sound" that every normal USB when connected gives.. So the phone isn't completely dead. After connecting, the computer doesnt react in any way :crying: