I was installing the new Myn's Warm lastnight upgrading from the previous version. It did not install properly and COMPLETELY BRICKED my phone. It won't turn on, can't connect to computer via USB, nothing at all! Anyone else have this problem? OR any solutions other than taking to Sprint?
I doubt that your phone is bricked. Hopefully you DO have a rooted EVO though. I would plug it in and let it charge. Then take out the battery and put it back in and turn it on while holding down power and volume down keys to boot into recovery. Also hopefully you made a nandroid backup so restore that and go from there. I had no problems with flashing RLS5 at all. Hopefully this helps. Otherwise maybe someone with a little more knowledge can help you...
Sprint is DEFINITELY not the answer...
do a battery pull and try to get it to hboot. then try and run the RUU. if not you may have to take it to sprint.
The phone won't charge, won't turn on, can't hboot. I do have backups if I could get it to turn on I could restore it. Had no problems before. I will attempt to charge it as you have suggested but I even put a different fully charged battery in and the phone does not even make at attempt to turn on. I agree I doubt that Sprint is the answer
did you flash any radio updates? any prls, I've never heard of flashing a rom making a phone brick, but definitely heard of radio updates bricking devices.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
i really doing think his update bricked your phone
This means that while installing Warm you bricked your phone. Don't give his ROM a bad name.
I would recommend trying to charge it and maybe try a different battery, but then just run the RUU and go from that. I had the same problem with RLS 4.
Sent from my EVO using XDA App
If you used the package to update the pri, radio, etc then that may be the problem, hopefully you aren't bricked.
Sent from my PC36100 using XDA App
Are you sure that you didn't flash the radio? I flashed Myn's rom last night and I didn't run into any issues, in fact I've never heard of a rom bricking a phone, that usually happens when a radio flash goes terribly wrong. Anyhow, you can take it back to Sprint since it's still under warranty and they will replace it for $35.
CheesyNutz said:
i really doing think his update bricked your phone
Click to expand...
Click to collapse
ive heard several people say it has in fact jacked their phones up. hence why i have not upgraded to it yet.
I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.
the radio update isn't included with the rom.
it's also been highly advised in the warm thread itself to flash just the radio, then just the wimax, then perhaps the nv/pri, because so many people have been having trouble with the pri update.
the radio combo pack isn't bundled with anything else and, right now, many think it should be avoided for reasons just like this.
not a solution, just clarification and friendly advice for anyone else who's curious about possible trouble with the upgrades.
I updated my radio/pri/wimax and all that jazz before the last Fresh update, so I had no need to this go around. I simply wiped data/dalvik/cache and flashed the RLS 5, with no problems. I did run into issues after I tried restoring my apps + data, but that was a Titanium Backup issue
arcurtis said:
I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.
Click to expand...
Click to collapse
Just my 2 cent.. often times we flash before reading the thread and then complain about a kernel,ROM or theme.
After reading what you said I can only come to the conclusion that you and all the others complaining about the radio update are obviously impatience. All who have had problem with the update on the radio all stated their phone sat on the white screen and they did a battery pull.
Yet the radio update thread says it will/can take up to 30 min to flash. The best way to check your phone would be to use another battery. I have never heard a bricked phone that doesn't cut on. That's a battery issue.
What kernel were you using before flashing?
What ROM?
What's your hboot?
Sent from my PC36100 using XDA App
I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.
arcurtis said:
I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.
Click to expand...
Click to collapse
Does the phone attempt to charge when you plug it in?
Sent from my PC36100 using XDA App
I can confirm brick.
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.
Nope the phone will not even charge. I've changed batteries and chargers. I am assuming I am one person who has just had extremely bad luck with a random flash. I was running Myn release and did a backup and wipe then phone would not reboot and completely shut down. I got the android guy with the arrow and then it went completely dead and won't turn back on.
dth4310 said:
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.
Click to expand...
Click to collapse
That is almost exactly what happened to me. I considered doing the same thing but don't really want to chance getting busted for a rooted phone
i've never flashed a radio update, i'm too chicken lol.
the quickest way to brick any phone is a f'ed up radio flash. or pulling the battery while flashing a radio.
i would take it to sprint and tell them you accepted a over-the-air update and then your phone shut off and this is what happened.
Related
I was attempting to flash 2.x using behnaam and lox's rom.
Rom: http://forum.xda-developers.com/showthread.php?t=592596
Here is the HBoot info previous to my tinkering:
HERC XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
SEP 1 2009,19:18:45
Phone is rooted using adb.
I used unlockr's guide to flash a custom recovery image onto my CDMA hero and that worked fine, here is the guide I followed:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I first moved the radio recommended for the rom by the dev to root on the sd and renamed it update.zip. After, I used the recovery image to wipe, then apply update.zip from sdcard. It seemed to flash fine, as it said please select reboot to complete, which I did, and it completed and rebooted the phone.
Once rebooted it gave me the android installing software image without anything else for a while, then turned off. I cannot seem to awaken my phone with any combo of keys or by plugging it into its use cable. The charging led doesn't even light up anymore.
Well I seem at the moment to be SOL, unless someone can come by and throw me a bone. I really am at a loss as to what I did wrong, as I have always read to do radio first. Not to mention as I watched it install radio it said it was installing radio.
Thanks for the help everyone.
You attempted to flash a GSM ROM to your CDMA phone, this is why your phone is bricked. I'm not sure if its possible to recover, people with more experience than I have can help you there. The problem was flashing a GSM ROM to CDMA. You are not the first to have done it, we all mess up from time to time.
Uuuh Umm...that software was for the GSM hero's NOT THE CDMA Hero.............bless your heart.
Ah **** I thought it was CDMA, guess it was a bad idea jumping into roms while still a noob.
Yea I only got the radio installed, not the rom, although that probably doesn't make a difference.
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Hmm well if worst comes to worst I'm going with what I read on another thread and saying that I was installing the update that it found when I went to phone details and halfway through the update the phone just turned off and won't turn on anymore.
According to the other thread once it is bricked beyond belief and you play stupid they can't prove you wrong.
Best case scenario they replace it, and I won't feel bad seeing as it was a defective phone that is allowing dust to enter under the screen. But that who ordeal is an entirely different rant...lol
Sigh
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
Go......Now......Move with haste...
gu1dry said:
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Click to expand...
Click to collapse
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
flipzmode said:
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
Click to expand...
Click to collapse
All is lost!!!!
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
unfortunately, flashing the GSM radio on pretty much destroys the phone.
i think its got something to do with the voltage and electricity used by the GSM radios. probably higher than what the CDMA radios use, so you didn't really brick your phone, you 'fried' it in a sense.
sorry bout that... but if you have the equipment protection plan you can probably get it replaced real easily, since the sprint people probably won't really understand what's wrong.
again I am reminded why I dont screw with radios
willowmp said:
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
Click to expand...
Click to collapse
Once you do get it replaced and you want to put a custom ROM on it, look at the first page of this forum and you'll find sticky threads regarding four different ROMs you can put on your phone (two production release and two experimental betas).
I would suggest either MoDaCo's rom or Fresh rom. I use Fresh in mine and had no problems (although I have used MoDaCo's before and also had no issues).
Also, if you want to root the phone, there are also sticky threads that will tell you how to root your phone from Windows, Mac and Ubuntu.
Good luck.
Yep thanks everyone.
Yea I figured once no buttons would do anything and the leds wouldn't even light up for charging that it was pretty much fried. Definitely got that sinking feeling in the pit of my stomach.
I definitely should have come into this section specific to my phone and read this info instead of just doing tons of searches and getting mixed up.
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Once again thought, thanks for the help. Especially to a noob that made a real noob mistake lol.
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
willowmp said:
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Click to expand...
Click to collapse
Well once you are retry the flashing on your new phone, just msg me & I'll give you my contact info & I'll walk you thru it.
willowmp said:
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
Click to expand...
Click to collapse
while the attempted flash was boneheaded , this (what I quoted) was very smart. I've had them try to reverse the decision and noted on my account in the past. All ended well, but a hard copy of the convo between me and Corporate would have been nice to have.
props for a good idea.
if you don't want trouble with rooting and flashing new ROMs to your phone, try flipz's pre-kitchen. just to try it, i RUU'd my phone and re-rooted it through that app, and its simply amazing. you just sit back and watch, don't even have to do anything.
Ok so its pretty funny but whoever it was who says that once you flash for the first time its addictive, I do have to agree. I will be getting my phone tomorrow because they had to replace it and I will be flashing, although this time I will play it safe and triple check before I get click happy...lol
So what are the danger zones in flashing, like what can brick or kill your phone? I know playing with radios can kill it if the wrong one is flashed, and I know powering off or interrupting a flash will kill/brick, but what else.
I know people said firmware alone usually will not brick you.
willowmp said:
So what are the danger zones in flashing, like what can brick or kill your phone?
Click to expand...
Click to collapse
Well obviously it can brick your phone if you flash the Radio I kid, I kid
willowmp said:
I know playing with radios can kill it if the wrong one is flashed
Click to expand...
Click to collapse
With the CDMA Hero, you do not have to flash the Radio. So if your attempting to flash the Radio, you're doing it wrong.
willowmp said:
I know powering off or interrupting a flash will kill/brick, but what else.
Click to expand...
Click to collapse
Well if the custom recovery is installed (RA-heroc), if the phone looses power while flashing the firmware, you are usually still safe, because you (usually) still boot into the recovery without issues.
Like I already said, if you want I can walk you thru the entire process thru an IM client, Steam, or Skype.
Oh ok thanks, I'm actually headed up to PA for a little trip but definitely will hit you up on that offer when I get back.
***Put away your pick forks and torches, the search function is disabled the only stuff I keep finding on google is either people overheating their phones or having the same issue as me but all the replies are retarded.***
It's really annoying. About 75% of the time I get on youtube or try downloading something big like a cyanogen update my phone restarts. I've been putting up for it for quite some time now but I'll be depending on my phone next week and this **** needs to stop. It's not the rom since it happens when I install fresh rom (to do prl and all that other sprint crap). I usually cruise with cyanogen (6.1 atm). It happened with mym's warm sumthin rom too. I don't let it overheat... EVER!... I've noticed the stand acts like a heat dissipater so I always keep it open when in use. Also I'm constantly checking to see if it's getting warm. I don't overclock/undervolt it (unless this is a feature added to cyanogen... which to the best of my knowledge isn't... I just skim the changelogs though so I might be wrong)
The phone also restarts when I play need for speed, but I don't really care about that. Would really appreciate help with this one. I'm sure there are other people getting screwed over with this one.
My phone:
Hardware version: 0002
(One of the phones that were handed out for google i/o prior to the official release.)
Cyanogenmod 6.1
Stock cyanogen kernel
Baseband:2.15.00.11.19
PRI: 1.77_003
PRL: 60674
Did it start happening when you updated to the latest radio? I thought I read something about people having freezing or rebooting issues with that radio and cm6, but I could be crazy. I'm almost certain that if you're running a sense rom, it needs to be based off 3.70 to use that radio.. so if the Fresh rom you tried was a little old, you may try the latest. If all else fails, I'd wipe, flash Calk's combo zip with radio/pri/wimax/nv, and then flash a 3.70 based sense rom (I recommend Calk's EViO rom). If problems still persist, it may be a hardware issue.
My phone was doing this with the latest MIUI rom and one of the new gingerbread ROMs that's going around ( I forget which). It only happened once using CM6 nightlies. For me the problem was with the kernel that I was using and my wifi at home. Experiment with some different kernels, that's what I did. The most successful combination is the one that's in my signature, the random reboots ended.
Here's thread dedicated to this problem.
Good luck.
xviiivx said:
Did it start happening when you updated to the latest radio? I thought I read something about people having freezing or rebooting issues with that radio and cm6, but I could be crazy. I'm almost certain that if you're running a sense rom, it needs to be based off 3.70 to use that radio.. so if the Fresh rom you tried was a little old, you may try the latest. If all else fails, I'd wipe, flash Calk's combo zip with radio/pri/wimax/nv, and then flash a 3.70 based sense rom (I recommend Calk's EViO rom). If problems still persist, it may be a hardware issue.
Click to expand...
Click to collapse
Nah, I've had this problem since 6.0 if i'm not mistaken. I did try flashing calk's combo but it gave me an error. It did it again so got my ass back on the computer to make this post. Right now I have fresh latest. Btw I install using rom manager and clockworks flash image. I used to use amonra but switched to clocks and for some reason my phone wont switch back to amon...
@semperlux
thanks for the link. i'll go read that now :3
pirokosan said:
***Put away your pick forks and torches, the search function is disabled the only stuff I keep finding on google is either people overheating their phones or having the same issue as me but all the replies are retarded.***
It's really annoying. About 75% of the time I get on youtube or try downloading something big like a cyanogen update my phone restarts. I've been putting up for it for quite some time now but I'll be depending on my phone next week and this **** needs to stop. It's not the rom since it happens when I install fresh rom (to do prl and all that other sprint crap). I usually cruise with cyanogen (6.1 atm). It happened with mym's warm sumthin rom too. I don't let it overheat... EVER!... I've noticed the stand acts like a heat dissipater so I always keep it open when in use. Also I'm constantly checking to see if it's getting warm. I don't overclock/undervolt it (unless this is a feature added to cyanogen... which to the best of my knowledge isn't... I just skim the changelogs though so I might be wrong)
The phone also restarts when I play need for speed, but I don't really care about that. Would really appreciate help with this one. I'm sure there are other people getting screwed over with this one.
My phone:
Hardware version: 0002
(One of the phones that were handed out for google i/o prior to the official release.)
Cyanogenmod 6.1
Stock cyanogen kernel
Baseband:2.15.00.11.19
PRI: 1.77_003
PRL: 60674
Click to expand...
Click to collapse
There is a thread on here for evo official random reboots. There was a lot of troubleshooting done, but most of us have a Hardware issue. A lot of people got there phones swapped out from sprint.
I picked up my launch day Evo hardware 0003. It always rebooted (even before rooting), but for the last 2 months it got really bad. No matter what I tried (SD card, Formatted SD card, no SD card, CM, Sense, Stock, rooted, unrooted, full wipe with no apps installed), it rebooted.
I purchased at bestbuy with their warranty. I had to deal with bestbuy warranty once already, and didnt want to ship it out and have them not find anything. I went to 3rd party sprint store that did repairs. Showed them the problem and they ordered me a new phone. I had to add Sprint TEP on, which I had no problem doing. I went and cancelled my bestbuy black tie protection.
Have new Evo for a month now, no reboots.
Before the EVO reboots do you notice a fair amount of heat??
Your PRI is the wrong version, just sayin'
Same problem...though i was blaming it on the super battery charge kernels I was using. Found that it is still a problem without the battery mods but less frequent.
It seems to me to happen only when downloading while charging and the screen is off. Also, if I am listening to something at the same time it wont reboot. Lastly, I've caught it a couple of times right before it happened and the phone becomes completely unresponsive.
I'm running with all the latest updates on Azrael's rom.
Sent from my PC36100 using XDA App
Hey everyone,
I just put the cyanogenmod 7.0.2.1 on my HTC EVO 4G about a month ago. At first it was working fine, now it will just randomly restart not while I'm ever using it, but when it is sitting idle it will just restart at odd times. Has anyone else had this issue?
Everything else with the ROM is working awesome. Please Help.
No issues here, why don't you come up to date and flash the stable 7.0.3.1. Are you running any custom kernels by chance?
Here's the link to 7.0.3.1 just flash over your current rom and wipe dalvik-cache.
http://mirror.teamdouche.net/get/update-cm-7.0.3.1-Supersonic-signed.zip
Oh thanks, been really busy with work, and hadn't had time to check for any updates. I appreciate the help very much. DL'ing the new ROM now.
Upgrade to the newer version. Maybe it'll help? Definitely clear cache & dalvik when you update.
Evo 4G / CM 7.0.3.1 - Tiamat 4.0.2 SBC / XDA Premium
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What ROM did you go to?
misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
Yeah I like the CM7 ROM, but just can't take the restarts. I am going to upgrade to the newest stable release and see if that fixes it. I would like to stay with the CM7 if at all possible.
Swype
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
beaukincade said:
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
Click to expand...
Click to collapse
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
dirkyd3rk said:
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
Click to expand...
Click to collapse
no its gone and won't let me use titanium backup to reinstall it either
beaukincade said:
no its gone and won't let me use titanium backup to reinstall it either
Click to expand...
Click to collapse
Do you have the latest titanium backup version? If you can't get it going the swype apk is all over the place lol. *wink wink*
Get the latest version (beta) from their site.
http://swypeinc.com/
dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
I have ran many different roms and CM7 was the ONLY one that caused my phone to reboot many times a day. A quick google search can show you threads about owners who had phones that bricked after running CM7. I never said it was gospel, I just dont need my phone rebooting multiple times during the day and it was way more often when I had wimax connected. CM is a great rom but its not the second coming of Android and not worth my phone rebooting during the day.
And I am running Smooth N Sexy V1.2 A sense ROM that looks like gingerbread.
Reboots
I've been through several ROMs now and the reboot problem appears to be not a ROM issue!
Here is the story. I had started with Baked Snack, very good, but I wanted more battery and to try CM and get away from Sprint messaging update nag.
CM worked great, I updated to 7, until the reboots started to happen during heavy use of Angry birds.
So I restored to early CM 6.x, and reboots continued off and on every few days, getting progressively worse.
So I tried Warm 2.2, same issues.
I went back to CM7 and still trouble.
I went to Fresh and It was fine for a week, and then on Friday, (I noticed that Friday was significant), reboots again.
So after a month of this the reboots are so bad that I can't use the phone. I called Sprint, de-provisioned the EVO, went back to my Palm, and then unrooted and went back to Stock ROM, but with no Cell access.
The phone is stable now. As long as it's off the Sprint Cellular network!!!
All of the reboots were related to cellular activity. Messages coming in, ads being updated, calls coming in, tower switching, roaming, or worse of all, no tower signals at all.
I will post back here if the phone remains stable without cellular. But all of the research I have done on the issue has pointed to cellular access. I am on wifi and all the apps and functions are working without issues so far. I am starting a dialog with HTC to see if there is a hardware problem.
The reboots also caused heat in the general area of the SD card...don't know what else is there but I do know the cellular antennas are on that side of the phone. Leaving the battery out all night, after an off state recharge would help stabilize the phone for a while, including cache wipes and factory resets.
But once the phone had been on for a while, or Friday morning would come, the reboots would continue.
I have been a computer nut for 30+years and I solve issues for a living. I strongly suspect the radio hardware or firmware as the culprit in this reboot issue. Every other account of this has had similar connections to the radio use.
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
dirkyd3rk said:
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
Click to expand...
Click to collapse
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
misterzeno said:
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
Click to expand...
Click to collapse
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
dirkyd3rk said:
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
Click to expand...
Click to collapse
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
misterzeno said:
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
Click to expand...
Click to collapse
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
dirkyd3rk said:
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
Click to expand...
Click to collapse
You win, you obviously have the bigger nerd e peen. I should go back to a flip phone. *Bowing to phone gawd*
You wouldn't be as much as an ass if you happen to suggest ONE resolution to the rebooting.
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
nzube14 said:
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
Click to expand...
Click to collapse
I'm just trying to learn from experience after all the flashing when you started to get freezing and acting up did you flash that one file on Virtuous Unity 2.35 page that states if you get phone freeze to flash the file
nzube14 said:
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
Click to expand...
Click to collapse
As of now, there is no way to fix it. Strange though, my old one had a dead eMMC as well but I.could still go in CWM
Sent from my HTC Glacier using xda premium
Always remember, after rooting you should Check your eMMC
If the eMMC is good, try flashing otherwise report it to T-Mobile
SEMO4G is the "good" one & M4G2DE is the name of the "bad" one.
__________________
If this replay helped, please hit the "Thanks" button.
Flashing that one file? I don't know which one you are talking about. If you saw it, could you point me to it, please?
Also, if your eMMC is bad, you could report it to T-Mobile? How? I was asking them about the eMMC, and they (the tech department) knew nothing about it. -__- Yeah, I had the M4G2DE. Although looking at this thread (http://forum.xda-developers.com/showthread.php?t=1081243) it seems that the SEM04G is still bad, or am I just confused?
Don't get confused. If you get just SEMO4G it is "good"
Try for yourself
Download terminal emulater
Type in:
su
(to gain root permission)
Than type in
cat /sys/class/block/mmcblk0/device/name
__________________
If this replay helped, please hit the "Thanks" button.
If your eMMC is bad, don't try to flash any custom Rom.
If you try to modify the system, the phone will get damaged.
febycv said:
Always remember, after rooting you should Check your eMMC
If the eMMC is good, try flashing otherwise report it to T-Mobile
SEMO4G is the "good" one & M4G2DE is the name of the "bad" one.
__________________
If this replay helped, please hit the "Thanks" button.
Click to expand...
Click to collapse
No. Check eMMC before rooting. That way, you will not have warranty problems.
Sent from my HTC Glacier using xda premium
Just to throw it out there though, it's not definitive that your phone will brick when you have the bad eMMC.
I used to have the bad eMMC before I exchanged it out for an unrelated problem. I flashed a ROM on that phone about couple times a week for 3-4 months with no issues. I've even seen some that have had the bad chip since day one and flash almost every CM7 nightly and still haven't had a problem. So my guess is that if your bad eMMC doesn't fail fairly soon and quick then you should be in the clear.
Ive had the bad eMMC since day one and have flashed many roms of all kinds. Knock on wood, i have had no problems
cowboy2844 said:
Ive had the bad eMMC since day one and have flashed many roms of all kinds. Knock on wood, i have had no problems
Click to expand...
Click to collapse
Yeah my point exactly. All of the failed ones are highly documented so every one thinks every "bad" eMMC is going to fail but who knows how many people with that eMMC has actually not failed?
I'm another one with the "bad" eMMC, so far no problems flashing roms.
I have the good eMMC chip and this is my 3rd failure. -.- after rooting using visionary+ it seems like data partition gets borked either while formatting or flashing rom.
CWM outputs unable to mount /data
lmao
anyway downloading pd15img.zip lets see what happens (I know I will lose root and my eng bootloader but oh well atleast i might get my phone back xD)
_ice_ said:
I have the good eMMC chip and this is my 3rd failure. -.- after rooting using visionary+ it seems like data partition gets borked either while formatting or flashing rom.
CWM outputs unable to mount /data
lmao
anyway downloading pd15img.zip lets see what happens (I know I will lose root and my eng bootloader but oh well atleast i might get my phone back xD)
Click to expand...
Click to collapse
Have you tried format the SD card with sdformatter v.2.0 or any other program to fat32 then try gain full root and put CWM on it to see if it stops that unable to mount problem
Sent from my HTC Glacier using XDA App
Just got another replacement, and looked up eMMC chip. SEMO4G!
With good screen as well! Hopefully, no more bricks.
Yeah I have the bad eMMC on a Mobilicity Panache. But so far nobody with a Panache (as opposed to MT4G) has reported failure, even though at least half of them have the "bad" eMMC. And seeing as a thread I started here is the only guide that speaks directly to rooting the Panache, I would expect any bricks to be reported on that thread.
Hello all. I am hoping I can get some advice as to what to do about my wife's phone(epic 4g). Her phone is completely stock and has never had any custom rom or anything flashed to it. Over the last three months, the phone has semi-bricked itself 3 times. The phone will just power off by itself and when it is rebooted, it gets stuck at the "samsung" screen. The only way I can get the phone back to normal is by flashing DI18 with Odin v1.85 (no other versions work). Anyway, my wife obviously does not want an unreliable phone. I should also note that about 8 months ago, my 2 year old son took my wife's phone and threw it in the toilet. After taking the phone apart and drying it, the phone worked perfectly for the following 5 months. For that reason, I do not think it is a good idea to have sprint look at it because the water damge indicators will be colored. I have seen a thread here that talked about calling sprint and complaining about the epic and in turn getting a new nexus s. I am not sure what to do. I cannot afford another phone. my wife uses her phone as the house phone as well. The phone bricked itself yesterday so I flashed the stock DI18 rom. I then tried to flash EC05 and it bricks itself again. Even the OTA update bricks the phone when ran. I really appreciate any help/suggestions the community can provide.
Thank you
Sent from my SPH-D700 using XDA App
Interesting problem you have there. I barely remember Di18.
I would use Odin to flash the EC05 stock rom. QBKing77 has an awesome video showing exactly how to do that. That would not brick your phone unless you are using the stock cable. Get a new one. First boot will take a little bit. Here is the link, the description includes all necessary downloads. I would fresh download everything even if you think you already have it. http://www.youtube.com/watch?v=YQ2g6J1JgjU
There is no reason it will Odin to DI18 and not EC05. Water damage doesn't force the phone to like one rom over another. If the others are "not working" as you said, then you are doing something wrong. Follow the video to a T and it will work.
If you want more I would the one click root it with CMW 3101 and remove all of the sprint bloat. Not necessary, but will help the phone a bit.
If the water indicator has already changed, what is stopping you from using a custom rom that is more stable? You might not have as many issues.
Thank you both for your replies. I am using the stock cable, so I will try a different cable. It may be possible that I am doing something wrong as far as flashing roms. It has been a while since I have flashed anything to my phone. Again, thank you very much for the help!
Sent from my SPH-D700 using XDA App
I am just so confused as to why the phone semi-bricks itself every so often. My wife doesn't do anything out of the norm with her phone. I guess the only likely possibility is that the water slightly damaged something.
Sent from my SPH-D700 using XDA App
Arion02 said:
I am just so confused as to why the phone semi-bricks itself every so often. My wife doesn't do anything out of the norm with her phone. I guess the only likely possibility is that the water slightly damaged something.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Like I said, water damage will not cause your phone to only be flashed to DI18. Now the random reboots may have something to do with the water damage, without more info as to what is happening when it reboots I have no idea. Maybe a custom stable ROM with voltage control set correctly would help with that?