Perhaps someone here can help...
I am running tommytomatoe's Classic ROM v0.1.0 w/ the Supreme Cream Sandwich theme.
Yesterday evening, I wanted to turn on 4G to do a largish download. I used the quick settings and tapped the 4G box. The phone attempted to turn on 4G but just sat there saying, "Turning on 4G," without succeeding. (I have used 4G in this location before.) I went to the main settings window, and looked at 4G. Same thing: "Turning on 4G," endlessly -- and no way to get the phone to stop doing this. I hot-booted. I did a full reboot. Still "Turning on 4G" -- and a noticeable drain on the battery. In the end, the only way I found out of this "loop," was to restore a Nandroid.
I noticed one strange thing while trying to make one of the settings interfaces turn off 4G. A long-press on the 4G box in quick settings brought up the dialog, pictured here, instead of the settings window. Something tells me this is at the root of the phone not succeeding with turning on the 4G. Tapping the upper one got me to the main 4g settings window. Tapping the lower one got me a dialog that said something like "No 4G service available. Contact your carrier." Where is this weird duplication, and how do I get rid of it?
Thanks ------>
Did you use the RSA keychecker app to make sure your RSA keys are intact? If you lose those 4g is borked.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
moseso said:
Perhaps someone here can help...
I am running tommytomatoe's Classic ROM v0.1.0 w/ the Supreme Cream Sandwich theme.
Yesterday evening, I wanted to turn on 4G to do a largish download. I used the quick settings and tapped the 4G box. The phone attempted to turn on 4G but just sat there saying, "Turning on 4G," without succeeding. (I have used 4G in this location before.) I went to the main settings window, and looked at 4G. Same thing: "Turning on 4G," endlessly -- and no way to get the phone to stop doing this. I hot-booted. I did a full reboot. Still "Turning on 4G" -- and a noticeable drain on the battery. In the end, the only way I found out of this "loop," was to restore a Nandroid.
I noticed one strange thing while trying to make one of the settings interfaces turn off 4G. A long-press on the 4G box in quick settings brought up the dialog, pictured here, instead of the settings window. Something tells me this is at the root of the phone not succeeding with turning on the 4G. Tapping the upper one got me to the main 4g settings window. Tapping the lower one got me a dialog that said something like "No 4G service available. Contact your carrier." Where is this weird duplication, and how do I get rid of it?
Thanks ------>
Click to expand...
Click to collapse
I know it might sound like alot of work mate,but i back up and wipe my complete sd card at least once a month and re-partition it with ext 4 and i will admit i dont have that sort of problem with my tele ever.Im always using 4G.Things and settings get cluttered after awhile and cache and delvik just dont do the trick anymore,so you need to do a full wipe,once in awhile mate.
6ANONAMUS9 said:
I know it might sound like alot of work mate,but i back up and wipe my complete sd card at least once a month and re-partition it with ext 4 and i will admit i dont have that sort of problem with my tele ever.Im always using 4G.Things and settings get cluttered after awhile and cache and delvik just dont do the trick anymore,so you need to do a full wipe,once in awhile mate.
Click to expand...
Click to collapse
You're right... That sounds like a lot of work -- but I'm backing up and preparing to do that now -- and reflash the ROM if need be.
I was hoping someone would be able to show me where the scalpel could be applied to excise this wiggliness. Since that ain't happening, I'm sure the sledge hammer approach will get it. Thanks!
Related
I was wondering if anyone else has this issue. I think most people know by now the issue we all ran into with 4G after we flashed roms with the new OTA update. The 4G would just be stuck at "scanning...." and never connect.
Anyways, I did manage to fix the 4G issue using bigbiff's steps here. So now the 4G connects with no issues but there's one problem: when I leave 4G area or go indoors and come back into 4G area it won't reconnect by itself. I have to either turn on and off 4G or hit the "Scan" button.
If anyone can give me any insight or ideas as to what's going on that would be very awesome.
I have the same problem, and I have seen at least one other person mention this problem (it's kind of hard to search the forum for this problem, since all you get are the folks having problems connecting to 4G).
This started after the OTA update. If the 4G signal fades out, the 4G status remains in "scanning" even in known 4G areas. I made one 4G change to try and fix this - I changed the wimax_idle_sleep time from 10 to 300 as was recommended in the 4G problem posts.
I am wondering if anyone knows what the other 4G settings do and if any of them would fix the problem. So far the only way I know to reconnect to 4G is to turn the radio off and on.
I posted this in another forum, the more frequented one. I thought it was more applicable there since this might be an issue concerning rooting, custom ROMs, home ROM flashing, or all the above. Until I see a wave of non-rooted users complaining about this, I think Sprint has found a gotcha for rooters and flashers. Input from some ROM developers would be nice if they happen to visit this forum.
I can enter a 4g area, turn on 4g, and connect. When I leave a 4g area, turn off 4g, then turn 4g back on before re-entering 4g area and enter a 4g area, it is stuck scanning. It never attaches to the 4g network in the area I entered. If I turn 4g off and on while in 4g area, it will connect.
Are unrooted stock users having these problems? It is a real let down and PITA. Is 4g working perfectly in all scenarios for any rooted user?
Click to expand...
Click to collapse
I also think it's related to one of the images we have to flash to get root, as the behavior is definitely different than stock. I noticed this after I first rooted / nand unlocked my phone, but before I applied the new radio & wimax. On my phone, however, 4G does eventually come back up. It might take 5 minutes or more, but it does eventually reconnect.
I'm not sure that it's really a bug though. I actually prefer this behavior because it results in fewer dropped connections when switching between 3G and 4G. For streaming apps (Rhapsody, Pandora, Youtube, etc) the frequent switching forces you to have to start the stream over. I think it might have been an attempt to increase the stability of the data connection at the expense of having a 4G connection less of the time. Could be a hold over from one of the older engineering builds we had to flash during the rooting process? It's strange that the behavior persists after flashing a new radio/wimax, but maybe it's actually controlled elsewhere.
Add me to the list. This is from my post about 20 hours ago which hasn't received any bites:
I have seen various issues reported:
1) 4g won't turn on. PERIOD.
2) 4g turns on but only scans - never connects.
3) 3g/4g alternate so there is never a stable connection.
4) 4g turns on and connects but after a while disconnects and won't reconnect until it is toggled on/off with the widget or check box in settings.
I used to have #3 until I did whitslack's "start over" method and now I have #4. I've changed my wimax idle sleep time to 300 in ##data# and verified a good MAC so other than the 2 evo last resort method I think I've tried everything other than the above.
So, does anyone know if renaming/moving macaddress.tree.xml is for my issue #4? Or does anyone know a specific fix for #4?
If it matters I rooted with toast 1/2 and am still on the rooted stock ROM from whitslack's "start over" method.
Click to expand...
Click to collapse
Some Observations:
I've noticed the following differences since the OTA (with Root-from the "How to Start over with 1.47.651.1" thread):
1. The 4G reconnection problem.
2. Bluetooth no longer auto connects when my headset is in range.
3. I have been getting "Error 67 Data Connection Lost" errors. This error blocks me from 3G data connectivity for a few minutes. During this time, "Mobile Networks" shows "Turning On" in the settings.
I suspect it is one of the following:
a. There is still a radio problem with the rooted OTA
b. the PRI that has not been updated since the root crack matters with this release.
c. Sprint/HTC introduced some new bugs.
d. Some hardware settings need to be tweaked (like the timeout that folks are changing from 10 to 300).
So we need to figure out who is having this problem, and under what circumstances.
I did however note something very interesting. I have repeated this 4 times today. If the 4G disconnects and stays in scanning, if you then place a call it will immediately reconnect. This leads me to believe that it is indeed a setting, and a voice call triggers it (if you recall in May, Sprint was saying that they hope to have Simultaneous Voice and 4G - so there is probably some code to trigger 4G at this point).
What do you folks think.
sw99 said:
Some Observations:
I've noticed the following differences since the OTA (with Root-from the "How to Start over with 1.47.651.1" thread):
1. The 4G reconnection problem.
2. Bluetooth no longer auto connects when my headset is in range.
3. I have been getting "Error 67 Data Connection Lost" errors. This error blocks me from 3G data connectivity for a few minutes. During this time, "Mobile Networks" shows "Turning On" in the settings.
I suspect it is one of the following:
a. There is still a radio problem with the rooted OTA
b. the PRI that has not been updated since the root crack matters with this release.
c. Sprint/HTC introduced some new bugs.
d. Some hardware settings need to be tweaked (like the timeout that folks are changing from 10 to 300).
Click to expand...
Click to collapse
I would take C out because I have not read complaints by non-rooted users.
The latest PRI is 1.40_003. Right?
Who can bring this over? ROM developers say those features are not part of what they do. If not them, then who?
What do you folks think.
Click to expand...
Click to collapse
I think being rooted currently sucks. One of EVO's greatest strengths, connectivity, has been crippled.
sw99, did you try the move the xml file with your mac address solution? If so, I guess it didn't make any difference.
sw99 said:
Some Observations:
I've noticed the following differences since the OTA (with Root-from the "How to Start over with 1.47.651.1" thread):
1. The 4G reconnection problem.
2. Bluetooth no longer auto connects when my headset is in range.
3. I have been getting "Error 67 Data Connection Lost" errors. This error blocks me from 3G data connectivity for a few minutes. During this time, "Mobile Networks" shows "Turning On" in the settings.
I suspect it is one of the following:
a. There is still a radio problem with the rooted OTA
b. the PRI that has not been updated since the root crack matters with this release.
c. Sprint/HTC introduced some new bugs.
d. Some hardware settings need to be tweaked (like the timeout that folks are changing from 10 to 300).
So we need to figure out who is having this problem, and under what circumstances.
I did however note something very interesting. I have repeated this 4 times today. If the 4G disconnects and stays in scanning, if you then place a call it will immediately reconnect. This leads me to believe that it is indeed a setting, and a voice call triggers it (if you recall in May, Sprint was saying that they hope to have Simultaneous Voice and 4G - so there is probably some code to trigger 4G at this point).
What do you folks think.
Click to expand...
Click to collapse
I will try making a call tomorrow when this happens and report back.
I had the same problem pre-root.
I wont be able to help anybody too much with technical stuff 'cause I'm basically a non-technical guy, but I've had the same problem with wimax dropping & not reconnecting ever since the OTA update (1.47....). I went to a Sprint store & the guy just went cross eyed, so it may not be too common.
In my case the connection will SOMETIMES come back on its own with a really strong signal, but rarely.
I just rooted tonight so I have no idea if it's worse or not, but I'll find out tomorrow, eh?
I've also had difficulty with Bluetooth automatically connecting, but I have a new stereo so I don't know where the issue lies.
Burt Reynolds said:
I wont be able to help anybody too much with technical stuff 'cause I'm basically a non-technical guy, but I've had the same problem with wimax dropping & not reconnecting ever since the OTA update (1.47....). I went to a Sprint store & the guy just went cross eyed, so it may not be too common.
In my case the connection will SOMETIMES come back on its own with a really strong signal, but rarely.
I just rooted tonight so I have no idea if it's worse or not, but I'll find out tomorrow, eh?
I've also had difficulty with Bluetooth automatically connecting, but I have a new stereo so I don't know where the issue lies.
Click to expand...
Click to collapse
Interesting. So this may have nothing to do with rooting.
kamiller42 said:
sw99, did you try the move the xml file with your mac address solution? If so, I guess it didn't make any difference.
Click to expand...
Click to collapse
Nope. Didn't touch the xml file, as my 4G was connecting, and the fix was for 4G just scanning.
I still think we can tweak the WIMAX settings and make it come back faster.
sw99 said:
Nope. Didn't touch the xml file, as my 4G was connecting, and the fix was for 4G just scanning.
I still think we can tweak the WIMAX settings and make it come back faster.
Click to expand...
Click to collapse
This is basically the only thing I haven't tried.
I tried making a call to reconnect to 4g three times this morning. IT WORKED ALL THREE TIMES! Odd....
sdc177 said:
This is basically the only thing I haven't tried.
I tried the making a call to reconnect to 4g three times this morning. IT WORKED ALL THREE TIMES! Odd....
Click to expand...
Click to collapse
Well at least its faster than toggling the 4G radio - just find a friend with a mobile phone so you don't waste any minutes.
sw99 said:
Well at least its faster than toggling the 4G radio - just find a friend with a mobile phone so you don't waste any minutes.
Click to expand...
Click to collapse
Just dial your own number which takes you to voice mail and shouldn't waste minutes. I'll probably put a direct dial shortcut on my home screen until a solution comes along. Not that I'm worried about wasting my regular minutes....I used 29 of 450 on my last bill!
I can now confirm that moving/deleting the xml file does nothing for our problem. At least not on my EVO.
So, I've been looking at the WIMAX settings (using ##DATA# and my MSL).
There are some settings that look like they could be effecting this problem. Be forewarned, however, that some of the values preset are not considered "valid" when you make a change (leading me to add credence to my theory that HTC/Sprint goofed), so I'm hoping a nandroid backup will recover them. Open each parameter and deleting the values, gives you a popup of the valid values and units.
Here is what I tried so far:
wimax_idle_sleep(s) changed from 10 to 300 seconds - effect: little to none.
wimax_scan_attempt_timeout(s) changed from 1 to 20 seconds - effect: little to none. (note only 5-300 are valid values after this change).
Other parameters that look interesting and their default values:
Wimax_scan_retry(s): 300 Seconds
Wimax_entry_delays(s): 300 seconds
wimax_exit_delay(s): 2 seconds
idle_mode_timer: 60 seconds
Standby Time: 10 Minutes
handoff Threshold: 6
Anyone willing to mess with these (at the risk of losing Wimax, of course)?
That is one place I'm not going to mess around. I saw a stern warning about that recently on the dev forum.
sdc177 said:
Interesting. So this may have nothing to do with rooting.
Click to expand...
Click to collapse
I still have my doubts about that. I put a link in the General forum to this thread, and we have one response. I read around the non-tech sites with 4G forums like SprintUsers, and I don't see these complaints.
I would like to hear from a tech oriented non-rooted user.
sdc177 said:
That is one place I'm not going to mess around. I saw a stern warning about that recently on the dev forum.
Click to expand...
Click to collapse
I'm hoping someone who knows what the settings mean can shed some light. I have not had any luck googling any of these fields.
kamiller42 said:
I still have my doubts about that. I put a link in the General forum to this thread, and we have one response. I read around the non-tech sites with 4G forums like SprintUsers, and I don't see these complaints.
I would like to hear from a tech oriented non-rooted user.
Click to expand...
Click to collapse
I did see a couple of non-root complaints, but I can't find them now (not on your standard sites).
So I wanted to try out different kernels yesterday. I'm rooted using the Stock ROM.
My phone was already running netanarchy's 4.1.9.1 with no problems, but I wanted to try out King's kernel BFS #8 as well as #6. I did a cache and dalvik wipe prior to each flash. In the end, I deemed that I personally like netanarchy's kernels more, so I switched back to 4.1.9.1.
However, now my 4G keeps turning on and off. This is causing my phone to significantly lag in intervals correlating with the on and off of the 4G toggle. Is it possible that flashing different kernels somehow borked my wimax radio?
Any help is much appreciated.
Is it anything like I described here:
http://forum.xda-developers.com/showthread.php?p=8052344
I'm having this issue and I never even rooted my phone. Note my latest reply that I did a hard reset on one of the evo's and now the 4g radio hangs on "turning on..." when I try to turn it on. Still seeing that now. Considering doing the unrevoked 3.2 to root it and try to fix it since sprint is clueless on the issue.
Yea, it is similar to your issue. I found your thread after I posted mine. I tried updating to the latest Wimax update found on XDA and that helped somewhat.
My 4G stays on, scans, and says connecting to Sprint network. However, it never successfully connects. I now believe I have the dreaded MAC address problem and am now trying to fix it.
I can't even see my 4G MAC address because I can't get the 4G radio to turn on. How else can I check whether my keys are screwed up (without being rooted)?
try dialing ##3282# and select view mode. Go to WiMax and look under NIA. That should have the MAC address.
If it does not match what is listed on your box, then your MAC addresses do not match.
hperry said:
I can't even see my 4G MAC address because I can't get the 4G radio to turn on. How else can I check whether my keys are screwed up (without being rooted)?
Click to expand...
Click to collapse
You gotta be rooted to do that. As for your keys getting hammered, the key issue arises on rooted phones after a bad flash, or corrupted radio file. More than likely your keys are fine. Let me ask you this, have you previously have 4G working, and it just stopped working? Or you now just tried to use it, and it's not working?
kf2mq said:
You gotta be rooted to do that. As for your keys getting hammered, the key issue arises on rooted phones after a bad flash, or corrupted radio file. More than likely your keys are fine. Let me ask you this, have you previously have 4G working, and it just stopped working? Or you now just tried to use it, and it's not working?
Click to expand...
Click to collapse
Yes, it used to work. I picked up signal around the boston area a month or two ago (before boston officially had 4g). I can't remember whether I used 4g successfully after the 2.2 upgrade. I was part of the group that did the .3 leaked 2.2 update and then took the .3 to .6 update OTA. I have never rooted this phone.
nvius said:
try dialing ##3282# and select view mode. Go to WiMax and look under NIA. That should have the MAC address.
If it does not match what is listed on your box, then your MAC addresses do not match.
Click to expand...
Click to collapse
There is no WiMax option when I do this. I think the WiMax radio needs to be switched on to see this. But I can't get the radio to turn on.
I've been using alogcat to try to debug the issue. I see this error come up about 90 seconds after trying to enable 4G (this is the same time the "turning on..." changes to "Unable to start 4g"):
E/WimaxStateTracker( 104): Failed to load Wimax driver -=>wl.release
I haven't been able to find any information about what this might mean.
same problem here; ever since running unrevoked 3 the other day, my evo 4g keeps turning 4G on and off by itself, and, wont let me stop it from doing that..
its killing my battery with its constant searching, and I cant find any sort of "tweak" that will allow me to just shut it off or leave it on; the widgets dont do it, so I cant figure out how to stop it..
was working fine before this..
On stock 2.2 froyo, stock kernel...
any ideas?
thanks!
hperry said:
Yes, it used to work. I picked up signal around the boston area a month or two ago (before boston officially had 4g). I can't remember whether I used 4g successfully after the 2.2 upgrade. I was part of the group that did the .3 leaked 2.2 update and then took the .3 to .6 update OTA. I have never rooted this phone.
Click to expand...
Click to collapse
Ok you may have hammered your 4G then. I've heard of a couple of people who took the leaked update, and fouled up their 4G. I would suggest you backup your stuff then run the latest RUU to see if that clears things up with the wimax driver not loading. If not take the phone to Sprint.
wase4711 said:
same problem here; ever since running unrevoked 3 the other day, my evo 4g keeps turning 4G on and off by itself, and, wont let me stop it from doing that..
its killing my battery with its constant searching, and I cant find any sort of "tweak" that will allow me to just shut it off or leave it on; the widgets dont do it, so I cant figure out how to stop it..
was working fine before this..
On stock 2.2 froyo, stock kernel...
any ideas?
thanks!
Click to expand...
Click to collapse
i read the thread you started about this issue. you mentioned you were having trouble breaking the on/off loop but then mentioned your wife somehow was able to do it. while in the on/off loop, did you find that the the radio was actually spending any time "scanning" after it turned on? on one of my evos, the phone would switch from on to off and back to on so quickly, the button was always grayed out in the wireless menu so i could never interrupt it. on my other evo, it would spend a little time scanning ( a second or 2), which was enough time to press the button so the 4g would turn off for good and break the on/off loop. a hard reset fixed the phone with the unbreakable loop (4g now works). a hard reset caused the other phone to change so that 4g just hangs at "turning on..." when i try to toggle it on.
kf2mq said:
Ok you may have hammered your 4G then. I've heard of a couple of people who took the leaked update, and fouled up their 4G. I would suggest you backup your stuff then run the latest RUU to see if that clears things up with the wimax driver not loading. If not take the phone to Sprint.
Click to expand...
Click to collapse
By running the latest RUU, do you mean perform the latest OTA sprint update (the .6) by putting in on my SD card and doing the volume down/power button trick? Is this safe if I already have the update applied? I was considering doing this but wasn't sure if it would be safe to do.
The issue: You go into menu -> wireless & networks and check the box for 4G. You watch it say "Turning on..." for a while, it looks like it does something for a split second, and then it turns off, and the box is no longer checked.
I just resolved this by accident (for myself anyway, ymmv) and I haven't seen this issue/resolution identified here yet, so here you go.
Are you using switchpro? Remember the issue where it would turn on 4g on reboot? Well, that was resolved in the most recent version, but it looks like the widget is still broken as it relates to 4g.
It looks like if you use the switchpro widget to toggle 4g on or off, it works fine and will scan for networks, and stay connected. But if you try to turn it on through menu and wireless networks, it turns off immediately. Also, if you turn it on through SwitchPro first, then you can turn it off and back on through wireless networks, and it will keep connecting fine,until you use switchpro to toggle it off.
Wierd, huh?
Thank you! I was having the same issue and couldn't figure it out. I don't have 4G in Denver so I've never seen it happen yet. I'm visiting in Orlando and was trying to test out 4G when I came across this issue.
holy cow thanks for posting I wish I would have got to a computer sooner to do a search I did a nand restore after flashing myn rc4, then still had issues, flashed again and it worked until I restored my apps and was getting ready to go through one by one. I am so relieved lol thanks a lot
I had this same problem before as well but for me it was System Info Widget causing the issue. It only happened when I restored it with Titanium. If I redownloaded it from the market everything was fine.
I had the same issue I did a nand restore and it fixed the issue than flashed to the rom I wanted.
Thanks OP. I didn't realize you had to exclusively use switchpro for 4g. It was driving me crazy the last day as I tried to figure out which one of my 96 apps was causing the issue!
Thanks OP.
Just had the same issue creep up on me. This solved it.
Hey guys, I have had a problem recently devolop on my phone, regarding 4g. First, I will start by saying that I have read just about everything I can read regarding broken 4g, but find nothing pertaining to my specific issue. Secondly, is there anyone is the Las Vegas area having issues connecting to 4g? Next, here is quick run down of the issue. I use 4g daily, all the time. I have never had an issue with it. I am currently using Myn's warm two point two, RLS2, on kings #11. Never had an issue with 4g, no matter what ROM i've used actually. I have NEVER flashed a wimax update. I have flashed a radio update, maybe a month ago or so. So I was tethering while on 4g, and I downloaded a modified "sexy" rosy, with the browser button on it. I then booted to recovery, wiped cache and davlik, then flashed the rosie zip and rebooted. Everything seemed fine, rosie worked, and all was well. Then I went to turn on 4g, and it won't connect. Just says scanning, connecting to sprint, disconnected, scanning, connecting to sprint, disconnected. After trying a billion times, once I got it to connect, for about 10 seconds, i had great 4g signal (as i always did prior to this) then it kicked back to 3g, and was continuing its scanning loop. So i restored my nandroid backup (which I made right before I flashed that rosie zip, while 4g was working) and I still have the same problem. So, my question is, is it possible to screw up the RSA keys, having not even flashed a wimax radio update? Or am i just experiencing some insane coincidence, that this started happening immediately after flashing that rosie zip. I am not sure how much troubleshooting i should put into this, seeing as I dont see how its possible that flashing that zip could've screwed up my 4g RSA keys. I am not sure how to figure out if it's my phone or sprint's network that is the problem. I have read some threads on how to check if the RSA keys are still in tact, which I will probably try to test that later, but I have never used a command prompt, or ADB shell before. I guess it's time for to read up on that and learn how to do it. I get confused about if I'm supposed to be doing these commands from the phone or my PC. Does anyone have any opinions, suggestions, ideas, insight? Anything? Any pointers would be super appreciated. Thanks fellas.
Sounds like 4g network went down. Can't be anything else if you were able to actually connect even though it was only for a brief moment.
Sent from my PC36100 using XDA App
Thanks for the reply. That is certainly what I am hoping. I used root explorer to look at my MAC address, via data/misc/wimax and the number it provides me with matches the number under my battery, so I believe that is a good thing. One of the post's I read, regarding this issue, said to rename that number (xxxxxxx.tree.xml) to xxxxxxxx.tree.xml.old. I'm not exactly sure what that will do, or if I should try it. I am hesitant to play with things I dont know about (yet). Any further suggestions or opinions? If I were to call sprint, would they tell me if 4g was down in my area? We did have 4 straight days with some pretty insane and sporrattic lightning storms. Perhaps something got damaged.
thanks
So it turns out 4g is down near my house. I'm on 4g right now, just in a different part of town. Sorry for wasting the thread space. Thanks again
not sure where to begin, i suppose by listing my phone specs after root--
using the galaxy s2, (epic 4g touch) using kernal 2.6.35-8lostkernelexp+, build number starburst 11.13.11 v1.9.8r and running nothing but the honey theme.
until today, everything seemed to work fine, then suddenly, i was unable to send pictures via text. not a real big issue, but i travel alot and sending pics back home by messages i a big deal for me. however, normal text's would go through, just not any pics. i could send and receive normal words with no issues.
then, totally lost internet connection--although the 3g is lit up on top, and i have 4 full bars of signal, i cannot surf, all i get is "unable to display webpage". since im at home, i turned on the wifi option and connected through the router in my house, and all worked fine-- i got online, send pic texts, etc...but when i turned wifi off, nothing.
now, back when i rooted the phone, i still kept getting the annoying "system update" messages that the phone normally does, forcing me to install whatever update the phone grabs. to prevent that, i did the steps on this site which was here--
http://forum.xda-developers.com/show...ght=freeze+ota
and disabled my update notifications. well, back to the beginning--now i have no internet at all and god only knows what else is wrong that i have yet to discover.
only thing i can think of at this point, is to unroot the phone , return it to the way it was and see how it goes but i dont want to do that--
any ideas?
since i made the post, i been playing around with the phone. ive reflashed the rom, reinstalled the nothin but honey theme, no changes.....
have NO internet what so ever, no market place, etc...
only way i can get online on the phone is through wifi.....
somethin has happened.... please help??
of course i cant call sprint tech support because of the root so thats not an option.
I'd love to help
You can always backup (Nandroid) then Odin back to stock. Then flash a different rom. WITHOUT THE THEME Hope this helps
thanks, but if at all possible, id rather see if it can be fixed before i do all that. i found another thread that said just reflash it and such, which i did-- no change...
again, only way i can get online is by wifi--- so far, dont seem to have any other issues but desperately need to get the regular internet connection to work, dont know what happened, just quit totally today for whatever reason.
anyone, please?
Try flashing just a different Modem.
Then Update Profile and PRL.
You'll want to check the General forum where you posted this exact same question. Some good advice there.
Sent from my SPH-D710 using xda premium
Check the general forums as suggested or just Reflash the Modem (radio's).