Develop Bugs

[RECOVERY][EC09]Clockwork Mod Recovery

I fixed recovery for the Continuum users so that you have your own button mappings. It isn't integrated into the kernel yet, but I'm going to attempt to get that fully working (I have it partially working atm). Until that is fixed, you get the update.zip method for CWM. So, to accomplish this, you'll need to download two things. First, you need the update.zip file, which is placed on the root of the SDCard (/sdcard/update.zip) and the second item is the recovery kernel, which is flashed via Odin (v1.3). It is now integrated into the kernel and it has been updated to the EC09 kernel. This package will flash both recovery and kernel (so you don't loose CWM when the system boots). Note that if you are still on DL17, you should use the archive packages below. What you will need is this file, and you will want to flash it via Odin (or extract it and use Heimdall).
Open Odin, click the PDA button and browse to and select the continuum_recovery.tar.md5 I400_CWM.tar.md5 file that you downloaded. Remove the battery from your phone, and hold down the volume down button while plugging in the USB cable that is attached to your computer. Make sure you have the drivers installed, if not, you'll need to install them before you continue. Flash the file by clicking start if the phone is detected in Odin. Once it completes successfully, all you need to do is boot to recovery and apply sdcard/update.zip and you'll be in CWM. I decided upon black background with cyan text. This can still be changed if you wish, but I like it
Here are your button mappings:
Camera button/Grip sensor - Select Item (applies to cwm and stock recovery)
Volume Up/Down - Scroll up/down in the list (applies to cwm and stock recovery)
Power Button - Select Item
Menu Button - Does nothing
Home Button - Go Back
Back Button - Go Back
Search Button - Hide Text
I'm still trying to figure out how to get buttons to show up for the touchkeys. For now, they're blank, so just press in the approximate location on the screen for them. We may or may not be able to get buttons there at some point. Also, when you initially boot to recovery, there will be a message about update.zip being gone. Ignore the message as it seems to be a bug. As long as you copied the update.zip from this thread to your SDCard, you should be fine. Enjoy.
If you like my work, feel free to donate to me. Alternatively, sign up for Dropbox via my referral link Also, remember that none of this would really be possible without the generosity of DroidXcon, so you could donate to him as well.
Archive said:
Recovery Kernel
Download - CWM 2.5.x
Download - CWM 3.x
Click to expand...
Click to collapse

Thank you so much imnuts
It works like a charm
and btw, i love the color scheme, lol

This is awesome! Im extremely happy to see great dev work still going on for the continuum!

I'm going to update the update.zip soon then as well to the latest CWM 3.x that we have for the Fascinate as well. Then, maybe look into replacing stock recovery again and hoping it works this time.

im having major problems well maybe not major but i installed cwn but after i rebooted and tried to install a softkey update.zip i lost my cwm and every thing i try to do i cant get cwm back

You have to apply the update.zip every time
Sent from my SCH-I400 using XDA Premium App

I do and I get the discolored screen then it send me to the stock recovery and when I try to install the update.zip it says update.zip not found when I know it's there
Sent from my Rooted Space Time Continuum w/h a 2600mAh battery

Mine says the update isn't found either but it still works for me. I dunno about the discolored screen. I'm sorry :/
Sent from my SCH-I400 using XDA Premium App

i figured out what i was doing wrong i renamed the file to update.zip when i should have left it at just update lol oh well you live and you learn

Ohh lol. The .zip is the type of file it is
Sent from my SCH-I400 using XDA Premium App

Noob question. Is the recovery kernel were supposed to download along with the update.zip an actual kernel?
Sent from my SCH-I400 using XDA App

And what exactly is the difference between this CWM and the original CWM?
Sent from my SCH-I400 using XDA App

ntien said:
Noob question. Is the recovery kernel were supposed to download along with the update.zip an actual kernel?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
You need to flash the recovery kernel via Odin, and it is an actual kernel. The update.zip is a fakeflash recovery. It basically kills the currently running recovery and starts up CWM recovery in its place.
ntien said:
And what exactly is the difference between this CWM and the original CWM?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
The difference is that this recovery has the correct button mapping, where the update.zip that Adrynalyne posted was using the Fascinate's button layout, so things didn't work as expected.

so i can't have both this version of the clockwork recovery mod and the peanutbutta jelly time kernel at the same time?

ntien said:
so i can't have both this version of the clockwork recovery mod and the peanutbutta jelly time kernel at the same time?
Click to expand...
Click to collapse
Yes you can. Recovery is a full kernel, it just boots using a different file and set of commands, and it doesn't start up the android system once booted and provides just a minimal environment. The recovery kernel and standard kernel lie on two separate partitions, and in actuality, this recovery kernel is the standard kernel as well.

