Database Info

Taking the risk of GB radiofor the sake of science.

Just talked to a friend from vzw, he told me that if something happened he will hook me up with a replacement for my tbolt.
I've been using gb radio since the 1st day it was leaked, i have no problems on my phone, just some random FCs but that's given.
Since we don't have a solid demographics on how many people got bricked, Im going to take the risk and see if i get bricked.
This morning i just got into a bootloop but looks like its just the battery giving false stats. Its been more than 6 hours now in my external charger and i assume battery doesn't hold charge anymore, Im going tommorow to vzw to have it replaced.
Question is, will logcat be enough to monitor my phone in case i got bricked so i can pull some important data regarding how it happen?, that way we can find a clue on how to fix a radio-bricked tbolt.

Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App

Wow. Very cool that you're willing to do this. Looking forward to seeing what you find out.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
From what I've read, that's not possible as the bootloop happens even booting into recovery.

kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Yes i have cleared my battery stats. My previous battery is now dead. I think i discharged it too much, now its not holding any charge. My phone still runs on gb bamf and loving my lockscreen. Will let you know if i get bricked.
Sent from my ADR6400L using XDA App

i too am sticking it through, im too in love with this to revert back.

yakitori2 said:
kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.
Click to expand...
Click to collapse
Lol you obviously didn't read his post. No risk involved.

I hope someone could shed a light to my questions.
1st. How does the radio firmware work on our phone? Does it work like a driver where it acts a mediator between the roms(software) to the phone's hardware.
2nd. What are the possible trigger to recreate the bootloop of death? There are some cases that my phone overheats because of non responsive apps and ever since i flashed on GB rom there i times i can feel my phone hot, which could be the case from some of the boot loop victim that they fried something inside their phone.
3rd. What are the chances that same bootloop of death could also occur in froyo radio? Just because vzw officially released the radio doesn't mean it has same risk like the leaked GB radio. It is like how HTC manufactured the phone, they tested most of it but some are still lemons.
Everything is in theory right now, there are no fix because it happens in random and the reason is still unknown. I'd choose to participate for the fix instead of waiting for someone to figure out the fix. We all do take a bold step in rooting our phone, flashing different roms, putting our faith on the battery that it wouldn't fail during the flashing process. Once we modified our phone from its stock settings we acknowledge the risk, and that risk is the one of the few factors the fuels the development of the rom/kernel community.
I've noticed several repacks of the GB radio:
http://www.multiupload.com/HU471CMQI0 ----
MD5: EE2A824E51CB148A2256F93E30A3B9F9
http://www.worldofjohnboy.com/dhemke17/ROMFiles/PG05IMGGB.zip ---- MD5: fda2a314975dd829b4e3611ecc8cfa13
PG05IMG_gingerradio.zip <- from http://forum.xda-developers.com/showthread.php?t=1082001 links alread removed. This is the same radio from androidpolice.com----
MD5: 52DD83AA40E30186C9FBEFAFD1BAB534
For the record, i flashed mine with the MD5: EE2A824E51CB148A2256F93E30A3B9F9
right now im using das bamf 2.0-5 running on imoseyon_leanKernel_v2.5.4GBtest6
Im keeping a close watch on my temp running on "extreme settings" 1.4ghz extremely undervolt.
SetCPU profile set to minimum setting when temp goes more than 97F

I just called verizon 611. My phone is not bricked and still functioning properly, but i told the operator that my phone constantly reboots( I pretended that my phone was bricked), i was passed to higher level tier support and they said they will be sending a new phone to me and there will be an extra envelop where i need to put my old phone to return to them. The call only took me 10-15 minutes and I believe VZW is aware that Tbolt has this issue even if its GB or the stock froyo rom.

i reverted back last night but i will def be back once things are more stable.. i already miss it

Going back to Gingerbread.

I was about to make the jump back to Gingerbread "I.e. The ROM/Radio of death" and just wanted to know how many people have gotten over the bricking debacle.
I have yet to hear of anyone who has had a bricked device since a day or two after the incident was brought up.

