Database Develop

[Q] Soft-bricked, some help, please.

Hello, today I've bought a used HTC One. It's soft bricked (I guess), I don't know what was done with it before, but previous owner said it was running official KitKat, I don't know if that's true.
Phone's bootlooping but I can get into bootloader, fastboot. When I try to access recovery it says entering recovery mode... and then reboots. Same happens if I choose Factory reset from bootloader menu.
I can't get this phone working with ADB. I've installed all drivers a few times. When I connect phone to computer I can hear Windows USB input sound and phone says "FASTBOOT USB" but adb is not detecting it. When I type "adb devices" I get no devices. I guess that's because USB debugging is off and I can't enable it since phone is in bootloop.
What I could do with it?
Bootloader information:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMc-boot 2048MB
Oct 17 2013, 23:06:14.0
I would appreciate any help, thank you.

Jst check out for ur mobile's official stock rom & install it

martis347 said:
Hello, today I've bought a used HTC One. It's soft bricked (I guess), I don't know what was done with it before, but previous owner said it was running official KitKat, I don't know if that's true.
Phone's bootlooping but I can get into bootloader, fastboot. When I try to access recovery it says entering recovery mode... and then reboots. Same happens if I choose Factory reset from bootloader menu.
I can't get this phone working with ADB. I've installed all drivers a few times. When I connect phone to computer I can hear Windows USB input sound and phone says "FASTBOOT USB" but adb is not detecting it. When I type "adb devices" I get no devices. I guess that's because USB debugging is off and I can't enable it since phone is in bootloop.
What I could do with it?
Bootloader information:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMc-boot 2048MB
Oct 17 2013, 23:06:14.0
I would appreciate any help, thank you.
Click to expand...
Click to collapse
When you see fastboot usb in the bootloader, your in Fastboot mode. adb will not work. Type fastboot devices.
Sent from my HTC One using XDA Premium HD app

Can you post an output of fastboot getvar all (remove imei/sn) ?

Now how I flash a new rom with only fastboot?
Maybe I should return to stock?
Edit: Can I flash RUU if I relock bootloader?
From image version: 3.62.401.1
To image version: 1.28.401.7
I've found somewhere, that it's okay to flash with diffrent image version, some guy in a video said, that you must have same image version numbers, so I don't know.

