Has anyone gotten Sprint MMS to work using any custom ROM? Every ROM I have tried I can get Data and SMS to work fine, but I am unable to send or receive and MMS. If I re-flash the stock it works just fine. I've tried builds of Lineage, AOSiP, AquiriOS, and dotOS. Everything else in all the ROMs seem to work just fine. Any idea what is causing this or how I might go about resolving it?
Sorry, I know this doesn't help you any but many of us are still trying to find an answer, is your Pixel purchased directly from Sprint? We still don't have a definitive answer to if the Sprint model Pixels bootloader can be unlocked or not.
Also if it helps any on my Nexus 6 running CrDroid 9.0 MMS isn't working either, hasn't worked since 8.0. I have tried changing the APN's, changing settings in Hiddenmenu, and messing around with Android Messages hidden settings as well as combing the system configs with root and everything looks normal, no weirdness in logcat, just failure to send.
LaGgY_42o said:
Sorry, I know this doesn't help you any but many of us are still trying to find an answer, is your Pixel purchased directly from Sprint? We still don't have a definitive answer to if the Sprint model Pixels bootloader can be unlocked or not.
Also if it helps any on my Nexus 6 running CrDroid 9.0 MMS isn't working either, hasn't worked since 8.0. I have tried changing the APN's, changing settings in Hiddenmenu, and messing around with Android Messages hidden settings as well as combing the system configs with root and everything looks normal, no weirdness in logcat, just failure to send.
Click to expand...
Click to collapse
No I purchased mine from the google store. I have to imagine that some package or apn setting is different between stock and the roms, but I don't know what at this point. It somewhat frustrating that it works just fine on stock, but not on anything else. Googleing the issue suggest that Sprint has changed similar things in the past which caused issues.
Factory reset, then flash stock. Once it boots and LTE connects, power off and go to bootloader and boot into twrp. Then, without wiping anything, flash whatever aosp rom you want. You should then be able to connect to data and have mms working.
If mms still doesn't work, you can dl an older version of Textra (Nov 2018ish) and select legacy settings for mms. Then you only have to set:
MMSC: http://mms.sprintpcs.com
MMS Proxy: oap7.sprintpcs.com
MMS Port: 80
jdee323 said:
Factory reset, then flash stock. Once it boots and LTE connects, power off and go to bootloader and boot into twrp. Then, without wiping anything, flash whatever aosp rom you want. You should then be able to connect to data and have mms working.
If mms still doesn't work, you can dl an older version of Textra (Nov 2018ish) and select legacy settings for mms. Then you only have to set:
MMSC: http://mms.sprintpcs.com
MMS Proxy: oap7.sprintpcs.com
MMS Port: 80
Click to expand...
Click to collapse
Thanks for the help! Flashing a rom without wiping anything did not work. However, using an old version of Textra using the legacy settings does. Do you know any way to force the regular Messaging app to us these APN settings as well? I tried changing the /system/etc/apns-conf.xml to match those setting but I'm still getting a failure to connect.
Code:
[07-07 13:06:17.535 1613:5348 E/MmsService]
[[email protected]] HTTP: IO failure
java.net.ConnectException: Failed to connect to /68.28.31.7:80
at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:143)
at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:112)
at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:184)
at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:126)
at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:95)
at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:281)
at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:224)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:461)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:127)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getOutputStream(HttpURLConnectionImpl.java:258)
at com.android.mms.service.MmsHttpClient.execute(MmsHttpClient.java:186)
at com.android.mms.service.SendRequest.doHttp(SendRequest.java:83)
at com.android.mms.service.MmsRequest.execute(MmsRequest.java:171)
at com.android.mms.service.MmsService$2.run(MmsService.java:414)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Here is the full logcat if it helps.
team_gold said:
Thanks for the help! Flashing a rom without wiping anything did not work. However, using an old version of Textra using the legacy settings does. Do you know any way to force the regular Messaging app to us these APN settings as well? I tried changing the /system/etc/apns-conf.xml to match those setting but I'm still getting a failure to connect.
Code:
[07-07 13:06:17.535 1613:5348 E/MmsService]
[[email protected]] HTTP: IO failure
java.net.ConnectException: Failed to connect to /68.28.31.7:80
at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:143)
at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:112)
at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:184)
at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:126)
at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:95)
at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:281)
at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:224)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:461)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:127)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getOutputStream(HttpURLConnectionImpl.java:258)
at com.android.mms.service.MmsHttpClient.execute(MmsHttpClient.java:186)
at com.android.mms.service.SendRequest.doHttp(SendRequest.java:83)
at com.android.mms.service.MmsRequest.execute(MmsRequest.java:171)
at com.android.mms.service.MmsService$2.run(MmsService.java:414)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Here is the full logcat if it helps.
Click to expand...
Click to collapse
I'm really not sure why it started working for me. I tried editing settings.db and lost all connectivity. I wiped and then flashed stock, then after connecting to lte, I dirty flashed aquarios and everything was working.
I'm having the same issues with AquariOS , restoring a backup to get mms back. Everything else worked great and loved the custom touches. I also noticed I couldn't add an APN, I'd fill it out and save but it never showed up as an option.
jdee323 said:
Factory reset, then flash stock. Once it boots and LTE connects, power off and go to bootloader and boot into twrp. Then, without wiping anything, flash whatever aosp rom you want. You should then be able to connect to data and have mms working.
If mms still doesn't work, you can dl an older version of Textra (Nov 2018ish) and select legacy settings for mms. Then you only have to set:
MMSC: http://mms.sprintpcs.com
MMS Proxy: oap7.sprintpcs.com
MMS Port: 80
Click to expand...
Click to collapse
I followed your textra advice on Sprint LG V30 AOSP also. It worked. Thanks
Related
Hey. I have been having an issue getting data to work for H2O mobile when using CM7 (latest nightly.) I have tried using the settings that they list on their website, but it says that I must enter an MCC and MNC number when it says it should be blank. If I leave the defaults, it does not work. I downloaded their install app, but the data still does not work with those settings selected. All CM7 based roms do this (at least all those released within the past 2 months.)
The strange thing is that it does work (with the install method) when using OTA based roms. I don't know why one does and one doesn't. On the OTA it says I am running on AT&T, where as H2O shows up on CM7.
Does anyone have a solution for this? Or will CM7 just not work?
Thanks.
lightofhonor said:
Hey. I have been having an issue getting data to work for H2O mobile when using CM7 (latest nightly.) I have tried using the settings that they list on their website, but it says that I must enter an MCC and MNC number when it says it should be blank. If I leave the defaults, it does not work. I downloaded their install app, but the data still does not work with those settings selected. All CM7 based roms do this (at least all those released within the past 2 months.)
The strange thing is that it does work (with the install method) when using OVA based roms. I don't know why one does and one doesn't. On the OVA it says I am running on AT&T, where as H2O shows up on CM7.
Does anyone have a solution for this? Or will CM7 just not work?
Thanks.
Click to expand...
Click to collapse
CM7 has a problem with data connections in general on the G2x. Try doing a hard reboot and see if that brings back a data connection for you, if you had one in the first place
Once again, a hard reboot is holding power + volume up until the phone resets
I never had data on 2.3.5, but I did a hard restart and still nothing. :/
I know a lot of people have been reporting issues with getting or keeping LTE with some of the CM based roms. I too had the issue.
After digging through threads for the HOX and several other devices I was able to find a solution (for me) and just wanted to share my findings here in a fresh thread (plus I'm a noob and can't post in the developer threads for those experiencing the issue).
Any time I went from a 4.0.4 Sense-based rom to any of the cm based roms I could never get my LTE to stick even after changing apns or *#*#info#*#*. What I discovered was if I would flash a Sense-based rom that was prior to 4.0.4 (I use cleanrom 4.0) , wipe caches, full wipe and then install the CM based rom all things were good with my LTE regardless of which radio I flashed.
Hopefully this will help some of you out there.
I've also discovered that coming from cr4.5 that there are settings that stick...namely wifi settings. I've wiped everything on my phone including internal storage and flashed something new and in the newly flashed roms there are wifi settings were remembered.
I don't know where any of this stuff is stored in the phone but i thought that a full system wipe, cache, dalvich would have cleared EVERYTHING.
jess.hickey said:
I've also discovered that coming from cr4.5 that there are settings that stick...namely wifi settings. I've wiped everything on my phone including internal storage and flashed something new and in the newly flashed roms there are wifi settings were remembered.
I don't know where any of this stuff is stored in the phone but i thought that a full system wipe, cache, dalvich would have cleared EVERYTHING.
Click to expand...
Click to collapse
wifi settings are synced to google FYI
gunnyman said:
wifi settings are synced to google FYI
Click to expand...
Click to collapse
Learn something new every day...thanks!
Then might I ask, why don't those settings, or why don't my apps auto load, when I use an AOKP rom?
jess.hickey said:
Learn something new every day...thanks!
Then might I ask, why don't those settings, or why don't my apps auto load, when I use an AOKP rom?
Click to expand...
Click to collapse
good question, that's one for the AOKP folks.
Flash to CR 4.0 works!
jess.hickey said:
Any time I went from a 4.0.4 Sense-based rom to any of the cm based roms I could never get my LTE to stick even after changing apns or *#*#info#*#*. What I discovered was if I would flash a Sense-based rom that was prior to 4.0.4 (I use cleanrom 4.0) , wipe caches, full wipe and then install the CM based rom all things were good with my LTE regardless of which radio I flashed.
Hopefully this will help some of you out there.
Click to expand...
Click to collapse
THANKS! I wasn't getting a 4G icon at all on CM10 but I did a full wipe (factory/system), flashed CR 4.0, checked 4G speeds (check), did another full wipe and installed CM10 & GA. As soon as the welcome screen came up I saw a 4G in the status bar. :good:
edditnyc said:
THANKS! I wasn't getting a 4G icon at all on CM10 but I did a full wipe (factory/system), flashed CR 4.0, checked 4G speeds (check), did another full wipe and installed CM10 & GA. As soon as the welcome screen came up I saw a 4G in the status bar. :good:
Click to expand...
Click to collapse
I can confirm that the above mentioned fix worked for me too!
When u say full wipe. What exactly do u wipe? cache? system? external storage? factory reset?
jzhang0818 said:
When u say full wipe. What exactly do u wipe? cache? system? external storage? factory reset?
Click to expand...
Click to collapse
Wipe Caches, Factory Reset, System wipe. Everything but the SD card.
[EDIT] I shouldn't say "everything". No need to wipe battery stats, rotation or SD card for this particular fix.
Should I do a fresh flash of cm? Or do u think a cm backup would work?
(Update), dirty flash back no working for that. Too lazy to go other route at this point.
Sent from my One X using xda app-developers app
worked for me perfectly. Thanks.
this is driving me nuts
I tried following this.... nothing works
clean ROM 4.0 then wipe 'all' then install CM10 8-29 (since link to 8-30 is broken)
I am still only getting HSPA and 3G
APN is always set to WCDMA by default
I use clockwork recovery... could that be it ?
help me out guys.
philippe.bureau said:
I tried following this.... nothing works
clean ROM 4.0 then wipe 'all' then install CM10 8-29 (since link to 8-30 is broken)
I am still only getting HSPA and 3G
APN is always set to WCDMA by default
I use clockwork recovery... could that be it ?
help me out guys.
Click to expand...
Click to collapse
Under settings, wireless and networks, more, mobile networks, access point names are you on the ATT LTE apn?
Sent from my One X using xda premium
stnguyen09 said:
Under settings, wireless and networks, more, mobile networks, access point names are you on the ATT LTE apn?
Sent from my One X using xda premium
Click to expand...
Click to collapse
I am with Rogers. I see rogers-core-appl1.apn that was set by default.
I do not know if this should or not connect to LTE. I found on a website that I could use ltemobile.apn but its only getting me HSPA and 3G.
I might have to reflash on cleanrom 4.0 and compare APN. but i do get 4G-LTE with clean rom
Anyone can tell me what APN they use to get LTE on rogers with all APN info?
Thanks
---------- Post added at 12:06 PM ---------- Previous post was at 11:16 AM ----------
SUCCESS !!!!!
ok, so the APN was indeed rogers-core-appl1.apn and this one does not give LTE access.
I set up a new APN as below
Name: Rogers LTE
APN: ltemobile.apn
MMSC: xxxx://mms.gprs.rogers.com (please xxxx by https at beginning of the line... sorry as I am new on forum I cannot paste URL)
MMS Proxy: 10.128.1.69
MMS Port: 80
MCC - 302
MNC - 720
APN Type: *
I then changed the mode to LTE/GSM/CDMA using the *#*#4636#*#* and I now get 4g icon that means LTE.
I also see the its LTE from the phone info page.
Thanks for your help.!!
philippe.bureau said:
I am with Rogers. I see rogers-core-appl1.apn that was set by default.
I do not know if this should or not connect to LTE. I found on a website that I could use ltemobile.apn but its only getting me HSPA and 3G.
I might have to reflash on cleanrom 4.0 and compare APN. but i do get 4G-LTE with clean rom
Anyone can tell me what APN they use to get LTE on rogers with all APN info?
Thanks
Click to expand...
Click to collapse
For the Rogers phones I have done 3 of them now and when you flash CleanRom 4.0 you have to go in and setup the Rogers APN and connect at least once. I found this makes a huge difference. If you don't for whatever reason the settings don't stick.
Once you flash CM10 I turn mobile data off and erase the 3 APN's that are listed. I then start fresh with a new APN for LTE.
I only have HSPA+ out here where I am so I can't test if the LTE or 4G symbol comes up. I have noticed that with HSPA+ I still only show as connected to HSPA under Phone Info but the speeds are HSPA+.
The settings for the APN that I used for Rogers is:
Name Rogers LTE
APN ltemobile.apn
Proxy Not Set
Port Not Set
User Not Set
Pass Not Set
server Not Set
mmsc http://mms.gprs.rogers.com
mms proxy 10.128.1.69
mms port 80
mms protocol WAP 2.0
mcc 302
mnc 720
auth Not Set
apn type *
apn enabled enabled
bearer unspecified
Also CM10 erases the voicemail number from the phone. So call your phone from your phone and access your voicemail. If you check your call log after that the voicemail number should show up there.
josh3794 said:
Also CM10 erases the voicemail number from the phone. So call your phone from your phone and access your voicemail. If you check your call log after that the voicemail number should show up there.
Click to expand...
Click to collapse
yes I had that fixed. number is +1 514 992 1188 for my region (Montreal)
By the way, the signal type reset on reboot. I need to dial *#*#4636#*#* and select LTE/GSM/CDMA.
I know some people have made it stick and I followed the instructions but it does not work for me. hopefully they can fix this.
I cleared everything and flashed to cleanROM 4.0 then cleared again and installed CM10-8-29.
This is a minior issue but gets on my nerves.
Cheers !
philippe.bureau said:
By the way, the signal type reset on reboot. I need to dial *#*#4636#*#* and select LTE/GSM/CDMA.
I know some people have made it stick and I followed the instructions but it does not work for me. hopefully they can fix this.
I cleared everything and flashed to cleanROM 4.0 then cleared again and installed CM10-8-29.
This is a minior issue but gets on my nerves.
Cheers !
Click to expand...
Click to collapse
Try backing up in twrp then flashing to cr4.0 (not 4.5) connect to lte then restore backup without wiping
Sent from my One X using xda app-developers app
sdotfitz said:
Try backing up in twrp then flashing to cr4.0 (not 4.5) connect to lte then restore backup without wiping
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Thanks, I will try that. I always wiped caches in my many attempts
---------- Post added at 01:54 PM ---------- Previous post was at 01:11 PM ----------
philippe.bureau said:
Thanks, I will try that. I always wiped caches in my many attempts
Click to expand...
Click to collapse
Its not working either. Nothing seems to get the signal type to stick on my phone.
Its a minor bug and I guess I can be patient and wait for a fix.
The one that is really bugging me is the low volume on calls.
Hope they can fix it.
philippe.bureau said:
Thanks, I will try that. I always wiped caches in my many attempts
---------- Post added at 01:54 PM ---------- Previous post was at 01:11 PM ----------
Its not working either. Nothing seems to get the signal type to stick on my phone.
Its a minor bug and I guess I can be patient and wait for a fix.
The one that is really bugging me is the low volume on calls.
Hope they can fix it.
Click to expand...
Click to collapse
In regards to the call volume: http://forum.xda-developers.com/showpost.php?p=30919624&postcount=3061
I installed the Infected Eternity Rom on my HTC Thunderbolt and my MMS not working. I have Cricket as my carrier and before I flash my ROM I was able to send and receive MMS. I tried going to messages>menu>setting>multimedia messages>connection settings but I'm unable to click on anything once in connection settings. I also tried put in a new apn.xml, but I couldnt get into the connection settings to finish it. I hope someone can help me out, thanks in advance!
Try hooking the thing up to your computer and using QPST, from there, I think you might be able to modify MMS and APN settings.
http://www.mechacentre.com/resources/thunderbolt-qpst
I have been unable to send or receive MMS messages to/from anyone. Outgoing messages just get stuck at "sending" and I've had multiple people try to send me an MMS. I believe my APN settings are correct based on other threads here. Has anyone else seen/dealt with/have a solution for this bug?
I'm currently running CM10.1 April 8 Nightly off of a clean complete wipe flash, but I believe the problem has occurred with prior versions as well.
dcvito said:
I have been unable to send or receive MMS messages to/from anyone. Outgoing messages just get stuck at "sending" and I've had multiple people try to send me an MMS. I believe my APN settings are correct based on other threads here. Has anyone else seen/dealt with/have a solution for this bug?
I'm currently running CM10.1 April 8 Nightly off of a clean complete wipe flash, but I believe the problem has occurred with prior versions as well.
Click to expand...
Click to collapse
I saw some commits related to unicode encoding with the MMS app. It's possible (Disclaimer: I am not a dev, these are just theories) that these have something to do with the MMS issue. You could extract the MMS.apk from a prior build (where your MMS was still functional) and push it to /system/apps, rename your current MMS.apk to MMS.bak (just in case), set permissions to R-W, R, R, then reboot. If that works then we know there's an issue with the CM commits to the MMS.apk.
Had the same problem this morning. Turns out I had mobile data turned off.
Sent from my SAMSUNG-SGH-I727 using xda premium
Nope, mobile data is on and I have no idea when the last time it was working.
I can't be the only one dealing with this... Anyone? Now running CM 10.1 4/22 Nightly.
dcvito said:
I can't be the only one dealing with this... Anyone? Now running CM 10.1 4/22 Nightly.
Click to expand...
Click to collapse
I've been having the same issue since sometime in march. Also running CM nightlines. I've read it may be something to do with the Access Point Names but no solution is given
briguy42 said:
I've been having the same issue since sometime in march. Also running CM nightlines. I've read it may be something to do with the Access Point Names but no solution is given
Click to expand...
Click to collapse
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
mrfeuss said:
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
Click to expand...
Click to collapse
I've checked out and even rebuild my APN's multiple times to troubleshoot to no avail.... Let's see what ideas we can come up with... Thanks for the help so far.
dcvito said:
I've checked out and even rebuild my APN's multiple times to troubleshoot to no avail.... Let's see what ideas we can come up with... Thanks for the help so far.
Click to expand...
Click to collapse
Hmm. Interesting. And you're using the stock MMS app in the CM Nightlies? Have you tried updating to a newer version?
mrfeuss said:
Hmm. Interesting. And you're using the stock MMS app in the CM Nightlies? Have you tried updating to a newer version?
Click to expand...
Click to collapse
Yes, stock messaging app included with the CM nightlies. What are you recommending that I update?
mrfeuss said:
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
Click to expand...
Click to collapse
Tried using this APN config too and it still didn't work, thanks for the suggestion though.
I have this issue on rooted stock jelly bean I had to set sms to convert the images to smaller resolution to get it to send. Been working for now but would like to be able to send hi res pics
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I had that issue at one time on my stock rooted unit. Turns out that AT&T had changed something on the network side and my account didn't get changed. You might call them and check the settings.
Sent from my GT-N8013 using xda app-developers app
bryanclane said:
I had that issue at one time on my stock rooted unit. Turns out that AT&T had changed something on the network side and my account didn't get changed. You might call them and check the settings.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
I've put in a trouble call with AT&T hopefully they find something....
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
dcvito said:
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
Click to expand...
Click to collapse
If I were you I'd just make a nandroid backup of my current setup, transfer that (and any other important data) to either my external or PC, ODIN back to stock and head over to an AT&T store. Just my two cents. You can always re-root and flash a custom ROM again. If you'd corrupted something through flashing (not saying you did, just a thought) getting AT&T to straighten it out and then going custom from there might be your best option.
dcvito said:
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
Click to expand...
Click to collapse
Sinnce AT&T uses the IMEI number as the ID for the device, that wouldn't be the issue you aren't receiving push messages. I agree with mrfeuss, back up the phone, flash the stock rom, and go have AT&T fix it on their end. Then you can re-root and install your custom ROM again. Better to have them look at it than live without MMS.
bryanclane said:
Sinnce AT&T uses the IMEI number as the ID for the device, that wouldn't be the issue you aren't receiving push messages. I agree with mrfeuss, back up the phone, flash the stock rom, and go have AT&T fix it on their end. Then you can re-root and install your custom ROM again. Better to have them look at it than live without MMS.
Click to expand...
Click to collapse
Check mms after returning to stock as that may solve your problem.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I was afraid that was going to be the suggestion.... Guess I'll start my Firmware DL and backup now... here we go lol
mrfeuss said:
If I were you I'd just make a nandroid backup of my current setup, transfer that (and any other important data) to either my external or PC, ODIN back to stock and head over to an AT&T store. Just my two cents. You can always re-root and flash a custom ROM again. If you'd corrupted something through flashing (not saying you did, just a thought) getting AT&T to straighten it out and then going custom from there might be your best option.
Click to expand...
Click to collapse
Just used Odin to flash back to stock. After the Odin reboot how long should it take for the phone to start up? I've been sitting on the ATT logo screen for a few minutes now.... please don't tell me I bricked....
Never mind, figured out my own mistake..... Always factory reset/clear data before flashing!
Hi All.
I've got a Samsung Galaxy Relay 4G using PhilZ Touch 6 recovery and cm-11-20140518-NIGHTLY-apexqtmo. I have an AT&T sim card and when I try to input APN settings for AT&T nothing saves. I've tried everything including 5 ROM's, all running KitKat emulations. I read that Android 4.0+ will not allow you to change APN settings, but is there some workaround. I've also discovered it disables APN apps from accessing APN settings.
I've also tried to flash 10.2 but I get Status 7 errors every time I try. I've followed instructions on removing access commands from the updater-script file and re-zipping, but it also aborts.
I've called *#*#4636#*#* and it doesn't look like the phone sees the SIM card, but maybe that's due to the APN settings? It won't even call let alone send/receive data. I've tried 2 different AT&T SIM cards with the same result.
Any help would be greatly appreciated!
Kenwood97031 said:
Hi All.
I've got a Samsung Galaxy Relay 4G using PhilZ Touch 6 recovery and cm-11-20140518-NIGHTLY-apexqtmo. I have an AT&T sim card and when I try to input APN settings for AT&T nothing saves. I've tried everything including 5 ROM's, all running KitKat emulations. I read that Android 4.0+ will not allow you to change APN settings, but is there some workaround. I've also discovered it disables APN apps from accessing APN settings.
I've also tried to flash 10.2 but I get Status 7 errors every time I try. I've followed instructions on removing access commands from the updater-script file and re-zipping, but it also aborts.
I've called *#*#4636#*#* and it doesn't look like the phone sees the SIM card, but maybe that's due to the APN settings? It won't even call let alone send/receive data. I've tried 2 different AT&T SIM cards with the same result.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
yes there is a way to be able to and requires modding the build.prop file... i can show you how if need be
REV3NT3CH said:
yes there is a way to be able to and requires modding the build.prop file... i can show you how if need be
Click to expand...
Click to collapse
Actually it turns out I couldn't see the IMEI number either, so I returned to stock ROM and could then see the IMEI. I then flashed CWM 6.0.1.2 and CM 10.2 and was able to then set the APN. I'm still having trouble getting phone and data connection over the cell, but at least it now shows some bars. Thanks for replying, though.
My connection issue was a problem with the SIM. It's all working properly now.