Ya, I'm starting to think this may have had alot to do with just user error. I remember back in the early days of rooting when people used to brick phones because they didn't know what they were doing.
I think I'll wait another week and if I don't hear of anymore "bricks" I may switch back to GB.

Dnakaman said:
Ya, I'm starting to think this may have had alot to do with just user error. I remember back in the early days of rooting when people used to brick phones because they didn't know what they were doing.
I think I'll wait another week and if I don't hear of anymore "bricks" I may switch back to GB.
Click to expand...
Click to collapse
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.

bp328i said:
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Interesting, thats actual enough for me to hold off till a future release. I had a friend who got bricked but had little Android/Rooting knowledge so I kind of blew it off as it must have been user error. Thanks for the heads up, and will now continue waiting for a new release. Damn.
Edit: Did you have any luck getting a replacement from Verizon?

bp328i said:
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Man, that sucks. I know I've seen you post about the issue, but you seem to be the only one that actually has this issue that has actually posted anything concrete here.
Others that have posted about "bricks" sounded like they just didn't know what they were doing and were actually recoverable.
But like Mike said, enough for me to wait until more evidence is uncovered.
Thanks for the info.

miketoasty said:
Interesting, thats actual enough for me to hold off till a future release. I had a friend who got bricked but had little Android/Rooting knowledge so I kind of blew it off as it must have been user error. Thanks for the heads up, and will now continue waiting for a new release. Damn.
Edit: Did you have any luck getting a replacement from Verizon?
Click to expand...
Click to collapse
And to add to the above I do all my rooting via adb, I have never used a one click root. I'm also an Official Themer on another forum, so I know my way around Android a little.
I had insurance that made me send it off to try to have it repaired first. I just got a new one yesterday.
I'm waiting on a new Gingerbread radio to come out before going back to Gingerbread even though how much I miss it.

Well right before the news was posted, I noticed some connection issues, it was kind of a weird issue. So I reverted back right after seeing the brick thread....
SCARY!

I was just about to make a thread similar to this. Seems as though the bricking phenomenon has blown over. I just flashed gingeritis beta IX and I'm loving it!

bp328i said:
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Question for you. Did you have a third-party or extended battery in it?

want a droid said:
I was just about to make a thread similar to this. Seems as though the bricking phenomenon has blown over. I just flashed gingeritis beta IX and I'm loving it!
Click to expand...
Click to collapse
It's blown over because most everyone went back to froyo. Nothing has actually been resolved.

Jaxidian said:
Question for you. Did you have a third-party or extended battery in it?
Click to expand...
Click to collapse
Nope, stock battery and charger.
Sent from my ADR6400L using XDA App

SirVilhelm said:
It's blown over because most everyone went back to froyo. Nothing has actually been resolved.
Click to expand...
Click to collapse
This is what I figured.

A lot of people stayed on gingerbread though with no more reports of bricks...
Sent from my ADR6400L running Gingeritis v1.0 Beta IX

want a droid said:
A lot of people stayed on gingerbread though with no more reports of bricks...
Sent from my ADR6400L running Gingeritis v1.0 Beta IX
Click to expand...
Click to collapse
I think that is where the real problem is.
The issue is so random, there is no set explaination at this time to explain why/how it happened.
Since the one person that I know of sounds like a very creditable person based on feedback on these forums, I myself am going to error on the side of caution.
I was running GB with no issues as well, but I would hate to kill my phone, just because I "thought" it was safe to reload GB.

I have been on BAMF since they came onto the TB scene. Less than a week from phone release I rooted and started rom'ing. I loaded the new ginger radio about a day before the first report of the brick came out. I havent had any problems. But I have been keeping my eyes open to see when or what will cause a brick so every two seconds I cheack my phone BUT i can't post in the development forum yet So i gotta wait till ten UGH

i'll wait for our developers to give the thumbs up on going over to GB roms, whats the rush vs the risk? Not a big deal to wait another week or two considering what u could be going thru. BAMF remix 1.7 is running flawlessly for me after I dropped back from GB.

