I ran a couple of searches on Google( and in this forum) to try and find the original thread about this issue, however I didn't find it so I'm posting here in case anyone else can be saved by this fix.
First, some background:
I have been running CM10 Nightlies for almost a month now, also using the leaked Jelly Bean radio version T999UVLI2 with absolutely no problems. Everything was working great, data, ROM, etc. (Prior to that I was on Stock ICS, rooted. Had not run any custom ROMs whatsoever).
I noticed after flashing the latest CM10 Nightly (Oct. 14) that my phone had started acting a little weird - nothing drastic mind you, just a few glitches here and there. The weird thing was, all of the previous nightlies I had flashed pretty much worked flawlessly for me, minus a volume issue when in-call which was a known bug. I had done a clean flash as I always do, so I attributed the glitches to a possible bug or two in the latest Nightly and figured it would probably be resolved in the next release. No big deal.
Yesterday afternoon, after reading a thread that is tracking all available T-Mobile radios by region (to see what works best in your area) I saw someone who posted that the T999UVLI3 radio gave them the best speeds, and they happened to live in the same exact city as I do here in Southern California. So I decided to flash the new radio using Team Sonic's Modem flasher, which I used in the past to flash the LI2 radio that I was currently on. I flashed the T999UVLI3 radio and found that it did indeed provide better data speeds than the LI2 radio, so I was pretty happy about that. Used my phone all day/all night with no problems, everything was great.
I always leave my phone plugged in at night so that I have a fresh charge in the morning - this morning I turned off my phone while it was still plugged in as I leave it off during the drive to work to save a little battery before I start my day. Typically I unplug it first and then turn it off, but not always. So nothing really out of the ordinary there.
I get to work and turn on my phone, and all of the sudden I notice that I have no bars - at all. It doesn't say "T-Mobile" at the bottom of my lock screen. I figured it was just taking it's time booting up, which would be very weird as it never does that, but I waited. And waited. Nothing. Now I'm starting to get a little worried.
Went into settings and checked "About Phone" and it said my Baseband version was "unknown". Oh crap. IMEI, unknown. Serial number, unknown. GREAAAAT
For the life of my I couldn't imagine how this could happen when I didn't even do anything from last night to this morning. I started going over everything I had done recently to my phone.. the power off while plugged in, the nightly update to the Oct 14 build, then it hit me.. the new radio version. Maybe that was it
In a desperate attempt I booted into recovery and ran Team Sonic's Modem Flasher and flashed back to T999UVLI2. Rebooted the phone and... BAM! Back to normal. W...T...F..?
If anyone loses their IMEI, before going through the entire injection fix process, try reflashing a radio. Worked for me!
Any theories on why this happened? Many people have been using the T999UVLI3 radio, I believe without any issues.. but I could be wrong. Anyone flashed that radio and lost their IMEI?
Related
So I've had my EVO since launch and it's been properly rooted and running various ROMs for over a month. Suddenly I've been having incredibly frustrating random reboot issues. It seemed to all start when it randomly began rebooting during navigation (other GPS apps seemed ok). So it got stuck in a boot loop and I wiped everything and installed the latest nightly of CM6 (this was probably around 8/2). That seemed to fix it.
Until now. For the past few days the phone has been rebooting randomly. Once it reboots randomly once or twice it gets worse - the phone will reboot before I reach my home screen over and over again (sometimes I can get to set-up, sometimes not); it's rendered the phone unusable. I've wiped countless times (even my SD card) and have tried various ROMs, including the modified official Froyo ROMs from HTC. I've even tried using a different SD card - still the issue persists.
I just don't know what they hell is going on here. Can anyone shed any light on this? It's a major pain in the ass and is really starting to make me loathe this phone.
UPDATE:
The problem persisted, so I broke down and un-rooted my phone and did the official updates - the problem arose again in about 4 hours. I took it to my local repair center, they basically just wiped it and installed the updates and told me to come back if I had any issues - I used navigation to get home, and it started rebooting on my way home. So I'm currently waiting for a replacement from Sprint (goddamned things are backordered, they said 5 days or so), they really had no idea what was causing the issue at the repair center. So I'm guessing there's an actual hardware issue here that's directly conflicting with the software? It definitely seems to be happening to a decent number of people, just Google "EVO randomly rebooting" to see what I mean.
I feel your pain. Mine started doing the same thing about a week ago. I wiped, wiped and wiped, installed new ROM's, ran without the SD card, tried different recovery consoles, all to no avail.
My last resort was to try to RUU back to the Sprint 2.2 (non-rooted), but it didn't help. I have tried different 3G drivers, different 4G drivers, etc. I have run the phone with only wifi on, only 3g on, only 4g on and it doesn't matter.
I even connected it to my laptop and ran the "adb logcat" command from the shell to try to see a common error or log just before it would reboot. I caught four instances last night, but nothing in the logs to indicate a common problem.
I am thinking about taking it into a Sprint store tomorrow to see if they can do a wipe and clean install out of desperation.
Mine too it was a 0002 Novatek and i think it's mid-term defect with early versions...claim your insurance is all i can say. That's what i did and got a 0003 that works good so far...maybe the CPU is overheating and rebooting?? IDK i couldn't use mine either..its seems to work best on CM but still reboots...got rid of it....hardware problem....If they HAD to make 0003 then something was obviously wrong with hardware version 0002.....INSURANCE!!!!
awesomerobot said:
So I've had my EVO since launch and it's been properly rooted and running various ROMs for over a month. Suddenly I've been having incredibly frustrating random reboot issues. It seemed to all start when it randomly began rebooting during navigation (other GPS apps seemed ok). So it got stuck in a boot loop and I wiped everything and installed the latest nightly of CM6 (this was probably around 8/2). That seemed to fix it.
Until now. For the past few days the phone has been rebooting randomly. Once it reboots randomly once or twice it gets worse - the phone will reboot before I reach my home screen over and over again (sometimes I can get to set-up, sometimes not); it's rendered the phone unusable. I've wiped countless times (even my SD card) and have tried various ROMs, including the modified official Froyo ROMs from HTC. I've even tried using a different SD card - still the issue persists.
I just don't know what they hell is going on here. Can anyone shed any light on this? It's a major pain in the ass and is really starting to make me loathe this phone.
Click to expand...
Click to collapse
this has been happening to me as well, it just started though last night for me.
http://forum.xda-developers.com/showthread.php?t=753969
theres my thread see if there answers can help
maybe this might help
theunlockr.com/2010/06/14/how-to-unroot-the-htc-evo/
revert it back to 1.47 then re-root with simpleroot or unrevoked and start over? i just used it and rerooted my phone in hopes of fixing an error that wont let me flash any roms, it didnt fix the error. but maybe it will help with ur rebooting issue
My guess is the kernal your using is too undervolted for your phone, and when it kicks into high gear, for example when it fires up say bluetooth gps and data, it reboots because it didnt have enough juice at that given time.
everyone phone reacts to different kernals differently, try one with more voltage <worse battery life>
I am running this kernel. Isn't it the stock kernel?
2.6.32.15-g746f4f0
[email protected] #58
Like I said, I have reverted back to pure stock 2.2 (non-rooted). Maybe something remains from my rooting days. Are any of these not stock?
Android version:
2.2
Baseband version:
2.15.00.07.28
Kernel version:
2.6.32.15-g746f4f0
[email protected] #58
Build number:
3.26.651.6 CL218634 release-keys
Software number:
3.26.651.6
Browser version:
Webkit 3.1
PRI Version:
1.34_003
PRL Version:
60669
I took my phone to a Sprint store and showed them what it is doing. The manager at the store said that is the reason he hasn't upgraded his EVO to 2.2 yet. He agreed to order me a replacement, even though I don't carry insurance on my phone. I am happy to be gettting a new one, the problem is that it may take a few weeks since they are backordered everywhere.
Cool...so was the manager implying its caused by 2.2?
snandlal said:
Mine too it was a 0002 Novatek and i think it's mid-term defect with early versions...claim your insurance is all i can say. That's what i did and got a 0003 that works good so far...maybe the CPU is overheating and rebooting?? IDK i couldn't use mine either..its seems to work best on CM but still reboots...got rid of it....hardware problem....If they HAD to make 0003 then something was obviously wrong with hardware version 0002.....INSURANCE!!!!
Click to expand...
Click to collapse
Insurance?! Its under factory warranty. Wipe off all the rooted stuff and make them replace it for free.
I have been running froyo for a couple of weeks, and I haven't had this problem. I use navigation, pandora, and BT. Running DC 3.5
Sent from the bowels of my mind...
snandlal said:
Cool...so was the manager implying its caused by 2.2?
Click to expand...
Click to collapse
That was my angle going into the store...it started right after the 2.2 update.
It's probably the kernal...otherwise download setcpu from the forums and mess wit that. ...fixed my reboot issue
Sent from my PC36100 using XDA App
kris54241 said:
It's probably the kernal...otherwise download setcpu from the forums and mess wit that. ...fixed my reboot issue
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
it's definitely not the kernel.
I've been having the same reboot problems. I think its a hardware issue with froyo because the root cause of my restart issue is that the battery is running hot. Most evo's will power cycle when the battery hits ~100f, so anything data intensive causes it to overheat.
I took it into my local sprint store and demonstrated that it would power cycle from normal use and I'm now going to get the first evo in their door.
PS. I'm also on the 002 model.
I was running the stock 1.26 version and it was perfect. No flickering, very smooth, but the phone kept bugging me for the update, so I updated it. Update went smooth, but now I have that terrible screen flicker, it's by far not as smooth... so if you have no problems with 1.26, don't update. I'll revert to 1.26 and hope that it goes back to being as flawless as it was before.
Edit: Just noticed that wireless connections are much worse as well with this update. At the moment I can only use WiFi and even that doesn't work properly for some reason (i.e. can surf but can't get to beta.swype.com - but I can get there on my desktop using the same WLAN). All borked...
You are one of the only people who has said this about the 1.28 update. Also you can't revert unless you get a new phone with 1.26 as your HBOOT was updated when you installed this update.
Yes, I just noticed that . So until 3 come up with a better update, I'm stuck with this junk Should have stuck to my usual motto: Don't fix it if it ain't broke.
Updated mine on the day I got the phone not noticed any screen flicker at all and I have been looking for it. Dont use Wifi as the 3's 3G is plenty fast enough and I have all you can eat data so can't comment on that. Data connection is FAR more stable than on the ONE S which I swapped it for.
I don't know but this update has royally screwed my phone. Each time the alarm is supposed to go off, the phone reboots (no matter which alarm app I use). I also get reboots for random other apps.
For me it's just a real PITA and at the moment, I would consider the phone unreliable at best. I'll try flashing the 1.28 from Three again but I'm not holding my breath
Just wish I could go back to 1.26.
Edit: I just flashed Energy ROM and the phone still reboots when using Alarm Clock Extreme. It's just sooooooooo annoying!
Isn't there any way to go back to 1.26?
Edit2: After the phone just rebooted, it rebooted again when I was just looking at the notification screen.
Is it a problem with Three UK if the phone has been unlocked? I feel very much inclined to return the phone and get a replacement... phone is unsuable at the moment as a smartphone...
Edit 3: I can't even re-flash it... updater says "can't update this". Oh gosh, Three, please make it fast to the next update.
Figured I'd cross post this as it seems to be an issue for a few people. ( http://forum.xda-developers.com/showthread.php?t=1951699 )
I've noticed this issue since first getting my S3 in July. So I do know it happened with 4.0.4 and now with 4.1.1. I've never used the "Stay Awake" option in the dev options and it still remains off. I've had the issue with both "Smart Stay" on and off. I've tested it with all screen time out times, as well as going through the trouble of factory resetting the device and nothing changed. The only solution I've found is reboot the phone and it will work again for a day or so until I notice it again. Very annoying and would love to find a solution to this!
I just started having the same issue. I was using Black Jelly's JB ROM for like 2 weeks without the problem then I flashed the LK3 modem and it started happening. I did a full wipe and flashed the ROM from this thread - http://forum.xda-developers.com/showthread.php?t=2034844 last night and I'm still having the problem. My touch key lights stay on all the time too along with the screen not timing out.
My S3 has been stock from day one. I also got mine a few days after it was released, starting to wonder if its a hardware issue?
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
I've noticed it on a replacement S3 I got when it wasn't an issue with the prior one. The new one (as with the old) is stock, updated to JB when I got it. GFs phone does the same.
geiswiz said:
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
Click to expand...
Click to collapse
This is interesting. I've been noticing this issue ever since I updated to 4.1.1 some weeks back, but had not considered any connection with missed calls. Among the dozens of reports I see online (with not a single one resolved), I found another thread that mentions it happening after missing a call (or receiving an SMS).
I completely wiped my phone and flashed a stock 4.1.1 rom two days ago and noticed this happening again while sitting at my desk today. I did miss a call earlier, so I think there is something to that suspicion; I rebooted the phone and sure enough the screen and touch keys timeout as they should. I just received a text and that didn't trigger the issue, but I'll have to wait til I get another call to know for sure, or until I get home and have the time to test it.
Ok, yep, it definitely is somehow triggered by missing a call, but it seems to only happen some time later after the last reboot. I had rebooted my phone yesterday, missed a call not too long after, and the keys and screen would shut off normally. But I just missed a call right now and sure enough it's acting up again...
I am currently having some data connectivity issues with my E4GT. I have been running the Blu Kuban rom for some time now and have been a huge fan of it, but now my phone is acting really weird (no fault to the rom at all). First my GPS wouldn't lock as I thought this was kernel related I re installed the Blu Kuban rom with both of the other kernels and still couldn't get a GPS lock. Since I use GPS daily for work I went back to my classic Epic Venum rom and the GPS worked albeit poorly, it got me through the day. When on this rom whenever I used data my phone would drop down to zero percent battery and power off, this seems to occur only over 4g/3g and not over wifi. I tried flashing multiple modems from EG30 to FI27 on a multitude of roms (both GB and ICS) and using desktop Odin, but I cannot figure out what is causing my phone to crash (which now occurs consistently). I tried installing new roms (currently on AOKP build 37) which works great until the data is used and then it crashes again. I don't think this is cause from any specific rom, and I am now fearing it is a hardware issue. To summarize GPS now works, using data causes my phone to crash regardless of the rom used. Just thought I would ask the community, any help would be greatly appreciated. Thanks!
Update: I ended up restoring to stock to see if that would fix the problem and it didn't. So I took it to the Sprint store where they discovered I had a defective battery, and it just so happened that I bought the phone a year ago today so the new battery will be covered under warranty . I will update my status upon receiving the new battery, but I am feeling optimistic at this point.
These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.
Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.