Database Info

[Q] Can't Connect To Mobile Data

Hi, I have an HTC Sensation running Cyanogenmod 9's June 14th Nightly. Originally I was running the June 15th Nightly, but I realized that my data was not connecting.
I was using WIFI and that worked perfectly, but when I was out of range, my phone attempted to connect to T-Mobile's network but failed to do so. The HSPA+ icon flickers on and off while the bars remain full and white. I was still able to make calls but I have no data connection. This was originally on the June 15th CM9 nightly. I flashed back to the June 14th nightly and the problem persists. I have also tried re-booting my phone several times.
I flashed the stock ROM with the 1.17 radios and Data worked but when I went back to ICS ROMS with the latest radios it didn't work. I also tried installing the latest RILs and Data still doesn't work.
Here is how my homescreen looks:
http://gyazo.com/8e4c50313720c6ce34434292d6616a2e
Any help would be greatly appreciated.

I had the same problem using my new Miui Rom (it's based off cm9 nightly) . I used titanium backup to clean out my Roms and just like you I realized that my data keep starting and cutting out. I backed up everything so i re-installed everything one by one until something called Key Chain 4.0.4 finally was found as the missing piece. You might want to install titanium backup and check for that app (key chain)

Mine did that when I was trying to use different APN's. The only one that allows me to connect is wap.cingular
You could check that, I guess. Otherwise, try opensensation and/or a different radio.

[Q] No data connection with any Jellybean ROMs

Hi,
I recently decided to flash a jeallybean ROM since most of them are getting really great and we don't have any word on the official update. Unfortunatly, I'm now unable to get a data connection on my HOX. It's the rogers version which I unlocked and I'm now using on the Bell network. Before flashing, LTE worked fine with the stock sense ROM, but now I don't have any data at all.
ROMs I've tried :
AOKP, MIUI and CM10.
I've tried to : set the data connection to GSM only, nothing, to LTE only, nothing, to WCDMA only, nothing. I've tried all the APNs I've found (pda.bell.ca, pda2.bell.ca, inet.bell.ca). On AOKP it sometimes said "Error while searching for network". WiFi, texts and calls work fine.
If anyone could help me, it would be really appreaciated. Otherwise I'll just revert to Rogers ROM. Thanks alot!

I cant offer any help, but I'm having a similar issue recently. I was on a nightly build of CM10 (from 10/06/12 I believe). I upgraded to a newer build (from 10/10) and I get no data over cell. I flashed it back and things were fine.

Dravyy said:
Hi,
I recently decided to flash a jeallybean ROM since most of them are getting really great and we don't have any word on the official update. Unfortunatly, I'm now unable to get a data connection on my HOX. It's the rogers version which I unlocked and I'm now using on the Bell network. Before flashing, LTE worked fine with the stock sense ROM, but now I don't have any data at all.
ROMs I've tried :
AOKP, MIUI and CM10.
I've tried to : set the data connection to GSM only, nothing, to LTE only, nothing, to WCDMA only, nothing. I've tried all the APNs I've found (pda.bell.ca, pda2.bell.ca, inet.bell.ca). On AOKP it sometimes said "Error while searching for network". WiFi, texts and calls work fine.
If anyone could help me, it would be really appreaciated. Otherwise I'll just revert to Rogers ROM. Thanks alot!
Click to expand...
Click to collapse
Before flashing jelly bean roms you need to flash a sense rom then do full wipe and install cm10 or aokp..
jspidey said:
I cant offer any help, but I'm having a similar issue recently. I was on a nightly build of CM10 (from 10/06/12 I believe). I upgraded to a newer build (from 10/10) and I get no data over cell. I flashed it back and things were fine.
Click to expand...
Click to collapse
Sent from my HTC One X using xda premium

I have the exact same problem with my SGS using the X-bean 3.0 rom.
What's the best solution? Is it because I used to Cwm?

Svenomous said:
I have the exact same problem with my SGS using the X-bean 3.0 rom.
What's the best solution? Is it because I used to Cwm?
Click to expand...
Click to collapse
Every device has its own nuances, as do various ROMs. So I'd advise posting this in the forum specific to your device.

Still no data connection.
I am having the same issue with my AT&T One X phone.
The phone was running 2.20 before it was unlocked/rooted. Installed TWRP, was a noob and forgot to save a backup, fastbooted the boot.img, flashed AOKP and CM10 successfully. With both of these ROMs, I could not get internet to work via cellular connection. I have tried everything with the APNs (even had AT&T help me setup APN settings) and still no mobile data connection. I can still receive/send SMS/calls, use bluetooth and wifi, just no mobile internet.
I'm not entirely sure what to do next. I attempted to go back and flash the UrDroid 4.1 Stock Sense ROM, but after fastbooting it's boot.img and attempting to flash with TWRP, I got a signature verification failure. Got scared and restored back to AOKP (I remember to make a backup this time.)
Thoughts? Sorry for being a noob.

Are you in an LTE area?

redpoint73 said:
Are you in an LTE area?
Click to expand...
Click to collapse
I am in a "4G" area (HSPA+) but I am also a hour drive away from LTE. I have tried APNs for both, but AT&T recommended I stick to the LTE APN. AT&T had me go to Settings->More->Mobile Networks->Network Operators and the phone just sat there searching without finding anything. I just did that above operation again and it found AT&T and I selected it. It spins on "Registering on AT&T..." for a few minutes and eventually errors out "Cannot register on this network at this time."

Have you tried switching off LTE by selecting "GSM/WCDMA Auto" in Settings?
I've had data problems on certain ROMs, where turning off LTE got the HSPA+ connection working.
In that case, it was probably a base of build.prop not playing well with AT&T's network. Although I would think the ROMs you mentioned would have these issues worked out at this point (and for some time now).

redpoint73 said:
Have you tried switching off LTE by selecting "GSM/WCDMA Auto" in Settings?
Click to expand...
Click to collapse
When I switch to "GSM/WCDMA Auto", it immediately switches itself back to the LTE setting. This is concerning.

[Q] No cellular wireless signal after Cyanogenmod 9 - ICS on i897

Not getting a cell phone signal at all on my Captivate. very rarely I get it and it stays on until I reboot for some reason, or sometimes goes off on its own. No problem with wi-fi or anything else.
Have had Gingerbread 2.3.5 - KK4 (official) for a long time, and did not have this problem. Here is what I did:
Installed Cyanogenmod 9.0 (ICS 4.0.4) on my Captivate that had the stock Gingerbread KK4. Also installed the gapps-ics package from 29 April 2012
I did this after rooting, and installing clockworkmod.
Even updated it to Cyanogenmod 9.1, but have the same issues.
More detail on it:
- The cellular radio shows no signal, but Wifi is on fine.
- When I press the power button, I see the power off and reboot options, including one that says "Airplane Mode is ON", although it clearly isn't since Wifi is working
- A couple of times, I rebooted into recovery, and did a "repair permissions" and rebooted, and it got a signal, but does not happen always
- Once the signal is on, it stays on for the whole day, but goes off again after a reboot
- Turning Airplane mode on and off does not help
Is this a modem issue, that seems to be a popular problem. It's almost as if there is a software bug that fools the phone into switching off wireless radio
Please help me fix it, or share successful fixes

I had same problem when I went to helly bean then back to remics-jb I flashed back to stock then back up to what I wanted it fixed the problem so I think its the modem.
Sent from my SGH-I897 using xda app-developers app

You need to flash to stock and back.
Sent from my SGH-I777 using xda premium

How do you flash your rom?
Im a little bit afraid to bricked again my cappy.
Sent from my SAMSUNG-SGH-I897 using xda premium

KOROCK is right
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?

up_on1 said:
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
Click to expand...
Click to collapse
Not fixed yet. Wheredo I get the stock rom.?

rdugar said:
Not fixed yet. Wheredo I get the stock rom.?
Click to expand...
Click to collapse
A little search/reading goes a long way.. http://forum.xda-developers.com/showthread.php?t=1300843
KK4 is what you'll want to go back to stock but I highly suggest you read this before you do anything http://forum.xda-developers.com/showthread.php?t=1350266
Also, before returning to stock, you could try flashing a different modem.

Check to see if your baseband is still there. If it said "Unknown", you need to restore it. CM9 is supposed to have the modem.bin file included though. Check to see if the /radio folder have modem.bin in it, if it does, and the baseband still say Uknown, then manually delete the modem.bin, do a wipe and reflash a CM rom that have modem.bin included.
If Baseband is still there and still no signal, then check to see if IMEI is corrupted or lost (if its null or doesn't match the back of the phone). You can either copy over the efs backup folder if you have one and "fix permission" in CWM. If not, then you need to ODIN the phone to stock to fix it.

[Q] Service is toggling after flashing JB on i727

I have two questions 1) is my only way to fix this to go back to stock ICS using ODIN? 2) Once i get back to that, what do i do in order to get to a working version of JB? is it as simple as trying another ROM? Is it ok to skip ICS and just flash another version of JB?
Background if you want it....
Followed vincon guide : http://forum.xda-developers.com/show....php?t=1773659
Started with Stock ATT 4.0.4
CWM via odin
baseb: UCLI3
I flashed JB [ROM] [4.1.2] [UCLL3] Stock Debloat to my i727 last night. Everything went seemingly smooth, everything worked with a strange exception being my exchange account wouldn't authenticate.Today my service is off about 95% of the time, then it will come on and ill get a text or two, then it goes off. voice calls dont work at all. LTE data is hit or miss.WiFi works
In phone status under network type its toggling: UTMS:3 to HSPA:11 to HSPAP15 to no service...then it drops everything and service state will say out of service and disconnected.
My IMEI is correct, I confirmed that.
It tried dialing the *#*#XXXX#*#* thing, that just said no connection and ended.
I started to go down the path of looking to flash a new radio, but that just doesn't seem like the answer to me... obviously the risk of me being wrong is high. i did check the MD5 numbers on other radios though and they came back as mismatched, so i did nothing there.
Also i wiped cache 3 times, as well as dalvek
Is there a simple solution that Ive missed or do i need to go to stock via ODIN? What, if anything, did i do wrong>

