Develop Bugs

{CLK1.5}with 4ext RC5 Themed in one zip

Here CLK 1.5 with 4EXT RC5 themed working 100%

kasserx said:
Here CLK 1.5 with 4EXT RC5 themed working 100%
Click to expand...
Click to collapse
Nice, where is the zip..???

Whats the difference between this and CWM's Ext3? Is it faster or something?

mountainmon said:
Whats the difference between this and CWM's Ext3? Is it faster or something?
Click to expand...
Click to collapse
.... 4EXT... not EXT4... wakie wakie...
on that note, its nice to see, but putting the crapple logo on our wonderful hd2 makes me want to "slaps OP with a rather large trout"... to quote old IRC emotes..

That will not say anything, but try not to lose anything
ex4 faster than ext3

lol apple!!!!! hope this is some kind of a joke

kasserx said:
That will not say anything, but try not to lose anything
ex4 faster than ext3
Click to expand...
Click to collapse
Hi, there's a mistake with the name, 4ext is NOT the same as EXT4. Yes, it seems equal but there two different things. The object of that thread is a kind of recovery.
A question for the author: the first edition of 4ext that I tried doesn't power on the phone while is plugged to charger. Is this item corrected right now?

look at Attached Thumbnails you'll see ext4 format (sd-ext) that not fake

Rando81 said:
lol apple!!!!! hope this is some kind of a joke
Click to expand...
Click to collapse
I think you did not see the word Themed in the title

kasserx said:
I think you did not see the word Themed in the title
Click to expand...
Click to collapse
no, we just wished you had put iCrapple themed instead of just themed...
And the misunderstanding continue to fly...
EXT# <- this is the formatting for the file system, with EXT4 being better (in most cases) in terms of performance then EXT3 (sadly, no headway on EXT4 NAND.. QQ)
4EXT <- this is an alternative recovery platform much like CWM and AmonRa and TWRP, it has the ability to format (external media only at the moment) your media to EXT4 and set specifics like size, offset, and even alignment, its REALLY good when setting things up for a first run*
Please READ and stop confusing the two... ones a file system, and ones a TOOL that CAN use said file system;...
*I have used 4EXT to format all 6 of my MicroSD cards and align them properly, FAT32 -> EXT4 -> SWAP in partition layout, or Storage -> App2SD -> PseudoRAM