New CWM update.zip file. Like we did for the Fascinate about a month or so ago, I'm going to try to get everything moved over the CWM 3.x and Edify Scripting. Here is a new update.zip file to be able to use the most up-to-date version of CWM. I'll also try to keep this file updated as Koush and the rest of the CM team update CWM.
Instructions
1. Download me
2. Rename file to update.zip and put it on the root of your SD Card, overwriting the previous update.zip
3. Boot to recovery and apply update.zip
I may give replacing stock recovery entirely again another shot as well, eliminating the need for the update.zip entirely, but no promises. Also note that nandroid backups made with the previous update.zip file will not work with this version of CWM. If you like having the nandroid backup available, redo your backups so you have them for the new CWM.

Deleted cause it was a stupid question

imnuts said:
New CWM update.zip file. Like we did for the Fascinate about a month or so ago, I'm going to try to get everything moved over the CWM 3.x and Edify Scripting. Here is a new update.zip file to be able to use the most up-to-date version of CWM. I'll also try to keep this file updated as Koush and the rest of the CM team update CWM.
Instructions
1. Download me
2. Rename file to update.zip and put it on the root of your SD Card, overwriting the previous update.zip
3. Boot to recovery and apply update.zip
I may give replacing stock recovery entirely again another shot as well, eliminating the need for the update.zip entirely, but no promises. Also note that nandroid backups made with the previous update.zip file will not work with this version of CWM. If you like having the nandroid backup available, redo your backups so you have them for the new CWM.
Click to expand...
Click to collapse
I guess I should read the whole thing before wondering why I can't restore an old backup with the new CWM
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God

Hey imnuts, every time I try to restore my phone with this clockwork, it screws up my phone saying it cant mount this stuff etc. it worked with regular recovery and old clockwork, but the new clockwork messes up my phone when I try and restore my phone. Im running the DL17 ROM (not the new edify one)
Sent from my SCH-I400 using XDA Premium App

ntien said:
Hey imnuts, every time I try to restore my phone with this clockwork, it screws up my phone saying it cant mount this stuff etc. it worked with regular recovery and old clockwork, but the new clockwork messes up my phone when I try and restore my phone. Im running the DL17 ROM (not the new edify one)
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
...Did you not even see my post right above yours?

Weird Problem flashing Roms

Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.

You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky

I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.

jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.

jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637

I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped

abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours

playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^

Rom Manager with the Photon Q recovery works fine on the Razr M.

So you are Unlocked & Rooted.
Download the apk here
Just choose the setup for The Photon Q let it do its thing.
It is just a "stepping stone" to flash the newest from the same recovery.
It is 6.0.1.3 & works a lot slower than the newest 6.0.4.5 or TWRP from my goodies.
For the doubters I will say that, except the keyboard & digitizer input, the Q & the M are the same phone.
Atrix HD using RM also.
More
See method 4
Love TWRP? RM installs TWRP also. Just flash the zip from cwmr see housekeeping goodies.
The biggest news is that one can go from rooted stock to custom recovery with this. If you want TWRP OR Matt's CWMR just flash it from this recovery -see goodies below. Also the attached flash-able zip is a larger font CWM version from the Atrix HD forum.
This also allows you to take the OTA using 3 (or 4 if you have not unlocked yet ) phone "apps": Rom Manager, VooDoo rootkeeper, and the stockRECOVERY.zip (Motopocalypse.apk).
Get VooDoo on your SDcard from the Developer http://androidvnd.com/download.php?id=org.projectvoodoo.otarootkeeper
Now we have phone maintenance without a PC. More housekeeping goodies here. The bootloader unlock apk is there too http://forum.xda-developers.com/showthread.php?t=2327340
Steps to restore to the newest stock rom: I have a Mac and have to : ( using Parallels desktop & W7)
1. Data wipe from CWMR a must do or WiFi breaks. No more TWRP for me, I lost extSD cause of the box in normal selection.
2. Enter fast boot ...
3. Rsdlite & select the XML from Matts util...Reboots.
4. ByPass SETUP go settings/Dev. settings for USB debug.
5. Root w/ Matts.
6. Say no to logins & syncs.
7. VooDoo protect & unroot.
8. Check for update......yes yes...stock recovery... reboot
9. VooDoo restore root.
10. Login and DL RM.
11. RM with Photon Q recovery.
12. I keep ROM on extSD only... back home
CWMR is way faster and more space efficient than TWRP. Yet the blob folder can lead many to think otherwise.
Never use a space if you rename that date code label.
You never want to use internal SD for backup or anything else as it gets wiped in the often needed data wipe/reset. That is why a SD swap is so needed on our phone.
I keep RomMgr & VooDoo on my SD so I can skip all the logins and syncs If I have to restore w/ RSD.
Now I see why there are no supporters of RM on the Photon Q forum. ROM installations do not work well with the M (read Q also).
Help for general errors & what to do about them:
http://forum.xda-developers.com/showpost.php?p=43043608&postcount=1
The Q and the M are identical hardware and use the same emulated storage0.
But their digitizer screen input is the mirror of each other.
That is why the cwmr hard button version works but their official twrp will work but the screen input is mirrored.

