Database Info

Little Emergence

ok im not that new to flashing i have flashed about 6 or 7 roms on my phone in the past. today i was running dutty's V4 and i have been running it since it came out to the public and today i went to read a txt message and the phone blacks out and i get a red light at the top but its only there when the phone is on a charger. i can not restart the phone at all.
dont know if it helps but i was running Dutty V4 with cube enabled also running s2u2 and thats about it as far as stuff that was running other than the rom itself. i really hope there is a fix to this. i have already tried to reflash but device is not found.

well crap... i hear the red light be nicknamed the red light of death... i hope to god there is a way around this... if not would att know i reflashed something else if i went in and started to complain?

i had a similar thing with my orange uk keiser and i just got orange to ghange it for a new one. that was over a month ago now and i have had no questions so far. if you cant get it to work then they cant either

gimini said:
ok im not that new to flashing i have flashed about 6 or 7 roms on my phone in the past. today i was running dutty's V4 and i have been running it since it came out to the public and today i went to read a txt message and the phone blacks out and i get a red light at the top but its only there when the phone is on a charger. i can not restart the phone at all.
dont know if it helps but i was running Dutty V4 with cube enabled also running s2u2 and thats about it as far as stuff that was running other than the rom itself. i really hope there is a fix to this. i have already tried to reflash but device is not found.
Click to expand...
Click to collapse
Have you tried to put it in Boot Loader mode? Can you do a hard re-set?

As posted above, this is referred to as "red light of death" - RLoD.
Rzanology had a potential fix for this involving removing battery cover and pumping battery up and down on battery contacts (battery cpr), that appeared to work for some folks - tried to find the thread but was unsuccessful. You might try pm'ing him.
If you are unable to resuscitate your device, most have simply returned it. Good luck!

