Database Develop

June security patch OTA

Has anybody other than Note 8 Global or Verizon received June security patch for Note 8 ( N950U)?

I have lol

Anyone on N950U1 yet?

Not for Tmobile. I'm on may security patch still S4CRE1

Sprint still on may

Dchoi229 said:
I have lol
Click to expand...
Click to collapse
Which network you on?

N950U1 unlocked Snapdragon version and I am still on May security patch.

jehdesai said:
Which network you on?
Click to expand...
Click to collapse
T-mobile but I have the N950F/D model.

Got one this morning on Tmobile

Nothing yet on my Srint 950U

Nothing on my Sprint Note-8......still on May patch.

Still on May update?

I'm just curious if there are any other N960W users that can confirm that they're also still on the May update on Telus. I have yet to receive the June or July update at all.
Anyone else?

jd14771 said:
i don't have your phone, however, samfirmware shows there at least being the June update available., with the security patch showing as:
Fri, 24 May 2019 08:35:48 +0000
https://www.sammobile.com/samsung/galaxy-note9/firmware/SM-N960W/TLS/download/N960WVLU1CSE3/275532/
If you search "baseband version" in settings, does "N960WVLU1CSE3" match with your phones version? if so you are on the latest at the moment as far as i can see.
Click to expand...
Click to collapse
Thank you for the reply, that baseband version matches, so I guess I am on the latest build available after all.

jd14771 said:
yeah, i had similar questions, and it seems that the security version is usualy a month or two behind the builds release date. hence the june update with may security patch.
Click to expand...
Click to collapse
I am on SM-N960F, international Eyxnos based version in UK which is different to your model, that said the latest build over here has the latest security update.

MoistPicklez said:
I'm just curious if there are any other N960W users that can confirm that they're also still on the May update on Telus. I have yet to receive the June or July update at all.
Anyone else?
Click to expand...
Click to collapse
Hi. I am with Rogers and have the same model as you. Rogers will have an update at the end of July and I am pretty sure you will too. It will be the July update but I do not know if it will include the camera night mode which is what I really want.
BTW, I am also just on the May 1 update

jd14771 said:
since you have the snapdragon variant, then the chances of getting night mode is .1%. only exynos has gotten camera night mode so far.
Click to expand...
Click to collapse
The update actually just happened now on Rogers - over 700 MB - and it includes night mode.

Korean Exynos variant here (KOO), I also still have the May update only. Tried all kinds of crazy stuff to get the camera night mode and latest security update to no avail. Samsung sucks.

jd14771 said:
can you post a screenshot of settings>about>software
Click to expand...
Click to collapse
Here it is

here is the system.img( from cdn july updt)
ive stripped all other partitions so that its only system that is left.
https://1drv.ms/u/s!AhXVLDDj8g3AgrxJZli8wU0bizZk2g?e=btQ0by

ca12bon said:
Korean Exynos variant here (KOO), I also still have the May update only. Tried all kinds of crazy stuff to get the camera night mode and latest security update to no avail. Samsung sucks.
Click to expand...
Click to collapse
same here, n960n only that im in (SKC) and on april , which by the way is quite bad, you would think samsung will update those models first seeing that its for their home market but nope.
i thought maybe samsung knows we are outside korea but when i check sammobile and other web pages it doesnt show new updates.
i really didnt want to root but this might make me to root and flash a rom with latest updates, but first i have to visit samsung service center to check my camera module.

Same here, verizon update last night. Includes night mode. Also includes typo...lol

just got the update with night mode and july security - n960n.

Still on the June update. Im on sprint

Sorry for going off topic here, I see you "W" guys updated the firmware - any battery life hit on Canadian N9? I am on Koodo and still on Oreo, scared to upgrade after reading many complaints about the battery life issues.
Thanks

Just got an update from at&t 882mb

Build Info