Nobody believes me.
http://www.droidrzr.com/index.php/t...nager-works-on-the-xt907-sleeper-of-the-year/

Famous Dev's opinion.
http://forum.xda-developers.com/showpost.php?p=44055839&postcount=370

Well that's neat and all, but whats the point?

Leraeniesh said:
Well that's neat and all, but whats the point?
Click to expand...
Click to collapse
I never used it before. But it is very handy I think all the features work. I went and bought the premium app when I first got into android with the Dx2. Looking for a bluetooth ready cm based rom to install. Carbon is not yet ready.

while I can agree it "works". The screen resolution is not set-up properly for a Razr M so the text is like a font 8. Let's not forget that one can manually or even automatically install CWM recovery that is not only appropriate for their device, but also up-to-date ie (CWM 6.0.3.2 vs 6.0.1.3) AND can be manaually assigned to be recognized by ROM manager anyway.

tucstwo said:
while I can agree it "works". The screen resolution is not set-up properly for a Razr M so the text is like a font 8.
[I do not see any difference. The Q is also qHD.]
Let's not forget that one can manually or even automatically install CWM recovery that is not only appropriate for their device, but also up-to-date ie (CWM 6.0.3.2 vs 6.0.1.3)
[True, but this allows custom recovery with out a PC. Then one can flash any recovery they want.]
AND can be manaually assigned to be recognized by ROM manager anyway.
[I have found all of the housekeeping features work]
Click to expand...
Click to collapse
Thanks for the feedback.

OP updated.

FYI the more up to date Recovery for 3.4 kernels

Update
arrrghhh's TWRP Q 2610 in my goodies.
Until Matt takes care of the 2.6 fix this is our best recovery for 4.3 roms. It is really not that hard to anticipate where to touch & you can touch & hold without activating a button to know where to touch.
Use with TWRP MANAGER is flawless!
Screen input requires the mirror of the buttons.
For normal use it only works if choosen from bootloader (abort to bootloader w/keys).
I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL....
Dim Screen perks up on after a time out.
Naming a BU in recovery-Impossible.
But twrp manager makes homescreen batch operation easy, SD usb mounting & 4.3 ready....
***********************************
The XT925/926 twrp can handle the needs of the new kernels.
Edit up'ed to goodies pg 2.
Update Twrp Mgr works well with the blind xt926 recovery!
Be sure to choose ext SD.
Use twrp mgr. For "remote control operation".:laugh:
Source:
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134
I can up a twrp flashable ver & it works but only from twrp manager- batch mode. The 926 graphics bork it for normal use.
Source: http://goo.im/devs/Hashcode/vanquish/twrp-2.6.0.0-recovery-vanquish.img

aviwdoowks said:
The XT925/926 twrp can handle the needs of the new kernels.
Edit up'ed to goodies pg 2.
Update Twrp Mgr works well with the blind xt926 recovery!
Be sure to choose ext SD.
Use twrp mgr. For "remote control operation".:laugh:
Source:
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134
I can up a twrp flashable ver & it works but only from twrp manager- batch mode. The 926 graphics bork it for normal use.
Source: http://goo.im/devs/Hashcode/vanquish/twrp-2.6.0.0-recovery-vanquish.img
Click to expand...
Click to collapse
Its a lot easier to use cwm or cwm touch or ouds that are actually built for our phone. Not to mention a lot safer.

ej1911 said:
Its a lot easier to use cwm or cwm touch or ouds that are actually built for our phone. Not to mention a lot safer.
Click to expand...
Click to collapse
These phones are siblings & this is a work around to have a working recovery for cm 4.3. The xt907 ver will not work!

