Database Info

[RECOVERY][GPL] ClockworkMod 3.1.0.1 PURPLE UPGRADE RFS/EXT4/USB CUSTOM FOR EPIC4G

CWM 3.1.0.1 PURPLE UPGRADE WITH RFS/EXT4/USB MASS STORAGE SUPPORT!
Some of you might be asking,
WHY DID I DO THIS?
Well, as soon as I released cwm 3.0.2.5, I got requests from all over the epic community, to make some changes to cwm, changes I couldn't incorporate, until I learned to compile the ClockworkMod binary itself. So, with some help from skeeterslint and Rodderik, I did just that...
So, the changes in CWM 3.1.0.1 purple are:
* USB Mass Storage working from the menu, and top text changed, to reflect safe removal of sdcard from PC *before* leaving USB Mass Storage menu
* Purple text and icon color, everyone seemed to hate the orange color
* Key Codes fixed, menu is now the select key, and top text changed to reflect this
* Only one "No" in confirmations, only need to click down once to get to "Yes"
* Built-in busybox is full Cyanogen busybox 1.16.2, with --install -s feature built in
* sd-ext ext4 partition listed in recovery.fstab, a direct change from koush
* Compatible with cwm 3.0.2.5, and has been tested by many in irc.fossnet.info #epic channel
These features are the direct results of feedback from both devs and users in the irc channel... so, if you want input on things like this in the future... it pays to be involved in the epic irc channel!
Please note: some people have had the samsung recovery appear after this flash, and in my testing, in some circumstances, the stock kernel can actually flash back the stock recovery. Due to this, I highly recommend that anyone flashing the new cwm with this flash, please also flash my clean kernel, located here: Clean Kernel EC05 thread Also note, that the one click version of this should not have this problem, since it takes away the ability of the stock kernel to flash the samsung recovery.
OK, there's been some confusion to what the recovery kernel is and does... even among developers at times... so let me explain, before you download:
This flashes the recovery partition of the phone. When I release a CWM upgrade, I am flashing bml8, which is the recovery partition. The recovery partition is only booted when the phone is powered off, and a 3 finger boot is performed, using vol down, camera, and power, held down until the menu appears.
Reboot recovery relies on the kernel (bml7), or a cwm redirector (from the stock kernel, is what the one click root does) to provide cwm, which is why you get an older cwm version with reboot recovery with most kernels. My Clean Kernel EC05 was made to provide a bassline for other kernels for cwm reboot recovery, so until other kernel devs incorporate the new recovery into their kernels, the Clean Kernel is the only one that does reboot recovery to cwm 3.1.0.1. I hope this clarifies things a bit.
I have been actively training other kernel devs on how to incorporate cwm reboot recovery into their kernels, so that koush himself can start pushing cwm updates officially through ROM Manager. This is how ROM Manager is intended to be used (and once was, before ext4 invaded the epic development scene)... but for this to happen, the new recovery needs to be standardized, and everyone on the same page, for this to happen. I know koush will be ready to push official cwm updates for the Epic through ROM Manager, as soon as we as a community are ready for it.
NEW!!! Thanks to qbking77 for making this video, showing both install methods in action, for those that just hate to read instructions:
http://www.youtube.com/watch?v=dsRA7q4JWPQ
DOWNLOADS
cwm3.1.0.1.purple.zip
Flash this with your current ClockworkMod to be upgraded!
NEW!!! If you have problems with the flashing the zip, or just wanna use Odin, here is an Odin flashable tar will get you all squared away, with a quickness, just load the file into the PDA slot of Odin
cwm3.1.0.1.tar.md5
NOTE: if you're phone won't boot after flashing the zip from cwm, just flash this, there is no need to flash a complete stock tar.
Notes:
* This flashes bml8 kernel only, this kernel is stripped of bloat, for minimal file size
* 3 finger boot required to enter the bml8 recovery from power off
* Key assignments: vol/keypad up/down= up/down, camera button/menu softkey/keypad enter= enter, back softkey/power/keypad delete= back
hehe: has mkasick keyboard patch, so thumbing is faster!!!
* Full restores of backups done from prior cwm versions may not be possible. Do backup and restore > advanced > {choose backup} > and selectively restore the partitions you need.
* Once new backups are performed, those backups can be restored to *either* rfs or ext4.
* Now backup and restore includes both the kernel and recovery too
* Use in conjunction with my Clean Kernel, for ROM Manager support, other kernels will soon follow suit:
Clean Kernel EC05 thread
credits:
THE COMMUNITY!!!! I HAVE FINALLY SEEN DEVS WORKING TOGETHER IN WAYS I DIDN'T THINK WERE POSSIBLE...
LET'S KEEP THIS UP, AND KNOW THAT COOPERATION BENEFITS EVERYONE!!!!
* kain203: donated the use of an 8 core linux machine for my use in compiling kernels and the cwm binary. This *greatly* increased my productivity, and allowed me to edit and compile everything for cwm and my kernel, *all* from my Epic 4G, believe it or not...
* Rodderik: without his initial kernel training, I never would have gotten this done at all, also, helping with installing packages necessary to get cwm to compile, he also generously provides the hosting for these files you're downloading.
* koush: the friggin man! The creator of ClockworkMod and ROM Manager! He gave me the advice I needed to finally get dual fs support!
* tanimn: for hosting of cwm koush files in this github, and sharing experience that was genuinely helpful
* vocaltreat: the cwm3.1.0.1 purple clockworkmod icon
* skeeterslint: help in getting cwm to compile, and pointing me to files to edit, from his prior expertise on cwm
* mkasick: for the keyboard sysfs patch, for faster key response
Notes for sources:
The Samsung kernel, ClockworkMod, and busybox, are *all* open source, and as such, mods to all, should have the sources included. Since I like to *practice* what I preach, here are all the sources for the CWM kernel, recovery, and busybox edits:
https://github.com/DRockstar/CWM-3.1.0.1-Kernel
https://github.com/CyanogenMod/android_device_samsung_epic4g
https://github.com/DRockstar/android_bootable_recovery
https://github.com/DRockstar/android_external_busybox

