Database Develop

Still on Oct Security Patch

Hey All,
When I bought my N6 in September, it was already enrolled in the Preview program. I got 7.0 immediately after release... but I have yet to receive any of the security patches.
I know, I can find the factory images and such and flash, but this is the first device in 14+ years (going back to the Toshiba e800) that I haven't tinkered with... yet. Google is supposed to keep OTA'ing them for another year or two, is my understanding
So, just wondering, anyone else still stuck on 10/16 security patch?

cameraddict said:
Hey All,
When I bought my N6 in September, it was already enrolled in the Preview program. I got 7.0 immediately after release... but I have yet to receive any of the security patches.
I know, I can find the factory images and such and flash, but this is the first device in 14+ years (going back to the Toshiba e800) that I haven't tinkered with... yet. Google is supposed to keep OTA'ing them for another year or two, is my understanding
So, just wondering, anyone else still stuck on 10/16 security patch?
Click to expand...
Click to collapse
Umm no. The nexus 6 is EOL. The only thing you ma get is security patches but as you can see those are not always available. If you want to stay up to date you will need to flash the image.

zelendel said:
Umm no. The nexus 6 is EOL. The only thing you ma get is security patches but as you can see those are not always available. If you want to stay up to date you will need to flash the image.
Click to expand...
Click to collapse
I know that. And that is what I said. I know I can flash the images... I'm asking if anyone else is still stuck on the Oct patch through the OTA system. Google supposedly promises them for another year past EOL.

cameraddict said:
I know that. And that is what I said. I know I can flash the images... I'm asking if anyone else is still stuck on the Oct patch through the OTA system. Google supposedly promises them for another year past EOL.
Click to expand...
Click to collapse
I know a few people that have never even gotten a single OTA the entire time they have owned the device. Yet they are not worried about it. Most of the security updates are a joke really.

zelendel said:
I know a few people that have never even gotten a single OTA the entire time they have owned the device. Yet they are not worried about it. Most of the security updates are a joke really.
Click to expand...
Click to collapse
I mean absolutely no offense, but your answers aren't very helpful. Perhaps some people could care less about the OTAs, but I do- and I'm sure that I am far from the only one. As to their efficacy, I'd rather have an official security patch than not.

cameraddict said:
I mean absolutely no offense, but your answers aren't very helpful. Perhaps some people could care less about the OTAs, but I do- and I'm sure that I am far from the only one. As to their efficacy, I'd rather have an official security patch than not.
Click to expand...
Click to collapse
Then by all means flash the update. OTA have always been touchy. I have been sitting right next to someone else when they got an OTA to the same device and I never saw it.
That is why we here at XDA long ago gave up on OTA and advise people to do it for themselves if they have the ability (nexus users).
No offense taken at all. Been around to long to take offense to things posted on the interwebs

T-mobile Note 9 Pie Update Status

As the title suggests, I'm on the T-mobile Note 9. I was looking around online for a Pie update and found this page. I thought I'd share for those who hadn't seen it.
https://support.t-mobile.com/docs/DOC-39346
Apparently, there are three different statuses: Development, Testing and Complete.
As of yesterday, the Note 9 was still in Development. Today, it is in the Testing mode. Lets hope we're getting pretty close to the release!
EDIT 3/2/2019
According to the above link, the device is still in TESTING. In this document, Android 9 Pie HAS BEEN released as of 3/1/2019, but only to a limited audience. Not sure if this is a test group or what's going on.
EDIT 3/3/2019
Hi everyone. Please keep this on topic. The reason I made this thread is to provide a reference (T-mobile users) on the status of the update. If you need assistance getting back on the OTA track, please create your own topic. Furthermore, this thread is meant for users on the T-mobile SM-N960U, "probably not" the SM-N960U1 , which I know nothing about. Thanks!
EDIT: 3/4/2019
According to the document I originally posted, the phase of the update has now changed to COMPLETE. Hopefully, I'll have it by the end of the week, but we shall see how long actual deployment takes. The document provided in the 3/2/2019 update of this thread does not detail any further updates past 3/1/2019.
I just checked for updates. A security level patch level February 1, 2019 is now downloading. Size 1867.41 MB. Versions: N960USQU1CSB3 / N960UOYN1CSB3.
EDIT: 3/5/2019
I'm now on Android Version 9 / N960USQU1CSB3.
First Impression: I do not like the fact that the time clock is moved to the left side. They should've kept it where it was. I'll be looking for a way to change it.