All of the newer cwm variants work with 4.3. And they all have full graphical functionality with our phone.
I can't understand why you wouldn't recommend a solution that offers a fully working user interface when several exist.

ej1911 said:
All of the newer cwm variants work with 4.3. And they all have full graphical functionality with our phone.
I can't understand why you wouldn't recommend a solution that offers a fully working user interface when several exist.
Click to expand...
Click to collapse
In the above post
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134

Yes, I have seen that. It still does not answer the question of why you recommend a hacked up solution with TWRP when a much cleaner solution with CWM is available.
Sent from my Droid Razr M using xda app-developers app

ej1911 said:
Yes, I have seen that. It still does not answer the question of why you recommend a hacked up solution with TWRP when a much cleaner solution with CWM is available.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
The same reason I use rom manager on our M.
It is very handy.
Xt897 stock recovery is way better than ours.
Handy.
I backed up from the home screen & then restored from home screen with the xt926 ver.
Some posters on rzr could not get our recovery to succeed w/ 907 versions.

I don't claim to be an expert. I have been playing with Android since 1.6, and have been using UNIX and Linux based systems for over 2 decades, so I do have a decent working knowledge.
In that time, most of the expensive devices that I have seen turned into paperweights were caused by either using incorrect tools or using the correct tools without fully understanding how to use them.
I'm not trying to get into an argument, but I would suggest any user that has an interest in modifying their device learn how to use the tools that are required to do so. A working knowledge of fastboot, adb, basic Linux commands, factory and aftermarket recoveries, and RSD(or the manufacturers flashing tool for your device is the bare minimum anyone should have before rooting.
As far as 4.3 recoveries, I highly recommend switching to CWM at this point before playing. Dhacker has some available to download or you can build the newest (regular and touch) at the cwm builder site.
Sent from my Droid Razr M using xda app-developers app

Be careful. I forgot this was my recovery & started to do a 2 step from twrp mgr. Backup & flash the miui alpha! In a panic I used the keys to abort.

arrrghhh's TWRP Q 2610 in my goodies.
Until Matt takes care of the 2.6 fix this is our best recovery for 4.3 roms. It is really not that hard to anticipate where to touch & you can touch & hold without activating a button to know where to touch.
Use with TWRP MANAGER is flawless!
Screen input requires the mirror of the buttons.
For normal use it only works if choosen from bootloader (abort to bootloader w/keys).
I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL....
Dim Screen perks up on after a time out.
Naming a BU in recovery-Impossible.
But twrp manager makes homescreen batch operation easy, SD usb mounting & 4.3 ready....

[RECOVERY][Unofficial][Epic4GTouch] TWRP 2.6.3.0 touch recovery [2014-02-11]

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.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
Latest Builds Here
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 40 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.[/QUOTE]

Links are up enjoy the light show
Twrp now has haptic feedback.

Wow...first post. I thought this would explode...Lol.
Great job dev.

Like the haptic... Thanx!
Sent from my SPH-D710

Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.

EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.

HighxVoltage said:
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.
Click to expand...
Click to collapse
It works to flash jb+ I first built twrp when I was on stock then I flashed jb and went to 4.4
Sent from my SPH-D710 using Tapatalk

This is a repost of the twrp from a while back right?
sent from tumblr
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
I've used an older version of twrp. I install it through Odin then upgrade to this one.
sent from tumblr

@Linux guy this is a new build hint why it has haptic feedback.
Sent from my SPH-D710 using Tapatalk

Working great on my E4GT. Thanks
☞"And on the eight day the Lord made a backup"☜

Any chance for v2.7.0.0 in the near future?

CrimsonKnight13 said:
Any chance for v2.7.0.0 in the near future?
Click to expand...
Click to collapse
This is 2.7 basically I wait for major changes but probably in a week

Unjustified Dev said:
This is 2.7 basically I wait for major changes but probably in a week
Click to expand...
Click to collapse
Thanks! I look forward to your next release.

Any updates regarding 2.7 being compiled & released?

How does one flash this?
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"

os2baba said:
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"
Click to expand...
Click to collapse
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk

dirtyhewr said:
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?

os2baba said:
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?
Click to expand...
Click to collapse
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk

Surj138 said:
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.

os2baba said:
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.
Click to expand...
Click to collapse
This device is different because the recovery comes bundled with the kernel. This particular recovery is only for kk aosp ROMs... It overwrites the recovery those ROMs come with (CWM).
There are custom kernels for stock ROMs that come with a custom recovery. If you're on stock JB I recommend Agats 1.3
Trolling from my SPH-D710 using Tapatalk