Nice work. You going to make this a one click method?

Nice thanks for this man flashing now.
Sent from my Epic S 4G using XDA Premium App

Sweet!!!!

Is this compatible with EE03? I see it flashes a kernel and assume that it isn't compatible with the gingerbread leak.

ebejoe said:
Is this compatible with EE03? I see it flashes a kernel and assume that it isn't compatible with the gingerbread leak.
Click to expand...
Click to collapse
Yes it is. Just flash it through your current clockwork.

Awesome work. Flashing from Yellowstone.
Sent from my SPH-D700 using XDA Premium App

qbking77 said:
Yes it is. Just flash it through your current clockwork.
Click to expand...
Click to collapse
Flashed and is working well. Nice work.

Now I need that initram for my kernel drock! Goodjob..
Sent from my SPH-D700 using XDA App

Awesome Job Pimpin'!!!!!
Sent from my SPH-D700 using Tapatalk

I almost forgot to post all of my sources for this, which is very important to me... sources for the cwm Kernel, recovery, and busybox, are all listed at the bottom of the post.

Worked perfect first try. I actually am using Genocide 1.1 kernel and had no problem. Thank you for the hard work. The purple looks sharp. I can see a purple and black theme in the future now
Sent from my SPH-D700 using XDA Premium App

Really like not having to scroll through so many "NO"'s just to flash something.
Excellent work
The busybox is awesome too.

Will this work correctly on gingerbread or will it mess up the kernel?
Sent from my SPH-D700 using XDA App

marcusant said:
Will this work correctly on gingerbread or will it mess up the kernel?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Flashing this cwm kernel to bml8 won't affect the gingerbread leaks, just do not flash the Clean Kernel on the gingerbread leak, or the phone won't boot.

DRockstar said:
Flashing this cwm kernel to bml8 won't affect the gingerbread leaks, just do not flash the Clean Kernel on the gingerbread leak, or the phone won't boot.
Click to expand...
Click to collapse
I am aware about the 2nd part. Can I include this in my rom?
Sent from my SPH-D700 using XDA App

I've been using this with ee03 and it works fine.
Sent from my SPH-D700 using XDA Premium App

1. Can you make a version in red?
2. Can I use this in my rom?
Sent from my SPH-D700 using XDA App