apologies for the hijack (and sorry to hear that you're having problems) but I've always wondered what they check when you send it back for a fault repair.
Just wondering how many people have sent back their phones with hardSPL and custom roms still installed

well if it totally dead don't worry about sending it back with custom things flashed to it. most of the time they just hook it up to a charger and see if it will turn on and if not throw it in a bin of other messed up kaisers. I'm sure HTC knows about the red light of death and what makes it happen.

no biggie on the hijack
well im stil standing in att but obviously since im sending this I got a new phone. they tried to give me a loaner until they sent mine for repairs but when they offered me a 89.00 phone I laughed and told them my kaiser is worth more as a paer weight and that I run my bar from my phone and that their loaner wouldn't cut it. they then offered my an iPhone to replace it, telling me its a beter phone anyhow so I went to the magazine stand across the isle and showed the a mobile power magizine that has the tilt listed higher and also told them that I needed my 3g internet and also said look if ur willing to give me an IPhone why not a tilt. after about 10 mins talking to me I got my new tilt.
now omg I can not wait to get the htc today screen back and opera. ie sucks

austinsnyc said:
well if it totally dead don't worry about sending it back with custom things flashed to it. most of the time they just hook it up to a charger and see if it will turn on and if not throw it in a bin of other messed up kaisers. I'm sure HTC knows about the red light of death and what makes it happen.
Click to expand...
Click to collapse
So if I properly brick it they'll probably just replace it? Is there a guide on bricking anywhere

gimini said:
they then offered my an iPhone
Click to expand...
Click to collapse
bah... ruddy kiddes toy

apperently I dotn have trouble bricking one so just pretend ur me...but tbh if u want to brick it completely I would just replace the fuse in ur car charger with a much higher one and crank juice into the phone... but don't put too much into it burn chipsets smell horrible.

the microwave for 1 minute does wonders for bricking phones not that I would know that for fact though

austinsnyc said:
the microwave for 1 minute does wonders for bricking phones not that I would know that for fact though
Click to expand...
Click to collapse
Not the old microwave trick - wasn't it you who posted this in Hermes thread a few months ago?

Phone insurance which covers "accidental" damage is a good move, although you will probably need to pay a small excess. I managed to push the usb port inside my universal a couple of years ago and got a straight swap. If you dropped it (from a height onto a concrete floor) I'm sure no one would even try to turn it on. Alternatively have a run in with a stranger in a hoody on a dark night, get a crime number and no one will even have your phone to check for HardSPL or custom roms

foobar1977 said:
So if I properly brick it they'll probably just replace it? Is there a guide on bricking anywhere
Click to expand...
Click to collapse
As mentioned in the other thread (no I'm not going to search for it. ) the only thing AT&T cares about is if the water sensor has been tripped (little white square under the battery permanently changes color when wet), or if there is obvious physical damage/abuse. Apparently they can't get past the RLoD either. As an aside I'd really love to know what the RLoD return rate is...
So, given those constraints the other thread's conclusion was that 12v across the battery/charge contacts should permanently brick it quite nicely. Just watch out for arcing.
THERE IS NO EVIDENCE THAT THE FLASH IMAGE AT THE TIME HAS ANYTHING TO DO WITH THE RLoD. It appears to be a hardware problem, and no-one here has reported an issue with a returned RLoD Tilt or Kaiser with a 3rd party flash image loaded.
In my case I also had to wait a few days to get the replacement units unlock code because apparently the IMEI was so new it wasn't in the database according to the service drone. Which suggests that AT&T is using a table of unlock codes from HTC rather than a piece of software to generate the codes. Now that we have an unlocker and "Super CID" program available, it's moot anyway. (Good karma wishes jockyw2001!)
James

gimini said:
well crap... i hear the red light be nicknamed the red light of death... i hope to god there is a way around this... if not would att know i reflashed something else if i went in and started to complain?
Click to expand...
Click to collapse
My Tilt hasn't gotten messed up yet. But I have return 2 8125's and 1 8525 back in the days and I sent them back with custom roms. AT&T never complain or anything like that.

My bad, it wasn't Rzanology, it was sWuRv (that avatar freaks me out).
Here's the thread in case it happens again...
http://forum.xda-developers.com/showthread.php?t=358136

I think I found a way out of the cemetery! Fix a FULL bricked phone"Pandora Battery?"

I think I found a way out of the cemetery! Fix a FULL bricked phone"Pandora Battery?"
deleted

Pandora Battery works with PSP 1000 lol.

wesjeex3 said:
Pandora Battery works with PSP 1000 lol.
Click to expand...
Click to collapse
deleted

Nice idea but this is nothing like the Pandoras battery, the battery doesn't fix the psp it puts it in service mode by flashing an incompatible serial number. This in turn allows the psp to re do the firmware from a memory card.
Sounds like you have an intermittent hardware fault. HTC phones come with a user accessible recovery mode unlike the psp that has to have it locked out for secuirty/flashing purposes...

shame on u for making ur father go to tmo just because ur logic didnt let u try the same battery change trick the 2nd time witch worked once ....

It might be more time. I bricked my prophet, couldn't get it into the boot loader or anything but only have the one battery.
Taking the battery out and putting it back in straight away didn't fix it but after I'd left it in a drawer for a few days whilst I was thinking about how to fix it I could then boot it into the firmware flash tri-colour screen.
Might be some capacitors that need to discharge or something, so leaving the battery off for a little while will do it, switching batteries may have the same effect but I think it's more to do with the time you left it and then switched batteries.

wesjeex3 said:
Pandora Battery works with PSP 1000 lol.
Click to expand...
Click to collapse
and the 2000 (cept for the last set of black ones)

Interesting theory either way
After kicking myself in the leg for bricking my phone I was willing to try anything. I made an attempt at this to no avail. It was worth a shot though.

Samsung Galaxy S 4G suddenly keeps shutting itself off

Ok guys let's see you work that voodoo that you do so well...
I got the idea to come here when someone of a T-Mobile support forum for Samsung Galaxy S 4G said they gave up on getting any help from those people but the guys from XDA were great and her phone has worked right since speaking with them. So here I am.
I own a Samsung Galaxy S4 G since July 2011, no real issues at all aside from a few random freeze ups from various programs. Well, a few days ago it starts turning itself off randomly. Sometimes it turns itself back on when I press the on button, sometimes I have to plug it back in, sometimes it says the battery is way less than it was right before it shut itself off. So I do what any savvy computer person does that's still a noob at anything technical- I learn how to reset the phone to its factory settings, delete all data and start fresh, figuring I had some bug in the system. This did nothing to help.
So I go online and discover all these different web forums with people complaining about the same problem. They all say the same thing, update the phone, don't update the phone, reboot, don't reboot, nothing fixes it. I even considered there being the "impossibility" of a loose battery connection and cut a thin strip of a business card to shove between the phone base to push the connection end tighter together.
The only place on any forum that anyone seemed to find an answer, albeit the answer was not discussed, mentioned coming here.
I apologize in advance if I don't immediately understand any technical details people may offer up as help, but please please please if anyone has an idea of how to fix this issue let me know.
Thanks in advance to everyone for their thoughts or suggestions :cyclops:

Sounds like it might be your battery. Have you tried switching batteries?
Sent from my SGH-T959V using xda app-developers app

that could be it I remember when I had the g1 and it was doing that it wouldn't charge and it wouldn't stay on
Sent from my SGH-T959V using xda premium

HolyGhostBoy1 said:
that could be it I remember when I had the g1 and it was doing that it wouldn't charge and it wouldn't stay on
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
My g1 did the same thing, after I swapped the battery it stopped.
Sent from my SGH-T959V using xda app-developers app

pisherthefisher said:
My g1 did the same thing, after I swapped the battery it stopped.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
yeah mine did that too new battery helped... my my touch also had a problem with the battery staying in place; so try the business card trick and leave your phone on a flat surface with no movement and for a day without charging... Don't blow money on the battery if you aren't sure, unless you've wanted a backup battery anyway.

one more thing
Good ideas so far...
One more thing, I've noticed the few times today its lasted for awhile and then I go to show someone something on youtube, it will play part of the video like 30 secs or so and then 'blip' we're back to automatic shut down again. Does this spark any different ideas?

another interesting discovery
oldandronicus said:
Good ideas so far...
One more thing, I've noticed the few times today its lasted for awhile and then I go to show someone something on youtube, it will play part of the video like 30 secs or so and then 'blip' we're back to automatic shut down again. Does this spark any different ideas?
Click to expand...
Click to collapse
Ok so I mentioned before about the 30 secs of video and then dead right? Based on the theories so far, which I'm also leaning towards and praying is correct, I ordered a new battery, won't be here for 3-5 days, but I decided to test an idea...
I thought perhaps if its the battery, if I plugged in the charger, things that kept shutting me down should 'in theory' continue to work.
So I plugged it in and tried to watch the same video 'Cat man do' again and see if it died in the same place it had done 3 or 4 times before or if it would work on through. And guess what, it played through the whole video, no random shut downs.
So I believe this might go a long way to proving your theories on the battery are correct, also the battery itself seems to be slightly swollen through the middle, which could cause a host of different issues, not the least of which would be slightly changing its size and therefore its connection to the power cup link.
Still happy to hear any other ideas, but as soon as I get and test the new battery I will repost on here and let you guys know if that did the trick.
Thanks again so much!

oldandronicus said:
Ok so I mentioned before about the 30 secs of video and then dead right? Based on the theories so far, which I'm also leaning towards and praying is correct, I ordered a new battery, won't be here for 3-5 days, but I decided to test an idea...
I thought perhaps if its the battery, if I plugged in the charger, things that kept shutting me down should 'in theory' continue to work.
So I plugged it in and tried to watch the same video 'Cat man do' again and see if it died in the same place it had done 3 or 4 times before or if it would work on through. And guess what, it played through the whole video, no random shut downs.
So I believe this might go a long way to proving your theories on the battery are correct, also the battery itself seems to be slightly swollen through the middle, which could cause a host of different issues, not the least of which would be slightly changing its size and therefore its connection to the power cup link.
Still happy to hear any other ideas, but as soon as I get and test the new battery I will repost on here and let you guys know if that did the trick.
Thanks again so much!
Click to expand...
Click to collapse
I would also suspect the sdcard. Have you tried another sdcard?

bhundven said:
I would also suspect the sdcard. Have you tried another sdcard?
Click to expand...
Click to collapse
Hadn't thought of that. Sure hope not though, been using this 32 gig sdcard since a week after I bought it and haven't experienced any issues with it during that whole year. Do you suspect anything on the sd card or just the card itself, just in case this battery issue isn't the culprit.

Sdcards go bad from time to time. Even get brand new ones that are flaky. When was the last time you reformatted it and started fresh.

eollie said:
When was the last time you reformatted it and started fresh.
Click to expand...
Click to collapse
Don't forget to backup first

eollie said:
Sdcards go bad from time to time. Even get brand new ones that are flaky. When was the last time you reformatted it and started fresh.
Click to expand...
Click to collapse
Reformatting the sd card itself? Never, hadn't even thought of it, nor ever learned how. Certainly happy to try it you have a couple of quick step instructions.
Again, apologies for being such a noob, but I love learning more to help for the future so all this info is great.

oldandronicus said:
Reformatting the sd card itself? Never, hadn't even thought of it, nor ever learned how. Certainly happy to try it you have a couple of quick step instructions.
Again, apologies for being such a noob, but I love learning more to help for the future so all this info is great.
Click to expand...
Click to collapse
First back up your sdcard. Copy all of its contents to your computer.
I do this every now and then, because if my phone eats my sdcard, I keep all my pics and music.
Second, reboot to recovery: Advanced -> Partition sdcard
It should then ask about ext partition size and swap partition size. I usually set ext partition to 2048 and swap to 0. We don't use swap. ext is the sd-ext partition, but iirc, recoveries with voodoo lagfix will use that to backup partitions it is converting. It has to be 2048 or it will fail. Unless you will never use older voodoo lagfix (which none of my roms/kernels do) you can use any size you wish.
Repartitioning sdcard can take a while, so be patient.

"So I believe this might go a long way to proving your theories on the battery are correct, also the battery itself seems to be slightly swollen through the middle, which could cause a host of different issues, not the least of which would be slightly changing its size and therefore its connection to the power cup link. "
I am 110% sure its your battery. Same exact thing happened to me battery was swollen and it kept randomly shutting off whenever I used internet based apps. I ordered a new factory Galaxy s 4g battery from amazon for about $8 popped it in and it stopped shutting off and battery life was actually way better. I suspect the swollen battery is caused by stuffing the business cards in the battery compartment.

oldandronicus said:
Reformatting the sd card itself? Never, hadn't even thought of it, nor ever learned how. Certainly happy to try it you have a couple of quick step instructions.
Again, apologies for being such a noob, but I love learning more to help for the future so all this info is great.
Click to expand...
Click to collapse
Hey, sorry to revive a dead thread but did getting the new battery work for you or not? I am having the exact problem that you described with my Galaxy S. I would love to hear how it turned out for you.

tyrst5544 said:
Hey, sorry to revive a dead thread but did getting the new battery work for you or not? I am having the exact problem that you described with my Galaxy S. I would love to hear how it turned out for you.
Click to expand...
Click to collapse
I had the very same issue 2 months ago, and it was the battery. I think the telltale sign of what is happening is that when your phone reboots, it has gone from almost a full charge to just a few percent. The issue as I understand it is that basically, when higher processing loads are being placed on the battery by the phone, at some point, it cannot provide the level of requested power, at which point, your phone believes the battery has died, and shuts down.
I swapped the SGS4G stock battery (1650 mAh) for the Anker 1800 mAh battery, and had great success and no issues. Best part is, you can buy 2 of them (which includes a wall charger as well) for $20 bucks on Amazon. http://www.amazon.com/Anker-Batteri...2126170&sr=8-2-spell&keywords=anker+1800+s4+g (Free 2 Day shipping if you have Prime) Things are almost disposable at that price, but the Ankers have worked great, and not had the reboot issue since.

oldandronicus said:
So I believe this might go a long way to proving your theories on the battery are correct, also the battery itself seems to be slightly swollen through the middle, which could cause a host of different issues, not the least of which would be slightly changing its size and therefore its connection to the power cup link.
Click to expand...
Click to collapse
And for the record, ANYtime your battery ends up swollen and distorted, you can guarantee that it's on its way out. At work a few years ago, had an issue where we were supposed to support PDAs and their battery life went down to seconds rather than the days they were supposed to last. Turns out their cells were swollen, sometimes enough to actually distort the back of their case. Replace the battery pack and get back to normal life. Without exploding batteries.
Random news story from 4 years ago with swollen battery pictures:
http://www.engadget.com/2009/01/28/sony-ericssons-bst-33-li-polymer-batteries-swelling-into-a-laws/

Great- thanks for the advice. Glad to hear from a few others as well that this should take care of the problem.

ariesgodofwar said:
I swapped the SGS4G stock battery (1650 mAh) for the Anker 1800 mAh battery, and had great success and no issues. Best part is, you can buy 2 of them (which includes a wall charger as well) for $20 bucks on Amazon. http://www.amazon.com/Anker-Batteri...2126170&sr=8-2-spell&keywords=anker+1800+s4+g (Free 2 Day shipping if you have Prime) Things are almost disposable at that price, but the Ankers have worked great, and not had the reboot issue since.
Click to expand...
Click to collapse
Wow what a deal..
Just ordered mine Free Shipping..
Great find Thanks for the link..
Sent from my SGH-T959V using xda premium

My God. I remember my g1. A new battery did not help its situation. I would charge, within 20 minutes, dead.
Sent from my SGH-T959V using xda premium

Bricked my maxx. Spare time to help?

I am somewhat of a n00b when it comes to android phones. I have had my maxx for about a month. Installed the leaked JB version and everything was working fine.
Today I decide to go back to 4.0.4 with the utility and something went wrong. I am stuck in a AP Flashboot loop. It sucks. I have tried everything....at least what I think is everything.
I have tried multiple utilities and RSD lite, etc. with no success.
Am I missing something?
Thank you!

Have you had any success yet?

projekt8e said:
Have you had any success yet?
Click to expand...
Click to collapse
negative.
same issues?

Fortunately no, but I have been searching around a little because I am new to Motorola (fresh out of samsung) and I have had some issues like this in the past that were rather frustrating, but as far as I can tell, considerably less frustrating than what one might experience with our phone.
so for my own sake, since I can't see it, is your phone essentially just going into fastboot and automatically rebooting or can you access any of the menu options?

projekt8e said:
Fortunately no, but I have been searching around a little because I am new to Motorola (fresh out of samsung) and I have had some issues like this in the past that were rather frustrating, but as far as I can tell, considerably less frustrating than what one might experience with our phone.
so for my own sake, since I can't see it, is your phone essentially just going into fastboot and automatically rebooting or can you access any of the menu options?
Click to expand...
Click to collapse
Yes it is extremely frustrating.
Said something about not being able to write to partition. Any option that I pick comes up to the fastboot menu. It seems to fail anytime it attempts to write to the phone.

One thing that I have noticed is that battery level seems to be important. (above 50% specifically)
not that this will fix your problem, but it might be preventative maintenance from further problems. Have you seen this?
http://forum.xda-developers.com/showthread.php?t=1549625
It covers charging in a scenario like yours, because it sounds like it might be nearly impossible to get anything down without a decent charge.

projekt8e said:
One thing that I have noticed is that battery level seems to be important. (above 50% specifically)
not that this will fix your problem, but it might be preventative maintenance from further problems. Have you seen this?
http://forum.xda-developers.com/showthread.php?t=1549625
It covers charging in a scenario like yours, because it sounds like it might be nearly impossible to get anything down without a decent charge.
Click to expand...
Click to collapse
Thanks! Ill keep that in mind. I think I was about 40 percent when I did it..... I doubt if that was the issue. I think as long as you dont lose power you should be OK... well what do I know... I will most definetly keep this in mind and make sure I use a full charge. My replacement phone should be here tomorrow morning...

Yeah, I think as long as you have power it should be ok, this was more of a measure to consider if your battery might be getting too low now after trying to fix it. But I guess if you have a replacement phone on the way, that will be easier, but maybe not as much fun! haha. Do you have to return the bricked one right away then?

projekt8e said:
Yeah, I think as long as you have power it should be ok, this was more of a measure to consider if your battery might be getting too low now after trying to fix it. But I guess if you have a replacement phone on the way, that will be easier, but maybe not as much fun! haha. Do you have to return the bricked one right away then?
Click to expand...
Click to collapse
Yup has to be returned within 5 days. I am making sure the battery is completely dead before i box it up. So they would have to at least charge it before they see the error.
They said something about being charged 299.00 if I messed with the image, software or something like that.... I think that it would be very hard for them to prove that point though in all actuality. Not much option.... Yeah.. not the way I really wanted to go but it is what it is..

fair enough. Yeah, leave it dead.

projekt8e said:
fair enough. Yeah, leave it dead.
Click to expand...
Click to collapse
This is exactly what i needed.
http://forum.xda-developers.com/showthread.php?t=2035131
All is working well. Perfect, perfect, perfect.

right on, so what did you end up doing then, if you don't mind explaining?

[Q] Razr MAXX HD battery sensor bug?

First of all, I'm happy to be a part of the site now. I'm not new to Android in any way, but have only decided to join a forum because Motorola tech is no help at all, and I can't figure it out on my own.
So here's the story. When I plug my Maxx HD in at night, it functions perfectly, and seems normal. Normal temperature and charge rate. Let's say for example it was at 50% when I plugged it in just before I went to bed at midnight or so. But when I wake up in the morning, the phone is powered off and doesn't register as charging. I unplug it, and it won't power up regularly, so most of the time I have to soft reset just to get the screen on. When it boots up, it runs smoothly like nothing happened. The battery is usually 5% or 10% higher than it was when I plugged it in many hours ago, so it's safe to assume it locks up and shuts down fairly quickly after I fall asleep. I have yet to be able to recreate this problem while I am awake. I have tried disabling, reenabling, and uninstalling just about everything, and the problem doesn't seem to relate to anything in the software. The curious thing is that this problem does not occur regularly. Sometimes, it will happen 3 nights in a row. Other times, it won't happen for a week.
A side effect of this, it seems, is that when it does decide to hold a charge, it will run from 100% to 90% and hold there for an hour or so, no matter how lightly or heavily I use it. Then, out of the blue, it will drop to around 60% or 70%, and the rest of the day will drop at a regular rate.
I've been searching for a solution for this problem for weeks and haven't found a valid answer other than "use a Motorola charger" "get a new phone" the always relevant "Have you tried an FDR?", and the typical answers from a bored Motorola employee about whether I've turned the phone off and on again.
To reply to those answers, yes, I've used a regular Motorola charger, Verizon's most powerful and expensive speed charger, and even the cheapest charger I can find and it still shuts off and won't charge no matter the charger. I currently use the Verizon charger because it is the most convenient and fastest charging.
No, I can't return it because the RMHD was a trade. I don't have the receipt of any documentation of the purchase. I had an S3 that I disliked because, let's be honest, Touchwiz is intrusive and irritating at times, and I was too lazy to try and find a working rom for it. I cold traded some guy that lived near me for his RMHD, phone for phone. No chargers, no receipts. just straight up trade. His still had the plastic on the screen, and he claimed he changed his mind about it as soon as he took it out of the box and thought it was too thick, and wanted an S3.
As for the FDR, yes I've done that 4 or 5 times now with no change.
So my question is, is this a hardware problem or a problem with the battery sensor? I'm tempted to say that the battery sensor is defective and protects the phone from overheat by shutting it down even when it's at normal temperature and won't take any more charge. But if that was the case, why doesn't it happen every night? Any help is appreciated, and I'm prepared to hear someone say "suck it up until the S4 or the Motorola X is released". Thanks for your help, and if I need to root my precious HD to fix it, I'm prepared to do so.

Sounds like there is an issue with your phone man, If you have already done FDR n whatnot and it still behaves the same, then not sure what else you could do to rectify that. If you have insurance on it you could put in a claim, it would cost money, but not as much as getting another phone.
Id say at this point though, why not unlock, root, try other roms, whatever. If for some reason it clears up running something else, then great! If not then you haven't lost anything but the time spent doing it. Id go for the 4.1.2 roms If you do, since they will have everything functioning, 4.2 roms are nice but not everything works yet (camcorder, HDR photos, voice search/transcribing, GPS issues, etc.)
I agree on the moto employees being lazy, they have 3 solutions to everything, FDR, reboot, FDR a ton of times in a row, its kind of insulting when they do that even after you say you already did it. "Hey I got a problem, I FDR, cleared this, rebooted, etc" - me "Did you FDR, clear that, reboot, etc??? Mine runs fine, must be something you did!" - Moto guy
Either way, let us know how it goes, and good luck, hope your issue gets resolved.

hollovoid said:
Sounds like there is an issue with your phone man, If you have already done FDR n whatnot and it still behaves the same, then not sure what else you could do to rectify that. If you have insurance on it you could put in a claim, it would cost money, but not as much as getting another phone.
Id say at this point though, why not unlock, root, try other roms, whatever. If for some reason it clears up running something else, then great! If not then you haven't lost anything but the time spent doing it. Id go for the 4.1.2 roms If you do, since they will have everything functioning, 4.2 roms are nice but not everything works yet (camcorder, HDR photos, voice search/transcribing, GPS issues, etc.)
I agree on the moto employees being lazy, they have 3 solutions to everything, FDR, reboot, FDR a ton of times in a row, its kind of insulting when they do that even after you say you already did it. "Hey I got a problem, I FDR, cleared this, rebooted, etc" - me "Did you FDR, clear that, reboot, etc??? Mine runs fine, must be something you did!" - Moto guy
Either way, let us know how it goes, and good luck, hope your issue gets resolved.
Click to expand...
Click to collapse
To put it simply, if there's ANY way I can determine if it's a software issue, I'd like to try it. A phone this expensive really has no excuse to have a hardware issue. I've heard the SIM reader can sometimes cause system problems, so I'll try blowing in the slot like an old N64 cartridge and seeing if maybe it misreads while charging and shuts off because of a speck of dust, or something ridiculous like that..

greydelta38 said:
Would it be worth reflashing the stock Motoblur 4.1.2? I used to run CM10 on the old GNexus, I'd love to use that again on my HD, if it's available.
As for a new phone, if need be, my upgrade happens to be right after the GS4 is released on Verizon so I might as well get that and then not have to worry about F-ing up my primary phone. I'm a little wary of rooting whatever my primary device is, because I've bricked a Bionic with a stupid mistake I made when I was new to Android.
Click to expand...
Click to collapse
You could try reflashing the stock rom, and there is a couple CM10 unofficial builds floating around in the roms section. Of course there is always risk in doing anything, but they have a pretty good method for rooting/unlocking, so id say if you feel up to it, go for it.

hollovoid said:
You could try reflashing the stock rom, and there is a couple CM10 unofficial builds floating around in the roms section. Of course there is always risk in doing anything, but they have a pretty good method for rooting/unlocking, so id say if you feel up to it, go for it.
Click to expand...
Click to collapse
I changed that post after I found a little more info, btw.
I usually don't go for unofficial. The only 10.1 I could find was a 4.2 but call audio, camera, nfc, and wifi weren't working. I wish they had a timeframe on an official release. Moto phones never have enough support.

greydelta38 said:
I changed that post after I found a little more info, btw.
I usually don't go for unofficial. The only 10.1 I could find was a 4.2 but call audio, camera, nfc, and wifi weren't working. I wish they had a timeframe on an official release. Moto phones never have enough support.
Click to expand...
Click to collapse
At this point, all CM builds are unofficial. All 10.1 builds are 4.2, 10.0 is 4.1. We are only going to get official when a proper kernel is ready and we have full functionality. 10.0 should have most everything working though, as the official moto builds are on 4.1.2. It does suck, Imagine if moto had never developed that ridiculous bootloader of theirs, we would be in great shape! But it is getting better, just everybody is starting from scratch now that its unlocked, so the pace seems slow.
If you don't mind the camcorder not working, the AOKP and Xenon HD builds are pretty awesome for 4.2. Best way to try them out is to put TWRP on and backup your stock, then you can switch between roms very easily and see if anything improves. The other recoveries should work the same as well, but ive only had experience with TWRP on this phone, and it works very well.

greydelta38 said:
First of all, I'm happy to be a part of the site now. I'm not new to Android in any way, but have only decided to join a forum because Motorola tech is no help at all, and I can't figure it out on my own.
So here's the story. When I plug my Maxx HD in at night, it functions perfectly, and seems normal. Normal temperature and charge rate. Let's say for example it was at 50% when I plugged it in just before I went to bed at midnight or so. But when I wake up in the morning, the phone is powered off and doesn't register as charging. I unplug it, and it won't power up regularly, so most of the time I have to soft reset just to get the screen on. When it boots up, it runs smoothly like nothing happened. The battery is usually 5% or 10% higher than it was when I plugged it in many hours ago, so it's safe to assume it locks up and shuts down fairly quickly after I fall asleep. I have yet to be able to recreate this problem while I am awake. I have tried disabling, reenabling, and uninstalling just about everything, and the problem doesn't seem to relate to anything in the software. The curious thing is that this problem does not occur regularly. Sometimes, it will happen 3 nights in a row. Other times, it won't happen for a week.
A side effect of this, it seems, is that when it does decide to hold a charge, it will run from 100% to 90% and hold there for an hour or so, no matter how lightly or heavily I use it. Then, out of the blue, it will drop to around 60% or 70%, and the rest of the day will drop at a regular rate.
I've been searching for a solution for this problem for weeks and haven't found a valid answer other than "use a Motorola charger" "get a new phone" the always relevant "Have you tried an FDR?", and the typical answers from a bored Motorola employee about whether I've turned the phone off and on again.
To reply to those answers, yes, I've used a regular Motorola charger, Verizon's most powerful and expensive speed charger, and even the cheapest charger I can find and it still shuts off and won't charge no matter the charger. I currently use the Verizon charger because it is the most convenient and fastest charging.
No, I can't return it because the RMHD was a trade. I don't have the receipt of any documentation of the purchase. I had an S3 that I disliked because, let's be honest, Touchwiz is intrusive and irritating at times, and I was too lazy to try and find a working rom for it. I cold traded some guy that lived near me for his RMHD, phone for phone. No chargers, no receipts. just straight up trade. His still had the plastic on the screen, and he claimed he changed his mind about it as soon as he took it out of the box and thought it was too thick, and wanted an S3.
As for the FDR, yes I've done that 4 or 5 times now with no change.
So my question is, is this a hardware problem or a problem with the battery sensor? I'm tempted to say that the battery sensor is defective and protects the phone from overheat by shutting it down even when it's at normal temperature and won't take any more charge. But if that was the case, why doesn't it happen every night? Any help is appreciated, and I'm prepared to hear someone say "suck it up until the S4 or the Motorola X is released". Thanks for your help, and if I need to root my precious HD to fix it, I'm prepared to do so.
Click to expand...
Click to collapse
You could always ask Verizon and see if it's under warranty. These phones aren't a year old yet if I am correct. Rooting your device is not the best idea because it technically can void your warranty.
Keep calling. Email Motorola support. Contact your carriers Cs. Or just sell the thing on ebay.
Sent from my DROID RAZR MAXX HD

jfriend33 said:
You could always ask Verizon and see if it's under warranty. These phones aren't a year old yet if I am correct. Rooting your device is not the best idea because it technically can void your warranty.
Keep calling. Email Motorola support. Contact your carriers Cs. Or just sell the thing on ebay.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
As I said in my post, I don't have a warranty, and I don't particularly care about a warranty. Motorola CS is pretty awful, they're all bored and don't really give a crap about your problems, unlike the friendly and caring service I've gotten from Samsung before. I don't want to sell it, seeing as how the RMHD is arguably the best phone on the market for the time being.

UPDATE: I uninstalled a RAM booster called Memory Booster - RAM Optimizer a few days ago, and have yet to have a charging problem. I had the booster set to auto clean the system garbage when the screen was off. I'm making an educated guess here, but I'd be tempted to say that it was killing one of the Android processes that keeps the phone awake while charging, and it would bug out and crash.
Long story short, if you're having a problem with an HD shutting down overnight, UNINSTALL ANY APP KILLERS, TASKERS, OR RAM BOOSTERS.
Hope this works.

Okay, so I thought I was in the clear. I was wrong. It definitely is less frequent, but my RMHD still continues to totally die every night. I've determined that it's definitely NOT a hardware problem. I'm convinced that it may be overheating at night and Android shuts it down for safety, and somehow locks it up in the process. Last night, I went to sleep with 20% battery, and plugged in. This morning it was totally dead and would only respond to a soft reset, booting into recovery, where I prompted a reboot. It started fine, showing 44% battery.
What the hell is going on? I went so far as to reflash Motoblur, and I tried Eclipse 4.1.2 and still had the same problem. Is it maybe an app that is hostile? Someone has to know how to fix this huge annoyance.
Sent from my DROID RAZR HD using xda app-developers app

greydelta38 said:
Okay, so I thought I was in the clear. I was wrong. It definitely is less frequent, but my RMHD still continues to totally die every night. I've determined that it's definitely NOT a hardware problem. I'm convinced that it may be overheating at night and Android shuts it down for safety, and somehow locks it up in the process. Last night, I went to sleep with 20% battery, and plugged in. This morning it was totally dead and would only respond to a soft reset, booting into recovery, where I prompted a reboot. It started fine, showing 44% battery.
What the hell is going on? I went so far as to reflash Motoblur, and I tried Eclipse 4.1.2 and still had the same problem. Is it maybe an app that is hostile? Someone has to know how to fix this huge annoyance.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Not hardware but it gets hot and shuts down? Sounds like hardware to me.
Sent from my DROID RAZR HD using Tapatalk 2

Yeah sounds like hardware.
Sent from my XT926 using xda app-developers app

scoobaspeaz said:
Not hardware but it gets hot and shuts down? Sounds like hardware to me.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
It's not hardware. I reflashed stock 4.1 AGAIN, and have yet to have it screw up. It's been about a week and a half since. Motorola sent me a new charger just in case. I know you guys think it's hardware but for some reason I'm totally convinced that it was an app screwing with Android. I guess I'll find out sooner or later. Thanks for the feedback.
Sent from my Galaxy S4 using xda app-developers app