T-Mobile U.S.A. is now sending out an OTA update for Samsung Galaxy S Blaze 4G, which is packed in Android 2.3.6 Gingerbread. The new baseband build version is T769UVLF5 and according to T-Mo it will adds-up security enhancement. Yes folks, you heard it it’s 2.3.6 GB and don’t ever ask me why it is reverting back to 2.3.6 Gingerbread when they already released the 4.0.4 Ice Cream Sandwich build T769UVLH5 last October.
Well, maybe this is an important update though, when I read the word “security enhacement” from the changelog. It reminds me some sort of “memory bug exploit fix” that has been also released in some international devices lately like the Samsung Galaxy S3, but I think it’s not, since international variants runs with ‘Exynos’ as opposed to U.S. variants mostly runs with ‘Qualcomm’ processors. Or, maybe this is a preparation for the Jelly Bean that might coming soon, who knows?
T-Mobile has been releasing this “Security Enhancement” update lately, not just only for the Samsung Galaxy S Blaze 4G but also almost all of their Samsung slates, the Samsung Galaxy Note SGH-T879, Samsung Galaxy S III SGH-T999, Samsung Galaxy S II SGH-T989 and the Samsung Galaxy S Relay 4G SGH-T699.
Beginning February 4, the Samsung Galaxy S Blaze 4G (Gingerbread only) will have a software update to Android version 2.3.6 / Baseband T769UVLF5 via OTA and Samsung Kies. This update improves security and provides an improved user experience.
You can update in two ways:
Over the air (OTA) update to Baseband T769UVLF5: See below steps to manually request the OTA update.
Manual download to T769UVLF5: If you want to update to T769UVLF5 via OTA or the OTA notification is not received, you can update via Samsung Kies. Ensure you are on the latest version of Kies prior to attempting the update. See http://www.samsung.com/us/kies/ to confirm the version.
Get to know better details about this update for I don’t have any more ideas of what’s this update is all about., Just head over to T-Mobile official support page – http://support.t-mobile.com/docs/DOC-4182
If you have something about to add, just drop it on the comment form below.