[Q] Stuck in Bootloader Loop after Critically Low Battery - T-Mobile HTC One (M7)

My T-Mobile HTC ONE M7 had very low battery life and eventually died before I could get to my charger. When I plugged it in and attempted to turn it on this screen appeared on my phone:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jun 21 2013,20:19:45:9912
After doing quite a bit of research it appears as if my phone is stuck in a "bootloader loop". I left the phone on the charger last night and I have tried rebooting from this menu and even a factory reset however all the phone does is power off and return to this screen. I have NOT tampered with the phone, have not attempted to unlock or root it, or any other type of modification. I work for T-Mobile and know well enough that doing so would void any warranty. Which is why I am troubled by the fact that it states *** TAMPERED *** (otherwise I would have just performed a simple warranty exchange, however due to the tampered tag I have feeling they would reject my claim)
Any assistance would be greatly appreciated! Has this happened to anyone else with a critically low battery?

---

ohbeeasy said:
My T-Mobile HTC ONE M7 had very low battery life and eventually died before I could get to my charger. When I plugged it in and attempted to turn it on this screen appeared on my phone:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jun 21 2013,20:19:45:9912
After doing quite a bit of research it appears as if my phone is stuck in a "bootloader loop". I left the phone on the charger last night and I have tried rebooting from this menu and even a factory reset however all the phone does is power off and return to this screen. I have NOT tampered with the phone, have not attempted to unlock or root it, or any other type of modification. I work for T-Mobile and know well enough that doing so would void any warranty. Which is why I am troubled by the fact that it states *** TAMPERED *** (otherwise I would have just performed a simple warranty exchange, however due to the tampered tag I have feeling they would reject my claim)
Any assistance would be greatly appreciated! Has this happened to anyone else with a critically low battery?
Click to expand...
Click to collapse
I just exchanged my first One for case issues, but it also happened to crash to 0% battery several times (due to Google services wakelocks). In no instance did it crash hard enough to ruin the entire phone.
So...I'm going to be cynical first:
TAMPERED usually comes up once you have flashed a custom partition (recovery, so on...), and the Security Warning *typically* occurs when you try to re-lock your HTCDev-unlocked phone while you still have your custom recovery installed (you have to reflash a stock recovery before attempting a re-lock). If you had done something in the past and relocked your bootloader to bring it back to 'stock' without restoring your recovery, you would see things like this. The solution would be to unlock the bootloader again, flash stock recovery, then relock.
But since you have never done anything like that:
It's *possible* that your phone shut down in a very awkward/damaging way and now doesn't recognize the signature of your never-modified OS--that would require that there was damage or corruption across the non-OS partitions. If that's the case, then you could try to reload an official RUU yourself (if you had the appropriate software to do so, which you would need to get...), or take it to a T-Mobile location and ask them to try to push a new stock image to your phone. As long as you are able to see menu options under those warnings that you can navigate with the volume buttons, then the stock ROM should be able to reload all those 'tampered' partitions. If that doesn't work, though, you'd have to take your chances with T-Mobile support.

---

tuxkamen said:
I just exchanged my first One for case issues, but it also happened to crash to 0% battery several times (due to Google services wakelocks). In no instance did it crash hard enough to ruin the entire phone.
So...I'm going to be cynical first:
TAMPERED usually comes up once you have flashed a custom partition (recovery, so on...), and the Security Warning *typically* occurs when you try to re-lock your HTCDev-unlocked phone while you still have your custom recovery installed (you have to reflash a stock recovery before attempting a re-lock). If you had done something in the past and relocked your bootloader to bring it back to 'stock' without restoring your recovery, you would see things like this. The solution would be to unlock the bootloader again, flash stock recovery, then relock.
But since you have never done anything like that:
It's *possible* that your phone shut down in a very awkward/damaging way and now doesn't recognize the signature of your never-modified OS--that would require that there was damage or corruption across the non-OS partitions. If that's the case, then you could try to reload an official RUU yourself (if you had the appropriate software to do so, which you would need to get...), or take it to a T-Mobile location and ask them to try to push a new stock image to your phone. As long as you are able to see menu options under those warnings that you can navigate with the volume buttons, then the stock ROM should be able to reload all those 'tampered' partitions. If that doesn't work, though, you'd have to take your chances with T-Mobile support.
Click to expand...
Click to collapse
Thanks for your response, I probably should have mentioned that this device is not new, it was a replacement device through Asurion as the result of the insurance claim. So it sounds like whoever may have had the phone previously may have done some "tampering". The phone eventually cut off and has refused to turn on entirely. I went to T-Mobile and had an assistant manager memo the account with the information I provided above. I'm familiar with the bootloading screen but have never seen it not respond like mine was doing. I'm going to read up on the forums and see if I can become a little more familiar with the process so I can learn how to fix something like this in the future. Thanks for your quick reply!

---

ohbeeasy said:
Thanks for your response, I probably should have mentioned that this device is not new, it was a replacement device through Asurion as the result of the insurance claim. So it sounds like whoever may have had the phone previously may have done some "tampering". The phone eventually cut off and has refused to turn on entirely. I went to T-Mobile and had an assistant manager memo the account with the information I provided above. I'm familiar with the bootloading screen but have never seen it not respond like mine was doing. I'm going to read up on the forums and see if I can become a little more familiar with the process so I can learn how to fix something like this in the future. Thanks for your quick reply!
Click to expand...
Click to collapse
Try flashing the RUU. but since you are 1.44 can your revone and s-off first?
I would s-off before RUU.