Current security patch level?

[RayfenWindspear]

I have decided to keep this thread current as new potential updates are posted. If you have just gotten an update that is more recent than I have listed, please share it and I'll update to match.

Security Patch: March 1, 2018
Wear Version: 2.6.0.176354550 (Unchanged*)
Google Play Services: 11.7.46 (530-175121617) (Unchanged*)
Build Number: NWD1.180306.004

*See related post


(Content before edit)
I forced my watch to install wear 2.0 and I haven't received an update since. I just wanted to see if anyone has seen any new updates, or if anyone knows if they've discontinued support?

P.S. I had to sideload wear 2.0 manually. I have a theory that LG actually disabled the OTA which, if true, suggests they have discontinued support altogether. None of the standard tricks would work to trigger the OTA (unpair, wipe, connect, check for updates, rinse, repeat).

 

[mdw1995]

I'm still on the May security patch but I have received a few updates of the AW version since sideloading 2.0. The most recent one I received through the watch's Play Store yesterday. I'm currently on 2.0.0.166998750.

 

[RayfenWindspear]

Just got an update today that pushed my security patch level to August 1st. Of course, I get the update the VERY DAY that the BlueBorne exploit shows up everywhere. Here's hoping for a fix for that soon. At the very least, the watch hasn't been abandoned yet.

BlueBorne exploit info.
Link omitted due to the auto spam flagger. Google it.

My current versions as of this post.
Security Patch: August 1st
Wear Version: 2.0.0.166998750
Google Play Services: 11.5.09 (530-164803921)
Build Number: NXH210

 

[StimulatorCam]

I have a theory that LG actually disabled the OTA which, if true, suggests they have discontinued support altogether.

But my W200A got the AW 2.0 update build NXH20E through OTA back in July. Or do you mean just for this new patch?

 

[RayfenWindspear]

But my W200A got the AW 2.0 update build NXH20E through OTA back in July. Or do you mean just for this new patch?

I think they may have disabled the Wear 2.0 OTA for pre 2.0 watches as of August. Mine didn't have it then and all the tricks that everyone was using to get the OTA weren't working. I unpaired and factory reset the thing over a half dozen times. It's just a theory, but you got yours in July, so who knows. At least we've just gotten an update, so it seems they haven't abandoned the watch.

Of course, now they immediately have to start working on another update due to the BlueBorne exploit...

 

[kbboykin]

Several members on XDA have gotten an OTA update to 2.0 from 1.5 in the last day or so, so looks like they may be rolling it out.

 

[RayfenWindspear]

Several members on XDA have gotten an OTA update to 2.0 from 1.5 in the last day or so, so looks like they may be rolling it out.

I actually just read that 1.5 => 2.0 was a carrier update, and as I didn't have an AT&T plan and kept my cell off, it would explain why I never got it.

Also, I emailed LG about patching the BlueBorne exploit. The response I got was noncommittal, but somewhat encouraging. I believe that they will eventually roll out the Sept(+) security patches to fix it, but the issue is "when". Seems it takes them a long time to roll out updates. So glad that Oreo is finally addressing that problem.

 

[Jaycemiskel]

I actually just read that 1.5 => 2.0 was a carrier update, and as I didn't have an AT&T plan and kept my cell off, it would explain why I never got it.

Also, I emailed LG about patching the BlueBorne exploit. The response I got was noncommittal, but somewhat encouraging. I believe that they will eventually roll out the Sept(+) security patches to fix it, but the issue is "when". Seems it takes them a long time to roll out updates. So glad that Oreo is finally addressing that problem.

I don't think that's the case. I don't have AT&T and mine downloaded over Wifi. Just got it a few days ago.

 

[RayfenWindspear]

I don't think that's the case. I don't have AT&T and mine downloaded over Wifi. Just got it a few days ago.

You got Aug 1st patch, which was a re-push not through carrier. The original OTA to 2.0 was back in July.

 

[Jaycemiskel]

You got Aug 1st patch, which was a re-push not through carrier. The original OTA to 2.0 was back in July.

I never had 2.0 though. This was my first time to get it.

 

[RayfenWindspear]

I never had 2.0 though. This was my first time to get it.

That's exactly what I'm pointing out. The original 2.0 OTA was a carrier push, which is why you are only getting it now. The newest one was not through carrier, so now all the people who never got it before are finally getting it.

 

[Jaycemiskel]

That's exactly what I'm pointing out. The original 2.0 OTA was a carrier push, which is why you are only getting it now. The newest one was not through carrier, so now all the people who never got it before are finally getting it.

I thought updates usually built upon the last update, but oh ok.

 

[mdw1995]

Received an update today with the November 6, 2017 security patch.

 

[StimulatorCam]

Same here, was a little bit surprised to get any update at all after hearing it won't get Oreo.

 

[RayfenWindspear]

Yep, I can also confirm. For those who got it, did anyone else's watch drop bluetooth AND Wifi to download the update over cellular? I was able to add the APN for FreedomPop and have been using that, so I got an alert when it suddenly dropped 350mb and almost cost me a chunk of change for usage.

We are in luck with the update. It includes the patch for Blueborne (which was my real concern at the time) and KRACK, which barely slid in with it being Nov 6. Bluetooth is probably the bigger issue with most wearables though.

In light of recent news regarding Spectre and Meltdown, I don't think wearables are at serious risk for those exploits, but I could be wrong. They have a low market share compared to other platforms and a much more limited scope than other prospects for exploitation (just my take, don't quote me on that).

 

[RayfenWindspear]

Not sure when, but March 1, 2018 security patch hit my watch.

Security Patch: March 1, 2018
Wear Version: 2.6.0.176354550 (Unchanged)
Google Play Services: 11.7.46 (530-175121617) (Unchanged)
Build Number: NWD1.180306.004

If anyone has a higher version of Wear or Play Services, shout it out. I'm sure mine is unchanged because I'm refusing to factory reset at the moment to fix the dreaded "Download Pending" bug with the play store, so I can't update anything. I might try to find the latest version of play and sideload it. I don't want to factory reset because I added the APN for my FreedomPop SIM and I'd lose that in the process.

 

[StimulatorCam]

I also have the March 1 security patch and same Build Number, but have the following:

Wear OS: 2.12.0.197555195
Play Services: 12.6.85 (050300-197041431)