Former Writer · Jul 13, 2012 at 12:00 am

Bypass the Locked Bootloader on the Verizon Galaxy S III

It can be said that development on the Verizon Samsung Galaxy S III has been a struggle. What was once anticipated to be a utopia of development between the four major carriers due to having nearly identical Galaxy S III devices has been marred by the locked bootloader on the Verizon version. Understandably, this has somewhat stifled development for the device, as the other three US variants rush forward at a breakneck pace while Verizon developers are held at the starting line.

This is a problem that CMTeamEpic is looking to fix. By reviving a concept Motorola Droid RAZR members will recognize, CMTeamEpic plans to get beyond the locked bootloader using Kexec, the bootloader workaround. The premise is to install a custom kernel in such a manner that it boots from the recovery instead of from the bootloader. CMTeamEpic explains:

Also recently, we’ve finished porting kexec hardboot—a method of booting kernels through recovery without needing to flash them to the device—to the Sprint SGS3, a feature that would also enable Verizon SGS3 users to make use of custom kernels despite the locked bootloader.

Despite being a breakthrough in development, the process is far from being complete. The ability to use a custom kernel is actually successful, but there’s a few unusual problems that CMTeamEpic are running into. The most interesting of which is that, once booted with the custom recovery, using the power menu to reboot the device automatically takes users back to recovery. Additionally, Kexec for the Galaxy S III is still being touted as a proof-of-concept process, so users should definitely be cautious while using it, as there can be some serious issues. CMTeamEpic released the standard boilerplate:

This is a proof-of-concept kernel intended for developers and experienced testers. It offers no new features in addition to the stock kernel. While we don’t expect these kernel images to cause touble, improper installation of these kernel images may cause irreparable harm. Use at your own risk.

For additional discussion, check out the original thread.


_________
Want something on the XDA Portal? Send us a tip!
Emil Kako · Jan 31, 2015 at 02:59 pm · 1 comment

Do You Prefer Physical or on Screen Buttons?

More and more smartphone manufacturers have been moving towards on-screen buttons, with Google really pushing for it over the physical button alternative. However, there are still a few OEMs (we're looking at you, Samsung) that have preferred to keep things a bit more traditional. Tell us which way you prefer and why.

DISCUSS
Pulser_G2 · Jan 31, 2015 at 02:08 pm · no comments

New AOSP Branch Details Potential Build System Upgrades?

While there are frequent unexplained changes and pushes to Google's AOSP repositories, an interesting-looking new branch has been pushed out recently, called "master-soong". Taking a look at the changes made to the manifest repository (which is used to specify the repositories to be downloaded when building Android), it appears there are some new repositories making an appearance. Of note here are new prebuilt repositories for Go, and Ninja. Go is a programming language, created by Google, which compiles to produce...

XDA NEWS
GermainZ · Jan 30, 2015 at 09:29 pm · 1 comment

Send Links to Any Nearby Device with CaastMe

There already are many solutions on the Google Play store if you want to send a link to one of your devices -- but what if you wanted to do it quickly without having to install any software or logging in to a website on the recipient end? Most apps require you to do either or both, which can be a hassle (or even a security risk) in some cases. Luckily, XDA Forum Member wyemun has developed CaastMe. Inspired by...

XDA NEWS