December 18, 2013 By: eagleeyetom
A custom recovery is where most of the aftermarket magic happens in Android. Using one, you can backup your ROM, wipe your data, and of course flash a new ROM. In contrast to fastboot, recoveries can flash ROMs even on locked devices. There are some workarounds required, but it can be done.
Owners of AT&T variant of Samsung Galaxy Note 3 now have a working recovery thanks to XDA Recognized Developer Hashcode, who used a bootstrap method in order to make his fully working recovery. The method used by Hashcode differs from the standard method used in, for example, the Nexus 5. This type of bootstrap recovery preserves the /system partition and creates up to 2 “ROM slots” located on the internal eMMC area: /sdcard. Basically, the custom ROM acts like a second /system partition on the device. Once the second slot is activated, a standard TWRP-based recovery flashes all necessary files.
The size of the second partition is adjustable, but you need to remember that more slots mean less space for other ROMs. The recovery can be installed as an application and doesn’t require messing with the /system partition. The development is still in alpha stage, and some bugs may be present, but it’s still a great start!
[Big thanks to XDA Forum Member dirtydroidx for the news tip!]
August 13, 2013 By: Jimmy McGee
We have talked about the Oppo Find 5 before. This relatively unknown phone manufacturer (though well known for their home entertainment equipment) has created a lot of buzz recently. To be honest, this video is going to continue that buzz. And rightfully so, as the Oppo Find 5 is easy to root and install a custom recovery.
In today’s video, XDA Developer TV Producer Kevin talks about the Oppo Find 5′s features. He then talks about how to install a custom recovery. Once you get there, you can flash a SuperSU APK from Recovery and you are rooted. Check this video out.
A custom recovery is an incredibly useful tool for anyone who wants to make the most of his or her (rooted) device. Even if you aren’t a fan of custom ROMs or kernels, you probably still use a custom recovery if for nothing but the ease of backing up and restoring your device. There are of course many other reasons why you might find yourself diving in and out of recovery, and that is a process which can become tedious.
That’s where TWRP Manager by XDA Recognized Developer and Forum Moderator jmz comes in. The application allows the user to initiate recovery functions without rebooting by using OpenRecoveryScript commands. TWRP is one of the most popular options available when it comes to custom recoveries, and with a wealth of features above and beyond the norm as well as support for a lot of the most popular devices available, it’s easy to see why. TWRP Manager mirrors the distinctive recovery UI that you are already familiar with. It allows you to flash, wipe, and restore your device easily without the need to reboot or use a button combination.
It’s important to note that the application is still in beta, so there will be bugs. However, if that’s not something that bothers you and TWRP is your recovery of choice, this is well worth a look. Head over to the original thread for all the details.
We don’t usually cover individual custom kernels here on the Portal for the simple reason that thanks to the development community, there are so many great options available that we wouldn’t have time to cover anything else. However, every once in a while, a kernel developer brings so much awesome to the table that it would be downright rude of us not to sit down and stuff our faces until we are fat and happy. Devil Kernel by XDA Recognized Developer DerTeufel1980 definitely falls into that category.
This is no ordinary Note 2 kernel. It’s a Linux 3.0.80 kernel based on the sources of the popular Perseus kernel that many Note 2 owners will no doubt be familiar with. The crucial (but by no means only) difference though is that Devil (in conjunction with DerTeufel1980′s custom recovery) will allow you to dual boot your device by splitting the system partition and enabling you to have two different ROMs installed at the same time—even a combination of AOSP- and TouchWiz-based ROMs.
This does take a little bit of setting up and there are some things that you will certainly want to be aware of before diving into this, so as always make sure to read through the details thoroughly before just throwing things at your device to see what sticks. Once set up, this is an incredibly beneficial option for those of you (and indeed myself) who are torn between a stock or AOSP firmware for this device. And yes, for those of you with an N7105 or AT&T/T-Mobile variant, you’re not being left out . There is a version of the kernel and recovery for these devices too.
Check out the original development thread for more information.
Some time ago, we gave the Android-powered Ouya game console a place in our forums. Since then, we’ve not heard too much about this curious little non-phone/tablet device other than a guide to help users connect via ADB, sideload apps, and obtain root access and some as of yet fruitless efforts towards UART and Play Store access.
Luckily, this development lull has been interrupted thanks to XDA Forum Member mybook4, with some help from Forum Member sonofskywalker3 and Recognized Developer rayman. Mybook4 managed to port an unofficial CWM build to the device.
To install the CWM port on your own device, you need to first achieve root. To do this, visit Forum Member tcollum‘s root thread linked in the introduction. After you’ve achieved root access, fastboot boot into a recovery image stored on your computer. Once in the temporary recovery, flash a recovery-flashable update.zip for permanent recovery access.
Those interested in getting started should head over to the recovery thread. To learn more about the process, and how sonofskywalker3, mybook4, and rayman achieved this, visit the development project thread.
May 23, 2013 By: Mike Szczys
Those of us who use Linux on a day to day basis don’t think twice about sinking our fingers into the system files that govern how our devices perform. For instance, I use an LG L9 and was quite comfortable playing around with the way my SD card was being mounted in order to improve performance. For those who aren’t at home with the way the OS works, adding a startup script with a few lines of code might as well be witchcraft. That’s why flashable zip files are so handy for simple tasks and indispensable for complex projects. If you do it right, all the end-user needs do is copy a file to his SD card and reboot into recovery to flash the package.
There are some automatic tools out there that can help create these files. In fact, we’ve already covered at least one of them. But there’s really no substitute for knowing exactly what goes into one. XDA Senior Member Denkantor can explain it all, and decided to make an XDA University guide on package for flashing from recovery. Head on over to his original thread to see what he’s up to.
It doesn’t take much to make an update.zip file. Denkantor likes to use 7zip. And if you’re on Windows, he recommends Notepad++. You’ll also need the file(s) you want to flash. The Edify scripting language is what a custom recovery is looking for. You’ll be guided through the basics, but learning more is easy since you can look at any flashable file as an example.
April 18, 2013 By: Conan Troutman
Up until recently, it was possible to take a screenshot of your recovery of choice using DDMS. This option, however, no longer works with some newer HTC devices. Now why is this a problem? Who needs a screenshot of their recovery? Well for a start there are themers who work with the ever popular TWRP. Additionally, it may just end up being useful in a troubleshooting situation. Whatever the reason, it used to be possible but now it’s not. And for XDA Recognized Developer/Themer Whiskey103, that needed to be resolved.
The solution that he devised comes in the form of a script used to take screenshots via ADB using an open source project called android-fb2png by Kyan He. The actual software itself comes in two parts, one for the PC and one for the device. Whiskey’s script will allow you to grab a screenshot in a timely and hassle free manner, upon execution the script will automatically push the relevant files to your device, run the desktop application, and then pull the screenshot into your ADB folder for you. Job done.
We understand that taking screenshots of your recovery environment might not exactly be a priority for many people, but that’s no reason for it not to be possible. If this is something you can make use of then be sure to check out the forum thread for more information.
Muchas gracias to M_T_M for the tip.
April 16, 2013 By: egzthunder1
We have had some rather long running projects on XDA over the years. Some involve simple, yet elegant things like theming engines (UCCW, VR Theme, etc), while others focus a bit more on the functionality side of things. The case for recovery images is one such area that needs to be constantly evolving due to the evolution of the devices and their inner workings. Pushing an insecure recovery into a device is not always easy. Or rather, it is not as simple as some people make it be. Lots of things and information are required even before beginning the process of loading it onto a new device. For XDA Recognized Developer Dees_Troy and other members of Team Win, this has been the case for a while now, but they always tend to come out on top.
TWRP (Team Win Recovery Project) is an open recovery project that has been around for a couple of years now. It is a great alternative to the ever popular CWM if you are looking for something with a bit more flair and functionality. This new version, which stands at 188.8.131.52, is loaded with updates and fixes. These changes make the overall experience smoother and more enjoyable. For instance as of version 184.108.40.206, TWRP was given the ability to turn off the screen to save battery while in recovery. Version 2.5 takes that concept a step further and not only allows the user to select the timeout, but now even the screen brightness can be tweaked as well. On top of that, partition handling and selection has been vastly improved, and it is now easier to use thanks to the implementation of a scrollable list. And as if that weren’t enough, not being in the Android UI should not mean that you cannot enjoy a good looking recovery with our ever-growing-pixel-packed screens. So, a theme for 1080 x 1920 was added for devices like the Xperia Z, HTC One, and others. And speaking of which, the recovery is now available for the new beast from HTC… the One.
Please do keep in mind that the new version is still undergoing somewhat heavy testing and there are some bugs that you may run into. On the other hand, if you manage to get this installed, rooting the One will be as simple as using the built in tool to inject SuperSU. Please take it for a spin and report feedback and bugs that you may run into.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer.
[Thanks to OEM Relations Manager jerdog for the tip!]
March 2, 2013 By: Haroon Q. Raja
The Team Win Recovery Project has been on a roll lately, adding several new features including auto screen timeout and built-in SuperSU flashing in the 220.127.116.11 update just a few days ago. Things are getting even better, as XDA Recognized Developer Dees_Troy and team have just released the 18.104.22.168 update that brings even more improvements, bug fixes, as well as a couple of new features to TWRP.
File selectors and list boxes now have a scroll bar to help you navigate their contents. Also, the recovery now uses libblkid to detect file systems more accurately, getting rid of problems with exFAT partition detection. Aesthetically, there’s now a screen dim effect on some devices that appears two seconds before the screen times out.
When it comes to the bug fixes, mknod failures and issues with restoring hardlinks when restoring backups have been taken care of, and your backups should now restore correctly. File selector crash, screen timeout loading during startup, and military time persistence problems have been fixed as well. The screen timeout code has also been optimized and some other bugs have been ironed out.
You can read the official change log and find links to device-specific forum threads for downloads and more information in the TWRP Touch Recovery Device master thread.
Regardless of what the US Government and the PAC behemoth CTIA would have you believe, choice is a good thing in the wireless industry. And when it comes to having choices for different types of software you want to run on your devices, it is a great thing. TWRP (TeamWin Recovery Project) is one of those options for recovery on many different types of devices, with over 80 being officially supported at this time.
TeamWin has been very supportive of the community, from providing instructions on how to build TWRP for devices they don’t officially support, to actively participating in online and forum discussions assisting users with the usage and porting of TWRP. Their source code is completely open source and doesn’t require that you purchase an app in order to utilize the OpenRecovery scripting functionality, unlike other options available.
As of late, they have been hard at work adding various features that add value and continue to set TWRP apart from the other recoveries. Version 22.214.171.124 brings with it new features like using libtar instead of busybox’s tar implementation for better backup options, exFAT sdcard support, decryption of Samsung TouchWiz encrypted devices, updated ADB sideload functionality, and much more. You can view their site for a full list of supported devices or visit some of the device-specific threads below:
If you spot an official TWRP thread that we’ve left out, please let us know, and we’ll promptly add it in!
December 17, 2012 By: Haroon Q. Raja
When there’s mention of custom recoveries for Android, ClockworkMod is one of the first names that comes to mind. In the past, we had AmonRa recovery, which still retains several faithful followers. Lately, TWRP has emerged as another excellent custom recovery that many have started to favor over CWM due to a larger feature set and killer interface.
COT (Cannibal Open Touch) is a new recovery aiming to bring some of the best features from other options in a single package. The project comes courtesy of XDA Forum Members Drew Walton (Project Head), thenameisnigel, and Sblood86.
The current feature list of COT includes:
COT recovery v2.1 is currently available for the following devices:
Development is planned to bring COT recovery to other devices soon, starting with Galaxy Nexus, Samsung Galaxy S III and the Barnes & Noble Nook Color. You can learn more and download the appropriate recovery for your device using the links provided above.
The Acer E350, otherwise known as the Liquid Gallant, is one of those devices that sits squarely in the middle of the road. While more than capable of running Android 4.0.3, its specs aren’t really anything to write home about. This coupled with the fact that Acer’s devices aren’t particularly renowned for their developer support means that the E350 wasn’t given it’s own dedicated forum. That however has not stopped those with the device from providing it with that all important trio of root, recovery, and ROM that no device should be left without.
XDA Forum Member jaapstreepjan posted a thread detailing exactly how to go about gaining root access and installing a custom CWM-based recovery to the E350, as well as a simple tweaked stock ROM to be flashed from your shiny new recovery. The ROM includes some enhancements such as Google Now, init.d support, and a less bloated /system partition among others. The root method is courtesy of XDA Forum Member Bin4ry, and the recovery via XDA Forum Member erlucky.
If you own one of these devices and are looking to extend its capabilities, check out the original thread for more info.
We’ve made a fair amount of noise about TWRP (Team Win Recovery Project) here on the Portal, and with good reason. It’s been ported to a wide array of devices, from the Sprint Galaxy Note 2 to the ever present mobile geriatric that is the HTC Hero. Now it’s available to owners of the brand spanking new Nexus 10. I personally can’t think of a better way to celebrate the arrival of your new device by slapping a custom recovery on there.
This particular port of the increasingly popular recovery option is brought to us courtesy of XDA Recognised Developer Dees_Troy, lead developer of TWRP, and includes all the features you would expect to find. And because it’s based on the latest version (126.96.36.199), it fixes an issue with ADB in recovery and enables USB OTG capabilities. There is however a slight issue with the theme. Due to the high resolution of the Nexus 10, the recovery requires some upscaling and won’t quite fill the entire screen. This is purely aesthetic though, and does not affect functionality in any way.
Installation can be accomplished via either the good old fashioned way of fastboot flash recovery or by simply installing the Goo Manager app and selecting the install recovery option if you’re already rooted. Take a look at the development thread for all the details.