Database Develop

Can't get latest AT&T updates

AT&T is showing latest security update as August 2016, but I am unable to get it on my device. My phone is currently on T-mobile so I'm not sure if that has anything to do with it. I have tried updating through the phone, and also smart switch, and both say up to date. Are any others on the june security update or have you got the latest august update. Thanks in advance.

smoovy said:
AT&T is showing latest security update as August 2016, but I am unable to get it on my device. My phone is currently on T-mobile so I'm not sure if that has anything to do with it. I have tried updating through the phone, and also smart switch, and both say up to date. Are any others on the june security update or have you got the latest august update. Thanks in advance.
Click to expand...
Click to collapse
From my knowledge, you can only receive updates if you are on AT&T. To update please refer to this thread. However, flashing will result in data loss, so be sure to backup.

I've been able to get these updates even though I was on tmobile in the past. I didn't have any issues with the marshmallow update through WiFi as well, but the latest security patches have been no where to be found.

smoovy said:
I've been able to get these updates even though I was on tmobile in the past. I didn't have any issues with the marshmallow update through WiFi as well, but the latest security patches have been no where to be found.
Click to expand...
Click to collapse
You don't want those updates trust me.
They lock your phone down from you.. the end user.
You are not any more secure with those updates.
Actually you are less secure and more prone to full identity and activity disclosure with At&t and Google's " 3rd party affiliates ".

Nexus 6 (Verizon) still running MOB31H (6.0.1). Should I manually update via OTA?

I've got a Nexus 6 with Verizon Wireless. It is purely stock: I have never rooted or modified the phone in any way other than accepting the standard OTA updates pushed out by Google/Verizon.
I've been patiently waiting for the OTA update to upgrade my phone to Nougat, but I haven't seen any updates in over a month. My phone is currently running MOB31H (6.0.1) which, according to the Google Factory Images page is the security update from October 2016. However, according to the same page there have been two security updates in November (MMB31C and MOB31K), and there have been two versions of Nougat released since then (NBD90Z and NBD91P). My phone has not seen any of these updates, despite repeatedly checking for updates via the settings menu.
I've got a few questions along these lines:
1) I've seen rumors about trouble with Nougat, which suggests maybe Verizon/Google have been delaying a widespread roll-out. However, I have not seen anything posted recently about this (latest reports are from early October), and what I did see seemed focused on other phones (not the Nexus 6). Are there any known issues with Nougat running on the Nexus 6 that would make me want to delay upgrading manually?
2) Is it unusual for my Nexus 6 to still be running 6.0.1 with the October security update? Shouldn't it have at least received the November security updates? Have others experienced this issue?
3) If I download the OTA directly from Google and sideload the update, will this disable the automatic OTA updates in the future? I'd like to at least apply the November 6.0.1 security updates to keep my phone secure.
4) If I want to update my phone to Nougat manually, can I simply download the OTA for Nougat and follow the instructions Google includes for sideloading the OTA update? Or do I have to download the entire 7.0 factory image and install that image? I have experience installing the factory images (I have a Nexus 10 that I've had rooted for a while, so I've gotten good at installing the factory images whenever a new image is released) but it is still a bit of a pain and I would prefer the OTA updates for my phone if I can.
4a) If I can update via the OTA, can I pick the latest OTA (NBD91P), or do I have to go incrementally (install NBD90Z first then update to NBD91P)?
5) Only tangentially related question: I've noticed that Google has included the month and year on more recent factory images, but is there any way to determine the exact date that an image was released? For example: I see there are two November OTA updates for Nexus 6, how can I tell if MOB31K was released this morning vs. November 2? If it was released this morning that may explain why I haven't seen the update yet, but if it was released November 2 I would be surprised I haven't seen the update yet.
Thanks in advance for any help.

1. Verizon has no control over updates on this device. That said, no major issues with the stock ROM.
2. Not unusual at all. When I received my N6 earlier this year it stopped updating after the latest Android 5.0.1 update. I had to flash an Android 6.0.1 image manually.
3. No.
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
5. No way to tell outside of paying attention here, since someone will inevitably announce the release of the latest version. Of course, once you've installed the latest image, OTA updates should continue as usual if you don't modify the firmware like most of us do.

Thanks for the helpful reply! One quick follow-up:
Strephon Alkhalikoi said:
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
Click to expand...
Click to collapse
I will likely follow your advice regarding updating from the full factory image instead of the OTA. My main limitation is my two-factor authentication. Because I haven't rooted, it is a pain to transfer some of that from one device to another (in some cases it requires disabling two-factor authentication and re-enabling it on each site, and I have at least 12 website that are using two-factor authentication on my device). I need to make sure that I don't accidentally lose the authentication tokens.
If I get lazy, or just want to "risk" using the OTA: Can I use either OTA image (the one from October or November) to upgrade from 6.0.1 to 7.0? Or does the one from October apply a full update and the November is just an incremental update intended to by applied to an existing 7.0 build?