Hammerfest said:
no, we just wished you had put iCrapple themed instead of just themed...
And the misunderstanding continue to fly...
EXT# <- this is the formatting for the file system, with EXT4 being better (in most cases) in terms of performance then EXT3 (sadly, no headway on EXT4 NAND.. QQ)
4EXT <- this is an alternative recovery platform much like CWM and AmonRa and TWRP, it has the ability to format (external media only at the moment) your media to EXT4 and set specifics like size, offset, and even alignment, its REALLY good when setting things up for a first run*
Please READ and stop confusing the two... ones a file system, and ones a TOOL that CAN use said file system;...
*I have used 4EXT to format all 6 of my MicroSD cards and align them properly, FAT32 -> EXT4 -> SWAP in partition layout, or Storage -> App2SD -> PseudoRAM
Click to expand...
Click to collapse
Thanks to cjward23 and friends for testing, 4EXT Recovery is now also available for the Desire Z / G2.
Quick note about themes:
Available themes as of Aug/28:
Themes by pravus_nephilim
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
• Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
• Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
• New option: check and optionally repair the file system on your sdcard (fat32)
• Removed duplicate format cache option inside the format menu (wipe cache does the same)
• When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
• Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
• Added new size option (128mb) to the partitioning menu per request
• Parted is no longer used to format fat32 in the partition menu
-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
• 4EXT Recovery themes should now stay when formatting /system or flashing new roms
• New option: format /sdcard fat32
• New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)
enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
• Size for recovery greatly reduced
New 4EXT Recovery Control Features
• Please see www.4ext.net for more.
• Fix permissions
• Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
• As an example, the following would be possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Features: Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!
not all features may be relevant for all devices
Displays additional information:• Identifies your current rom and displays its name
• Current filesystems on your partitions
• Free space remaining of all of your volumes
• Current battery charge level
Backup | Restore: • Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
• Tar backups (can be switched on or off)
• Complete CWMR5 compatibility
• All Backups you create will be named after your currently installed Rom for easier identification.
• Never unwillingly get "downgraded" to EXT3 again
• Always restores backups using the file systems you HAD on your partitions at the time of creation!
-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.
• You can manually change any existing Backup to ext4 or ext3
-> so that after a restore, all partitions and up with the file system you wanted!
• Advanced Backup: backup only a single partition
• Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:• When you wipe or format it will always use the same file system you currently have.
-> but you can change that
• When you format ext4 it will always create an aligned file system
•Correctly identifies unformatted sd-ext partitions
-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu
•Filesystem check and repair option in advanced menu
Partitioning:• Alignment check of your partitions
• Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
• (RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
• All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:• Integrated md5sum checking option
Themes:• Customize all colours used throughout recovery
• Use your own icons, background images, progress bars.. more to come.
• Assign different backgrounds to different menu categories (version >= 2.1.2)
• Create a flashable zip for others to flash your theme.
Menus:• Most popular menu items rearranged
• Format menu
• Power Menu + option to reboot into bootloader
• Less "No's" in confirmation dialogues
• Changed Advanced Restore: first select what you want to restore, then select the backup
-> Useful for restoring from "Advanced Backups"
4ext.prop:• Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
• Change all settings conveniently with 4EXT Recovery Control
• Many more options to come
• Share your settings / themes by packing your config into a flashable theme
Other stuff:• USB Storage Autostart (must be switched on)
• Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)
-> you could even partition your sdcard from your PC while connected via USB
• Switch haptic feedback on/off
• You don't need to reboot recovery if you transferred a file to show up in the install menu.
-> This bug affected only some users with either CWMR or previous versions of 4EXT.
• Button backlights (Desire S, Desire HD and Incredible S only)
Download:
•All downloads are now available through 4EXT Recovery Updater. It's free, no ads, no tracking, no nothing, don't worry
.. and of course via 4EXT Recovery Control
• This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
• It also notifies you when there are any new critical bugs found
• Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
• You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control •Free version: Recovery Updater
•Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :•Flash as many zip files you want in one go
•Automatically calculate and display the md5sums of all zip files you are going to flash
•Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
•Optionally, but highly not recommended:
If md5sums don't match but you REALLY NEED that backup BADLY, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup to "forcefully" restore it!
• Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
• Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
• As an example, the following is possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
• Much, much more! See www.4ext.net
Recovery theming • Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
• Change all colours with live preview and a nice colour picker.
__________________
Please send bugreports | feature requests via:
4EXT Recovery Control or Updater App
4EXT Recovery Touch 1.0.0.3 RC 3
Free 4EXT Recovery Updater v2.2.5
Want to support development of 4EXTRecovery?
Check out 4EXT Recovery Control
please read this full it is from www.4ext.net ((for desire hd sensation ...etc)) now for hd2
http://forum.xda-developers.com/showthread.php?p=17748849

