Database Develop

htc one bootlop brick

My htc One is bricked and i dont know what to do.
One day it just randomly prompted that it was going to power down and after that its been stuck in the bootloop cycle.
it only powers on to bootloop cycle when connected to a charger or pc after a period of time. The charging LED has been does not show.
I tried to launch recovery but it reboots before completing the process; infact it only stays in the bootloader screen for 5 secs before it reboots.
I've tried to fastboot erase cache and i get the error too many links, as the phone reboots back into the loop. also to note that when i plug in the htc one into the pc it tries to install it (when its in fast boot right before it reboots) but it cant because it says its unplug. (Ive tried many different cord, i even got a brand new oem cable from another htc one at the AT&T store)
the phone is rooted/unlock with a trickdroid and has been over 2 months without a issue.
I fear that the phone is gone....please help
i would even be willing to open the phone since its not under warranty....

I had my phone boot looping a couple days ago although the issue was because it did not have a rom nor recovery installed. I managed to get out of the boot loop and into the bootloader by holding both the up and down volume keys with the power button until the phone shut down, you should see the home and back keys flash 7 or 8 times before the screen shuts down. IMMEDIATELY after your screen powers down, release the keys you are currently holding and press the down volume and the power key, with any luck this should get you to the bootloader screen.

Wozzie said:
I had my phone boot looping a couple days ago although the issue was because it did not have a rom nor recovery installed. I managed to get out of the boot loop and into the bootloader by holding both the up and down volume keys with the power button until the phone shut down, you should see the home and back keys flash 7 or 8 times before the screen shuts down. IMMEDIATELY after your screen powers down, release the keys you are currently holding and press the down volume and the power key, with any luck this should get you to the bootloader screen.
Click to expand...
Click to collapse
I've been in the bootloader menu plenty of times, the problem is the phone reboots in 5 sec regardless... so when I select fastboot might open up that menu or may not either way it reboots. Thanks for your responding... Im going to let it drain overnight and tinker with it in the morning

Dreadedfox said:
I've been in the bootloader menu plenty of times, the problem is the phone reboots in 5 sec regardless... so when I select fastboot might open up that menu or may not either way it reboots. Thanks for your responding... Im going to let it drain overnight and tinker with it in the morning
Click to expand...
Click to collapse
I do not know if this is the wisest idea or if it has been tried before but you could try interrutpting the reboot cycle by booting into ruu mode. Try
Code:
fastboot oem rebootRUU
The code should take less then a second to enter if you have it typed out and waiting.
Once you are in the RUU section just type this
Code:
fastboot reboot-bootloader
With any luck you might be able to break the bootloop

Dreadedfox said:
My htc One is bricked and i dont know what to do.
One day it just randomly prompted that it was going to power down and after that its been stuck in the bootloop cycle.
it only powers on to bootloop cycle when connected to a charger or pc after a period of time. The charging LED has been does not show.
I tried to launch recovery but it reboots before completing the process; infact it only stays in the bootloader screen for 5 secs before it reboots.
I've tried to fastboot erase cache and i get the error too many links, as the phone reboots back into the loop. also to note that when i plug in the htc one into the pc it tries to install it (when its in fast boot right before it reboots) but it cant because it says its unplug. (Ive tried many different cord, i even got a brand new oem cable from another htc one at the AT&T store)
the phone is rooted/unlock with a trickdroid and has been over 2 months without a issue.
I fear that the phone is gone....please help
i would even be willing to open the phone since its not under warranty....
Click to expand...
Click to collapse
so you cant get to bootloader?

zaphodbeeb said:
so you cant get to bootloader?
Click to expand...
Click to collapse
Sorry for being unclear. I can get in the bootloader but the boot loop cycle is interrupting any process I begin
I can enter ruu with a custom rom. I'm currently running trickdriod

Wozzie said:
I do not know if this is the wisest idea or if it has been tried before but you could try interrutpting the reboot cycle by booting into ruu mode. Try
Code:
fastboot oem rebootRUU
The code should take less then a second to enter if you have it typed out and waiting.
Once you are in the RUU section just type this
Code:
fastboot reboot-bootloader
With any luck you might be able to break the bootloop
Click to expand...
Click to collapse
I did this and it didnt break the bootloop cycle but it did go into ruu mode before rebooting and once it rebooted it showed the trickdriod splash screen which it hasnt before and the bottom keys flashed a few times.... I tried getvar... and heres the info
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3448mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.273s

