Won't detect OTA update (ATT) - Samsung Galaxy S10+ Questions & Answers

My S10+ will not detect the day one OTA update. I check every day and it says software up to date even thought its still on G975USQU1ASAT. AT&T says to contact Samsung and Samsung says to contact AT&T. Anyone else had this problem or have any idea how to fix it? I've already tried factory reset, clearing cache and data on the updater apps with no luck.

Do you need to be connected to WiFi or have a certain battery level? Try charging to 100% and connecting to WiFi then manually search for the update.

What I had to do is go into the date and time and shut off auto time update and manually set it 2 days a head then mine found the update.

loffer said:
My S10+ will not detect the day one OTA update. I check every day and it says software up to date even thought its still on G975USQU1ASAT. AT&T says to contact Samsung and Samsung says to contact AT&T. Anyone else had this problem or have any idea how to fix it? I've already tried factory reset, clearing cache and data on the updater apps with no luck.
Click to expand...
Click to collapse
Two options:
1) Borrow someone else's sim or ask At&t for another
2) Download the S10+ OTA and update via SD

Did you put the sim that came with it in? I used my old sim and had the same problem till I changed the sim card.

Sorry for the late response and thanks for the suggestions. Just returned from vacation so I will try the suggestions. Also yes I used the sim they sent me. I suspect something got messed up in the sim provisioning as I came in as a new line then ported my number in. I will try putting my wife's sim in and report back. Thanks again!

Mine wouldn't detect an update. I'm only using mine on wifi as this one is just a spare phone for now.
To get the update though I needed to put in my att dim and put the date a week in the future. That's the only way I was able to actually get it to check the server.

