Samsung Updates the Galaxy S6 Edge Plus, A5 2017, A5 2016 with July security patch

Samsung is quite on a roll this month in keeping its promise to provide monthly updates. This time the tech giant is not only keeping its Flagship devices updated but also its mid-range devices are being updated as well. Now the Samsung has the new update goodies for four of its devices, for the month of July. These little security updates from Google keep your Android devices safe from the latest malware attacks and fixes vulnerabilities.

The devices getting these new updates are in total four of them. The Galaxy A5 2016, A5 2017, the real old Note Edge and the Flagship Galaxy S6 Edge Plus. The update is arriving over the air for the following build number of Galaxy S6 Edge Plus.

  • G928GUBS3CQG1 (Galaxy S6 Edge Plus)

And another device is receiving the update with the build number.

  •  N9150ZCS1CQG1 Galaxy Note Edge (Chinese variant)

Samsung also has the same July security update for its mid-range devices such as the Galaxy A5 2015 and A5 2017 with the following build numbers.

  • A510FXXU4CQG1 (Galaxy A5 2015)
  • A520FXXU2AQG6 (Galaxy A5 2017)

Samsung is fulfilling the call of giving monthly security updates for its Flagship devices as promised by them earlier which is a good thing for both the Company and the users.


OTA updates are always released in phase by phase according to the region, so don’t worry if you haven’t got the Notification yet. To do a quick manual check head over to Settings > About device > System updates. Make sure to backup your important data before updating as a failure while updating can cause data loss.

Akshay Mhatre is a Tech Journalist who likes to keep up with the latest from the tech world. He has worked at many popular news portals like BGR and TechRadar before joining TheLeaker as a News writer and journalist. A writer by day and a VFX artist by night. In his free time, he also likes to make motion graphics and concept art. You can find him on Instagram @akshayrazr_95 and contact him on akshaymhatre[@]

Leave a Comment