Former Writer · May 23, 2012 at 11:00 am

TWRP 2.1 to be Ported to the Epic Touch

The Team Win Recovery Project has been picking up major steam for awhile now. And since its update to version 2.1 that we covered not too long ago, it’s been getting closer and closer to being one of those must have recoveries on newer devices. Unfortunately however, not every device has made the list quite yet. That doesn’t mean it can’t be.

Samsung Epic 4G Touch users have been clamoring for a TWRP 2.1 release for some time now, and XDA Recognized Developer Dees_Troy wants all the Epic Touch users know that Team Win is listening. While Team Win can’t personally get the recovery working on the Epic Touch, as they don’t have the Epic Touch to test it, Dees_Troy wants to spur the device’s already vibrant development community:

The TWRP source code is all public, including the GUI. It’s pretty easy to compile and work with and we have a nice guide to help you out here: http://tinyw.in/nP7d

If you need help integrating TWRP into your builds or have questions about compiling TWRP, feel free to find us in #twrp on Freenode.

So this begs the question, why the complicated response from Team Win? Well the answer, as expected, is rather complicated as well. As with most Samsung phones, there isn’t a proprietary recovery partition. Or rather, as Dees_Troy calls it, they don’t use a proper recovery partition. What actually happens is that the recovery is packed into the boot.img. This means that whenever a user installs a new kernel, they’re stuck with whatever recovery comes with that boot.img. As many Epic Touch owners will tell you, there’s a few different recoveries roaming around depending on which kernel you flash. This makes porting the recovery a little more difficult than normal because you not only need to port the recovery so it works, but you also have to compile a kernel in which to pack it. So, Team Win has made the code available for anyone who wants to go through all that for the Epic Touch.

For additional discussion and information, check out the original thread and let the porting begin!


_________
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 · Jul 7, 2015 at 06:00 am · no comments

How to Lock and Protect Your Apps – XDA Xposed Tuesday

The smartphone revolution has passed. Everybody has mobile apps. Some of these apps have access to very important information. Your mobile banking app gives you access to your money. Your Dropbox app could hold your secret plans to world domination. These apps should have greater protection than your Trivia Crack game. In this episode of XDA Xposed Tuesday, XDA TV Producer TK reviews an Xposed Module that enables you to control access to your apps. XDA Senior Member defim created...

XDA NEWS
Mario Tomás Serrafero · Jul 6, 2015 at 12:49 pm · 14 comments

Which OEM Would You Like to Help?

Most manufacturers have moments of greatness and moments of decadence, and in the past few years we've some of our favorite companies' tables turned. Some are stagnating, some are struggling, some lack direction. Despite this, we often hold them dear to our hearts. Many of them could use a hand, be it with design, marketing, or other tasks. If you could help out an OEM and take it back to its golden days, which one would it be?

DISCUSS
Aamir Siddiqui · Jul 6, 2015 at 11:03 am · 5 comments

Root T-Mobile S6/Edge on 5.1.1 Without Tripping Knox

If you purchase phones from a carrier, you may be no stranger to the difficulties involved in rooting and installing a custom rom, recovery and kernel on such a carrier locked device. Add to this the extra layer of security that Samsung adds in the form of the Knox counter on its devices, and one can only imagine the roadblocks for enthusiasts who want to play around with their device without losing warranty in the process. It's a slippery slope...

XDA NEWS
Share This