version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main:3.62.401.1
version-misc: PVT SHIP S-on
serialno: it's ok
imei: (it's ok, lots of numbers)
meid: 0000000000000000000
product:m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery...
voltage...
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0

martis347 said:
Now how I flash a new rom with only fastboot?
Maybe I should return to stock?
Edit: Can I flash RUU if I relock bootloader?
From image version: 3.62.401.1
To image version: 1.28.401.7
I've found somewhere, that it's okay to flash with diffrent image version, some guy in a video said, that you must have same image version numbers, so I don't know.
Click to expand...
Click to collapse
No, you can't as you are S-ON. You can downgrade only if you are S-OFF.
Please try the following, even if you have tried it and paste your command prompt output.
- Connect the phone in fastboot mode.
- Downlaod stock recovery: http://d-h.st/WJ8
fastboot flash recovery stock_3.62.401.1.img
fastboot erase cache
fastboot reboot-bootloader
Try to enter recovery, you should see a triangle with android or a red exclamantion mark. Post back if your device can still NOT enter stock recovery
May have to try flashing couple times

Flashed twice, when I choose recovery in bootloader it only reboots and starts bootlooping.
I've uploaded log picture, it's faster than rewriting.

martis347 said:
Flashed twice, when I choose recovery in bootloader it only reboots and starts bootlooping.
I've uploaded log picture, it's faster than rewriting.
Click to expand...
Click to collapse
Interesting. You are having the same issue as another user right now. Try this please:
Download http://files.trjlive.com/android/htc/one/firmware/firmware_3.62.401.1.zip
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware_3.62.401.1.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware_3.62.401.1.zip and wait for process to complete
Type: fastboot reboot-bootloader
Type: fastboot erase cache
Please select Bootloader and then select recovery to enter stock recovery. Post back your result.

I should flash, firstly reboot bootloader and then erase cache? Because in previous post order was: flash,erase cache, reboot, as far as I know you have to clear cache and then reboot. Or it doesn't matter?

Please follow as written in my instructions.

I've done everything like you said.
Type: fastboot oem lock (if your device is not relocked yet) (Phone rebooted. Then in bootloader it said relocked)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware_3.62.401.1.zip and wait for process to complete I got error both times. While flashing first time I renamed "firmware_3.62.401.1.zip" to "firmware.zip" When flashing second time I renamed it back to "firmware_3.62.401.1.zip"
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware_3.62.401.1.zip and wait for process to complete
Type: fastboot reboot-bootloader
Type: fastboot erase cache
Now phone is same as it was. No recovery, when I'm trying to access it it just reboots and keeps bootlooping.

Sorry looks like the firmware was not signed., yoru fastboot indicates the failure. Please retry with: http://xda7.androidrevolution.nl/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip
I checked it is signed.

Now somehow phone does not detect computer when I try plugging in. I mean when I connect it to pc, it's not responding. If i plug it to a wall charger it says Fastboot AC, if i plug it to computer it says only FASTBOOT. Didn't occur before...

Restart computer??

SaHiLzZ said:
Restart computer??
Click to expand...
Click to collapse
I've tried a different computer, restarted mine, nothing changes.
I think phone's charging animation (while off) has changed.

Okay, I got it working.(Haven't tried a port where my mouse is connected)
Flashed firmware like you said, from second try everything went okay.
Tried booting to recovery, still no change. Just bootloops...

damn .. sucks if the official recovery is failing to boot as well. dont have any other suggestions.

SaHiLzZ said:
damn .. sucks if the official recovery is failing to boot as well. dont have any other suggestions.
Click to expand...
Click to collapse
Can't I flash a ROM through FASTBOOT?
Or is there any chance to use RUU?

There is no RUU For 3.62.401.1 or higher. As you are S-ON, you can NOT flash the lower version RUU. You should pray for the day someone releases the RUU for 3.62.401.x or higher!
I am intentionally NOT suggesting you to run the 4.19.401.8 as that will most likely not help and if a month later someone releases the 3.62.401.x RUU, you wont be able to run it. Staying at a lowest possible version will help your odds, however small they are right now.

[Q] AT&T HTC One M7 soft-bricked. Fastboot works, can't boot to recovery [Concluded]

[Q] AT&T HTC One M7 soft-bricked. Fastboot works, can't boot to recovery [Concluded]
Wondering if I can get somebody to weigh in on this one. Trying to help a friend of a friend out--I don't know the back story of what happened to this, but sounded like a 'bricked his phone doing dangerous things without enough knowledge' kind of situation.
The phone is stuck in a boot loop, just the HTC wordmark on a white background. You can enter the bootloader just fine, and fastboot can read and send commands just fine, flash recovery just fine, etc. The device cannot, however, enter recovery mode. It just says "entering recovery..." at the top, with the same HTC wordmark and white background. It displays for 30 seconds, then the screen goes black for 4-5 seconds, then back to the HTC logo.
Some info about the phone:
AT&T HTC One M7
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: [redacted]
imei: [redacted]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3838mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Things I have tried already:
The first thing I did was I re-locked the bootloader and flashed the RUU exe, thinking that might be the quickest fix. The exe took the expected length of time and said it was successful, and rebooted the phone.
Still looping.
I then got the unlock token, unlocked the bootloader again, erased the cache, and fastboot flashed CWM recovery-clockwork-6.0.4.3-m7att.img - Attempted to reboot to recovery.
Still looping.
Cleared the cache, flashed openrecovery-twrp-2.7.1.1-m7.img - Attempted to reboot to recovery.
Still looping.
What's Next?
So that's about where I am now, I have functional bootloader and fastboot, but something is corrupted and I just absolutely can't get into recovery no matter what I try. I really thought the RUU would be a simple way to fix it, and was surprised when it didn't work.
From the reading I've done it sounds like there's some sort of emmc partition corruption possibly? Am I going in the right direction? I did post the fastboot getvar all results above--perhaps that can tip somebody off? I don't know quite enough to be able to spot trouble there at a glance, unfortunately.
I don't personally have a lot invested in getting this running, its owner already replaced it and I'm just doing it for the fun and challenge of the learning experience. But I may be out of my depth at this point, I've exhausted my barely-passable knowledge when it comes to this stuff.
Thanks for any comments or guidance you can provide!
Thanks to all for your help. I've come to believe the issues were hardware related, and have returned the phone.

matt314159 said:
Wondering if I can get somebody to weigh in on this one. Trying to help a friend of a friend out--I don't know the back story of what happened to this, but sounded like a 'bricked his phone doing dangerous things without enough knowledge' kind of situation.
The phone is stuck in a boot loop, just the HTC wordmark on a white background. You can enter the bootloader just fine, and fastboot can read and send commands just fine, flash recovery just fine, etc. The device cannot, however, enter recovery mode. It just says "entering recovery..." at the top, with the same HTC wordmark and white background. It displays for 30 seconds, then the screen goes black for 4-5 seconds, then back to the HTC logo.
Some info about the phone:
AT&T HTC One M7
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: [redacted]
imei: [redacted]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3838mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Things I have tried already:
The first thing I did was I re-locked the bootloader and flashed the RUU exe, thinking that might be the quickest fix. The exe took the expected length of time and said it was successful, and rebooted the phone.
Still looping.
I then got the unlock token, unlocked the bootloader again, erased the cache, and fastboot flashed CWM recovery-clockwork-6.0.4.3-m7att.img - Attempted to reboot to recovery.
Still looping.
Cleared the cache, flashed openrecovery-twrp-2.7.1.1-m7.img - Attempted to reboot to recovery.
Still looping.
What's Next?
So that's about where I am now, I have functional bootloader and fastboot, but something is corrupted and I just absolutely can't get into recovery no matter what I try. I really thought the RUU would be a simple way to fix it, and was surprised when it didn't work.
From the reading I've done it sounds like there's some sort of emmc partition corruption possibly? Am I going in the right direction? I did post the fastboot getvar all results above--perhaps that can tip somebody off? I don't know quite enough to be able to spot trouble there at a glance, unfortunately.
I don't personally have a lot invested in getting this running, its owner already replaced it and I'm just doing it for the fun and challenge of the learning experience. But I may be out of my depth at this point, I've exhausted my barely-passable knowledge when it comes to this stuff.
Thanks for any comments or guidance you can provide!
Click to expand...
Click to collapse
Try to download TWRP 2.6.3.3 from here http://techerrata.com/browse/twrp2/m7 . When it has downloaded put it in your fastboot folder, plug your phone into your computer, open a command window, and type "fastboot devices" to make sure it recognizes your phone. If it doesn't you will need the drivers, if it does recognize it type "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" . That is the same file and procedure I just used a week ago, hope it helps you.

chuckwago88 said:
Try to download TWRP 2.6.3.3 from here http://techerrata.com/browse/twrp2/m7 . When it has downloaded put it in your fastboot folder, plug your phone into your computer, open a command window, and type "fastboot devices" to make sure it recognizes your phone. If it doesn't you will need the drivers, if it does recognize it type "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" . That is the same file and procedure I just used a week ago, hope it helps you.
Click to expand...
Click to collapse
Thanks for the suggestion, but it's still no joy: TWRP 2.6.3.3 acts the same as TWRP 2.7.1.1 and CWM 6.0.4.3
I'm starting to think this thing is toast.

matt314159 said:
Thanks for the suggestion, but it's still no joy: TWRP 2.6.3.3 acts the same as TWRP 2.7.1.1 and CWM 6.0.4.3
I'm starting to think this thing is toast.
Click to expand...
Click to collapse
I noticed that you have 3.17.502.3 firmware, you might try to flash this RUU 4.18.502.7 it is a higher version and might correct what I suspect is a mismatch between your version and the hboot. If this is successful, you might think about this AT&T 5.12.502.2 Guru Reset. Read the entire OP for both, it might give you some insight.

Hmm... With this RUU, I get as far as "Updating 1/5 Checking headers" at 5% and never any further. Thought I might just need to be more patient, so I left it through three episodes of Trailer Park Boys season 8, and a subsequent afternoon nap before powering off the handset and killing the windows process. Tried it again and it seems to be doing the same thing. The MD5 matched so I don't think it was a bad download, so I wonder if there are any workarounds.
I'm running windows 7 x64, have the proper drivers installed, HTC Sync has been removed, and I've used this PC successfully on another HTC One when I needed to get it back to factory stock to send in for warranty work just a couple of weeks ago. So I'm pretty sure it's nothing to do with my setup...

Can you find the same firmware (or extract from ota) and flash it?

matt314159 said:
Hmm... With this RUU, I get as far as "Updating 1/5 Checking headers" at 5% and never any further. Thought I might just need to be more patient, so I left it through three episodes of Trailer Park Boys season 8, and a subsequent afternoon nap before powering off the handset and killing the windows process. Tried it again and it seems to be doing the same thing. The MD5 matched so I don't think it was a bad download, so I wonder if there are any workarounds.
I'm running windows 7 x64, have the proper drivers installed, HTC Sync has been removed, and I've used this PC successfully on another HTC One when I needed to get it back to factory stock to send in for warranty work just a couple of weeks ago. So I'm pretty sure it's nothing to do with my setup...
Click to expand...
Click to collapse
Those 4.xx.502 RUU are crap...
Are you sure the 3.x.502 RUU completed ? I have never seen a phone bootloop after flashing that RUU.

clsA said:
Are you sure the 3.x.502 RUU completed ? I have never seen a phone bootloop after flashing that RUU.
Click to expand...
Click to collapse
Fairly sure, anyway? It takes the expected length of time (about 10 minutes), the progress bars march through their steps on the computer screen and phone screen, and the RUU exe congratulates me and says it's going to reboot the phone now when it's finished.
Can I try fastboot flashing a zip RUU, or does it require S-Off for that?

matt314159 said:
Fairly sure, anyway? It takes the expected length of time (about 10 minutes), the progress bars march through their steps on the computer screen and phone screen, and the RUU exe congratulates me and says it's going to reboot the phone now when it's finished.
Can I try fastboot flashing a zip RUU, or does it require S-Off for that?
Click to expand...
Click to collapse
it's no different ..if the EXE RUU worked and your still in bootloop you have a corrupt partition and will need expert advice. Maybe @nkk71 will have some time to help you

clsA said:
it's no different ..if the EXE RUU worked and your still in bootloop you have a corrupt partition and will need expert advice. Maybe @nkk71 will have some time to help you
Click to expand...
Click to collapse
Okay, thanks. I'm going to be taking this back to my colleague at work tomorrow, so I probably don't want nkk71 to spend much time on it unless he thinks it's something quick I can do tonight to get it running again.
Just on a lark, I also flashed twrp-recovery-2.7-m7-nobcb.img from This thread.--no change. Although my symptoms were different, it sounded like it might be worth a shot, but no dice.

matt314159 said:
Okay, thanks. I'm going to be taking this back to my colleague at work tomorrow, so I probably don't want nkk71 to spend much time on it unless he thinks it's something quick I can do tonight to get it running again.
Just on a lark, I also flashed twrp-recovery-2.7-m7-nobcb.img from This thread.--no change. Although my symptoms were different, it sounded like it might be worth a shot, but no dice.
Click to expand...
Click to collapse
@clsA is quite right about those 4.xx RUUs, they do work, but are very sensitive (for lack of a better word), about PC configuration, USB ports, etc... no clue what is the defining problem.
though all this sounds strange indeed, usually when the emmc is fried, "fastboot oem rebootRUU" will throw an error.
can you extract the ROM.ZIP from the 3.17.502.3 RUU.EXE and try flashing it using fastboot commands:
run the RUU.EXE, once you're at the welcome screen, it would have extracted all the files into %TEMP%/<weird long numbered folder name> (use sort by date modified to find the newest folders), in it you should find a 1.5GB or so ROM.ZIP <- that's an encrypted/signed ruu.zip) copy it to your fastboot folder, exit the RUU.EXE, and flash the ROM.ZIP (it will give a lot more output):
relock bootloader (since you are S-On):
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice, the first one only does the hboot preupdate
fastboot reboot-bootloader
and copy/paste the command prompt output here, make sure to set the command prompt buffer size to a large enough size (at least 500+ lines)
obviously, if we had some background as to what happened previously, it would/could help too

nkk71 said:
@clsA is quite right about those 4.xx RUUs, they do work, but are very sensitive (for lack of a better word), about PC configuration, USB ports, etc... no clue what is the defining problem.
though all this sounds strange indeed, usually when the emmc is fried, "fastboot oem rebootRUU" will throw an error.
can you extract the ROM.ZIP from the 3.17.502.3 RUU.EXE and try flashing it using fastboot commands:
run the RUU.EXE, once you're at the welcome screen, it would have extracted all the files into %TEMP%/<weird long numbered folder name> (use sort by date modified to find the newest folders), in it you should find a 1.5GB or so ROM.ZIP <- that's an encrypted/signed ruu.zip) copy it to your fastboot folder, exit the RUU.EXE, and flash the ROM.ZIP (it will give a lot more output):
relock bootloader (since you are S-On):
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice, the first one only does the hboot preupdate
fastboot reboot-bootloader
and copy/paste the command prompt output here, make sure to set the command prompt buffer size to a large enough size (at least 500+ lines)
obviously, if we had some background as to what happened previously, it would/could help too
Click to expand...
Click to collapse
Thank you for the clear instructions. I followed them over my lunch hour. My only problem was getting the command prompt buffer to stick, I changed it to 999 but it kept truncating the output anyhow. So I ran the commands a second time and snagged the output a few times throughout the process and cobbled it back together.
Here's the output at pastebin: http://pastebin.com/dNKaKKtd (note that it does not show the lock command as this was the second iteration that I captured)
presently, the phone is still looping.
I still have the phone for another night, so I'll keep going with this if you have more suggestions or instructions.
Many Thanks!

