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.
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
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.
DOWNLOAD AND INSTALLATION:
GooManager:
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
ZIP file
Flash the ZIP file in your existing recovery to install TWRP.
You can find ZIP files here, choose the version you want, the file has to end with .zip.
http://goo.im/devs/OpenRecovery/p500/
Recovery Image
Use fastboot or flash_image to install this image.
You can find IMG files here, choose the version you want, the file has to end with .img.
http://goo.im/devs/OpenRecovery/p500/
OLD UPDATE-BINARY (error executing updater binary in ZIP)
P500 is fairly old device, so it is quite possible that some ROMs use old update-binary in their ZIP files, which is not compatible with TWRP. This is not a bug, rather a design feature - TWRP simply does not use such old parts anymore.
You can fix the ZIP by yourself. Download correct update-binary and put it to folder META-INF/com/google/android/ in the ZIP file. You should see previous update-binary in there, just overwrite it.
The binary affects only the ZIP file, nothing else - it is used only to install the contents of the ZIP file.
SOURCE CODE
Recovery: https://github.com/TeamWin/Team-Win-Recovery-Project
Device folder: https://github.com/Tasssadar/android_device_lge_p500 (branch jellybean)
P505
This looks exciting. I'll likely flash it to my p505 but it would be nice if someone could modify this with the correct screen drivers for p505/p506. Even though still functional it just looks terrible lol. Thank you for the update Tassadar and all other devs who helped.
Any bugs???
Sent from my LG-P500 using xda app-developers app
I'm hoping for a p505 version
Sent from my LG-P505 using xda premium
Glad to see you back Tassadar
borchaniz said:
Any bugs???
Click to expand...
Click to collapse
Don't noticed new, but old fixed.
At least error when restoring backups from previous version and saving last ZIP folder path.
Tasssadar, big thanks for continuing porting this great recovery.
Any 1 tried this awesomeness?? Howz it??
Sent from my LG-P500 using xda premium
kunnaliskinng said:
Any 1 tried this awesomeness?? Howz it??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
no bugs...
kunnaliskinng said:
Any 1 tried this awesomeness?? Howz it??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
no other recovery can compare to TWRP.i am using it since last 2 year.
vikasb32 said:
no other recovery can compare to TWRP.i am using it since last 2 year.
Click to expand...
Click to collapse
Does it safe for flashing GB,IcS,JB+ ??
What does old binaries mean ??
Sent from my LG-P500 using xda premium
kunnaliskinng said:
Does it safe for flashing GB,IcS,JB+ ??
What does old binaries mean ??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I assure you it's the best recovery Just use it once
Let me thank the OP first for creating twrp.
Since I have a hard-to-press power button this recovery really helps a lot.
No more pressing down hard on hardware buttons!
update:
hmm.. somehow just replacing the updater-binary doesn't fix the problem
update 2:
@OP
after a couple of research i stumbled upon this one that uses a twrp 2.6 too.
he stated that
If you get a "status 2" error when installing a recovery-update-package(zip) that used to work with your old recovery, change the update-binary inside the zip file with a newer one (API 3).
DON'T FORGET to check the syntax in the updater-script and verify that format() and mount() commands have the correct amount of arguments, otherwise you'll end up having other errors like "status 7".
i.e. if you use the update-binary included in the attached file below, format takes 2: format("MTD", "boot").
Click to expand...
Click to collapse
what does he mean by format takes 2: format("MTD", "boot").?
if i found this line at updater-script of CM10.1.3 (line 11)
Code:
format("yaffs2", "MTD", "system", "0", "/system");
should i change it to?
Code:
format("yaffs2", "MTD");
format("system", "0");
format("/system");
If I remove all the code, as I flash the new zip, the old files are kept in system, its just like its being factory reseted.
Thanks
Update 3:
With a little bit of experiments leading to slight mind disturbances at the middle of the night...
I managed to successfully flash a kernel.
I used cm10.1.3 by armv6.
Added this binary (see attachments)
and modified the updater-script on the line 11 to
Code:
format("yaffs2", "MTD", "system", "0");
Tasssadar, I was wondering if you could lower down the brightness a bit in recovery mode?
Junior Einstein said:
Tasssadar, I was wondering if you could lower down the brightness a bit in recovery mode?
Click to expand...
Click to collapse
You can adjust it in settings>screen. If you don't have this option use the default theme.
Sent from my LG-P500 using xda premium
[noob][Q] How to remove custom theme? I'm on ver 2.4.4.0 and would like to flash 2.6.
Sent from my GT-P7510 using Tapatalk 4
jaibar said:
How to remove custom theme?
Click to expand...
Click to collapse
If you installed it delete /sdcard/TWRP/theme/ui.zip
Updated to TWRP 2.6.1.0.
EDIT: Currently, it crashes when restoring backup of boot.img. Working on a fix, shouldn't take long.
EDIT2: Dees_Troy is rather busy, so I've built TWRP 2.6.1.1 which fixes the crash by myself - http://goo.im/devs/Tassadar/p500 - you can't use goo.im method to install it though, as it is in different directory.
PLS!
Add support for UOT Kitchen!
On my sdcard lies for this AmonRa recovery zip
engr_exxi said:
Let me thank the OP first for creating twrp.
Since I have a hard-to-press power button this recovery really helps a lot.
No more pressing down hard on hardware buttons!
update:
hmm.. somehow just replacing the updater-binary doesn't fix the problem
update 2:
@OP
after a couple of research i stumbled upon this one that uses a twrp 2.6 too.
he stated that
what does he mean by format takes 2: format("MTD", "boot").?
if i found this line at updater-script of CM10.1.3 (line 11)
Code:
format("yaffs2", "MTD", "system", "0", "/system");
should i change it to?
Code:
format("yaffs2", "MTD");
format("system", "0");
format("/system");
If I remove all the code, as I flash the new zip, the old files are kept in system, its just like its being factory reseted.
Thanks
Update 3:
With a little bit of experiments leading to slight mind disturbances at the middle of the night...
I managed to successfully flash a kernel.
I used cm10.1.3 by armv6.
Added this binary (see attachments)
and modified the updater-script on the line 11 to
Code:
format("yaffs2", "MTD", "system", "0");
Click to expand...
Click to collapse
can u share ur zip file?
Related
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.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.1:
-Added USB OTG support
-Updated kernel from HTC (may result in short lag when rebooting out of recovery and a color shift when using aroma)
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout
CHANGELOG for 2.3.2.0:
-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
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
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.
XDA:DevDB Information
[RECOVERY][ONE-X/EVITA] TWRP 2.5.0.0 Touch Recovery! [2013-4-9], a Tool/Utility for the HTC One S
Contributors
eyeballer, dees_troy, bigbiff
Version Information
Status: Testing
Created 2013-09-16
Last Updated 2013-09-16
do stuffs here one day
This is awesome thank you.sucks that it won't restore cwm backups through.because I have three back ups of different roms
sent from a guy living in a van down by the river
WoW, this looks so ugly But working rly fine so far. I like it.
good work guys!
cheers
Midian666 said:
WoW, this looks so ugly But working rly fine so far. I like it.
good work guys!
cheers
Click to expand...
Click to collapse
Haha good thing its themable
sent from a guy living in a van down by the river
Will Aroma Installer work with this recovery?
Sent from my HTC VLE_U using Tapatalk 2
Pretty awesome change from cwm, I like it. Going to install on my gtablet tonight.
Sent from my HTC VLE_U using xda premium
Mathato said:
Will Aroma Installer work with this recovery?
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
Does not work
Dimson75 said:
Does not work
Click to expand...
Click to collapse
That's a deal breaker for me
sent from a guy living in a van down by the river
Yepp i really like that recovery, but without aroma support. No thanks!
Since none of us in TeamWin actually own this device we need logs to help debug issues you may hit.
If you find a bug or other error, do not just post saying "X doesn't work" - please pull a recovery.log and pastebin it along with what you were trying to do. If the device has usb/adb working, then "adb pull /tmp/recovery.log" alternatively, go to the Advanced menu and copy log to sdcard.
v2.1.7 is live, with working adb.
We need some logs from aroma installs..
EDIT: scratch that, pulled the downloads for a second to fix an issue.
EDIT2: DL link is back up, please test adb
Great work! I used TWRP on my HP TouchPad so far and really loved it. Was hoping you guys would have a One S version out soon -- thanks!!!
Development is booming now.
I missed TWRP had it on my Amaze.
So has anyone had issues with Aroma & this recovery ??
Dont suppose the Mount USB Storage option works either does it ??
My phones in the repair centre, So cant test........And before you all ask, Its not bricked Just a faulty antenna
Incredible work guys! Toast has been a part of every phone I've had since my Hero, glad that can now continue....
Edit: I've always had problems getting CM9/AOKP to run on my device. I installed this, flashed AOKP and it booted first try without a problem.....NICE! Don't know what the difference would be with CWM, but there is something.
eyeballer said:
v2.1.7 is live, with working adb.
We need some logs from aroma installs..
EDIT: scratch that, pulled the downloads for a second to fix an issue.
EDIT2: DL link is back up, please test adb
Click to expand...
Click to collapse
Thanks it worked with the Aroma instaler
Tried restoring a backup it looked like all went well till after boot. Got a "Process system is not responding" error and it freezes with no touch input.
Here is a logcat hopefully just before error shows.
http://pastebin.com/embed_js.php?i=aBCGSF3C
Edit: I don't think it's restoring the boot.img. I had it checked to back up, but coming from AOKP to a sense nandroid it wouldn't boot all the way until I reflashed the sense Kernel. Just FYI, thanks for this!
So does this backup and restore boot.img like cwm does kind of a big deal for us s-on people
sent from a guy living in a van down by the river
I should have made a follow up post, sorry. It is working well. I only had problems with my first rom that I restored with CWM then backed up with TWRP. Haven't had a problem since with roms I flashed with TWRP.
IRC on freenode: #sk8erwitskil
NEW: I have created a script to easily update to the latest version of my recovery.
- Download this file ----> updater.sh (updated to fix typo)
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh skyrocket
- it will reboot you into recovery
- starting in v14.2.1 it will automatically start installing and reboot when its done
Note: If your sdcard is not mounted on /mnt/sdcard then open the script and change the line that says path=/mnt/sdcard/sk8sUpdater to match your mount point. i.e. ICS users may have to change it to say path=/mnt/emmc/sk8sUpdater
Click to expand...
Click to collapse
I have ported touch recovery to Clockworkmod 6. I will be making updates to this just like my other touch recovery. I have added a few menu items and tweaks to make it like my CWM5 recovery.
Looking through the cwm code more in depth i have noticed MANY flaws with the code for new(er) phones that use /emmc instead of /sdcard as the main storage. i have now fixed those flaws in v9+.
Here is a video of how it works: --------> YOUTUBE LINK
Flashable zip:
cwm6027touch_v14.4.6_skyrocket.zip: ---------> DOWNLOAD
Click to expand...
Click to collapse
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
[/CODE]
Current Version:
v14.4.6
- added exFAT support
- some under the hood optimizations
Click to expand...
Click to collapse
Major update to how touch works now:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Whats in the extras menu?
- change bootanimation (this lets you select a bootanimation form your internal sdcard. it backs up your current bootanimation to /{internal sdcard}/clockworkmod/ba_backup/. it only backs up the original bootanimation so if you keep changing your bootanimation you will still only have your original one in ba_backup.)
- enable/disable one confirm (this makes it so you only have to scroll through one confirm selection when installing something instead of having to go through 10 of them to click yes)
- hide/show backup & restore progress (this makes it so the progress bar when you backup/restore doesnt show up and makes backups/restores a bit faster since it doesnt have to show you the progress and files its backing up)
- select android_secure on internal/external (use this to select where you have .android_secure. default is internal, so if you have it on external make sure to choose this once to set it up)
- aroma file manager (file explorer)
- create custom zip (this will create a custom rom from the currently installed files you have on your phone. it takes your /system partition and /boot partition and makes them into a zip file ready to be flashed. the end product will be in clockworkmod/custom_rom/. this has recently been fixed to work on all phones/roms
- choose custom openrecoveryscript (read THIS)
- recovery info (shows the version of recovery and the build date)
- Special Backup & Restore (backup and restore your kernel/boot and /misc partitions)
- Misc Nandroid Settings (change time zone, turn preload support on/off (default is off), enable md5 checking)
I used the odin install and now I cant boot into recovery at all. just goes to a black screen.
its fixed now
BaconStep said:
I used the odin install and now I cant boot into recovery at all. just goes to a black screen.
Click to expand...
Click to collapse
let me take a look.
sk8erwitskil said:
let me take a look.
Click to expand...
Click to collapse
almost fixed. uploading now
watching this
Hope to check this out soon! Gotta wait for a more stable release though.
Slightly off topic but what are the benefits in upgrading CWM? I'm on 5.5.0.4 touch and have always disregarded upgrading with each phone I root as they all seem to function the same.
Sent from my SGH-I727 using Tapatalk 2
lnfound said:
Slightly off topic but what are the benefits in upgrading CWM? I'm on 5.5.0.4 touch and have always disregarded upgrading with each phone I root as they all seem to function the same.
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Mostly bug fixes and compatibility issues.
This should be ready soon! Gweedo and utkanos are working on it as well so something good is coming
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
augh yes! i fixed it and its running smooth as buttah!!! ill add recovery.img and recovery.tar.md5 later but there is a flashable zip in the OP. just flash in recovery.
When wiping davlk, it throws like it was on CWM 5
E:unknown volume for path [/sd-ext]
Dismal Shadow said:
When wiping davlk, it throws like it was on CWM 5
E:unknown volume for path [/sd-ext]
Click to expand...
Click to collapse
yes thats expected. i dont know how many times this has been talked about. /sd-ext is a legacy option in cwm that was used for apps2sd. if you can find a cwm that doesnt show that error i would be shocked. the only reason it doesnt do it on my 5.5.0.4 touch recovery is because i took out the part where it prints it to the screen so people would stop asking about it. lol.
You are awesome, we need you over on the gsiii side...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Will this work for the t989?
Gotroot said:
Will this work for the t989?
Click to expand...
Click to collapse
Yea it should i flashed the first one put up and it wrked on my t989
Sent from my SAMSUNG-SGH-T989 using xda premium
Gotroot said:
Will this work for the t989?
Click to expand...
Click to collapse
yes it will work. but the fix permissions might not work. i have to make one specifically for the hercules. thats my project tomorrow.
So just to clarify. Download zip. Flash in current cwm touch and that's it?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
garydv2002 said:
So just to clarify. Download zip. Flash in current cwm touch and that's it?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yessir
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
RiNo808 said:
You are awesome, we need you over on the gsiii side...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
no poaching our devs!
deezhemi said:
no poaching our devs!
Click to expand...
Click to collapse
Heh.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
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:
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!
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.
Reserved.
Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]
Thx for this mate
Sent from my HTC Butterfly using xda premium
Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]
It had something wrong with the resolution? Sorry for my bad english^^
Sent from my HTC Butterfly using xda premium
resolution is indeed smaller than 1080p, thats why whole screen isnt occupied, perhaps next release can fix this?
fastcx said:
resolution is indeed smaller than 1080p, thats why whole screen isnt occupied, perhaps next release can fix this?
Click to expand...
Click to collapse
I don't own a device with the 1080x1920 resolution but once I do I'll get it fixed properly. For now there are custom themes that you can use instead, mostly in the HTC Droid DNA forums.
Thanks man, confirmed working on the x920e. Resolution is off, but I could give a cr** :cyclops:
[RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
goo manager says invalid MD5 checksum... on X920D
there is mistake on the site, it calls X920d as dlxu and X920e as dlxub1, whereas it is the opposite.
I looked at the theming guides and I missing something very fundamental - where to put theme? does anyone know?
So which one should we download? for x920D... dlxu or dlxub1?
PG101 said:
So which one should we download? for x920D... dlxu or dlxub1?
Click to expand...
Click to collapse
get into bootloader. On the top is written what type you have dlxu or dlxub1. And download image that matches your device
[RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]
So, does anyone know where to put theme files for this recovery? I'm tired of this quarter-screen GUI.
Is there an explanation of exactly what all functions of wipe there are? For e.g. if I wipe data.. what does it wipe? System? Etc..
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]
PG101 said:
Is there an explanation of exactly what all functions of wipe there are? For e.g. if I wipe data.. what does it wipe? System? Etc..
Click to expand...
Click to collapse
Check the FAQ in my signature.
wipe dalvik cache (in advanced) doesn't work for me...
does anyone else have this issue? I click on the option and then it reloads the same menu over and over again.
I experience very odd problem with TWRP.
Tried M7 ROM yesterday and realized that there is no much gain, but lot of small and annoying bugs. So I decided to restore my stock ROM from backup. So much surprise I couldn't do that! After restore my phone stuck on boot screen. No logcat, no shell. So I have no slightest idea what happens with phone.
My first guess was "same story as on Desire S - htcdev unlock doesn't let flash boot from recovery!".
There is no S-OFF yet for Butterflies, so I decided to flash boot myself. And again unpleasant surprise - TWRP backup is in unknown format (.win) and there is no way to fetch boot.img file...
So I had to flash killx kernel, but I hate do things that I didn't plan to do.
I still want to recover my old boot.
Is there way to do that?
Is there way to fetch other files from recovery (data, system, etc)?
[NOSTALGIC_HOWL]So pity there is no 4EXT recovery for Butterfly. It is sooo good[/NOSTALGIC_HOWL]
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]
SamePaul said:
I experience very odd problem with TWRP.
Tried M7 ROM yesterday and realized that there is no much gain, but lot of small and annoying bugs. So I decided to restore my stock ROM from backup. So much surprise I couldn't do that! After restore my phone stuck on boot screen. No logcat, no shell. So I have no slightest idea what happens with phone.
My first guess was "same story as on Desire S - htcdev unlock doesn't let flash boot from recovery!".
There is no S-OFF yet for Butterflies, so I decided to flash boot myself. And again unpleasant surprise - TWRP backup is in unknown format (.win) and there is no way to fetch boot.img file...
So I had to flash killx kernel, but I hate do things that I didn't plan to do.
I still want to recover my old boot.
Is there way to do that?
Is there way to fetch other files from recovery (data, system, etc)?
[NOSTALGIC_HOWL]So pity there is no 4EXT recovery for Butterfly. It is sooo good[/NOSTALGIC_HOWL]
Click to expand...
Click to collapse
boot.emmc.win is a boot.img with a different file name.
Dees_Troy said:
boot.emmc.win is a boot.img with a different file name.
Click to expand...
Click to collapse
Thank you for reply
Should I flash whole file as is or drop first 256 bytes?
I compared boot.img from Killx
Code:
ANDROID!ЂЭ:..Ђ`Ђ©ъ...Ђ*Ѓ......PЃ..`Ђ............................
console=ttyHSL0,115200,n8 androidboot.hardware=dlxub1 user_debug=31.
with boot.emmc.win
Code:
DЊ.€0.ЈЁoќb-ЛрvЁ§EљУ[ѓ†›aэAKФK.ЖR.ыМявK‡EЗ.ђ]’w^Џ.ѓЪд.Џ.€ЂЯѕџе›.ЖД›±.®“6ГА…/$4ѓluҐkBiтљA.]Aшgtк.љЁылLџЉ.$Ю}Ђ.Ѕ.&«S*UЂ*r.ющXWТш.ХK·№ЫЃлДт._$nуБГ†/Ё.Ъ0‘ЮјJА·ЕЭ..Ч..ю©‰.Й..b.ЛGQФ“;ІІI>3Ј°n‘.µfд..$~ЙЮHн:ѕ1»ЅщФL..Nфъ.G.ќЗkюпњ±.Ц.D.Иґ«SЭЏЫjшЛ·‡.я1?Љ8Ћ+1•CБE†tћ-®
ANDROID!ёуM..Ђ`Ђфу...Ђ*Ѓ......PЃ..`Ђ............................
console=ttyHSL0,115200,n8 androidboot.hardware=dlxub1 user_debug=31.
first 256 bytes is something completely different, but then continues pretty similar stuff.
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.
DOWNLOAD:Better to scroll down for New TWRP
>>Hit Thanks First<<
Steps to Install TWRPExtract It anywhere on pc
Connect ur mobile in fastboot mod(green color Power+ Volume Up)
go to extracted folder
run runme.bat
follow on screen instruction
That's it
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.
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
BugsEvery thing is working fine... but still if u found any bug Report Here...
Volla.. New TWRP is Updated Here is the link of Default one
Here is for white theme
Here is for Black one(My Fav)
CreditSHUVO for providing this
Abdul for test
Saurabh Singhal for giving me Link of themes i didnt use that directly
And rest of the TEAM like a boss
Me..
Moment for Which A7 users were waiting...
Here is the TWRP for A7
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.
Download
Hit thanks FirstChange Log-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
Instruction to installConnect your phone to pc in fastboot mod..(Green colour Mod)
Extract the zip anywhere on pc
Open that extracted folder
Run recovery.bat
Follow on screen instruction and you are done
Credit
Vietnamese developers
jaydev6681
Click to expand...
Click to collapse
Enjoy
Best a Man can get no gillete but TWRP recovery
The Droid Master said:
Best a Man can get no gillete but TWRP recovery
Click to expand...
Click to collapse
Hehe True..
Is this the same as the 90% Eng in A5 thread?
shreyans4020 said:
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.
DOWNLOAD:>>Here<<
Steps to Install TWRPExtract It anywhere on pc
Connect ur mobile in fastboot mod(green color Power+ Volume Up)
go to extracted folder
run runme.bat
follow on screen instruction
That's it
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.
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
BugsEvery thing is working fine... but still if u found any bug Report Here...
CreditSHUVO for providing this
Me..
Click to expand...
Click to collapse
hey bro make it for A7 just have to add touch screen drivers
Re: [RECOVERY][Spice Mi-355/Karbonn A5] TWRP 2.3.1.1 Touch Recovery!
arafsheikh said:
Is this the same as the 90% Eng in A5 thread?
Click to expand...
Click to collapse
U can read the change log
Sent from my Karbonn A5 using xda app-developers app
Re: [RECOVERY][Spice Mi-355/Karbonn A5] TWRP 2.3.1.1 Touch Recovery!
xyagnesh.davex said:
hey bro make it for A7 just have to add touch screen drivers
Click to expand...
Click to collapse
Hmm may be but then i need a helper
Sent from my Karbonn A5 using xda app-developers app
Re: [RECOVERY][Spice Mi-355/Karbonn A5] TWRP 2.3.1.1 Touch Recovery!
Touch not working on A7...plz make it for A7...Eklovya will help u...:thumbup:
Volla...) As on the request of every single Spice Mi355 and Karbonn A5 user I proud to present TWRP 2.4.0.0r1
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.
I would like to thank TeamWin for their efforts and supporting open source with this recovery.
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
Dev Note: This Version is 100% English
I am glad to say this time TWRP will be in 3 Themes use any one of them u like...Congo
Download Default one
Default one directly flashable through any recovery
How to install r u kidding me check the first post...
Next ThemeDownloadWhite one
White Flashable
One More ThemeDownloadBlack (My fav)
Black Flashable
Dont like TWRP no problem Here is flashable zip of cwm
shreyans4020 said:
Volla...) As on the request of every single Spice Mi355 and Karbonn A5 user I proud to present TWRP 2.4.0.0r1
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.
I would like to thank TeamWin for their efforts and supporting open source with this recovery.
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
Dev Note: This Version is 100% English
I am glad to say this time TWRP will be in 3 Themes use any one of them u like...Congo
Download Default one
Default one directly flashable through any recovery
How to install r u kidding me check the first post...
Click to expand...
Click to collapse
Once again thanks bro :good:
The Droid Master said:
Once again thanks bro :good:
Click to expand...
Click to collapse
Try that on Ics... hope this time it will work
Sent from my Spice-Mi355 using xda app-developers app
Great work dude! The Black one is really awesome and clean
Also the new version has the option to wipe android_secure and that is great!
arafsheikh said:
Great work dude! The Black one is really awesome and clean
Also the new version has the option to wipe android_secure and that is great!
Click to expand...
Click to collapse
Ur request came true.... now go and hit tnx...
Sent from my Spice-Mi355 using xda app-developers app
shreyans4020 said:
Ur request came true.... now go and hit tnx...
Sent from my Spice-Mi355 using xda app-developers app
Click to expand...
Click to collapse
Haha, done...Also keep bring the latest updates. TWRP really rocks, I feel like being in the recovery only
arafsheikh said:
Haha, done...Also keep bring the latest updates. TWRP really rocks, I feel like being in the recovery only
Click to expand...
Click to collapse
No bro this is my last project for this phone and may be the last day on xda for next 3 mnths
Sent from my Spice-Mi355 using xda app-developers app
shreyans4020 said:
No bro this is my last project for this phone and may be the last day on xda for next 3 mnths
Sent from my Spice-Mi355 using xda app-developers app
Click to expand...
Click to collapse
What are you saying?!? Kya hui?
[ THIS POST IS TEAMWIN'S STOCK TWRP POSTING. USE OF THE WORDS "US" AND "OURS" MEANS "DEES_TROY AND TEAMWIN" NOT HASHCODE ]
*** ALL CREDIT FOR TWRP BELONGS TO DEES_TROY AND TEAMWIN. ***
They do a BANG UP job on making a fantastic customizable touch-based recovery.
SEE BOTTOM OF THIS POST FOR DOWNLOAD / INSTALL INSTRUCTIONS
Donate to TeamWin:
http://www.teamw.in/project/twrp2
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848
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.
Tablet look:
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **
DOWNLOAD:
[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE.
IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR KINDLE FIRE HD'S ]
You can download a flashable recovery zip and place in your SDCARD area on the device:
ON THE FOLLOWING DEV-HOST LINK
USE THE BLUE "DOWNLOAD NOW" BUTTON
-- DO NOT INSTALL AN EXECUTABLE DOWNLOADER TO YOUR SYSTEM! --
I'LL LOOK FOR A BETTER HOST WHEN I GET MORE TIME.
Mirror 1 : Download recovery zip from Dev-Host
INSTALL INSTRUCTIONS:
While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button)
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
KNOWN ISSUES:
[07/08] Disabled the screen blank due to a display issue where screen doesn't come back on well.
BUGS:
First: I'd read through this thread and see if your issue isn't answered.
Second: Try googling for it
Third: If it seems like a Kindle Fire HD issue, then post in the thread.
Lastly: If you have found a bug, please consider posting it to TeamWin's 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 #kindlefire-dev or #twrp on Freenode with your IRC client or just click this link.
error
im ending up with this error when i try to flash
Can you check the md5sum on that file and make sure it matches 4056520ee7b13be01d42d785cca2b15e?
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Hashcode said:
Can you check the md5sum on that file and make sure it matches 4056520ee7b13be01d42d785cca2b15e?
Click to expand...
Click to collapse
the md5 does match
tried it again and this time it worked thanks hashcode
seokhun said:
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Click to expand...
Click to collapse
Yes, I can probably do a .zip update. I'll need a night or 2. Been pretty busy.
Hashcode said:
Yes, I can probably do a .zip update. I'll need a night or 2. Been pretty busy.
Click to expand...
Click to collapse
and how is the kernel goings man?, good job with this
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery for KFireHD 7" [2013-04-02]
seokhun said:
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Click to expand...
Click to collapse
Hey you can install the new version through fireflash also I just did with no problem
Sent from my KFTT using xda premium
As in, plugging in the .img recovery file Hashcode provided, leave everything else blank and just flash? Are you sure? Seems a little risky to me. If someone else can verify that, I'll do it, but I'm willing to wait for Hashcode's .zip, no offense.
seokhun said:
I'm willing to wait for Hashcode's .zip, no offense.
Click to expand...
Click to collapse
+1
Sent from my KFHD using xda premium
I promise u it works will post a video of proof by about 12 tonight if everyone would do this and leave hash code alone about petty crap maybe we would have cm 10.1 and custom kernel by :screwy:
Sent from my LG-E970 using xda premium
Respectfully disagree,
If people start bricking their devices because of unnecessary flashes, the threads will be overwhelmed with people griping and begging for help...
Personally I am waiting for cm10 as well and have not even installed recovery yet on my device due to this..
But I do understand that twrp allows a proper backup and honestly is something all android devices should have installed
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
Respectfully disagree,
If people start bricking their devices because of unnecessary flashes, the threads will be overwhelmed with people griping and begging for help...
Personally I am waiting for cm10 as well and have not even installed recovery yet on my device due to this..
But I do understand that twrp allows a proper backup and honestly is something all android devices should have installed
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Jester6 said:
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Click to expand...
Click to collapse
:good:+1
Jester6 said:
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Click to expand...
Click to collapse
You got wrong what he said. The user above stated that we're wasting hashcode's time by making him do zip updates for twrp (instead of flashing them), and he (the one you quoted) added that is better to update twrp with ZIPs since its less risky.
Sent from my KFTT using xda app-developers app
jailuis said:
You got wrong what he said. The user above stated that we're wasting hashcode's time by making him do zip updates for twrp (instead of flashing them), and he (the one you quoted) added that is better to update twrp with ZIPs since its less risky.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Either way, it makes little to no sense. I understand that hashcode has a lot on his plate but update zips are a simple enough process and take a small amount of time/work, now I don't know that about twrp as its not officially supported (to my knowledge) but an update zip for a ROM is a very easy process, I'm sure there's a bit involved in making twrp work for the kfhd but I don't imagine its crazy.
Thank You Hashcode for your efforts. An update zip would be sweet. Keep up the great work!
This is a Kinology HD using XDA Premium
video with instructions and proof of concept
seokhun said:
As in, plugging in the .img recovery file Hashcode provided, leave everything else blank and just flash? Are you sure? Seems a little risky to me. If someone else can verify that, I'll do it, but I'm willing to wait for Hashcode's .zip, no offense.
Click to expand...
Click to collapse
yes that's correct i need no one else to verify this but there's a video on my channel here>http://www.youtube.com/user/choppedncut79cutlass/videos <as for the rest of these space wasting comments i reply in the morn nite all work in the morning
So I got brave and decided to work with fastboot, and I can flash with the standard platform-tools procedure. I know I have fastboot using Hashcode's "getvar product" command, and booted into fastboot successfully. However, I don't know how to flash using the "fastboot -i 0x1949" command. Do I first CD to the folder that the file is placed in? A little help for a noob will be greatly appreciated, Hashcode, or anyone else well-versed in fastboot. Thank you!
I'd also like to know if the standard procedure will also work here. In other words, if I place the file in \platform-tools and ran the "fastboot flash <filename>.img", would it work? I'm afraid it would fail because of the Kindle's locked bootloader and how we're working with a 2nd one. Sorry, I'm very new to this whole bootloader thing and willing to learn.
Where ever fastboot is, I think.
This is a Kinology HD using XDA Premium