Database Develop

[Q] Samsung Galaxy S GT-I9000 won't work if not plugged on external power source

Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !

Marc_B_ said:
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Click to expand...
Click to collapse
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?

timberman4444 said:
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
Click to expand...
Click to collapse
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?

Marc_B_ said:
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Click to expand...
Click to collapse
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.

Hi again, try to play a song and turn the screen off to see what happens.
Sent from my GT-I9000 using xda app-developers app

timberman4444 said:
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Click to expand...
Click to collapse
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress

Marc_B_ said:
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Click to expand...
Click to collapse
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then

timberman4444 said:
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
Click to expand...
Click to collapse
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?

Marc_B_ said:
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Click to expand...
Click to collapse
you tried to install the rom on the recovery instead of odin?

timberman4444 said:
you tried to install the rom on the recovery instead of odin?
Click to expand...
Click to collapse
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive

Marc_B_ said:
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Click to expand...
Click to collapse
so, you can`t install any rom at the moment?

timberman4444 said:
so, you can`t install any rom at the moment?
Click to expand...
Click to collapse
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...

Marc_B_ said:
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Click to expand...
Click to collapse
Pretty bad signals there.. i think you should go to a repair shop or buy another device

timberman4444 said:
Pretty bad signals there.. i think you should go to a repair shop or buy another device
Click to expand...
Click to collapse
Sadly, yes... thanks for helping however !

Unbrick HTC One M7 (M7wls)

Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.

Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!