matt314159 said:
Thank you for the clear instructions. I followed them over my lunch hour. My only problem was getting the command prompt buffer to stick, I changed it to 999 but it kept truncating the output anyhow. So I ran the commands a second time and snagged the output a few times throughout the process and cobbled it back together.
Here's the output at pastebin: http://pastebin.com/dNKaKKtd (note that it does not show the lock command as this was the second iteration that I captured)
presently, the phone is still looping.
I still have the phone for another night, so I'll keep going with this if you have more suggestions or instructions.
Many Thanks!
Click to expand...
Click to collapse
Well that output looks just fine, the ruu is successfully flashed, and has put everything back to stock. So unfortunately i can't really think of anything else, my only two guesses would be:
1- hardware problem
2- if he did flash something into p19 (the active cmdline overflow error), then maybe try the older cwm 6.0.2.8 recovery which seems to sometimes work for s-on users
you should first try to find out from your friend if this was the result of him flashing something, or if it happened by itself (in the latter case, it would be a hardware problem for sure)

nkk71 said:
Well that output looks just fine, the ruu is successfully flashed, and has put everything back to stock. So unfortunately i can't really think of anything else, my only two guesses would be:
1- hardware problem
2- if he did flash something into p19 (the active cmdline overflow error), then maybe try the older cwm 6.0.2.8 recovery which seems to sometimes work for s-on users
you should first try to find out from your friend if this was the result of him flashing something, or if it happened by itself (in the latter case, it would be a hardware problem for sure)
Click to expand...
Click to collapse
Thanks so much for your help! Nothing ended up working, so I gave the phone back. My colleague wasn't sure the history of it, but I'm willing to bet hardware issue. I appreciate your guidance, though! This was good learning experience for me. I feel a lot more at home with a lot of the basic fastboot commands and that kind of thing, so it wasn't a total loss on my part. I'm usually having to look up tutorials just to remember basic syntax!
Anyway thanks to all who chimed in. If mods want, they can close this thread, otherwise I'll just let it sink to its grave.

HTC One M7, boot loop, can flash small ROMs but boots hang