I was using Gingeritis from Beta 3 to Gingeritis IX. Honestly, I haven't had a single random reboot or any problem at all.
However, I did have a data issue. If my phone would change to a 3g signal, it wouldn't bring back 4G. But, once I rebooted the phone one time, the problem was fixed from there on.
I still have Gingeritis IX on my phone, and its great. I'm running Imo's test6 kernel as well.

miketoasty said:
I was about to make the jump back to Gingerbread "I.e. The ROM/Radio of death" and just wanted to know how many people have gotten over the bricking debacle.
I have yet to hear of anyone who has had a bricked device since a day or two after the incident was brought up.
Click to expand...
Click to collapse
Honestly the bricking thing threw me off first, then I noticed it takes forever to charge, drains quicker and camera and camcorder sucks on gingerbread. So I'm sticking on froyo Bamf for awhile.

Yeah I'm back on froyo. And to those who are "watching my phone and no signs of bricking", there will be no signs. You'll pull your phone from your pocket and have a bootlooping phone, unfortunately. I'm running CM7 gb, 95% of things work like they should, and since it's a froyo radio, I'm immune to the brick of death.
Sent from my ThunderBolt using XDA Premium App

Jaxidian said:
Question for you. Did you have a third-party or extended battery in it?
Click to expand...
Click to collapse
Hmmm... I was wondering this myself. I'm on GB BAMF 2.05 and only have random reboots when I have my 3rd party battery in. The stock battery doesn't seem to have any issues.

[Q] Anyone have success fixing restart issues?

I've had my G2X for about a month, and have been experiencing the common issue where my phone randomly shuts off and the only way to get it to turn back on is to pull the battery.
I've installed the GB update, that didn't fix it. Factory reset didn't help either.
Has anyone successfully fixed this issue on their phone? If so, what'd you do? Is there any chance that rooting my phone would correct the problem?
Sorry if there was a post about this, I couldn't find anything talking about if anyone's been able to fix the problem.
Thanks

yes... the onlyhh way to fix the problem is to root! nvflash clock work mod recovery, then flash eagle blood 2.3.3 rom and it is perfect...

Thanks, this did indeed seems to do the trick. Not a single reboot so far after 2.5 days.
Sent from my LG-P999 using XDA App

My G2X actually restarted on its own today. It was the first time since the first few days I had the phone over a month-month and a half ago. Wasn't really a big deal, lol. It comes back on.

Have been playing with this phone for 3 days now and haven't had any issues (I did install xboarder's stock rooted version). Minor screen bleed is the only issue.
Sent from my LG-P999 using XDA Premium App

Finally, someone (dmaniscool) who can say they switched to an xda dev'ed ROM and got rid of the lock ups. I've posted many times asking if anybody ACTUALLY FIXED a problem (specifically the battery pull lock up); I got no responses, and someone finally stated it. Great. Next time my wife's G2x locks up, I'm rooting and putting a ROM on it.
Thank you dmaniscool
-Bob

so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob

namklak said:
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
Click to expand...
Click to collapse
Will do, so far so good! I had no experience with rooting, and was able to figure it out looking at the guides available on the forum. It kind of looks intimidating, but it's not actually very difficult.

By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App

RZJZA80 said:
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Mine did both actually, shut down and restarts. But mostly just shut downs, which required a battery pull to power back on.

My 2 will do both - but I think the "shut-off" is a lock up, because the longer I leave it locked up, the less battery I'll have after I do a battery pull.
8 days of both phones not locking up by doing one restart per day per phone.

Since I raised the minimum CPU speed to 389 from 216, I have far fewer sleeps of death
You don't wanna know where this was sent from.

I've tried every ROM and kernel combination possible and nothing actually fixes these problems for me.

Wow this post was scary at first, I had a thunderbolt and no matter what. RUU, Different ROMS, Stock, Kernels, Radios. Changing all that didn't matter it still turns off constantly and doesn't turn back on till I do it meaning no text or calls, basically same as having a phone on silent all the time without even having the luck chance of pulling it out while ringing.....