Amazing trick
Thanks a million times!
Incredibly for me, the light-bulb-and-play-with-buttons trick worked for me straight away.
Just incredible!
(I might be too noob, but what's the hidden logic for it?)
Thanks again !!

Thanks a million mate, it worked like a charm. God Bless you !!

RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
These are only soft bricks

Bricks!
MacHackz said:
These are only soft bricks
Click to expand...
Click to collapse
Yep. A real hard brick is a brick. Make a "I dragged my phone behind my car and this is how little it got beat up in my Otterbox" video.
himhz said:
Incredibly for me, the light-bulb-and-play-with-buttons trick worked for me straight away. what's the hidden logic for it?
Click to expand...
Click to collapse
It apparently has something to do with resetting input awareness. Either there's a photodiode that picks up on light levels, or the IR diode detects the heat from the bulb. Thus, when the phone's diode is fully activated, it apparently activates that reset. I haven't heard from anyone, but I strongly suspect if the battery were completely drained somehow, then it might allow you to charge it and turn it back on regularly. Otherwise, the option 2 bypass should still work even on a dead battery refusing to charge till it resets, since it may current from light/heat. I'm also curious to find if anyone can tell if the handset is actually still accepting a charge despite the lack of LED activity while its in the soft-bricked state, or if the charging circuitry refuses to allow current to pass to the battery. HTC? HTC?
Thumbs ups appreciated!
See you all at XDA: DevCon

RDshift said:
Yep. A real hard brick is a brick. Make a "I dragged my phone behind my car and this is how little it got beat up in my Otterbox" video.
See you all at XDA: DevCon
Click to expand...
Click to collapse
A real brick is when hboot is not accessible no matter what you do, and there is no sign of life.
Don't get sarcastic

Matt said:
A real brick is when hboot is not accessible no matter what you do, and there is no sign of life.
Don't get sarcastic
Click to expand...
Click to collapse
I've tried the two steps from above and my phone still just flashes the Back and Home lights when I hold down power.
I was running a cyanogen nightly (from maybe 3 weeks ago) when the phone shut off randomly (not dead battery) and wouldn't turn back on.
When plugged in via usb the device shows up in the eject devices system tray but "fastboot devices" lists no devices. I have the phone plugged into a rear usb2.0 port.
Starting to get nervous...not sure what my options are.
EDIT: Holy smokes option two worked after a third try. That's so wild. Thank you!

XeoNiCaLiTy said:
Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!
Click to expand...
Click to collapse
WOW after an hour of trying to fix the issue option number 2 worked for me lol i can't believe it. sounds so ridiculous

None of the options worked for me... Please help!
My HTC One shutdown and now I can't turn it back up.
Hardware is in flawless condition.
I tried all combinations and options and still my phone is dead.
I know it's not the hardware problem. Checked voltage regulator, phone is charging, voltage and amps are ok. Logic board is in excellent condition, checked with microscope and multimeter.
Was used regularly and one day just turned off by itself.
Also I haven't messed around software because I don't have need for that kind of work.
Again please help me, I'm pretty desperate.

dude!
RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
Option 2 did the trick for me!you'r a life saver mate!kudos

My is stuck in a reboot loop. It was running GPE which cause the sim unlock code not to stick. One person told me that I need to go back to stock so I tried to flash the stock RUU and now stuck in reboot loop.
Neither method work for me! I can get into fastboot screen but can't flash anything. Having a hard time trying to install adb driver though

HOLY BEJEEZUS!! I just tried your option 2! I thought i just bricked this thing, and i need to return it for the warranty exchange in a few days. Holy cow thank you!!!! I had the capacitive lights blinking and the red charging light on. Coudln't run commands. Held it up to a CFL bulb, played with the power and volume buttons and BAM!! Booted back up. Thanks tons!! Phew!!!
Now to get rid of the frigging tampered stamp in fastboot. Can't get rid of it for the life of me. Tried using just Revone, Tried the All in One toolkit. Nothing. Thanks again.

whitetiger_0603 said:
HOLY BEJEEZUS!! I just tried your option 2! I thought i just bricked this thing, and i need to return it for the warranty exchange in a few days. Holy cow thank you!!!! I had the capacitive lights blinking and the red charging light on. Coudln't run commands. Held it up to a CFL bulb, played with the power and volume buttons and BAM!! Booted back up. Thanks tons!! Phew!!!
Now to get rid of the frigging tampered stamp in fastboot. Can't get rid of it for the life of me. Tried using just Revone, Tried the All in One toolkit. Nothing. Thanks again.
Click to expand...
Click to collapse
Are you S-Off? if yes, you can either use adb commands (if your comfy with that): http://forum.xda-developers.com/showthread.php?t=2477792
or just use this tool: http://www.htc1guru.com/guides/guru-bootloader-reset/

RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
Unfortunately, neither of these options worked for me. My phone is completely unresponsive with no charge light, no reaction to light, no USB recognition, no hard reset functionality, inability to access bootloader or anything for that matter.
I am uncertain as to what the problem is, but the phone had <40% charge when it failed. Are there any other alternatives?
[pending update(s)]

THANK YOU!!!!
Dude thank you so much, I just formatted my internal storage using the new TWRP 2.7 and for some reason I had a black screen with only the red light on. After a few minutes of failure, not being able to boot up to both recovery and bootloader, I tried OPTION 2, which saved my phone.
THANK YOU SO MUCH!

No OS Installed.
Hi guys. I was flashing ARHD Rom and it was suddenly failed. Now I stuck at recovery mode, twrp 2.6.3.3. I forgot to do back up. and I did some factory reset and now that's how I stuck at the recovery mode. So yeah. I need help. Thanks.

Thanks a ton
Option 2nd worked... i installed insertcoin 2.1.4 and it happened.
flashed back to renovate.
once again thanks mate. cheers

Crazy way to unbrick M7
XeoNiCaLiTy said:
Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!
Click to expand...
Click to collapse
Sounds like urban legend, but i tried everything else. Worked right quick.
BTW, my soft brick came from just trying out droidwall blocking a puzzle game. App must have crashed badly.

No OS Fix
heyAmirulS said:
Hi guys. I was flashing ARHD Rom and it was suddenly failed. Now I stuck at recovery mode, twrp 2.6.3.3. I forgot to do back up. and I did some factory reset and now that's how I stuck at the recovery mode. So yeah. I need help. Thanks.
Click to expand...
Click to collapse
Try sending a rom using adb, then flashing to that rom. That's what I had to do when I had no OS installed on my Kindle Fire.

Some serius help needed. Bootloop, stuck, bootloader not working etc..

Hi. To start with I bought a phone from a friend which I knew was faulty but decided to take my chances and try to fix it. He claims he did nothing to the phone but don't know for sure. Phone is in constant bootloop, Goes until splash screen and reboots. Worst yet to come - even bootloader menu restarts on constant basis when i try to get into it. Meaning it goes into bootloader but restarts in few seconds before i can get to factory reset. Computer is not picking up this device but i also don't have any drivers installed but don't even know how to install them with a phone in this state. Is there anything i can do about it? Been with Samsung for the past few years and here is everything completely different so don't know much about adb but am a quick learner and can follow any steps! I can provide picture of bootloader if it would be any helpful.

michal_alton said:
Hi. To start with I bought a phone from a friend which I knew was faulty but decided to take my chances and try to fix it. He claims he did nothing to the phone but don't know for sure. Phone is in constant bootloop, Goes until splash screen and reboots. Worst yet to come - even bootloader menu restarts on constant basis when i try to get into it. Meaning it goes into bootloader but restarts in few seconds before i can get to factory reset. Computer is not picking up this device but i also don't have any drivers installed but don't even know how to install them with a phone in this state. Is there anything i can do about it? Been with Samsung for the past few years and here is everything completely different so don't know much about adb but am a quick learner and can follow any steps! I can provide picture of bootloader if it would be any helpful.
Click to expand...
Click to collapse
Send a picture of the bootloader while I find the drivers you need

Seems like battery is completely dead as it only reboots when there is power supply connected, but then it won't turn off (any charging light don't come on, not sure if it should though). Just now i've seen a vodafone logo for a very short second when I connected to pc from charger. But phone rebooted again just after.
HTC_Phone said:
Send a picture of the bootloader while I find the drivers you need
Click to expand...
Click to collapse
edit. downloaded drivers (4.8) but that didn't change anything and windows still doesn't pick up device.
After connecting my one to computer for past 3 hours its started more frequently boot and showing Vodafone menu but still restarts shortly after. Vodafone logo shows on and lights on soft buttons starts flashing like 3 times and than it keeps rebooting. Does it mean anything?

