HTC One with TWRP and Cm10 brick

[MissDjinn]

This is, at least in my experience, the oddest crap for a phone to do.

Im working, phone is next to me on the charger. I receive and reply to a text, than a few minutes later press the top button on my mophie case to power the screen on to check the time, and it doesn't respond. At all, ever again.

I had been rooted and running CM for a solid few months without major issue. I had not made any changes, major or minor, to the phone in the previous several days.

At one point I plugged it into my computer. and got a message asking for QSUSB_Dload. (or something simiar). I tracked this down, downloaded and installed, with no change.

Im sending it back to HTC. In my reading I have come across posts from several people who had send unlocked phones in for this exact repair without issue.
I've also read a few people mentioning excessive time on a charger being the culprit, which got me thinking of the mophie juice pack. Before I use one again, I'd sure like to figure out what the bloody deal is.

 

[TheEgonSpengler]

This is, at least in my experience, the oddest crap for a phone to do.

Im working, phone is next to me on the charger. I receive and reply to a text, than a few minutes later press the top button on my mophie case to power the screen on to check the time, and it doesn't respond. At all, ever again.

I had been rooted and running CM for a solid few months without major issue. I had not made any changes, major or minor, to the phone in the previous several days.

At one point I plugged it into my computer. and got a message asking for QSUSB_Dload. (or something simiar). I tracked this down, downloaded and installed, with no change.

Im sending it back to HTC. In my reading I have come across posts from several people who had send unlocked phones in for this exact repair without issue.
I've also read a few people mentioning excessive time on a charger being the culprit, which got me thinking of the mophie juice pack. Before I use one again, I'd sure like to figure out what the bloody deal is.

Need so much more info.

M7what?
CM10.what?
Hboot soff/on version?
What happened when you plugged it in?

What version of all the things?

Sent from my One using Tapatalk

 

[MissDjinn]

ALL the things>?

Um...I didn't know anything came after the M7....? It's your standard HTC One, ATT. As it is now en route to the good folks at HTC, I cannot look at it to be sure.

Im fairly sure I was on CM10.2.

What other things would be important? I assure you I do not know the version number of all the apps that were on that bloody phone.

When I plugged it in, the computer made the I found something in my USB port noise...than just a second later played another noise. I had never ever heard it play that sound before.

It informed me that it was searching for those drivers I mentioned. When it couln't find them., I went out and got them installed. It didn't make a difference.

I tried to run the adb but it would not find the device. Small wonder, what with not having the proper drivers for it's current, jacked up state. I tried recovery., I tried mirroring the screen, nothing. the home and back lights are dead, LED is dead, screen is dead.


Yet., somehow, the computer recognizes something is there.
If anyone knows what the devil is did, I'd be pleased to know.

 

[TheEgonSpengler]

Um...I didn't know anything came after the M7....? It's your standard HTC One, ATT. As it is now en route to the good folks at HTC, I cannot look at it to be sure.

Im fairly sure I was on CM10.2.

What other things would be important? I assure you I do not know the version number of all the apps that were on that bloody phone.

When I plugged it in, the computer made the I found something in my USB port noise...than just a second later played another noise. I had never ever heard it play that sound before.

It informed me that it was searching for those drivers I mentioned. When it couln't find them., I went out and got them installed. It didn't make a difference.

I tried to run the adb but it would not find the device. Small wonder, what with not having the proper drivers for it's current, jacked up state. I tried recovery., I tried mirroring the screen, nothing. the home and back lights are dead, LED is dead, screen is dead.


Yet., somehow, the computer recognizes something is there.
If anyone knows what the devil is did, I'd be pleased to know.

I'm wondering if the battery wasn't dead. Not enough people are coughing up the fastboot getvar to be sure.

Sent from my One using Tapatalk

 

[MissDjinn]

Most assuredly...

I'm wondering if the battery wasn't dead. Not enough people are coughing up the fastboot getvar to be sure.

Sent from my One using Tapatalk

Most assuredly, the issue was not a dead battery. This I know to be true for several reasons --
60% charge when it went dead
On the OEM charger
left on the charger overnight with no change
no LED response when put on the charger.

 

[TheEgonSpengler]

Most assuredly, the issue was not a dead battery. This I know to be true for several reasons --
60% charge when it went dead
On the OEM charger
left on the charger overnight with no change
no LED response when put on the charger.

The last charged state has nothing to do with the battery ability to discharge or recharge it can indicate the batteries health but is a piss poor measuring stick.

Batteries just go bad, 100% - 1% if a cell fails or something else goes wrong it's done no matter how much it's charged.

So no, you don't know unless you tested it.

I'm wondering if the battery wasn't dead. Not enough people are coughing up the fastboot getvar to be sure.

Sent from my One using Tapatalk

Sent from my One using Tapatalk