Just a few questions, can you get into fastboot at all? can you lock your bootloader using fastboot and then run a stock RUU.exe while your phones in fastboot?

TaintedCross said:
Just a few questions, can you get into fastboot at all? can you lock your bootloader using fastboot and then run a stock RUU.exe while your phones in fastboot?
Click to expand...
Click to collapse
Yes i can get into fastboot for a few seconds.... I cant lock my boot bootloader it always fail, im guessing due to the phone rebooting before it is done

< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.198s
ok I relocked bootloader but its still reboot cycle now going straight into bootloader....

Can I unroot from fastboot?

I Can Only Access Fast Boot And RECOVERY. Is there any way to unroot and and put my phone back in stock mode from here? Stock recovery. I don't care if I can't install the stock ROM. I just need this area to be stock so i can send the phone to warranty
Sent from my myTouch 4G using xda app-developers app

dpshptl said:
I Can Only Access Fast Boot And RECOVERY. Is there any way to unroot and and put my phone back in stock mode from here? Stock recovery. I don't care if I can't install the stock ROM. I just need this area to be stock so i can send the phone to warranty
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Why do you only need a stock recovery to send it to warranty?
For warranty, as far as I can tell, you need a LOCKED bootloader (not RELOCKED), and no TAMPERED, and stock firmware and ROM.
You could check out my guide, on how to return 100% back to stock.

nkk71 said:
Why do you only need a stock recovery to send it to warranty?
For warranty, as far as I can tell, you need a LOCKED bootloader (not RELOCKED), and no TAMPERED, and stock firmware and ROM.
You could check out my guide, on how to return 100% back to stock.
Click to expand...
Click to collapse
The problem is my phone was stock and running kitkat just a few days ago. Then one day i used it and the screen flashed a few times the buttons on the bottom flashed a few times. Then it reboot itself and got stuck. I could never go back from there. I tried a few diff things nothing worked. So I ended up rooting and installing a custom ROM. All was fine but when I reboot it would get stuck again. Sometimes it would auto reboot and get stuck. The only thing I could do is wipe and reinstall a ROM and it would be fine as long as it did not reboot.
So i would like to undo my root and return my phone. The only problem is I can only access the bootloader.
Here is the fastboot getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

dpshptl said:
The problem is my phone was stock and running kitkat just a few days ago. Then one day i used it and the screen flashed a few times the buttons on the bottom flashed a few times. Then it reboot itself and got stuck. I could never go back from there. I tried a few diff things nothing worked. So I ended up rooting and installing a custom ROM. All was fine but when I reboot it would get stuck again. Sometimes it would auto reboot and get stuck. The only thing I could do is wipe and reinstall a ROM and it would be fine as long as it did not reboot.
So i would like to undo my root and return my phone. The only problem is I can only access the bootloader.
Here is the fastboot getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
I have already explained to you their is no T-mobile RUU for your version
all you can do is flash the GURU Reset and install stock recovery and take the OTA and send your phone back

If you can get s off you can go back to stock t mobile. I did it with my o2-UK phone. But you def need s off first
Sent from my HTC One using xda app-developers app

The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app

Have you tried using firewater to get s off? If it doesn't work, as mentioned above, guru reset only option
Sent from my HTC One using xda app-developers app

dpshptl said:
The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
no the Guru reset does not require s-off
you flash it like a rom and choose to install stock recovery during install
---------- Post added at 06:32 PM ---------- Previous post was at 06:27 PM ----------
dpshptl said:
The problem with this is it requires s-off. From my understanding I can't gain s-off from where my phone is stuck. Correct me if I'm wrong.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Read this page very carefully you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset
http://www.htc1guru.com/downloads/stock-rom-downloads/

No the guru reset does not require s off. It will not be stock t mobile though as well
Sent from my HTC One using xda app-developers app

Now I have a new problem. The phone boot up somehow and went to the lock screen. I cant do anything there though. The screen is not responsive. Vol up and down turns the vol up and down. Holding down the power button does not reboot or turn off the phone. A message says hold for 3, 2, 1 sec and the phone will reboot. But nothing happens. I have been holding the power button down for mins at a time while pushing and not pushing the vol buttons and the home buttons.