I'm hoping it comes out next week. Att already has it, so I dont know what's taking them soo long to release it for tmobile

My wife's S9+ got the update today from TMobile. I'm surprised that S9+ got it first before Note 9.

Today it shows its moved to testing, hoping to get it soon now.

chinmayfun said:
Today it shows its moved to testing, hoping to get it soon now.
Click to expand...
Click to collapse
Been like that all week.

My guess you won't see any updated to the Note 9 till long after the S10 is in stores. T-mobile is a crap company and this is how they do business. They will hold the update till we have had many weeks to look at the S10. T-mobile want you to spend the money on the upgrade. It's the 25th of February this update has been available on unlocked devices for nearly a month. AT&T has had it on their Note 9 for a few weeks already.

Big D5 said:
My guess you won't see any updated to the Note 9 till long after the S10 is in stores. T-mobile is a crap company and this is how they do business. They will hold the update till we have had many weeks to look at the S10. T-mobile want you to spend the money on the upgrade. It's the 25th of February this update has been available on unlocked devices for nearly a month. AT&T has had it on their Note 9 for a few weeks already.
Click to expand...
Click to collapse
If any part of what you said was even remotely true, then they wouldn't have pushed the update to their S9/+. Note 9 owners aren't the target audience for the S10/+

Imo keep Oreo untill the next Pie update at least. It has bugs and if you just got the device there may be things you want but aren't on Pie.
Updates are fine but OS version changes I let others be the guinea pigs...
Photo's[emoji2398] by Sully using SM-N960U or SM-870A

Just talked to a Tom rep, they stated they were sorry about removing the note o update and that they were in process of approving a new update that would release in March but that he was not sure. Smh

hondasforlife said:
Just talked to a Tom rep, they stated they were sorry about removing the note o update and that they were in process of approving a new update that would release in March but that he was not sure. Smh
Click to expand...
Click to collapse
that mustache Tom is a bastard.

hondasforlife said:
Just talked to a Tom rep, they stated they were sorry about removing the note o update and that they were in process of approving a new update that would release in March but that he was not sure. Smh
Click to expand...
Click to collapse
Assuming similar as the U1 update not dropping until March as well

This is depressing
However, I did update mine manually using the OTA that is posted. Could wait for T-Mobile.
Went fairly smooth. Couple minor issues, one with Google Home. Home would crashed every time I opened it. In the end, a factory reset brought everything in line.
I would recommend this upgrade to anyone and I would also recommend just side-loading it like I did.

Pie is ugly and slow

pbedard said:
Pie is ugly and slow
Click to expand...
Click to collapse
Ugly can be changed with a theme but then again ugly is subjective.
As far as speed .. it actually behaves faster on my 9 then Android 8.x did. Not sure what you are running on yours that would slow it down so much.

Been on Pie now for a week. Love it. Better battery life, faster in almost every aspect. Didn't wanna wait for TMO to push it so went the firmware science route.
Haven't experienced any issues that have been reported, quite the opposite for me. I personally prefer pie over Oreo, but that's just me. Now if only, they fix the Swift installer app to work with Pie (unrooted) now.

Saw this on Droid Life just now...
https://www.droid-life.com/2019/03/01/t-mobile-galaxy-note-9-receiving-pie-update/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+DroidLife+%28Droid+Life%29

https://support.t-mobile.com/docs/DOC-38176

I'm on CSAA will it be able to OTA to the least tmobile on release?

