Re: HTC One Stuck in Bootloader and Can't get into Recovery. HELP!!
GEEZ! I have this exact same issue. Caused by the battery dying as well. Stupidest hardware bug I have ever seen. My post is over here:
[Q] HTC One (T-Mobile) soft bricked - Page 9 - xda-developers
Did you ever get an answer or at least find out what it actually was? If I have to replace the damned thing I'd rather not waste more time fighting with it. Going on 3 days now. HTC told me to blow off or spend $250 because it was "tampered". Tmobile told me to blow off because of the same thing, but as far as I can tell this has happened to a TON of people on TMobile who havent even rooted. At my wits end here and tempted to take it to HTC real good legally since there is likely enough trail with others having this problem to PROVE its a hardware/design flaw.
Just read through you entire post over at xda. You have exactly the same problem as me except I never got mine into recovery. I tried flashing different version of TWRP and CWM but even when I tried CWM it tried to boot into TWRP and then boot looped. I didn't get it fixed since nothing worked. I tried RUU, All in one toolkit, flashing, etc and they all boot looped.
I filed a claim with Asurion and should get a new phone tomorrow. It was 150. Sprint is supposed to service rooted phone. I have a document saying so but they said no to me. They wouldn't even try when I said I would pay for the service since it would have been likely less than 150.
I would like to try that philz recovery but I don't think there is a compatible version for m7wls, I checked. As for the battery issue, did yours die extremely fast? and then you had to charge it up? Mine was fully charged, I went to school and after a 3 hr class I pulled my phone out only to notice it was dead. It wasn't glitchy at all that morning so a random battery fail and possibly causing damage to the phone makes perfect sense. I initially thought it had gone into a boot loop for a random reason and that's what killed the battery, but your discovery makes sense too.
Have you gotten any closer to get it running? The first thing you need to fix after the recovery is that boot loop issue and getting it locked. The boot loop is just going to screw you over every time you try a new approach.