I'm having the same exact problem. I purchased my S10+ directly from Samsung, but it was the AT&T model. I've been stuck on the ASAT baseband with the Feb 1 Security patch since day 1. I've been on the phone/chat with AT&T for the last 3 days. Each time they've promised that they have pushed the update to my phone, and every time I check, I get the "Software is up to date" message. I just tried setting the date to next week, restarted, and checked for the update..still nothing.
The same thing happened to me with my Note 8, but I was able to get around it using ODIN. I've told AT&T that I'm not paying my bill until this is resolved (like that's gonna do anything). Anyway, I'm at the breaking point on this, and not getting anywhere fast.

Related

Galaxy Note 3 won't activate to my phone number??

Hey all, I just got my GN3, still am using the GN2 though BC Verizon can't get the phone to activate to my phone number? Actually Verizon says it show the GN3 activated, but l have no service/phone/data/anything at all. They tried 5 different GN3's and 13 different SIM cards before they gave up trying to activate. My number works/activates just fine on my GN2. So they gave me a temporary number yesterday to see if it was a problem with my particular phone number and sure enough, my GN3 activated on the temp number. When I switched back to my reg # it wouldn't connect...again. Then I went to work which was about 10 miles away and the GN3 activated on my reg#. I called my wife, made a few texts, surfed the net, etc... for about 2 hours, when I got about 8 miles from home, I lost all connection again... What gives here? It's the weirdest problem I've ever seen. I'm home now, and tried activating it again with no luck. Any thoughts??
I'm sorry if this is the wrong forum for this thread, if so please move??
Mine wouldn't activate for the first 20-30 minutes or so. I removed the sim card, reinstalled then went on the website and updated the Note 3 in formation for my line. Had keep refreshing my lines info on the Web page about 2 more times and hit accept before it Finally activated. Took about 5 additional minutes after removing the sim. Not sure if that will help, but hope you get it working.
Sent from my SM-N900V using XDA Premium 4 mobile app
chino0131 said:
Mine wouldn't activate for the first 20-30 minutes or so. I removed the sim card, reinstalled then went on the website and updated the Note 3 in formation for my line. Had keep refreshing my lines info on the Web page about 2 more times and hit accept before it Finally activated. Took about 5 additional minutes after removing the sim. Not sure if that will help, but hope you get it working.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well seeing as how I got mine on 10OCT2013 at 10 am and it still hasn't activated, I think it's not going to at this point. I may sadly have to go back to my GN2 and return the GN3 altogehter. :crying:
Mine seemed stuck on activation, ended up using my old sim card, activated almost instantly.
Update: just got off phone with Big Red and they said that for some reason when I'm on my "home" towers, my activation has trouble letting go of the GN2?? Maybe it really is hard to say good-bye...
They are working on it now...
I've always had an issue activating my old number on a new phone with a new SIM.... I've always just switched my old SIM card in and it's worked perfectly lol
Make sure the SIM card has been linked correctly to your phone number. The easiest way is to look on the VZW paperwork that came with the phone and make sure it's your phone nbr and not another person's on your plan.
I am having more or less the same issue.
To make a long story short, whenever I leave the "home" cell tower that the phone was activated on, it will not connect to any kind of network whatsoever. It just shows a circle with a line through it, and at the same time it reboots itself, randomly and frequently, even when it isn't being touched. All of these problems go away as soon as I get back home to that cell tower. I wonder if the original poster activated his phone at work the first time, and that's why it only works when he returns to work?
I have tried 3 different SIMS to fix this: the one that came in the GN3, the one from my old Galaxy Nexus, and a brand new one from a Verizon store. I have done half a dozen factory data restores.
My next step is to try an in-store swap. A local store around here first refused to hold a phone for me to swap, then when I got there (or rather when a family member got there), we were told that there was a master ticket for this issue and there was a freeze on doing any exchanges until Samsung released a "fix". My subsequent conversations with Verizon tech support have confirmed that the whole story about a master ticket and not doing exchanges was a complete lie. The stores are actually required to uphold the 14 day worry free guarantee no matter what. Obviously this store didn't want to give up a phone to me that they could sell to someone else. They weren't just being unhelpful, they were running interference on resolving my problem for their own greed.
I had an activation problem in store yesterday when swapping my note 2 for note 3. The sales rep entered the sim card info that was on the sticker on the box for the sim card that comes with the phone.
It all ended up causing major activation / service connectivity issues because the sim card info on the box did Not match the actual sim card number for the sim pre-installed on the phone.
This is apparently an issues for some other people as well. If the sim card in the phone is not reconciled with the info on the box prior to entering the info into Verizon's system.... You will be in for a time consuming headache
Sent from my SM-N900V using xda app-developers app
urielsynthesis said:
I am having more or less the same issue.
To make a long story short, whenever I leave the "home" cell tower that the phone was activated on, it will not connect to any kind of network whatsoever. It just shows a circle with a line through it, and at the same time it reboots itself, randomly and frequently, even when it isn't being touched. All of these problems go away as soon as I get back home to that cell tower. I wonder if the original poster activated his phone at work the first time, and that's why it only works when he returns to work?
I have tried 3 different SIMS to fix this: the one that came in the GN3, the one from my old Galaxy Nexus, and a brand new one from a Verizon store. I have done half a dozen factory data restores.
My next step is to try an in-store swap. A local store around here first refused to hold a phone for me to swap, then when I got there (or rather when a family member got there), we were told that there was a master ticket for this issue and there was a freeze on doing any exchanges until Samsung released a "fix". My subsequent conversations with Verizon tech support have confirmed that the whole story about a master ticket and not doing exchanges was a complete lie. The stores are actually required to uphold the 14 day worry free guarantee no matter what. Obviously this store didn't want to give up a phone to me that they could sell to someone else. They weren't just being unhelpful, they were running interference on resolving my problem for their own greed.
Click to expand...
Click to collapse
Switching your device or SIM will not work. I have now gone through 6 GN3's and almost 20 different SIM cards. It's the towers/service from Verizon. They have noted that this is a problem and are working diligently to fix it...lol Meanwhile, I've returned my GN3 and will wait until they fix this disaster. This rollout is almost as bad as Obamacare...haha
dead batteries said:
Hey all, I just got my GN3, still am using the GN2 though BC Verizon can't get the phone to activate to my phone number? Actually Verizon says it show the GN3 activated, but l have no service/phone/data/anything at all. They tried 5 different GN3's and 13 different SIM cards before they gave up trying to activate. My number works/activates just fine on my GN2. So they gave me a temporary number yesterday to see if it was a problem with my particular phone number and sure enough, my GN3 activated on the temp number. When I switched back to my reg # it wouldn't connect...again. Then I went to work which was about 10 miles away and the GN3 activated on my reg#. I called my wife, made a few texts, surfed the net, etc... for about 2 hours, when I got about 8 miles from home, I lost all connection again... What gives here? It's the weirdest problem I've ever seen. I'm home now, and tried activating it again with no luck. Any thoughts??
I'm sorry if this is the wrong forum for this thread, if so please move??
Click to expand...
Click to collapse
Mine kept trying to activate on the phone and would continually fail.
I thought I had a faulty device and was going to go to the store. Something told me to login to MyVerizon online on my computer [since I kept my old phone off as directed via the on-screen instructions] and poke around and see if there was anything there that might be able to help me.
I clicked on my line, and the Manage My Device link on the left hand side of the screen and ended up being able to complete the activation via the website. Re-booted the phone, and then voila~! Activation complete.
FYI, I was migrating from an iPhone 5 to the GN3.
nimitch said:
Mine kept trying to activate on the phone and would continually fail.
I thought I had a faulty device and was going to go to the store. Something told me to login to MyVerizon online on my computer [since I kept my old phone off as directed via the on-screen instructions] and poke around and see if there was anything there that might be able to help me.
I clicked on my line, and the Manage My Device link on the left hand side of the screen and ended up being able to complete the activation via the website. Re-booted the phone, and then voila~! Activation complete.
FYI, I was migrating from an iPhone 5 to the GN3.
Click to expand...
Click to collapse
Yeah I tried that as well. I'm not sure there is anything I haven't tried. I've returned my device and decided to stick with my Note 2. Maybe when Verizon gets their heads on right and fixes this, I'll come back.

[Q] updated to 4.3, now Sprint ID wont leave me alone

Hello all, my family all just got new phones. Both my mom and dad got the S4. I activated my dad's phone with no problems and everything is running great. It did not get the OTA update so it is still on 4.2.2. My mom's phone on the other hand has some issues. Right after activating and running initial stuff, I got the OTA update message, and decided to update that phone. it downloaded, rebooted, installed, and rebooted again. It seemed everything went fine.
Upon further setting up her phone, I noticed that there would be a notification about Sprint ID downloading a "Default ID" pack, and it trying to install it. But it would fail every time. Any changes to the internet connection (going from 3g to wifi or vice versa) would trigger Sprint ID to start up over again and download and fail to install. This kind of gets annoying after a while. Since my mom's phone is not rooted, I can not freeze or uninstall the Sprint ID apk. Force closing it does not help, because it starts up again when changing internet. I spent a good 30 minutes with the Sprint Chat online with no help. Even factory resetting does not fix the problem. Sprint could not help, and forwarded me to a Samsung chat person online. After 20 minutes with that person, they said that they went through all troubleshooting steps and could not help and asked me to call their hotline (which is open on Monday).
The odd thing is, according to Sprint's website, Sprint ID isn't supported on the S4, and my dad's S4 with 4.2.2 does not have it. could the 4.3 update have accidentally added Sprint ID? Is there any way to remove Sprint ID without root? Or root with 4.3, and somehow flash back to stock 4.2.2 without messing with knox? I can try going to the Sprint store tomorrow and see if they can do anything, but I would rather try alternatives first.
on the phone that's already taken the 4.3 update you cannot go back to stock 4.2.
You can however root. Then install titanium and freeze the 'sprint installer' and sprint id applications.
Just wait 'till tomorrow do not take any risks because it's your mother's phone and she wont need root. Service will flash a rom to it hope it will fix it. Have a good day
Sent from my E-Tab10 using xda app-developers app
Yes, take it to Sprint and have them fix it. You did nothing wrong so it shouldn't be upu problem.
Sent from my SPH-L720 using Tapatalk
So I went to the Sprint store today, to see if I can get my mom's phone fixed. According to the technician, there is nothing they can do until Sprint pushes an update to fix this problem. The technician tried fixing a previous customers phone with the same problem, and came to this conclusion. He even said switching out the phone wont help because eventually the 4.3 update will push to that one and might glitch like this phone. I guess I will hold back on updating my dad's phone when he gets his OTA.
I have temporarily fixed the notification by turning off notifications for Sprint ID, so it wont keep on popping up, but I do not know if it will try to download in the background or not.
I heard Sprint was going to push an update to fix the Knox notification showing up when switching to wifi on the S4 and Note 3, and hope they might attach a fix to this in the update.
chaosacolyte said:
So I went to the Sprint store today, to see if I can get my mom's phone fixed. According to the technician, there is nothing they can do until Sprint pushes an update to fix this problem. The technician tried fixing a previous customers phone with the same problem, and came to this conclusion. He even said switching out the phone wont help because eventually the 4.3 update will push to that one and might glitch like this phone. I guess I will hold back on updating my dad's phone when he gets his OTA.
I have temporarily fixed the notification by turning off notifications for Sprint ID, so it wont keep on popping up, but I do not know if it will try to download in the background or not.
I heard Sprint was going to push an update to fix the Knox notification showing up when switching to wifi on the S4 and Note 3, and hope they might attach a fix to this in the update.
Click to expand...
Click to collapse
Thanks for the update! the auto install of the Sprint ID on my gf phone was driving me crazy..
chaosacolyte said:
Hello all, my family all just got new phones. Both my mom and dad got the S4. I activated my dad's phone with no problems and everything is running great. It did not get the OTA update so it is still on 4.2.2. My mom's phone on the other hand has some issues. Right after activating and running initial stuff, I got the OTA update message, and decided to update that phone. it downloaded, rebooted, installed, and rebooted again. It seemed everything went fine.
Upon further setting up her phone, I noticed that there would be a notification about Sprint ID downloading a "Default ID" pack, and it trying to install it. But it would fail every time. Any changes to the internet connection (going from 3g to wifi or vice versa) would trigger Sprint ID to start up over again and download and fail to install. This kind of gets annoying after a while. Since my mom's phone is not rooted, I can not freeze or uninstall the Sprint ID apk. Force closing it does not help, because it starts up again when changing internet. I spent a good 30 minutes with the Sprint Chat online with no help. Even factory resetting does not fix the problem. Sprint could not help, and forwarded me to a Samsung chat person online. After 20 minutes with that person, they said that they went through all troubleshooting steps and could not help and asked me to call their hotline (which is open on Monday).
The odd thing is, according to Sprint's website, Sprint ID isn't supported on the S4, and my dad's S4 with 4.2.2 does not have it. could the 4.3 update have accidentally added Sprint ID? Is there any way to remove Sprint ID without root? Or root with 4.3, and somehow flash back to stock 4.2.2 without messing with knox? I can try going to the Sprint store tomorrow and see if they can do anything, but I would rather try alternatives first.
Click to expand...
Click to collapse
I just received a replacement phone that is having the same issue, and it's on 4.2.2 - has not received ota update notice. In addition, the CF Root Procedure which seems to work for most everyone is not rooting my phone.

[Q] S4 - disconnecting from network and not reconnecting again

Hi all,
Regular reader but hardly ever post!
I have a Galaxy S4 (GT-I9505) - with Android 4.4.2. Unrooted.
Purchased and used in Singapore on the Starhub network since around October 2013. Everything was working fine until approx Feb or March when the latest Android version, 4.4.2 got rolled out.
Ever since then I am experiencing regular disconnections from the network. But the phone does not re-connect back to the network again, the only fix is to restart the phone.
These disconnections are often once or twice a day, and are very frustrating because if I don't notice it, I may be off the network for hours before noticing it - and are therefore missing out on calls emails etc etc.
This only happened after the Android 4.4.2 got rolled out, so I am pretty confident this is the cause of the problem.
What I tried myself to fix:
- restore APN's back to default state
- Factory reset (both via settings, and via boot screen)
What I have been able to narrow down troubleshooting, is:
- Disconnects seem to only happen when Network Mode is "LTE/WCDMA/GSM (auto connect)"
- If I use network mode "WCDMA/GSM (auto connect)" the disconnections have not happened (yet!)
- When the disconnection does happen in the first mode, I cannot manually change the network mode. The radio buttons are greyed out, and if I try to select "WCDMA/GSM auto connect" the request times out (I forget the exact message - it does respond to the tap but then nothing happens)
So it seems to me this is some sort of software bug/fault introduced with Android 4.4.2 that affects 4G connections.
After that, I have taken it to Samsung for warranty service. I have now had 4 visits to them and they have not been able to fix it yet. This is what they have done so far:
- First visit - factory reset (despite telling them I already did that) - did not fix
- Second visit - checked hardware and replaced mainboard. Did not fix.
- Third visit - checked hardware again and factory reset again. Did not fix.
- Fourth visit - who knows. I think same as visit three but done via a Service Manager instead of staff, Did not fix.
When I first called them back in Feb or March, they said it was a "known Issue' and sugegsted to "wait for a patch". However since visiting them, they said the known issue was only with Note 3's (not with S4's) and replacing the mainboard on the Note 3's fixed the problem. In my case replacing the mainboard - twice - has not fixed it.
I'm getting very annoyed with Samsung who seem to just be trying the same thing each time and are not fixing it. Staying in 3G only mode is a workaround but not an acceptable solution.
Now they've asked me to take if back again - for a 5th time.
Beginning to wish I had never bought the S4, or at least never got Android 4.4.2.
So I thought I would turn to here for help instead, I think you guys and gals probably know more than the Samsung service staff!
Any suggestions?
By the way, I don't run any memory/battery saver apps. I do run one data usage monitoring app that I thought perhaps was conflicting, so I tried not installing it after one of the resets, but the problem continued.
Chikara71 said:
Any suggestions?
Click to expand...
Click to collapse
you CAN try other modem flash, but be careful with your warranty.
I do not know about the warranty conditions in your country, but in EU normally 3 unsuccessful repairs = phone refund or replacement.
I would try reflashing stock file or just flash a different modem
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Dial *#1234# and paste here what appears.
Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUFNBE
CP: I9505XXUFNBE
CSC: I9505OLBFNB3
I should add, I took it in *again* to Samsung, to the Service Manager. Said they would replace the antenna and try that, which they did.
Still have the same problem though.
Not sure who to believe, Samsung are starting to run out of ideas and starting to say it may be a network issue. But if the network is down, then the phone should automatically reconnect once the network is back available again. And it doesn't.
I'm convinced it's a bug introduced with KitKat, as the problem only started then, but of course I cannot prove it...
felgrab said:
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Click to expand...
Click to collapse
Sounds very similar to my problem, that it just started with Kitkat only. I'm sure it can't be just us two having this problem! I don't have anything special or different installed on my phone, and it's too suspicious that it was working fine, 100% perfectly until the KitKat software came out...
Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUGNE5
CP: I9505XXUGNE5
CSC: I9505OXAGNE5
Thank you so much for giving us a hand!!
Chikara71:
I know it just cant be the two of us from such diferent places in the world but, i just cant find any similar in any post or google. It has been almost 3 months from the update an me using another phone...
Well I thought I would post again to close the loop.
After Samsung tried 5 times to fix my phone, checking hardware and trying to reinstall the OS with no luck, they suggested I try replacing my SIM card.
Surprise surprise, it has fixed the problem with no recurrence yet after a week so far.
I still don't understand how the sim card could be the problem, especially as my phone was working perfectly right up to the Kitkat software update. All I can assume is somehow KitKat either had an incompatibility with my simcard (maybe the new sim is technically slightly different?) or maybe KitKat somehow changed something on the simcard, if that's even possible.
Interestingly, I did contact my telco first, and they told me to contact Samsung. As it turned out, the fix was in the control of the telcom right from day one.
Anyway, so far the problem is resolved, so I thought I would post this here to help anyone that may have this problem.

Enablement error Wi-Fi Calling

Hello,
So I recently had my phone sent to repair for the Pink line issue. I activated an old htc one while I waited for my s7 edge to get back. Once it got back I activated the edge again, and now whenever I turn on wifi calling I am getting enablment error? "we are unable to process your request at this time, please power cycle the device and try again" Anyone have this happen? If so how did you fix it? Have tried wiping, updating prl/profile. reverting from beta to stock, nothing seems to work.
Robisgnarly said:
Hello,
So I recently had my phone sent to repair for the Pink line issue. I activated an old htc one while I waited for my s7 edge to get back. Once it got back I activated the edge again, and now whenever I turn on wifi calling I am getting enablment error? "we are unable to process your request at this time, please power cycle the device and try again" Anyone have this happen? If so how did you fix it? Have tried wiping, updating prl/profile. reverting from beta to stock, nothing seems to work.
Click to expand...
Click to collapse
Same here. I deactivated my S7 Edge and went back to my Nexus 6. Then I went back to my Edge and WiFi calling has not worked since. I actually opened a ticket with Sprint and later talked to 2 different engineers......that was almost a year ago, many factory resets and ##72786# as well. I still have the entitlement errors.....it's pretty sweet lol. Please let me know if you figure it out.
D

Help me with my Verizon S8

Hi
I owned an S8 on Verizon for a year or so and switched to Sprint's Bring Your Own Device Plan. One a Sprint SIM was inserted, the phone was rebranded and all Verizon apps were wiped off and replaced with Sprint. Fast forward a few months after, early June, I get a firmware update notification which I prompted to accept (as I have many times before for Verizon and Sprint updates). After the update, the phone worked for a few days and then all of the sudden gets stuck on the word Samsung S8 logo and restarts on its own. It keeps looping!
Resetting didn't work and I sent it to a store nearby (You Break, We Fix) and nothing could get this thing to go back to normal. I think the fact that the phone was on Verizon and was rebranded to Sprint is what caused the problem.
I downloaded Odin but can't figure out which version of the firmware I should use to flash the phone and get it to work. The original box that came with it says SM-G950UZKV and the SW-VER is G950USQU1AQC8. I don't care about the phone's photos/other data, I just want it to work again.
What firmware should I download to get the phone to work?

Categories

Resources