marcusant said:
1. Can you make a version in red?
2. Can I use this in my rom?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sure, you can use the recovery in your ROM...
As for the red, it does entail a minor edit with a recompile of the binary, and repackage of the kernel... atm, my donated vm is down, but perhaps later I can do something for ya

Just did my first theme flash from the new recovery. Its so much better not having to scroll through the "NO's." I didn't think it was that big of a deal at first but it really is much better. Great job.
Sent from my SPH-D700 using XDA Premium App

[RECOVERY][EVO4G][NOBRICKS] TWRP 2.2.1 with on-screen keyboard! [2012-07-28]

For those of you who have been waiting for the triumphant return of TWRP 2. Well wait no longer! TWRP 2 is back for the supersonic with 100% less bricking!*
*Anything is possible... we take no responsibility for actual outcome on your device
Team Win Recovery Project 2.2, 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.
Phone look:
Tablet look:
v2.2.1 - various bugfixes and HTC Dumlock support now built in for latest hboots that don't support flashing to /boot.
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

DL does not work

jminor4326 said:
DL does not work
Click to expand...
Click to collapse
Some regions have been experiencing routing issues with our domain today. Kind of crappy. Links do work since others have been able to download, but they don't work for me personally either. :/

ViViDboarder said:
Some regions have been experiencing routing issues with our domain today. Kind of crappy. Links do work since others have been able to download, but they don't work for me personally either. :/
Click to expand...
Click to collapse
I too am having this problem is there any chance of a mirrorfor those of us going thru TWRP withdrawals
Sent from my PC36100 using XDA Premium App

I'll have to give this a try.
Thanks for your hard work.

Got it from the twrp website today from the other thread . So far I'm loving it.
Sent from my PC36100 using xda premium

Flashing Now Thank You.

This is nice. I'm using it now, backing up, but having some strange issues with tapping the icons on the middle of the bottom of the screen.

Working on grabbing the directly dl links.
Zip:
http://techerrata.com/file/twrp2/PC36IMG-twrp-supersonic-2.0.0RC0.zip
Img:
http://techerrata.com/file/twrp2/twrp-supersonic-2.0.0RC0.img

attached is the recovery.log for the failure to wipe data (factory reset). Let me know if anything further is required.
http://dl.dropbox.com/u/8128460/recovery.log

I flashed version 2, when I rebooted, I didn't rename the PCIMG36.ZIP but even after I did rename it by manually taking the card out and doing it in a USB drive, I am ONLY booting to the white screen on my Evo. Help, I am in an endless loop that it only boots into the white screen on my evo. I can't get the system to boot up past the white screen with the three androids on skateboards. I can get back to recovery, flashed back to 1.1.1 TWRP, but what did I do wrong?
Any and all help would be most appreciated.
Help.

Btw. Rename it to sometying with recovery in the name and you can use flash image GUI with the the .img file
Sent from my PC36100 using xda premium

SD-EXT
I don't have any useful information unfortunately but same problem as in twrp 1.1.1 it doesn't find my sd-ext ext3 partition created with AmonRA2.3 so I either have the choice of redoing the phone to use this or stick with Amon. I'll probably redo the phone because this recovery is nice!
Thank you noticed that quickly after typing this. I'll redo my phone next day or so and I'm sure that will remedy the problem. Very nice work though!
Last note: wiped everything tried to partition using 2.0 and it says successful but still won't mount ext.

bhint15 said:
I don't have any useful information unfortunately but same problem as in twrp 1.1.1 it doesn't find my sd-ext ext3 partition created with AmonRA2.3 so I either have the choice of redoing the phone to use this or stick with Amon. I'll probably redo the phone because this recovery is nice!
Click to expand...
Click to collapse
Yea, that issue is being tracked on Github. So we are looking into it.

Do u have a version coming for the Droid incredible
Sent from my Touchpad using xda premium

Takes. While to load on evo any special button to hit to go in.
Sent from my Touchpad using xda premium

This looks pretty amazing! A full GUI in recovery is like UEFI on pc's!

was able to flash rom fine ....... tried checking md5 sum said no md5 sum

Kchitown1977 said:
was able to flash rom fine ....... tried checking md5 sum said no md5 sum
Click to expand...
Click to collapse
Yea, for the md5 it looks for filename.zip.md5 with the checksum.
Sent from my Touchpad using xda premium

