Rogers Please start updating security Patches on Samsung Devices

[Dx9]

Like honestly you should be updating the security of the Samsung line of phones especially when you have already received the patch. This goes for the Note 5, Galaxy S6, and Edge. Google releases these each month. Samsung has stated they want to push out these monthly system updates. Always the carriers have to be involved? In the US they are getting security system updates for the Galaxy line. Do some good for your customers and keep their system up to date with security like Apple does for iPhone. You have the system update from Samsung so start updating your customers system.

***Edited Labels***

[jmatteis]

Quick question.  I ported out to Koodo, and my phone was originally with Rogers.  It is unlocked and working on Koodo network, so how do I get my updates on my S7 now?  Will Rogers push it, or Koodo?  Or do I go to Samsung?  I still have all the Rogers bloatware on here unfortunately.

[gp-se]

---

@jmatteis wrote:

Quick question.  I ported out to Koodo, and my phone was originally with Rogers.  It is unlocked and working on Koodo network, so how do I get my updates on my S7 now?  Will Rogers push it, or Koodo?  Or do I go to Samsung?  I still have all the Rogers bloatware on here unfortunately.

---

I would suggest you backup everything on your phone using Samsung Smartswitch. 

Once everything is backed up, you can change the CSC Code on the phone to Koodo/Your Current Provider. You can google "Samsung CSC Code" to learn how to change the CSC code, I would suggest doing it since your not with Rogers anymore. 

However once you change your CSC, the phone will be Wiped/Erased and reset to factory defaults, this is why you need to backup everything. 

After doing all that your phone will still be unlocked, but better suited to Koodo, and will get updates from Koodo.

[IainS]

Im sorry but Rogers process for getting security updates out to customers is laughable at best. Both my Samsung S8+ and Note 8 are still on the Android November security update, it in January 2018 now Rogers. There is no way you should be behind 2 months in issuing security updates to customers. Your tech team and approval process for security updates needs to be updated to reflect the seriousness of having up to date security measures on ones devices. There is a major security flaw that was fixed in the December patch and another major issue that was fixed in the January patch. ROGERS WITH YOUR SLOW AS MOLLASES APPROACH TO GETTING SECURITY UPDATES OUT TO CUSTOMERS IS LEAVING THEM WITH UNSECURE DEVICES. We as Rogers customers need better from you. Start making these patches available right away. Dont pass the buck onto the OEM as they have had these available to carriers right away.

[RogersShaun]

Hello @IainS,

As a fellow Note 8 user, I completely understand where you're coming from.

As stated previously in this thread, security is a top priority at Rogers and we continue to work with all device manufacturers to roll out any security updates as soon as we can.

Rogers releases all security updates from OEMs once verification has been completed. Once a GMR (General Maintenance Release) or EMR (Emergency Maintenance Release) is ready, your device will prompt the OTA download option.

As always, stay tuned to the OS Update Schedule.

RogersShaun

[bismarck]

This is simply false, as a former Note4 owner and now S8, Samsung released monthly updates that you never released (only GMR and critical fix). For the S8, you're still lagging behind by 2 months of updates. Carrier don't really care about security, they need to make sure their crapware still works.

For S8, 1-SMR-DEC-2017 has been released

Critical
CVE-2017-11013, CVE-2017-11015, CVE-2017-11014, CVE-2017-0427, CVE-2017-0872, CVE-2017-0878, CVE-2017-13151, CVE-2017-13160, CVE-2015-3868, CVE-2017-0675, CVE-2017-6211

High
CVE-2017-0871, CVE-2017-9077, CVE-2017-7541, CVE-2017-0843, CVE-2017-11092, CVE-2017-11028, CVE-2017-0838, CVE-2017-0807, CVE-2017-0870, CVE-2017-13153, CVE-2017-0837, CVE-2017-0873, CVE-2017-0874, CVE-2017-0880, CVE-2017-13148, CVE-2017-13156, CVE-2017-13157, CVE-2017-13158, CVE-2017-13159, CVE-2017-13077, CVE-2017-0879(L5.1, M6.x), CVE-2017-13149(L5.1, M6.x), CVE-2017-13150(M6.x)

Moderate
CVE-2017-11057, CVE-2017-11059, CVE-2017-11061, CVE-2017-11060, CVE-2017-11052, CVE-2017-11064, CVE-2017-0861, CVE-2017-1160, CVE-2017-11073, CVE-2017-11035, CVE-2017-11012, CVE-2017-11085, CVE-2017-11091, CVE-2017-11032, CVE-2017-11024, CVE-2017-11025, CVE-2017-11023, CVE-2017-11029, CVE-2017-11018, CVE-2017-9702, CVE-2017-11089, CVE-2017-8239, CVE-2017-11090, CVE-2017-11093, CVE-2017-8279, CVE-2017-9696, CVE-2017-11058, CVE-2017-11022, CVE-2017-0879(N7.x, O8.0), CVE-2017-13149(N7.x, O8.0), CVE-2017-13150(N7.x, O8.0), CVE-2017-13152

and 

SMR 1-JAN-2018

Critical
CVE-2017-11043,CVE-2017-13177, CVE-2017-13178, CVE-2017-13179, CVE-2017-13208