Hey all, probing into here. Can everyone please post what build they have and what phone they have, unlocked, or what carrier?
Att Pixel 4 XL - build QD1A.190821.011.C4
Thanks!
(Trying to see differences in why there are three different images on Google's site)

P4XL
From Google, bootloader unlocked
Verizon carrier
Buuld# QD1A.190821.007
This is how the device came to me on Monday, 10-29-19 :good:

Pixel 4 XL from Google
Google Fi
QD1A.190821.011 build

I don't get the difference

virtyx said:
I don't get the difference
Click to expand...
Click to collapse
It's kinda interesting that the 3 of us that posted before you, all have different build numbers and different carriers. We'll see what google does on the next update.

Badger50 said:
It's kinda interesting that the 3 of us that posted before you, all have different build numbers and different carriers. We'll see what google does on the next update.
Click to expand...
Click to collapse
My thoughts exactly. Curious to see what November brings

Pixel 4 XL
Purchased from Google Store
Carrier: AT&T
Build: QD1A.190821.007

Pixel 4 XL
Unlocked version from Best Buy on launch day
AT&T
QD1A.190821.007

4 XL 128GB
Google Store unlocked
Build ending with .007
In Canada, carrier is Fido

Google Fi Pixel 4 XL - build QD1A.190821.011.C4

Pixel 4 XL 64GB direct from Google Canada
Build# QD1A.190821.007
Currently on Virgin & Telus

Pixel 4 XL (Oh So Orange! 64gb)
Purchased directly from Google Store
Carrier = AT&T
Build = QD1A.190821.007

Pixel 4 XL 64gb
Verizon
Build QD1A.190821.011.C4

eg1122 said:
Google Fi Pixel 4 XL - build QD1A.190821.011.C4
Click to expand...
Click to collapse
same here except I'm on an AT&T locked phone

Pixel 4 XL from TMobile
TMobile
QD1A.190821.011 build
Sent from my Pixel 4 XL using Tapatalk

Pixel 4 XL
Purchased from Verizon
Came with QD1A.190821.007 out of the box
I was able to unlock my bootloader before activation YMMV
OTA Update to QD1A.190821.011.C4 within a few days
Now I have another OTA for Nov Security Update QD1A.190821.014.C2

Pixel 4 XL - 64GB
Bought directly from the Google Store (for Germany)
Carrier: Telekom (the mother of T-Mobile )
Running QD1A.190821.011 in the moment.
Bootloader unlocked.
It was rooted (Magisk via patched boot.img), but something went wrong there, I was not able to boot into recovery mode or sideload menu anymore. No OTA Update was shown at all.
So I flashed the orginal boot.img from the Factory Image (10.0.0 (QD1A.190821.011.C4, Oct 2019) and now I am downloading the OTA Update. I am thrilled, what will happen next

Pixel 4 XL - 128GB
Seller: Google Store (Germany)
Carrier: o2.de
Build: QD1A.190821.014 / Sec Patch 5th November
Bootloader: locked.
Sent from my Google Pixel 4 XL using XDA Labs

4 XL 64gb (white)
Google Website
Build ending with .014
Bought from Germany, haven't inserted any sim/carrier yet.

Pixel 4 XL 64GB Orange UK version
007 --> 011 --> 014
there is a list from google explain the differents
https://support.google.com/pixelphone/thread/18553639?hl=en

KDDI Variant?

The OTA Images download page lists two images.
One normal one, and one "KDDI only".
What exactly is KDDI? My take from Googling it is that it's some Provider.
The device I got came with said "KDDI only" Image on it (Build Number ends with ...021.A1), and VoLTE and VoWiFi aren't working, and I somehow suspect it might be the wrong image.
Makes me wonder if I can just sideload the non-KDDI OTA image to fix it? Anyone happens to have any insight there?
Edit: Just sideloading the non-KDDI OTA image does not work. Downgrade-Prevention kicks in.

Same here in the UK. My phone is running (RD1A.200810.021.A1, Oct 2020, KDDI only) but surely since i brought direct from Google, it should be (RD1A.200810.020, Oct 2020)?
I've posted on the Google product forums, to see if anyone can shed any light on the matter.

Dilbert83 said:
Same here in the UK. My phone is running (RD1A.200810.021.A1, Oct 2020, KDDI only) but surely since i brought direct from Google, it should be (RD1A.200810.020, Oct 2020)?
I've posted on the Google product forums, to see if anyone can shed any light on the matter.
Click to expand...
Click to collapse
https://gadgets.ndtv.com/mobiles/ne...ges-published-android-developers-site-2311265
KDDI network subscribers in Japan

Hey there from Germany. I pre-ordered mine direct from Google and it was delivered from UK to Germany.
Mine also has the KDDI firmware preinstalled

Same here in france, tried to install magisk with the kddi boot img and it didnt worked

I also have the 021.A1 ROM on my Pixel in Germany, I rooted with the boot image from the international 020 build however - that worked fine, and I also pass SafetyNet on basic attestation with the HideProps module. @SOSODU13016 what issues did you have exactly? Did the root not get applied when booting up? Or did your device simply not boot?

The root did not applied ?, but booting was fine

SOSODU13016 said:
The root did not applied , but booting was fine
Click to expand...
Click to collapse
Try to patch the boot image yourself in Magisk Manager, and flash it another time. It also took two tries for me for some reason until Magisk finally was installed. I've also read from others that they had to reboot multiple times.

https://forum.xda-developers.com/newreply.php?do=newreply&p=83752561
Click to expand...
Click to collapse
I'm confused, how do i know if i choose the wrong boot.img ? will i enter in a bootloop ? i'll try to patch myself with the kddi version since i'm on the 021.A1
EDIT : Ok i used my own boot.img patched with magisk based on the 021.A1 boot.img from google and it worked. Thanks everyone !

My Pixel 5 sold by Amazon UK. Came with RD1A.200810.021.A1
The box says Imported into UK & EU by Google Ireland. So doesn't look like a Japanese version.
Sent from my Pixel 5 using Tapatalk

thesebastian said:
My Pixel 5 sold by Amazon UK. Came with RD1A.200810.021.A1
The box says Imported into UK & EU by Google Ireland. So doesn't look like a Japanese version.
Click to expand...
Click to collapse
Same here but bought from Carphone Warehouse.

I'm in France, bought it from the google store, I've a kddi image too. So I don't think it's related to an oper

I've been using the Pixel 5 since Monday, but this morning I should restart my phone for a system update.
It was on version RD1A.200810.020, Oct 2020
and now RD1A.200810.021.A1, Oct 2020, KDDI only
I live in Germany and the phone also comes from Ireland.
The update process seems to be bugged.

Hi,
I've actually sent an email to the Google support regarding this topic, enquiring if it is normal for a phone purchased on the French Google Store to have a Japanese carrier variant pre-installed.
For now the request has gone through 3 different departments at Google as none of them feel sufficiently qualified to answer the question.
I'll let you know if I get any real feedback.

Hi,
same here. Bought on the german Google Store and got my Pixel 5 from Ireland shipping with RD1A.200810.021.A1
Would be interesting to see if it is possible to flash the "global" november factory image without getting a downgrade warning.
Also it would be interesting to know what the actual differences are between the global and the kddi versions.

klopsknoedel said:
Hi,
same here. Bought on the german Google Store and got my Pixel 5 from Ireland shipping with RD1A.200810.021.A1
Would be interesting to see if it is possible to flash the "global" november factory image without getting a downgrade warning.
Also it would be interesting to know what the actual differences are between the global and the kddi versions.
Click to expand...
Click to collapse
Hey I managed to install the "RD1A.200810.020" version using the android flash tool (https://www.youtube.com/watch?v=1Aadgx7fDUQ)

cheptii said:
Hey I managed to install the "RD1A.200810.020" version using the android flash tool (
)
Click to expand...
Click to collapse
Interesting. Did you notice any differences between both versions?
I'm still waiting for feedback from Google that I will likely never get. I do hesitate though to "go global" as :
1) most (if not all) European pixel 5 have been delivered with KDDI version here in Europe. Must be a reason to this.
2) I have no idea about the changes between both
3) I actually have no issues with KDDI version. I even get WiFi calling here in France from French network operator.
Will keep my eyes open.

