Database Develop

Bionic is Not Turning On.

It's not rooted and doesn't have anything on it. Pretty much stock. Sent a text msg this morning and checked my email from it. Came back to it abt 20 minutes later and it won't even turn on. Tried charging it. Won't turn on. Tried swapping with my regular battery (which was fully charged when I put it away. It could be dead by now.). Nothing. Tried removing the battery, waiting, replacing the battery. Nothing. I did briefly get the M Dual Core icon and then all went blank.
Suggestions?

Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD

rduckwor said:
Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD
Click to expand...
Click to collapse
I second this.

Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
idefiler6 said:
I second this.
Click to expand...
Click to collapse
rduckwor said:
Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD
Click to expand...
Click to collapse
Thanks, all.. Hauled my cookies 30 minutes over to Verizon. The sales rep assumed I hadn't bothered to charge my phone. When he realized it wasn't the battery, he was extremely helpful and replaced the phone on the spot. He said he'd never seen that before and with a phone less than 1 month old, I shouldn't have those kinds of issues. Kudos to Verizon for a pleasant experience. I've had some bad experiences in the past, but this gentleman was helpful and didn't try to sell me any accessories! ;p (They always try to sell me something when I'm there.)

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
This is referencing what one would do if the software had an issue, if it does this will fix it but kinda sounds like hardware. I have returned my Bionic to stock twice its fairly easy, computer does almost everything. Here is this to get you going if you wanna do it.
http://forum.xda-developers.com/showthread.php?t=1262540
Just remember, phone has to be in fastboot mode to be detected by RSD Lite and once its detected and the file starts flashing, if it seems like its not making progress while saying otherwise, dont unplug it just wait
Sent from my DROID BIONIC using xda premium

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
One would need the ability to turn the phone on in the first place for this to be attempted. That's why no one was mentioning the FXZ.

The phone booted to the dual core M logo, which with myself that happens to be as far as mine would go when i successfully flashed my FXZ. The phone needs to boot to the fastboot screen which can be done on many occasions that the phone can get to the first logo, as long as there is battery left.
....
But congrats on the new replacement i just saw that after i posted
Sent from my DROID BIONIC using xda premium

It hasn't happened to me but I have to pull the battery on my wifes Bionic at least once a week and twice in one day. It would just go away suddenly and act like it was dead. I may return it for a replacement.

if anyone has exchanged their Bionic for a replacement because of the BSOD defect, will you please provide feedback in this thread? thanks

hi all:
just bought a bionic off ebay for cheap ($20 + free ship) but it has problems
it was being sold as "battery with water damage but phone is not but wont power on"
he said one night he left it in his drawer and when he woke up it didn't work anymore he tried removing battery and all that.
to my understanding the battery was previously water damaged and he could still use it and then got the wont power on later on.
anyhow to my question
the phone comes today with just the phone, water damaged battery and wall charger.
should I cut the end off the charger and do the wires to the battery and insert battery into phone and plug usb cord from laptop to the phone?
isn't this the correct way for bsod and a non water damaged battery?
is there anyway to test the waterdamaged battery to see if it could still be good?
I have a multimeter

[Q] Bionic won't turn on at all...

I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?

Creepazoid said:
I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?
Click to expand...
Click to collapse
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium

mistawolfe said:
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.

Creepazoid said:
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.
Click to expand...
Click to collapse
I wasn't being sarcastic, however this is me now saying you're probably screwed.
Sent from my DROID BIONIC using xda premium

Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?

Haha, alright, well thanks again for the heads up on the one-click, definitely going to come in handy in the future.
Sent from my MB860 using XDA App

beidave said:
Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?
Click to expand...
Click to collapse
He said he's tried a few different batteries.
Sent from my DROID BIONIC using xda premium

So what was the verdict? Mine just did the same thing. However, I Have followed all of the directions everytime i've flashed and never had an issue til right now.

If you can't get the phone on at all, no fastboot or anything. No hardware buttons do anything, nothing comes up on the screen with anything you try....
That's a hard brick.
= requires a new phone
No way to fix it.

Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.

When I messed up my flash and my phone was stuck at the dual-core logo, I followed the steps below.
Pull your battery.
When you put it back in, hold down the power and volume down to access fastboot mode.
From there you can do a one-click restore method.
That is how I solved my problem. I hope it helps you.
Sent from my DROID BIONIC using xda premium

nickbeisher said:
Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.
Click to expand...
Click to collapse
have you triedf pulling the battery and putting it back in. the hold volume key down and power at the same time? if that works then just restore using fxz. if it does not work your phone is bricked

Brick!!
This is my third droid, I had The D1, the X, and now the bionic. By far I like this one much better than the the others. I have rooted all of them, and done the basic app freezing, overclocking, and other basic mods. This is my first go round with the custom rom flashing. I Flashed R3blurr3d, and every new update ( each update a new flash ). I also flashed D3blurr3d, and Liberty, just to check them out. I personally like Reblurr3d. When I flashed I always followed every direction to the letter, and if I was unclear on something rather than ask a stupid question, or ask something that had already been covered. I read and search until I find the answer I need and it is clear to me, sometimes that means searching for hours on end. I do this for the fear of ending up with a "Brick".
Now with everything I have read about any of these phones to "Brick" It is an error on the user's end while flashing or something of that sort, ( not following directions ).
So with everything operating butter smooth, and flashing dozens of times before this. What would cause a "Brick" during everyday use?

My guess is....he didn't know what he was doing. You rooted it for him and left it rooted for a user that knows nothing about root access. He probably did something using root access to fck something up.
When someone asks you to root their phone for them, the answer is always no.
Unless they know what they're doing, never give someone root access.

my first bionic did same thing. it was not rooted yet. just started rebooting it self. got more frequint then just quit the way you talked about. hardware problem.

Yes. That is what it is. It is a hardware issue, after talking to tech support it is a capacitor or something like along those lines, it stores battery power for times when more power is needed, like turning on the phone for instance. And when it randomly boots it is because it runs short on power due to the faulty hardware.
But apparently it is a known issue with Verizon, so if it happens to anyone else they should not have any trouble getting a new phone. I talked to a very nice tech support agent, and I will have a new phone by noon on Saturday.
And also I didn't have anyone root my phone, I do all of it on myself, Im no computer genius, but like I said I take my time and follow directions. And until now I have had no issues, and this had nothing to do with root access, flashing custom rims, or any other tweaking just a bad part Anthe phone. The thread was started by someone else. When I searched the threads, I found this and it was the same exact problem as I had, so that's why I asked what the end result was.
So with all that being said maybe this will be informative to someone else.

[Q] Battery defect or just a bug?

Hey Guys,
I have been searching for hours now and cannot find anyone having the same or similar issues with the One as me
and I am really becoming desperate..
So, the problem is that I cannot charge the phone anymore, whenever I try to do so the battery symbol becomes grey with an exclamation mark.
I have no clue what the reasons for this are and why it occurs, also this is the second time now that this happens to me.
I have already sent it to the repair service 3 days after I bought the phone, this time it lasted around 3 weeks until it happened again.
So far I am loving the phone and its features, but this problem is driving me mad, any help would be appreciated!
Edit: it ran out of battery and now I can neither turn it on nor is it charging

Lazngann said:
Hey Guys,
I have been searching for hours now and cannot find anyone having the same or similar issues with the One as me
and I am really becoming desperate..
So, the problem is that I cannot charge the phone anymore, whenever I try to do so the battery symbol becomes grey with an exclamation mark.
I have no clue what the reasons for this are and why it occurs, also this is the second time now that this happens to me.
I have already sent it to the repair service 3 days after I bought the phone, this time it lasted around 3 weeks until it happened again.
So far I am loving the phone and its features, but this problem is driving me mad, any help would be appreciated!
Edit: it ran out of battery and now I can neither turn it on nor is it charging
Click to expand...
Click to collapse
Have you been using the provided charger? Sounds like they didn't change out the battery you got a bad one. I have never seen android do that unless the battery or something is really broken.

nullkill said:
Have you been using the provided charger? Sounds like they didn't change out the battery you got a bad one. I have never seen android do that unless the battery or something is really broken.
Click to expand...
Click to collapse
Yes, I used the charger provided which is working just fine with my previous One X and I also tried to use the charger of the One X without success though..

Lazngann said:
Yes, I used the charger provided which is working just fine with my previous One X and I also tried to use the charger of the One X without success though..
Click to expand...
Click to collapse
Yeah it's bad. Too weird. You are not alone a couple other people are having this issue just this morning. Like four or so ONES decided they would all just say goodbye at the same time. It's odd as I have not seen any other problems like this until this morning.
Guessing this is a DEV edition or you can't go to a carrier and have to go through HTC? If so make sure to tell them this device has already been in before for the same problem and at this point you want a new device not this defective one.

nullkill said:
Yeah it's bad. Too weird. You are not alone a couple other people are having this issue just this morning. Like four or so ONES decided they would all just say goodbye at the same time. It's odd as I have not seen any other problems like this until this morning.
Guessing this is a DEV edition or you can't go to a carrier and have to go through HTC? If so make sure to tell them this device has already been in before for the same problem and at this point you want a new device not this defective one.
Click to expand...
Click to collapse
I will do so as soon as I get back to Germany where i purchased it, as I'm still in London for studies until the end of may :crying:

The charging time is ver bad. I had the same thoughts at first. I changed the calbe and the charger... In Elixier2 i don`t have more than 500-700 mA... I charge the Phone overnight. But my Battery lasts more than two days

[Q] Did my phone brick itself?

I flashed Paranoid Android after wiping ARHD 10.2, everything installed perfectly, phone was working great until I was listening to Pandora and checking Facebook..then my SIM card became unreadable and I had to take it out and put it back in, when I turned my phone back on it had gone from 42 percent battery to 4 percent, then 2, then dead. I charged it for a little while before going out for dinner, I came home and it wouldn't turn on, and it won't charge now whatsoever.
What the ****?

Alright, this will sound silly but place the phone in front of a light so that the sensor picks it up then try to turn it on. Will have to hold the power button for a while but it should turn back on. Or, if it won't, also try booting into your hboot. Reason for this is so you can't accidently turn on your phone in your pocket or something like that. It's been a while since I read this, I could be wrong but this won't hurt your phone so just give it a try
Sent from my One using xda premium

g33mt4z said:
Alright, this will sound silly but place the phone in front of a light so that the sensor picks it up then try to turn it on. Will have to hold the power button for a while but it should turn back on. Or, if it won't, also try booting into your hboot. Reason for this is so you can't accidently turn on your phone in your pocket or something like that. It's been a while since I read this, I could be wrong but this won't hurt your phone so just give it a try
Sent from my One using xda premium
Click to expand...
Click to collapse
Light sensor trick didn't work. The phone won't even charge, let alone turn on.
I can't boot into recovery, nothing.

Have you tried a different charger, cable or wall port or all three?

TarekElsakka said:
Have you tried a different charger, cable or wall port or all three?
Click to expand...
Click to collapse
Yes, tried two chargers in two outlets along with USB only charging, none work. Both chargers worked this morning.

That happened to me today. Literally the exact same thing.
My solution:
Step 1. PANIC LIKE A MOTHA F******
Step 2. Contemplate spiking unibody sexiness into pavement because unibody is functionally retarded.
Step 3. Take a deep breath and remember why you love her...
Step 4. Hold down power button for 10 seconds or longer.
Step 5. Plug usb cable that came in your box into your device.
Step 6. Quit whimpering, people can hear you.
Step 7. Plug into PC. Watch for tiny red light at top of phone.
Step 8. Wait about 30 min.
Step 9. ??????
Step 10. PROFIT! !
Sent from my squash patch.

Followed your steps for 30 seconds of holding the power down, plugged in stock USB to phone, plugged into PC. Nothing. Black.
Sent HTC an e-mail, my phone shouldn't over-heat and brick while using Facebook and pandora and that's it. I'm about to swap this **** for a S4 and stop being a HTC fanboy. I'm upset.

Not every unit provided by manufacturer can be perfect. By the end of the day its electronics and something can go bad. If you feel s4 is better than get a s4. HTC One will be happy to leave you. I'm sorry for being rude and sarcastic but it is what it is.
Sent from my HTC One using xda app-developers app

You shouldn't quickly jump to conclusions in my opinion. Just get a replacement set and see how it goes. If it still has problems then you can go for S4 or whatever device is out there. Of course in the end it's your decision but I'm just saying that you shouldn't cloud your decision just because of one defective set.
Sent from my HTC One using Tapatalk 4 Beta

Bump, any other suggestions?

PapaRhino said:
Bump, any other suggestions?
Click to expand...
Click to collapse
Did you charge it overnight using the stock HTC charger and cable? That is about all I can thing of. Something in the ROM appears to have drained the battery flat, which is not normally possible.

This is device #4 that has died completely on a 10.1 rom

18th.abn said:
This is device #4 that has died completely on a 10.1 rom
Click to expand...
Click to collapse
Makes me wonder if they didn't do something to the safe charging capabilities, although I would think that stuff is in the hardware, not the ROM.

It seems if it was the base that's being used we would have a LOT of devices going down so can't really speculate the cause. I shouldn't have posted above in such a suggestive manner.

I don't imagine the rom would be stopping the phone from charging as the kernel etc is not loaded until after hboot, charging is dealt with well before this sequence in the boot process.
To be fair it sounds like a hardware failure, maybe an overheating issue, possible caused by the rom and many other factors but that's the risk you take flashing experimental 3rd party software to your device. I don't thing you will ever know, your not even getting a uart mode which to me says fried PCB..
Send it in for repair and play dumb

18th.abn said:
This is device #4 that has died completely on a 10.1 rom
Click to expand...
Click to collapse
Mine had the exact same too, using cm-10.1
Just overheated, drained dead and didnt want to turn on or charge anymore
Sent from my HTC One using xda premium

This is indicating that for the time being, there is something seriously wrong with 10.1 builds and it's dangerous to flash them...
It's a shame that the cause for the error cannot be found once the device is bricked...

Same with my phone. Using slimbean. Phone died and unfortunately htc said i installed 3rd party software and i need to pay the repairs.
I didnt know how they knew that i had a 3rd party software where my phone cant even charge or turn on
Sent from my HTC One using xda app-developers app

jadmask3rlm said:
Same with my phone. Using slimbean. Phone died and unfortunately htc said i installed 3rd party software and i need to pay the repairs.
I didnt know how they knew that i had a 3rd party software where my phone cant even charge or turn on
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You should raise that question with them to see if you can find out how they are getting the phone to turn on

MacHackz said:
You should raise that question with them to see if you can find out how they are getting the phone to turn on
Click to expand...
Click to collapse
I tried to ask them but they said they have somekind of hardware or software that can detect. Anyways im in a no win situation bec i knew all a long that if i flash 3rd party software its a goodbye to warranty
Sent from my HTC One using xda app-developers app

[Q] Sprint HTC One - Won't Boot - Won't Charge

The story is I was having a lot of general problems with my Sprint HTC One. I was using it with CyanogenMod 10.1 and I noticed it was getting VERY warm. I then noticed that the battery was at 21%, I had hardly used it all day. It would normally have been around 94% percent. So I was shocked. Then I noticed that is would make weird clicking and "eek" noises when I would browse the Operating system. It would make an especially annoying noise when I would turn on the LED Camera light. I also noticed that the battery would drop about 1 percent ever 30 seconds.
I immediately shut it off and plugged it into my charger (AC). I opened up ClockworkMod and wiped my cache and dalvik cache and then did a factory reset from ClockworkMod. The problems still occured. I then tried flashing an Earlier version of CyanogenMod 10.1. The problem still occured. So I let my battery charge up to 50% (it took a especially long to charge, it would actually lose a charge while charging at times) and then used RUU tool to flash it to Complete Stock. That got rid of the weird noises caused during the operating system use. But the battery continued to run hot and take especially long to charge (somtimes the battery level actually was dropping). I then installed an app to control the frequency of the CPU. It was set to always run at 1.7GHz. So I fixed that and made the minimum Frequency the lowest option and the Max Frequency 1.7GHz. That solved the charging problem.
I left it to charge over night and by the morning it was at 100%, so I unplugged it and turned it off. I thought I had solved everything. I left the phone alone for about 4 hours and when I checked on it, it would not boot whatsoever. I could not not even get into the Bootloader! Then I plugged it back into the charger to find out that the Orange charging indicator LED would NOT light up! So for now, it is just sitting in the charger without the charging indicator light lit up.
I would also like to mention that I am not the original owner. I bought this phone used. It does not have the normal Sticker on the back of the phone to indicate the Serial Number etc. And since I am not the original owner, I do not believe I qualify for a replacement warranty. Any help at all would be greatly appreciated. Thank you for your time.

this has been happening to alot of people
which of the nightlies did you flash?

flex360 said:
this has been happening to alot of people
which of the nightlies did you flash?
Click to expand...
Click to collapse
It was either the cm-10.1-20130731-NIGHTLY-m7spr (2013-07-31) build or the cm-10.1-20130730-NIGHTLY-m7spr (2013-07-30) build

Might need to go to sprint for a replacement
Sent from my HTCONE using Tapatalk 4 Beta

krazyflipj said:
Might need to go to sprint for a replacement
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Am I able to get a replacement even though I'm not the original owner?

ammuica said:
Am I able to get a replacement even though I'm not the original owner?
Click to expand...
Click to collapse
If you are under service they should. Phone is still under manufacturer warranty. If you don't have insurance, worst case scenario you pay $50 for a refurb/new phone. Of course that's if they can't repair
Sent from my HTCONE using Tapatalk 4 Beta

krazyflipj said:
If you are under service they should. Phone is still under manufacturer warranty. If you don't have insurance, worst case scenario you pay $50 for a refurb/new phone. Of course that's if they can't repair
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
It is not under service. I Bought it with the plan of not using it on a contract because I cannot afford a data plan, but I would still like to use an android smartphone.

Yeah just got and get a replacement for 50$ I was not the orginal owner and they got the serial number off they're system I got a refurbished one I think but it was in like brand new condition but now it seems the brick problem is still around
Sent from my HTCONE using Tapatalk 4 Beta

Alex1123 said:
Yeah just got and get a replacement for 50$ I was not the orginal owner and they got the serial number off they're system I got a refurbished one I think but it was in like brand new condition but now it seems the brick problem is still around
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
But will they still replace it if I'm not using it with a plan? I bought it from someone else and I never re-activated it.

I've called sprint and since I don't have the phone under my account and since it is not activated, they will not repair it. So a replacement/repair is out of the question. So is there anyway I can fix this myself? I'm familiar with flashing and all that stuff, so any of that stuff is just fine.

There is no way you can repair this yourself.
And eek! This problem's back? What? You were using the latest nightly too?
And since you have no warranty (pretty sure its non transferable), you should look up JTAG services. $60. It may not be as clean as you'd like, though. Besides, HTC repair service wouldn't fix your device for free because, even though the device is bricked, they can see your tampered boot loader. They charged me $200. I probably won't root again.
This has happened to at least a dozen people, but all if them were before July 3rd. This is kind of disturbing.

sauprankul said:
There is no way you can repair this yourself.
And eek! This problem's back? What? You were using the latest nightly too?
And since you have no warranty (pretty sure its non transferable), you should look up JTAG services. $60. It may not be as clean as you'd like, though. Besides, HTC repair service wouldn't fix your device for free because, even though the device is bricked, they can see your tampered boot loader. They charged me $200. I probably won't root again.
This has happened to at least a dozen people, but all if them were before July 3rd. This is kind of disturbing.
Click to expand...
Click to collapse
Hey, it's always worth a try. I always used the latest nightly. I updated whenever they pushed a new update. I had it running CyanogenMod 10.1 Nightly for over a month without a single problem. I've been using it on my Galaxy Nexus for over a year. This is the first time it's ever given me a problem.
I'll look into the JTAG, but if anyone else has any ideas I'm up to try anything. The bright light while holding Volume Down + Power didn't work for me.

OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T

Admiral Sir Manley Power said:
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Click to expand...
Click to collapse
I did know what I was doing. I was running a stock build flashed by RUU. So I assumed that it would have a decent frequency management (that should be a safe assumption). I know what I'm doing when it comes to android's. I'm not stupid enough to have the CPU running at the full 1.7 GHz. Immediately after it started getting warm again that was the first thing I checked. Normally I underclock my devices. I usually have my Galaxy Nexus run at 700 MHz. I've also been using Nightly builds for my Nexus for over a year and I've found it to be stable enough to decide to flash it on my HTC One. And until 2 nights ago, It was perfectly stable.
I've done no fault on my own. I personally blaim HTC for pumping out a ROM that let it run at 1.7GHz 24/7, even unrooted.

Also to include, while I was running CM 10.1 I had my CPU set to a minimum of ~300MHz (forget exact frequency) and a maximum of 1.7GHz. I'm not stupid enough to set it to run at 1.7GHz 24/7 for any reason whatsoever. I was shocked when I saw that it had been running at 1.7GHz 24/7 (had only been running for an hour in sleep mode at that point before I fixed it).

Admiral Sir Manley Power said:
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Click to expand...
Click to collapse
?
10.1 is very close to stable...
Except, you know, the bricking issue.
Where does it say the device was maxed out on purpose? Stock CM is supposed be pretty good at CPU management.
So now we know what is causing the bricks. The CPU is literally self destructing. We should have deck look into it.

I'm considering selling it to technollo.com . With a promo code, they will pay $70. I only payed $230, so I might as well just cut my losses.

ammuica said:
I'm considering selling it to technollo.com . With a promo code, they will pay $70. I only payed $230, so I might as well just cut my losses.
Click to expand...
Click to collapse
Really sucks man.
Again, just goes to show. If you can't afford to lose/fix your device, then you shouldn't be rooting it and stuff. HTC makes no guarantees that the phone will be able to run AOSP ROMs. The devs just do their best. Phones are getting more and more complicated, and it gonna get harder and harder to make stable ROMs for them.
Looks like this is your only option... maybe you can go and get yourslef an N5 when it comes out as a replacement?

sauprankul said:
Really sucks man.
Again, just goes to show. If you can't afford to lose/fix your device, then you shouldn't be rooting it and stuff. HTC makes no guarantees that the phone will be able to run AOSP ROMs. The devs just do their best. Phones are getting more and more complicated, and it gonna get harder and harder to make stable ROMs for them.
Looks like this is your only option... maybe you can go and get yourslef an N5 when it comes out as a replacement?
Click to expand...
Click to collapse
Well I think it's worth the risk. Usually I can fix nearly any software issue possible. However, this is a hardware issue. I love modifying my devices and I won't stop anytime soon. My Personal computer currently has full liquid loop (GPU + CPU) that I setup and maintain that I am proud of. Sometimes things just go wrong. That's no reason to give up. For now I'll just continue to use my Galaxy Nexus until I find it necessary to upgrade.
However if anyone would be interested in purchasing this HTC One from me, just message me and we could try to work something out.

ammuica said:
Well I think it's worth the risk. Usually I can fix nearly any software issue possible. However, this is a hardware issue. I love modifying my devices and I won't stop anytime soon. My Personal computer currently has full liquid loop (GPU + CPU) that I setup and maintain that I am proud of. Sometimes things just go wrong. That's no reason to give up. For now I'll just continue to use my Galaxy Nexus until I find it necessary to upgrade.
However if anyone would be interested in purchasing this HTC One from me, just message me and we could try to work something out.
Click to expand...
Click to collapse
I never asked you to stop rooting. It was just a PSA saying one should only root if one can afford to lose or fix one's device.
English is stupid.