[RECOVERY][N910T] TWRP Materialized - Dark / Light / Play - T-Mobile Galaxy Note 4 Android Development

TWRP Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Features
Recovery gone App: Designed to mimic the look and feel of an Android app.
Customisable UI: 15 different accent colors, center clock option, different navbar button layouts...
Added functionality: ability to flash image files (recovery, radio, boot), ability to change the recovery splash screen, bookmark function for file lists, Aroma File Manager support, theme changer...
Availability and Compatibility
Supported TWRP versions: 2.8.7.X.
Supported screen resolutions: 1440x2560 (Note 4).
Note 4 Canadian
Note 4 Indian N910G
Note 4 Sprint
Note 4 T-Mobile
Note 4 US Cellular
Note 4 Verizon
Note 4 International N910F
The theme stays compatible with new versions of TWRP until TWRP changelog says otherwise.
DOWNLOAD:
Note 4 T-Mobile (trltetmo)
TWRP Themes & Splashes (Note 4)
SCREENSHOTS
Don't get confused as Recovery version in Screenshots is 2.8.0.0. This is because these themes are also available for other version of TWRP here.
SPECIAL THANKS
@z31s1g for all of his Work.
@TWRP for their Recovery.
INFO
Original Thread
Code:
What’s new in 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)

How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
Install the theme:
The theme zips are not flashable. First installation has to be done manually:
Download the theme of your choice and rename it to "ui.zip".
On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Change the theme:
In Materialised settings, select CHANGE THEME.
Select the theme zip you want to use.
Confirm the change.
Remove the theme:
In Materialised settings, select the delete icon on the app bar.
Confirm the removal.
Alternatively, delete the ui.zip from /sdcard/TWRP/theme with a file explorer.
Change the recovery splash screen
In order to change the splash, one must unpack the recovery image, replace the splash and then repack the image.
General prerequisites:
Make sure the splash screen you want to use is in .jpg format and matches your screen resolution (e.g. 1920x1080).
Download a stock TWRP recovery image for your device.
Samsung users have to download .img files or pull them from the .tar files. Repacking .tar files won't work.
Change the splash while in recovery:
Download the AIK-Mobile-Installer.
Flash the AIK zip in recovery.
This will install the required scripts and binaries to \data\local\AIK-mobile.
In Materialised settings, select CHANGE SPLASH.
Select the stock TWRP .img file.
Select the .jpg file you want to use as splash screen.
Set options:
Make Sure
If Automatically install... is unchecked, the repack will only be created and saved to the same folder as the stock TWRP image.
If checked, the repacked recovery will also be installed on your device.
If Include current theme... is checked, the theme in its current state (accent color) will be included in the repack, replacing the stock TWRP ui.
The ui.zip will automatically be deleted from /sdcard/TWRP/theme, as it is no longer required.
Be aware that changing the accent color won't be possible with an integrated theme.
In general, I'd recommend to not include the theme into the repack. By keeping the ui.zip, there's always the stock ui as a fallback option in case there's something wrong with the theme.
Start repacking/flashing with a swipe.
During the process, Repacking in progress... will be shown.
Install image files while in recovery:
The theme currently utilises the Flashify script by @osm0sis to install boot, radio and recovery images.
The script comes with the theme and will automatically be installed to /sdcard/TWRP/flashify if required.
On the Install page, tap on Install Zip.
Select Install Image.
Select the .img file you want to flash.
Select the image type.
This selection determines the target partition. Make sure not to flash a radio.img to the boot partition...
Start flashing with a swipe.
Use the AROMA File Manager:
AROMA File Manager is not part of the theme.
The theme just contains a "shortcut" for directly starting AROMA FM, rather than going through the "install > flash zip" procedure.
Download this Flashable zip.
Flash the zip in recovery.
This will copy the Aroma FM package to \TWRP\aromafm.
In Materialised settings, tick the option to use Aroma FM.
From the main menu, the theme will now start Aroma FM instead of the TWRP file manager.
Resolve common issues
When I reboot to recovery, the theme isn't applied. Any ideas?
This is most likeley due to wrong naming of the theme folder or the ui.zip.
Make sure the folder is named "theme", without capital letters.
Also check if you accidentally renamed the downloaded zip to "ui.zip.zip" (common pitfall when renaming the zip in windows explorer).
When I reboot to recovery, I get a "recovery bootloop". Is my phone broken?
Nope, this is most likeley due to a bad download.
Please download the theme again using another browser or app.

reserved 2

This is excellent, thank you for taking the time to build these and share your work!

This looks great!!! Can't wait to try it out. Thanks for this and the tutorial!

Amazing and finally. Thank you so much for this.

Aroma file manager issue
@uzairabdulmajeed
Everything works fine for me except the aroma file manager, after I set it
up and rebooted into twrp then I click on the file manager all it does is a
quick blink and it ends up on the themed twrp screen.
Perhaps you can give me a hint about how I can fix it?
I am pretty sure I followed your instructions to a "T".
I even flashed the "holofied_aromafm_191" zip file twice
with the same results.
Thanks in advance!

Thanks for this!! Remember peeps, there is a thank you button, don't forget to click mine for reminding yall!! :thumbup:
Sent from my SM-N910T using Xparent Skyblue Tapatalk 2

aroma doesnt work please can you fix it? thanks!!

Misterjunky said:
@uzairabdulmajeed
Everything works fine for me except the aroma file manager, after I set it
up and rebooted into twrp then I click on the file manager all it does is a
quick blink and it ends up on the themed twrp screen.
Perhaps you can give me a hint about how I can fix it?
I am pretty sure I followed your instructions to a "T".
I even flashed the "holofied_aromafm_191" zip file twice
with the same results.
Thanks in advance!
Click to expand...
Click to collapse
noobiedev83 said:
aroma doesnt work please can you fix it? thanks!!
Click to expand...
Click to collapse
Use the AROMA File Manager:
AROMA File Manager is not part of the theme.
The theme just contains a "shortcut" for directly starting AROMA FM, rather than going through the "install > flash zip" procedure.
Download this Flashable zip.
Flash the zip in recovery.
This will copy the Aroma FM package to \TWRP\aromafm.
In Materialised settings, tick the option to use Aroma FM.
From the main menu, the theme will now start Aroma FM instead of the TWRP file manager.

Re: Aroma File manager recovery.log
uzairabdulmajeed said:
Use the AROMA File Manager:
AROMA File Manager is not part of the theme.
The theme just contains a "shortcut" for directly starting AROMA FM, rather than going through the "install > flash zip" procedure.
Download this Flashable zip.
Flash the zip in recovery.
This will copy the Aroma FM package to \TWRP\aromafm.
In Materialised settings, tick the option to use Aroma FM.
From the main menu, the theme will now start Aroma FM instead of the TWRP file manager.
Click to expand...
Click to collapse
Here is the error in the recovery.log which I get after flashing "holofied_aromafm_191.zip" and
rebooting to recovery. This is a cut/paste of the recovery log error:
AROMA Filemanager version 1.91
(c) 2013
by amarullz xda-developers
aroma/s: Open Archive
aroma/s:
Initializing Resource
I:Legacy property environment disabled.
E:Error executing updater binary in zip
'/sdcard/TWRP/aromafm/aromafm.zip'
Error flashing zip
'/sdcard/TWRP/aromafm/aromafm.zip'
Updating partition details..
.
Iata backup size is 5362MB, free: 8299MB.
I:Unable to mount
'/usbstorage'
I:Actual block device: '', current file system:
'vfat'
...done
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page:
'main2'
Iperation_end - status=1
I:Set page: 'reboot'
I:Set page:
'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page:
'advanced'
I:Set page: 'advanced_confirm_action'
I:Set page:
'advanced_action_page'
Iperation_start: 'Copy Log'
I:Copying
file /tmp/recovery.log to /external_sd/recovery.log
======================================
This is why the aroma file manager is not working for me.
Hope you get a chance to look into it and let me know how to fix.
Thanks,
Have a great day!