I am currently on Tmobile with the version N960U1UEU1ARL1, would i have to wipe my device if I download the update manually? In any case, I can't seem to find my version on the Firmware Science form so do i just have to wait for the unlocked version of the update or am I eligible for TMOBILE's

I am confused, on the official T-Mobile update page, it lists N960U1UEU1CSB3 as the build number for the update. I thought N960U1UE specifies it's for the unlocked N960U1, where as carrier builds for the N960U are N960USQ?

Updates for Pixel 5 on Verizon network

Checked for this through first 10 pages of this forum; my apologies if I missed it there or elsewhere.
Last update targeted to Verizon was February 2021.
Any idea why Verizon-focused updates are so infrequent? I'm guessing it's just not a priority to them.
Is there any reason not to use latest P5 image (either factory or OTA, like RQ2A.210505.003, for example) to get the benefit of Google feature updates as well as security aspects? I wouldn't use an image meant for another carrier, but I'm not sure if there are differences in the non-carrier versions that I might need to be aware of.
My P5 is rooted and on RQ1D.210105.003. I did NOT buy it through Verizon.
Thanks in advance for your time and help.

dm5530 said:
Checked for this through first 10 pages of this forum; my apologies if I missed it there or elsewhere.
Last update targeted to Verizon was February 2021.
Any idea why Verizon-focused updates are so infrequent? I'm guessing it's just not a priority to them.
Is there any reason not to use latest P5 image (either factory or OTA, like RQ2A.210505.003, for example) to get the benefit of Google feature updates as well as security aspects? I wouldn't use an image meant for another carrier, but I'm not sure if there are differences in the non-carrier versions that I might need to be aware of.
My P5 is rooted and on RQ1D.210105.003. I did NOT buy it through Verizon.
Thanks in advance for your time and help.
Click to expand...
Click to collapse
The only time there are Verizon specific updates are for when they are needed to work on their network. Most times, the regular update is all that is needed. They still get released on the same day, so if you don't see one that's Verizon specific, use the regular one.

I usually avoid the Verizon specific releases. Never had an issue.

Question No December update, nor January. Is anyone else experiencing this?

I usually receive my updates around the 5th of the month. November 2022 was my last update. The phone was bought direct from Google unlocked. I use it on Consumer Cellular (AT&T). I've called google support and posted the issue on their community forum. Support said to factory reset but admitted they have no idea of what's going on. My post was locked in the community forum.
I saw on the XDA Pixel 5 forum that there was some issue with the releases but its not confirmed by Google.
I'm more concerned over security patches than bug fixes. My phone is working fine.

hi.
i bought my 5a, like you, from Google and unlocked.
i use it in Argentina.
i never received any communication about updates but i allways get my monthly update looking for it in:
config-system-system updates
try that way
right now i have all the updates, the last is January 5

I also am stuck on Nov 5 with a phone bought direct from Google. I am on Mint (T-Mobile MVNO).
Manually re-checking in system - system updates - check for updates reports that it is up to date.

miguelAr9 said:
hi.
i bought my 5a, like you, from Google and unlocked.
i use it in Argentina.
i never received any communication about updates but i allways get my monthly update looking for it in:
config-system-system updates
try that way
Click to expand...
Click to collapse
Yes, I too look for my monthly updates in the path you describe. At least twice per day.

lightuser said:
I also am stuck on Nov 5 with a phone bought direct from Google. I am on Mint (T-Mobile MVNO).
Manually re-checking in system - system updates - check for updates reports that it is up to date.
Click to expand...
Click to collapse
Yep, same here. Just checked and says I'm up to date with the November update.

i don´t know how your cell companies work with google, but i knew that in other brands of phones there were different kind of updates, direct for the unlocked phones, with the cell companies attempt to intercept those updates to modify it, perhaps something has changed after November update giving them the control.
my cell company does not interfere.
did you ask the operators?

