[Q] No Service Anywhere, No APNs - Help? - Samsung Infuse 4G

I was downloading something, updated adfree, and all of a sudden, I couldn't connect to the internet. I toggled airplane mode, and it read zero bars in places I always had service. I checked with an iPhone 4S, I got full bars, but with my Infuse, it just didn't get signal at all. I tried to check the APNs menu, but when I opened APNs, it just sent me back to the normal settings.
I figured I would just flash a different ROM. Didn't work, still no service. Restored from backup, didn't work. Odined back to Froyo AND GB stock, neither worked. No matter what I do, I'm stuck without the radio. Help!

Delete whatever you were downloading, delete ad-free, wipe data,cache, and dalvik and reflash modem from ISET page. If that does not work it is likely you have a hardware problem. (warranty repair if still in first 12 months)

Related

[Q] Mobile AP and texting problems

My wife's Infuse was running Serendipity VII. She was having some minor problems with it (such as the camera's flash not working consistently) and some apps crashing. So we decided to go with Zeus. Then the problems really started pouring on.
I flashed Zeus without doing a factory reset. I just wiped the cache partition and the Davlik cache. It was OK for a day or two, then it started misbehaving. More crashes, sluggish, when she sent a text message she'd get a "Message not sent" error (so she'd keep trying until she didn't get the error, meanwhile every attempt was actually being sent so people were getting her texts multiple times), Mobile AP would turn itself off (we do pay for the Mobile AP plan with AT&T).
So I did a factory reset/wipe user data, wiped the cache areas, and re-flashed Zeus. Restored everything with Titanium Backup. No change in behavior.
So, I used Odin to flash back to stock UCKD5 (using this). Things were OK for a day or so except that the time was displaying UTC time instead of local time. (I started another thread about that.) Then, the mobile AP started shutting off again, now with a message saying we don't have a Mobile AP plan. But we do. I flashed a new modem (UCKL2) last night hoping that would clear up both issues. It fixed the time problem, but Mobile AP is still saying we don't have a plan. And now she's also getting the "message not sent" error again when sending text messages (although the messages ARE being sent).
Any ideas on what the heck happened and what I could do to get her going again? Using the "Mobile AP" is essential as it is our only home internet connection (no cable or DSL available and we ditched satellite a few months back) and our kids are enrolled in an online school.
Would flashing another ROM clear things up? Maybe try stock again with the "ultimate unbrick" package or the Heimdall one? Or maybe try Zeus again? Or CatyRom?
I reflashed to stock again using ultimate unbrick. (Wiped cache, factory reset, Odin to stock.) Mobile AP gave same errors. Texting seemed fine, but with Mobile AP not working I didn't test it long. Flashed Zeus again (Rooted, installed CWM, wiped cache, factory reset, formatted internal SD, installed the Zeus zip, rebooted and waited about 15 minutes before touching it.)
Mobile AP is fine (for now anyway) but texting is flaky. Some texts go through, but most don't. She just gets an error saying "Message not sent."
Any ideas out there???
HeathicusF said:
I reflashed to stock again using ultimate unbrick. (Wiped cache, factory reset, Odin to stock.) Mobile AP gave same errors. Texting seemed fine, but with Mobile AP not working I didn't test it long. Flashed Zeus again (Rooted, installed CWM, wiped cache, factory reset, formatted internal SD, installed the Zeus zip, rebooted and waited about 15 minutes before touching it.)
Mobile AP is fine (for now anyway) but texting is flaky. Some texts go through, but most don't. She just gets an error saying "Message not sent."
Any ideas out there???
Click to expand...
Click to collapse
Idk..maybe you need and apn change.
Go to settings. Wireless. Apn.
Menu to bring up 2 stock apn.
create a new one. it's around..check my sigs line. After you write it in, menu and save. Select the new apn.
Reboot
Found the APN info in the first link. Thanks! Does the name matter? I noticed it is "AT&T WAP" on my Captivate but "AT&T 310 410" on her Infuse.
HeathicusF said:
Found the APN info in the first link. Thanks! Does the name matter? I noticed it is "AT&T WAP" on my Captivate but "AT&T 310 410" on her Infuse.
Click to expand...
Click to collapse
no..you can call it what you want.
HeathicusF's 310 410
but just for s&g's, I would call it "AT&T 310 410"
Did it fix your issue?
I haven't made any APN changes yet. She uninstalled GoSMS (which had been restored with TiBu) and reinstalled it from the market. That was a "grasping at straws" solution since the problem was happening in both GoSMS and he stock SMS application. So far, no problems. But there have been other little spans of time with no problems then it would start acting up again. So I'm just keeping an eye on it right now. There are some differences between her APN settings and the ones listed, but I don't want to change anything if it really is working now.
OK she has narrowed it down to a problem with long text messages. Anything over 160 characters will fail. That is why she thought it was flaky and working for a while each time we made a change. She'd send a lot of short "testing" type messages, which would go through and she would think everything was good. Then eventually she would write a long "real" message and it would fail and she would think the problem had "returned". Not having any problems like that before, she never associated the problem with the message length.
Based on some quick research, I think that is a modem problem.
If we can fix this issue, she'll be all good again.
HeathicusF said:
OK she has narrowed it down to a problem with long text messages. Anything over 160 characters will fail. That is why she thought it was flaky and working for a while each time we made a change. She'd send a lot of short "testing" type messages, which would go through and she would think everything was good. Then eventually she would write a long "real" message and it would fail and she would think the problem had "returned". Not having any problems like that before, she never associated the problem with the message length.
Based on some quick research, I think that is a modem problem.
If we can fix this issue, she'll be all good again.
Click to expand...
Click to collapse
lol..click on my sigs -link #1. Read post #2.
it has to do with a modem ucki3.
She has UCKL2.
EDIT: I misunderstood and thought you were saying the problem was with the UCKI3 modem. Should have looked at that post you pointed me to first. I see now that UCKL2 is the problem and UCKI3 is the solution.
HeathicusF said:
She has UCKL2.
EDIT: I misunderstood and thought you were saying the problem was with the UCKI3 modem. Should have looked at that post you pointed me to first. I see now that UCKL2 is the problem and UCKI3 is the solution.
Click to expand...
Click to collapse
..........

