Database Develop

[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.

Soft brick (i think?) help please :(

Sorry i know this has been done a million times before but i cant seem to find anything that helps in my particular situation already. ill explain a bit what happened first exactly, my phone recently crapped itself and i sent it to the carrier for repair, they gave me a refurbished one that is faulty (gets really hot after about 20 min of use and restarts itself). anyways after a big headache of trying to send it back which is not really important here, i gave up and decided since i dont care enough about this phone to pay to fix it i can try and root it and hopefully install a rom that might keep the cpu cool and not reset so often (not sure if possible but it seemed harmless to try). anyways i unlocked the bootloader, installed CWM and not sure why but when i restarted the phone itll start up fine as if the first tiem you ever use the phone but you couldnt do anything after the set up. it just links to some site and you cant move at all or click anything its stuck. so i thought id install a ROM and hopefully fix it (decided on Maximus HD) im pretty sure i downloaded from here too so hopefully legit and now i cant even get into the menu at all. it gets stuck on the HTC boot logo unless i get into the bootloader which i still thankfully can and also into recovery. anyways i flashed TWRP just now in the hopes i can get an option in that to fix it that CWM doesnt have but still cant find anything and lot of the stuff i tried picking said "unable to flash s:" or somethng like that. same thing since isntalling TWRP though if i try restarting phone just to get into menu it hangs on the HTC logo screen i can only get into bootloader/recovery mode. what can i do? I still have s-on if thats relevant (probably that was the problem to begin with?)

misticknight1 said:
Sorry i know this has been done a million times before but i cant seem to find anything that helps in my particular situation already. ill explain a bit what happened first exactly, my phone recently crapped itself and i sent it to the carrier for repair, they gave me a refurbished one that is faulty (gets really hot after about 20 min of use and restarts itself). anyways after a big headache of trying to send it back which is not really important here, i gave up and decided since i dont care enough about this phone to pay to fix it i can try and root it and hopefully install a rom that might keep the cpu cool and not reset so often (not sure if possible but it seemed harmless to try). anyways i unlocked the bootloader, installed CWM and not sure why but when i restarted the phone itll start up fine as if the first tiem you ever use the phone but you couldnt do anything after the set up. it just links to some site and you cant move at all or click anything its stuck. so i thought id install a ROM and hopefully fix it (decided on Maximus HD) im pretty sure i downloaded from here too so hopefully legit and now i cant even get into the menu at all. it gets stuck on the HTC boot logo unless i get into the bootloader which i still thankfully can and also into recovery. anyways i flashed TWRP just now in the hopes i can get an option in that to fix it that CWM doesnt have but still cant find anything and lot of the stuff i tried picking said "unable to flash s:" or somethng like that. same thing since isntalling TWRP though if i try restarting phone just to get into menu it hangs on the HTC logo screen i can only get into bootloader/recovery mode. what can i do? I still have s-on if thats relevant (probably that was the problem to begin with?)
Click to expand...
Click to collapse
s-on is nothing to do with it, as long as your bootloader is unlocked, that's enough to flash custom roms.
TWRP is required to flash custom sense based roms, which version of TWRP depend on which rom you are trying to flash, so Lollipop based sense roms require TWRP 2.8.6.0, whereas the later ones require TWRP 2.6.3.3
after flash recovery, be sure to erase the cache and reboot the bootloader before trying to enter recovery, this clears anything that the previous recovery may of left behind, reboot bootloader is basically for changes to take effect, so your commands should look like this:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
when you enter recovery, personally in your situation, I would go into wipe, and select the format data button, this will wipe everything off your phone including the internal storage, so be sure to backup anything you need first, you can do this with the adb pull /sdcard/0 command from the recovery main screen. once the format is complete, reboot back into recovery again, and adb push or copy a rom to your internal storage, be sure to unplug your phone now and then flash it, also be sure to select full wipe during the installation.
you can only really use lollipop based custom roms if you are on lollipop firmware, people on lower firmware are reporting problems like no wifi, Bluetooth etc, so it would be helpful if you post your fastboot getvar all without your imei and serial number.

how do i get that? and i am using twrp 2.8.6.0.

misticknight1 said:
how do i get that? and i am using twrp 2.8.6.0.
Click to expand...
Click to collapse
well you know how to use fastboot commands, so with the phone booted in the bootloader and fastbootUSB showing on the screen and plugged into the computer the command is fastboot getvar all post the output here without imei and serial number.

Sorry took so long to respond to my own topic i was at work. heres the results:
(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.21.980.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Bump

Sorry i know this is annoying but one more bump before i let it die just want to know if its even possible to fix my phone.

misticknight1 said:
Sorry i know this is annoying but one more bump before i let it die just want to know if its even possible to fix my phone.
Click to expand...
Click to collapse
First step go into TWRP / Wipe / Advanced / Format Data ... type yes
when it's done go to Reboot / Recovery
now download and install this Rom >> https://www.androidfilehost.com/?fid=23991606952602541
during install choose Wipe system
the phone will take almost 10 min to boot ..wait on it and be patient

I'm trying to copy the zip file onto the phone but even though the computer reads it it says "cannot copy device has either stopped working or been removed".

misticknight1 said:
I'm trying to copy the zip file onto the phone but even though the computer reads it it says "cannot copy device has either stopped working or been removed".
Click to expand...
Click to collapse
unplug and replug in the phone and start over ... don't let it sleep

Nevermind found out it hadn't completed properly, redownloading now hopefully it should be alright.

Thanks heaps it worked

misticknight1 said:
Thanks heaps it worked
Click to expand...
Click to collapse
Great !!

Spoke a bit too soon used it for a bit now it still resets I guess that's a hardware problem for sure now though and not much I can do about it unless I take it to a pro.

"Active cmdline overflow!"

Hi there, I must have flashed the wrong sense ROM. I am extremely noobish, so bare with me.
I tried following this amazing guide: http://forum.xda-developers.com/showthread.php?t=2739126 but have had no luck when it comes to flashing the recovery indicated.
"C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
error: cannot load 'twrp-recovery-2.7-m7-nobcb.img'"
It looks like I entered it right...
My phone will power on and function OK with data and text, but cannot make calls. Sometimes it'll reboot into hboot when I plug it into USB/AC. I have access to fastboot, but not adb, nor recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: `
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35...
(bootloader) imei: 3559...
(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: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time, XDA!

Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk

cyrusct82 said:
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes and it shows under "fastboot devices"

It's now managed to have gotten worse and will only boot into the spash screen, then Fastboot (not Hboot).
If I remove the sim card, it will boot up normally (unless it's plugged into USB/AC). If I insert the sim, or plug in the microUSB, it will shortly thereafter crash into fastboot.

1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted

nkk71 said:
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
Click to expand...
Click to collapse
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!

Enigmatic Fart said:
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Click to expand...
Click to collapse
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy

nkk71 said:
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
Click to expand...
Click to collapse
Cool man, I'll run through and try to flash it again in the meantime and edit this post with results.
Thanks again for your help! Peace!
EDIT: OK, I see what the issue was, but a new one popped up. So I was attempting to flash the recovery I placed in my phone's storage. I now have "TWRP.img" (latest TWRP) and "TWRPnbcb.img" (the no bcb one from that guide) in my adb folder (where fastboot is) on my PC and have attempted to flash both recoveries for S&Gs.
Here are the results:
"C:\Windows\system32>cd C:\adb
C:\adb>fastboot devices
HT35xxxxxx... fastboot
C:\adb>fastboot flash recovery TWRPnbcb.img
sending 'recovery' (11278 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
C:\adb>fastboot flash recovery TWRP.img
sending 'recovery' (12534 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s"

Last ditch bump! I don't want my phone retire in a junk drawer!

Enigmatic Fart said:
Last ditch bump! I don't want my phone retire in a junk drawer!
Click to expand...
Click to collapse
please post a "fastboot oem last_dmesg", after trying to flash something
@alray, might be able to decipher that
(sorry for the ping)

802W China Unicom hard bricked

With my Htc One M7 802w, I tried to flash the stock google edition using this tutorial but I think i've bricked my device - it's almost completely dead - only fastboot is working but it also seems to be unrecognized :
F:\Android\ADB>fastboot devices
???????????? fastboot
Click to expand...
Click to collapse
Not able to go to "fastboot oem rebootRUU" ... the device is not found when sending this command.
Is there anyway to flash the stock ROM without fastboot mode - like some software or brushtool or whatever.
GETVAR:
F:\Android\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 3551*********10 (hide for security)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3385mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
F:\Android\ADB>fastboot flash hboot hboot_signedbyaa.img
target reported max download size of 452980736 bytes
sending 'hboot' (2047 KB)...
OKAY [ 0.109s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.109s
Click to expand...
Click to collapse
F:\Android\ADB>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
NEED HELP!!!:silly:

hruaiapunte said:
With my Htc One M7 802w, I tried to flash the stock google edition using this tutorial but I think i've bricked my device - it's almost completely dead - only fastboot is working but it also seems to be unrecognized :
Not able to go to "fastboot oem rebootRUU" ... the device is not found when sending this command.
Is there anyway to flash the stock ROM without fastboot mode - like some software or brushtool or whatever.
GETVAR:
NEED HELP!!!:silly:
Click to expand...
Click to collapse
omg looks like you did everything possible to brick your phone. Yuu can't use RUU for the M7_UL on a dual sim phone. Now you have the wrong bootloader, an incorrect MID and a missing CID. You must restore your original MID and CID and flas the correct dual sim RUU.
btw it looks like you missed the last step of your guide:
Step 8: Enjoy S-OFF! But Be Careful...
Having S-OFF will let you trick your HTC One into installing other phones' RUU files. As long as you only install compatible RUUs, you should be fine, but make sure to double check. This is how real bricks happen.
Click to expand...
Click to collapse

alray said:
omg looks like you did everything possible to brick your phone. Yuu can't use RUU for the M7_UL on a dual sim phone. Now you have the wrong bootloader, an incorrect MID and a missing CID. You must restore your orinial MID and CID and flas the correct dual sim RUU.
btw it looks like you missed the last step of your guide:
Click to expand...
Click to collapse
How to flash those original MID and CID? Is there a way to flash via software like ODIN or whatever...not just a fastboot mode? Thanks for your reply

hruaiapunte said:
How to flash those original MID and CID? Is there a way to flash via software like ODIN or whatever...not just a fastboot mode? Thanks for your reply
Click to expand...
Click to collapse
Odin is for samsung not htc. The corrupted CID/MID is probably caused by having the wrong bootloader on the phone. Normally you can change the CID using "fastboot oem writecid" command. The MID can be modified using a custom recovery. The MID might not be a problem for now since its all * but you'll definitively need to access RUU mode to flash the correct RUU

alray said:
Odin is for samsung not htc. corrupted CID/MID is probably caused by having the wrong bootloader on the phone. Normally you can change the CID using "fastboot oem writecid" command. The MID can be modified using a custom recovery. The MID might not be a problem for now since its all * but you'll definitively need to access RUU mode to flash the correct RUU
Click to expand...
Click to collapse
Yes, i know odin is for samsung, what i tried to say is that are there any flash tool, not through fastboot because as i already mentioned, computer cannot detect the device when
fastboot oem rebootRUU
Click to expand...
Click to collapse
command was given. It says
<waiting for device>
Click to expand...
Click to collapse
and i have to disconnect the USB cable. And then press a volume down+power button to enter fastboot mode again (when i perform this, the device does not power up, it for l goes directly to fastboot mode when pressing the key combination). And after plugin, the result was
*i didn't remember some* remote not allowed something like that
Click to expand...
Click to collapse
Anyway thanks for your response. Please give solution.

hruaiapunte said:
Yes, i know odin is for samsung, what i tried to say is that are there any flash tool, not through fastboot because as i already mentioned, computer cannot detect the device when
command was given. It says
and i have to disconnect the USB cable. And then press a volume down+power button to enter fastboot mode again (when i perform this, the device does not power up, it for l goes directly to fastboot mode when pressing the key combination). And after plugin, the result was
Anyway thanks for your response. Please give solution.
Click to expand...
Click to collapse
Theres no such tool for HTC phones, you must use fastboot. <waiting for device> when using fastboot commands means the computer doesn't detect the phone so even if there was a tool like Odin for HTC phones, it wouldn't work without being able to detect the phone. (there are actually some custom tools but they are only doing the fastboot commands for you by clicking a button instead of writing the commands yourself, they won't work if your phone isn't detected)
Usually, these fastboot connectivity issues are caused by using the wrong drivers, a bad usb cable, bad usb port etc. But i'm afraid that in your particular situation, your connectivity issue might be related to having the wrong bootloader installed on your phone variant. If this is the case, there is nothing you can do yourself. It might be recoverable using Jtag/ riffbox.
Still worth trying the usual troubleshooting (drivers, cables, ports(use only usb 2.0 btw). If you can get fastboot connectivity back, there are some (slim) chances to recover the phone, but without fastboot connectivity, like I said, there is nothing we can do.

alray said:
There no such tool for HTC phones, you must use fastboot. <waiting for device> when using fastboot commands means the computer doesn't detect the phone so even if there were a tool like Odin for HTC phones, it wouldn't work without being able to detect the phone. (there are actually some custom tools but they are only doing the fastboot commands for you by clicking a button instead of writing the commands yourself, they won't work if your phone isn't detected)
Usually, these fastboot connectivity issues are caused by using the wrong drivers, a bad usb cable, bad usb port etc. But i'm afraid that in your particular situation, your connectivity issue might be related to having the wrong bootloader installed on your phone variant. If this is the case, there is nothing you can do yourself. It might be recoverable using Jtag/ riffbox.
Still worth trying the usual troubleshooting (drivers, cables, ports(use only usb 2.0 btw). If you can get fastboot connectivity back, there are some (slim) chances to recover the phone, but without fastboot connectivity, like I said, there is nothing we can do.
Click to expand...
Click to collapse
Thanks for the clarification. I now have only one choice that is to send to the service center.

Trying to load an RUU to my soft-bricked VZW htc one

I've been looking for all over google for a signed RUU that I can flash to my phone through ADB. The phone goes to a bootloop when I try to boot normally. It got water damaged and recently I've been able to get back into the bootloader and have the device communicate with my pc, so I have hope. Here is my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA441S903495
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(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!
Click to expand...
Click to collapse
My bootloader is locked and USB debugging is off and the phone is S-ON, so I keep getting signature verify failures when I try to flash TWRP recovery or any RUU package. HTC doesn't seem to have an official RUU for the Verizon version of the phone for some reason. I did try to run the package I found here: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442 but the ARUwizard always gets a failure message that says the side-by-side configuration is incorrect, despite having updated my C++ visual packages. I've cleared my cache and the RUU's I've tried have failed, so I think I just need an official firmware that matches my phone, but I don't know where to find that.

Williamck said:
I've been looking for all over google for a signed RUU that I can flash to my phone through ADB. The phone goes to a bootloop when I try to boot normally. It got water damaged and recently I've been able to get back into the bootloader and have the device communicate with my pc, so I have hope. Here is my phone:
My bootloader is locked and USB debugging is off and the phone is S-ON, so I keep getting signature verify failures when I try to flash TWRP recovery or any RUU package. HTC doesn't seem to have an official RUU for the Verizon version of the phone for some reason. I did try to run the package I found here: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442 but the ARUwizard always gets a failure message that says the side-by-side configuration is incorrect, despite having updated my C++ visual packages. I've cleared my cache and the RUU's I've tried have failed, so I think I just need an official firmware that matches my phone, but I don't know where to find that.
Click to expand...
Click to collapse
Just a quick FYI. TWRP signature fail is because your bootloader is locked. You must unlock the bootloader to flash any custom software. Never mind TWRP for now. You need the bootloader locked to flash an ruu.
Try this RUU. https://www.androidfilehost.com/?fid=24052804347761412 It's in zip form so you'll need to manually flash it with htc_fastboot which you can download here https://www.androidfilehost.com/?fid=95916177934550031.
Download both files. Rename the ruu zip file to "ruu" then copy both htc_fastboot and the ruu to your fastboot folder.
Boot the phone to fastboot usb mode in the bootloader. Then flash the ruu with the following commands.
Code:
fastboot erase cache
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
The progress bar on the phone screen won't quite reach 100% that's normal. As long as the command window has finished it's output with a successful message your good.
Code:
fastboot reboot-bootloader
Select reboot from the bootloader menu :fingers-crossed:
Obviously with water damage there's no telling if it will still boot but let me know how it goes. :good:
Sent from my HTC One M9 using Tapatalk

Thanks for the quick reply! I followed your steps and something went wrong. The first flash failed due to an h-boot pre-update, but the process restarted immediately and seemed to be going well. The progress bar was almost completely full when I got this error:
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
(bootloader) start image[emmc_fw32] unzipping & flushing...
FAILED (status read failed (Too many links))
Execution time is 71(s)
Click to expand...
Click to collapse
I got an error message from my pc saying that htc_fastboot stopped working and needed to close. My phone shut off for a second and then restarted in rebootRUU mode like before, with a black background and silver htc logo, but now it has small caution symbols in all four corners.

Williamck said:
Thanks for the quick reply! I followed your steps and something went wrong. The first flash failed due to an h-boot pre-update, but the process restarted immediately and seemed to be going well. The progress bar was almost completely full when I got this error:
I got an error message from my pc saying that htc_fastboot stopped working and needed to close. My phone shut off for a second and then restarted in rebootRUU mode like before, with a black background and silver htc logo, but now it has small caution symbols in all four corners.
Click to expand...
Click to collapse
OK well the pre-update fail is normal. This is the bootloader being updated before the firmware is flashed.
The caution symbols in ruu mode are because the RUU did not complete. Strange that it stopped where it did though.
It may be that emmc is damaged and not writable. Try flashing the ruu again. Hopefully it will complete. If not check to see if it ends at the same point.
Also make sure your using a USB port at the back of your PC not the front ones. :good:
Sent from my HTC One M9 using Tapatalk

The flash worked completely this time, but the phone is still stuck in a bootloop. The phone has new variables from the flashed RUU, so at least there's that. I still can't boot normally or into recovery. I tried a factory reset from the bootloader menu to try to clear caches and this just leads back to a bootloop

Williamck said:
The flash worked completely this time, but the phone is still stuck in a bootloop. The phone has new variables from the flashed RUU, so at least there's that. I still can't boot normally or into recovery. I tried a factory reset from the bootloader menu to try to clear caches and this just leads back to a bootloop
Click to expand...
Click to collapse
Well as I said with water damage there's always the possibility there is hardware damage inside the phone.
If the ruu has flashed then all the software is restored to stock condition. Which only leaves hardware.
What method did you use to dry the phone? And for how long?
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
Well as I said with water damage there's always the possibility there is hardware damage inside the phone.
If the ruu has flashed then all the software is restored to stock condition. Which only leaves hardware.
What method did you use to dry the phone? And for how long?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I dried it in a tub of rice for about a month. It took a while to even turn on at all.
Could you go into a little more specifics, if you know, as to what exactly got damaged? I mean the bootloader can run, a zip can be flashed, the battery can be charged, and adb can report the internal partitions of the phone. So what is damaged, and can it be repaired or replaced?

I'm in the same boat. However does the "htc_fastboot" really differ from the one supplied by the android SDK? When I try to go into RUU mode, it simply reboots, could this be attributed to the wrong fastboot?

hansbogert said:
I'm in the same boat. However does the "htc_fastboot" really differ from the one supplied by the android SDK? When I try to go into RUU mode, it simply reboots, could this be attributed to the wrong fastboot?
Click to expand...
Click to collapse
The difference is Google's generic fastboot can't handle zip files larger than 1.5gb.
Most HTC lollipop and Marshmallow ruu's are all 1.6gb up-to 2.2gb. So you have to use htc_fastboot to flash them because it's designed to flash larger files.
Sent from my HTC One M9 using Tapatalk

Williamck said:
I dried it in a tub of rice for about a month. It took a while to even turn on at all.
Could you go into a little more specifics, if you know, as to what exactly got damaged? I mean the bootloader can run, a zip can be flashed, the battery can be charged, and adb can report the internal partitions of the phone. So what is damaged, and can it be repaired or replaced?
Click to expand...
Click to collapse
Yeah in rice is the best way normally for a day or two is enough. I guess it for quite wet?
To be honest it could be anything. A spot of corrosion in the right place could do it.
But without opening the phone it's impossible to know exactly what damage if any the water has caused.
The ruu you've flashed is officially signed from HTC. The same package the service center would use to restore the device. That's why I say it's unlikely to be a software issue.
Out of interest how long did you wait for the phone to boot, it can take up-to 20mins for first boot after flashing an ruu. The phone will hang on the HTC logo for 20mins+ before starting the app optimization.
Sent from my HTC One M9 using Tapatalk

It wouldn't give any indication of working at all, on the order of a week maybe. After that it started to show a generic charging symbol on the screen when plugged in, although no progression bar for charge, and the light would turn green but that's it. Only after several weeks would the screen start to show that the battery actually was charging, with a percentage, and turn on into bootloader.
So yeah, I think it must be pretty damaged. Now when I try to turn it on, like I said, it's a bootloop. the htc logo stays for a while but eventually it turns itself off and back on, again to the logo.
I think I'll try to open the back and see what it looks like...I've read that cleaning the logic board with alcohol will clear the buildup of contaminants from the river water, which could be causing this weird stuff to happen.