High
CVE-2017-13162,CVE-2017-0564, CVE-2017-7533, CVE-2017-13174, CVE-2017-14904, CVE-2017-14897,CVE-2017-14902, CVE-2017-14895, CVE-2017-14914, CVE-2017-11005, CVE-2017-13077,CVE-2017-13176, CVE-2017-0770, CVE-2017-13180, CVE-2017-13181, CVE-2017-13182,CVE-2017-13184, CVE-2017-0855, CVE-2017-13191, CVE-2017-13192, CVE-2017-13193, CVE-2017-13195,CVE-2017-13196, CVE-2017-13197, CVE-2017-13199, CVE-2017-13209, CVE-2017-13210,CVE-2017-13211, CVE-2017-13185(L5.1, M6.x), CVE-2017-13187(L5.1, M6.x),CVE-2017-13188(L5.1, M6.x), CVE-2017-13203(M6.x), CVE-2017-13204(M6.x),CVE-2017-13205(M6.x), CVE-2017-13186(M6.x), CVE-2017-13189(M6.0.1),CVE-2017-13190(M6.0.1), CVE-2017-13194(L5.1, M6.x), CVE-2017-13198(L5.1, M6.x)

Moderate
CVE-2017-13163,CVE-2017-15868, CVE-2017-1000380, CVE-2017-13168, CVE-2017-13169,CVE-2017-13164, CVE-2017-9708, CVE-2017-11030, CVE-2017-9703, CVE-2017-8244,CVE-2017-14901, CVE-2017-9700, CVE-2017-9722, CVE-2017-11049, CVE-2017-11047,CVE-2017-14899, CVE-2017-11044, CVE-2017-11045, CVE-2017-14900, CVE-2017-9710,CVE-2017-11019, CVE-2017-11016, CVE-2017-11033, CVE-2017-8281, CVE-2017-14903,CVE-2017-11031, CVE-2017-14905, CVE-2016-5341, CVE-2017-15813, CVE-2017-13201,CVE-2017-13202, CVE-2017-13206, CVE-2017-13207, CVE-2017-13185(N7.x, O8.0),CVE-2017-13187(N7.x, O8.x), CVE-2017-13188(N7.x, O8.x), CVE-2017-13203(N7.x, O8.x),CVE-2017-13204(N7.x, O8.x), CVE-2017-13205(N7.x, O8.x), CVE-2017-13200(L5.1,M6.x), CVE-2017-13212

Low
CVE-2017-13200(N7.x,O8.x)

NSI
CVE-2017-13186(N7.x,O8.x), CVE-2017-13189(N7.x, O8.x), CVE-2017-13190(N7.x, O8.x), CVE-2017-13194(N7.x,O8.x), CVE-2017-13198(N7.x, O8.x), A-68810306

[IainS]

so is this why Samsung have already released Jan 2018 patch and Rogers Samsung devices are all still sitting on the Nov 2017 security patch. I have over $3000 worth of Samsung devices with Rogers and find this totally unacceptable.

still not acceptable that Rogers is 3 months behind on Samsung security updates.

so you are telling us that you take more than 3 months to issue android security updates???? this is totally unacceptable.

well that's great to hear but you are now 3 months behind issuing security updates, Samsung has released the Jan 2018 android security patch and Rogers has yet to approve and release the Dec 2017 patch?? what gives here Rogers needs to get with the times and have a separate process for issuing security level patches than they do with a complete OS upgrade.

[teohatz]

Could be that they are waiting until Oreo is released? Doesn't make sense from a security standpoint. This is pure laziness. January will be over in 8 days and as an S8 Owner, I am still on the November 2017 Security Patch and it is frustrating! I cant even imagine when we will get Oreo from Rogers when it actually drops. Doubt it would be a month later. 3 or 4 months later perhaps? Either way, Security updates are critical to making sure that the device is running safely. Step your game up, Rogers. Jeez. Huge mistake on my part for getting a Samsung Phone, should have went with the Pixel, at least I would be getting updates directly from Google.

---

[IainS]

Yes Rogers needs to understand that these security updates are NOT OS updates and needs to start handling them different. Someone that actually matters with decision making privileges needs to be reading this, not forum mods. I doubt that we will see Oreo until closer to the end of summer, even though it will be released next month by Samsung.

[shaggyskunk]

Noticed that the OS Update Schedule needs some work.. It was updated last Friday and didn't show any pending or future updates for the SM-G955W. RogersHelps on Twitter also didn't have any information.. But around 3 am on the 29th of January the January Security Patch update was finally pushed by Robert... SEVERAL Days after Bell, Virgin and SaskTel.
A Security Patch of less than 50 Meg should be a PRIORITY and being told by a Rogers rep that it "needs to be tested" is utter nonsense!
Let's hope that Rogers is on the ball with the Oreo update for the SM-G955W!

[RogersDarrell]

Hi @shaggyskunk

I was actually able to confirm this morning that the S8 and S8 Plus December and January security update MR was released in batches on January 26th. Unfortunately the release notification missed our reporting window.

The OS Upgrade schedule has been updated at this time. Feel free to check it out here.