clsA said:
I have already explained to you their is no T-mobile RUU for your version
all you can do is flash the GURU Reset and install stock recovery and take the OTA and send your phone back
Click to expand...
Click to collapse
But how is he going to get LOCKED not relocked?
dpshptl said:
Now I have a new problem. The phone boot up somehow and went to the lock screen. I cant do anything there though. The screen is not responsive. Vol up and down turns the vol up and down. Holding down the power button does not reboot or turn off the phone. A message says hold for 3, 2, 1 sec and the phone will reboot. But nothing happens. I have been holding the power button down for mins at a time while pushing and not pushing the vol buttons and the home buttons.
Click to expand...
Click to collapse
you flashed a 1.xx rom on a 2.xx+ firmware, and @clsA mentioned in his post: "you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset"

I tried the guru reset but no luck. The process finished with no errors but when bootloader rebooted the phone was still in tampered and unlocked mode.
What is the old t-mobile reset method? I have an OTG cable and a mouse just need instructions or a link.

dpshptl said:
I tried the guru reset but no luck. The process finished with no errors but when bootloader rebooted the phone was still in tampered and unlocked mode.
What is the old t-mobile reset method? I have an OTG cable and a mouse just need instructions or a link.
Click to expand...
Click to collapse
The guru reset was to get your phone working again .. you now need to work on getting s-off so you can remove the tampered and lock the phone to return it

clsA said:
The guru reset was to get your phone working again .. you now need to work on getting s-off so you can remove the tampered and lock the phone to return it
Click to expand...
Click to collapse
All methods to get s_off requires the phone to boot up all the way. How do I get s_off from bootloader

dpshptl said:
All methods to get s_off requires the phone to boot up all the way. How do I get s_off from bootloader
Click to expand...
Click to collapse
install the guru reset .. your phone should boot up

The problem I'm having is even if I hey the phone back up. When it needs to reboot again it will get stuck at the splash screen and I'm back to where I started. Whenever I need to reboot to finish a process the phone hangs and I'm screwed. I have do so many things and wiped the pogo few so many times nothing helps. All install and updates and fast boot commands and everything works fine until the reboot.

dpshptl said:
The problem I'm having is even if I hey the phone back up. When it needs to reboot again it will get stuck at the splash screen and I'm back to where I started. Whenever I need to reboot to finish a process the phone hangs and I'm screwed. I have do so many things and wiped the pogo few so many times nothing helps. All install and updates and fast boot commands and everything works fine until the reboot.
Click to expand...
Click to collapse
I'm out of ideas maybe @nkk71 can think of something else
Did you flash the Guru reset and install stock recovery and then do a factory reset / wipe caches?

nkk71 said:
But how is he going to get LOCKED not relocked?
you flashed a 1.xx rom on a 2.xx+ firmware, and @clsA mentioned in his post: "you will need a usb otg cable to use a mouse to control you phone if you use the old t-mobile reset"
Click to expand...
Click to collapse
clsA said:
I'm out of ideas maybe @nkk71 can think of something else
Did you flash the Guru reset and install stock recovery and then do a factory reset / wipe caches?
Click to expand...
Click to collapse
Yeah guru flashed without any problems. Then auto rebooted into bootloader, where it was still tampered and unlocked. I went into recovery but it just kept looping to boatloader. So i flashed TWRP again and wiped everything and here I am. I think its some major hardware problem because whenever the phone reboots from anywhere on the phone, it starts looping and hanging. The phone has been wiped clean so many times and had everything installed from a jump drive. So I cant imagine something being left on there that is causing the problem.

Can someone give me a link to the stock RUU. I'm confused between all of them. The phone seems to be stable now. I reboot it several times and it works. But I do need to use a mouse cuz the touch screen does not work.

Their is no RUU
You need to start working on getting s_off
Sent from my HTC One_M8 using Tapatalk

[Q] HTC One M7 (AT&T-US) Stuck in Boot Loop

