Sprint says my phone is running the wrong fw. I'm running crc1 and sprint is using crc2. Not sure if that's the problem.
I fixed it. Sprint can't be trusted to troubleshoot their way out of a first grade math class.
Had to delete data from my messenger.
Leaving this up in the event that anyone else has this problem.
Related
I rooted and installed CM7 from stock for my Sprint Hero. When ever i make a local call, the phone company has a recording that says I need to enter the area code. Never had to do this before. Any ideas???
Also, will sprint sending me an OTA or reprovision the phone cause any problems with CM7???
FYI - The phone does not say I am roaming.
Thanks!!!
diva64 said:
I rooted and installed CM7 from stock for my Sprint Hero. When ever i make a local call, the phone company has a recording that says I need to enter the area code. Never had to do this before. Any ideas???
Also, will sprint sending me an OTA or reprovision the phone cause any problems with CM7???
FYI - The phone does not say I am roaming.
Thanks!!!
Click to expand...
Click to collapse
Never heard that one. I am pretty sure that the actual phone/dialer itself (aka radio) is entirely unaffected by a ROM. My guess is something went weird in how you rooted. Could you provide more details, maybe someone will recognize a step you missed or something. Also, if you are on CM7 sprint will not be able to send you anything, since the access they need/you need to do stuff like that is integrated with the sense framework. I would say on that front, either RUU or nand back to stock if you have that and work with sprint to resolve the issue, then reroot/flash etc.
If you dial the area code does it work? I will say that ever since I have had a cell phone I've been 10 digit dialing. I'm sure a lot of things could cause that but I'm not aware of anything rom specific that would cause it. You could try flashing the rom over itself but I would think this would be more than likely something specific to your area. Someone else may have more specific answers regarding reprovisioning but anything sprint could do to your phone specifically remotely would have mostly gone away with rooting and installing a custom rom. I could be wrong on that part but they certainly lose some ability to update a phone or we'd all still be stock.
~maybe I set it too high...
I think I have a very weird problem with my unlocked AT&T Galaxy Tab. I can send and receive message using my monthly data plan SIM card from AT&T. But the problem is I cannot use this SIM card to access to internet browsing. I tried to configure APN setting following some posts here and I found elsewhere, unfortunately they all didn't work for me. I use Canada Bell I9000 modem band and not sure if this is the reason. I rooted my AT&T Galaxy to unlocked European version.
Thank you
I have the same problem I'm in the US, and I put my att sim in my unlocked international G-Tab, and at first it worked fine but after a while it stopped. But what I don't understand is I can make calls and send text messages but no data. It is rooted using superoneclick I tried fooling with the APN settings as well but nothing.
Hmm maybe this is the problem I ran into as well. I have an AT&T Galaxy Tab, and I flashed it to Overcome, and also tried DXJPE. Using either of those, after adding the Broadband APN, it would work but then the data would randomly stop working.
In order to get it working again, I'd have to do one of: (1) reselect the APN (2) toggle airplane mode or (3) reboot. It didn't always seem consistent which one of those was necessary.
I tried numerous modems and never managed to resolve the issue.
I recently have been trying to return to stock to see if that would solve the issue, but it turns out once you've flashed off of AT&T stock, as far as I can tell you can never truly go back, since we don't have working bootloaders. I've managed to get it back to mostly stock, but with corrupted bootscreens and recovery, but apparently everything working once booted, and I haven't seen these problems with the APN since then. However, the problem was so random it's hard to know if it's gone for sure.
Does this sound like the same problem?
I have two ATT note 3's, my own, which is on 4.3 and rooted, and my wife's is completely stock. Mine tried to do the OTA update but fails to complete, most likely because I'm rooted, I'm guessing. Her OTA went through and she was updated to 4.4.2. Since the update SMS appears to send out fine from the phone, but never actually does based on testing. The APN settings initially reverted back to AT&T, so after setting that back, mobile data worked fine again.
We both recently ported from AT&T to Striaght Talk and use an AT&T Microcell in our home. It has all been working well until the 4.4.2 update to her phone, that's all that changed.
I have tried quite a few different APN settings but have seen no change. Right now I am not sure if this is an Android issue or Straight Talk issue. I've done the very obvious things like rebooting the phone, I'm just unsure on what the next troubleshooting steps would be, other than contacting Straight Talk or googling these symptoms, but it's just a very broad problem to find a specific fix for.
I'm using straight talk on an at&t s6 edge. Trying to get the google voice voicemail to work. I've tried the mmi code **004*gmnumber# to activate conditional call forwarding, but I always get "couldn't get server response".. Trying to change the voicemail service provider also gives errors. "Can not read data. Network or sim error"
I have tried the individual mmi codes for different kinds of conditional call forwarding, but get same error:"couldn't get server response".
I have read that at&t controls the conditional call forwarding service, being the original carrier for straight talk, but because I don't have an active account, they can not change features for my number.
The ST rep tells me that there might be a hardware specific mmi code that Samsung may provide?
Does anyone have any solutions?
Thanks guys,
Gozirra
Gozirra, I was having a similar problem with my iPhone 6 (on AT&T) and my S6 (on Cricket). I think it may wind up being these phones (both are AT&T branded). I wound up swapping the sim card into a spare (Cricket branded) Moto G LTE and the MMI code worked without issue.
This exactly what I just did and it works. For months I have been trying to forward my Cricket voicemail to Google Voice, from Samsung S5. I couldn't. I called Cricket, they said there's nothing they can do. I then I saw gm2racer's post, used my sim card in my son's Samsung Prime. Voila.
Same issue here with S6 active + straight talk and with youmail as well.. invalid mmi.. straight talk says they dont support conditional forwarding, however 3 windows phones prior all worked on ST (both att and vzw phones)..
Frustrating enough i'm considering switching to tmobile (not willing to switch phones per say, i just got the s6)
I know this isnt the most hit thread on this topic, but today I resolved my issue... I have an AT&T (unlocked cause its older and paid for) Galaxy S6 (SM-G920A), that I simply plugged in the cricket SIM from my older Cricket phone and started using on their network. I got the immediate system text messages that reconfigured most of the call settings and the phone worked fine but in the past couple months, i keep getting complaints that i dont have voice mail set up from callers.
I did, I do, and I have used my google voice number for years now, and use it for my outbound calling (install the gv app and have it set outbound for all to GV). I also use GV as my mailbox... and I know how to use the **004 string to change forwarding (conditional, as in when you dont answer, cant answer, etc).
But with my AT&T S6 and the MM 6.0.1 (DQC1 official AT&T rom) - that 004 string wouldnt work. Neither would changing forwarding settings from the phone settings. They all state they cant talk to the server... and theres no option in my call settings for voicemail to set voice as the handler (versus your carrier).
So I was kind of stuck.. and here is what I did.
I flashed it using odin to the sm-g920aZ QB2 firmware (as in , the Cricket firmware for the S6, 6.0.1 MM version in March 2017).
I know.. it is taking a risk as some people state it doesent work.. some do.. well.. mine did. And since I have never tried to get root or do a custom OS, i am still official (thats all I have ever flashed, was official ROMs), and galaxy pay works, and the phone works, more or less perfectly from what I can tell. In fact, its got a TON less bloatware running a cricket ROM vs AT&T ROM.
And lo and behold, call forwarding works great now. And I actually got a firmware update notice from cricket 5 minutes after it was flashed.. and, well... all I can say is COOL.
I would probably stay with a MM (6.0.1) version of the ROM or match whatever you have now. I understand once you go to nougat, you cant go back to MM, and that may be true for moving between carrier ROMs also.. (cant go from Cricket 7 to at&t 6).
Anyhow.. Ive done a ton of research on this and thought since XDA helped out immensely (thanks everyone for posting roms and such), I would give ya'll a heads up that this worked for me.
I might go ahead and take those cricket firmware updates OTA. I know its a risk, as my phone is really a 920A (it shows as 920AZ now in settings also), but I really think its the exact same hardware... if I brick it I'll let ya'll know.
Confirmed, updates are good.
24br said:
I might go ahead and take those cricket firmware updates OTA. I know its a risk, as my phone is really a 920A (it shows as 920AZ now in settings also), but I really think its the exact same hardware... if I brick it I'll let ya'll know.
Click to expand...
Click to collapse
I let it go ahead and apply all of the recent Cricket updates to the S6 (920AZ) and confirmed its been running fine for 2 days now with no issues and no loss of functionality.
Makes me wonder what setting was changed by the cricket firmware - that allowed call forwarding to work properly and be set/reset/accessed by the device? The network and device didn't change, just the firmware.. but I dont see anything in the APN settings that relates to voice mail (maybe its something else that needs to change to allow CF settings?)
ANyhow.. your mileage may vary.. and Cricket firmware is WAY less bloated than AT&T for sure!
This has been a frustrating issue. My wife and I both have Nexus 6 phones. She has the 32gb & I have the 64gb version. Hers recently started not receiving MMS messages. Anything with a large picture would simply never show up. Anything with a very small graphic or group text would show up as "Non-text content". Here are the steps we've taken to solve this:
1. TMO started by insisting it was an APN issue. So she edited her APN. Didn't help.
2. We then swapped SIMs. Hmmmm. My phone then behaved like hers while hers could then send/receive MMS.
3. TMO said ok maybe it's the SIM. They sent us a new one. SAME result. Her phone wouldn't receive MMS.
4. Out of frustration, I factory reset her phone and reset the APN info. Didn't help. (Cleaned up her phone of some trash programs though. :laugh
5. TMO engineering says they still can't find anything on their end. Elevate to tech supervisor. She tells us to go a TMO store (right near us) to try a THIRD SIM. OK, we do. SAME RESULT. We tried swapping SIMs around again and the same thing happens. My SIM in her phone, everything works. Her SIM in mine, I can't receive MMS.
6. TMO store guy suggests MAYBE (but unlikely) that there is something her account has that's stored on the SIM when its activated that causes the phone to freak. Also says it's above his pay grade .
So now we are again waiting on TMO to poke around further on their end. My question for all you smart types here is:
Has anyone ever heard of this issue? Is there anything you know of that could be causing it? I think it's a bad provisioning somewhere in the dark recesses of TMO. The ONLY change we made to our plans (which seems just coincidental) is that we moved from the 2 lines Unlimited for $100 plan to the over-55 Unlimited plan. We did this maybe 3 weeks ago. But the features are all the same on both plans.
We are both on the same Android 7.0 final OTA firmware updates from Google. NBD92G
Would there be ANY chance that a sideload firmware update would make any difference? We're getting desperate here. Any & all suggestions welcome.
I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case
Don't use old firmware... I had issues on certain custom ROMs and old firmware where MMS wouldn't work over WiFi. Never as bad as you were getting.
If you wanna stay stock, sideload the latest OTA to go to NGI55D. Anything older than that is vulnerable to Blueborne exploit, which is a HUGE security concern IMO. I can confirm MMS is working correctly (even with WiFi enabled) on bone stock NGI55D as well as custom ROM Dirty Unicorns v11.7.1 which includes September security patch.
ktmom said:
I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case
Click to expand...
Click to collapse
I've had this issue on most LOS roms. i ended up making a custom APN i flash when i try a rom built on LOS.
Yeah, it sure sounds like a problem with account partitioning, or something else with the account that gets associated with the SIM on initial use. What if you try the problem SIM in a phone that is not a Nexus 6? I wonder if you could get a new sim and set it up in a different phone, then transfer it to the problem phone?
OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.
RealSkier said:
OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.
Click to expand...
Click to collapse
Glad they figured this out.