I am getting a loop of the boot animation when I try to flash some roms, like JaredTheGreat's ICS Port

[RECOVERY][TF101][OFFICIAL] TWRP 2.3.2.3 with on-screen keyboard! [2012-12-12]

Team Win Recovery Project 2.3, 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.
Phone look:
Tablet look:
CHANGELOG for 2.3.2.3:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
-TF101: Ignore blkid when mounting /data
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please acquire a recovery.log - you can do this in two ways - the fastest is "adb pull /tmp/recovery.log" right after you have the issue. Alternatively in the advanced menu there's an option to copy the log to the sdcard. Also consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

We also now back up and restore boot! Yay!
Want to compile yourself?
I'm using this config: https://github.com/ViViDboarder/android_device_asus_tf101
And this kernel: https://github.com/ViViDboarder/android_kernel_TF101
And compiling against CM9 source tree
Further device specific announcements will go here
A few thanks for this specific build:
Roach2010 for helping be me test and find the mystery kernel
RaymanFX for finding a config that worked. Still not sure where he found it yet exactly
And... Dees_Troy and eyeballer for their relentless nagging

first ...
well second lol

So, third ......thanks guys, that's awesome !

thanks, been waiting for this.

great work, i've been waiting forever and finally have this on all my devices and those that I support.

I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.

gdeeble said:
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
Click to expand...
Click to collapse
Good note. That's a theme issue then. I can build a new theme zip or something later. Working on releasing the much delayed Nexus One build.
EDIT: I've been informed by Dees_Troy that we have build flags to do just this. So I'm adding them to my configs so the next build should have them removified.

It's worth pointing out that this build of TWRP has a recompiled kernel with boot and recovery exposed. You can finally back up boot and restore it.

GooManager keeps hanging at Looking for recoveries after trying to install OpenRecoveryScript. Unable to retrieve files...

Finally recovery on a touch screen device the way it should be! Thanks guys!
Sent from my SGH-I747 using Tapatalk 2

I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?

Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.

MassStash said:
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
Click to expand...
Click to collapse
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.

sidneyk said:
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
Click to expand...
Click to collapse
Weird. It didn't wipe my data. Just installed nicely as per instructions.

running great with no issues I used goo manager app but i flashed it through the flash roms selection on the main menu not the 3-dot menu install open recovery script selection.

sidneyk said:
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Click to expand...
Click to collapse
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium

ViViDboarder said:
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No, I was using RaymanFX's TWRP build prior to this and before that Team Rogue Touch and before that Roach's CWM build, all flashed from within recovery. I only did the GooManager thing because that was the recommended method. Subsequent boots to recovery did not reproduce the data wipe and after reflashing my ROM and restoring my apps, I went into recovery without a hitch. It was only after installing this one through GooManager per the instructions. It downloaded, rebooted and flashed and rebooted back to Android (Team EOS3 JB #57). After a few minutes I rebooted to recovery from the Power menu in EOS3 and as soon as the blue curtain raised it was wiping my data partition - /data/media. Of course, I didn't expect that and didn't get any chance to stop it. I know I read somewhere before that open recovery wasn't working on the TF101, but since this was new and it was recommended to use open recovery, I just assumed that meant it was now working. Oh well, all is well now.

never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks

cbrox said:
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
Click to expand...
Click to collapse
I had already flashed EOS3-N58, but had changed some files experimenting with getting Polaris Office to work and gave up. So, I followed your suggestion and moved a few other files that I normally flash along with the ROM and it worked like a charm. Pretty nifty. I setup the order to flash for EOS3-N58, gapps, Guevor kernel, nVidia codecs, iobusy, and DSP Manager along with the preliminary cache and Dalvik cache wipes and it just worked like you say. Thanks. I hadn't tried that feature yet, mostly because until now I thought it might break something since I had read that open scripting wasn't working yet for TF101 somewhere. I can say now, with this recovery and your change to the download folder, that it is working and working well. You just have to have whatever files you want to flash in that folder (or maybe just somewhere in /data/media) and you're good to go.

[RECOVERY][HeroC]TWRP 2.2.2.0 touch recovery [2012-08-24]

Team Win Recovery Project 2.2, 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.
Phone look:
Tablet look:
CHANGELOG (for 2.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)

Going to flash this now and give it a try. Hopefully it works out good.

whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!

thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks

I flashed this a week or two ago and been working awesome! I love it.

i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this

they are in different folders on the SDCARD, im not even sure they are compatible.

ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder

alsp cani get the twrp 2220 in a zip format?

will this recovery work with firerats? on heroc?

dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:

thanks im trying it now, love the use of touch

I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc

I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.

Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?

* DELETE *

There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.

DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app

Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.

[RFC] universal recovery [2012/09/16]

Hello Galaxy S users,
Specifically, in this forum, it's Galaxy S 4G.
I know you've been watching T.V., and know (maybe... well here in E-merica) a little about universal health care... well I have something totally unrelated to talk with you about. [word this sentence with Steven Colbert's voice]
Universal Recovery.
As it stands, our bootloaders know nothing about the silly recovery partition on our devices.
And on stock roms, it is a total waste of good space we could put to any other partition (mostly data).
When this topic first reared it's ugly head, I thought to myself about just incorporating the unused space to data. But no! I have seen the light. And it is good!
There are a few different recoveries out there that are mostly a preference thing.
Stock Android Recovery (think the "3e" thing...) (totally friggin stock. No modifications)
ClockworkMod Recovery (cwm)
ClockworkMod Touch Recovery (cwm-touch)
TeamWin Recovery Project (twrp)
manual partition magic (that really only devs know about... [Bryan Jedi waves his hand in your face] forget I said anything here.)
... to name a few. Granted I will not support/help you on the first or last versions of recovery mentioned above.
I would like to use the recovery partition to unify the storage of the recoveries.
As we have seen with the radio partition... On stock, it is a bml partition without rfs. The modem.bin is written (redbend_ua) directly to the bml12 partition and read back by /system/bin/rild
On (Gingerbread(mtd)/CM7/ICS(mtd)/CM9) MTD based roms, the radio partition is a yaffs2 formated partition in which modem.bin's are simply copied to. A symlink (/dev/block/bml12) to allow rild to work correclty... (well and a nasty hack on SGS4G to pad the modem.bin with zeros, because the rild reads more then the size of the modem.bin but less then the size of bml12)
Lets say we format the recovery partition as yaffs2 (or either vfat or ext4 on bml roms), and store ramdisk-recovery-<version>-<fstype>-<recovery-type>.img files there.
Examples:
ramdisk-recovery-gb-bml-cwm.img
ramdisk-recovery-ics-mtd-twrp.img
Then create a cwm update.zip that allows you to switch your recovery based on what is in the /recovery partition.
The title of this post is [RFC]... This is a Request For Comments.
As an amendment to this RFC, I would also like to have universal updater.sh and updater-script files to be created so that one could say, flash:
stock bml gb (cwm) -> ics mtd (cwm-touch)
ics mtd (twrp) -> stock bml gb (twrp)
ics mtd (cwm) -> gb mtd (cwm-touch)
gb mtd (twrp) -> stock bml gb (cwm-touch)
gb mtd (cwm-touch) -> ics mtd (cwm)
...without ever needing to go to download mode to run a oneclick or odin.
This thread should eventually turn into a development thread containing the results of this discussion.
...
A little while back, I started a poll.
The results of the poll, and comments lead me to believe that users are more interested in obtaining root and having the latest version then anything else.
All of these recovery methods should provide root access to install which ever rom you want (rooted or not rooted) and whatever recovery you want to use.
Goals (no particular order):
Run an updater.zip OR run an android app to change the current version of recovery.
Unify the updater.sh and updater-scripts for our roms, so you guaranty that you can flash from any rom to any rom (unless it has not been updated to use this new standard)
Do something with the lost 6-7M of unused space currently known as 'recovery'.
Let me know what you think. I already have a WIP, but it only supports cwm (at the time of this writing. cwm-touch and twrp coming soon...).
I am working on minimal environments (android manifests) to build each specific recovery nightly so that these will always stay up to date with what is in our repositories.
Being an RFC thread, please provide some helpful feedback.
ALSO, I leave this open to other Galaxy S phones as well!
You too have a device with this stupid recovery partition.
If all Galaxy S phones used the same codebase for updater.sh and updater-scripts and for setting the currently used recovery, it would be a win for everyone.
OK, Technical section:
--------------------------------------------------------------------------------------
On the latests CM10, a patch was applied by pawitp a little while back to allow a simpler packing of ramdisk and recovery.
Because of this, you can basically repack the initramfs with a different recovery.
If we changed our stock bml gb kernel, cm7 (and other mtd based kernels) to use a similar recovery method, we could unify the way we change between recoveries.
--------------------------------------------------------------------------------------
...Comments go here VVVVVVVVVVV