My AT&T HTC One is stuck in a continuous boot loop. It flashes to the HTC splash screen for roughly 7 seconds, turns off for roughly 5 seconds, then on again. It will do this until the battery is fully depleted. Plugging the phone into my PC yields no results as the boot loop triggers a "device is not plugged in" error message over and over on my windows 7 PC. I am able to access the recovery mode holding down the power button and volume down rocker but once in recovery mode the phone promptly reboots itself back into the continuous boot loop, I have a window of a couple of seconds to navigate options in recovery mode. Stranger still is that my up and down volume buttons seem to be less responsive, sometimes I am only able to move up, other times only down. I can select recovery if I am fast enough, which takes me to the HTC splash screen with the text "Entering recovery..." however the phone then reboots back into the boot loop.
My recovery menu:
M7-UL PVT SHIP S-ON RH
HBOOT-1.55.0000
OPEN DSP-v31.120.274.0617
OS 3.17.502.3
eMMC Boot 2048 MB
I am running stock odexed 4.3 with the Sense skin
Drivers cannot be installed on my PC due to the continuous resetting and navigating the recovery menu is borderline impossible.
After being severely annoyed by the bloatware that comes with the OTA firmware updates from AT&T I rooted my phone and installed the ARHD custom rom. It has worked flawlessly for about 3 months until yesterday 5/3/2014 the phone began the boot loop while it was sitting on my desk idle for about an hour. Plugging the phone into the charger yields no visible changes either (the charging indicator light does not turn on). Last night the phone boot-looped itself into a depleted battery. I plugged it in and after 5 minutes of charging I was able to get it to boot so I chose to boot it into safe mode. I had to get to bed and was unable to troubleshoot the phone further so I left the phone in safe mode, only to find it in the boot loop around 5-6:00 this morning. I am going to let the battery drain again and try to do a cache wipe once I can get the thing into safe mode. Any help on this issue would be much appreciated.

svenell said:
My recovery menu:
M7-UL PVT SHIP S-ON RH
HBOOT-1.55.0000
OPEN DSP-v31.120.274.0617
OS 3.17.502.3
eMMC Boot 2048 MB
I am running the HTC Sense skin of Android Revolution HD 4.3
Drivers cannot be installed on my PC due to the continuous resetting and navigating the recovery menu is borderline impossible.
Click to expand...
Click to collapse
First question ARHD 4.3 ?? (Sense Edition)? link please
second, let's start with the basics:
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)
how stable is bootloader? all good?
If yes, copy/paste a "fastboot getvar all" (excluding IMEI and s/n)

@nkk71 Thanks for the prompt response!
Out of left field my phone left the boot loop after 4 hours and I was able to get it to boot normal. I entered the recovery menu and was able to get into CWMR 6.0.4.3 where I wiped the cache partition. So far the phone seems stable. Any measures I need to take to prevent this problem from occurring in the future?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ~~~~~~~~~~
(bootloader) imei: ~~~~~~~~~~
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
I also misspoke, I am running a stock odexed 4.3 with Sense.

svenell said:
@nkk71 Thanks for the prompt response!
Out of left field my phone left the boot loop after 4 hours and I was able to get it to boot normal. I entered the recovery menu and was able to get into CWMR 6.0.4.3 where I wiped the cache partition. So far the phone seems stable. Any measures I need to take to prevent this problem from occurring in the future?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
I also misspoke, I am running a stock odexed 4.3 with Sense.
Click to expand...
Click to collapse
well that looks all good... could it be some debris in the phone's USB port? or the charger and/or cable is going bad? or even a bad power button?
(just a couple of guesses, nothing concrete... but worth checking anyway)

nkk71 said:
well that looks all good... could it be some debris in the phone's USB port? or the charger and/or cable is going bad? or even a bad power button?
(just a couple of guesses, nothing concrete... but worth checking anyway)
Click to expand...
Click to collapse
Thanks again for the help nkk71. So far so good, the USB port seems to be clear and functioning, and I did a key test in the recovery menu and the power button seems responsive to my clicks.
I am thinking about updating to the ARHD 53.0 (4.4.2+ HTC Sense 5.5) In hopes that it might fix any issues that could be going on causing my phone to be prone to boot loops. I just need to do some research before I update to make sure its safe.

svenell said:
Thanks again for the help nkk71. So far so good, the USB port seems to be clear and functioning, and I did a key test in the recovery menu and the power button seems responsive to my clicks.
I am thinking about updating to the ARHD 53.0 (4.4.2+ HTC Sense 5.5) In hopes that it might fix any issues that could be going on causing my phone to be prone to boot loops. I just need to do some research before I update to make sure its safe.
Click to expand...
Click to collapse
Sure no problem.
But, if you're going for a 4.4 ROM, then you need to get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
CWM is not fully compatible with 4.4 ROMs yet..... just a heads up

Thanks for the heads up! I guess this is considered SOLVED, however it was sheer luck that the boot loop stopped and I was able to get into the phone. Thanks again for the help