LuMe96 said:
Interesting. Did you notice any differences between both versions?
I'm still waiting for feedback from Google that I will likely never get. I do hesitate though to "go global" as :
1) most (if not all) European pixel 5 have been delivered with KDDI version here in Europe. Must be a reason to this.
2) I have no idea about the changes between both
3) I actually have no issues with KDDI version. I even get WiFi calling here in France from French network operator.
Will keep my eyes open.
Click to expand...
Click to collapse
I didn't notice any difference. But I am sure that the global versions will be updated before the carrier specific versions.

lol, that's kinda strange.
You guys bought the Pixel 5 from EU Google store and got Japanese carrier-based firmware while I bought the Pixel 5 from Google Store Japan and got normal variant firmware.

Google changed the description with the November-Update today and it seems that they've mixed it up previously.
So the current regional versions are:
RD1A.200810.020, Oct 2020, AU & JP carriers
RD1A.200810.020.A1, Oct 2020, KDDI only
RD1A.200810.021.A1, Oct 2020, EU carriers
RD1A.200810.021.B3, Oct 2020, Verizon
RD1A.200810.022.A4, Oct 2020 (global?)
RD1A.201105.003, Nov 2020, JP carriers
RD1A.201105.003.A1, Nov 2020, AU carriers
RD1A.201105.003.B1, Nov 2020, EU carriers
RD1A.201105.003.C1, Nov 2020 (global?)
Anyway. As said, I bought my Pixel 5 from the german google store and not from a german carriers store. So I expect to be on "RD1A.201105.003.C1" instead my phone updated to "RD1A.201105.003.B1".
Still confusing but at least the "KDDI only" - discussion is solved. I guess. ?

Question Using the G998U1 (US Unlocked) version outside US

Im using the SM-G998U1 (US Unlocked) Snapdragon variant of the S21 Ultra in Pakistan.
The official latest OTA update for Jan 2023 rolled out about 15 days ago but I haven't received it on my phone yet in Pakistan.
How long does it usually take for OTA updates to roll out outside US or specifically in Pakistan after official roll out?

It depends on the region and carrier?
Did you go to Settings-System Update?

valderdark said:
It depends on the region and carrier?
Did you go to Settings-System Update?
Click to expand...
Click to collapse
The phone I have is US Unlocked version. The carrier I have the sim for is Jazz in Pakistan. The G998B i.e. the locally sold Exynos version has already gotten the update.
Yes, I have tried the Settings-Software Update

yawarkhalid said:
Im using the SM-G998U1 (US Unlocked) Snapdragon variant of the S21 Ultra in Pakistan.
The official latest OTA update for Jan 2023 rolled out about 15 days ago but I haven't received it on my phone yet in Pakistan.
How long does it usually take for OTA updates to roll out outside US or specifically in Pakistan after official roll out?
Click to expand...
Click to collapse
Did you get the update? Facing the exact same issue.

MdMahfuz said:
Did you get the update? Facing the exact same issue.
Click to expand...
Click to collapse
Hi I got the update normally. There was a delay in release of update for this region. Now updating normally on a monthly basis.
Try Smart Switch desktop app if you aren't getting the update.