michal_alton said:
Seems like battery is completely dead as it only reboots when there is power supply connected, but then it won't turn off (any charging light don't come on, not sure if it should though).
Click to expand...
Click to collapse
Have you checked this: http://forum.xda-developers.com/showthread.php?t=2481211
michal_alton said:
After connecting my one to computer for past 3 hours its started more frequently boot and showing Vodafone menu but still restarts shortly after. Vodafone logo shows on and lights on soft buttons starts flashing like 3 times and than it keeps rebooting. Does it mean anything?
Click to expand...
Click to collapse
That almost sounds like your POWER button is stuck!! Are you able to completely power off, and it stays off.

I think i know what it is. Power button stuck and keeps restarting device. Although i can feel pressing it, this is what it looks like.

nkk71 said:
Have you checked this: http://forum.xda-developers.com/showthread.php?t=2481211
That almost sounds like your POWER button is stuck!! Are you able to completely power off, and it stays off.
Click to expand...
Click to collapse
Didn't see your comment but this is exactly how it looks to me. I can't switch off phone and in bootloader it acts like i was pressing power button. Although it operates normally meaning that it can be pressed down. Arranged warranty repair with HTC and they are collecting phone tomorrow.

michal_alton said:
Didn't see your comment but this is exactly how it looks to me. I can't switch off phone and in bootloader it acts like i was pressing power button. Although it operates normally meaning that it can be pressed down. Arranged warranty repair with HTC and they are collecting phone tomorrow.
Click to expand...
Click to collapse
Good luck mate, but definitely sounds like the power button is stuck

It's been fixed under warranty by HTC. They replaced motherboard on mine HTC. So all good

[Q] Could anyone please confirm if it's totally bricked?...

Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.

Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.

KomuroXV said:
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Click to expand...
Click to collapse
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.

Seanie280672 said:
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
Click to expand...
Click to collapse
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Fain11 said:
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Click to expand...
Click to collapse
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.

KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
Click to expand...
Click to collapse
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again

