Jump to content



About The Author
Derek De La Cruz
Derek has been an Android fanatic since the beginning but has been involved with the Android Community since 2010. He has had many Android devices which include T-Mobile G1 (1st device), MyTouch 3G, Google Nexus One, T-Mobile G2, Samsung Galaxy Tab and currently owns a Galaxy Nexus GSM, Amazon Kindle Fire, Galaxy S 2, Google CR-48. Derek started my own Android project as Co-Founder of Andranon.com but have then decided to join Android Activist to continue covering Android News & Applications. He is always in the mood to talk tech, android, and sports so hit him up.

Samsung Releasing Galaxy S III Developer Edition to Bypass Verizon's Bootloader Policy

Verizon is notorious for demanding OEMs to lock up their bootloaders. Reports indicate the reason behind Verizon Bootloader Policy is that; "an open boot loader could prevent Verizon Wireless from providing the same level of customer experience and support. (Full Statement)" Fortunately, Samsung understands the value of an open device for developers so instead of going head on with Verizon they are going around them. Samsung will be offering a $599 Developer Edition of their latest flagship device, the Samsung Galaxy S 3. This device will work on Verizon but will have an unlockable Bootloader.

Why is a locked Bootloader bad? It makes it difficult and at times impossible to root & run custom ROMs. This is great news for our community and for developers looking to support the SGS3 on Verizon. The device is unsubsidized and only sold by Samsung. Therefore, the $599 price tag will be unappealing to most but this device is not meant for everyone.

If you happen to purchase this device, be aware that "Verizon will not provide support for users with problems, and phones with unlocked bootloaders and custom software won't be covered by the handset's warranty." I guess this is the price you pay for openness. The sale of this developer device is not yet active but will begin soon.
Sources [Engadget], [Samsung Developers]

blog comments powered by Disqus