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.

S.o.d(screen of death)

So I just got my g2x, rooted,nv and cwm. Flashed cm7 and I keep getting s.o.d(screen of death). I thought was rom problem so I.changed rom and im on xdblasters 1.1.0 and keep on getting them. Any solution orhelp would be appreciated.
Sent from my LG-P999 using XDA App

Not sure I know of a rom for g2x called xdblasters.
Also, what kernal are you using? Are you overclocking or undervolting? Are you using setcpu or pimpmycpu? What is your max and min cpu settings? When you flashed, what was your procedure for wiping? Did you fix permissions after flashing? Did you use a program to restore apps? Did you use that program to restore system settings? Did you choose to restore apps and settings from google account?
The answers to all of these questions could help determine what you've got going on.

I apologize, its x boarders. And well I am using fauxs newest kernel currently using 1.1 overclock but it would also happen while at stock cpu with previous rom.i don't restore with google but I use titanium backup for batch. When I do new roms I always follow the clean slate rule;Wipe data,cache,dalvik,bat stats. occasionally I forget fixing permissions but I do when I get alot of force closes.
Sent from my LG-P999 using XDA App

I didnt' see you mention formatting /system under mounts and storage. This is a critical step.
If it were me, I would try to keep everything as basic as I could each step of the way so that i could try to pinpoint the issue. Start by wiping everything (including sd card...just backup your user added stuff to your pc) and install a stock rom/kernal. See if it occurs stock...who knows? It's possible your phone is bad. Then if it doesn't misbehave with stock, then I would wipe everything again, including sd cards (interal and external), and flash cm7 (keeping cm7 kernal). I would try manually installing apps again, rather than using titanium backup or google restore. Just hook up to wi-fi (so you don't waste your data mileage) and go to market/myapps and redownload (hopefully you have a list of what you have).
But something to point out. On my phone, when I use CM7 (with stock kernal), I have to increase my minimum cpu frequency to either 312 or 456 instead of the default 216....216 seems to cause my phone to get stuck with the black screen also. The same thing happens when I run an undervolt kernal. So I've learned that my phone simply doesn't like undervolting, overclocking, or lettign the cpu run lower than 400MHz. Maybe that might help you out.

i was about to back up my sd and reformat it for that reason.I already tried formatting eemc mount or internal mem, and nothing. I also stopped using uv kernels and i kept my cpu min at 506 to keep it from doing, but with no result.I just flashed the newest release of xboarders 1.1.1 and i already got 3 sod while the rom is stock with nothing added. I am starting to think phone is bad. I bought the phone on Craigslist, so i might be S.O.L. i Appreciate

what should my mounts look like when i do a system format?

thrashingdeth said:
i was about to back up my sd and reformat it for that reason.I already tried formatting eemc mount or internal mem, and nothing. I also stopped using uv kernels and i kept my cpu min at 506 to keep it from doing, but with no result.I just flashed the newest release of xboarders 1.1.1 and i already got 3 sod while the rom is stock with nothing added. I am starting to think phone is bad. I bought the phone on Craigslist, so i might be S.O.L. i Appreciate
Click to expand...
Click to collapse
I just traded my sensation for a g2x off CL, sure glad mines had no reboots or sod, actually the best g2x if had out of my 4..

Thats good news. So I wiped system and using xboarders 1.1.1 and so far since last night no sod. I hope it sticks.
Sent from my LG-P999 using XDA App

thrashingdeth said:
Thats good news. So I wiped system and using xboarders 1.1.1 and so far since last night no sod. I hope it sticks.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Awesome, hope it stays good.

guess i spoke to soon. Was running fine all day till around 2 i installed setcpu and configured it. Or so i think, so i uninstalled and reset but when i am charging it it keeps turning off. AHHHH headache with this phone. When it runs, its smooth and so fast, i love it, but i dont know whats wrong with it.

I think I'm done with this. Can't figure out a away around this. Awesome phone but overwhelming problems. Appreciate the help everybody.
Sent from my LG-P999 using XDA App

have you tried a new battery? I believe most of the G2x problems are likely due to a bad batch of batteries.. why you ask I have come to this conclusion? If I OC heavily OR run the LED light when the battery gets low >30%, my phone will shut off. This would conclude the battery cannot supply the needed current for the phone at the lower battery levels... this is my particular battery but I wouldn't doubt there are worse batteries out there AND/OR reported battery levels that are much higher than actual and getting the same problem I have encountered. Food for thought.

Black6spdZ said:
have you tried a new battery? I believe most of the G2x problems are likely due to a bad batch of batteries.. why you ask I have come to this conclusion? If I OC heavily OR run the LED light when the battery gets low >30%, my phone will shut off. This would conclude the battery cannot supply the needed current for the phone at the lower battery levels... this is my particular battery but I wouldn't doubt there are worse batteries out there AND/OR reported battery levels that are much higher than actual and getting the same problem I have encountered. Food for thought.
Click to expand...
Click to collapse
I agree with him... I had worst case of s.o.d with my g2x. Atleast 3 times a day I had to take battery out... but I solved it by doing the following
1. Increase min cpu speed 300 or more.
2. Discharging the phone completely and then recharging it completely.
I barely get s.o.d. may be once in 2 weeks. And whenever I do get em. I give my phone a discharge recharge cycle... then its good for next two weeks
Sent from my LG-P999 using XDA Premium App

What "Screen of Death" are you guys referring to? Never experienced such a thing...
Phone wont wake? Or what? A quick google search for "android screen of death" and "g2x screen of death" revealed pretty much nothing.
Have you pulled a logcat?

I always fully charge and discharge battery for proper calibration. Doesn't seem to be helping in any matter. I also stopped using any CPU management because I thought that was.
bshakil said:
I agree with him... I had worst case of s.o.d with my g2x. Atleast 3 times a day I had to take battery out... but I solved it by doing the following
1. Increase min cpu speed 300 or more.
2. Discharging the phone completely and then recharging it completely.
I barely get s.o.d. may be once in 2 weeks. And whenever I do get em. I give my phone a discharge recharge cycle... then its good for next two weeks
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App

The problem is when phone sleeps and doesn't wake up. I have not pulled one, been thinking its hardware related.
AdamHart612 said:
What "Screen of Death" are you guys referring to? Never experienced such a thing...
Phone wont wake? Or what? A quick google search for "android screen of death" and "g2x screen of death" revealed pretty much nothing.
Have you pulled a logcat?
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App

Only happened. Twice today. Bahamas improvement I guess.
Sent from my LG-P999 using XDA App

Its hardware defect. No matter what ROM you put on the phone, it will continue. Youve gotta call TMO and get a replacement. Sorry if thats not what you wanted to hear.

I agree with the battery theory. I purchased two generic batteries from ebay and they last 3 times as long and have resolved many of the resetting and SOD issues that I was having. Also, updated ROMS seemed to help, and not letting it fall asleep while you are playing games or something memory intensive.

Well I bought a battery, hoping that helps a bit. So far its a lil better than usual. Using stock voltage kernel. When I get new battery I will test
Sent from my LG-P999 using XDA App

[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.

Phone acting stooopid.

Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D

AgentCherryColla said:
Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D
Click to expand...
Click to collapse
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2

wiswis said:
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
I have no clue where my other battery is at XO

I keep on getting status 0 in recovery with any rom. But when that isn't happening, the rom will hang on flashing. Like Bulletproof 1.1, it will hang at Apply Kevlar ...please be patient.

Fixed it, flashed a backup :3 Any clue why it did this? I had to format the phone like a million times Xo
::Sense 4.0::

????? That's weird ???????
Sent from my myTouch_4G_Slide using Tapatalk 2

Ok, so my phone was acting dumb. I was finally able to get it to boot, but knock on wood *knocks on wall*. I had to flash to stock (Still S-Off). Now I'm booted and running fine. I have no idea why. :T Puzzles me, also I'm tired as hell. So this might be very random.
I couldn't get my phone to stay on for more than 10 minutes. Sometimes it just wouldn't. Boot. I was not able to get Roms to flash (status 0).
So I (re)flashed CWM 5.5, and that seemed to help. Then I was only able to use backups.
Then I just couldn't get my phone to work :T
So I flash the update in the Hboot to get back to stock.
1st it booted fine. But I rebooted to Hboot, and got funky issues (would not boot past bootanimation)
Flash Hboot update twice.
Then I did two factory resets in Hboot.
Then I got my phone working. I've been slowly typing this over 1 1/2 30 Rock episodes. No reboots :T Should I unlock and get CWM on here? I feel like my issue was not being on a stock kernel. Plus on stock I'm getting crazy battery life.
I'll see how my night charge goes. Hopefully she stays booted :d
Sent from my myTouch_4G_Slide using xda app-developers app

Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.

Blue6IX said:
Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.
Click to expand...
Click to collapse
I just got a replacement phone about a month and half ago. The only Rom it stays stable with is the stock Rom. That makes a lot of sense tho', I was thinking my phone couldn't handle a UV. My phones running perfectly (and faster, and smoother than ever). I'm going to try unlocking it again, and reflashing the recovery. See how far that takes me.

Ok, so I unlocked my bootloader (No recovery). It was having trouble booting. Wouldn't boot with the USB plugged in. But I'm still 100% stock (S-Off, Unlocked). I'm going to run stock for 2 hours, and see if I get reboots.

So my phone acts up on custom kernels, that's what I'm seeing.

So my phone starts acting up when the battery is below 15%, and not running a stock kernel. :T