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.
:/
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
KomuroXV said:
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
Click to expand...
Click to collapse
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
LibertyMarine said:
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
Click to expand...
Click to collapse
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
stovie_steve said:
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
Click to expand...
Click to collapse
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
KomuroXV said:
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
Click to expand...
Click to collapse
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
clsA said:
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
Click to expand...
Click to collapse
I've tried both.
Here's another one anyways.
https://www.youtube.com/watch?v=1zyA6XGFEpo&list=UUzlEfhRw_dyaJ7aAFpWC7-A
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
LibertyMarine said:
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
Click to expand...
Click to collapse
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
KomuroXV said:
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
Click to expand...
Click to collapse
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
nkk71 said:
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
Click to expand...
Click to collapse
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
@KomuroXV but what nkk suggested is a good idea, but just be very very gentle. I f#cked up my powerbutton pressing it too much. Luckily HTC believed my (altered) story and I got a replacement.
What you can try is to just go with a paper edge between the power button and the Magnesium surrounding then try to much it upwards and downwards, this may help "unstucking" your powerbutton if that's even the case.
I'm gonna test the with my phone how long it takes to reboot if I hold down the power button (will post again in a few min). If it's about the same as shown in your vid, it might really be a stuck power button.
LibertyMarine said:
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
Click to expand...
Click to collapse
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
nkk71 said:
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
Click to expand...
Click to collapse
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
LibertyMarine said:
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
Click to expand...
Click to collapse
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
KomuroXV said:
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
Click to expand...
Click to collapse
I'm gonna sleep now, will answer tomorrow evening. I have an important meeting tomorrow.
KomuroXV said:
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
Click to expand...
Click to collapse
i dont see how flashing / interrupting flashing a recovery could cause that, the recovery is in a different partition than bootloader, so even if you were unable to enter recovery (due to bad flash), you should be able to get to bootloader
but when you say it got stock at 40%, i'm seriously surprised, as flashing a recovery literally takes 2 seconds:
Code:
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
maybe try covering the light sensors completely, and hold voldown, when it reboots again.... maybe (though i doubt it), it will forego the simulated battery pull
KomuroXV said:
[...]
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
[...]
Click to expand...
Click to collapse
How did you turn it off? Did you press the power button very hard/strong?
Did you flash the recovery with fastboot
or did you flash your recovery within rebootRUU and with an firmware.zip ?
Because the method via fastboot (fastboot flash recovery recovery.img) doesn't indicate a percentage. And btw. I had issues with this method too and interrupted the installation several times, didn't cause any problems. To the theory that your phone wants to continue flashing recovery is not true. This isn't possible since your phone should boot correctly and if it wanted to boot into recovery you could prevent that with pressing the vol. down button. That didn't work in your case so I think that this theory doesn't work out.
If you flashed it with a firmware zip, was there another hboot.img that you installed too without knowing/wanting? Because interrupting a hboot flash will brick your device. but if that happend you wouldn't be able to boot your phone. So I think this isn't true either.
i have exactly the same problem, is very strange beacause i was updating my ROM