Both are full updates. I'm not sure as to how well your current data will transition over to Android 7.
I would look into finding a means of backing up your authenticator.

AT&T Galaxy S6 latest Firmware thread (cur: Mar update)

Straight to the content, new mirrors appreciated. I will update this thread as soon as a new update comes out.
Links to Odin are from sammobile, and the ADB drivers are on Github. All links are clean and untouched.
Odin 3.11.1
ADB for Windows
===========================
Untouched side loadable update zips downloaded from xdmd.sl.attcompute.com (sideload using ADB):
7.0 branch:
2017 Mar security level Android 7.0 (G920AUCU5EQB8 to G920AUCU6EQC9)
2017 Mar security level Android 7.0 (G920AUCU5DQB3 to G920AUCU6EQC9)
2017 Feb security level Android 7.0 (G920AUCU5EQA8 to G920AUCU5EQB8)
2017 Feb security level Android 7.0 (G920AUCU5DQB3 to G920AUCU5EQB8)
2017 Jan security level Android 7.0 (G920AUCS5DPK5 to G920AUCU5EQA8) | Credit goes to Mohit0144
6.0 branch:
2017 Feb security level Android 6.0.1 (G920AUCS5DPK5 to G920AUCU5DQB3)
2017 Feb secruity level Android 6.0.1 (G920AUCS5DPK3 to G920AUCU5DQB3)
2017 Jan security level Android 6.0.1 (G920AUCS5DPK3 to G920AUCS5DPK5)
2016 Dec security level Android 6.0.1 (G920AUCS5DPK1 to G920AUCS5DPK3)
2016 Nov security level Android 6.0.1 (G920AUCS5DPJ1 to G920AUCS5DPK1)
===========================
Official complete Odin images (flash using Odin):
2016 Oct security level Android 6.0.1 (G920AUCS5DPJ1)
Current update path to most current build:
G920AUCS5DPJ1 (odin flash) -> G920AUCS5DPK1 (sideload) -> G920AUCS5DPK3 (sideload) -> G920AUCS5DPK5 (sideload) -> pre-release G920AUCU5EQA8 (sideload) -> pre-release G920AUCU5EQB8 -> pre-release G920AUCU6EQC9
If you are on a version more recent than DPJ1, you can start from a later sideload update.
Disclaimer: You are responsible for what you do to your phone
How to flash using Odin (will wipe phone):
1. Extract complete firmware
2. Extract Odin software
3. Shutdown phone
4. Press BL, AP, CP, and CSC buttons in-order in Odin and load files, Odin may freeze during this, just wait it out. Don't touch other options
5. Press Volume down, home, and power together to go into download mode
6. Plug in phone to laptop, and press start to flash
How to sideload using ADB (will wipe phone):
1. Install ADB, reboot
2. Using cmd, cd into the folder of the sideload update zip
3. Shutdown phone, press Volume up, home, and power together to go into download mode
4. Select "apply update from adb", use power button to confirm
5. Using the command "adb devices", verify that the phone is detected after plugging in, if it is detected, proceed
6. Type in command "adb sideload SIDELOADZIPNAME"
7. Wait, it takes a bit for the update to work, and the phone may appear frozen during this process.
If confused, see this thread: http://forum.xda-developers.com/att...ating-to-android-6-0-1-g920aucu3cpd6-t3371884

did exactly what u said with the odin and i keep getting a fail...

Billfromnj05 said:
did exactly what u said with the odin and i keep getting a fail...
Click to expand...
Click to collapse
Well, the file is the exact same as that from this thread. And it is working for those people, so not sure why this is happening to you without more details.

Thank you for these updates.

would this fix the reboot issue? clearing cache doesnt help with previous update (oct)

drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update
(oct)
Click to expand...
Click to collapse
I have absolutely no idea about why your phone is crashing.
Installing an update may fix it, just by virtue of clearing the /data partition and resetting it to stock in the process. But personally I doubt it (unless google fixed a denial of service bug that you were somehow triggering?).
Not really a diagnosis thread, so do you mind creating a new post with USB debugging turned on and logcat output so the community can help?
See here: http://android.wonderhowto.com/how-...ture-logcat-for-detailed-bug-reports-0167774/