hd2
kasserx said:
Thanks to cjward23 and friends for testing, 4EXT Recovery is now also available for the Desire Z / G2.
Quick note about themes:
Available themes as of Aug/28:
Themes by pravus_nephilim
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
• Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
• Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
• New option: check and optionally repair the file system on your sdcard (fat32)
• Removed duplicate format cache option inside the format menu (wipe cache does the same)
• When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
• Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
• Added new size option (128mb) to the partitioning menu per request
• Parted is no longer used to format fat32 in the partition menu
-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
• 4EXT Recovery themes should now stay when formatting /system or flashing new roms
• New option: format /sdcard fat32
• New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)
enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
• Size for recovery greatly reduced
New 4EXT Recovery Control Features
• Please see www.4ext.net for more.
• Fix permissions
• Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
• As an example, the following would be possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Features: Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!
not all features may be relevant for all devices
Displays additional information:• Identifies your current rom and displays its name
• Current filesystems on your partitions
• Free space remaining of all of your volumes
• Current battery charge level
Backup | Restore: • Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
• Tar backups (can be switched on or off)
• Complete CWMR5 compatibility
• All Backups you create will be named after your currently installed Rom for easier identification.
• Never unwillingly get "downgraded" to EXT3 again
• Always restores backups using the file systems you HAD on your partitions at the time of creation!
-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.
• You can manually change any existing Backup to ext4 or ext3
-> so that after a restore, all partitions and up with the file system you wanted!
• Advanced Backup: backup only a single partition
• Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:• When you wipe or format it will always use the same file system you currently have.
-> but you can change that
• When you format ext4 it will always create an aligned file system
•Correctly identifies unformatted sd-ext partitions
-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu
•Filesystem check and repair option in advanced menu
Partitioning:• Alignment check of your partitions
• Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
• (RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
• All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:• Integrated md5sum checking option
Themes:• Customize all colours used throughout recovery
• Use your own icons, background images, progress bars.. more to come.
• Assign different backgrounds to different menu categories (version >= 2.1.2)
• Create a flashable zip for others to flash your theme.
Menus:• Most popular menu items rearranged
• Format menu
• Power Menu + option to reboot into bootloader
• Less "No's" in confirmation dialogues
• Changed Advanced Restore: first select what you want to restore, then select the backup
-> Useful for restoring from "Advanced Backups"
4ext.prop:• Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
• Change all settings conveniently with 4EXT Recovery Control
• Many more options to come
• Share your settings / themes by packing your config into a flashable theme
Other stuff:• USB Storage Autostart (must be switched on)
• Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)
-> you could even partition your sdcard from your PC while connected via USB
• Switch haptic feedback on/off
• You don't need to reboot recovery if you transferred a file to show up in the install menu.
-> This bug affected only some users with either CWMR or previous versions of 4EXT.
• Button backlights (Desire S, Desire HD and Incredible S only)
Download:
•All downloads are now available through 4EXT Recovery Updater. It's free, no ads, no tracking, no nothing, don't worry
.. and of course via 4EXT Recovery Control
• This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
• It also notifies you when there are any new critical bugs found
• Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
• You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control •Free version: Recovery Updater
•Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :•Flash as many zip files you want in one go
•Automatically calculate and display the md5sums of all zip files you are going to flash
•Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
•Optionally, but highly not recommended:
If md5sums don't match but you REALLY NEED that backup BADLY, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup to "forcefully" restore it!
• Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
• Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
• As an example, the following is possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
• Much, much more! See www.4ext.net
Recovery theming • Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
• Change all colours with live preview and a nice colour picker.
__________________
Please send bugreports | feature requests via:
4EXT Recovery Control or Updater App
4EXT Recovery Touch 1.0.0.3 RC 3
Free 4EXT Recovery Updater v2.2.5
Want to support development of 4EXTRecovery?
Check out 4EXT Recovery Control
please read this full it is from www.4ext.net ((for desire hd sensation ...etc)) now for hd2
http://forum.xda-developers.com/showthread.php?p=17748849
Click to expand...
Click to collapse
are u sure this works on hd2 as read post on link above and it doesnt mention our hd2 i dont want 2 brick my phone if its not compatible???!?

Hi, zip in first post contains cLk 1.4, not 1.5 am I right ?
BTW thanks for sharing

no reply
maddoc1007 said:
are u sure this works on hd2 as read post on link above and it doesnt mention our hd2 i dont want 2 brick my phone if its not compatible???!?
Click to expand...
Click to collapse
since no 1 answered this i take it its not for.hd2s?

maddoc1007 said:
since no 1 answered this i take it its not for.hd2s?
Click to expand...
Click to collapse
On my HD2 EU it worked, but i can't change current theme to any another 4EXT theme.

CyCaHuH-uBAH said:
On my HD2 EU it worked, but i can't change current theme to any another 4EXT theme.
Click to expand...
Click to collapse
you can re-flash from beginning
see this video from my hd2
http://www.youtube.com/watch?v=T_BIaVduUDs&feature=player_embedded
http://www.youtube.com/watch?v=T_BIaVduUDs&feature=player_embedded
see this pictures also from my hd2
go to medifire ( image view )
http://www.mediafire.com/?vbe9sfz2b...mv84ibfd3a2r3,jpnioltu8lqa1nd,xr67icguou77p1f

this is not clk 1.5 its 1.4
Sent from my HTC HD2 using XDA App

men this is no clk 1.5 this is clk is 1.4.1 ....

Is it possible to install & launch "touch" versions of 4Ext recovery? Classic version is too old for now and cant do as much as Touch.

[RECOVERY][CWM] ClockworkMod v6.0.2.7 Touch v14.4.6 | exFAT support (01/11/13)

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_hercules.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)

hellz yes!!!
Sent from my SGH-T989 using xda premium

Thank you and welcome back brother!

Thanks buddy! will report if I come across any bugs

Working great and looks beautiful do u recommend to do the hide the progress option or to not?

casonswag said:
Working great and looks beautiful do u recommend to do the hide the progress option or to not?
Click to expand...
Click to collapse
its up to you. if you want to know how far along the progress is then show it. but itll take a little bit longer to backup. or if you dont care about how far along you are and just want it to be done in the fastest time possible then hide it.