I think my phone is bricked (I didn't do it, honest).
Phone is HTC One M7, bought unlocked from Amazon. Branded AT&T. I have used it successfully for 9 months. In January (when I received it), I booted it up, went through root directions, and have had it rooted and unlocked (but left S-ON, didn't bother to S-OFF). I never installed any custom ROMs, I just wanted root for backup and for various utilities. I never bothered with any alternate firmware, either ... didn't want to brick my phone.
3 weeks ago it began draining the battery and running 100% CPU (observed via a Quick System Info in notification tray), and the phone would take forever to do simple things ... and then be fine again. I put up with that for a week, then began uninstalling apps 3 or 4 at a time. Nothing fixed the problem.
Last week, it was setting on my desk, and when I looked over at it, it had rebooted itself and was displaying the HTC boot logo ... not boot looping, just sitting there. I tried rebooting and it just looped. I tried going to recovery (TWRP), and the TeamWin logo would display, and then it would reboot to the HTC logo. Sometimes it would boot past the HTC logo and start the AT&T animation, but it would cut off after .5 seconds and reboot.
Since then - I've tried everything I can think of. I eventually had success flashing the clockwork recovery (touch 6048), that successfully boots to the menu interface, so then I could try wiping /cache and /data ... no joy. I then tried sideloading roms; large roms (1.3GB) get to 74% and then abort with an adb protocol error. A smaller ROM (Android_Revolution_HD-One_6.1_GE.zip) loads all the way, but upon reboot it again hangs at the HTC boot logo.
My fear is that there is a hardware memory fault in the device and I'm just toast. I finally gave up on it and ordered a Moto G LTE as a replacement ... nice little phone, but I'd love to resurrect my HTC One.
Help! Any ideas?

therealdeadlycheese said:
I think my phone is bricked (I didn't do it, honest).
Phone is HTC One M7, bought unlocked from Amazon. Branded AT&T. I have used it successfully for 9 months. In January (when I received it), I booted it up, went through root directions, and have had it rooted and unlocked (but left S-ON, didn't bother to S-OFF). I never installed any custom ROMs, I just wanted root for backup and for various utilities. I never bothered with any alternate firmware, either ... didn't want to brick my phone.
3 weeks ago it began draining the battery and running 100% CPU (observed via a Quick System Info in notification tray), and the phone would take forever to do simple things ... and then be fine again. I put up with that for a week, then began uninstalling apps 3 or 4 at a time. Nothing fixed the problem.
Last week, it was setting on my desk, and when I looked over at it, it had rebooted itself and was displaying the HTC boot logo ... not boot looping, just sitting there. I tried rebooting and it just looped. I tried going to recovery (TWRP), and the TeamWin logo would display, and then it would reboot to the HTC logo. Sometimes it would boot past the HTC logo and start the AT&T animation, but it would cut off after .5 seconds and reboot.
Since then - I've tried everything I can think of. I eventually had success flashing the clockwork recovery (touch 6048), that successfully boots to the menu interface, so then I could try wiping /cache and /data ... no joy. I then tried sideloading roms; large roms (1.3GB) get to 74% and then abort with an adb protocol error. A smaller ROM (Android_Revolution_HD-One_6.1_GE.zip) loads all the way, but upon reboot it again hangs at the HTC boot logo.
My fear is that there is a hardware memory fault in the device and I'm just toast. I finally gave up on it and ordered a Moto G LTE as a replacement ... nice little phone, but I'd love to resurrect my HTC One.
Help! Any ideas?
Click to expand...
Click to collapse
Could you post a fastboot getvar all except remove the imei and serialno? I think you need to flash the stock firmware or a RUU if one is available.

therealdeadlycheese said:
I think my phone is bricked (I didn't do it, honest).
Phone is HTC One M7, bought unlocked from Amazon. Branded AT&T. I have used it successfully for 9 months. In January (when I received it), I booted it up, went through root directions, and have had it rooted and unlocked (but left S-ON, didn't bother to S-OFF). I never installed any custom ROMs, I just wanted root for backup and for various utilities. I never bothered with any alternate firmware, either ... didn't want to brick my phone.
3 weeks ago it began draining the battery and running 100% CPU (observed via a Quick System Info in notification tray), and the phone would take forever to do simple things ... and then be fine again. I put up with that for a week, then began uninstalling apps 3 or 4 at a time. Nothing fixed the problem.
Last week, it was setting on my desk, and when I looked over at it, it had rebooted itself and was displaying the HTC boot logo ... not boot looping, just sitting there. I tried rebooting and it just looped. I tried going to recovery (TWRP), and the TeamWin logo would display, and then it would reboot to the HTC logo. Sometimes it would boot past the HTC logo and start the AT&T animation, but it would cut off after .5 seconds and reboot.
Click to expand...
Click to collapse
These problems can be addressed with a firmware flash as suggested by @majmoz. Definitely worth doing before you try to flash a new Rom but won't fix it if it's a hardware problem.
I then tried sideloading roms; large roms (1.3GB) get to 74% and then abort with an adb protocol error.
Click to expand...
Click to collapse
this can be because of a few reasons. Mainly out dated adb or Do you have HTC sync installed? its best to uninstall it but leave the drivers installed. It can interfere with connection for adb and fastboot.
A smaller ROM (Android_Revolution_HD-One_6.1_GE.zip) loads all the way, but upon reboot it again hangs at the HTC boot logo.
Click to expand...
Click to collapse
Android Revolution roms require TWRP 2.6.3.3 for successful install. This Rom will always fail to boot if installed with most other recoveries, especially CWM :good:
Provide @majmoz with your getvar and I'm sure he will help you flash your firmware after which you should try flashing another Rom but make sure it's compatible with your recovery to avoid boot problems.
My fear is that there is a hardware memory fault in the device and I'm just toast. I finally gave up on it and ordered a Moto G LTE as a replacement ... nice little phone, but I'd love to resurrect my HTC One.
Help! Any ideas?
Click to expand...
Click to collapse
Unfortunately there's a good chance this is hardware related. But best to use all software solutions before righting it off
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

majmoz said:
Could you post a fastboot getvar all except remove the imei and serialno? I think you need to flash the stock firmware or a RUU if one is available.
Click to expand...
Click to collapse
Hey, thanks for the quick reply. Here's the getvar output:
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4T.20.3218.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.17.502.3
INFOversion-misc: PVT SHIP S-ON
INFOserialno: ------------
INFOimei: ---------------
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4326mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-a85199f7
INFOhbootpreupdate: 11
INFOgencheckpt: 0

Danny201281 said:
These problems can be addressed with a firmware flash as suggested by @majmoz. Definitely worth doing before you try to flash a new Rom but won't fix it if it's a hardware problem.
this can be because of a few reasons. Mainly out dated adb or Do you have HTC sync installed? its best to uninstall it but leave the drivers installed. It can interfere with connection for adb and fastboot.
Android Revolution roms require TWRP 2.6.3.3 for successful install. This Rom will always fail to boot if installed with most other recoveries, especially CWM :good:
Provide @majmoz with your getvar and I'm sure he will help you flash your firmware after which you should try flashing another Rom but make sure it's compatible with your recovery to avoid boot problems.
Unfortunately there's a good chance this is hardware related. But best to use all software solutions before righting it off
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
Hey, thanks for the tips.
I'm a linux user, so everything is command-line, fastboot or adb. No HTCSync or drivers other than what is in my kernel (3.14.22-100.fc19.x86_64).
I would have been happy to have used TWRP but I couldn't get it to boot all the way, just would hang at the TeamWin logo. Here are the ones I tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7ul.img
openrecovery-twrp-2.7.1.1-m7.img
openrecovery-twrp-2.8.0.2-m7.img
openrecovery-twrp-2.8.1.0-evitareul.img
I would be willing to try again, or another one, if you suggest it ... didn't realize that CWM would bork the Android Revolution ROM. I might try 2633 again to see if it works after flashing CWM, somehow.
Hey, thanks for the tips. I fear it is hardware, but I agree, the smart thing is to exhaust firmware flash attempts.

Danny201281 said:
Android Revolution roms require TWRP 2.6.3.3 for successful install. This Rom will always fail to boot if installed with most other recoveries, especially CWM :good:
Click to expand...
Click to collapse
therealdeadlycheese said:
(Android_Revolution_HD-One_6.1_GE.zip) loads all the way, but upon reboot it again hangs at the HTC boot logo.
Click to expand...
Click to collapse
Just want to add that this version of ARHD require s-off (GE). use a Sense based rom like arhd 82.
Would also suggest to do a full "format data" (not only a wipe) before pushing and installing the rom, for me, the initial issue sounds like something got corrupted and a format data wouldn't hurt.

therealdeadlycheese said:
Hey, thanks for the quick reply. Here's the getvar output:
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4T.20.3218.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.17.502.3
INFOversion-misc: PVT SHIP S-ON
INFOserialno: ------------
INFOimei: ---------------
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4326mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-a85199f7
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
lock the bootloader with fastboot
fastboot oem lock
then download and flash this RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
For Linux the RUU zip is here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/

therealdeadlycheese said:
Hey, thanks for the tips.
I'm a linux user, so everything is command-line, fastboot or adb. No HTCSync or drivers other than what is in my kernel (3.14.22-100.fc19.x86_64).
I would have been happy to have used TWRP but I couldn't get it to boot all the way, just would hang at the TeamWin logo. Here are the ones I tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7ul.img
openrecovery-twrp-2.7.1.1-m7.img
openrecovery-twrp-2.8.0.2-m7.img
openrecovery-twrp-2.8.1.0-evitareul.img
I would be willing to try again, or another one, if you suggest it ... didn't realize that CWM would bork the Android Revolution ROM. I might try 2633 again to see if it works after flashing CWM, somehow.
Hey, thanks for the tips. I fear it is hardware, but I agree, the smart thing is to exhaust firmware flash attempts.
Click to expand...
Click to collapse
Sigh. Tried openrecovery-twrp-2.6.3.4-m7ul.img again ... boots to teamwin logo, screen blanks for 2 seconds ... and reboots, hanging at htc logo.

therealdeadlycheese said:
Sigh. Tried openrecovery-twrp-2.6.3.4-m7ul.img again ... boots to teamwin logo, screen blanks for 2 seconds ... and reboots, hanging at htc logo.
Click to expand...
Click to collapse
do what cisa told above, There a ruu that match your verison it should be the easiest way to restore you phone. relock and run the ruu

alray said:
Just want to add that this version of ARHD require s-off (GE). use a Sense based rom like arhd 82.
Click to expand...
Click to collapse
Good catch :good:
therealdeadlycheese said:
Hey, thanks for the tips.
I'm a linux user, so everything is command-line, fastboot or adb. No HTCSync or drivers other than what is in my kernel (3.14.22-100.fc19.x86_64).
I would have been happy to have used TWRP but I couldn't get it to boot all the way, just would hang at the TeamWin logo. Here are the ones I tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7ul.img
openrecovery-twrp-2.7.1.1-m7.img
openrecovery-twrp-2.8.0.2-m7.img
openrecovery-twrp-2.8.1.0-evitareul.img
I would be willing to try again, or another one, if you suggest it ... didn't realize that CWM would bork the Android Revolution ROM. I might try 2633 again to see if it works after flashing CWM, somehow.
Hey, thanks for the tips. I fear it is hardware, but I agree, the smart thing is to exhaust firmware flash attempts.
Click to expand...
Click to collapse
Ahh a Linux user nice. Have you tried killall adb. To fix the protocol error
In your terminal type
Code:
killall adb
disconnect your phone for a few seconds then
Code:
sudo adb devices
Also worth checking your adb version with
Code:
adb version
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 02:19 AM ---------- Previous post was at 02:13 AM ----------
therealdeadlycheese said:
Sigh. Tried openrecovery-twrp-2.6.3.4-m7ul.img again ... boots to teamwin logo, screen blanks for 2 seconds ... and reboots, hanging at htc logo.
Click to expand...
Click to collapse
Just follow instructions from @clsA to restore your phone.
But for future reference are you using
Code:
fastboot erase cache
after flashing recovery?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

therealdeadlycheese said:
Hey, thanks for the quick reply. Here's the getvar output:
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4T.20.3218.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.17.502.3
INFOversion-misc: PVT SHIP S-ON
INFOserialno: ------------
INFOimei: ---------------
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4326mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-a85199f7
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
Here is full wipe stock firmware 4.18.502.7. It will wipe your data so you will need to copy your files off your phone to your PC. Since you are S-ON, you will need to lock your bootloader prior to flashing this firmware. Download the file and place in your adb/fastboot folder and rename it firmware.zip for ease of typing. Here are the steps for flashing the firmware.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
If this firmware didn't flash successfully, then you can execute RUU 3.17.502.3 or the next available RUU 4.18.502.7.
If the firmware flashes successfully, then the only RUU you can run is the 4.18.502.7 one.

majmoz said:
Here is [link removed]. It will wipe your data so you will need to copy your files off your phone to your PC. Since you are S-ON, you will need to lock your bootloader prior to flashing this firmware. Download the file and place in your adb/fastboot folder and rename it firmware.zip for ease of typing. Here are the steps for flashing the firmware.
If this firmware didn't flash successfully, then you can execute [links removed] or the next available.
If the firmware flashes successfully, then the only RUU you can run is the 4.18.502.7 one.
Click to expand...
Click to collapse
OK, I really appreciate all the help. Where I'm at:
- booted clean Windows7 VMware image
- installed adb/fastboot/drivers in Windows7
- verified windows VM access with "fastboot devices" (success)
- ran "fastboot oem lock" ; last line said "FAILED (status read failed (Too many links))", but the phone says "RELOCKED", so I'm guessing it worked
- ran RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe
in windows VM
- phone now shows silver HTC logo, green bar at about 20%, RUU installer shows "Updating Boot...." with 20% in the progress bar .... but it has been that way for about 10 minutes ... and the phone shows a triangle with an exclamation point in it at the end of the progress bar.

therealdeadlycheese said:
OK, I really appreciate all the help. Where I'm at:
- booted clean Windows7 VMware image
- installed adb/fastboot/drivers in Windows7
- verified windows VM access with "fastboot devices" (success)
- ran "fastboot oem lock" ; last line said "FAILED (status read failed (Too many links))", but the phone says "RELOCKED", so I'm guessing it worked
- ran RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe
in windows VM
- phone now shows silver HTC logo, green bar at about 20%, RUU installer shows "Updating Boot...." with 20% in the progress bar .... but it has been that way for about 10 minutes ... and the phone shows a triangle with an exclamation point in it at the end of the progress bar.
Click to expand...
Click to collapse
forget the VM ..just use the ruu.zip

clsA said:
forget the VM ..just use the ruu.zip
Click to expand...
Click to collapse
VM RUU is still stuck on 20% ... reboot and start over with the zip from linux, then?

therealdeadlycheese said:
VM RUU is still stuck on 20% ... reboot and start over with the zip from linux, then?
Click to expand...
Click to collapse
yes you'll have to force reboot the phone if it's stuck
hold the power and volume down under a bright light for about 15 seconds

clsA said:
yes you'll have to force reboot the phone if it's stuck
hold the power and volume down under a bright light for about 15 seconds
Click to expand...
Click to collapse
heh
rebooting now, will try flashing again from linux.

Well, last night I let it sit at 20% for 45 minutes before giving up and disconnecting the phone. But, when I tried to reboot it, it wouldn't boot, no lights, no sounds, not anything. I let it sit for a bit, tried again, nothing ... hold power button, hold volume buttons, clickety-clickety power and volume buttons, recharging ... still nothing. Went through all the gyrations again this morning ... still dead.
I may get farther under warranty with it in this totally inert state than I would if it booted to a custom recovery image, so maybe I'm better off.
Thanks everyone for the help, though.
Has anyone had any experience with HTC Warranty repair? Any tips or gotchas to share?

I didn't want to start a new thread, since this is very similar to my situation.
I have a sprint htc one m7. I'm pretty sure the phone is hot since my girlfriend bought it for me from some guy she works with for $10. I soon found out that Sprint either hates their customers, or wants to try their hardest to protect their customers from street corner electronics hustlers (probably a bit of both). I want to unluck the sim, but it seems nearly impossible...
I immediately unlocked and rooted my new android phone. When I tried using firewater to unlock the sim, I was told that my kernel had anti-firwater. So I tried flashing a kernel from this site which was compatible to my device, but the device was stuck in boot loop. The arrogant noob that I am started screwing around with the device, and eventually bricked the phone.
Luckily, I was able to find an ruu from this site that didn't require s-off and successfully restored the device.
WHERE I STAND AT THE MOMENT:
before I go on, here are my specs;
Android version 4.4.2
sense 6.0
software 5.05.651.2
rooted with supersu and recovery is TWRP
I tried running firewater again...failed. protected. So, I tried flashing Android_Revolution_HD-One_6.1_GE. It installed perfectly, but when I rebooted, it hung at the htc splash screen. I tried again after doing another restore.
What I don't understand is this: when I reboot after installing this rom (and a viper rom), TWRP tells asks me to install SuperSU because my device "doesn't seem to be rooted". I found that odd since I had previously rooted the phone, so I downloaded a root checker just to make sure. The app congratulated me, ensuring that my device was rooted, but I'm still being asked to install supersu after flashing the rom. I did, of course, but the device just reboots when I "swipe to install"

Nikatichi said:
I immediately unlocked and rooted my new android phone. When I tried using firewater to unlock the sim, I was told that my kernel had anti-firwater. So I tried flashing a kernel from this site which was compatible to my device, but the device was stuck in boot loop.
Click to expand...
Click to collapse
Are you sure you have flashed a sprint compatible kernel? Sprint htc one is not the same as the Htc One, different hardware and different partition layout. Flashing a kernel, a rom or a recovery not explicitly made for sprint htc one will soft brick your phone and will probably corrupt your partitions.
I tried running firewater again...failed. protected. So, I tried flashing Android_Revolution_HD-One_6.1_GE. It installed perfectly, but when I rebooted, it hung at the htc splash screen. I tried again after doing another restore.
Click to expand...
Click to collapse
Go back in ARHD 6.1 thread and read the OP:
you should see:
For HTC One International GSM/LTE (UL), International GSM (U), all U.S. carriers (apart from Sprint) (click here for more details)
Click to expand...
Click to collapse
and
Android Revolution HD 6.1
Google Edition
You need S-OFF, otherwise you'll experience boot-loop!
Click to expand...
Click to collapse
Your device is sprint and is not s-off....
What I don't understand is this: when I reboot after installing this rom (and a viper rom), TWRP tells asks me to install SuperSU because my device "doesn't seem to be rooted". I found that odd since I had previously rooted the phone,
Click to expand...
Click to collapse
I think you don't understand what "rooting" mean. You root the OS aka Android aka System, not the phone itself. If you flash another rom aka system, you have to root it again (except if the rom is pre-rooted).
+
You are probably not using a sprint recovery/sprint rom so the recovery is probably not looking for root files at the correct partition.
and you'll be happy to know that there is a dedicated thread in the sprint htc one "general" forum to help users achieving s-off and sim-unlock on 5.x.651.x version. You might want to try what said there.
http://forum.xda-developers.com/spr...rint-htc-one-s-off-sim-ulock-hboot-1-t2890412
So remember, do not use anything (ruu/rom/recovery/mods/guides) that are not explicitly made for the Sprint htc one variant, which mean basically everything posted in this forum section (Htc One)

ElementalX-m7-Sprint-13.1 is the name of the kernel, and thank you for responding so fast. I've jumped in head first and now have deep respect for developers; especially those that give their own time to help. Thank you. I'm diving into that link you gave me right now.

[Q] Help...can't make/receive calls (Andriod 5.02 / Rev. 90.1)

Hi there,
I bought a 2nd hand phone [HTC M7] off ebay with Revolution 90.1 / Android 5.02 / Build No. 7.15.401.1
Everything works great...but I can't make or receive calls. I figured this was the same issue that struck HTC phones in Dec, but from my understanding 7.15.401.1 is more recent than the official HTC fix (6.10.531.10) & Rev. 90.1 already has this fix included also. I've also installed Viperone 7.02 (fix incl.), but no difference, so I'm now back to Rev. 90.1. I've also cleared google caches, froze HTC lockscreen etc etc but now I've run out of ideas.
Can anybody help?!
Thanks..!

Dial tone on a mobile phone... Whaaat? Bring the phone to your service provider, which is advice I never really give out, but from what you wrote, I think your missing something, like installing the SIM card or provisioning the phone correctly. Do you even have service and signal on it?
Sent from my HTC One using Tapatalk

synt3k said:
Dial tone on a mobile phone... Whaaat? Bring the phone to your service provider, which is advice I never really give out, but from what you wrote, I think your missing something, like installing the SIM card or provisioning the phone correctly. Do you even have service and signal on it?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sorry - Dial tone meaning when I call I don't hear a ring [orig post now edited].
Data/Wifi works & I get signal. If people call me my phone rings, I can pick up but then silence

Tinky24 said:
Sorry - Dial tone meaning when I call I don't hear a ring [orig post now edited].
Data/Wifi works & I get signal. If people call me my phone rings, I can pick up but then silence
Click to expand...
Click to collapse
can you post the fastboot getvar all of the phone please, remove imei and serial number before posting

Seanie280672 said:
can you post the fastboot getvar all of the phone please, remove imei and serial number before posting
Click to expand...
Click to collapse
:
I can't get Min. Adb & Fastboot to see my device [ adb devices just prints "List of Devices" then a blank line], which suggests I'm missing drivers
I've done both routes suggested on technobuzz.net/fastest-easiest-method-setup-adb-fastboot-windows/ and no luck. I've uninstalled and reinstalled my HTC m7 drivers, to no avail.

Tinky24 said:
:
I can't get Min. Adb & Fastboot to see my device [ adb devices just prints "List of Devices" then a blank line], which suggests I'm missing drivers
I've done both routes suggested on technobuzz.net/fastest-easiest-method-setup-adb-fastboot-windows/ and no luck. I've uninstalled and reinstalled my HTC m7 drivers, to no avail.
Click to expand...
Click to collapse
which version of windows are you using ?
also have a look in device manager whislt your phone is plugged in and phone in bootloader with fastbootUSB showing on the screen, see if device manager is seeing your device, it should say MyHTC under Android Devices (post a pict of device manager if possible)
fastboot commands only whilst in bootloader, adb wont work, adb is only for booted rom and recovery.
Just had a look at the link you posted, The adb and fastboot files are fine, I use those ones myself, the drivers are probably too far out of date, download HTC sync manager and install it, then goto add remove programs and remove HTC sync only, you will see the driver package just above it, leave that there, then plug your phone in and try fastboot devices or fastboot getvar all again.

Seanie280672 said:
which version of windows are you using ?
also have a look in device manager whislt your phone is plugged in and phone in bootloader with fastbootUSB showing on the screen, see if device manager is seeing your device, it should say MyHTC under Android Devices (post a pict of device manager if possible)
fastboot commands only whilst in bootloader, adb wont work, adb is only for booted rom and recovery.
Just had a look at the link you posted, The adb and fastboot files are fine, I use those ones myself, the drivers are probably too far out of date, download HTC sync manager and install it, then goto add remove programs and remove HTC sync only, you will see the driver package just above it, leave that there, then plug your phone in and try fastboot devices or fastboot getvar all again.
Click to expand...
Click to collapse
Right, getting somewhere, thanks for clarifying the fastboot/adb difference:
fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.401.2
version-misc: PUT SHIP S-OFF
meid: 000000000000
product: my_url
platform: HBOOT-8064
modelid: PN710000
cidnum: 11111111
battery-status: good
battery-voltage: 4250mv
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
[Windows 7 btw]

Tinky24 said:
Right, getting somewhere, thanks for clarifying the fastboot/adb difference:
fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.401.2
version-misc: PUT SHIP S-OFF
meid: 000000000000
product: my_url
platform: HBOOT-8064
modelid: PN710000
cidnum: 11111111
battery-status: good
battery-voltage: 4250mv
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
[Windows 7 btw]
Click to expand...
Click to collapse
dont change to windows 8 you will have all sorts of problems due to your HBOOT, you are on a very early firmware there and as you are s-off, that helps alot, I think you really need to bring your phone back up to speed to be sure thats not whats causing the issues your having, bear with me whilst I find the link of 401 firmwares. (version-main: 1.29.401.2)
If there is anything on the phone you need to keep, pictures, photo's music etc, please back it up now as firmware flash can wipe the device in some cases.
OK heres the link to the firmwares, you need to flash them one at a time, starting with the earliest 2.24.401's then the 3xxxxxx's then the 4xxxxx's then the 5xxxxxx and finally the 6xxxxxx's,: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/ this issue you experiencing was fixed in the 7xxxxxx firmware which i'll find the link for shortly.
Do you know how to flash the firmware ?

Thanks so much.
I've found a guide

Tinky24 said:
Thanks so much.
Is it the same way as flashing a ROM i.e. Recovery > Install?
Click to expand...
Click to collapse
no, heres a good guide on how to do it: https://trjlive.com/guide-install-firmware-htc-one-m7/
if your phone is already in fastbootUSB mode, then skip the first 2 commands, also something not mentioned in the guide is the firmware.zip file MUST be in the same folder as your adb and fastboot files on your computer, when you download the firmware files (one at a time) they will be named as per the name on the site, just rename them to firmware.zip for ease, once you've finished flashing each one and the phone has finished booting, delete it and download the next then follow the prceedure once again.
your battery must be 50% or more before proceeding, but I can see yours is good at the moment at 4250mv
If you check yourself, no need to post each one, you should notice the version main number going up, the HBOOT version going up, you will also have stock recovery (a red triangle with an exclamation mark)
do not skip any steps and you'll be fine, report back after the first flash and let us know how it went, any problems, just ask.

Ok all done, getvar now gives me:
version-main: 6.09.401.12
HBOOT 1.57

Tinky24 said:
Ok all done, getvar now gives me:
version-main: 6.09.401.12
HBOOT 1.57
Click to expand...
Click to collapse
perfect, as long as it still says your s-off, ps, never go s-on, you'll regret it, you can do one of the following.
You can flash this firmware https://www.androidfilehost.com/?fid=95897840722644637 (unsigned) not official yet, but will work for you as your s-off, if you go s-on your phone will brick, and then test your rom, your issue should be fixed.
Or you can do this which is what I did: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311 This is official

I rebooted after finishing the v6 updates, then got the red triangle thing - do I now factory reset?
"can not mount SD card"

Tinky24 said:
I rebooted after finishing the v6 updates, then got the red triangle thing - do I now factory reset?
Click to expand...
Click to collapse
hold down the power button with the volume down, keep holding whilst the home and back bottuns on the bottom flash about 15 times, when they stop flashing, release the power button, but continue to hold down the volume down, the phone should boot to the bootloader, factory reset is in the list, use the volume button up / down to highlight it and power button to select, why do you want to factory reset ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
cannot mount sdcard is a normal error if you have entered recovery, there is no sdcard.

Sorry ignore the fact. reset bit.
I've now uploaded the last firmware zip you gave me. Can I just System reboot or is there something left to do?

Tinky24 said:
Sorry ignore the fact. reset bit.
I've now uploaded the last firmware zip you gave me. Can I just System reboot or is there something left to do?
Click to expand...
Click to collapse
yeah just system reboot, the lollipop rom's do really require Lollipop firmware which is what you just flashed in order toi work properly, your firmware was about 2 years out of date.

Reboot brings up the white HTC screen...then the screen returns to Stock Recovery Triangle...

Tinky24 said:
Reboot brings up the white HTC screen...then the screen returns to Stock Recovery Triangle...
Click to expand...
Click to collapse
The firmware flash may of messed up your rom, did you flash android revolution 90.1 yourself ?

No it came with Rev. Should I reflash it?

Tinky24 said:
No it came with Rev. Should I reflash it?
Click to expand...
Click to collapse
yes, or a rom of your choice, you will need a custom recovery first, so download this:
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
put your phone into fastbootUSB mode on the screen again by holding down the volume down and power button method again as I described earlier, this is the white screen not the black screen with silver HTC logo.
rename the download above to recovery.img and place it in the same folder as adb and fastboot again and with your phone plugged in issue these commands one at a time:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, as long as your drivers are working correctly, this recovery supports MTP so the computer should see the internal storage, just downlaod and copy the rom you want to flash straight to the internal storage, unplug your phone and install it, its recommended to install option with full wipe, dont worry, internal storage isnt touched, just wipes data and system.

HTC M7 - Tried to root (Installed TWRP) but now phone won't boot

I tried to use this guide to on htconeroot
Got to installing the zip for SuperSU v1.30
The phone rebooted but it said SuperSU failed
Tried to install Update Super SU v2.46
Phone no longer reboots. It shows the white HTC One loading screen but then just goes very dark grey forever.
I can still access the white menu that comes up when you hold volume down and power
Can also access the TWRP screen, however I tried factory reset there and it didn't change, it still won't boot.
Can't take out sd or battery as metal case
Anyway not sure if this is meant to be in the HTC M7 category, a TWRP category, Rooting one.
I'm not sure if it is because the guide was for 4.3 and on 5.02 or what.
I also held the power off button when it was doing some things which may have also caused it
I don't really care about it being rooted so much as having my phone back. The only reason I wanted it rooted was to install the camera change that is supposed to get rid of the green tint.
Anyway thank you for your time. And I appreciate any assistance that can be given. I have spent hours trying to figure it out, but I am still confused and figure I am likely to screw it up even more

Syrup4 said:
I tried to use this guide to on htconeroot
Got to installing the zip for SuperSU v1.30
The phone rebooted but it said SuperSU failed
Tried to install Update Super SU v2.46
Phone no longer reboots. It shows the white HTC One loading screen but then just goes very dark grey forever.
I can still access the white menu that comes up when you hold volume down and power
Can also access the TWRP screen, however I tried factory reset there and it didn't change, it still won't boot.
Can't take out sd or battery as metal case
Anyway not sure if this is meant to be in the HTC M7 category, a TWRP category, Rooting one.
I'm not sure if it is because the guide was for 4.3 and on 5.02 or what.
I also held the power off button when it was doing some things which may have also caused it
I don't really care about it being rooted so much as having my phone back. The only reason I wanted it rooted was to install the camera change that is supposed to get rid of the green tint.
Anyway thank you for your time. And I appreciate any assistance that can be given. I have spent hours trying to figure it out, but I am still confused and figure I am likely to screw it up even more
Click to expand...
Click to collapse
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.

mb_guy said:
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
Click to expand...
Click to collapse
Thank you very much for responding.
I am not sure what a nandroid backup is. I was following a guide.
I copied every file on phone to my computer via the file manager. And I used the command prompt and typed in "adb backup -apk -all -f backup.ab". I am not sure if that is the right kind.
I don't know how to post that output you asked for. I googled it, but it sounded like I needed to use my computer, and my computer no longer recognizes my phone due to it not booting. Or is that done in TWRP? Thank you again.
PS: htconeroot .com /htc-one-root/how-to-root-htc-one-windowsmaclinux/ is the guide I was following. Got up to install SU before it went bad. In case it helps. I can't properly link as I haven't made enough posts.

Syrup4 said:
Thank you very much for responding.
I am not sure what a nandroid backup is. I was following a guide.
I copied every file on phone to my computer via the file manager. And I used the command prompt and typed in "adb backup -apk -all -f backup.ab". I am not sure if that is the right kind.
I don't know how to post that output you asked for. I googled it, but it sounded like I needed to use my computer, and my computer no longer recognizes my phone due to it not booting. Or is that done in TWRP? Thank you again.
PS: htconeroot .com /htc-one-root/how-to-root-htc-one-windowsmaclinux/ is the guide I was following. Got up to install SU before it went bad. In case it helps. I can't properly link as I haven't made enough posts.
Click to expand...
Click to collapse
A nandroid backup is actually made with in twrp, read up on for future.
You obviously have adb installed since you used it for backup.
Put the phone in bootloader mode, restart holding down power and volume down. (have you not gone into twrp?) Then plug in usb and you should see "fastboot usb"
then from the adb folder type "fastboot getvar all"
Do some google searching there are dozens of articles regarding flashing htc one and using adb and fastboot commands phone bootloader and recovery .

Delete please, forgot to quote/ reply.

mb_guy said:
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
Click to expand...
Click to collapse
Hello, thanks again. is this what you were referring to posting?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Removed
(bootloader) imei: Removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s

Syrup4 said:
Hello, thanks again. is this what you were referring to posting?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
When posting a "fastboot getvar all" edit out your imei and serialno, don't post these 2 numbers on the forum (edit your above post and remove them).
You should be able to restore your phone by flashing the 7.17.631.7 7.17.661.7 RUU. You'll first need to edit your MISC partition to change your version-main from 7.17.661.35 to 7.17.661.7 then relock your bootloader and flash the RUU. Once done, you'll have to install 2 ota updates so your phone is back to the 7.17.661.35 version. When back on this version, re-unlock your bootloader, re-flash twrp and flash supersu version 2.46 (any version lower than that will not work on lollipop)
Instructions how to change your version-main at the end of post #2 of this thread (see "how to downgrade with s-on")
The RUU and instructions how to flash it in the same thread at post #1

alray said:
When posting a "fastboot getvar all" edit out your imei and serialno, don't post these 2 numbers on the forum (edit your above post and remove them).
You should be able to restore your phone by flashing the 7.17.631.7 RUU. You'll first need to edit your MISC partition to change your version-main from 7.17.631.35 to 6.17.631.7 then relock your bootloader and flash the RUU. Once done, you'll have to install 2 ota updates so your phone is back to the 7.17.631.35 version. When back on this version, re-unlock your bootloader, re-flash twrp and flash supersu version 2.46 (any version lower than that will not work on lollipop)
Instructions how to change your version-main at the end of post #2 of this thread (see "how to downgrade with s-on")
The RUU and instructions how to flash it in the same thread at post #1
Click to expand...
Click to collapse
Thank you very much. Both for the help fixing it, and letting me know to remove that info. I read the instructions however given that it won't boot. My computer won't recognize it to transfer the tool (Misc_Tool_1.00.zip) over, so I can install it in TWRP. I tried pushing it using a command with adb. But it said Device not found. Given it has no removable SD card I do not know how to move it. The manual one also required adb shell, which says device not found. I shall continue looking things up in the mean time.
Edit: Strangely HTC Sync manager pops up when it does fail to boot if I restart the phone. Given it is set to do so when the phone is plugged in. However it always says "no phone connected". As if it recognizes it for a second then stops.

Syrup4 said:
Thank you very much. Both for the help fixing it, and letting me know to remove that info. I read the instructions however given that it won't boot. My computer won't recognize it to transfer the tool (Misc_Tool_1.00.zip) over, so I can install it in TWRP. I tried pushing it using a command with adb. But it said Device not found. Given it has no removable SD card I do not know how to move it. The manual one also required adb shell, which says device not found. I shall continue looking things up in the mean time.
Edit: Strangely HTC Sync manager pops up when it does fail to boot if I restart the phone. Given it is set to do so when the phone is plugged in. However it always says "no phone connected". As if it recognizes it for a second then stops.
Click to expand...
Click to collapse
First thing you want when using adb or fastboot commands is to make sure HTC Sync is not installed or your computer because it can interfere with adb/fastboot connectivity. So go ahead and uninstall it (not closing it, uninstall for real) don't uninstall the drivers btw.
Make sure you have the latest htc drivers installed, that you are using a good usb cable (preferably the original cable or any other cable already known to work with data transfer as opposed to usb cables that can only provide power). Make sure you are using a usb 2.0 port on your computer at the back of your tower (not using front ports neither an external usb hub). Finally, adb commands will only work when booted in twrp recovery, they will not work when in bootloader mode as opposed to fastboot commands which only works in bootloader.
If using the commands to change your version-main, better to post it here before so I can confirm its the correct one. A simple typo in this command could make the situation worse (i.e: corrupting your misc partition).

alray said:
First thing you want when using adb or fastboot commands is to make sure HTC Sync is not installed or your computer because it can interfere with adb/fastboot connectivity. So go ahead and uninstall it (not closing it, uninstall for real) don't uninstall the drivers btw.
Make sure you have the latest htc drivers installed, that you are using a good usb cable (preferably the original cable or any other cable already known to work with data transfer as opposed to usb cables that can only provide power). Make sure you are using a usb 2.0 port on your computer at the back of your tower (not using front ports neither an external usb hub). Finally, adb commands will only work when booted in twrp recovery, they will not work when in bootloader mode as opposed to fastboot commands which only works in bootloader.
If using the commands to change your version-main, better to post it here before so I can confirm its the correct one. A simple typo in this command could make the situation worse (i.e: corrupting your misc partition).
Click to expand...
Click to collapse
Hello, thank you again.
I uninstalled sync. I am using the original cable, and have now plugged it in to a USB 2.0 port on the back.
I also tried to use the commands while the phone is on the TWRP screen. The one with a grey background and big touch buttons with blue on them that say "Install" "Wipe" "Backup" etc.
But it still won't recognize my device. I can type in ADB to get a list of commands.
But when I try to push anything, it says "error: device not found"
I tried the command "adb get-serialno" to see if other commands worked but it said "unknown".
Edit: Got it to show up as a device when in Fastboot USB. However it won't show up as a drive in mycomputer. ADB won't recognize it in either that mode or on TWRP. And once I access TWRP, it changes to android phone" as shown in the second pic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Syrup4 said:
Hello, thank you again.
I uninstalled sync. I am using the original cable, and have now plugged it in to a USB 2.0 port on the back.
I also tried to use the commands while the phone is on the TWRP screen. The one with a grey background and big touch buttons with blue on them that say "Install" "Wipe" "Backup" etc.
But it still won't recognize my device. I can type in ADB to get a list of commands.
But when I try to push anything, it says "error: device not found"
I tried the command "adb get-serialno" to see if other commands worked but it said "unknown".
Edit: Got it to show up as a device when in Fastboot USB. However it won't show up as a drive in mycomputer. ADB won't recognize it in either that mode or on TWRP. And once I access TWRP, it changes to android phone" as shown in the second pic.
Click to expand...
Click to collapse
When you're in TWRP are you sure you don't see the device as a disk drive, the newer versions of twrp support mtp which allows this. You should be able just to copy paste from you PC to the device. It looks to me this is working from your second picture.

mb_guy said:
It looks to me this is working from your second picture.
Click to expand...
Click to collapse
same. Maybe re-installing the latest drivers version wouldn't hurt...

alray said:
same. Maybe re-installing the latest drivers version wouldn't hurt...
Click to expand...
Click to collapse
mb_guy said:
When you're in TWRP are you sure you don't see the device as a disk drive, the newer versions of twrp support mtp which allows this. You should be able just to copy paste from you PC to the device. It looks to me this is working from your second picture.
Click to expand...
Click to collapse
Thanks once again both of you. But even though it seems like it should be listed. It is not. And if I right click on the device that appears, it is greyed out.
Which drivers? HTC ones? Android ones? or the Universal ADB (Android Debug Bridge) Driver for Windows.? I think I am getting confused between uninstalling and installing so many drivers, as to which overwrite.
Thanks again
Edit: It is TWRP v2.6.3.0

Syrup4 said:
Thanks once again both of you. But even though it seems like it should be listed. It is not. And if I right click on the device that appears, it is greyed out.
Which drivers? HTC ones? Android ones? or the Universal ADB (Android Debug Bridge) Driver for Windows.? I think I am getting confused between uninstalling and installing so many drivers, as to which overwrite.
Thanks again
Edit: It is TWRP v2.6.3.0
Click to expand...
Click to collapse
The HTC drivers, not the universal ones.
2.6.3.0 is to old and will cause problem. Once your drivers problem is fixed, update your twrp recovery before going any further (at least 2.6.3.3 or much newer if you want MTP support)
Ill be back in a few hours good luck

alray said:
The HTC drivers, not the universal ones.
2.6.3.0 is to old and will cause problem. Once your drivers problem is fixed, update your twrp recovery before going any further (at least 2.6.3.3 or much newer if you want MTP support)
Ill be back in a few hours good luck
Click to expand...
Click to collapse
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day

Syrup4 said:
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Click to expand...
Click to collapse
Is fastboot connectivity working? (boot in bootloader mode and use "fastboot device" command to see if your phone is detected) Or is it only adb not working when in twrp?
You can update twrp using fastboot commands when in bootloader mode:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
(replace "file_name.img" by the file name of the recovery you want to flash.

Syrup4 said:
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Click to expand...
Click to collapse
I have good luck with these adb tools. Also did you reboot pc after removing old drivers, sometime things just magically work after.
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP is updated from fastboot (fastboot flash recovery nameofrecovery.img)
https://dl.twrp.me/m7/

mb_guy said:
I have good luck with these adb tools. Also did you reboot pc after removing old drivers, sometime things just magically work after.
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP is updated from fastboot (fastboot flash recovery nameofrecovery.img)
https://dl.twrp.me/m7/
Click to expand...
Click to collapse
alray said:
Is fastboot connectivity working? (boot in bootloader mode and use "fastboot device" command to see if your phone is detected) Or is it only adb not working when in twrp?
You can update twrp using fastboot commands when in bootloader mode:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
(replace "file_name.img" by the file name of the recovery you want to flash.
Click to expand...
Click to collapse
THANK YOU.
There has been progress.
So I installed the new TWRP posted, version 2.8.7.0-m7.
At first it said signature checking failed, so I booted the token thing from HTCDev again.
It then allowed me to install the new TWRP.
When the new TWRP was installed it came up with a screen with errors in red. "Can't write to Cache" or something.
I was going to write them down but it restarted itself then got stuck.
However once I turned the phone off and on again then went into recovery the new version allowed "MTP Device" to be recognized as a drive on my computer and I was able to copy over Misc_Tool_1.00.zip.
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Thank you both again for your time:good:

Syrup4 said:
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Click to expand...
Click to collapse
The tool Ive made will indeed hang if used with recent twrp version, sorry i forgot to mention that. So yes flash the 2.6.3.3 version and you should be able to use it without any problem. MTP isn't supported in 2.6.3.3 but you should be able to use "adb push" commands to transfer files, anyway I don't think you'll need any other file for now. Just change your version-main then relock your bootloader and flash the ruu.

Syrup4 said:
THANK YOU.
There has been progress.
So I installed the new TWRP posted, version 2.8.7.0-m7.
At first it said signature checking failed, so I booted the token thing from HTCDev again.
It then allowed me to install the new TWRP.
When the new TWRP was installed it came up with a screen with errors in red. "Can't write to Cache" or something.
I was going to write them down but it restarted itself then got stuck.
However once I turned the phone off and on again then went into recovery the new version allowed "MTP Device" to be recognized as a drive on my computer and I was able to copy over Misc_Tool_1.00.zip.
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Thank you both again for your time:good:
Click to expand...
Click to collapse
First I would download the ruu suggested by Alray to your computer (if you haven't already) have it in the adb folder
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
7.17.661.7 ruu
Then
Just flash the older twrp like you did the installed version
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot-bootloader
then run the misc tool and change cid
Then
then flash the ruu (it will replace twrp and rom with stock versions)
use the "how to flash" instructions on the first page of ruu download page.
Note: you MUST use htc_fastboot. Download it and place in the adb folder.
phone will reboot and then continue when flashing the ruu, don't rush, will take 10-15 min