Network icons never turn blue anymore on JB

My network icons (WiFi, Cell Signal) used to turn blue (showing connectivity to Google). I tried XenonHD and decided it wasn't for me so I flashed back my Nandroid of the 4.1.1 OTA from kibmcz. For some reason, it seems that after flashing back, my icon never turns blue, even though I can connect to the Play Store, retrieve Gmail, receive Google Voice notifications, etc.
Any thoughts on how to restore this background connection to allow my network icons to turn blue?
I'm backing up (TB) and getting a Nandroid, then reflashing. I think it may be due to the device ID. This was the first time I chose to get the old device ID back when restoring from TB, instead of choosing ignore and keep the new device ID.
Update coming soon...
I've never had issues with changing or not changing the device ID (I've done both over the course of trying out way too many roms). Any chance you accidentally restored some system or Google date with TB? That could cause some problems. In general, don't restore through TB unless there is unrecoverable data that doesn't really interact with the system (such as game scores). If you can restore the data from somewhere else (email from a server, etc) do that. Restore any apps that don't need their data restored from the Play Store (translate, browsers, etc)
Instead of reflashing the OTA, I decided to go with a CM10 (listed in signature). This time I selected "Ignore (keep the new device ID)" and this seemed to work. Coincidental or not, the only time this has been an issue is when I told TB to restore the device ID. Perhaps a TB bug? I'm not sure. I've always restore almost everything stored in TB and never had any issues, especially since I typically don't flash multiple ROMs. I usually stick to stock OTA.
Thanks for the reply, dvorak. I may start doing that if I switch ROMs and not just re-flash the same ROM.

Cant make/receive calls and data drops

After odining back to root66 and trying to install PA, I cant make or receive calls or use data. My IMEI is all still there and everything in phone status looks normal to me. Could you guys think of anything? I'm a little nervous. I've also backed up my imei a few different ways including the most recent one.
UPDATE: I just tried to re provision using the dialer code and still nothing.
I'll try odinging back to stock again. And my Imei, Iccid, eveything is still there.

Can't send texts on VRBMF1

I have not been able to send texts using vrbmf1 firmware since it has been released. Everything else works fine.
I have been using aosp ROMs pretty much since they first came out. I have tried everything, besides a TW rom to get it to work.
I always just get pissed and flash back to mb1 and boom, I can text again. Weird stuff. Frustrating because data and signal does seem to be better on MF1!
Over the last few months I have tried redownloading the modems, pulling my sim, full wipe, cache wipe, clearing messaging data, reinstalling my messaging app, and even doing a little dance.
My phone hates vrbmf1. If anyone has an idea, or has ran into this problem before I'd appreciate some help!
bump. anyone have any ideas? would the next step be trying to go back to stock? been so long since i have been on TW i dont even remember how to use odin anymore haha.
i thought the new baseband might fix it but it does the same thing. sometimes texts get out, but most of the time they just hang forever at sending.... i flash back to MB1 and they send right away. on cm11
what am i missing out on by not running the latest firmware?
I have the same problem, it works fine after resetting but after a few days it doesnt work if i text with the country code

Phone died and WiFi will not turn on.

I'm running DigitalHigh GPE ROM, 5.0.1, S-OFF, TWRP, etc.
My phone died last week (battery ran out) and after I charged it back up, it would no longer connect to any WiFi networks. When I go into the settings, and try to turn on the WiFi, the switch on the screen moves but nothing happens, and backing out and in the menu again the slider returns to the 'off' position. Is there a way I can reflash the Wifi module or restore it or something similar that doesn't require a full system refresh? If not, I'll probably end up flashing a nandroid backup from about 2 months ago and then working to recreate anything lost in the interim (backups of new software, sms db, etc.)
Edit: With no response I went ahead and restored to a backup from about 2 months ago. It worked fine, WiFi works again. Only problem now is that for some reason I can no longer send/receive MMS which is kinda a huge pain when my friends and family group text (mms) so frequently!

Categories

Resources