I am on miui x.26 (whatever kernal that comes with it) and have over 40 hours of uptime. I haven't had a crash yet, I just manually restart every couple of days because I'm weird like that.
Sent from my LG-P999

Well 6 days into it and I've had a total of 2 shutdowns. I don't know if it was a coincidence, but both times were after being outside when it was ~90 degrees out.
This is still much improved, I used to get 3-4 per day on average.
I'm using Eaglesblood 2.3.3. I'm thinking of trying MIUI because it's so nice looking.

For me I did a battery replacement the first time directly from T-Mobile and the phone continued restarting on me. I was just about to request a replacement phone from T-Mobile until I recently purchased a different brand of battery containing the same specs as the stock battery and to my surprise no overheating and definitely no restarts. I feel that the restarts and lockups are due to faulty batteries shipped out with the phones. I'm suprised no one has mentioned this.
Sent from my LG-P999 using Tapatalk

Do you mind sharing what brand battery you purchased?
Sent from my LG-P999 using XDA App

Wow, I told the CostCo kiosk girl I was having lock up problems and I had my grandkids with me. She took my phone and pulled the battery - at the same time my grandson stated he had to go to the bathroom NOW. She either looked at the battery or something on the phone under the battery. I didn't have time to ask. She didn't really comment and gave me my phone back.
Hmmmmmm........
-Bob

ok so do they know what exactly is causing the shut downs or reboot on this phone? i just got mine today and it was pre installed with gingerbread and idk if there is root for the gingerbread build yet. i just want root but no custom rom for me. i love the stock rom. it kicked the crap out of my sensation 4g as far as speed goes in everyday use.

Battery life worse since 2.11.605.5