I have the same issue it won't flash the aromafm.zip!!

So I installed the theme and everything looked great until I tried to flash a zip and the swipe to install bar was half off the screen. Would love to use this as it looks great, any help would be appreciated!
Sent from my SM-N910T using Tapatalk 2

uzairabdulmajeed said:
TWRP Recovery
DISCLAIMER
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Features
Recovery gone App: Designed to mimic the look and feel of an Android app.
Customisable UI: 15 different accent colors, center clock option, different navbar button layouts...
Added functionality: ability to flash image files (recovery, radio, boot), ability to change the recovery splash screen, bookmark function for file lists, Aroma File Manager support, theme changer...
Availability and Compatibility
Supported TWRP versions: 2.8.7.X.
Supported screen resolutions: 1440x2560 (Note 4).
Note 4 Canadian
Note 4 Indian N910G
Note 4 Sprint
Note 4 T-Mobile
Note 4 US Cellular
Note 4 Verizon
Note 4 International N910F
The theme stays compatible with new versions of TWRP until TWRP changelog says otherwise.
DOWNLOAD:
Note 4 T-Mobile (trltetmo)
TWRP Themes & Splashes (Note 4)
SCREENSHOTS
Don't get confused as Recovery version in Screenshots is 2.8.0.0. This is because these themes are also available for other version of TWRP here.
SPECIAL THANKS
@z31s1g for all of his Work.
@TWRP for their Recovery.
INFO
Original Thread
Code:
What’s new in 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)
Click to expand...
Click to collapse
Any fix for the aroma?
Thanks in advance

noobiedev83 said:
Any fix for the aroma?
Thanks in advance
Click to expand...
Click to collapse
no
tell me if it's working on stock TWRP 2.8..7.0 without themes

re: aroma filemanager
uzairabdulmajeed said:
no
tell me if it's working on stock TWRP 2.8..7.0 without themes
Click to expand...
Click to collapse
The aroma file manager does not work with twrp 2.8.0, 2.8.4, 2.8.7.0
It does not work with or without the twrp themes on my Note 4 N910T.
I even tried using Philz recovery and it did not work and it displayed
the exact same error.
I have spent a lot of hours trying to figure it out without any luck at all.
Here is the recovery log which displays the error:
======================================
AROMA Filemanager version 1.91
(c) 2013 by amarullz xda-developers
aroma/s: Open Archive
aroma/s: Initializing Resource
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/TWRP/aromafm/aromafm.zip'
Error flashing zip '/sdcard/TWRP/aromafm/aromafm.zip'
Updating partition details...
Iata backup size is 5420MB, free: 8202MB.
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
...done
=====================================
I re-downloaded the aromafm-2.00b7.zip file and the 1.9.1 version of it
and tested the zip files including testing the aromafm.zip zip file and
all three of the zip files unzip in my phone and in my computer without
any errors at all.
Hope you can fix it soon.
Have a great day!

Sent from my SM-N910T using Tapatalk

Splash screen
I made (modified really) this splash screen. Feel free to use it.

Related

[DEV][02/May/2015]unOFFICIAL TWRP|v2.8.6.1

