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!

Former Writer

Former Writer is an editor on XDA-Developers, the largest community for Android users. View Former Writer's posts and articles here.
Jimmy McGee · Mar 31, 2015 at 07:00 am · 2 comments

Fix Lollipop Memory Leak – XDA Xposed Tuesday

Unfortunately there was a memory leak in Android 5.0.x Lollipop. Thankfully it was fixed in Android 5.1. However, at the time of this video Xposed Framework doesn’t have Android 5.1 support. So you are faced with a choice of fixing the memory leak or running your Xposed Modules. Or are you? In this episode of XDA Xposed Tuesday, XDA TV Producer TK reviews an Xposed Module that adds the Android 5.1 memory fix to pre 5.1 Lollipop devices. The module...

XDA NEWS
Mario Tomás Serrafero · Mar 30, 2015 at 11:00 pm · 2 comments

Would The LG G4 Fare Well With The Snapdragon 808?

The LG G4 has a lot to prove, given that last year’s LG G3 was among the best smartphones of 2014. The Global Mobile Awards given out during the time of MWC 2015 named it the Smartphone of The Year (SOTY?) alongside the iPhone 6, and at the time of its release it packed the very best in Android specifications, from the powerful Snapdragon 801 to the class-leading 1440p display. The camera, battery life and feature set were also deemed...

XDA NEWS
GermainZ · Mar 30, 2015 at 02:41 pm · 3 comments

DexPatcher: Patch Android APKs Using Java

You've probably seen or installed modified applications, be it a patched dialer for your resolution or a custom WhatsApp version with added features. How do developers do that, though? A lot of the time, the applications' source code isn't even available, so how does it all work? We'll see that first, then take a look at a new tool that aims to make the process much easier, and finally compare it to the popular Xposed framework to see how they...

XDA NEWS
Share This