Recently wiped and started from scratch on Warmrom due to a messed up backup and suddenly I'm unable to send or receive any MMS messages.
Out of pretty much nowhere, I'm suddenly getting "Download of message unsuccessful - Generic network failure" when I try to download picture messages and "Failed to send after multiple attempts - generic network failure" when I try to send.
I haven't installed anything that would mess with my APN settings or MMS settings in general.
I've tried multiple fixes including clearing the data for my phone's MMS app as well as checking my APN settings for errors and problems with APN Backup and Restore - I couldn't find anything way out of the ordinary. I've also tried PRL and profile updates multiple times from settings.
Any ideas?
Edit: Apparently the "proxy" was stuck on from when I was on WIFI. I thought I messed with it, but apparently the settings didn't stick properly. Re-edited them and rebooted and messages are at least coming in now, but I'm still getting the generic error when I try to send or receive MMS.
Edit2: Also tried wiping MMS settings via Titanium. No go.
Edit3: Just restored a backup I made a month ago, back when my MMS messages were working. Again, no go. No freaking idea what could be going on.
update your profile manually or have sprint do it
t3project said:
update your profile manually or have sprint do it
Click to expand...
Click to collapse
How would I go about updating my profile manually aside from "System update > Update Profile"?
I've already used that method. Is there another way to do it that is more likely to stick? I know there's a technique involving one of the hidden setup screens, is that what you're talking about?
Edit: Called Sprint, they said they reset remotely and then told me to hit ##3282# and reset my profile. I need to install that epst.apk that allows for the process, so I'll come back here if it works.
Ok weird. No matter what I do, I can't get the data menu to come up, even with alternate EPST. No freaking idea what is going on. Hopefully whatever the sprint rep did will fix it in time.
Final edit: Figured it out. Apparently it was just a series of unfortunate events that led to me having screwed up messaging. The newest nightly of Warm seems to have a problem getting to the data screen even with the old EPST.apk, so I had to revert back to a Nandroid I made early December, reset my profile from there, and upgrade to the current version again after that to get my text messages working properly again.
Related
Is it just me or is anyone experiencing a "Forbidden" error when sending/receiving MMS after updating to AT&T's new ROM with 1.14.25.35 Radio?
I've reflashed the updated AT&T ROM and then flashed NRG's latest 6.5 ROM with the correct Rilphone.dll and still have the Error. I even tried sending from the new stock ROM and got the error. I did this multiple times to make sure it wasn't a bad flash and still have the "Forbidden" error. Did I do something wrong when I flashed the new ROM and Radio? The settings in MMS are correct and I didn't load anything else prior to testing MMS.
At first I thought it was AT&T and wasted over 30 minutes with a rep that knew next to nothing. Then it dawned on me that this all started after I updated to the new ROM/Radio release for AT&T on HTC's website. So, I reverted back to the original shipped ROM with 1.02.25.32 Radio, flashed NRG's latest 6.5 ROM and can now send/receive MMS.
I had the same forbidden error and had to talk to tech support from att.. apparently it's because i had placed my sim into an iphone and we all know iphones can't send mms so it registered into their system that i was using an iphone thereby causing the iphones imei to register to my number hence why it's forbidden to send/receive a mms. did you perhaps do something similar?
ATT0001 file can't open it
Hey Guys... sorry than I can't help to solve your problem.. But i have a problem too with the MMS... what happens is that every time I send or receive a mms to a windows mobile phone comes as ATT0001 file and I can not open .. I need help with this thanks
Loner2DEnd: I did but only to unlock one. I've done this before and have never had that problem up. I only noticed that I wasn't able to send/receive MMS after I had the official update from HTC for the FUZE. I was on the phone with the tech and they told me that using my SIM in an iPhone wouldn't have updated my account. You can log onto your online account with AT&T and see what phone/IMEI is registered with your account. Mine still has my FUZE and correct IMEI. Everything is working now that I reflashed the original shipped ROM with the 1.02.25.32 Radio.
I downloaded another copy of the ROM update from HTC for the FUZE and ran the same tests to see if maybe it was a corrupted file/bad flash and I still had the same issues with MMS. My internet still worked but I got the same Forbidden Error. For now, I'm going to just stay with my current (original shipped) Radio since everything's working.
Dannyedilber: I'm not familiar with that Error. Sorry man. I don't know much about MMS and had to do some homework and some trial and error to finally find this solution. Maybe one of the seniors can answer your question.
I've had this problem a few times but usually fixes itself after a reset or a quick disconnect/reconnect of the radio.
I find that if I leave my data on for an extended period of time, it seems to happen. Almost like AT&T is seeing the high traffic and cutting me off.
Also check to make sure you guys don't have Data disabled in your accounts.
@Dannyedilber: I don't even know what an "ATT0001" file is?
@Loner2DEnd: My wife just returned her iPhone because she said it sucks compared to Windows Mobile (smart girl eh?) and went back to her old Samsung Blackjack. We did this yesterday, after her having the iPhone for a little under 30 days. I just sent her a picture and she got it.
From AT&T
The data network works for all of our devices and the Windows Mobile devices are the only ones that seem to have had some issues with the way the data network is configured. Rather than trying to re-configure and potentially break the network for other users, we have been working on a fix for the Windows Mobile issue. We have a fix that will be implemented by the end of this quarter and we should have the problem resolved at that time.
Click to expand...
Click to collapse
From AT&T
Just wanted to let you know that I did get an update. The project to "fix" the 403 error is moving forward. Right now we plan to have the implementation complete in June with Project closure in Early July. I will follow up again in about a month to see the status and provide closure information.
Just for clarification: This project hasn't slipped a month, we keep the project open during a "soak" period to ensure that everything is going as expected. Also, as we apply the fix to the elements in the network the fix will be applied to certain markets and complaints should drop for that market dramatically. I haven't seen this issue in a while here so I believe that the patch has been applied for the Minneapolis market.
Click to expand...
Click to collapse
An easy temporary fix is to put your phone into flight mode and then take it out. A new data connection almost always works. Worst case scenario soft reset the phone.
so its by market then?
I flashed the new rom about last week, had no issues receiving and sending MMS on it and on NATF's 4.7 rom.
Still No MMS
nmbr6 said:
...An easy temporary fix is to put your phone into flight mode and then take it out. A new data connection almost always works. Worst case scenario soft reset the phone.
Click to expand...
Click to collapse
My MMS is not working incoming or outgoing. I have tried it from TF3D2, Titanium, after reset, after airplane mode and reset with no success. I put my SIM card in my backup phone and MMS send and receive worked flawlessly. I do not get the forbidden error message some of you have gotten; it just does not work. I have reset the RegEdit keys several times and they are currently set at 1.2mb. I know that 6oo K is at&t max, but the two test MMS messages are 77K and 317k. Thanks - David.
Black C5 said:
My MMS is not working incoming or outgoing. I have tried it from TF3D2, Titanium, after reset, after airplane mode and reset with no success. I put my SIM card in my backup phone and MMS send and receive worked flawlessly. I do not get the forbidden error message some of you have gotten; it just does not work. I have reset the RegEdit keys several times and they are currently set at 1.2mb. I know that 6oo K is at&t max, but the two test MMS messages are 77K and 317k. Thanks - David.
Click to expand...
Click to collapse
It sounds like you have a different issue altogether. My posts were answers from AT&T strictly for the 403 forbidden issue.
Player911 sorry that I was not very specific...whats happening is when I send a ATT MMS to someone who have a HTC touch pro to her hotmail account.. she can't open it because the picture come as ATT0001.. even when I send att MMS to myself at my email account I receive as a ATT0001
Need help with this guys.. please
Sorry my english
Hi All:
First off thank you for the info in resolving this issue. Since swithing back to the original shipped ROM with radio 1.02.25.32 then flashing EnergyROM 3.0 Phoenix 6/12, I've had no problems with MMS Forbidden Error. It's been a week now and I've had no data/network issues either. I'll try again with the new Radio/ROM this weekend when I have some free time and will report back. Thanks everyone!
Tru using a registry editor and go in and change the registry in Arcsoft under HKLM>Software>Arcsoft>Arcsoft MMS UA>Config>MM1>MMSCSetting>SampleMMSC>Wap1SendDefault and Wap2SendDefault and change to a desired number. For instance, I have 102400 set to send up to 1MB.
See if that allows you to send.
try enabling ATT's proxy. This always works for me.
1. Enable the proxy
2. Kill the data connection
3. Reconnect data
4. Try sending or receiving.
This has worked countless times for me.
EDIT: 11:15pm 9/25/2012 - ISSUE RESOLVED, SEE BOTTOM OF POST FOR SOLUTION
Okay, relevant information first:
Evo 4G LTE on Sprint
HBOOT 1.15 S-ON HTC DevUnlock
Current ROM CM10 Nightlies
Sprint-Google Voice integrated number
Now for the issue:
Texts can not be sent through the messaging app. When attempting to send a text, it will say "sending..." for a few seconds, then I get a notification saying "message not sent". Clicking on this notification takes me to the messaging app where the failed message has a red triangle next to it. When I long press the failed message, it comes up with a menu, and when I click "view details" it says "Error Code 98".
This happens both when connected to WiFi and when not connected to WiFi. It also happens both in my home town, and another town 45 minutes away (meaning the issue doesn't seem to be with the particular tower).
The last successful text sent or received was on Sept 13th.
Calls still operate as normal.
No changes were made by me between when my SMS was working properly, and when it stopped working. (Same ROM, Recovery, Kernel, etc). I haven't downloaded any SMS apps (handscent, gosms, etc) that could be interfering with the messaging app. I DO have the Google Voice app, but I had that when SMS was working properly as well, and the GV app hasn't been updated since March (meaning it shouldn't have changed how it was behaving).
Other peculiar behavior:
In addition to not being able to send texts via the messaging app, it seems that my number is also unable to receive texts. When texts are sent to my number, my phone does not receive them and they also do not show up in my Google Voice inbox. The sender is given no notice that the text has not been received. I am able to send texts from the Google Voice app, and others successfully receive them. When I send a text to myself from the Google Voice app, I receive it in my Google Voice app, but not in the stock messaging app (even though my Google Voice app settings say that texts will be received via the messaging app).
Things I've Tried (Updated: 3pm EST, 9/25/2012 ):
* Turning it off and on again
* Updating CM10
* Changing Google Voice settings (though it's possible I overlooked a setting)
* Factory Reset, Reflash ROM
* Flash Sense ROM, Update Profile/PRL
* Flash different AOSP ROM (Paranoid Android)
Things I've Not Tried (in order of how willing I am to do the things):
* Using an alternate SMS app (GoSMS, Handscent, etc)
* Un-integrating (and Re-integrating) Google Voice
* Giving the EvoLTE a relaxing bubble bath, to calm it down
* Flash Stock, Unroot, Update Radio
So, does anyone know what might cause this problem, and/or how to resolve it?
EDIT: Solution below
STORY:
I called Sprint Support, and had them reactivate my old phone (Evo4G running a CM9 alpha), by giving them the MEID for that phone. At this point I powered the phone back on, and called an activation number that they had given me (888-546-0314). On a Sense ROM, I would have simply updated my profile, instead of calling the number. We then tried SMS on the reactivated phone, and it worked (also, texts began showing up in Google Voice again at this time). I turned off my Evo 4G LTE, then I gave him the MEID for it and had him switch my number back to that phone. After he said he had switched it, I powered the Evo 4G LTE back up, and updated the profile, which I was able to do since I was still on Viper4G (note: I had to update the profile via WiFi, it might have worked over data, but it was taking longer than expected so we cancelled and just use WiFi for the update). Once the profile had updated, I called the test number again to confirm that the phone was activated. When I tried SMS, it worked as it should, including sending a copy to Google Voice.
TL;DR:
1. Find an old phone
2. Write down the MEID of both phones
3. Find a third phone to use to call Sprint (since you'll be activating/deactivating the other phones throughout the call)
4. Call Sprint Customer Support (888-211-4727), and punch the appropriate numbers until you are talking to someone
5. Have them switch your number to the old phone's MEID. Make sure the old phone is activated.
6. Have them switch your number back to the new phone's MEID. Make sure the new phone is activated.
7. Texting should be working on your new phone again.
Notes: The old phone may not be necessary. It may be enough for the Sprint Service Rep to deactivate your phone and then reactivate it. But I figured I would write out the EXACT method that solved the problem for me, since I am positive that this method has worked at least once. I have neither the means nor the desire to recreate the problem, so I will have to leave testing of other methods to the next person that experiences this problem.
Update: Clean flash of Paranoid Android did NOT resolve the issue. Still getting "Error Code 98".
So, this tells me/us this is not an issue with CM10 (which is not surprising, since I have no idea how what ROM I have flashed would keep Google Voice from receiving the texts as well).
This may sound odd but try moving the time up an hour or back an hour, error 98 is a problem with home agent, it's a sprint network error. I don't know of anything else that's helped
Try calling sprint and ask them if they can do anything. When I went s-off I had to call them bc my calls and text had errors. Data worked though.
They pushed something that fixed it in less than 10 seconds. Just wanted me to verify my account.
I tried changing the time 1 hour forward, and 1 hour backward, neither of those resolved the issue.
On hold with the Sprint tech department (it's taking longer than 10 seconds, but hopefully they figure out how to fix it.)
EDIT:
Mini-Update: Flashed Viper4G (a sense ROM), problem persists.
Updated profile and PRL while in Viper4G, problem persists.
Was told by Sprint technical support to press ##6-digit-MSL-here# and edit something, then reboot. Did that. Problem persists.
SOLUTION
The problem has been resolved, and the OP has been edited to include the method used to solve the problem.
If this was a game, Anthonicia would win for being closest (though it took closer to 2 hours on the phone with Sprint to fix the issue, if we include all four calls I made, 20-30 minutes if we only include that final one).
http://forum.xda-developers.com/showthread.php?t=2351840
I have a new (used) Samsung Galaxy S4 for Verizon running NC5 (which I bought for my gf for Christmas). I rooted it with towelroot, put in permissive mode with SE Linux mode changer, loaded SafeStrap (either 3.72 or 3.71), and then I installed Eclipse S4 TW v4.0.2 ROM (into the system slot, since the ROM slots are not working yet. Then I loaded a bunch of apps, copied stuff over from the older phone, and then got to the last step. This phone is to be used with PagePlus, which is an MVNO that runs on the Verizon network, and to get it to run with the least expensive plan I needed it flashed from 4G/3G to 3G-only.
I paid someone experienced at this flashing to do this and it worked, but it seems that something didn't work and now the messaging app cannot send pictures. At first the phone generated an error saying APN is not defined over and over and over. We tried other messaging apps, and eventually the error message went away, but nothing we tried would allow sending or receiving picture by text. Then we went into Settings -> Network Connections -> More Networks -> Mobile Networks -> Access Point Names, and found only a setting for VZWINTERNET , which has MMSC "not set" and grayed out, Port "not set" and grayed out, and at the APNs screen there is a plus sign on the top right and it is grayed out, so no new APNs can be added or configured.
So it seems this functionality is something that got snipped out as bloat from the Eclipse ROM. So in this case, unless there is some other fix or some other ROM that will provide the desired functionality (the ability to support picture messaging while flashed to 3G, with nothing else being broken), I would just like to return to the original Galaxy S4 for Verizon code (but still rooted, of course). But unfortunately, I don't have a good backup of the stock ROM image from before I installed SafeStrap.
Please have pity on this poor hapless noob and provide a clear uninstall/restore path, including links to any ROM images or other code needed. I'm totally lost here, and I'd rather not have to just junk this phone and buy a replacement.
Will this work, even if SafeStrap is installed the way that I have it?:
Settings > Accounts > Back Up and Reset > Factory Data Reset > Reset Device > Delete All/Erase Everything.
Or will that only return me to SafeStrap with Eclipse MOD? Or worse, bricked? Any thoughts?
[email protected] said:
Will this work, even if SafeStrap is installed the way that I have it?:
Settings > Accounts > Back Up and Reset > Factory Data Reset > Reset Device > Delete All/Erase Everything.
Or will that only return me to SafeStrap with Eclipse MOD? Or worse, bricked? Any thoughts?
Click to expand...
Click to collapse
Honestly, all this for picture messaging? Use hangouts to send pictures or something.
Thank you so much for the suggestion, but my gf is even more technology-impaired in regards to cell phones than me, she uses picture messaging, has a VERY low data plan, and I didn't realize that loading Eclipse MOD would break the phone (although obviously I knowingly took that chance). Anyhow, probably later this year she will be moving back to 4G (waiting for a new MVNO to take 4G) and I don't want any bug coming back to bite me on the a** later on. So I am trying to fix this now, hopefully without me having to buy a new one.
Or maybe there will be an "Uninstall Recovery" option from within the SafeStrap recovery mode, and if so that will that work? Leaving me with the original Verizon code and not a brick?
Surge1223 said:
Honestly, all this for picture messaging? Use hangouts to send pictures or something.
Click to expand...
Click to collapse
By the way, I did just try Google Hangouts because none of the messaging apps I have seen seem to be as good as the default one, which is not included in the Eclipse ROM.
But outgoing MMS messages can still not be sent, they timeout while sending, and incoming MMS messages can still not be received, although when APN/MMSC settings are defined within the app they are detected as "available for download"--except they can't then be downloaded. Hangouts says "mobile data is disabled," but it is not and I can get data on the phone--and I disabled the firewall just to be sure.
When I upgraded my M7 I restored from my TiBu due to some important old messages and I think I selected to restore app/data instead of just data and it appears to have borked my app - person calls, I get missed call notification but no indicator that a vmail was left and nothing new appears in the app.
I guess it restored back to T.5.3.4.42 which is old from M7....got the latest T.6.0.1.15 APK from @OMJ (many thanks), installed and it went thru like it was a normal upgrade from the old app but I'm still not getting either notifications or messages showing up in the app.
I was on chat with Sprint they had me update profile, reprovisioned on their end, had me check numerous settings and nothing. Asked if I'd do a factory reset and I laughed.
Any ideas are welcome.
Whatever Sprint did behind the scenes finally took. got a call, declined it, went to vmail and then all the vmail tests from yesterday and this one showed up.
Mod please close thread.
Guys - thought I had the APN settings figured out, but apparently not.
What happens is when I get a MMS (pic, vcard) type text message, it just says downloading and never comes through. However, if I reset the phone, it works temporarily, and then stops. (goes back to downloading)
I've been back on my X2 in the meantime. If anyone can share their APN settings, please do.
I know there are a ton of webpages that give the settings and I have tried several to no avail.
I use T-Mobile.
Thanks
In case anyone has the same problem - a factory reset solved the issue!