Introduction:
---------------------
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:
---------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notice:
---------------------
The attached recovery images were compiled from TWRP's open source.
They were only tested on a European version of the HTC-HD2 powered by cLK bootloader.
The performance on devices powered by MAGLDR bootloader should be considered untested.
Disclaimer:
---------------------
As usual, use at your own risk. TeamWin, arif-ali or kokotas is not responsible for anything bad that may occur from using twrp2.
Nobody appointed me to compile TWRP for HD2. I'm not TeamWin's member. It just happened...
If anyone else is willing to do it and probably do it better I will be glad to step aside,​
Key Features:
---------------------
* Ability to save custom recovery settings
* Touchscreen driven with real buttons and drag-to-scroll
* XML-based GUI that allows full customization of the layout – true theming!
* Settings are saved to the sdcard and persist through reboots
* Ability to choose which partitions to back up and which to restore
* Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
* Basic file manager (copy, move, delete, and chmod any file)
* OpenRecoveryScript scripting engine
* On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
* ADB sideload functionality from AOSP
* Pseudo-terminal emulator
* Ability to backup large partitions (size>4GB) by splitting the backup archive.
Mainline TWRP Change-Log:
---------------------
Follow up the changes in mainline project at TeamWin's page : http://www.teamw.in/project/twrp2.
HD2's TWRP Change-Log:
---------------------
Initial TWRP versions
List of changes
TWRP v2.4.0.0.r1 @ 2013.01.17
Compiled version based on mainline code (v2.4.0.0Alpha).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix getting fs-type from a partition created with a label.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.4.4.0 @ 2013.04.03
Compiled version based on mainline code (v2.4.4.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.5.0.0 @ 2013.04.10
Compiled version based on mainline code (v2.5.0.0).
NOTE: Compiled unmodified source code refused to boot! So I had to change a little bit more this time, just to get it to boot up.
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.0.0 @ 2013.07.09
Compiled version based on mainline code (v2.6.0.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.1.0 @ 2013.08.31
Compiled version based on mainline code (v2.6.1.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.6.3.0 @ 2013.09.14
Compiled version based on mainline code (v2.6.3.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
TWRP v2.8.6.0 @ 2015.04.30
Compiled version based on mainline code (v2.8.6.0).
Fix boot partition's filesystem for MAGLDR's backup&restore to work.
Fix the name of the backup sub-folder(htcleo instead of 0s).
Fix some ui bugs in the default theme.
TWRP v2.8.6.1 @ 2015.05.02
It is version 2.8.6 with a quick fix over a bug in the default theme engine that was causing an error during each boot.
Installation:
---------------------
Make sure you have adb and fastboot working. Please don't ask here questions about this - a simple web search will be enough to help you.
Make sure that the size of the 'recovery' partition is enough for the image to fit.
Make sure the name of the recovery *.img file is the one you use in the commands or in flash.cfg
[cLK/MAGLDR]
Flashing the zip file from Recovery
Download zip file to your computer and copy to /sdcard.
Reboot phone into recovery.
Select to install the zip file from your /sdcard.
Reboot Phone into recovery as normal.
[cLK/MAGLDR]
Flashing the *.img file while booted in Android
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
(Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
(Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
Execute the commands:
Code:
adb push recovery-leo.img /sdcard/recovery-leo.img
adb shell erase_image recovery
adb shell flash_image recovery /sdcard/recovery-leo.img
Reboot Phone into recovery as normal.
[cLK]
Flashing the *.img file while in fastboot mode(cLK menu)
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
(Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
(Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
Reboot phone into cLK menu (fastboot mode).
Execute the commands:
Code:
fastboot erase recovery
fastboot flash recovery recovery-leo.img
fastboot oem boot-recovery
[MAGLDR]
Flashing the *.img file while in USB Flasher mode(using DAF.exe)
WARNING!!! This will erase your current Rom on NAND too!
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
Open the folder you have the recovery and place DAF.exe and flash.cfg in that same folder.
Edit flash.cfg according to required recovery partition size:
Make sure the .img file has the name that flash.cfg specifies!!
i.e. If the *.img file is named recovery-leo.img and min-required-size = 6MB then the flash.cfg could be:
Code:
misc ya 1M
[U]recovery rrecov|ro|nospr 6M recovery-leo.img[/U]
boot yboot|ro 5M
system ya 150M
cache ya 2M
userdata ya|asize|hr allsize
Check out the info about flash.cfg.
Connect the device to the computer via usb, enter MAGLDR and select USB Flasher option.
Right click on DAF.exe and select Run as Administrator.
Click [NEXT] when asked and wait to finish.
Download:
---------------------
HD2_TWRP_2.8.6.1.zip
md5: 93972887cfd3e017d16a09a74900496d
Info: You need to have a recovery partition at least 9 MB to fit the img
HD2_SD_TWRP_2.8.6.1.zip
Info: Extract to the root of your SD Card
Old Releases:
---------------------
HD2_TWRP_2.8.6.0.zip
md5: 882aaa25d9ff17613c64efe53c127d3a
HD2_SD_TWRP_2.8.6.0.zip
HD2_TWRP_2.6.3.0.zip
md5: 53c9522dbaa5ab465874258c01758143
HD2_SD_TWRP_2.6.3.0.zip
HD2_TWRP_2.6.1.0.zip
md5: d66519b22d219865d741389013ea034f
HD2_SD_TWRP_2.6.1.0.zip
HD2_TWRP_2.6.0.0.zip
md5: 185e6b34699e4cdb176780695e9e06aa
HD2_SD_TWRP_2.6.0.0.zip
HD2_TWRP_2.5.0.0.zip
md5: 9604cb28b3e91047abdc3a63d5b827df
HD2_SD_TWRP_2.5.0.0.zip
HD2_TWRP_2.4.4.0.zip
md5: b24bdf020b8ea3222c92df0644c88203
HD2_SD_TWRP_2.4.4.0.zip
HD2_TWRP_2.4.0.0_r1.zip
md5: 8bd2b557442c5af73d38f9e7a054b67a
HD2_SD_TWRP_2.4.0.0.r1.zip
HD2_TWRP_2.3.2.3.img
md5: ad8d1909d54c440f9b79eacad31910b9
recovery-twrp-leo-2.0.0RC0.1.img
md5: 6279a726b19a4ff2fccfe592e23b2e48
recovery-twrp-leo-2.0.0RC0.img
md5: e12fc48a863e4a2984d7fcf3b2cad50a
recovery-twrp-leo-1.1.1-3.img
md5: 6198e06b7ca85379e16acde4d9a19752
recovery-twrp-leo-1.1.1-2.img
md5: 52c51eee07c50a928341b22c3e2a60b6
recovery-twrp-leo-1.1.1-1.img
md5: 4801f88e0d2a62b5a1c3d168a4116d0d
recovery-twrp-leo-1.1.1.img
md5: 7fa63b205facf64bd69d805acf34ae8c
recovery-twrp-leo-1.1.0-2.img
md5: 8bd05c6b1e25bd8cf410e308bed23fe5
recovery-twrp-leo-1.1.0.img
md5: 449b06b28f73e996a33e06c047b51b98
Special Thanks to:
---------------------
* Core twrp 2 development team: agrabren, Dees_Troy, ViViDboarder, and AssassinsLament
* Toastcfh – for his underappreciated dedication to the community
* s0up and kevank for their hard work on the web side of things.
* The rest of Team Win: shift, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, and eyeballer
* Amon_RA - for his great Recovery
* Koush - for his dedication to the community and ClockworkMod
* For all the help with devices and testing Akmzero, arif-ali, Evil_DevNull, gus6464, Jesusice, Pyrostic, [R], and Rootzwiki
* As always thank you to the Team's supporters and the Android Community.
[22 Dec 2011][RECOVERY] Team Win Recovery Project (twrp) v2.0.0RC0.1
Original OP
FAQ
FAQ from TWRP team is here
Q: Does Rom Manager work with this
A: No
Q: Will you be providing support for Rom Manager
A: Maybe, when I have time, or if Team View release it before me
Q: Does it work with MAGLDR
A: Yes, use AD recovery
Q: Does this mean we cannot easily install ROMs
A: Yes, but the code for that may be added at later date, this is Work In Porgress
Q: Will reboot to Recovery work as normal
A: Yes
Q: Does Off-mode charging still work
A: Yes, same as CWM on cLK. it will charge when off, but pressing the power button while charging will not turn the phone on
Q: I got "failed with error: -1"
A: make sure the recovery size is 5M, anything below that is not supported, You can check this by running adb cat "/proc/mtd | grep recovery"
Changelog
ChangeLog
---------------------
2011-12-22 - v2.0.0RC0.1
Fix issues with wiping data on MTD devices (thanks Dees_Troy)
2011-12-18 - v2.0.0RC0
Initial release of twrp 2
Full GUI touchscreen with buttons and XML engine
Fixed sdcard free space checking
Fixed bugs with MD5 zip file checking
Now check more places for a serial number
Too many fixes versus twrp 1.1.1 to list
2011-10-11 - v1.1.1-3
Fix sd-ext issues (no longer use auto FS, and use ext3)
2011-10-08 - v1.1.1-2
Fix sd-ext restore issue
Fix issue with SD repartition and the send button again
2011-10-08 - v1.1.1
fixed fix permissions bug
fixed md5 checking for zip install
2011-10-07 - v1.1.0-2
Changed the select key from power to call button
2011-10-07 - v1.1.0-1
Changed buttons so that it works with the HD2
HD2 Initial Release
2011-10-05 - v1.1.0
brand new nandroid process with more error checking and supports ext3/ext4 types of devices
sdcard partitioning is available for devices with a sdcard (courtesy of koush from CWM source)
can choose multiple zips before flashing and they will flash in the order chosen
files & folders are sorted case insensitive
added option to sort zips by file date instead of file name
can apply themes and change time zones without rebooting for instant gratification
saved settings will now persist through version changes
added myn's warm theme with color codes courtesy of myn
added option to wipe system, data, and cache with rm -rf during a nandroid restore to maintain existing file system settings like block size
added options for automatic md5 checking of zips
twrp spam off by default which makes nandroids up to 10x faster
2011-08-05 - v1.0.3
Added timezones that should cover everyone
Added twrp spam feature (twrp settings)
Added fix permissions (advanced menu)
Added wipe cache and dalvik into Flash Zip menu
Added copy recovery.log to /sdcard (advanced menu)
Added output spam/no spam to restores
Added mke2s prebuilt to /sbin
Fixed SD-EXT issues, (no partition SD-EXT features yet)
Fixed EFS partition issues
Changed the way we do backups on mtd devices, which should fix any boot partition issues (we suggest making new backups if you have an mtd device, EVO4G,NS,NS4G,etc)
2011-07-31 - v1.0.2
Fixed SD-EXT issues
Added Format SD-EXT into format menu
Removed GAPPS support, CM7 automatically backsup and restores if you already have GAPPS installed. If you don't, just flash GAPPS zip
Fixed issue where when flashing a rom, rebooting brings you back to recovery. Auto reboot after successful flash should work great now!
Rearranged the format menu
2011-07-30 - v1.0.1
Initial release
Since I had Already started with the ports for the Recovery Themes...
This is the Link to New Thread.
Sory for Any Inconvenience this has caused you Arif...
Please Visit New Thread Here...
If you See any New themes that you would like me to Port please feel free to post on the Thread Linked Above...
tobiascrystal said:
No kidding, you are super fast! In your experience would you say that this has anything over cwm that you have learned getting it to work for us?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
It is customizable and has touchscreen capabilities.
wow very nice new features compared to clockworkmod...
Just installed few minutes ago, as far as I can tell, it seems all is working fine!
I might have a "small" request, is it possible to map the buttons just like in cwm? I didn't like the idea of using the end button that much...
---------- Post added at 01:51 AM ---------- Previous post was at 01:49 AM ----------
Ultimaex said:
It is customizable and has touchscreen capabilities.
Click to expand...
Click to collapse
Not just yet! This is 1.xx version based, the one you're refering with ts capabilities is 2.x based...
Kool... Now users will have a choice for more than one recovery on leo too... Al thanks to you cheers
And button customization would be good... I hate using the end key.. I fearing... My touch screen might get spoilt again ...
Sent from my HTC HD2 using XDA App
Seems to work great. I did a backup and restore and all went well thumbs up
Sent from my HTC Runnymede using XDA App
So right off the bat I'm impressed with the compression....does it allow us to produce our own zips? I'd like to rename my backups based on the rom they backed up instead of just a date/timestamp.
Nice........
Definitely a thing to look in future
Hope all the bugs are resolved soon
EDIT: - Thanked & RATED 5 STAR (All I can do as of now )
i don't understand how can i install this, becouse this is not zip file. Can you help me please
you install through adb. if you dont know what that is, do a search. there are many FAQ's about it. I would recommend doing plenty of research on it before diving right in.
if someone can do some pictures for me that would be great, as I don't have a camera, or a second phone which has a good quality camera
thanks
How's about battery charging, like clk?
huhjun said:
How's about battery charging, like clk?
Click to expand...
Click to collapse
It's the same as CWM
Edit: Added to FAQ
arif-ali said:
if someone can do some pictures for me that would be great, as I don't have a camera, or a second phone which has a good quality camera
thanks
Click to expand...
Click to collapse
Here you go with some phot... Not so high quality though... If you need better.. Tell me I will upload photos taken from my handy cam ... And what vabout changing end call button to call button
http://db.tt/afg0Szat
Sent from my HTC HD2 using XDA App
i got "failed with error: -1"

[Recovery] TWRP 2.8.3.0 (Unofficial)

Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
Glacier Device Config: https://github.com/Evervolv/android_device_htc_glacier
Kernel: https://github.com/Evervolv/android_kernel_htc_msm7x30-3.0
Flashable through Hboot
Glad to see what you still supporting this device
Отправлено с моего GT-i8190 через Tapatalk
Got to give the users some new goodies to play with.
Thanks so much man! My glacier doesn't stay on for long enough for me to flash things, but still I know I would have loved this lol.
N_otori0us_ said:
Thanks so much man! My glacier doesn't stay on for long enough for me to flash things, but still I know I would have loved this lol.
Click to expand...
Click to collapse
Yeah people who want to try and port newer ROMs will need this
Sent from my Nexus 5 using XDA Free mobile app
Is there a way to convert the image to a flashable zip?
Or, how to push/flash the image via adb?
flash using fastboot, look here for examples
http://forum.xda-developers.com/showthread.php?t=1242901
Is there another download link for this?
The one in the op isn't working for me.
Here is a screenshot of what the browser shows. This is on 3 different browsers on my phone, I get the same thing.
TIA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
linsalata28 said:
Is there another download link for this?
The one in the op isn't working for me.
Here is a screenshot of what the browser shows. This is on 3 different browsers on my phone, I get the same thing.
TIA
1 Right click on Download link in Elgin's post
2 Save target as
3 Change your recovery download from .htm to .img
Click to expand...
Click to collapse
Now I have CWM 5.8.1
Problem:
[email protected]:/$ su
[email protected]:/ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
error scanning partitions: No such file or directory
[email protected]:/ # cd /system/bin
cd /system/bin
[email protected]:/system/bin # ls flash_image
ls flash_image
flash_image
[email protected]:/system/bin # ./flash_image recovery /sdcard/recovery.img
./flash_image recovery /sdcard/recovery.img
error scanning partitions: No such file or directory
[email protected]:/system/bin # ls /sdcard/recovery.img
ls /sdcard/recovery.img
/sdcard/recovery.img
http://forum.xda-developers.com/showthread.php?t=1200147
Replace the recovery in this file with the twrp build. Then follow the rest of the instructions. Always do it from a computer.
Sent from my Nexus 5 using XDA Free mobile app
garleest said:
linsalata28 said:
Is there another download link for this?
The one in the op isn't working for me.
Here is a screenshot of what the browser shows. This is on 3 different browsers on my phone, I get the same thing.
TIA
1 Right click on Download link in Elgin's post
2 Save target as
3 Change your recovery download from .htm to .img
Click to expand...
Click to collapse
Thanks. This worked great..I would have never thought to do it that way.
Click to expand...
Click to collapse
Been sometime but i used to do this in the past with no problem... i tryed the steps above & still dont read image to install in fastboot. Says no image found .nbh file needed or something similar has me confused because i did this years ago no issue threw fastboot with CWM n such.
are you in bootloader mode or fastboot mode? there is an option in t hboot to switch back and forth
elginsk8r said:
are you in bootloader mode or fastboot mode? there is an option in t hboot to switch back and forth
Click to expand...
Click to collapse
HI Elgin,
You had mentioned earlier that you might be making a zip file...any updates on that please?
Thanks
elginsk8r said:
are you in bootloader mode or fastboot mode? there is an option in t hboot to switch back and forth
Click to expand...
Click to collapse
ahhh! that's what it was. thanks a lot, problem is now i'm on windows 8.1 i tried all the xda fixes n drivers to make it read would not recognize driver... that being said for anyone not able to install no matter the reason.... DOWNLOAD Flashify https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en from play store...make sure to have ES Explorer already installed. Once Flashify installed give it root rights then choose flash recovery option, Click Es Explorer option inside Flashify APP, find your image on SD, select YUP! to flash. Just be sure you have a LEGIT recovery image your flashing or one you trust like this one found in this thread or you may lose recovery. Worked first try this method
Notice: Improvements to 10 Post Rule
A New Q & A thread , for This Topic has been created in the Q&A, Help & Troubleshooting Sub-Forum.
New Discussion and Q & A Tabs have also been created, located just under threads Title when viewing in a Browser.
Posts from members with less than 10 posts will automatically be posted in the new Q & A thread.
Please check it out, and see if you can help out someone with a question about this Topic.
For more about this new feature see: Improvements to 10 Post Rule
Link updated for twrp 2.8.3.0, device now uses by-name mapping for the fstab. should still be compatible with older roms.
Hi,
I am experiencing error in creating backup, after the process ends it says in red "failed". I copied the recovery log into pastebin: http://pastebin.com/mS6dAG65
had to remove some lines as the log was too large for paste bin, so removed lots of repetitive entries "setting selinux context: ubject_r:unlabeled:s0 I:addFile '/data/misc/wifi/wpa_supplicant' including root: 0"
I'm pasting below the last lines of log. Any ideas what is the reason for fail- and more important- is there a way to check if the backup created is good for use?
* MD5 Created.
I:Estimated total time: 1
Estimated remaining time: 0
Backing up System...
I:Creating backup...
I:Creating tar file '/sdcard/TWRP/BACKUPS/SH0C8RM02807/2015-06-17--10-30-21 ev_glacier-eng 4.4.2 KVT49L eng.elginsk8r.2//system.ext4.win'
I:Using compression...
E:Failed to open '/sdcard/TWRP/BACKUPS/SH0C8RM02807/2015-06-17--10-30-21 ev_glacier-eng 4.4.2 KVT49L eng.elginsk8r.2//system.ext4.win'
E:Error creating tar '/sdcard/TWRP/BACKUPS/SH0C8RM02807/2015-06-17--10-30-21 ev_glacier-eng 4.4.2 KVT49L eng.elginsk8r.2//system.ext4.win' for thread 0
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:InfoManager saving '/sdcard/TWRP/BACKUPS/SH0C8RM02807/2015-06-17--10-30-21 ev_glacier-eng 4.4.2 KVT49L eng.elginsk8r.2/system.info'
I:createTarFork() process ended with ERROR=255
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'backup'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log

[Recovery][a5][CWM Advanced Edition] PhilZ Touch Recovery [v6.48.4] [22/7/2014]

* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
​
Support clockworkmod developement
​
>> Downloads and How to Install in POST 2<<​>> Special Features Guide in POST 3<<​>> Changelogs in POST 4<<​
Main thread here: http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch Features: Read POST 2 for instructions to use special functions like aroma and ors support
Main menu and PhilZ Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
Enjoy, and do not hesitate to post feedbacks and comments
Credits
Koush for having created and maintaining cwm
Cyanogenmod for making all this possible
Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
Patrics83 and HTC One X xda community for their big help in debugging the touch events input code
Chenglu for his great unpack / repack tool
kbc-developers for the base semi-touch code and much more
[email protected] for his great job / support
McKael for his invaluable support in fixing for Nexus 4
sk8erwitskil for his recovery source, a great place to start learning
amarullz for bringing Aroma File Manager
shoe63 for his testing and great help in porting to the N7000
Tectas and zscomp for their great support in porting to i9300, but not forgetting rulala and störte
wanam for compiling kernels for N71xx and i317M to fix boot delay for custom kernels
dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
The_Steph: for his major help in debugging for n7100.
a3955269 for providing an updated port of TWRP to i9100
adishakthi, ttav and kolmanb for the time they took to debug touch UI for tablets (N8xxx/P31xx)
jeboo for all his feedback about fixing bootloops...
utkanos for his great and kind support over IRC
gweedo767 @ #Koush for sharing his touch code source (not used)
myfluxi for his xxRecovery source in fixing dual usb mount
RM57380 for the tip to grab pictures: fb2png
Chainfire for his support (stock recovery flash) and all his work for the Android community
superatmos and Dharam_Maniar for their great guides on unpacking/building custom kernels
XDA:DevDB Information
PhilZ Touch Recovery, Tool/Utility for the HTC Desire 816
Contributors
v_superuser, Grarak
Version Information
Status: Beta
Beta Release Date: 2014-07-22
Created 2014-07-22
Last Updated 2014-07-23
Downloads and Instructions
Downloads​
Get the latest recovery image from here -
Android File Host - http://www.androidfilehost.com/?w=files&flid=16920
Goo.im - https://goo.im/devs/philz_touch/CWM_Advanced_Edition/a5/
How To Install​
Run these commands in fastboot -
Code:
fastboot flash recovery recovery.img
For support, join support channel on IRC, #htca5​
Reserved
PhilZ Touch 6 Guide!​It is based on Koush clockworkmod 6.x to which I added many features and a full reliable touch interface
Version 5 brings mainly a true touch and scroll interface with a much more optimized and portable touch source
How to select your .android_secure path
In Custom Backup and Restore operations, you can select the target/source for android.secure or disable it
In stock backup/restore operations, include those started with ROM Manager, you can also force a target/source for .android_secure
basically, recovery will check first external storage for a .android_secure folder. If it doesn't find it, it will look in internal storage
If you want for example .android_secure to be in internal sd, just delete .android_secure folder from external sd and ensure there is a .android_secure folder in internal sd
for external sd, just ensure there is a .android_secure folder in it. It will be chosen what ever is the internal sd state
Custom Backup and Restore menu
This is one of the most powerful features of this recovery.
It is made completely open source code, built from sratch. Just keep credits headers and give proper credit if you use them
You can select which partitions you want to backup or restore
You can choose your .android_secure source and target or even disable it
You can set it to reboot directly after job is done
backups will go under the folder clockworkmod/custom_backup
TWRP backups go under stock TWRP/BACKUPS/device_id folder and will be automatically recognized by TWRP
Custom Restore Menu allows you to restore from any of the stock clockworkmod/backup folder, the custom_backup or the TWRP backups
If your backup folder was moved to /sdcard/0/clockworkmod after installing Android 4.2, you can go through the Custom Restore process. When it prompts you to browse sdcards, it should show an additional menu to offer you to browse Android 4.2 folder (/sdcard/0). The additional menu is shown only if recovery detects a /sdcard/0/clockworkmod folder on /data/media devices
efs is backed up under clockworkmod/custom_backup/.efs_backup
modem.bin files can be named any_thing.bin and must go under clockworkmod/custom_backup/.modem_bin
if you enable compression and disable md5, your backups will no more be recognized by stock cwm builds. Otherwise, all stock and custom backups are backward compatible with stock cwm (except special partitions like preload, recovery, modem and efs which stock cwm doesn't support)
Open Recovery Script Support (ORS): revised and adapted from original sk8erwitskil source
On start, recovery looks automatically for /cache/recovery/openrecoveryscript installed by goomanager or any tasker. If it finds it, it is run and phone will reboot
You can also add custom ors scripts you edit your self:
When pressing the ors menu, it will look at default locations for your custom scripts:
clockworkmod/ors first in external_sd, then in internal sd. Put your custom scripts there with file extension .ors
That way you can access your jobs (flash, wipe, backup, restore...) instantly
If no scripts are found in default folder, you get option to browse both sdcards for a custom location
To learn how to write ors scripts to automate your backup/restore/wipe/flash tasks, read here, it is very easy: http://wiki.rootzwiki.com/OpenRecoveryScript
Give Goomanager a try
All backup and restore options are supported except special partitions 1, 2 and 3 (could add modem, efs and preload linked to them later)
/preload will be included with /system if you enabled the /preload option in Misc Nandroid Settings
you have an extra here: you can set the target volume for ors backups under Misc Nandroid Settings menu
Aroma File Manager Support *Adapted from amarullz and sk8erwitskil
You get here the possibility to browse your phone with root access in a friendly GUI file browser, while being in recovery
You even now get a terminal emulator to run in recovery
Download Aroma File Manager from its Home Page
Get the 1.80 version and name the file aromafm.zip
Put the aromafm.zip in clockworkmod/.aromafm/aromafm.zip in external or internal sdcards
In recovery, tap the Aroma File Manager menu or double tap any part of the screen outside menus
It will launch the file manager automatically
Double tap gesture linked to Aroma File Manager can be altered in the GUI Settings menu
Touch GUI Preferences:
This is another unique feature of this recovery and is built from scratch
You can toggle through 4 touch modes:
Full Touch: menus are validated by touching them. I added extra checks to make it robust to validation by error while scrolling. After scrolling, your first touch will only highlight touched menu instead of validate it. If a delay of 1 sec passed, it will validate immeadiately on touch
Double Tap: menus are highlighted on first touch. To validate action, you need to double tap the same menu
Semi Touch: the classic semi-touch interface I enhanced. Menus are selected/highlighted on first touch. You can scroll by swiping up/down, but no validation on touch.
Disable Touch: touch code completely disabled. You have all gui options left, but only hardware keys
When Full Touch mode is selected, it will automatically set recommended menu height, touch accuracy and scroll sensitivity. You can alter them later if you want
Scroll sensitivity controls scrolling on swipe up/down. Lower values are the most sensitive. Adjust this based on selected menu height
Touch accuracy: increase it if your touch gestures are not well accounted for
Config files are saved in /data/philz-touch/philz-touch_5.ini file.
You can do a backup of your settings file, it will go under /sdcard/clockworkmod/philz-touch.ini.bak
You can choose to be prompted to restore your settings whenever they are wiped while you have a backup. You can also set recovery to auto-restore them when needed. This check is done when you reboot to main system from within recovery
There are many gesture actions that you can setup at your wish (some default actions are setup by default)
Long press/move is the bad equivalent to a long press gesture action: just that after one sec of touch, slightly move your finger or change the pressure surface without actually lifting it
Your screen should auto-dim automatically after one minute and turn off after 3 mn. You can change those time settings. Just touch the screen to reset brightness and turn it on
All GUI parts can be customized: menu hight, text colors, menu colors, selection colors, background color and icon, menu seprators, battery and clock, header text...
To setup a custom background image: put a png image with your device resolution in a folder clockworkmod/custom_res
You can take screen shots from recovery display by the slide left gesture (change it at your wish). Pics captures will go under clockworkmod/screen_shots folder. External storage will be always used first. If no external storage is found, internal storage is used. You can take up to 999 pics before it resets to 1
Setup Free Browse Mode and Multi-zip Installer:
Free Browse Mode:
You can setup a default folder from where the Install Zip menu will start
From within your set default folder, you can now browse backward up to the root file system to install a zip file
Multi-zip Installer menu:
Lets you select multiple zip files to flash at the same time
The zip files must go into a subfolder under: "clockworkmod/multi_flash"
At least one subfolder with your zip files must be created. You can create as many subfolders as you want
exp: clockworkmod/multi_flash/NEAT_ROM_files
Easy Log View and Pause on Logs:
In Easy Log View mode, your logs will have a smaller size to better fit the screen. This will be completely revised in upcoming v5 though
Pause on Logs: when enabled, after flashing a zip file or doing a nandroid job, you will be prompted for a key to return to menu display. That way, logs are kept in full screen. Obviously, no pause will be performed on boot scripts and multi-zip operations
Full Change History
6.48.4 (06.07.2014)
- merge multi stage install packages support from AOSP
- CWM 6.0.5.0
6.48.1 (30.06.2014)
- add option to directly parse time_daemon data files
- refresh current time in menu header after time daemon fixes
- fix first passkey prompt screen did not show proper background under some circumstances
- libtouch_gui 1.30
6.47.7 (25.06.2014)
- preserve background icon user settings after sideload, install zip and wipe actions
- use real fstype instead of auto in /etc/fstab when converting between ext4 <-> f2fs using extra.fstab
- libtouch_gui 1.29
- LG G2 variants: enable performance mode in recovery (device tree)
- HTC One Mini (m4): enable f2fs and exfat kernel support
- Galaxy S5 LTE (klte): enable backup/restore of /efs, /modemst1 and /modemst2 partitions
6.47.6 (24.06.2014)
- recovery lock: support use of virtual / capacitive keys as pass key
- libtouch_gui 1.28
6.47.4 (23.06.2014)
- fix adb was disabled when no recovery lock passkey was setup
- Galaxy S3 D2 variants: enable f2fs support
6.47.3 (20.06.2014)
- add recovery lock with passkey on start
- better extra partitions support in custom nandroid operations
- fix segfault during shell nandroid backup/restore commands
- enable progress display during "adb shell nandroid backup/restore" commands
- enhance and fix bugs of progress display during install/nandroid... operations
- nandroid restore: fix progress bar animation when md5 verify is enabled
- nandroid md5: fix progress bar was not reset for each file
- nandroid md5: fix .android_secure md5 sum was never generated or checked
this could cause md5 check to fail under some circumstances
- limit logging to console in adb shell nandroid and mount commands
- fix detection of real fstype (pointer to in the scope char array bug)
- merge: "Only chmod backup/blobs directory if it exists"
- merge: "Enable cmdline nandroid backup of vold volumes"
- disable useless sd-ext warnings and errors
- merge loki updates
- f2fs <-> ext4 conversion: support fs_options2 through extra.fstab before dropping to bare minimal options
- clean up code
- libtouch_gui 1.26
6.43.8 (02.06.2014)
- fix recursive path creation bug for /data/media/0
- f2fs: do not try f2fs recovery.fstab mount options on an ext4 partition
- f2fs: do not redefine default recovery ext4 mount options when migrating from an f2fs recovery.fstab
- f2fs: error message when converting unsupported file systems
- fix Galaxy Mega variant background resolution
6.43.5 (01.06.2014)
- default to /data/media/0 unless we define BOARD_HAS_NO_MULTIUSER_SUPPORT
- use lstat to check if file exists
6.43.4 (01.06.2014)
- fix text print colour could persist after md5 check
6.43.3 (31.05.2014)
- fix f2fs conversion of /data on /data/media devices
- allow ext4 <-> f2fs backup data migration in nandroid
- cleanup code
6.43.0 (30.05.2014)
- nandroid backup: fix 'media' exception:
In CWM, a bug present from the begining was preventing any path/file named media from backup on /data/media devices
This fix will only exclude /data/media path and not other media files/folders
6.42.9 (30.05.2014)
- default again to libtar for backup/restore
6.42.7 (30.05.2014)
default to busybox tar:
- use busybox tar by default as it now supports selinux context backup/restore
- unify libtar and busybox tar options (-p for selinux context)
- remove now deprecated external selinux container code
6.42.5 (30.05.2014)
- f2fs: recreate /etc/fstab after ext4/f2fs conversion for proper use of system mount command
- comment useless dead code
6.42.4 (30.05.2014)
- f2fs: fix nandroid restore to f2fs partitions
- f2fs: support format extra storage to f2fs (vold patch needed)
- f2fs: support switching between f2fs/ext4 (needs f2fs in kernel modules), thanks @KumaJaya
- f2fs: reload volume table after f2fs/ext4 conversion (no reboot needed after conversion)
- f2fs: do not format whole /data when not expected on /data/media devices
- f2fs: allow /data f2fs/ext4 conversion for non data_media devices
6.41.8 (26.05.2014)
Preserve recovery settings after a wipe
- on settings change, create a second copy of recovery settings on primary storage (/sdcard)
- on recovery exit, always copy recovery settings to sdcard if no copy is present
- after a wipe, on recovery exit, try to restore settings from the copy on primary storage
- fix save/restore settings menu labels
- libtouch_gui 1.22
6.41.6 (12.05.2014)
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
6.41.5 (11.05.2014)
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
6.40.1 (03.05.2014)
- proper libtar implementation: support backup/restore of selinux context inside archive
- dedupe: support backup/restore of selinux context by @Chenglu
- libtouch_gui 1.20: support custom key files (BOARD_CUSTOM_RECOVERY_KEYMAPPING)
Thanks for great work!
could u make it for HTC E8? i have the partions but dont know how to compile a rec...thanks
Great man, was always a fan of cwm but abandon this due to the lacking of touch capabilities..
---------- Post added at 11:51 AM ---------- Previous post was at 11:50 AM ----------
One question, does this recovery support off-line charging?
Can you elaborate how to install
Kindly let me know what is fastboot.
How to open fastboot?
Sorry, I never use HTC before.
Can u make a flashable zip plzz?
Sent from my HTC D816w using XDA Premium 4 mobile app
Not sure if I got it right...I tried to access the /etc directory to replace the platform.xml file, but i only found 4 files inside. I have already mounted /system before launching aroma so...am i missing anything?
Can't use TWRP cuz its not supported on my 816 (touch screen doesn't work). Mine is a single sim 4g malaysian model.
Never mind, got it to work after a few tries... lol, finally i can get camera-fv to work now.
Other than that...looks great. be careful on the touches...the go back key is way too close to the to the rest of the format options
p/s: not very sure what happened...after flashing this in, i got the tampered word in my fastboot screen. Previously with earlier versions of cwm, it only has the unlocked word. not sure what will actually trigger the tampered word.
Battery incorrect
hi ! I flashed this recovery . I find the battery number is incorrect . the number show 100% under normal boot ,but the number become 50% only when entering recovery .
If anyone know what happen ?
It says Android is upgrading and keeps rebooting,please help.

[NO LONGER MAINTAINED][RECOVERY][supersonic]TWRP touch recovery

UPDATE: I am no longer posting on XDA.​
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Installation instructions
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Alternate Installation Method:
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Click to expand...
Click to collapse
Device Changelog
Current version: 3.1.1-0:
Code:
[LIST]Initial official release[/LIST]
Older Device-specific versions:
Code:
[LIST]N/A[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.1.1:
Code:
[LIST]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)[/LIST]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]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 [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
[*]Add Greek translation to some builds.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]support new CM 13.0 pattern encryption (sultanqasim)
[*]fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
[*]libtar updated to latest upstream and fixes (jcadduono)
[*]fixes for loading custom themes (_that)
[*]TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
[*]translation updates - added Italian, Czech and Polish and significant updates to Dutch
[*]progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
[*]fix input box text display (Dees_Troy)
[*]reboot option after zip install complete (bigbiff)
[*]other mostly invisible bug fixes and improvements[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]Completely new theme - Much more modern and much nicer looking (by z31s1g)
[*]True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
[*]Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
[*]Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
[*]Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
[*]Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
[*]SuperSU prompt will no longer display if a Marshmallow ROM is installed
[*]Update exfat, exfat fuse, dosfstools (by mdmower)
[*]Update AOSP base to 6.0
[*]A huge laundry list of other minor fixes and tweaks[/LIST]
[U]Additional Notes[/U]
[LIST]WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
[*]Notes for themers: In addition to the updated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
[*]Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
[*]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![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[U]Additional Notes[/U]
[LIST]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 [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
Download
Latest Official versions
Sources
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
None
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be 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 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!
Click to expand...
Click to collapse
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
Team Win Recovery Project (TWRP), Tool/Utility for the HTC EVO 4G
Contributors
Captain_Throwback, Dees_Troy, bigbiff, _that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.1.1-0
Stable Release Date: 2017-05-18
Created 2015-03-20
Last Updated 2018-03-07
Device-specific Information
Reserved for FAQ (if needed)
Ty captain,
I like the new additions can't wait to check it out.
+1
Sent from my SM-G900P
2.8.6.0 has been uploaded.
2.8.7.0 has been uploaded.
Anybody tried the new TWRP yet?
Captain_Throwback said:
Anybody tried the new TWRP yet?
Click to expand...
Click to collapse
Working on maKing a Wi-Fi only phone for my cousins birthday out of my old evo I tried to find "supersonic" in the twrp app but it didn't come up. Would you be able to fix that or should I just install it manually?
paridoth said:
Working on maKing a Wi-Fi only phone for my cousins birthday out of my old evo I tried to find "supersonic" in the twrp app but it didn't come up. Would you be able to fix that or should I just install it manually?
Click to expand...
Click to collapse
What TWRP app? There's no official TWRP app. The install method is listed on the Download page for the device and in the OP here.
On the download page it links to the twrp manager app. I am installing over clockwork mod so can't install with recovery and I don't have access to a computer.
paridoth said:
On the download page it links to the twrp manager app. I am installing over clockwork mod so can't install with recovery and I don't have access to a computer.
Click to expand...
Click to collapse
Yeah, that's not an official TWRP app. You can disregard that. You can try Flash Image GUI or Flashify to flash recovery to your device, if you have to use an app, but I never recommend using an app if fastboot is available .
Yea I tried flashify but it locked up. Could I put it in a pc36img.zip and flash it from bootloader?
paridoth said:
Yea I tried flashify but it locked up. Could I put it in a pc36img.zip and flash it from bootloader?
Click to expand...
Click to collapse
What about Flash Image GUI? There's a free version available on XDA (last time I checked).
The bootloader method should also work, it just requires having an appropriate android-info.txt.
I'll try flash image gui and report back thanks!
---------- Post added at 10:28 AM ---------- Previous post was at 10:17 AM ----------
Is this the right one? https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui
paridoth said:
I'll try flash image gui and report back thanks!
---------- Post added at 10:28 AM ---------- Previous post was at 10:17 AM ----------
Is this the right one? https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui
Click to expand...
Click to collapse
Did you find more than one?
Just wasn't sure that was the right one. I found it on xda. Flashed twrp 3.0 rebooted to recovery but it took me to the boot loader. Tried again same thing. I'll try flashing an older version
paridoth said:
Just wasn't sure that was the right one. I found it on xda. Flashed twrp 3.0 rebooted to recovery but it took me to the boot loader. Tried again same thing. I'll try flashing an older version
Click to expand...
Click to collapse
You might just have to wait until you get to a PC and do it via fastboot. That way should work without issue.
Unfortunately I'm in hospital so no computer access. I flashed an older version and that worked when I get out I'll try flashing 3.0 with adb thanks!
paridoth said:
Unfortunately I'm in hospital so no computer access. I flashed an older version and that worked when I get out I'll try flashing 3.0 with adb thanks!
Click to expand...
Click to collapse
If you got a previous version installed, you should be able to flash the new version from within TWRP (as indicated in the OP).
Unfortunately it was 2.7 I installed I tried 2.8 but had the same issue
paridoth said:
Unfortunately it was 2.7 I installed I tried 2.8 but had the same issue
Click to expand...
Click to collapse
Is your EVO on the last available software update? I believe it was 5.07.651.6 or something like that?

[RECOVERY] TWRP Materialized - Dark / Light / Play for Note 4 Sprint

TWRP Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Features
Recovery gone App: Designed to mimic the look and feel of an Android app.
Customisable UI: 15 different accent colors, center clock option, different navbar button layouts...
Added functionality: ability to flash image files (recovery, radio, boot), ability to change the recovery splash screen, bookmark function for file lists, Aroma File Manager support, theme changer...
Availability and Compatibility
Supported TWRP versions: 2.8.7.X.
Supported screen resolutions: 1440x2560 (Note 4).
Note 4 Canadian
Note 4 Indian N910G
Note 4 Sprint
Note 4 T-Mobile
Note 4 US Cellular
Note 4 Verizon
Note 4 International N910F
The theme stays compatible with new versions of TWRP until TWRP changelog says otherwise.
DOWNLOAD:
Note 4 Sprint (trltespr)
TWRP Themes & Splashes (Note 4)
SCREENSHOTS
Don't get confused as Recovery version in Screenshots is 2.8.0.0. This is because these themes are also available for other version of TWRP here.
SPECIAL THANKS
@z31s1g for all of his Work.
@TWRP for their Recovery.
INFO
Original Thread
Code:
What’s new in 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)
How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
Install the theme:
The theme zips are not flashable. First installation has to be done manually:
Download the theme of your choice and rename it to "ui.zip".
On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Change the theme:
In Materialised settings, select CHANGE THEME.
Select the theme zip you want to use.
Confirm the change.
Remove the theme:
In Materialised settings, select the delete icon on the app bar.
Confirm the removal.
Alternatively, delete the ui.zip from /sdcard/TWRP/theme with a file explorer.
Change the recovery splash screen
In order to change the splash, one must unpack the recovery image, replace the splash and then repack the image.
General prerequisites:
Make sure the splash screen you want to use is in .jpg format and matches your screen resolution (e.g. 1920x1080).
Download a stock TWRP recovery image for your device.
Samsung users have to download .img files or pull them from the .tar files. Repacking .tar files won't work.
Change the splash while in recovery:
Download the AIK-Mobile-Installer.
Flash the AIK zip in recovery.
This will install the required scripts and binaries to \data\local\AIK-mobile.
In Materialised settings, select CHANGE SPLASH.
Select the stock TWRP .img file.
Select the .jpg file you want to use as splash screen.
Set options:
Make Sure
If Automatically install... is unchecked, the repack will only be created and saved to the same folder as the stock TWRP image.
If checked, the repacked recovery will also be installed on your device.
If Include current theme... is checked, the theme in its current state (accent color) will be included in the repack, replacing the stock TWRP ui.
The ui.zip will automatically be deleted from /sdcard/TWRP/theme, as it is no longer required.
Be aware that changing the accent color won't be possible with an integrated theme.
In general, I'd recommend to not include the theme into the repack. By keeping the ui.zip, there's always the stock ui as a fallback option in case there's something wrong with the theme.
Start repacking/flashing with a swipe.
During the process, Repacking in progress... will be shown.
Install image files while in recovery:
The theme currently utilises the Flashify script by @osm0sis to install boot, radio and recovery images.
The script comes with the theme and will automatically be installed to /sdcard/TWRP/flashify if required.
On the Install page, tap on Install Zip.
Select Install Image.
Select the .img file you want to flash.
Select the image type.
This selection determines the target partition. Make sure not to flash a radio.img to the boot partition...
Start flashing with a swipe.
Use the AROMA File Manager:
AROMA File Manager is not part of the theme.
The theme just contains a "shortcut" for directly starting AROMA FM, rather than going through the "install > flash zip" procedure.
Download this Flashable zip.
Flash the zip in recovery.
This will copy the Aroma FM package to \TWRP\aromafm.
In Materialised settings, tick the option to use Aroma FM.
From the main menu, the theme will now start Aroma FM instead of the TWRP file manager.
Resolve common issues
When I reboot to recovery, the theme isn't applied. Any ideas?
This is most likeley due to wrong naming of the theme folder or the ui.zip.
Make sure the folder is named "theme", without capital letters.
Also check if you accidentally renamed the downloaded zip to "ui.zip.zip" (common pitfall when renaming the zip in windows explorer).
When I reboot to recovery, I get a "recovery bootloop". Is my phone broken?
Nope, this is most likeley due to a bad download.
Please download the theme again using another browser or app.
reserved 2
Nice. Thank you
deleted
This is cool, I used the PLAY theme and loving it, thanks!
Great work!! Was hoping someone would come out with something like this for our recovery. You knocked it out of the park with this one my friend!! Thanks again.
I wanna change the splash screen but I don't understand how to repack
Looks great! Using dark theme and the UI is excellent!
thatdudeaaron said:
I wanna change the splash screen but I don't understand how to repack
Click to expand...
Click to collapse
Change the splash while in recovery:
Download the AIK-Mobile-Installer.
Flash the AIK zip in recovery.
This will install the required scripts and binaries to \data\local\AIK-mobile.
In Materialised settings, select CHANGE SPLASH.
Select the stock TWRP .img file.
Select the .jpg file you want to use as splash screen.
Set options:
Make Sure
If Automatically install... is unchecked, the repack will only be created and saved to the same folder as the stock TWRP image.
If checked, the repacked recovery will also be installed on your device.
If Include current theme... is checked, the theme in its current state (accent color) will be included in the repack, replacing the stock TWRP ui.
The ui.zip will automatically be deleted from /sdcard/TWRP/theme, as it is no longer required.
Be aware that changing the accent color won't be possible with an integrated theme.
In general, I'd recommend to not include the theme into the repack. By keeping the ui.zip, there's always the stock ui as a fallback option in case there's something wrong with the theme.
Start repacking/flashing with a swipe.
During the process, Repacking in progress... will be shown.
Downloaded theme zip created theme folder lower case renamed zip to ui.zip still not themed
Sent from my SM-N910P using XDA Free mobile app
lilmeanz said:
Downloaded theme zip created theme folder lower case renamed zip to ui.zip still not themed
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Did you extract the main zip? It has like 3 or 4 zips in it. Those zip files need to be renamed ui.zip, depending on which one you choose, then put into a folder on Internal sdcard where TWRP folder is. So, Internal sd/TWRP/theme/put "ui.zip" here , then reboot recovery.
Main zip
Finally got everything set up I love this
I went to change my splash screen again and now it's soft bricked. It keeps booting into download mode. Wonder what I did wrong
Thanx for this. Very sick!!
Workin good on NK2.4.4.4
First reboot to recovery after Odin Flash had a hang and then about 5 sec later it showed the old looking twrp. rebooted phone to system.
Made the mistake of adding the theme folder to ExternalSD/TWRP/, added the ui.zip to MainStorage/TWRP/theme
(Backup Folder is still on the ExternalSD/TWRP, which is what you want)
Rebooted to recovery without flashing it again and Materialized Recovery worked this time(no hang either), went to change to dark theme(my ui.zip) and also works flawlessly!
Thanks.
re: download mode issue
thatdudeaaron said:
I went to change my splash screen again and now it's soft bricked. It keeps booting into download mode. Wonder what I did wrong
Click to expand...
Click to collapse
You need to odin flash the latest version of TWRP 2.8.7.0
Have a great day!
Good luck!
It works great for me, weird thing is after applying the themes, my backup times are cut in half. I know it's probably a fluke but i made two different nandroids and both were half as long to backup. Same version as TWRP with both tests so IDK what is going on but it's definitely faster.
Do I need to flash the latest verision of TWRP first or does this contain it?

Categories

Resources