My G2 won't boot normaly and is acting very straingly. I did a search of other similar problems people have had, but nothing matches what is happening to mine. It started when I noticed my power button and volume up button stoped working. I assumed it was a glitch and thought a reboot might help. Since the power button wasn't functioning, I pulled the battery to reboot it. That's when it stoped working. When I turn it on normaly with the power button, the screen stays off, it vibrates three times, and the led blinks orange untill I put the battery. If I attempt to boot into recovery with the button combination, it does the same. If I attempt to boot into HBoot, it vibrates five times and the led lights up solid green. Here's where things get realy strange. When I plug the phone into the charger while the phone is off, after about five seconds the phone comes on into the recovery bootloader even though when I boot while holding the buttons it dosn't work. I have the ClockworkMod touch recovery installed. From within the recovery I have full access to everything including ADB with root access. When I select the reboot option from recovery, it does the same thing with the vibrating and the blinking led. I tried the key test in the recovery and I discovered that my volume up button only works intermitently and my power button seems to be working fine. I haven't attempted to flash a new rom yet because I'm assuming it must be something else since I can't even access HBoot, and I'm scared if I touch anything I'll loose access to recovery and ADB as well.
Any advice? Could a damaged volume up button contact cause all this to happen? Should I try flashing it from recovery even though I can't access HBoot?
Thread moved to Q & A section, post in the relevant section next time.
in adb try
adb reboot-bootloader
demkantor said:
in adb try
adb reboot-bootloader
Click to expand...
Click to collapse
Just tried it. Screen goes black, vibrates three times, and led blinks orange untill I pull the battey. It was a good Idea though, I didn't think to try that myself.
you know what, are these very quick vibrates? you mentioned there is a problem with your volume rocker (sticky keys?) your phone may be trying to get into the jtag/download mode.
not sure how to use this mode on the vision but tell me if this is the same response you get.
take out battery, hold both volume buttons, plug phone into computer.
it should vibrate three times rapidly and computer should look for driver :
Qualcomm CDMA Technolgies MSM driver
not sure where to get the proper driver for the vision but ive used this mode to root other android phones and i know there is a "unbricking project" for various phones that use this mode.
nothing for the vision that i know of though.
but being you have adb access maybe test a few things first like see if anything is accessible from your emmc
type:
Code:
adb shell
dmesg | grep mmc0
and see what happens
edit:
i can replicate you situation by holding volume up while powering on
you have a stuck volume up key, almost 100% just open up phone and clean it out and you should be just fine!
Related
Hey,
The issue is that the screen is blank and goes on a boot loop because the volume down button on the volume rocker is continuously pressed.
Because of which the phone doesnt allow android revoluntion to boot at all..
Always goes to the HBOOT menu from which if i click the power button it goes into bootloader mode but windows shows
QUALCOMM CDMA driver instead of the correct drivers.....
it doesnt show the correct driver.
Then i tried adb after removing the battery again.
i typed
adb devices
(once it found the devices)
adb shell
recovery.
now the screen comes alive and shows my 4ext recovery console.
The biggest problem here is the volume button not allowing me to boot into a ROM.
Is their a way to disable that or is it something else that i have done that i am not even able to revert to stock rom in
BOOTLOADER mode??
I thought it was a SLCD because i saw this post
http://androidforums.com/desire-all-things-root/215886-solved-desire-slcd-black-screen-bricked.html
But i realised that the above was for Desire and NOT of DHD.
I cannot even see the HBOOT menu. I somehow managed to get to the recovery becos of the shell command by adb.
What am i to do??
Can someone please help?
Moderator can close this Tread
I fixed it....everythings in working condition now...
I just took a twesers and removed the volume rocker from its housing by pulling the cable under the manufacturing sticker.
And then suspected that putting it back in its place would make it go back to the same state again but i hasnt for now...
It wasnt showing the HBOOT menu as the volume down button was constantly pressed instead of being released.
I wish i would have just done it sooner but anyways phewww.....
Hey guys,
I've flashed quite a few ROMs in the past 2 years. Today, I flashed a new ROM and it worked fine. After that, I installed Nova Launcher and changed the density to 160 and the phone asked for a reboot. However, it isn't booting after the reboot. I can see the white HTC screen for 1-2 seconds, after that the display dims and then turns off. Can't go into the bootloader or the recvovery. The phone charges normally (can see the orange light) and on connecting to the PC, it gives the successful connection sound. Any tips on how to fix this? I've done S-OFF long back if that helps. I've tried removing the battery and inserting after 5-10 mins, however I'm still getting the same output.
EDIT: Guys, just noticed that the phone isn't turning off after the HTC white boot screen. The backlight starts and then turns off after a second, and then starts again for a second and this keeps repeating..
Pull the battery.
bananagranola said:
Pull the battery.
Click to expand...
Click to collapse
Tried it a 100 times, same result ..
UPDATE: Though I can't see anything on the screen, the adb seems to recognise it.
http://prntscr.com/1zf32k
prateek.htc said:
Tried it a 100 times, same result ..
Click to expand...
Click to collapse
Did you reboot holding power and volume-down?
bananagranola said:
Did you reboot holding power and volume-down?
Click to expand...
Click to collapse
Yeah, tried all possible combinations incl the usual power + vol down. The HTC logo appears for 5 seconds and then I can only see the backlight on the screen for another 2 seconds. This backlight then turns off and turns on repeatedly every 2 seconds and continues till I remove the battery again.
In short: No bootloader access, no recovery access. Just can see the device after I connect it to pc and type adb devices.
UPDATE: Fixed. Used the adb, on typing adb reboot-bootloader, I could access the bootloader. Thanks guys!
Same problem, Please Help!
My DHD, passes the HTC logo, then goes blank. The backlight doesnt go off, its just blank and remains like that indefinitely.
There is no charging led light when on the blank state,
The blank state does get detected by the computer.
Fastboot Commonader V1.51 says no fastboot device detected.
(P.S. My volume keys are water damaged and do not work, so i cannot use Vol- and power)
quasar_sky said:
My DHD, passes the HTC logo, then goes blank. The backlight doesnt go off, its just blank and remains like that indefinitely.
There is no charging led light when on the blank state,
The blank state does get detected by the computer.
Fastboot Commonader V1.51 says no fastboot device detected.
(P.S. My volume keys are water damaged and do not work, so i cannot use Vol- and power)
Click to expand...
Click to collapse
just try plug your phone to pc...then open cmd n change source to adb folder that you place..then type "adb devices" if your phone detected in there..then you can continue to next command type "adb reboot bootloader" or "adb reboot recovery"..next if you success go into recovery..just flash/ install another rom from there..
hopefully can help...
That worked. Thanks
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)
wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.
Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.
Hello Everyone
TL;DR Screen doesn't come on at all, battery led only flashes while it is rebooting (More details below), and When plugged in to my windows pc, a bunch of "Local Disk Found" pop up, some of the volumes I can access, most I cannot.
I have searched and searched the internet the past 24 for solutions, and have yet to find one. So imma walk you through what led up to the issue, as well what solutions I have tried.
Yesterday while I was trying to update my rom, I ended up getting stuck in what I thought was a boot loop. I then decided to hard reset my phone and go into recovery in hope to try to reinstall the rom. To my surprise, I could not access the internal sd card in the phone. Data was unmounted in the "Mount" settings and I could not what so ever remount it. After this I tried to side load it, but to no avail.
In response to all my attempts to fix the phone at that point, in frustration, I just said "**** it" and went into factory reset in the bootloader. This is where the hard brick happened. At this point, the screen would not come one, and the battery led was not lit when plugged in. I tried letting my phone charge over night and then, tried the "Battery Recalibrate method". I then tried the "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader"
After that, I then thought that the firmware was corrupted, so I tried to see if I could push an img to the phone, however fastboot does not see the device. I tried RUU, it does not see the device. I tried the HTC Unbrick method by Dexter that required me to install ubuntu and do some things in terminal, that also did not find the device. And here I am stuck. One thing unique to my situation that I have yet seen reported in the countless threads I have searched, is that when I plug my phone to my pc, a large amount of disk drives are found. Most of them are not accessible, but there are a couple that I can go in and see files for. Windows asks me if I want to format the ones I can't access. When hooked to my pc, I tried the the Power + volume button combinations, the only thing that seems to happen off of this is that my phone seems to reboots, and the battery indicator briefly shows.
Anyways, this is all I can remember. Any help would be GREATLY appreciated. I don't really think it is a hardware related issue since my phone does somewhat boot. However it seems it can't get to a bootloader what so ever.
Try holding power and vol up for a long time, like a minute or more. Try with and without charger attached, and after sitting on charger overnight.
If the bootloader is intact, the phone is likely not truly bricked (recoverable). And I don't see how you could have damaged hboot by the actions you mentioned.
What is the phone's original CID (carrier version) and are you s-on or s-off?
redpoint73 said:
Try holding power and vol up for a long time, like a minute or more. Try with and without charger attached, and after sitting on charger overnight.
If the bootloader is intact, the phone is likely not truly bricked (recoverable). And I don't see how you could have damaged hboot by the actions you mentioned.
What is the phone's original CID (carrier version) and are you s-on or s-off?
Click to expand...
Click to collapse
Verizon is the carrier version, and I am s-off.
Held vol + up for 5 minutes both with and without the charger. One time with the charger into my computer, and another into the wall. When it was in my pc, I can tell its doing nothing but rebooting over and over by the notification sound, and the constant "Found new disk" notifications I got. However still no luck, no screen turns on, no sign of hboot. I'm hoping to have some luck after leaving it on charge overnight and trying again.
TheBizkit said:
Held vol + up for 5 minutes both with and without the charger. One time with the charger into my computer, and another into the wall. When it was in my pc, I can tell its doing nothing but rebooting over and over by the notification sound, and the constant "Found new disk" notifications I got. However still no luck, no screen turns on, no sign of hboot. I'm hoping to have some luck after leaving it on charge overnight and trying again.
Click to expand...
Click to collapse
So still nothing after leaving it on charge overnight and I held vol + up for about 5 minutes. Things seem grim.
I think the proper thing to do when you discovered internal storage was not mountable, would have been to use the TWRP option to format internal storage (in Advanced Wipe options).
But now I'm baffled as to what happened that would have rendered the phone unable to boot into fastboot mode. Fastboot won't recognize the device if you can't boot into fastboot mode, which leaves use kinda stuck.
So you didn't try to flash anything during the course of all this troubleshooting?
What you did - "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader" is totally wrong
I used to get this bunch of local disk pop-up and this is how I get out the problem
Connect the device to pc, you can hear notification sound on pc that device is connected. Ignore all those bunch of local disk pop-up
Press & hold both power button & volume up button until you hear another notification sound that device is disconnected from PC (that's the indication that device is restarted)
Release both power & volume up button and quickly press & hold volume down button (only this one button)
This should get you on bootloader
redpoint73 said:
I think the proper thing to do when you discovered internal storage was not mountable, would have been to use the TWRP option to format internal storage (in Advanced Wipe options).
But now I'm baffled as to what happened that would have rendered the phone unable to boot into fastboot mode. Fastboot won't recognize the device if you can't boot into fastboot mode, which leaves use kinda stuck.
So you didn't try to flash anything during the course of all this troubleshooting?
Click to expand...
Click to collapse
No, nothing was flashed except the original Rom update that got this snowball rolling (Not saying its the roms fault, most likely mine).
ckpv5 said:
What you did - "Hold Pwr + Volume up for 10 seconds, then Power + volume Down until you access the bootloader" is totally wrong
I used to get this bunch of local disk pop-up and this is how I get out the problem
Connect the device to pc, you can hear notification sound on pc that device is connected. Ignore all those bunch of local disk pop-up
Press & hold both power button & volume up button until you hear another notification sound that device is disconnected from PC (that's the indication that device is restarted)
Release both power & volume up button and quickly press & hold volume down button (only this one button)
This should get you on bootloader
Click to expand...
Click to collapse
This is the one combination I forgot to mention in the op, sorry for that.
But I have tried this, before and after your post, still no luck.
If it worth mentioning, I can just hold power + down and it still reboots over and over. As well as just power. As a matter of fact, all button combinations reboot the phone over and over.
TheBizkit said:
If it worth mentioning, I can just hold power + down and it still reboots over and over. As well as just power. As a matter of fact, all button combinations reboot the phone over and over.
Click to expand...
Click to collapse
I thought the screen was dead? If so, how do you know its rebooting?
redpoint73 said:
I thought the screen was dead? If so, how do you know its rebooting?
Click to expand...
Click to collapse
By it constantly connecting and disconnecting from my pc. If that doesn't mean its rebooting, then I guess I'm mistaken.
TheBizkit said:
By it constantly connecting and disconnecting from my pc. If that doesn't mean its rebooting, then I guess I'm mistaken.
Click to expand...
Click to collapse
Well, it might mean that.
If it in fact is rebooting over and over on its won, simply holding the vol down button for a long time, should put you into bootloader (on the next reboot "cycle"). Again, assuming it is in fact rebooting, and that bootloader is intact.
Hi everyone,
So yeah, I probably shouldn't have played around with recovery, bootloaders and custom OS, but my XZ2 Compact was rendered nearly useless by the last Android update, so I tried to install the new official Lineage OS on it. But I failed. Hard.
Symptoms
The phone now only reacts to the power button. When I press it, it displays a battery charge icon for a minute or two, then the screen turns off.
None of the other physical buttons do anything, and the button combinations don't work. As a result, I can't boot to recovery, or even access to fastboot.
The light indicator is on and red.
I let the phone drain its battery, see what happens, and well, nothing. Eventually the screen stops turning on. When I replug the phone, even if I don't touch anything, it will end up showing me the battery icon again, and is stuck in the same loop.
'adb devices' still sees my phone, but with no permissions. 'fastboot devices' doesn't see anything.
On Windows, Emma (Sony's flashing tool) doesn't see the device.
Causes
I was following this tutorial. I went up to "temporarily booting a custom recovery using fastboot". I used the latest LineageOS recovery for my phone, and the flashing worked fine according to the output of the fastboot command. But that's all. Impossible to do anything after that.
Do I now own a glorified paper weight? Or can I save this?
Thanks!
SOLVED! I managed to stop the charging loop with a key combination I discovered: volume up + volume down + power for about 10s. Then was able to load the bootloader and re-flash a recovery, custom ROM etc. Thank you all for your help.
Have you tried to hold vol+, vol- and power button all together for (at minimum) a minute?
I would then try to restore stock firmware with newflasher (you'll find it using Google search or here on xda).
Great, thanks a lot I didn't know this key combination and it allowed me to get out of that charging loop and start the bootloader. Problem solved!
Nice, glad to hear!