Seanie280672 said:
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Click to expand...
Click to collapse
KomuroXV said:
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
If only I could find a way to the bootloader mode, I would be so happy.
q.q

KomuroXV said:
If only I could find a way to the bootloader mode, I would be so happy.
q.q
Click to expand...
Click to collapse
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.

KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN

Fain11 said:
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
Click to expand...
Click to collapse
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
nkk71 said:
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Click to expand...
Click to collapse
Oh... yes, I've heard about the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.

KomuroXV said:
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
Oh... yes, I've heard abot the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
Click to expand...
Click to collapse
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.

Seanie280672 said:
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Click to expand...
Click to collapse
Did just that, right at those two little spots,but now the trick's not working, even though it had before, only I'm not sure if it was flashing to the two-little-spots.
Phone was charged and off. I turned it on holding Power+ Volume Down, with the phone's two spots facing straight to the flashlight.
It went straight into the bootloop still.
Are you sure it is there, and not right in the front or back camera?

Is it bricked?
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.

hugof99 said:
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
Click to expand...
Click to collapse
Well, unlike your case, my phone was actually 99.9% clean since I fixed it with the RUU. I don't think there's a ROM related issue with these reboots my phone has now.
Problem: Turned phone off while it was doing something inside stock's Recovery. Now got caught in an infinite reboot because of that,

It is actually something like this.
http://www.youtube.com/watch?v=85HtJYcVAos
http://www.youtube.com/watch?v=rai4nCciKBg
http://www.youtube.com/watch?v=W5PCJYKaCrE
Just that mine is HTC One, and, well, besides from that screen it's also rebooting on his own every 8-10 seconds.

When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?

iElvis said:
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
Click to expand...
Click to collapse
Just as it sounds. I pressed down the power button to turn it off while Recovery was starting, and soon after that, the infinite bootloop started.
The RUU was 100% good, and I tested everything I could before trying to flash a ROM again.
But, just in case, it was this one:
http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/
Anyway, as I said, after I checked everything around the phone, I went to bootloader, clicked recovery by accident, and on reflex turned it off pressing down the power button.
Since then, there's been an infinite bootloop, rebooting every 8 to 10 seconds.
Sadly, and I guess it's because it was freshly flashed from a RUU, I can't access through ADB either.
q-q

Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684

iElvis said:
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I've been trying to do this for days on my own (couldn't get help) but I finally managed to install a Unbuntu and run the sudo ./revive.sh
[email protected]:~$
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ chmod +x revive.sh
[email protected]:~/Downloads$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
The phone is actually connected to an USB 2.0 port, rebooting on his own still, but connected.
It's not detecting it though.
:/

My One keep restarting and stuck at HTC screen

Hey guys,
So I have had my One more than a year, never root, never install any mod in it, just simple, daily use. It worked well till last night when some weird thing happened:
- At first, the Back, Home and HTC buttons keep flashing along with the screen. When I unlock my screen pass lock and go to the home screen, it showed a notification like "To restart the phone, keep pushing the power button for (x) second" with x is the count down number. After that, the phone is automatically rebooting, then the problem happen again.
- After a few times, I manage to shut it down properly then turn the phone up. As I notice, as long as I doing something with the phone such as calling somebody or checking facebook or simply sliding the home screen, thing is normal. But as I stopped using it, that weird notification pop up again
- The phone keep restarting after that, again and again. Sometime it boot successful, but when Im go to the home screen, the notification shows up and my phone restarts again. As I couldnt turn off my phone, it is drained and out of battery.
- This morning, I put the cable in and try to charge it, and My One now stuck at the first HTC logo screen then restarting and then stuck again. That looping process is drive me crazy. As I try to pull out the cable, the phone is not working (Obviously) since it is out of battery.
- As I hold down Power and Volume down, I can enter bootloader screen. I saw a "locked" banner and cannot navigate through the menu and can not press Fastboot or anything. After 2-3 seconds, the phone is shut down and keep looping.
Long story shot, can anybody tell me how to fix this. As I have a lot of pictures that havent been backed up, I really appreciate if I can keep everything without doing a factory reset. Oddly enough, I cant even do a factory reset since the bootloader is not working.
Please help.