Am I the only one who's got worse battery life since the update?
I keep my brightness set low, bluetooth and GPS are off. My mail and Twitter are set to update manually. Weather updates every four hours, and I use only a few widgets (the weather clock and a few that toggle settings). I've got a solid LTE signal.
Before the update (and even after the 2.11.605.3 Gingerbread update that I'd got before Verizon and HTC pulled it), I could take my phone off the charger when I woke up, use it moderately, and still be in the green when I'd put it back on the charger at bed time. If I used it a bit more, maybe I'd be in the yellow, but I'd never had a problem going 18 hours or so on a single full charge.
Since the update, though, my phone can't get through a day without recharging in the middle. Even if I don't use it. Just sitting on my desk, untouched, I'm losing about 11% an hour.

Chances are the phone will re adjust through battery cycles. Also there are power saving options now if you go to the power setting. The efficiency setting works very well. Other than that I would wait a little longer before going about any tinkering.

And one more thing. You don't have a task manager do you? If so get rid of it. Android is incredibly efficient on managing its ram and tasks.
Sent from my ADR6400L using XDA App

LTE? You're running 4G all the time? I wouldn't make it past late afternoon if I didn't toggle the LTE off most of the time and use CMDA (3G).

I'm stock and also having horrible battery life since the last update. Like 5 hours worth of battery with little use before I'm in the yellow. I'm giving up on 4G and switching over to 3G for good... maybe that will last longer as it did in the past
I'm tempted to do a factory reset

mdeblaz said:
I'm stock and also having horrible battery life since the last update. Like 5 hours worth of battery with little use before I'm in the yellow. I'm giving up on 4G and switching over to 3G for good... maybe that will last longer as it did in the past
I'm tempted to do a factory reset
Click to expand...
Click to collapse
If my assumption is wrong on your knowledge of factory resets, i apologize and i'm not trying to insult your knowledge of these phones. That being said, factory reset won't allow you to revert to pre 605.5 software, as it just wipes the data completely and you stay on the same 605.5 you are on. If you are rooted already, make a backup and flash back an older release of the software that you are happy with. If you aren't rooted, now is a good time and then to revert back to past software haha

Hmm..sounds like someone should get an extended battery.I have one and never had a problem before or after gb.
Sent from my ADR6400L using XDA App

nbdysreal said:
If my assumption is wrong on your knowledge of factory resets, i apologize and i'm not trying to insult your knowledge of these phones. That being said, factory reset won't allow you to revert to pre 605.5 software, as it just wipes the data completely and you stay on the same 605.5 you are on. If you are rooted already, make a backup and flash back an older release of the software that you are happy with. If you aren't rooted, now is a good time and then to revert back to past software haha
Click to expand...
Click to collapse
Insult not taken... I'm well aware of what a factory reset is. And I don't care to root - been rooted before. Battery was much better before... so I figure its probably an app causing the drain - not playing nice with the update. A reset could remedy that.
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
holla420 said:
Hmm..sounds like someone should get an extended battery.I have one and never had a problem before or after gb.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Unfortunately, I don't care to have that over grown tumor on the back of my phone. My battery has been fine before so I know it's possible to use the stock battery and have it last throughout the day.

Lol well suit urself.I don't kno why a lot of people hate it.I mean besides the phat ass on the back it last 16+ hrz.but Wat ever floats ur boat
Sent from my ADR6400L using XDA App

And one more thing. You don't have a task manager do you?
Click to expand...
Click to collapse
Nope. Never have, never will. I'll give it a few more days and see if, as you suggest, the battery doesn't readjust.
LTE? You're running 4G all the time? I wouldn't make it past late afternoon if I didn't toggle the LTE off most of the time and use CMDA (3G).
Click to expand...
Click to collapse
Yep. The area I'm in (just east of Pittsburgh) seems to have good coverage. I've never had to manually turn off LTE, and until the last update, I've never had trouble making it through the day.
Hmm..sounds like someone should get an extended battery.I have one and never had a problem before or after gb.
Click to expand...
Click to collapse
Unfortunately, I don't care to have that over grown tumor on the back of my phone. My battery has been fine before so I know it's possible to use the stock battery and have it last throughout the day.
Click to expand...
Click to collapse
I'm with mdeblaz. Getting through the day on the stock battery hasn't been an issue until the update. And I'll buy a new phone before I buy a ginormous battery for this one. I've had a couple of HTC phones now, and the Thunderbolt has been the most problematic for me. Maybe I'll sell it back to Verizon and get the Rezound. If the battery issue doesn't clear up on it's own, it's either going to be new phone or (for the first time since I started using Android phones) flashing a new ROM.
Anyone know a good Gingerbread ROM for the Thunderbolt that has Sense 3? I know I'm a minority, but I keep buying HTC phones because I actually like Sense.

BAMF Forever 1.09.
You may have an issue with the camera taking pics, try clearing data from the camera app. Like having a new phone for me.
Sent from my ADR6400L using XDA App

collije said:
BAMF Forever 1.09.
You may have an issue with the camera taking pics, try clearing data from the camera app. Like having a new phone for me.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
That one looks pretty good. Is LTE working in it? Is it ok to use over the current stock software? Any guides for noobs who have never even rooted, let alone installed a custom ROM?

mikeszekely said:
That one looks pretty good. Is LTE working in it? Is it ok to use over the current stock software? Any guides for noobs who have never even rooted, let alone installed a custom ROM?
Click to expand...
Click to collapse
Some advice for noobs. Read read read. Do your homework. Read through the guides and walkthroughs on this forum (mainly in the development section). Learn now to root and learn how to recover BEFORE attempting to mod your phone in any way. Learn how to setup and use ADB.
Sent from my HTC ThunderBolt powered by KillaSense 3.2

And it seem its cycling through 3g, 4g, 1x, again. Why can't HTC get this right wtf.
Sent from my ADR6400L using xda premium

As killa just said do read.
Going root is probably the only way to fix the thunderbolts stock problems.
I have had mine rooted since it was rootable and I have been loving my phone. I also use the stock battery and can get over 18 hours daily with wifi on at all times, lte and GPS when I'm not home. Those are the wonders of custom kernals and setcpu . I run AOSP but I have ran sense and Bamf forever is definitely the way to go for sense.
Good luck.
Sent from my ADR6400L using xda premium

I'm having no problems with data connectivity on 2.11.605.5 perhaps your area is having network problems...
Sent from my HTC ThunderBolt powered by KillaSense 3.2

Problems with my Phone?!?!

****** PROBLEM SOLVED ******
"I decided to buy a new battery from Amazon which didn't cost that very much. My phone is back to normal so it was my battery I'm guessing like the battery exploded because it felt all lumpy & stuff."
** Thank you everyone who left suggestions & answers to help me with my problem much appreciated! **
Okay I've recently rooted my Samsung Galaxy S 4G for about 2 weeks now & I am currently having some problems with my phone. I'm not sure if its my phone or the ROMs that I am flashing. The problem that I am having is that when I'm using my phone that has a full battery my phone just shuts off completely. I turn it back in on the battery is almost dying so I charge the phone. When its done charging I unplug it & continue to use my phone, but for some reason it keeps turning off on me. I can't use my phone at all because of this the only way I can use my phone is if its plugged in to charge. I thought maybe it was the ROM that I am using which was Valhalla FINAL so I flashed it again & I get the same result. So, I decided to download a different ROM which was HebrewValhalla3.5_AROMA & guess what I get the same result. I really want to use my phone, but I can't so if someone can please help I would really appreciate it very much!
So what do you think could be the problem is it the ROMs that I am flashing or what? Please give me some tips & what ROMs do you recommend? I really need anyone's help...Thanks
Sent from my SGH-T959V using xda app-developers app

It's the battery.

Battery.....can buy em all day long @Amazon.com for $5.00

It can't be the battery because it works normal when my phone is not rooted
Sent from my SGH-T959V using xda app-developers app

Its not the battery my phone works fine when it isn't rooted.
Sent from my SGH-T959V using xda app-developers app

So you unrooted it and it works fine now?

Yeah it works fine like normal when it isn't rooted, but when I root it again it does the same thing
Sent from my SGH-T959V using xda app-developers app

Well if you really wanna find where the problem is, assuming it's not the battery, try running on stock unrooted for a day, then flash just a rooted kernel, and then try a full rom.

Okay I will try that, but what would you recommend I'm kinda new to this stuff.
Sent from my SGH-T959V using xda app-developers app

You should read this.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G

I would have to say its not Valhalla final because i am running it with no problems. I have 1day 12hrs 35mins on a single charge. With 38% left on battery. Simply rooting your phone would not cause massive battery issues. Gotta be something more going on.

just wanted to chime in. i was having the same issue, but my sgs4g has been rooted with froyo 2.2.1 since i took it to a guy to root it for me(i had bricked my first one ha!) when KD1 was still the thang. and just a few months ago i started having this problem out of no where, just as used described it op, except i haven't been flashing anything on or off it, and i thought it had to do with a shetty app i had installed. i put a 'new' battery in and had the same issue, eventually the new battery(which was a very sensitive 1500mAh i bought for $20 at a local phone spot) blew up when a gf sat on me while it was in my pocket. the batteries seem really sensitive, there's a warning label to not apply pressure to the battery and it's easy to do with the sgs4g. anyway i went out and bought a 900mAh from best buy for 40 bucks :"""( but it works fine now. battery slowly creeps to zero like its supposed to. i haven't flashed anything or changed anything app-wise, still rooted.
when i was having this problem i also found that there's a battery calibration app for when you flash a new rom, but it didn't help me. worth a shot when you flash a new rom though i reckon.
hope that helps!

Sensitive? Really? Lmao
That's a load of crap.
I have 4 batteries that i charge on a continuous basis with an external charger and 2of them have been thru hell and back and still work as good as new. And for your info battery calibration apps do nothing good for your battery.
I'm not saying they don't go bad cuz I've had several that have....but sensitive? I'm not buyin that.
I am an ironworker and keep my extra batteries in my pocket all day every day and always have one in the charger.
As for rooting your phone causing the battery problems.....not buyin that either....that my friend is in your head....or there's more to it than your telling us.