when i go into cwm it says read only file system...?...how do i fix that...cause my system is monted and my sd card is mounted...pleasse help...thanks in advance...

ooo this is sweet , thanx, now i can delet the other thread and leave
only the non-touch version!

if your .android_secure folder lives on your external sdcard then download this file -----------> [url said:
http://d-h.st/PdV[/url]
Click to expand...
Click to collapse
I do see that folder in my external, micro sd right?? So, i just need this file only?? Its the recorvery itself..??
Sent from my SGH-T989

phordych05 said:
when i go into cwm it says read only file system...?...how do i fix that...cause my system is monted and my sd card is mounted...pleasse help...thanks in advance...
Click to expand...
Click to collapse
can you please explain more? what are you trying to do when it says read only file system? are you trying to adb something to your system partition? you need to remount it as rw before you can put something there. thats always the case.
noodles2224 said:
I do see that folder in my external, micro sd right?? So, i just need this file only?? Its the recorvery itself..??
Sent from my SGH-T989
Click to expand...
Click to collapse
yes if you have .android_secure in /sdcard then download the secondary one

I hate to be "that guy" who asks this question, but...
Will this play nice with installing the various ROM's for this phone? Although I have never personally had a problem with installing any ROM's on the various recoveries, people always report problems with certain combinations.

I downloaded this last night and used it right away... This takes waaaay too long to do a backup. Close to 15 mins... too long for me

TWRP all day, everyday. Why bother with prehistoric recoveries.

tikay00 said:
TWRP all day, everyday. Why bother with prehistoric recoveries.
Click to expand...
Click to collapse
Dude why are you going to every thread Trolling making nonsense comments thats not needed ?

sk8erwitskil said:
can you please explain more? what are you trying to do when it says read only file system? are you trying to adb something to your system partition? you need to remount it as rw before you can put something there. thats always the case.
yes if you have .android_secure in /sdcard then download the secondary one
Click to expand...
Click to collapse
Well i have it in /sdcard/external_sd not just /sdcard. Still download the second one right? Sorry but with this samsung internal and external, sometimes just saying sdcard is a little confusing..
Sent from my SGH-T989

scribbles92 said:
I downloaded this last night and used it right away... This takes waaaay too long to do a backup. Close to 15 mins... too long for me
Click to expand...
Click to collapse
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
noodles2224 said:
Well i have it in /sdcard/external_sd not just /sdcard. Still download the second one right? Sorry but with this samsung internal and external, sometimes just saying sdcard is a little confusing..
Sent from my SGH-T989
Click to expand...
Click to collapse
correct. because /sdcard/external_sd is how your OS mounts it. but in recovery it will be mounted as /sdcard. for samsung devices the stock way to mount storage is: internal = /emmc, external = /sdcard. depending on what rom you use though the developer of that rom may change the way that the OS mounts it because he prefers a different way. but in recovery i set it to be internal = /emmc, external = /sdcard

tikay00 said:
TWRP all day, everyday. Why bother with prehistoric recoveries.
Click to expand...
Click to collapse
cool story, bro

sk8erwitskil said:
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
Click to expand...
Click to collapse
Oh ok, thanks sk8er... I was looking for another recovery and hadn't read up on it so... maybe I will give this another shot. (I'm actually coming from your other recovery -CWMR 5.5.0.4)

sk8erwitskil said:
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
correct. because /sdcard/external_sd is how your OS mounts it. but in recovery it will be mounted as /sdcard. for samsung devices the stock way to mount storage is: internal = /emmc, external = /sdcard. depending on what rom you use though the developer of that rom may change the way that the OS mounts it because he prefers a different way. but in recovery i set it to be internal = /emmc, external = /sdcard
Click to expand...
Click to collapse
I hate to ask this but how do I know if it's located there or not?
Sent from my SAMSUNG-SGH-T989 using xda premium

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

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!

Dees_Troy is one of the best and nicest developers here, he did it all in like 5 minutes
Kudos brother, this is a great addiction for the Wonder!

sorry , is the image size 7.984MB ?

hadidjapri said:
sorry , is the image size 7.984MB ?
Click to expand...
Click to collapse
4.37MB, MD5 is 4c689ba24c1657540d8094124bf1e155