drek_67045 said:
would this fix the reboot issue? clearing cache doesnt help with previous update (oct)
Click to expand...
Click to collapse
Not sure as to specifics of your reboot issue, but I had an S6 that started giving me multiple random reboots per day. Luckily I was inside warranty by a couple weeks - it was a hardware issue. Ended up with a new main board, plus a new display since the tech broke the original somehow changing the board.

That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.

supersmilers said:
That's funny. I never got Dec update for my AT&T S6 variant over OTA. I guessing, it's time to sideload it again.
Click to expand...
Click to collapse
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.

sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)

sand_bit said:
This has not been officially released yet. But it has been sitting on AT&T servers for quite a bit (along with DPK2). The kernel has a build date of Dec 14. My guess is that AT&T is waiting after the holidays to officially release this. It's a fairly small update coming in at 17MB.
Edit: I should note that I am running DPK3 without issue.
Click to expand...
Click to collapse
December update has been pushed out OTA. Is PK3.
Sent from my SAMSUNG-SM-G920A using Tapatalk

GilbertoXDA17 said:
Man can you tell me, how do you flash in adb sideload the latest firmwares?, my s6 send me an error
E: Error in /sideload/package.zip
(status 7)
Click to expand...
Click to collapse
Not sure, but probably need to flash this with Odin

worked fine, note of caution.
my att gs6 was on oj9. flashed went through fine initially then an error came up "can't open the serial(com)port" and FAIL in red above the blue part.
however, the phone progress meter kept going and eventually the flash was successful.

My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.

wiltaf said:
My g920a is stuck at g920aucs5dpi1 and on ota it says my software is up to date. I don't know what's happening or is it because I am not using at&t sim? But it's already unlocked.
Click to expand...
Click to collapse
I would bet that it's because you're not on an AT&T sim. I don't think they feel responsible to update the phone if it's not on their network. Not sure if you can throw someone's sim in there to update it or if you just ODIN flash it to update it.
Edit: You can also try to use Smart Switch to see if it'll pull the update, or try a Samsung Experience at a BestBuy to see if they can push the update.

Thanks. Now my phone is up to date.
This is the only way I can apply updates. For some reason I never get the OTA updates.

Thanks my phone updated to latest.

will my unlocked galaxy s6 become locked if i update using this?

Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA

Is this for phones already with root access?
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
Zero4 said:
Could someone tell me if the encryption menu items are available on your GS6, and what build you are on?
I encrypted my phone about 2 builds back, and after the December update, upon reboot it no longer asks for my PIN/PW and encryption is no where to be seen in the settings, or at least I (and search) can't find it. I don't want to factory reset to see if it reappears...yet.
If AT$T removed encryption from the device in the next update, I'm going to be real pissed.
Also, I think (at the moment) my battery life is worse on the latest build, but I have been using my phone a little more lately. But last night I went from 100% at 7:05pm to 5% at 11:30pm. 4.5 hours is not way to quick for a battery to die. Wakelock Detector (no root) didn't give much info, and the system menu for battery gave 3 of the top 4 to Android OS, Google Play services, Android System.
TIA
Click to expand...
Click to collapse
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
---------- Post added at 06:22 PM ---------- Previous post was at 05:42 PM ----------
mjr4281 said:
Hey guys,
I'm on a stock Samsung Galaxy S6, SM-G920A, Android Version 6.0.1, Security Patch Level December 1, 2016, Build Number: MMB29K.G920AUCS5DPK3. I have an AT&T Go-Phone account (pre-paid). Do I have to root my phone before following this procedure? I have never tried to root this phone before. I have been researching the topic for a long time and just wanted to make sure I understand everything thoroughly before I pull the trigger. Don't want to trip KNOX or brick my phone. Any help would be much appreciated. Thanks fellas.
Matt
---------- Post added at 11:42 AM ---------- Previous post was at 11:31 AM ----------
I'm on AT&T Galaxy S6, SM-G920A, Android Version 6.0.1, Build #: MMB29K.G920AUCS5DPK3. My phone is stock, no root. I have the encryption settings and am currently using them. Everything seems to be working fine.
Click to expand...
Click to collapse
They did change it up though. Whatever you choose as your screen lock i.e., pattern, pin, password, is what will be used for unencryption at start-up. The one thing that doesn't make sense to me is that they now give you an option to use one of these methods or none at all during start-up. I don't see the point in using encryption if you can't password protect it, but I haven't fully researched all the options yet.

T-Mobile Nexus 6 - 6.0.1 - Security Updates