Weird black screen problem

Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line

Poesini said:
Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Click to expand...
Click to collapse
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

Poesini said:
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?

Poesini said:
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Click to expand...
Click to collapse
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen

Poesini said:
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Click to expand...
Click to collapse
Flash twrp 2.6.3.3 newer versions of twrp can be temperamental and probably why your having trouble flashing roms
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 07:26 PM ---------- Previous post was at 07:07 PM ----------
Try the bright light trick again but this time power off the device. Hold the sensors close to the light
Hold volume up and down +power for 60 secs the phone will bootloop while your holding the buttons. Hopefully that will be enough to reset the sensor. :fingers-crossed:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[Q] HTC One does not charge while in OS. Kernal or Firmware??

So the full story is my HTC ONE m7 has had this happen about 3 times now. The first time it happened the battery ran to 0% and I fixed it using a flashlight, Power + Vol down while plugged in. The second time I was playing a game and the phone seemed to overheat and shut itself down, that was fixed with Power + Vol down while plugged in. This time my son was watching videos and the phone went to 0% again and shutdown. I charged it while off to 100% and turned the phone on but now it doesn't charge again while powered on or in 'OS'. I've had this phone for a year and a half, love the phone but this issue drives me crazy and a lot of people seem to have the same problem but there is no apparent fix.
I've tried:
Power + Vol up and down for 2+ minutes
Power + Vol down with/or without flashlight
Power + Vol up
Safemode/ reboot
factory reset (lost everything)
HTC support (useless)
All this was done while completely stock. So I did this next:
Rooted/Bootloader Team Win 2.8.3.0 twrp then totally wiped everything even original 'OS' without a backup first 'Dumb' on my part... so I eventually loaded the twrp recovery 2.8.3.0 and flashed ROM HD revolution 84.
What I really don't get is that there is no way it is hardware related because while I'm in Bootloader or Recovery the phone charges fine and communicates through usb (PC see's it with access to the internal storage) totally fine. But as soon as I'm in the 'OS' I can't use the usb port at all. PC doesn't see the phone (no sound when plugged in) and doesn't charge even while plugged into AC adapter. My question is could it be a corrupt kernal or firmware?? Whatever it is between the bootloader and OS load the phone completely disables the usb port. Possible Fix???

Roddyrex said:
So the full story is my HTC ONE m7 has had this happen about 3 times now. The first time it happened the battery ran to 0% and I fixed it using a flashlight, Power + Vol down while plugged in. The second time I was playing a game and the phone seemed to overheat and shut itself down, that was fixed with Power + Vol down while plugged in. This time my son was watching videos and the phone went to 0% again and shutdown. I charged it while off to 100% and turned the phone on but now it doesn't charge again while powered on or in 'OS'. I've had this phone for a year and a half, love the phone but this issue drives me crazy and a lot of people seem to have the same problem but there is no apparent fix.
I've tried:
Power + Vol up and down for 2+ minutes
Power + Vol down with/or without flashlight
Power + Vol up
Safemode/ reboot
factory reset (lost everything)
HTC support (useless)
All this was done while completely stock. So I did this next:
Rooted/Bootloader Team Win 2.8.3.0 twrp then totally wiped everything even original 'OS' without a backup first 'Dumb' on my part... so I eventually loaded the twrp recovery 2.8.3.0 and flashed ROM HD revolution 84.
What I really don't get is that there is no way it is hardware related because while I'm in Bootloader or Recovery the phone charges fine and communicates through usb (PC see's it with access to the internal storage) totally fine. But as soon as I'm in the 'OS' I can't use the usb port at all. PC doesn't see the phone (no sound when plugged in) and doesn't charge even while plugged into AC adapter. My question is could it be a corrupt kernal or firmware?? Whatever it is between the bootloader and OS load the phone completely disables the usb port. Possible Fix???
Click to expand...
Click to collapse
You are correct the next logical thing to try is either the firmware or kernel (which is included with the stock firmware). See if you can find the stock firmware for your version and give it a try. If stock kernel doesn't help then try a custom kernel, you can find them in the Development Section.

So to update my firmware I would need to be S-OFF and I'm not sure how to do that when I have no USB/ADB available in windows with my device at the home screen ie. rumrunner. Is there a way to get S-off from bootloader or Fastboot?

Here is my phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4104mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s