Have you tried a factory reset?
On boot, bottom down n power will take u to fastboot.
You can do a factory reset from there.
HTC sync can save your stuff.
Sent from my HTC One_M8

mashk said:
Have you tried a factory reset?
On boot, bottom down n power will take u to fastboot.
You can do a factory reset from there.
HTC sync can save your stuff.
Sent from my HTC One_M8
Click to expand...
Click to collapse
As I mentioned above, I can hardly do anything from that fastboot screen. Up, down and power button is not working as I cannot navigate to recovery or factory reset. Even pushing power button wont do.
When I connect the phone to PC, nothing happen. It is because the phone is out of battery i suppose?
The problem is when I start to charge the phone, it will keep looping. But if I dont, the phone is death and I cant do anything.

I honestly dont know. I suspect you have
Fast boot selected under Settings>power.
You've got to try till you can get into fastboot otherwise send it for repairs.
Sent from my HTC One_M8

evelucife said:
Hey guys,
So I have had my One more than a year, never root, never install any mod in it, just simple, daily use. It worked well till last night when some weird thing happened:
- At first, the Back, Home and HTC buttons keep flashing along with the screen. When I unlock my screen pass lock and go to the home screen, it showed a notification like "To restart the phone, keep pushing the power button for (x) second" with x is the count down number. After that, the phone is automatically rebooting, then the problem happen again.
- After a few times, I manage to shut it down properly then turn the phone up. As I notice, as long as I doing something with the phone such as calling somebody or checking facebook or simply sliding the home screen, thing is normal. But as I stopped using it, that weird notification pop up again
- The phone keep restarting after that, again and again. Sometime it boot successful, but when Im go to the home screen, the notification shows up and my phone restarts again. As I couldnt turn off my phone, it is drained and out of battery.
- This morning, I put the cable in and try to charge it, and My One now stuck at the first HTC logo screen then restarting and then stuck again. That looping process is drive me crazy. As I try to pull out the cable, the phone is not working (Obviously) since it is out of battery.
- As I hold down Power and Volume down, I can enter bootloader screen. I saw a "locked" banner and cannot navigate through the menu and can not press Fastboot or anything. After 2-3 seconds, the phone is shut down and keep looping.
Long story shot, can anybody tell me how to fix this. As I have a lot of pictures that havent been backed up, I really appreciate if I can keep everything without doing a factory reset. Oddly enough, I cant even do a factory reset since the bootloader is not working.
Please help.
Click to expand...
Click to collapse
looks like an hardware defect, maybe your power button is stuck?

alray said:
looks like an hardware defect, maybe your power button is stuck?
Click to expand...
Click to collapse
I dont think so man. It seems working normal for me. But thanks anyway

evelucife said:
I dont think so man. It seems working normal for me. But thanks anyway
Click to expand...
Click to collapse
"To restart the phone, keep pushing the power button for (x) second" with x is the count down number.
Click to expand...
Click to collapse
Because this is exactly the message we usually get when holding the power button for more then 5 sec...
and that would explain the reboot issue
looks like the "power" key is always active
definitively sounds like an hardware issue imo
and your issue is even present in bootloader what confirm that this is an hardware defect.

alray said:
Because this is exactly the message we usually get when holding the power button for more then 5 sec...
and that would explain the reboot issue
looks like the "power" key is always active
definitively sounds like an hardware issue imo
and your issue is even present in bootloader what confirm that this is an hardware defect.
Click to expand...
Click to collapse
Yeah u has a point. Any idea how to fix that? Or I have to bring it to someone else to fix it.

evelucife said:
Yeah u has a point. Any idea how to fix that? Or I have to bring it to someone else to fix it.
Click to expand...
Click to collapse
You'll probably have to send it for repair. Better to contact HTC and see how much it will cost...

alray said:
You'll probably have to send it for repair. Better to contact HTC and see how much it will cost...
Click to expand...
Click to collapse
Thanks man. I will see if i can do.