Hola,
A few weeks back, out of nowhere, my Desire started roaming back and forth which sucks cause internet gets disconnected every 2-5min or so.
This was not during a ROM change or anything else, it just kind of happened... and it is still happening.
I had never actually flashed different radios before, it always worked the way it was with any rom I used... today I flashed a couple different radios... issue remains.
Btw, no issue with wifi or phonecalls, not sure about gps signal.
I don't see how the APN would be wrong as I didn't change it for over a year and had no issues before.
Anyone got a clue what could be wrong?
(S-OFF, CWM Touch Recovery, cm7r2 hboot) if that matters...
Obviously I'd be really happy if anyone could help me solve this!
Thanks!
Related
I recently rooted my Evo and put CM7 nightly 12 on it. All was well, I even installed the Savaged Zen kernel. Even better. Just yesterday I updated to CM7 RC2 to give it a shot. Today I went to work and had to drive to a remote area where I don't get service, so I put my Evo in airplane mode to save battery life. (this was after having it overheat while charging, could be a hardware issue) At the end of the day I turned the 3G radio back on and nothing... It connects and disconnects to the tower. It will not send data and it will not place phone calls on the 3G connection (WiFi works). I did a restore back to nightly 12 to see if maybe it was a problem with the OS. Nothing. A few hours ago it began functioning again, but after checking it a few minutes ago I have discovered it is back to no connection. (the signal bars bounce between nothing and full, but never shows the X for no signal) Has anyone else had an issue like this? Should I restore back to sense and unroot to take advantage of my warranty? If this has already been posted before please direct me to the right thread.
I'm having the same problem. I installed Cyanogen RC 2 and had no problem since it came out. I went on vacation to a beach, and during my trip I switched it on to airplane mode since I was in a remote location. After turning it back on, I noticed I can't get the Data Connection to work. The 3g bar doesn't even show up, and after messing with the settings trying to fix the problem I managed to do nothing. I tried using a backup I made from a week past, and encountered the same problem. Then I flashed the newest nightly and still no Data whatsoever. Wifi works fine, and 4g is acting weird but I got it to work a few times. Does this have something to do with sprint?
I think it is the same as the 4G 3G hang. I typically get it while tethering and the phone is normaly quite warm.
So I managed to fix the problem. I ended up flashing Koni's Elite Rom
http://forum.xda-developers.com/showthread.php?t=941055
I got an error that said "Error 67 registration failure"
I updated my profile and it was automatically fixed. I'm not aware you can do this on cyanogen stock rom, but I think you can dial a number that will do this for you.
After getting the 3g to work again, I flashed back to the stock cyanogen, and it is still working. So for now im good to go.
I do think is sprint and not the rom because I did a restore to warm z and was still having the same problems. Also my brother's evo was doing the same thing and he doesnt have cm7 on it.
I figured it was something to do with the profile... I restored all the way back to sense and attempted to update profile, but it doesn't seem to be doing anything. I will try that ROM and see if it does anything. Why can't they just make this easy and allow updating of vital software that allows the radios to work on WiFi or from SDcard? This is dumb.
I tried that ROM and nothing works. Not really sure what to do. I might have to restore to Sense and unroot to take it back... I really want to avoid that if at all possible.
Unrooted my phone and getting a free replacement from Sprint. Still unsure of the problem, seems to work randomly.
jmoh said:
So I managed to fix the problem. I ended up flashing Koni's Elite Rom
http://forum.xda-developers.com/showthread.php?t=941055
I got an error that said "Error 67 registration failure"
I updated my profile and it was automatically fixed. I'm not aware you can do this on cyanogen stock rom, but I think you can dial a number that will do this for you.
After getting the 3g to work again, I flashed back to the stock cyanogen, and it is still working. So for now im good to go.
Click to expand...
Click to collapse
I also have the same problem. No 3g data, gps, and 4g is acting weird.
I also had the same registration error number 67. My question is, how do you update your profile?
I've been seeing this problem for a few weeks now, with several different ROMs, including the original rooted stock ROM now. In nearly all of my recent calls, I get disconnected one or more times with the message "Call disconnected" and a "Dismiss" button. I'm thinking that this is because of my EVO and not the other side, since usually if they accidentally hang up or something the call just ends without a message box. As far as I can tell, I have good reception (at least according to the bars), and this is happening at home, where I've not had the problem before.
Does anyone know what could be causing this? My wife's EVO is not rooted, and she does not seem to be having this problem. But then again, I've not had the problem until fairly recently either. I've tried updating my profile and PRL with each new ROM, but it doesn't seem to have made a difference. Anyone have any suggestions as to how to stop this from happening?
Go into the settings menu andbupdate both your PRL and your profile. That *should* help with reception related issues.
posting & replying via the XDA Premium app.
Unfortunately, I've tried both of those things. I just did some testing today, and it seems that my phone is unable to stay connected during a phone call for more than five minutes before disconnecting, even if I don't touch the phone and just leave it sitting on a table.
Any other ideas? As far as I know, I haven't ever flashed my radio away from its default (2.15.00.11.19), and I'm currently using the leaked stock gingerbread ROM (build number 4.12.651.1 CL41771 release-keys and kernel 2.6.35.10-gaa602b7 [email protected] #1).
Maybe it's time to unroot and contact Sprint?
You can try downgrading from 2.15.00.11.19 to 2.15.00.09.01. You can download it from http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Afterwards, go into recovery, wipe cache & dalvik cache then flash the zip. You will be taken to the radio update screen and appear to hang. don't worry or get impatient. After it is finished, you will reboot into recovery and see the words "clearing cache" at the top of the screen. Simply select reboot and then you will boot to your homescreen. The initial boot will take a tad longer since it will be rebuilding the dalvik.
Hmm... I'm hesitant to downgrade my radio because my wife has an EVO with the same radio version number and hers doesn't have this problem. Granted, she is not rooted...
I understand. I've downgraded and upgraded everything several times for testing purposes and troubleshooting purposes and have never had a problem. The only hing about flashing radios is patience and not to pull the battery. Anyway, you can always call Sprint and see if they can troubleshoot it for you from their end.
posting & replying via the XDA Premium app.
I would contact sprint @ 877-809-6696 (advanced tech supp). Ask them to push a full reprovision to your device. See if that helps any. I was having issues when when on the airave, I was unable to receive incoming calls. This corrected it. I did try all the other steps listed above without any success.
This is interesting. I unrooted to test things out before calling Sprint, and the problem went away. I was able to stay connected for an hour (where before I couldn't last longer than 10-15 minutes). Yay, fixed, right? So, I rooted again and didn't install any ROMs or anything, just rooted, and the problem came back.
So, I have a solution, but I don't like it very much because it means I need to stay unrooted. Anyone have any idea why simply rooting the phone with Unrevoked 3 (and doing nothing else) could cause calls to disconnect? I'd love to be able to root again, but I can't deal with a phone that randomly disconnects all the time.
I am interested in this as well as I am rooted using unrevoked and get disconnected as well. I do find that it mainly happens though talking to people who have service on AT&T.. Quite wierd. All I hear is a beep then disconnected. This happens when I first place a call and it rings once or twice then beep, disconnected...
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
KingFunderberk said:
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
Click to expand...
Click to collapse
So whats the final call on this ..?
Is it Rooting , Is it network .. i am too getting psyche with this .
I'm pretty sure it is not rooting. But I don't yet know for certain what it is. Sprint thought there might be something wrong with the antenna on my phone, but they had already replaced the phone, so I think that is unlikely. They gave me a femtocell range extender to use in my house. Basically, I plug it into my broadband connection, and it is like having a mini cell tower in my house, giving me a very strong connection. Sure enough, when connected to that, I haven't had any calls drop. However, my phone still sometimes doesn't connect to the femtocell and instead connects to some other tower for some reason. My wife's phone doesn't do this, so I still think there is something wrong with my phone. I may contact Sprint again about this. ...sigh...
What is your area some area evo don't work properly like on rahim yar khan in this time connection don't work properly some signal drop and some time up i sure after few day signal work properly then problems will be solve.
My phone EVO is doing this now as well. Has anyone heard/read a solution?
greg_99 said:
My phone EVO is doing this now as well. Has anyone heard/read a solution?
Click to expand...
Click to collapse
I am having the same issue, out of the blue. No problems up until a few days ago. I'm wondering if it is maybe an issue with a certain version of the Evo. I have a version 002. Thoughts?
Greg_99 any progress on what might be causing this issue?
Hi,
Two days back my htc desire suddenly lost connection to the mobile network. I now get a small cross on top of the signal bars and "no service" written on the notification bar. Sometimes this changes to "sos".
The wifi is working fine. t
The only problem is voice and data over the mobile network.
I tried a lot of things:
reboot
flashed a new radio
complete wipe/ factory reset
flashed a new rom
But to no avail.
A strange thing did occur though, at a mall, my phone suddenly started working for a few minutes and then went back to the same state as before. This same thing happened last night too.
I am unable to understand this and request all of you to help.
current status:
Phone: htc desire amoled
s-on
bb: 32.56.00.32U_5.17.05.23
miui 17.15
Ring your provider.
S.O.S. Problem
Originally Posted by mythmystic
Hi,
I got a problem since upgrading to 1.7.17 ... I thought with new updates it's going to settle the problem.
I always get S.O.S, the emergency call thingy!
How to solve this? I tried flashing to CM7 and its fine.
So I assume the problem would be the ROM
Any solution to this? Patches or something?
I would love to continue on using MIUI
Thanks all
Regarding the above problem.. had the same thing... what i did is this..
on dial pad use *#*#4636#*#*
then goto phone information (first one)
scroll down you'll see "set preferred network type"
mine was selected "WCDMA" I changed that to "GSM Only"
Since then no problem of S.O.S has come to me
I am sending it here because I am unable to post in the forum... something to do with minimum of 10 Post.. Hope this helps
Guys thanks for your replies.
I have already done the *#*#4636#*#* bit and it hasn't helped.
Regarding the rom, I was originally on cyanogenmod 7 when this problem started. I re-flashed CM7. Didn't help. Then i flashed miui. the problem remains.
Although I would like to add that over the past two days, at two different locations, I have been able to make one call and recieve one. How this happens, I don't know.
Still trying to figure it out but I just read elsewhere on this forum an exactly similar problem being faced by a few people during the last few days.... so keeping my fingers crossed.
Ah! and one more thing, I have tried sim cards of almost all operators and none work in this phone.
Same problem here aswell,
me too tried every thing,
but non of them helpfull..
Still searching for help
This may seem like a dumb question, but the people experiencing this problem, are you in the same country/region?
Sent from my CM7.1 Desire using XDA Premium App
A little update in my situation:
I visited another city for an hour yesterday and the phone latched onto vodafone in seconds and worked like a charm but as soon as i got back to base, it was back to its dead state.
This is a really confusing situation because, one moment it seems like its a hardware problem (since none of the operator's sims tend to work in it while in delhi) and then sometimes it seems to be a network problem (as it seems to work just fine in some areas)
Guys, please.... please help. This is so frustrating.
guys i'm still waiting for a reply.... doesn't anyone here have a solution to my problem?
Install cm7, then full wipe and then install freshly your new rom.
I did that way and after that was network connection back.
Sry my bad english!
Sent My Desire.
i understand your frustration, im here just to tell u, i have a different situation which no one has any solution, ive googled and spent 1 whole F()[email protected]((U)#($I)(#U$)(U#)($U day but no one reported the same issue as me..
sigh
taaviu said:
Install cm7, then full wipe and then install freshly your new rom.
I did that way and after that was network connection back.
Sry my bad english!
Sent My Desire.
Click to expand...
Click to collapse
Hey this worked but only partially. Now the phone does latch on to network at most places except two: my workplace and home.
And in some places it shows full signal strength but calling is not possible.
Hi, I know I know there maybe threads already about the same issue but couldn't find the right answer.
the thing is. last night I accidentally dropped my T-mo G2. hence all was working before and after(just as it seems to be) but when I tried turning on wifi it says error. tried to reboot, reflashed with full wipes. tried another sense ROM and reinstalled the radio. still the same thing. is this a hardware issue? I still have mobile data working. and I have a DZ hboot. before this actually happened I used wifi ages ago. so I really don't know what caused the problem. any tips?suggestion? or clues anyone out there can point out? thanks in advanced
+1 to anyone who can try
gonemad02 said:
Hi, I know I know there maybe threads already about the same issue but couldn't find the right answer.
the thing is. last night I accidentally dropped my T-mo G2. hence all was working before and after(just as it seems to be) but when I tried turning on wifi it says error. tried to reboot, reflashed with full wipes. tried another sense ROM and reinstalled the radio. still the same thing. is this a hardware issue? I still have mobile data working. and I have a DZ hboot. before this actually happened I used wifi ages ago. so I really don't know what caused the problem. any tips?suggestion? or clues anyone out there can point out? thanks in advanced
+1 to anyone who can try
Click to expand...
Click to collapse
From what I understand, the radio is just dealing with cellular data.
You most likely damaged your Wi-Fi antenna; have you tried running alogcat while turning on/off Wi-Fi to see what's happening?
Sent from my HTC Vision using XDA App
let's see. I'll post a logcat in a while. and yeah I think I damaged the wifi antenna when I dropped it
Okay, so I decided to spend my weekend solving my girlfriends HTC Desire problems. It was basically 2 things that were bothering her - lack of space to install apps and fluctuating carrier signal.
The first one was easy - I was able to root her T-Mobile (Germany) branded Desire with unrevoked and did the whole ext partitioning thing, etc. etc.
Our second problem however persisted - gsm signal from her phone will randomly completely vanish causing her to miss calls, sms, etc... unfortunately - this happens quite often. The weird thing is that she can initiate the call herself and then the signal will return for a few minutes, but vanish again afterward.
Its not her SIM or the carrier - I tried it in my phone and it works fine and my SIM in her phone also experiences the same problems.
I tried installing different latest ROMs like GingerVillan, SuperNova, Sandvold's ICS BETA, etc. It doesn't help whether its 2.2, 2.3 or 4.0.3. Yes, with full wipes in between.
Her Radio was 5.11.05.27 and I tried updating it to 5.17.05.23 - but no change. Still the same problem.
I was also playing with the phone menus accessed by *#*#4636#*#* trying to set my network to GSM only. This also didn't give a permanent solution.
Any ideas what else I could try? Different older Radios? Would messing with RILs help?
Should I try flashing the complete RUU package? Which one? I'm still S-ON... I'm not really sure what else I could try - kernel changes with ROMs anyway. Would changing the Hboot make any difference at all in that department - its probably the only thing that stays the same (0.93.0001) but I'm not sure if it has anything to do with cell signal?
Pls help - any ideas? I find it difficult to believe it could be a hardware problem - because again if she initiates the call then the signal comes back. But if somebody calls her she might be unreachable and it goes straight to voicemail. Sometimes.