Dees_Troy said:
Direct Download
Turn the device off. Press and hold volume down, volume up, and power until the device boots, then on your computer:
fastboot flash recovery openrecovery-twrp-2.3.2.3-mako.img
Click to expand...
Click to collapse
this link refers me to the file with 7.984MB

hadidjapri said:
this link refers me to the file with 7.984MB
Click to expand...
Click to collapse
Ahhh, that is what I get for copying and pasting >_<

Dees_Troy said:
Ahhh, that is what I get for copying and pasting >_<
Click to expand...
Click to collapse
you get me bricked my phone :crying:
i hope nobody do the same mistake as i am by flashing "extreme huge" recovery.img
i didn't notice that ancora's recovery partition only capped to 7.5MB :crying:
well, it's not a problem. ssc is near my house
thanks for porting TWRP to ancora :good:

post no weighted ANCORA WAE LAH ....!:good:

hadidjapri said:
you get me bricked my phone :crying:
i hope nobody do the same mistake as i am by flashing "extreme huge" recovery.img
i didn't notice that ancora's recovery partition only capped to 7.5MB :crying:
well, it's not a problem. ssc is near my house
thanks for porting TWRP to ancora :good:
Click to expand...
Click to collapse
Odin should be able to fix it.

Dees_Troy said:
Odin should be able to fix it.
Click to expand...
Click to collapse
well, ancora's download mode sucks. it wastes me almost 1,5hours only stucked in "press up to continue"
gonna try the twrp after ssc fix my phone :good:

Testing it..
Sent from my GT-P5100 using xda premium

Thanks for porting it!

Can I flash this with adb and this command? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
-sent from my awesome phone-

hotheabilly said:
Can I flash this with adb and this command? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
-sent from my awesome phone-
Click to expand...
Click to collapse
Tested it, yes it works. But I reverted to CWM for a reason.
Sent from my GT-I8150 using xda app-developers app

Kreaz said:
Tested it, yes it works. But I reverted to CWM for a reason.
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Yes it works for me too, and yes I'm back to cwm for some reason too
-sent from my awesome phone-

comment removed.

hotheabilly said:
Yes it works for me too, and yes I'm back to cwm for some reason too
-sent from my awesome phone-
Click to expand...
Click to collapse
I screwed up ma phone. I flashed TWRP via ADB. When i reboot to recovery it goes to CWM. When i switch on normally it goes to TWRP!!! Now im havin 2 recoveries and i cant boot to SlimBean!!!!!! Any fix?!?!?
Edit: I did a full wipe and Restored my system. Thanks to CWM!!

jassim007 said:
I screwed up ma phone. I flashed TWRP via ADB. When i reboot to recovery it goes to CWM. When i switch on normally it goes to TWRP!!! Now im havin 2 recoveries and i cant boot to SlimBean!!!!!! Any fix?!?!?
Edit: I did a full wipe and Restored my system. Thanks to CWM!!
Click to expand...
Click to collapse
lololol you probably format your ROM partition by your command line and replacing the whole rom to TWRP, but this is the first case I've ever seen!

hotheabilly said:
lololol you probably format your ROM partition by your command line and replacing the whole rom to TWRP, but this is the first case I've ever seen!
Click to expand...
Click to collapse
Is there .tar format for flashing TWRP via Odin?

Twrp.3.1.0-0 ??? Just a few questions....

So the newly released twrp 3.1.0-0 has been released and i was wondering if it will be better than my unreleased twrp 3.0.4-1 and in better i mean will it be more compatible and stable with nougat on oneplus 3 , i chose version 3.0.4-1 because everyone seemed to be having problems with the official versions if anybody has any knowledge about this new recovery then please comment , here is a list of updates to the new twrp -
Vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
ADB backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
Tweak MTP startup routines (mdmower)
Support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
Support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
Better indicate to users that internal storage is not backed up (Dees_Troy)
Improve automatic determination of TW_THEME (mdmower)
Minimal getcap and setcap support (_that)
Try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
Shut off backlight with power key (mdmower)
Timeout during FDE decrypt (Dees_Troy and nkk71)
Support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
Boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
Support for AB OTA zips (Dees_Troy)
Support new Android 7.x log command (Dees_Troy)
Update recovery sources to AOSP 7.1 (Dees_Troy)
Numerous bugfixes and improvements by too many people to mention

OT : You sound like some random private channel Indian reporter..