If you didn't flash corresponding UCLL3 baseband - AFAIK intermittent service is expected.
If you need to flash baseband - flash the latest UXUMA7 baseband.

Well i've actually had the exact same problem, in several variations and on several androids and here's my conclusions:
1 Magnetic storms and grid issues with the carrier. There's not much to do about these, except maybe for a making a tin hat for your phone. But, on a second thought this would also kill the signal
2 If the issue persists for more than a couple of days then the other thing for me was = radios that just didn't work with my carrier or rom. Changing these showed instant results.

I actually had this exact problem but for me it was on the carrier end. I tried every ROM and radio out there to no avail. After about a month and my parents also experiencing the issue, we called the carrier and they had it fixed in about two weeks.
Sent from my SGH-I727 using xda app-developers app

thanks for the help -
gonna try latest baseband and see how it goes

bgcole said:
thanks for the help -
gonna try latest baseband and see how it goes
Click to expand...
Click to collapse
It worked. Thanks again to all.

That's good to hear

[Q] SMS won't send. Can receive/send MMS calls and Data

The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.

This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already

It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899

Just looking for more info
Sent from my SCH-I535 using Tapatalk

Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.

I'm 717
Sent from my SCH-I535 using Tapatalk

I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.

I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk

Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658

DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.

Anyone try aosp to see if fixed yet?

Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.

capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...

What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app

capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app

I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.

capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.

I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.

Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,

Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.