My T-Mobile Nexus 6 still has 6.0.1 and I am not looking to upgrade to Nougat 7.xxx. What I am trying to do is install the security updates. The last OTA was from November 5, 2016. Why is T-Mobile not sending these out? Do I have to root my phone to download and install? Help would be appreciated. Thanks Dan

Strange. I had a 6.0.1 February security update from T-mobile. I got the 7.0 update with the March patch earlier this month, which was probably the end of the 6.0.1 patches. You can sideload the February patch from the OTA site, but don't expect any more.

Ota 7.1.1 havoc with Radios.
I finally attempted to sideload 7.1.1 N6F26U - cell data has been horrible. I am on T-Mobile. What 7.0 or 6.0.1 I think has the most security packages that I should install. BTW N6F26U broke Android Pay which makes me sad. Thanks in Advance.

What I wound up doing was go to the T-Mobile page and established the official latest factory image was 6.0.1 MMB29K - installed that using Wugfresh. After installing and logging into WiFi and my Gmail account was prompted to install 7.0.0 NBD92G - this installed fine and then after installing a couple of security updates (thru April 2017) was able to Re-Lock my Bootloader (I wanted Android Pay to accept my credit cards). Data reception is still degraded significantly, am now thinking there is a problem with the tower.

voyageurs60 said:
Data reception is still degraded significantly, am now thinking there is a problem with the tower.
Click to expand...
Click to collapse
Sorry, I haven't read through this thread. It's likely, in doing your updates, the modern (radio) software was updated as well. The modems are OS version independent and you may now have one that doesn't work as well for you as your original one did. You may not know which one you started with, but you could just try several to see if any improve the situation for you. Here are flashable zips of many of the modems.
You might also double check your APN settings against TMO website. I use Sprint, so no APNS, thus I can't really give you a step thru. If you search though, it's not an uncommon discussion.

November Update#2

I installed the November Update in 5th and few seconds ago a new update showed up with 1.82GB.
Did anyone has the same, I am a little bit nervous to install.

I had this same issue with my wife's p4a 5g. in the process of updating mine to the Nov security update (finally got around to opting out of the beta so I could update it) and then I'll see if mine does the same thing.
UPDATE: Finally got the security update installed and my 4a 5g also has the upgrade notification. After doing some digging around, it seems that Google accidentally pushed the VZW specific update to all Pixels (the update in question is this one: 12.0.0 (SP1A.211105.002.A1, Nov 2021, Verizon, Verizon MVNOs)). I will most likely ignore this update if that's the case. (took almost an hour to optimize apps for the security update, not looking forward to doing that again right now lol).

same here..lets see if the build number will be sam

Hersfeld said:
I installed the November Update in 5th and few seconds ago a new update showed up with 1.82GB.
Did anyone has the same, I am a little bit nervous to install.
Click to expand...
Click to collapse
Same here.
Just 2 days ago i did a clean install of nov 5 image SP1A.211105.003

I received the update the same day pixel 6 was launched,today received another update to install 12.i paused it until be sure whats going on

Mine installed ...
Previously : SP1A.211105.003
After : SP1A.211105.002.A1

According to their release details
Pixel 4a 5G: Android 12 – SP1A.211105.003, SP1A.211105.002.A1 (Verizon, Verizon MVNO), SP1A.211105.004 (Telstra, Optus, Vodafone AU) – Factory image – OTA (2) (3)

Same thing is happening on the Pixel 5 and 6. I'm currently on the ,003 firmware on my Pixel 5, even did a clean factory install. Still getting an update notification. It would be nice if Android would define the version of the update...
If you are rooted, DO NOT take the automatic update. If you do, you will have to wipe to re root.

clark71822 said:
I had this same issue with my wife's p4a 5g. in the process of updating mine to the Nov security update (finally got around to opting out of the beta so I could update it) and then I'll see if mine does the same thing.
UPDATE: Finally got the security update installed and my 4a 5g also has the upgrade notification. After doing some digging around, it seems that Google accidentally pushed the VZW specific update to all Pixels (the update in question is this one: 12.0.0 (SP1A.211105.002.A1, Nov 2021, Verizon, Verizon MVNOs)). I will most likely ignore this update if that's the case. (took almost an hour to optimize apps for the security update, not looking forward to doing that again right now lol).
Click to expand...
Click to collapse
But is working fine with the Verizon firmware?

Good day; would a factory reset be a solution to revert back to the global version ? Thanks !

Saturnin97 said:
Good day; would a factory reset be a solution to revert back to the global version ? Thanks !
Click to expand...
Click to collapse
No.
Use the Android Flash Tool to install the global version. Data wipe/factory reset should not be necessary.

Update no longer available for me. Seems like Google realized their mistake.