This happened rarely on stock ROM but reliably reproduced when rang by my friend who on 3 network. I flashed last nightly & have the one upgrade so far. Did not seem to have this problem on last nightly. However, Lin OS did seem to be stuck on booting after upgrade so I power cycled. Seems I was not patient enough...
Seems another nightly landed hot on heels of last, this issue seems fixed.
Edit; still present.
Related
Hi, tried a search, no luck.
Tonight I did soft reset on the phone after it hung whilst I tried to make a call.
Now when it boots, I get the message:
No GSM
on the white T-Mobile screen, then two lines down, the WWE version number. Before, I think I had 3 lines of information.
When the phone boots, there is an exclaimation mark next to the Signal meter, and nothing works.
Any ideas apart from:
It's broken, return for repair?
AFAIK it has had no knocks today, and has had nothing done to it recently, no software updates etc. in the last month
Gareth
Try reading this topic, it might help:
http://forum.xda-developers.com/viewtopic.php?t=36730&highlight=
as far as I know the latest rom update fixes this bug (or whatever it is)
Update Problem?
I updated to 1.20.32 Tuesday morning, reset and the system loaded with the GSM
Played around for a while, left it working for almost 2 days.
Then installed the blackberry stuff. Instantly the system is toast again, and I can no longer access the GSM (No GSM printed again).
I am wondering whether there is a blackberry bug which crashed my radio?
I've had my magic (rogers 32a) for about 6 months, and a few days ago developed a major issue.
Everything was fine, I was running Cursorsense rom. I found battery life was short on that rom, so I flashed Marsdroid. This seemed better, and I used it fine for almost a week. Then Thursday (a week after I made any changes to it), my phone was off, so I turned it on. It just sat at the rogers screen forever, even an hour later it was still sitting there.
I could get into recovery fine, could mount it as usb storage from recovery fine.
I wiped it from recovery,and rebooted, but it had the same issue.
I was able to get it to boot twice, both times the SIM card was out. Not sure if that was coincidence or not, as several other times with the SIM card out it wouldn't boot. Even those two times it took much longer then normal. I did replace the SIM incase it was bad, but the problem remained.
So I eventually decided to try reflashing. I flashed cursorsense back onto it, and the phone seemed to be fine again after that. I decided to goto a newer rom after a half day though. So I loaded a 2.1 dump from the Eris. This also was working fine for over a day. then I rebooted it again today, and now it's doing the same sitting at rogers logo.
This is before I get any of the HTC logos, the Rogers logo comes on as soon as I power on.
Any thoughts? This is 6.35 radio and the newer spl. Any chance memory is getting corrupted that reflashing fixes temporarily.
No one?
It booted up again now, not sure why it's so intermittent.
Also noticed it appears my speaker in the ear isn't working? if I call someone, I don't hear it ringing from the earpiece, or hear the person speaking. if I hit speakerphone button, it works, as does bluetooth.
Guess I should probably just warranty it. If I flash the stock rogers update, will that erase any evidence of the roms I've had loaded on here? (clear out amon recovery and the like). The problem appears to be a hardware issue, so it's not like a rom bricked it or anything, so I don't think it's taking advantage of rogers.
Morning everyone,
During last weekend I went to Birmingham and was using TomTom on my Hima (6.5 swampy ROM). While going towards Birmingham the phone was fine however once I got to Birmingham, it suddenly restarted. I thought maybe it crashed so I waited for the ROM to come back up.
Once it came back, it was running very slow. I switched on TomTom again and yet again it restarted. I again waited for it to come back on but this time when it came back on, it restarted again. It restarted around 5-8 times.
I was very frustrated since all my contacts were on the phone and not on the SIM nor I knew the direction to get to my friend house. I plugged the phone into the Ciggerete lighter (to charge it), and it worked fine for a while. Once I came back home I uninstalled few programs off it so that it can have some free memory. Yet it restarted again.
I then hard reset the phone yet it still getting stuck and getting rebooted at random times. I then downgraded it to 1.72 Old Original ROM with 1.7 Radio. At the time it worked fine so I updated it back to 6.5 with 1.9 Radio and so far it is working ok-ish.
My question is, is it the ROM or the Battery which is causing this issue? I mean it has been running stable until I tried to use TomTom for directions. I have tried 2 other 6.5 ROMs, yet after importing my contacts the Hima was running very slow. So I went back to Swampy ROM.
Sorry for a long post and I'd say some points it sounds random but that is due to very early time here .
Has anyone else experienced the same issue with their hima?
Regards
Jay
i understand this might be a known issue (radio crash after froyo update). anybody know what to do?
rooted my phone awhile ago... upgraded to Froyo a couple days ago (leaked FROYO.DJ29) and things were moving along pretty well. today while the phone was sitting inactive, it decided to go into airplane mode.
the last thing it did was try to download a google maps update.
i'm completely unable to get out of airplane mode. if i unselect it, it says "turning on wireless connections..." but never finishes that. resetting doesn't help. taking the battery out doesn't help.
in fact, the date on the phone reset to December 31, 2004.... any help would be super appreciated!!
try flashing the di18 modem file. i fixed a couple of my buddys friends epics like this.
UPDATE: i turned off my phone for an hour and when i turned it back on it was working fine.
add it to the bug list i guess if others report similar findings
This happens a few times a day on my epic....I went back to 2.1....ill wait for the official froyo release
Happened to me once over a week ago was a bad flash wiped everything again and reinstalled been running this verson since with absolutly no issues actually I find it better then 2.1 as I don't hang up on people anymore when talking on the phone.
Phone is rooted and unlocked with multirom since July and has been working great. 3 roms installed; liquidsmooth 5.1.1, chroma 5.1.1, and Ubuntu.
Yesterday, calling started to be intermittent. Sometimes switching airplane mode on/off fixed it, sometimes it didn't. Today I cannot get calls to work at all. Phone shows dialing but then hangs up before any ringing. Incoming calls don't work either, it goes straight to voicemail. I thought it may have been lollipop but the problem occurs in Ubuntu as well. Funny thing is that the phone finds the network carrier and has decent signal.
I havent changed anything on the phone recently, only thing is that I dropped it 3 days ago. Thankfully no cosmetic damage, but am starting to think internal damage.
I've tried soft reboot, cold booting, pulling the sim...no luck
Should also mention I'm on virgin mobile canada...
Any ideas?
mouf said:
Phone is rooted and unlocked with multirom since July and has been working great. 3 roms installed; liquidsmooth 5.1.1, chroma 5.1.1, and Ubuntu.
Yesterday, calling started to be intermittent. Sometimes switching airplane mode on/off fixed it, sometimes it didn't. Today I cannot get calls to work at all. Phone shows dialing but then hangs up before any ringing. Incoming calls don't work either, it goes straight to voicemail. I thought it may have been lollipop but the problem occurs in Ubuntu as well. Funny thing is that the phone finds the network carrier and has decent signal.
I havent changed anything on the phone recently, only thing is that I dropped it 3 days ago. Thankfully no cosmetic damage, but am starting to think internal damage.
I've tried soft reboot, cold booting, pulling the sim...no luck
Should also mention I'm on virgin mobile canada...
Any ideas?
Click to expand...
Click to collapse
You could try flashing the radio image via fastboot.
I tried flashing the radio via recovery... No luck either