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 184.108.40.206, is loaded with updates and fixes. These changes make the overall experience smoother and more enjoyable. For instance as of version 220.127.116.11, 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 18.104.22.168 update just a few days ago. Things are getting even better, as XDA Recognized Developer Dees_Troy and team have just released the 22.214.171.124 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 126.96.36.199 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 (188.8.131.52), 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.
For those unfamiliar, TWRP stands for Team Win Recovery Project. It’s an open source recovery for Android devices that offers an advanced touch-based UI and Open Recovery Script support, as well as several other features not offered in other recoveries.
This port comes courtesy of XDA Senior Member Ron G, and based on the user response, it is working virtually bug-free on the device. Installation is as simple as flashing the provided file from your existing recovery.
You can find more information, the complete feature list and the download link in the forum thread.
April 22, 2012 By: Conan Troutman
Sony Xperia S users rejoice. The FreeXperia Project, has released not only a ClockworkMod-based recovery for the device, but also an unofficial version of CyanogenMod 9. So if you’ve been longing for a little AOSP action, your wait is now over.
First things first, before you begin installing that new ROM, you’re going to need a nice new recovery image. XDA Recognized Developer DooMLoRD has ported his version of a CWM-based recovery entitled DooMRecovery to the Xperia S. If you’re already familiar with his work, you may recognize this recovery. If not, be warned—this is not your average recovery. Although based on the standard CWM, DooMRecovery is heavily themed with a Honeycomb styling. Furthermore, it is touch capable, so there’s no fiddling around with the volume keys. It also implements haptic feedback to make sure you’re aware that your selections have been acknowledged. Other notable features and changes include:
This is a great take on the classic recovery that we’re all so used to so I highly recommend checking out the original development thread and familiarise yourself with its features.
Once you have your new recovery installed you’re going to need something to flash, right? Not a problem, as the FreeXperia Project and in this instance, XDA Recognised Developer Bin4ry have released an unofficial version of CyanogenMod 9. As with any first release there are still a few bugs and issues, some of them fairly major such and WiFi and GSM not being fully functional .HDMI, FM Radio, and ANT+ are also still being worked on. It important to note that this is an unofficial release of CM9, and is not coming directly from the CM team themselves. Installation is a standard flash-from-recovery, as you would expect.
March 10, 2012 By: Joseph Hindy
Sometimes, users who are new to a device require a little more than even the most precisely worded How-To thread in order to get started with the basics such as rooting their phones, unlocking their bootloaders, and installing custom recoveries. XDA Senior Member hasoon2000 has solved this problem for HTC Vivid owners and want to get their phones rooted, unlocked, and ready to go.
The HTC Vivid All-In-One Toolkit gives users a plethora of aids including permanent root, CIQ removal, ClockworkMod Recovery, and a debloater that will remove the bloatware. The full list includes:
- Install HTC Drivers
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Install Recoveries
-Flash Kernels provided
Stock Vivid Kernel
Holicakes OC Kernel
- CIQ Removal v1.1 (credit to 8125Omnimax)
- Link to this thread
- Link to the FAQ thread
- Link to the Vivid Development thread.
- Boot Into Recovery
- Relock Bootloader (must be in fastboot)
- Debloater and Debloater Remover (Credits to Bling)
The user interface is very plain and easy to understand, so there’s no real guess work involved. Just plug in your HTC Vivid and start going.
Check out the original thread for download links, screenshots, instructions, and everything else you’ll need to get started. Once you’re rooted with that custom recovery, make a full Nandroid backup—just in case.
February 12, 2012 By: Joseph Hindy
Caring is sharing and in the world of AOSP Android development, that’s more than a motto, it’s basically a rule. More ROMs have been forged from the depths of repositories like Github than any other single source out there and ROMs don’t even comprise all the source code in Android repositories.
It is with the caring and sharing in mind that XDA Senior Member Napster and XDA Recognized Developer DooMLoRD of Team UtterChaos have merged their Touch versions of ClockworkMod Recovery and have released the repositories containing their source code to the public.
Their mission? To give the code to any developers who want or need it in order to port the super nifty touch recovery to phones that do not yet support it. Of course, they already know that XDA Recognized Developer, and CM Team Recovery Guru Koush has been working on his touch recoveries, but they say:
we are well aware that koush is already working on a touch version of CWM recovery… we do not mean to compete with anyone… since we have been working on this for a while, we felt others might benefit from this and learn something new, we sure did learn a LOT ourselves throughout this project…
So for any developers out there who are yearning to port the ClockworkMod Touch Recovery on their device, you can find the Github link and all additional information in the original thread.
January 30, 2012 By: Joseph Hindy
It’s hard to throw around some words in the Android development community. Some mods are superb, some ROMs get tens of thousands of users and their threads have millions of views. Some themes are universally loved and some things people just can’t imagine living without. Even so, there are very few releases that can be described as truly great.
So, as a result of my work, I would like to present the first ever Ubuntu Recovery. This will totally wipe your device. With the exception of the ROM Partition which contains serial information, every single partition will have zeros written to it then flashed with just enough to perform an initial factory reflash. Normally when you perform an update or flash of a device, it is simply formatted. A formatted device can be unformatted. A zeroed device cannot be unformatted. All information is overwritten with zeros.
This will also work if you’ve damaged the bootloaders or recovery partition.
The recovery will wipe your device clean sans some important ROM information and the parts that allow for a factory re-flash and could be helpful for those trying to restore back to 1.4.0 firmware on their Nook Tablets.
For additional information, screenshots, full instructions and even a nifty how-to on creating a recovery SD card, you can find everything you need in the original thread.
The LG P350, also known as the LG Optimus ME Titanium, is a mid range device that is pretty affordable. If that isn’t enough, it also has received CyanogenMod 7.
XDA Member pax0r has been kind enough to compile the mega popular ROM to this humble device and while the ROM is still a beta, it’s got enough features working to use as a daily driver for some people.
The list of features not working is very short and only includes a small break in the camera where users can’t see previews. However, the camera does still take pictures. This doesn’t mean there aren’t more, as pax0r states:
It’s testing and still WIP release so there still could be bugs.
Before installing, make sure you pick up the LG Optimus ME compatible custom recovery from the link and always take the proper precautions such as creating a full backup. Once you’ve got the proper prerequisites, though, it’s all a matter of installing the ROM.
For additional information, the installation instructions, download links and if you just want to keep updated on the progress, you can find all that and more in pax0r’s original thread.