miguelAr9 said:
i don´t know how your cell companies work with google, but i knew that in other brands of phones there were different kind of updates, direct for the unlocked phones, with the cell companies attempt to intercept those updates to modify it, perhaps something has changed after November update giving them the control.
my cell company does not interfere.
did you ask the operators?
Click to expand...
Click to collapse
My company doesn't gatekeep updates on any phones on their network.

mikehd1959 said:
I usually receive my updates around the 5th of the month. November 2022 was my last update. The phone was bought direct from Google unlocked. I use it on Consumer Cellular (AT&T). I've called google support and posted the issue on their community forum. Support said to factory reset but admitted they have no idea of what's going on. My post was locked in the community forum.
I saw on the XDA Pixel 5 forum that there was some issue with the releases but its not confirmed by Google.
I'm more concerned over security patches than bug fixes. My phone is working fine.
Click to expand...
Click to collapse
I'm still on December 5th security update and November 1st Google Play system update on my Pixel 7

Like others, I bought my Pixel 5 unlocked, direct from Google.
The last update I received was November 2022. Typically, on the 5th of the month or so, I could pop into settings and check for update and it would be there.
I saw reports on several sites of an issue with the Dec update on 5 and 5a phones - some getting bricked - and so I didn't so much mind never getting that update. BUT, this was a pricey phone, and I buy from Google specifically to get 3 years of monthly security (and feature) updates.
Google NEEDS to provide some manner of explanation. If they would just state that there's an issue and they are working to address it, just that acknowledgement would be appreciated.

mikehd1959 said:
I usually receive my updates around the 5th of the month. November 2022 was my last update. The phone was bought direct from Google unlocked. I use it on Consumer Cellular (AT&T). I've called google support and posted the issue on their community forum. Support said to factory reset but admitted they have no idea of what's going on. My post was locked in the community forum.
I saw on the XDA Pixel 5 forum that there was some issue with the releases but its not confirmed by Google.
I'm more concerned over security patches than bug fixes. My phone is working fine.
Click to expand...
Click to collapse
Yes, I have the same problem, no update on my 5a since Nov 5th.
Googles lame "support" function can be reliably counted on to punt with a factory reset recommendation whenever they don't know the answer. The next suggestion will be to exchange the phone under warranty. Of course, if it is no longer under warranty then you are SOL
Has Google head Sundar Pichai laid off the help to save some $$?

Both of my Pixel 5As on Google Fi never updated beyond November. I finally gave up and sideloaded the January OTA on mine. My wife is still stuck on November on hers.

skeeterfood said:
Both of my Pixel 5As on Google Fi never updated beyond November. I finally gave up and sideloaded the January OTA on mine. My wife is still stuck on November on hers.
Click to expand...
Click to collapse
Have you had any issues with the January OTA?

skeeterfood said:
Both of my Pixel 5As on Google Fi never updated beyond November. I finally gave up and sideloaded the January OTA on mine. My wife is still stuck on November on hers.
Click to expand...
Click to collapse
Can you give more info here? Is there a way to safely download and apply the update or does it involve a reset and firmware install?
I went through the google support chat and ended with them pointing me to https://pixelrepair.withgoogle.com/carrier_selection to "manually install the system update". I haven't pursued it yet, because it talks about doing a backup and restore and I'm not looking forward to that...
I'm not sure my app state will be preserved and it will be a hassle to go through other recovery processes for some of them.
I am a Linux user and relatively clueful about computers, but naive about Android. I think I'd be able to follow some ADB command steps, but I get put off by web discussions around Android that expect folks to download from sketchy looking file-share sites and blindly trust whatever is in them

FWIW, I tried to follow the support advice at the pixelrepair carrier selection link above. After wiping and reinstalling my phone using the appropriate "USA Others" carrier choice, it left me with the exact same TP1A.221105.002 build number I had before and the same problem of showing up to date with Nov 5.
So a big waste of time and the incomplete backup/restore I expected means I get to piece back together a number of extra app accounts etc...
Edit: the next support reply just says something similar to what others said above...
Thanks for trying the steps. Our most recent Pixel update will be deployed at a later date for a small subset of Pixel 5 and Pixel 5a (5G) users. We are currently re-evaluating the build before distribution to this group.
Click to expand...
Click to collapse