sarus_b said:
OT : You sound like some random private channel Indian reporter..
Click to expand...
Click to collapse
Hahahaha i don't know how on earth you came up with that assumption but no i am a white male that lives in the UK...

I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...

Xceeder said:
I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...
Click to expand...
Click to collapse
Are you using F2FS for data and cache? Also pls report if first boot of new 3.1 TWRP has wiped Internal storage files (/sdcard) like it did for many using f2fs for data..

arvindgr said:
Are you using F2FS for data and cache? Also pls report if first boot of new 3.1 TWRP has wiped Internal storage files (/sdcard) like it did for many using f2fs for data..
Click to expand...
Click to collapse
I had that issue but it only happened when I used open gapps. They seem to be having a lot of issues with this device.
EDIT: Nope, it happened using dynamic gapps too. Has happened on multiple ROMS, must be a TWRP/F2FS issue.
Double Edit: Happened on EXT4 as well.

JohnHorus said:
I had that issue but it only happened when I used open gapps. They seem to be having a lot of issues with this device.
Click to expand...
Click to collapse
Seems unreleased 3.0.4 is really stable on Nougat F2FS devices., Until update for official 3.1 comes fixing those issues, I'll stick with prev. version. Thanks for trying and posting here..

arvindgr said:
Seems unreleased 3.0.4 is really stable on Nougat F2FS devices., Until update for official 3.1 comes fixing those issues, I'll stick with prev. version. Thanks for trying and posting here..
Click to expand...
Click to collapse
Haha... yeah. Nah. It actually just happened for me using dynamic gapps, so forget about that. I had it happen all the time on Lineage, so I assumed it was Lineage at first. I switched to AOSP-Extended, and only had it happen once, when I tried using open gapps. I switched to dynamic gapps for other reasons, and it never happened in 4 or 5 flashes, so I assumed it was open gapps.
BUT it just happened to me, maybe 20 minutes after posting that, using AOSP-Ex and dynamic gapps. So at this point I'm like 100% positive it's this messed up TWRP, not sure if it's F2FS related or not as I've only ever used F2FS, but after this I may just start using EXT4.
Edit: AANNNDD it happened on EXT4 as well... at least it only happens during initial setup.

Xceeder said:
I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...
Click to expand...
Click to collapse
There shouldn't be any issues since 3.0.4-1 was developed by a member of TWRP team (jcadduono) specifically for the 3 and the 3T and TWRP seem to have merely polished it and posted it as 3.1.0
If you read the description of 3.1.0 on the TWRP site, you will see that it also mentions jcadduono as the developer.

JohnHorus said:
Haha... yeah. Nah. It actually just happened for me using dynamic gapps, so forget about that. I had it happen all the time on Lineage, so I assumed it was Lineage at first. I switched to AOSP-Extended, and only had it happen once, when I tried using open gapps. I switched to dynamic gapps for other reasons, and it never happened in 4 or 5 flashes, so I assumed it was open gapps.
BUT it just happened to me, maybe 20 minutes after posting that, using AOSP-Ex and dynamic gapps. So at this point I'm like 100% positive it's this messed up TWRP, not sure if it's F2FS related or not as I've only ever used F2FS, but after this I may just start using EXT4.
Click to expand...
Click to collapse
I only have the data partition as f2fs if that's any help and my device is not encrypted... As for the recent twrp it works fine with me i can back up and restore nandroids as well as flashing zip files..

tnsmani said:
There shouldn't be any issues since 3.0.4-1 was developed by a member of TWRP team (jcadduono) specifically for the 3 and the 3T and TWRP seem to have merely polished it and posted it as 3.1.0
If you read the description of 3.1.0 on the TWRP site, you will see that it also mentions jcadduono as the developer.
Click to expand...
Click to collapse
Yeah i thought everything would be fine i was just testing it for other people...

[RECOVERY][blanc] TWRP 3.2.1-0 touch recovery [2018-02-19]

This is for the Mate 10 Pro (BLA). Touch does not work quite right on the non-Pro Mate 10. It may work on other models, but I have not tested it and most likely the device name will be wrong.
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
CHANGELOG for 3.2.1-0:
-minui fixes (cryptomilk)
-Better android-8.0 compatibility in ROM trees (Dees_Troy)
-Fix missing library in android-8.0 (nkk71)
-Fix inconsistent SDCard naming (DevUt)
-Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
-Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
CHANGELOG for 3.1.1-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
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.

