Related
Something really weird is going on with my At&t galaxy s3. I'm new to this forum so I'll just explain what I'm experiencing and do my best to work through it will all of you. This phone got rooted by someone else and when I got it, the rooted program was in chinese and was acting all weird and wasn't getting good reception, although it was before it was rooted. I flashed it back to normal and it's acting very curious. It will receive an At&t simcard but the service bars will go from 1 bar to 4g to Edge to 1 bar all in a matter of 20 seconds or so and doesn't seem to work. It will occasionally work to send messages, make calls, but it seems like it can't ever receive calls. I checked and the IMEI number is still the same. Also, I had originally tried to unlock it to another carrier and when I put in different simcards (From other carriers such as verizon) the service bars don't show up, instead, all it shows is a cancel sign and doesn't ask for an activation code or anything. I'm honestly not sure what to do here, I thought I had broken the simcard reader and replaced that, but that made no difference. I'd greatly appreciate any help. Thanks!
StookDog said:
Something really weird is going on with my At&t galaxy s3. I'm new to this forum so I'll just explain what I'm experiencing and do my best to work through it will all of you. This phone got rooted by someone else and when I got it, the rooted program was in chinese and was acting all weird and wasn't getting good reception, although it was before it was rooted. I flashed it back to normal and it's acting very curious. It will receive an At&t simcard but the service bars will go from 1 bar to 4g to Edge to 1 bar all in a matter of 20 seconds or so and doesn't seem to work. It will occasionally work to send messages, make calls, but it seems like it can't ever receive calls. I checked and the IMEI number is still the same. Also, I had originally tried to unlock it to another carrier and when I put in different simcards (From other carriers such as verizon) the service bars don't show up, instead, all it shows is a cancel sign and doesn't ask for an activation code or anything. I'm honestly not sure what to do here, I thought I had broken the simcard reader and replaced that, but that made no difference. I'd greatly appreciate any help. Thanks!
Click to expand...
Click to collapse
Unlock is supposed to be permanent so it's odd that you lost it.
Now as for your problem, a lot of people are getting this issue lately, where unlocking damages their nv file. The solution can be found here: http://forum.xda-developers.com/showpost.php?p=43842387
BWolf56 said:
Unlock is supposed to be permanent so it's odd that you lost it.
Now as for your problem, a lot of people are getting this issue lately, where unlocking damages their nv file. The solution can be found here: http://forum.xda-developers.com/showpost.php?p=43842387
Click to expand...
Click to collapse
Thanks for your quick response I have been looking for a long time and never saw this issue before. I'm not sure where I'll be able to find a replacement nv file...but i'll see if anyone I know has a galaxy s3 from at&t. Maybe once I do this the unlock issue won't be messed up anymore.
Hey folks,
I bought an S7 Active from eBay and I'm using it in Ireland. Everything is working fine that I need, but my carrier recently introduced WiFi Calling and upon trying to set it up from the setting menu where it reads
"wifi calling lets you make and receive calls over wifi with your at&t accoumt. when you use wifi calling, information about the country where the wifi connection is made will be sent to your carrier. Learn more about wifi calling (link).
GET STARTED"
I get the following error:
"Wifi Calling activation not successful, try again later"
I rang support for my carrier and they think it's something to do with the handset. They support the S7 and the S7 Edge but as the S7 Active is an AT&T exclusive and appears to have custom AT&T software, it seems like it might be trying to connect to AT&T and it can't?
Also, when I check for software updates, it says AT&T Software Update at the top of the screen, now this doesn't give any errors and it says software up to date, so I'm not sure if this is correct or if there's new software out that it can't connect to update?
Is there any way around this? I know maybe it's possible to ROOT and install a new ROM, but I'd rather avoid that hassle..
Any feedback would be great
I am in the same situation. S7 Active unlocked from EBAY, and using it in Czech Republic with Vodafone sim. Is here chance to get OTA Nougat update?
I'm using one in Canada and flashed the updates described in another thread in this phone's forum. They will reset your phone to factory, but you will have 7.0 nougat and security patches into April, 2017. I doubt any kind of OTA will be forthcoming unless you have an ATT SIM, but I'm not an expert in this at all. I plan on keeping good backups and flashing the updates as they become available. Aside from that, it's a great phone. If they make the s8 active global, then I'll look into getting one some time down the road.
Thanks for the replies. Does the S8 have an active version? I hadn't heard anything on it yet?
so when you flash nougat 7, does it completely wipe and install a new ROM on your phone, or it just updates the AT&T rom, so even with the update, you're still bound to the AT&T settings for updates/wifi calling etc?
Yes, it wipes out the phone completely, you'll have to set it up again. Everything else is same, such as AT&T bloats, wifi calling etc.
Ok thanks for letting me know. So no point I guess if it doesn't solve the issue
I live in Czech Republic. In situation, when I will buy prepaid sim card from AT T, and I will use it in my unlocked S7 Active, it is possible to get OTA Nougat update?
That's not a bad idea, would possibly work for the OTA update, but maybe not if it's not actually connected to AT&T?
It wouldn't work for the wifi calling though I'm sure?
faronium said:
I'm using one in Canada and flashed the updates described in another thread in this phone's forum. They will reset your phone to factory, but you will have 7.0 nougat and security patches into April, 2017. I doubt any kind of OTA will be forthcoming unless you have an ATT SIM, but I'm not an expert in this at all. I plan on keeping good backups and flashing the updates as they become available. Aside from that, it's a great phone. If they make the s8 active global, then I'll look into getting one some time down the road.
Click to expand...
Click to collapse
I'm in Edmonton AB, Yes, there will be nothing for updates or WiFi calling if you are not on the ATT network with their SIM.
Which ROM did you update to, the QD4, or past it?
Keep it rolling
I'd love to know more about using the S7 Active internationally from anyone who has been down that road already. In the UK and considering getting one from Ebay but I would immediately want to update it to Nougat and I'm unsure if this will be possible? I have a Mac laptop in the house and would hope to use that to apply any upgrades. Really appreciate any info you guys have!
mmmbient said:
I'd love to know more about using the S7 Active internationally from anyone who has been down that road already. In the UK and considering getting one from Ebay but I would immediately want to update it to Nougat and I'm unsure if this will be possible? I have a Mac laptop in the house and would hope to use that to apply any upgrades. Really appreciate any info you guys have!
Click to expand...
Click to collapse
ODIN is only available for Windows (Vista/7/8/10). You will have to run Wine for just the Odin program or Boot Camp for the full Windows OS in a partition.
Wine is the easiest solution, start there and install the program, USB drivers.
UnableToResetOldProfile said:
ODIN is only available for Windows (Vista/7/8/10). You will have to run Wine for just the Odin program or Boot Camp for the full Windows OS in a partition.
Wine is the easiest solution, start there and install the program, USB drivers.
Click to expand...
Click to collapse
I to am in the UK and purchased a S7 Active from Ebay. The phone came in a sealed box and worked fine. No AT&T logo at startup or bloatware. However when I rebooted the phone after switching of, an integrity error came up which forced me to wipe/erase the phone. I thought maybe a first time glitch but it did it again and all was lost. Had my old S4 Active so persevered and read info on this post to reflash firmware to QB2 using ODIN. Now note this is the first time i have ever attempted anything like this so complete newbie. However all went well and I now have a phone on Nougat. It reboots without error now. But it is now back to AT&T with logo at Startup and US voice for google navigation etc... Google pay now does work though. I am pleased with my results but would love to have firmware that makes it non AT&T specific for use in the UK, any ideas would be greatly appreciated.
Hello all,
I was warned of an impending "update" a few nights ago. Since it hit, my mobile hotspot no longer works.
Does anyone else have an S7 Active on Red Pocket who has a working hotspot? If so, could you share the APN settings you are using, and the Android version you are on?
I think they rolled me back to January 2018. G891AUCU2BRB5
Would rather not factory reset or root, but getting very close to doing so. Neither RP or AT&T are helpful here.
Thank you,
Bob
Red Pocket Mobile Hotspot problem solved - stock Oreo 8.0 fixed it
Well, for anyone who might encounter this, I finally resolved it.
Pulled the SIM card and did a factory reset. Then it recognized the Oreo update over Wifi. Had to load an intermediate update first.
I put it Red Pocket's AP settings.
First time I tried Mobile Hotspot, it still didn't work.
Restarted the phone.
Still didn't work.
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
After ten hours of wading through poor advice, I'm back to where I was four days ago.
With one exception: I learned how to turn on Developer Mode (tap Build Number 7 times in Software Info)
AND SHUT OFF THE AUTOMATIC UPDATES UNDER DEVELOPER MODE SO IT WON'T HAPPEN AGAIN!!!
I have a stock S7 Active/G891A that I bought unlocked on eBay in March of 2018. It's currently running Oreo 8.0.0, build G891AUCS4CSA3. I just now disabled OTA updates thanks to you.
I've been trying to get Mobile Hotspot to work on this phone ever since I switched Consumer Cellular several months ago. Whenever I tried to enable hotspotting the phone screen would display a popup:
Please wait while verifying
Which was a normal message on the AT&T network, but now (using AT&T's network through Consumer Cellular), after 5-10 seconds a different window would appear:
Tethering/Mobile AP is unavailable.
A network issue may be preventing use of your Mobile Hotspot. Please call Customer Care at 611.
[excessive hard-coded line breaks omitted]
Over the course of several weeks in January I literally spent hours on the phone with several Consumer Cellular 1st and 2nd tier support techs trying to get past that error. Tier 2 support gave me new APN settings, had me do a network reset, and suggested that I do a factory reset. Which I did later, but that didn't work, either. Then CC tier 2 support gave up and bumped my ticket to tier 3. Tier 3 support then transmitted their version of an APN definition to my phone, but still no love. At the end of the 2nd week of phone tag, a Tier 2 tech told me that "it <Mobile Hotspot> just doesn't work with some phones not sold by us".
Maybe hotspotting won't work with my old Motorola Razor, but I was pretty sure that I'd eventually strike gold with my trusty G891A.
Because my S7 Active has version 4 of the boot loader (thank you, latest and final OTA), I haven't been able to find anything that resembles a working root. I even paid OneClickRoot to do it via remote desktop session, hoping that they had some good mojo that I hadn't yet discovered. But their support tech hit a wall, too, and ended up flashing my phone back to stock Oreo 8.0.0. They also refunded my purchase almost immediately which made me sort of happy but still sad that I had no Hotspot abilities.
While searching for possible workarounds (ROMS, root, mystical incantations) tonight I came across your posts:
bobcpdx said:
[snip]
Then I remembered one rep saying to switch MVNO type to "IMSI".
[snip]
Click to expand...
Click to collapse
So I followed your tip. I created a new APN definition and copied in all of the values from the CC Tier 3 definition . I then set Mobile virtual network operator type to imsi . This value was set to None in all in all of the other APN definitions on my phone.
I didn't even need to reboot the phone. I selected my new APN definition and enabled Mobile Hotspot. The first message about verifying came up. But then the phone didn't direct me to dial 611. Mobile Hotspot simply started working.
Thanks every so much for sharing this insight.
bobcpdx said:
Well, for anyone who might encounter this, I finally resolved it.
…..
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
….
Click to expand...
Click to collapse
WOW! Thanks so much for posting this. I've been struggling for a couple of months to find a way to hotspot my two unlocked LG's (G6 and a G7) on Cricket and Consumer Cellular. This trick enabled hotspot/tether quickly and easily.
My apologies to Cricket and CC, for my unflattering thoughts about them. I assumed it was their issue! Not sure why these unlocked LG's are fidgety like this. We got a Moto X4 (Android One flavor) in the family, and it can hotspot with no tweaking.
BTW - I have a similar issue with call forwarding on the LG's. Can't enable it, get an error. But the Moto X4 has no problem on either of these AT&T MVNO's. Anyone have an easy answer for that? Thanks.
This doesn't answer the call forwarding question. I'm not sure who pushes OTA updates, but soon after my last post I got a notification that an my phone needed to be rebooted for an update to finish. This was after I (at least thought that I had) disabled automatic updates. After the update the hotspot feature no longer worked. I checked APN settings and found that the update had reset the APN MVNO type to NONE . I manually changed it back to imsi and it's been working ever since. I also made sure (twice with reboot in between) that automatic OTA Updates are disabled.
Although enabling/disabling these features seems to be problematic with AT&T MVNOs, what I find more curious is that techs at Consumer Cellular claim not to know how to fix them. Maybe that's true, or maybe that's what they are told to say.
Was it coincidence that I received an OTA update within days of making this change, or is the Big Brother with the Blue Death Star logo watching us so closely?
Hello, I'm desperately seeking help to remedy this issue I'm having. I have unlocked Note 10+ on T-Mobile Network and ever since I got the device I been getting this "Network Error" pop up message dead on center of the screen.
It happens very randomly regardless of which app I'm using, on both wifi and mobile data. The error message pops up very briefly and disappears. Luckily it hasn't stopped me from doing daily tasks but it's extremely annoying.
These are things that I have already tried;
Factory reset, Network reset, brand new simcard, clear cache, returned the device for brand new replacement, uninstalled all 3rd party apps.
Nothing seems to help, I still get error message intermittently...
I'm out of ideas and clueless on how to go about it.
Anyone else on unlocked Note 10+ with T-Mobile experiencing same issue?
as you have tried everything else, maybe try with tm firmware or maybe contact tm tech support in case they can push some config settings
raul6 said:
as you have tried everything else, maybe try with tm firmware or maybe contact tm tech support in case they can push some config settings
Click to expand...
Click to collapse
Thanks for your input. When I contacted tm, they told me since it's unlocked they can't do much about it....
If I flash to tm firmware would it cause an issue when I return the device to Samsung for Samsung upgrade?
zen0s said:
When I contacted tm, they told me since it's unlocked they can't do much about it....
Click to expand...
Click to collapse
That wasn't nice on part of tm, I also have U1 N10+ and I've never had problems switching sims for different networks. Have you tried using other provider's sim? Some tm secondary mvnos, I know to work well on my phone, will send you a free 1 month sim to try. I'm not going to spell its name(to avoid xda-free advertisement) but I'm very happy with its services(and super low prices)
What apps are you using? And have you disabled anything? You say you factory reset it, but did you start to install something again? And it happening with a 2nd device is odd
Has anyone else experienced the same problem? Is there any way to get them to reactivate it?
I had an an XT1955-5 that was fully functional on the AT&T network, including voice over LTE. I bought this phone because XT1955-5 was on their list of approved phones. I even checked the sim status to verify that it didn't kick down to 3g/H+ when I made a call, and it had the HD symbol on the call screen.
Despite this, AT&T disabled it because they were shutting down the 3g network. I got them to reactivate it and it worked again for several months. Then, when they sent me the cheap replacement phone and sim card, they deactivated my old phone and I couldn't get it to work again. I tried calling them and talking to their technical support to explain the situation that VoLTE was fully functional on it. They didn't seem to know much other than "the computer says this phone isn't compatible." They said they would try changing my provisions, but they ended up making it much worse so mobile data wouldn't even work anymore.
Do they just go by an IMEI whitelist that can't be overridden? My best guess is that they seem to be shutting down all phones that weren't AT&T branded, so this one gets the axe because it was unlocked from another carrier. This is very disappointing because I really liked this phone for a combination of several factors that I can't seem to find in any others.
Unless I'm misreading the list, this is a whitelisted device on the AT&T network.
Correct, the model number is on their whitelist. That's why I chose this phone and why it's so frustrating that it was deactivated. I guess there's a subset of whitelisted IMEIs within that list, but isn't published. This particular one must not have been on their whitelisted IMEI list because it was unlocked from a nother carrier. Do you know if there's any way to get ATT to add it of am I SOL?
They say nothing about IMEI number limitations.
As long as it's not blacklisted there shouldn't be an issue. This list was just revised so your phone may not have been previously whitelisted.
There's quit a bit of confusion is what I gathered.
Some of the AT&T features like vid calling won't work without the AT&T software maybe firmware. Guess we'll both find out on the 22nd.
Call AT&T advance tech support as this is the game that moves as you play it.
I have a development:
I flashed back to stock/RetUS ROM from LineageOS 18.1 to try to fix wifi calling on T-Mobile since I was trying to switch to them due to this hassle. While I was at it, I read a post on a forum for another phone, where the person said they reflashed stock to reprovision the sim. I figured it's worth a try, so I popped in my AT&T sim card while on stock ROM and to my surprise, it fixed it. The LTE network is fully functional, at least for now. I didn't think Lineage did anything to change the radio firmware or whatever it is that controls how it interacts with the cell carrier. I guess I was wrong.
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
MotoMan1955-5 said:
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
Click to expand...
Click to collapse
AT&T isn't witch hunting. As long as it's firmware is compatible with their protocols it will work.
I have no clue what those protocols are though.
(deleted, mistook carrier)
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
MotoMan1955-5 said:
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
Click to expand...
Click to collapse
If these apply to you try:
Clear system cache
Clear Sim Toolkit data
Reset network setting
Get a new sim card from AT&T, handle like a stick of ram as they can be damaged by ESD.
From what is described, it does sound like a provisioning issue, and calling to get it fixed would probably be the correct solution. But why is it flagged as incompatible? Why would that status be persistent for that line? It's weird.
FWIW, AT&T kicked me off for switching from a OnePlus 6 (not a 5g phone) to a OnePlus N10 (5G phone). They were nice enough to disable my account on a Friday night when I switched sims, and was without cell service all weekend since they apparently don't want to do customer service outside banker's hours. Couldn't use the old one either (on 4G), I was completely blacklisted.
T-Mobile happily accepted my porting on Monday .
I'll save my unkind thoughts past "maybe consider firing them" as I don't want to sound like a loonie.
Man, I wish I could switch. I actually tried switching to a T-Mobile MVNO. They provisioned my SIM correctly, but unfortunately their coverage was insufficient in my rural area. I considered sticking with them and using wifi calling at home if that would work, but that feature was broken on lineage and I thought I got this to work correctly with AT&T.
I did get it working by flashing stock again, calling ATT to have them correctly provision it, then flashing LineageOS again. It has been working properly for about a week so with any luck I'll get to continue using the phone.
The 22nd came and went. I'm noticing some vids pause occasionally. May be just a random glitch otherwise no change. I may eventually try a network reset and have AT&T do it on their end.
Long live 4G LTE