mikehd1959 said:
Have you had any issues with the January OTA?
Click to expand...
Click to collapse
I haven't noticed any new issues. The Bluetooth connections to my Garmin watch and Dexcom CGM are still a little flakey sometimes, but they have been since the upgrade to Android 13, so nothing new there.
I figured Google would have pulled the OTA images off the official website if there was a big enough problem.
There have been reports of the OTA causing the black screen death, but I thinks it's just coincidental and the phone was going to die anyway. I decided I might as well get the repair/replacement over now before they end the extended warranty for it.

FWIW, mine got an update today and so went straight from Nov to Feb 5 patch level.

lightuser said:
FWIW, mine got an update today and so went straight from Nov to Feb 5 patch level.
Click to expand...
Click to collapse
Thanks for the heads up. I just checked and my 5a is now preparing for system update.

You can ADB sideload updates, even on a locked bootloader, without wiping your device. If this ever happens again and you're months behind on the update, just sideload it rather than being at the mercy for Google to actually push out the update to your phone. Instructions: https://developers.google.com/android/ota

Dopamin3 said:
You can ADB sideload updates, even on a locked bootloader, without wiping your device. If this ever happens again and you're months behind on the update, just sideload it rather than being at the mercy for Google to actually push out the update to your phone. Instructions: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Yes, that's always an option, however, there was enough internet chatter about it being deliberately withheld, or causing issues with phones that I was reluctant to take that path.
Google's silence on these topics doesn't help.

It seems to be happening again in March - the phone does not find an update either manually or automatically. There are March images, Factory and Full OTA, available on Google's site though. I'm wondering if there is a reason to not install the update with Fastboot. This is all very odd.

Great to join the club!!

Hey guys! I have been scouting around for Note 8 help but thought it was time to join myself.
Hopefully if I am able to solve my specific problem or get my questions asked it can help someone else.
Specifically, right now, I picked up and refurbished a Samsung Galaxy Note 8 since I have one currently that is phenominal, and wanted one in the back pocket in case anything happens but it is locked to ATT, which isnt the real problem. The real problem is that it is still on Android 7.1.1 and I would like to get it to Android 9 Pie.
I am unsure of a few things like whether I need all updates between 7 and 9, or if I can jump straight to it. But things of that sort.
It sucks that its ATT locked but I feel its worse that its on old Android since I refurbed it, (fixed screen and replaced with fresh samsung battery) but its being held back in certain functional capabilities. Either way, I am a techy, not yet able to solder, but definitely able to troubleshoot my way around a Windows Blue screen of death.
Looking forward to learnin more!

MethudMann said:
Hey guys! I have been scouting around for Note 8 help but thought it was time to join myself.
Hopefully if I am able to solve my specific problem or get my questions asked it can help someone else.
Specifically, right now, I picked up and refurbished a Samsung Galaxy Note 8 since I have one currently that is phenominal, and wanted one in the back pocket in case anything happens but it is locked to ATT, which isnt the real problem. The real problem is that it is still on Android 7.1.1 and I would like to get it to Android 9 Pie.
I am unsure of a few things like whether I need all updates between 7 and 9, or if I can jump straight to it. But things of that sort.
It sucks that its ATT locked but I feel its worse that its on old Android since I refurbed it, (fixed screen and replaced with fresh samsung battery) but its being held back in certain functional capabilities. Either way, I am a techy, not yet able to solder, but definitely able to troubleshoot my way around a Windows Blue screen of death.
Looking forward to learnin more!
Click to expand...
Click to collapse
Welcome to XDA! As for updating your phone, could you please tell me your model number?