NOTE: fastboot flash to recovery_ramdisk and not to recovery as this device does not have a regular recovery partition.
Device Page, Download Links, Mirrors:
https://twrp.me/huawei/huaweimate10pro.html
Download:
https://dl.twrp.me/blanc

Omg thank you so much for this its feels like a hope of life for a cancer patient ?

where is the download?

@Kane1706 https://twrp.me/huawei/huaweimate10pro.html and the direct link https://eu.dl.twrp.me/blanc/twrp-3.2.1-0-blanc.img.html

Booted into recovery but touch is not working
Mate 10 alp-l29.

Has anyone tested this on the Mate 10 (non-pro) yet?

aDarkBox said:
Has anyone tested this on the Mate 10 (non-pro) yet?
Click to expand...
Click to collapse
Tested on ALP-l09 Huawei mate 10 but does not work although installed and everything but pressing swipe does not work the touch
Enviado desde mi ALP-L09 mediante Tapatalk
---------- Post added at 10:31 AM ---------- Previous post was at 10:31 AM ----------
Dees_Troy said:
This is for the Mate 10 Pro. It may work on other models, but I have not tested it and most likely the device name will be wrong.
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
CHANGELOG for 3.2.1-0:
-minui fixes (cryptomilk)
-Better android-8.0 compatibility in ROM trees (Dees_Troy)
-Fix missing library in android-8.0 (nkk71)
-Fix inconsistent SDCard naming (DevUt)
-Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
-Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
CHANGELOG for 3.1.1-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
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.
Click to expand...
Click to collapse
Tested on ALP-l09 Huawei mate 10 but does not work although installed and everything but pressing swipe does not work the touch
Enviado desde mi ALP-L09 mediante Tapatalk

This is for BLA-L09 / BLA-L29
Not for ALP

Backup ans Restore Working?

touch is working fine for bla-l29 but storage is not the internal storage that i placed my files on its full of garbled folders

BLA-L29 Working?

Look at the post above yours, you may get the answer.

ngoralph said:
touch is working fine for bla-l29 but storage is not the internal storage that i placed my files on its full of garbled folders
Click to expand...
Click to collapse
This is because the internal storage is encrypted, and for now, this version of TWRP doesn't support decryption.
I guess that only solution for now would be to format (not Wipe) internal storage. Maybe dees_troy will soon find a solution, and decrypting will be fully supported.

Pretoriano80 said:
This is because the internal storage is encrypted, and for now, this version of TWRP doesn't support decryption.
I guess that only solution for now would be to format (not Wipe) internal storage. Maybe dees_troy will soon find a solution, and decrypting will be fully supported.
Click to expand...
Click to collapse
at least that's a partial fix, thank you

ngoralph said:
at least that's a partial fix, thank you
Click to expand...
Click to collapse
I didn't tested personally, so i can't guarantee if it works or if the /data is re-encrypted upon reboot.
Let us know if you succeed!

ngoralph said:
at least that's a partial fix, thank you
Click to expand...
Click to collapse
Pretoriano80 said:
I didn't tested personally, so i can't guarantee if it works or if the /data is re-encrypted upon reboot.
Let us know if you succeed!
Click to expand...
Click to collapse
You need to remove fileencryptioninline from /vendor/etc/fstab.kirin970, else it will re-encrypt
And formatting wipes /data (Like a factory reset, meaning files will be missing )

ante0 said:
You need to remove fileencryptioninline from /vendor/etc/fstab.kirin970, else it will re-encrypt
And formatting wipes /data (Like a factory reset, meaning files will be missing )
Click to expand...
Click to collapse
Thanks, i knew there's a way to remove encryption from fstab, but i wasn't sure how it works on Mate 10. [emoji6]
Obviously, the best way would be to have encryption support in TWRP, but at least we have a workaround.
Btw, this encryption issue also affects backup operations, i guess!?

Pretoriano80 said:
Thanks, i knew there's a way to remove encryption from fstab, but i wasn't sure how it works on Mate 10. [emoji6]
Obviously, the best way would be to have encryption support in TWRP, but at least we have a workaround.
Btw, this encryption issue also affects backup operations, i guess!?
Click to expand...
Click to collapse
For /data yes, all other partitions will backup fine.

ante0 said:
For /data yes, all other partitions will backup fine.
Click to expand...
Click to collapse
Yes, i mean for /data! [emoji6]The best part is that now, with TWRP available, we have more options to recover from possible soft-bricks, bootloops, etc.