As we were discussing on #teamacid, I think I can help with figuring out the mtd -> bml portion of this since most of my previous work has been with installer scripts and the recovery environment.
Bryan was telling me that it should just be a matter of flashing the bml zImage and to reboot and continue the install.
I definitely think that storing the recovery.img files in /recovery would be a great solution. It'll keep the kernel/boot.img files leaner and allow us to update the recovery without messing with the kernel.

FBis251 said:
As we were discussing on #teamacid, I think I can help with figuring out the mtd -> bml portion of this since most of my previous work has been with installer scripts and the recovery environment.
Bryan was telling me that it should just be a matter of flashing the bml zImage and to reboot and continue the install.
I definitely think that storing the recovery.img files in /recovery would be a great solution. It'll keep the kernel/boot.img files leaner and allow us to update the recovery without messing with the kernel.
Click to expand...
Click to collapse
Essentially, yes. There are two "universal"s here.
Universal recovery selection
Universal updater.sh and updater-script usage
And, yes, kind of... the reservoir may also be apart of the big problem here.
There is much experimentation and discovery to happen before anything really results from this thread.

I definitely support the movement. What can I do to speed up the process or help with this development?
Sent from my SGH-T959V using Tapatalk 2

I'm interested in the implications this could have to the S devices with a flash counter.
Sent from my SGH-T959V using xda premium

GreyDark said:
I'm interested in the implications this could have to the S devices with a flash counter.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I know that the sgs4g has a flash counter, but it never increments.
I think it was something they were thinking about, but never got working for the release.

VillaCastana321 said:
I definitely support the movement. What can I do to speed up the process or help with this development?
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
I just need to finish my WIP and let other devs at it so they can make changes to it.
The WIP is driven by what is in the OP of this thread. It is not written very well and not very detailed.
I hope that changes over time with feedback.

Having botched my share of kernel/recovery flashes, this would be very interesting if I could always access something that would let me flash a known-good kernel/recovery from microSD when I next mess up.
Admittedly, I could stop flashing unknown kernel/recovery when I'm not within reach of Heimdall, but...

So the SII can use triangle away for the flash counter while with the SIII it's still usable yet not recommended from what I saw. By using dd to get the recovery in, the SIII dodges the counter again, (first time by using Odin to get root) but there can always be people who might even do that wrong. I don't know about the other S devices, but if there was an easy way to get root and a custom recovery, definitely a plus for average users.
Sent from my SGH-T959V using xda premium

I think its a very good idea. It makes perfect sense, I don't see a downside and see its possible. It would be great actually
Sent from my SGH-T959V using xda app-developers app

This sounds awesome... would b willing to test.....
sent from my t959w running RemICS, Voodoo sound, Rom Toolbox pro.

Fun starts in a month or so.
Wait... For... it.

bhundven said:
Fun starts in a month or so.
Wait... For... it.
Click to expand...
Click to collapse
Patiently waiting... teeth clenched....staring at my screen,watching for that post up..... LOL
sent from my t959w running RemICS-UX, Voodoo sound, Rom Toolbox pro

abonides said:
Patiently waiting... teeth clenched....staring at my screen,watching for that post up..... LOL
sent from my t959w running RemICS-UX, Voodoo sound, Rom Toolbox pro
Click to expand...
Click to collapse
So you are told to wait about a month, and you are spazing after six days? Wow, really patient.

Cooptx said:
So you are told to wait about a month, and you are spazing after six days? Wow, really patient.
Click to expand...
Click to collapse
I think he was joking

pisherthefisher said:
I think he was joking
Click to expand...
Click to collapse
I hope so
SMH
Sent from [CONTET DELETED]

love the idea <3

Sorry,my sick twisted humour cannot b appreciated via text.
sent from my t959w running RemICS-UX, Voodoo sound