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.
Related
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
So my just powers off, doesn't matter what state the battery in. It does not reboot. It just turns off. I have no idea what is causing this and I have been running this setup for awhile now without problems.
ROM: BAMF Stripped 1.7
Kernel: leanKernel 1.92x
Any ideas?
engagedtosmile said:
So my just powers off, doesn't matter what state the battery in. It does not reboot. It just turns off. I have no idea what is causing this and I have been running this setup for awhile now without problems.
ROM: BAMF Stripped 1.7
Kernel: leanKernel 1.92x
Any ideas?
Click to expand...
Click to collapse
You're burning up the CPU from overclocking it?
Asside from that obvious first, thought. I'm leaning more and more towards the fact that these sd cards are having issues wiping the info off of them. You know, the one that comes with the phone that's 32GB.
I've noticed that with mine I keep having issues seeing partitions and wiping old information off of the sdcard for that matter.
I won't delve to much in to details but I know for a fact that a couple of times that I've told my phone to wipe info from the sdcard, it leaves stuff behind and i tshows when I boot up in to my freshly installed ROM what ever it may be at the time.
I've even gone as far as booting in to gparted only to see that it doesn't see the partition...
thewebsiteisdown said:
You're burning up the CPU from overclocking it?
Asside from that obvious first, thought. I'm leaning more and more towards the fact that these sd cards are having issues wiping the info off of them. You know, the one that comes with the phone that's 32GB.
I've noticed that with mine I keep having issues seeing partitions and wiping old information off of the sdcard for that matter.
I won't delve to much in to details but I know for a fact that a couple of times that I've told my phone to wipe info from the sdcard, it leaves stuff behind and i tshows when I boot up in to my freshly installed ROM what ever it may be at the time.
I've even gone as far as booting in to gparted only to see that it doesn't see the partition...
Click to expand...
Click to collapse
I have caught it saying that the SD card was inaccessible but I don't see why that would make it power down. I lowered the overclock back down to 1.4ghz to see if it helps.
Just curious.. but are you running the "new" radio that came out with the OTA update? (Obviously not the official OTA, but the leaked version? and no I don't mean GB radio).
Hubby's phone started doing this after he got the OTA. I wasn't even rooted at the time but the new radio started causing his phone to shut down. Mine which was rooted and had received the leaked and rooted version of the OTA was rebooting at random times throughout the day.
This weekend I flashed them both back to the previous radio (Combo #2 in the obligatory radio post) and they've been running ever since with no shutdowns or reboots.
engagedtosmile said:
I have caught it saying that the SD card was inaccessible but I don't see why that would make it power down. I lowered the overclock back down to 1.4ghz to see if it helps.
Click to expand...
Click to collapse
I have mine set to 1.4. There's no reason besides for epenus to really go over that IMO. You don't want to burn the CPU up. Even at 1.4 you need to find out if it likes to be undervolted or uber undervolted as well. Mine was happy with uber undervolt then on the next couple kernels that came out that changed to the undervolted so..
That part is a crap shoot. The sd card is deffinately causing some funky behavior IMO. Probably not shutting down like you said but funky things none the less and I really wish I could get a better handle on it.
I had a program the other day on my computer that seen the partitions fine and now none of them do that I try. I don't know if I'm using the wrong app now or what...
I'm busy getting ready to move in to a house right now though so I'll get to it more later I suppose for now I'm chilling on GB.
I agree with Sam as well a little I suppose but Sam, factory resetting the phone is supposed to fix the new ota update issue or atleast it did for my wifes phone. That was per HTC's advice that we tried that with hers and hers is unrooted not even touched and it stopped it so..
Some people say it didn't work for them but that's neither here nor there..
thewebsiteisdown said:
I have mine set to 1.4. There's no reason besides for epenus to really go over that IMO. You don't want to burn the CPU up. Even at 1.4 you need to find out if it likes to be undervolted or uber undervolted as well. Mine was happy with uber undervolt then on the next couple kernels that came out that changed to the undervolted so..
Click to expand...
Click to collapse
I play a lot of PSX on my phone and the few FPS helps sometime. Also helps with the audio becoming choppy.
And yes, this is the leaked radio but I have been using it since day one. I lowered it to 1.4ghz and I think was it. The rise in temperature outside probably wasn't helping.
engagedtosmile said:
I play a lot of PSX on my phone and the few FPS helps sometime. Also helps with the audio becoming choppy.
And yes, this is the leaked radio but I have been using it since day one. I lowered it to 1.4ghz and I think was it. The rise in temperature outside probably wasn't helping.
Click to expand...
Click to collapse
Sweet glad I could help. You should thank me and Samxxx .
thewebsiteisdown said:
Sweet glad I could help. You should thank me and Samxxx .
Click to expand...
Click to collapse
It happened again last night so it wasn't the OC afterall, I am on the stock radio now.
Happened again with stock radio, I'm out of ideas as to what is causing it.
engagedtosmile said:
Happened again with stock radio, I'm out of ideas as to what is causing it.
Click to expand...
Click to collapse
Mine did this a couple times. I read some stats and realized it was reading the battery as dead when it would happen. So I took the battery out and made sure it was in firmly and correctly, made sure the battery door was on tight and it never happened again.
Is the phone actually powering off or is it just not waking up? If its not waking up then its just undervolted to much. I would try another kernel that's not as undervolted.
Sent from my ADR6400L using XDA Premium App
dlongb13 said:
Is the phone actually powering off or is it just not waking up? If its not waking up then its just undervolted to much. I would try another kernel that's not as undervolted.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Powers off completely.
I think I found the issue, it's the hardware. If I put any pressure on it or if it bends a little, it will power off like its shorting out. (Happens mostly in my pocket while sitting.) Going to talk to verizon about it.
Bad thing is you don't like to use the thank you button so I won't be helping you any more at this point.
thewebsiteisdown said:
Bad thing is you don't like to use the thank you button so I won't be helping you any more at this point.
Click to expand...
Click to collapse
lol okay.
heres your thanks.
Thanks.
My phone seems to be having a similar issue. I'm running BamfGingerRemix 2.1, the MR2 radio, with Nerozehl's Dream Kernel, overclocked to 1.4Ghz, and with swap enabled. The low clock speed is 368.
I have no idea what is causing it, but I'm pretty sure the phone is actually off. I have to do a battery pull before I can get it to boot. This has happened 3 times over the past 3 days. If it happens again, I'm going to call myself from my roommate's phone to see if it is truly off.
I know it isn't from the battery being too low because last night after I got it rebooted, the battery was at 99% (it was on the charger when I tried to wake it). I'm hoping this isn't a sign of something bad coming to my phone.
I've heard some people call this the sleep of death? I'm on aosp (both cm7 and OMFGB) and I've seen this a few times. Werid eh?
Edit: I'm on the 402w1 radio
Sent from my Thunderbolt using XDA Premium App
My phone would also not wake up a few times when I was running various BAMF Roms - I should note that I have only run their ROMs since rooting the phone. It seemed to happen a few minutes after sending a text, not every time but randomly. I haven't changed any of the defaults regarding overclocking, so it would seem strange if that was the reason. I also don't know if it was off, or if it just wouldn't wake up because I had to pull the battery to get it running again.
However, I have been running the newest 3.0 RC3 for a couple of days and haven't seen it happen at all.
Finally got a response from LG mod SmartPhoneGeek at the LG Forum...such as it is.
One of the questions I asked.......How about a log of fixes? A statement of some sort?
"The upgrade will deliver Android 2.3 (Gingerbread) and is expected to provide some performance enhancements, addressing:
•Unexpected restarting
•Battery life
•Front-facing camera operation with Qik Record and Share
•Responsiveness of Car Home"
wifi is still not fixed.
You might have an issue with your phone. My Wi-Fi has never been broke.
Still getting the reboots and SOD- but I didnt do a clean install. I just updated.
This hasn't cured the phone getting hot while charging. It's burning up right now..
Sent from my LG-P999 using XDA Premium App
Way too easy!!
After reading *literally* every post about this update since I saw the announcement on TMONEWS I was expecting the worst..
The joke was on me!
The download, and install took all of 15 minutes and I didn't have a single adrenaline moment. My phone rebooted, it took a few minutes to get past the G2X screen and BANG! there it was! All my data, all my apps, I haven't finished playing yet but I can say, honestly, this was WAY TOO EASY..
Exact same for me!
One of the rare moments I wish I was unrooted. Not because I want stock or anything, just envious of the joy everyone is feeling who gets to update from stock.
Sent from my LG G2x
TJBunch1228 said:
One of the rare moments I wish I was unrooted. Not because I want stock or anything, just envious of the joy everyone is feeling who gets to update from stock.
Sent from my LG G2x
Click to expand...
Click to collapse
why don't you just flash back to stock and unroot?
you dont even need to unroot, just roll back to stock lol
tq745 said:
why don't you just flash back to stock and unroot?
Click to expand...
Click to collapse
Really?... I just said I don't want stock. My custom GB ROM is better than anything LG will put out. I was saying I'm envious of the joy the stock folks are feeling at being able to upgrade their stock build. Not what they are actually accomplishing, just the happiness they are feeling.
Sent from my LG G2x
Has anyone mentioned to LG that this camera software is worthless?
mmapcpro said:
Has anyone mentioned to LG that this camera software is worthless?
Click to expand...
Click to collapse
Considering this update is not meant for consumer consumption really, I'm sure they know it's a pos.
I was reading TMO news 15 minutes before this was dropped, left work and got home, fell asleep and when I woke I just checked at random and sure enough, there it was. Gonna stick with Ultimate rom till someone makes a custom rom based off the new stuff, hopefully we can port the camera app over from 2.2 maybe?
Do a quick reboot or try to go to recovery by vol dwn and power...mine went and factory reset when I was gonna flash back. No root no nandroid no nothing. Guess I'm gonna wait for a rooting method now. Cause this sucks. Would rather not have updated at all.
Sent from my LG-P999 using XDA Premium App
TJBunch1228 said:
Really?... I just said I don't want stock. My custom GB ROM is better than anything LG will put out. I was saying I'm envious of the joy the stock folks are feeling at being able to upgrade their stock build. Not what they are actually accomplishing, just the happiness they are feeling.
Sent from my LG G2x
Click to expand...
Click to collapse
Yea right... I get that feeling every morning when I wake up. *bling* There is an update for your rom
Asus Transformer 3.1 pwnd
www.MiiWiiChat.com
www.SnapSiteAdmins.com
TJBunch1228 said:
One of the rare moments I wish I was unrooted. Not because I want stock or anything, just envious of the joy everyone is feeling who gets to update from stock.
Sent from my LG G2x
Click to expand...
Click to collapse
Ditto LOL...Everyone else is like a kid at Christmas. I"m sitting here with my thumb up my arse LOL
Sounds like some of you sickos are having your full 3 inch erections for the first time. Feels great!
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.
In the past month I bought a used mytouch 4g slide off ebay in good working order. Lately though the phone keeps shutting off on me whenever I try to do anything. The phone is rooted with S-ON OFF.
I have installed many different roms but of late they all seem to be shutting off. I had this problem but it only happened every few days beforehand. After install of the rom I am waiting around 7 minutes before using my phone. Right now I'm back to my G2, which in my opinion feels better and battery last longer. I also dislike Sense but the camera is fantastic compared to the G2.
I have used Bulletproof 1.1, DoubleShot Lite 1.2.3, and MikTouch-0.7 and all had the same problem.
montusama said:
In the past month I bought a used mytouch 4g slide off ebay in good working order. Lately though the phone keeps shutting off on me whenever I try to do anything. The phone is rooted with S-ON OFF.
I have installed many different roms but of late they all seem to be shutting off. I had this problem but it only happened every few days beforehand. After install of the rom I am waiting around 7 minutes before using my phone. Right now I'm back to my G2, which in my opinion feels better and battery last longer. I also dislike Sense but the camera is fantastic compared to the G2.
I have used Bulletproof 1.1, DoubleShot Lite 1.2.3, and MikTouch-0.7 and all had the same problem.
Click to expand...
Click to collapse
Are you doing full wipes between ROMS? Sounds like a hardware issue to me because MikTouch has Stock Kernel
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Are you doing full wipes between ROMS? Sounds like a hardware issue to me because MikTouch has Stock Kernel
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Yup, always wipe everything. As I got the phone used that limits my options for hardware issues.
montusama said:
Yup, always wipe everything. As I got the phone used that limits my options for hardware issues.
Click to expand...
Click to collapse
Yep looks like you row the same boat I do and I pay outright for all my devices
Sent from my myTouch_4G_Slide using Tapatalk 2
Definitely a hardware problem. Multiple roms should not all have that same problem. Either your battery, battery connection might be bad. But with such a general problem, it can be nearly anything
(exactly why I don't like buying used phones)
Phone Powering off by itself Solved!
So I have bought several phones over the past year cause of this same problem. I take it to the service provider for troubleshooting and all they keep telling me is its a hardware issue. They do a hard restart and blah blah blah. Long story short. IT NEVER FIXES THE PROBLEM... BUT.... I realized it was the battery slipping loose. every time you place the phone down it gently slips out of place. Of course it doesn't fall out cause the phone has a back. So. I just taped my battery to the inside of my phone. PROBLEM SOLVED!!!! Did this with my Samsung Conquer 4g... and with my friends 4g slide. It stopped the mysterious powering off, Try it and see it if works for you! Hope this helps someone!
kays123 said:
So I have bought several phones over the past year cause of this same problem. I take it to the service provider for troubleshooting and all they keep telling me is its a hardware issue. They do a hard restart and blah blah blah. Long story short. IT NEVER FIXES THE PROBLEM... BUT.... I realized it was the battery slipping loose. every time you place the phone down it gently slips out of place. Of course it doesn't fall out cause the phone has a back. So. I just taped my battery to the inside of my phone. PROBLEM SOLVED!!!! Did this with my Samsung Conquer 4g... and with my friends 4g slide. It stopped the mysterious powering off, Try it and see it if works for you! Hope this helps someone!
Click to expand...
Click to collapse
I actually have had a problem like this before with the battery contacts. It seems very snug in the 4g slide.
gtmaster303 said:
Definitely a hardware problem. Multiple roms should not all have that same problem. Either your battery, battery connection might be bad. But with such a general problem, it can be nearly anything
(exactly why I don't like buying used phones)
Click to expand...
Click to collapse
I'm going to say its a hardware problem but my phone has been on for days now, though I'm not using it as I'm using my old G2.
A part of me just wants to stay with the G2 but I miss the excellent camera on the 4g slide. Of course I need to find a use for the slide though. Gotta love turning a very minor decision into a big deal.
If you're going to go used . if you have your area supported in craigslist buy it from there. Then atleast you can check for full functionality before you fork any dough over. I dont think ive ever bought a new phone in my life and never got a lemon
I've bought most of my phone's used and never had a problem. I would get a new phone but my phone selection is limited due to the QWERTY and good camera I want.
My phone tends to turn off when connected to WiFi with WiFi calling on... or at least it used to with stock and the CM 7 kang, but I haven't tried other ROMs.
Since the CM 9 alpha just got WiFi calling, I haven't had much time to test for that yet.
Have you tried not using WiFi or WiFi calling?
Hi all,
I'm having a similar shut off issue, only mu phone is fully stock. No root, no s-off, and no rom. It seems to be completely at random either by using the browser or any app or no app at all(after I've set my phone down, I've tried using it only to find it shut off). I did a factory reset and the problem persist, though not as often. Any ideas? Thanks!
mojoffdawal said:
Hi all,
I'm having a similar shut off issue, only mu phone is fully stock. No root, no s-off, and no rom. It seems to be completely at random either by using the browser or any app or no app at all(after I've set my phone down, I've tried using it only to find it shut off). I did a factory reset and the problem persist, though not as often. Any ideas? Thanks!
Click to expand...
Click to collapse
Sounds like warranty replacement is in your future...
Hastily spouted for your befuddlement
Coug76 said:
Sounds like warranty replacement is in your future...
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Only if the phone came from TMO though
montusama said:
Only if the phone came from TMO though
Click to expand...
Click to collapse
HTC doesn't care where it came from.
Hastily spouted for your befuddlement
wifi calling / replacement
mojoffdawal said:
Hi all,
I'm having a similar shut off issue, only mu phone is fully stock. No root, no s-off, and no rom. It seems to be completely at random either by using the browser or any app or no app at all(after I've set my phone down, I've tried using it only to find it shut off). I did a factory reset and the problem persist, though not as often. Any ideas? Thanks!
Click to expand...
Click to collapse
Did you have any luck getting a replacement?
Was WiFi calling on? (My phone would reboot even stock randomly when WiFi calling was in use.)
qayshp said:
Did you have any luck getting a replacement?
Was WiFi calling on? (My phone would reboot even stock randomly when WiFi calling was in use.)
Click to expand...
Click to collapse
I did. Same thing happened with the replacement. I rarely use WiFi and I make sure WiFi calling's off when I do use it. I thought it might be an app but so far, it's turned out to be the battery. I got the phone in February so I didn't think it would go bad so soon. Got an Anker and been restart free since.