ethical_haquer said:
Welcome to XDA! As for updating your phone, could you please tell me your model number?
Click to expand...
Click to collapse
Yeah, sorry for long response time.
For the important info:
Model: SM-N950U
Android. 7.1.1
Build:NMF26X.N950USQU1AQH7
CSC: ATT

I'll monitor more closely so let me know if you need any other info

MethudMann said:
Yeah, sorry for long response time.
For the important info:
Model: SM-N950U
Android. 7.1.1
Build:NMF26X.N950USQU1AQH7
CSC: ATT
Click to expand...
Click to collapse
Alright, there are two versions of firmware available for your device. One is "branded" and has carrier bloat, whereas the other does not have carrier bloat but might have issues with VoLTE (probably not, but there is a chance). What one would you prefer? Let me know if you have any questions regarding the difference.

ethical_haquer said:
Alright, there are two versions of firmware available for your device. One is "branded" and has carrier bloat, whereas the other does not have carrier bloat but might have issues with VoLTE (probably not, but there is a chance). What one would you prefer? Let me know if you have any questions regarding the difference.
Click to expand...
Click to collapse
Thanks for the research and yes I do have questions if its not too much of an issue:
1.) Carrier bloat is like the usual and can just be deleted anyways correct?
2.) In what scenarios (in case everything was working fine with OTA updates) would the phone have downloaded a version without bloat?
3.) Would updating to the non-bloated version cause any issues since the phone is still carrier locked?
4.) Lastly, for the firmware, would I need to download multiple updates until that point or just straight to the firmware?
If not, I can research the answers as I have been on it on and off for a month with research but other than that, you're a god send.
By the way, if #1 is true, I'll just take the bloatware no doubt just to be as safe as possible.

Thanks again for all the help @ethical_haquer
Been busy researching in the Samsung Note 8 ATT threads and I was able to find the answer to number 4 in that using Full ODIN files is a complete flash and different than just an update which requires the previous updates.
The answer to number 3 from what I have seen no. The only thing is that certain features may NOT work such as VoLTE; pretty much you already answered 3 and I was literally too dumb to see that until I started writing this message. *face palm
Question 2 is pretty much inconsequential so don't worry answering that. Its was just curiosity. But for anyone who does see this possibly, my speculation is that NO, the carrier version would never download the non-carrier version. The non-branded update is for those unlocked phones that receive over-the-air (OTA) updates that were not associated with any carrier, in other words buying a phone directly from samsung's website.
For 1, I am guessing it is "Yes" since I was able to do that in the past with all my other phones. But either way it is not a make it or break it so it doesn't matter.
I have been able to find some full ODIN files for the updates I was looking for, so will be attempting my first flash soon. Will be posting all my findings to the thread I was reading just to potentially help anyone else (though rare since this device is getting real old) who has the same questions I had and I can get them up to speed without having to search everything

Just finished flashing the ATT Note 8 to and the Answer to Number 1 is that NO, you cannot Uninstall the bloatware
Again, will post all these findings to the proper thread in after completed

Sorry for the late reply! I would try installing the firmware for the SM-N950U1 (notice the 1). It should work and won't have carrier bloat.

ethical_haquer said:
Sorry for the late reply! I would try installing the firmware for the SM-N950U1 (notice the 1). It should work and won't have carrier bloat.
Click to expand...
Click to collapse
You're all good!
I may but I actually have to find one more update I am looking for (Full ODIN FILES). My daily driver note 8 is on N950USQS7DTE5 and it is a T-Mobile Version (though it bein g TMO is inconsequential at the moment. Just thought I might mention it).
That is the update I would like for ATT just so that I know there wont be any differences (or less differences) between my daily driver and this.This is me being picky at this point but isn't the point of life getting what you want? I found one update above that but different bootloader. So for whatever reason may happen, no going back.
What I currently flashed to was N950USQS3BRA8 so it's still on Android 7.1.1 but I did this just to test to the process (my first flashing). Now I am ready.
So I will look for that then flash it and update as usual

Just found, or couldnt find, that ATT has the same update so will just go with what I have. Close as I can get