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?
Related
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"
Hello Guys .. this is clockworkmod v 6.0.1.0 By Koush
Now It's The Final build
Here is what Koush said on his G+ Account
ClockworkMod Recovery 6 for Galaxy Nexus
... has been released on ROM Manager.
Changes:
New backup format that deduplicates data between backups.
Faster backups.
Fixed restores > 2GB.
Minor UI tweaks (new background, animated Android)
Future:
In the past, I have merged/rebased every CWM with AOSP. With Jellybean, I have decided this is no longer in the best interest of the project. There are only a few areas of AOSP recovery that are of interest (roots.c - file system, minui, and updater). Those will continue to be merged into CWM. Other than that, doing a full rebase with every code drop has been a giant headache, with the code churn from upstream that providing little to no value to CWM.
In any case, this unties my hands to deviate completely from AOSP, with the primary goal to make a much more polished touch UI.
ROM Manager
ROM Manager is a little over 2 years old, and though it has grown in features quite a bit since its first incarnation, parts are starting to show its age. I've been contemplating a significant UI rewrite for some time now, and will pull the trigger on that shortly. I also want to add in some features that I am hoping will be of some interest:
* A paid ROM section for devs to publish their work and support their hobby.
* Upload your current ROM to ROM Manager for anyone to use, from the device.
* Connect ROM Manager to the Recovery Builder for automatic updates of recovery. No device left behind
Speaking of the Recovery Builder; it has been pleasantly successful. To date, around 1700 recoveries have been built. Many for devices ROM Manager currently does not even support.
Anyways, if you have any suggestions for the future of ClockworkMod products, please drop me a line!.
Click to expand...
Click to collapse
Here Koush explains how the new CWM method works that makes the backup files so small in size
New ClockworkMod Backup Format
TL;DR:
Don't delete /sdcard/clockworkmod/blobs
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.
Click to expand...
Click to collapse
{
"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"
}
Download links
CWM v6.0.1.0
http://goo.gl/Ohcrl
Touch CWM v6.0.1.0
http://goo.gl/DKxEX
Use Fastboot Commands to Flash it
Type " Fastboot Flash Recovery recovery-clockwork-touch-6.0.1.0-toro.img
or Fastboot Flash recovery-clockwork-6.0.1.0-toro.img
I take no credits for the Recovery i'm just trying to share it with you guys it's Done by Koushik as i mentioned
The original Post on G+ : http://goo.gl/jGgl5
This is a flashable zip for the 6.0 series Touch recoveries, in case anyone wants it. Boot into recovery, install zip, choose zip, go back, go to advanced, reboot recovery, profit. I hold no responsibility if it blows up your phone, but I've tested each one before uploading. So enjoy and thanks to D3vious for the OP.
This is the Flashable zip for the 6.0.0.1 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.1-Toro.zip
MD5 - 4acbc676039817382cab3e6338c1872f
This is the Flashable zip for the 6.0.0.4 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.4-Toro.zip
MD5 - 4cfe0f710120c820915e37948ecc2cd2
This is the Flashable zip for the 6.0.0.5 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.5-Toro.zip
MD5 - 026a7d86db10da65c358f1a67952bc1e
Thank you for posting this. The previous version didn't work well on my end. One press on the volume keys made the selection jump around and sometimes not even register the selection when selected and produce a black screen.
6.0.0.1 works great. I'll flash the touch when i get home.
I wish there was an app like Flash Image GUI that i used for my Evo 3d for the G-NEX. Unfortunately that's way beyond my abilities to cook up. If someone did it would be a money maker. Unless there's a way to trick Rom Manager into flashing the touch recovery
Sent from my Galaxy Nexus using Tapatalk 2
totally forgot I saw this on droid-life. Thanks for reminding me!
xavier86 said:
Thank you for posting this. The previous version didn't work well on my end. One press on the volume keys made the selection jump around and sometimes not even register the selection when selected and produce a black screen.
6.0.0.1 works great. I'll flash the touch when i get home.
I wish there was an app like Flash Image GUI that i used for my Evo 3d for the G-NEX. Unfortunately that's way beyond my abilities to cook up. If someone did it would be a money maker. Unless there's a way to trick Rom Manager into flashing the touch recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Renaming it should work
Sent from my Galaxy Nexus using xda app-developers app
When in the Touch recovery when I go to reboot my device I get this screen that says:
"ROM may flash stock recovery on boot. Fix? THIS CAN NOT NE UNDONE."
The usual multiple NOs and a "YES - Disable recovery flash"
What does this mean? Do I choose yes? or keep hitting no or Go Back when I reboot?
I flashed using the CWMR Touch app which can flash IMG files
Also my background is grey not black?
Maybe I should give it a try.
destinydmm said:
When in the Touch recovery when I go to reboot my device I get this screen that says:
"ROM may flash stock recovery on boot. Fix? THIS CAN NOT NE UNDONE."
The usual multiple NOs and a "YES - Disable recovery flash"
What does this mean? Do I choose yes? or keep hitting no or Go Back when I reboot?
I flashed using the CWMR Touch app which can flash IMG files
Also my background is grey not black?
Click to expand...
Click to collapse
Background being gray is part of the change log, Koush just decided to change it is all. Its normal.
As for your other issue, I'm not sure. Mine definitely hasn't done that
Sent from my Galaxy Nexus using xda app-developers app
bill12690 said:
Background being gray is part of the change log, Koush just decided to change it is all. Its normal.
As for your other issue, I'm not sure. Mine definitely hasn't done that
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
EDIT: Refresh my memory on how to flash with flashboot commands again?? PLEASE
NEVERMIND READ THE WIKI
Saw it on Koush's G+ page don't delete the new "blobs" folder
Edit nevermind.
Works great but now when I reboot from recovery it throws up another menu and talks about stock recovery. Is this something I can delete from the recovery. I just want it to reboot with no warnings. If this is a new feature then that's fine. I am OK with it I just have never had this option and it reboots whether I click go back or yes
6.0.0.4 is out now
Khayos said:
6.0.0.4 is out now
Click to expand...
Click to collapse
Yep. Saw the announcement for the CWM update and got myself 6.0.0.4.
Where can you grab the 6.0.0.4 img file?
Any chance of a flashable 6.0.0.4? In the process of moving, don't have computer available to issue fast boot commands.
Sent from my Galaxy Nexus using xda premium
thenewguy821 said:
Any chance of a flashable 6.0.0.4? In the process of moving, don't have computer available to issue fast boot commands.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Use ROM manager
I did read somewhere you can put it on your SD card and use terminal emulator but have never done it myself. Sorry.
Is anyone else having problems backing up the blobs folder to your PC? Whether I use the Backup SD Card option in the toolkit or just try to drag and drop in Windows it fails to copy.
otaku91 said:
Is anyone else having problems backing up the blobs folder to your PC? Whether I use the Backup SD Card option in the toolkit or just try to drag and drop in Windows it fails to copy.
Click to expand...
Click to collapse
A moderator on AndroidForums said he was having issues with CWM 6.0.0.1 and restoring a NANDRIOD made with it. Has this issue been resolved with this build?
Team Win Recovery Project 2.x, or twrp2 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.
Phone look:
Tablet look:
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
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
Device Page on our website:
http://www.teamw.in/project/twrp2/203
Downloads:
http://techerrata.com/browse/twrp2/R819
In my OPPO R819 Goomanager says "No recoveries were found for your device"
This is great news. Finally a custom recovery for R819!
Download img file here
http://techerrata.com/browse/twrp2/R819
Flash with MobileUncle MTK tools found from Play Store
https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox
Do this with your OWN responsibility! I am not responsible if you screw around and brick your phone!
1. Put downloaded IMG file in root of SDcard
2. Open Mobileuncle Tools
3. Choose 'Recovery Update'
4. On the top of the list should show the IMG file on you SD card that you downloaded.
5. Tap it and confirm with OK to flash.
Can I flash Stock Recovery Back
I have installed TWRP 2.6.3.0, and I have used it to make Backups of the whole ROM.
However, I tried to install the ColorOS Beta 1.0.0 and found out it would not install, reason unknown.
So I used TWRP to clean the partitions /Data, /System, /Cache etc. and then installed successfully the complete ROM for Oppo R819 - R819AS-11.A.07-OTA-INT-007-all-SVN4875-wipe.zip since this is the only available until now. Perfect installation.
The system says that there is a downloadable OTA Update Stock Oppo OS 4.2.1 (Build R819AS_11_A.09_131010). I downloaded it, clicked the greenish-blue button "Install", but the phone is not able to install it, obviously, because the Stock Recovery is different, and the instructions are for it alone. Is there a way to return back to Stock Recovery, despite it looks so bare and ugly, just to update the system?! Or is there another way to do it? Maybe if I knew where is stored the downloaded OTA update, I could flash it via TWRP...
Hmm, strange, I installed Color OS with TWRP. To change to stock recovery all you need is to flash a stock rom, it overwrites the recovery during the install process.
TWRP 2.6.3.0
Sorry, there is no logic in that. I did install Stock ROM, the complete ROM for Oppo R819 - R819AS-11.A.07-OTA-INT-007-all-SVN4875-wipe.zip since this is the only available until now. Perfect installation. Via TWRP, of course. Nothing can change the recovery, it stays the same, it is on its own partition, most notably, so that nothing could mess with it. Simple principle - if you are in Recovery, you cannot destroy Recovery itself.
Thanks to a person, who has a phone Oppo Find 5, but told me the problem is with the root privileges, I managed to get past the problem. I preserved the same TWRP 2.6.3.0 Recovery, since I have no other, and I can't change it. I opened the SuperSU program, and checked inside it to "Disable", temporarily. I did not use the "Permanent Uninstall Root" option, which also exists in it. I rebooted to Recovery, and in TWRP wiped the Cache & Dalvik partitions. After that I chose "Install" and the ColorOS 1.0.0 ROM installed perfectly well. It is beautifull and shiny! :good:
{
"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"
}
Where can I find the stock recovery to flash it back in case I want to revert? Or can anyone give me instructions on how to backup the stock recovery before flashing TWRP?
mundano said:
Where can I find the stock recovery to flash it back in case I want to revert? Or can anyone give me instructions on how to backup the stock recovery before flashing TWRP?
Click to expand...
Click to collapse
Yeah I'd like to know too. Or perhaps anyone has stock recovery.img for R819 ?
Sent from my R819 using Tapatalk
distan7 said:
Yeah I'd like to know too. Or perhaps anyone has stock recovery.img for R819 ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
I have the Stock Recovery from 131010, the file is recovery.img 5,865,472 bytes but it can only be flashed with SP Flash Tool, which is not a thing to recommend to beginners, the Tool needs to have the "MT6589_Android_scatter_emmc.txt". That is why I am afraid to post it plainly, open to anyone, just because they might start experimenting without knowledge and break their Oppo R819. Trust me, if you have installed TWRP Recovery from above, using the MobileUncle Tool, you are safe and well, it is a much better Recovery than the plain Stock one.
I understand your point, but I'm not comfortable in flashing non reversible stuff in my phone...
So I will stick with the stock recovery until there is a safe way to revert back to stock.
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Distan7 managed to find a way to revert from TWRP back to Stock Recovery :good:
He has explained it here, has done it twice just to be sure it works every time:
http://www.oppoforums.com/posts/125077/
This is his detailed explanation. Nothing irreversible!
[Oppo R819] Flashing Stock Recovery After Using TWRP
More information on a couple of ways how to recover Oppo R819 are written here:
http://www.oppoforums.com/posts/133578
TWRP was updated today to version 2.7.0.0. I flashed it without problems on my R819.
Sent from my Nexus 7 using Tapatalk
TWRP 2.7.1.0 Updated
TWRP 2.7.1.0 is uploaded to the same place http://techerrata.com/browse/twrp2/R819
vickfred said:
TWRP 2.7.1.0 is uploaded to the same
Looks like development is dead
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
distan7 said:
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
There are many tools available u can get any
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
distan7 said:
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
There are many tools available u can get any
---------- Post added at 11:15 PM ---------- Previous post was at 10:47 PM ----------
ccav2000 said:
TWRP was updated today to version 2.7.0.0. I flashed it without problems on my R819.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thats nice
Click to expand...
Click to collapse
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.
{
"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"
}
Introduction
I'm not a developer. After 4 days of messing with files I made this using AIK (Android Image Kitchen). It include files from different TWRPs. The theme is not mine. I provided all credits below.
As you guys know, our 64 bit TWRP from this thread is usable, but has some major bugs. Specially the touchscreen doesn't work & it's too big to flash. Now, here is a fixed twrp, no need to hassle with OTG & adb anymore!
Installation
Command-
fastboot flash recovery <filename>.img
Booting into TWRP-
- Power off
- Volume down + Power
- Keep pressing volume down until Recovery mode option comes
- Press power
Or,
Command-
adb reboot recovery
Install magisk.zip to avoid twrp being replaced by the stock recovery
Decryption
- Format data
- Install Disable_Dm-Verity_ForceEncrypt.zip
My works
I didn't know these steps from the beginning. I had to discover these. After 30-40 attempts & making 7 versions, the final result came out. To make the thread "To the point" here is what I did for the final one-
Touchscreen Fix :
- Extracted the old TWRP and started modifying it.
- Extracted plus-linux kernel, took "kernel image" & "kernel offset" from there. Inside TWRP, replaced kernel image & kernel offset with these new files. Touchscreen got fixed.
Minimal size :
The TWRP file must be 16 MB or less to be flashable for moto e5. This is because the device has very low recovery partition size. Making a 64 bit TWRP v3.7 under 16 MB was almost an impossible task. Here is how I finally did it-
- Removed txt files.
- Replaced /ramdisk/sbin/ folder with the sbin folder of official TWRP for Asus Nexus 7 2012 3G. This greatly reduced the file size & also made the TWRP v3.7. This happened because that TWRP is 32 bit. Means I used sbin from a 32 bit recovery. But our TWRP didn't become 32 bit because "bit" depends on split_image folder (specially kernel image file inside it)- not sbin folder. After this step, the twrp became 15.1 MB !
- Because of the previous step, a bug came where the cursor was always showing on the middle of the screen even though I was not using mouse via OTG. So I replaced cursor.png with a completely transparent image. So now, the cursor is hidden. And also you won't see cursor while using mouse. But no one need that, as touchscreen is fixed.
- Replaced files inside /ramdisk/twres/ with the files I got by extracting flashable zip of SHADOW"S BLACK THEME. We had a useless font that took almost 4 MB in our old TWRP. After doing the step, got the same font in 100 kb. But the overall file size increased because of new images in /ramdisk/twres/images folder. These images makes the recovery look better. After all, the size became 15.4 mb.
The steps look pretty much easier. But I had to suffer 3 days to discover them. I can briefly say that I ported a 32 bit twrp, used sbin from 8 TWRPs, tried to port 64 bit, removed languages and fonts, removed files from sbin folder, repacked & booted image every time after making every single changes, compressed images using online tools and many more !
I shared all these in case anyone finds them useful.
Bugs
- Adb push / pull (Sideload works though)
- Terminal
NB. Use adb version (boot only) to use adb features like push/pull & inbuilt terminal.
- MTP (Read File Transfer part)
File Transfer
MTP works fine. If you aren't able to use mtp & adb (in adb version), the problem is related to drivers. Here is the fix for windows (Sorry for linux / mac)-
1. Download Drivers.zip.
2. While in twrp, connect it with computer.
3. Go to device manager & uninstall devices related to adb - mtp. Adb device can be under "universal serial bus devices".
4. Disconnect the mobile.
5. In Device Manager, click on view & select "show hidden devices".
6. Again, Uninstall all drivers/devices related to adb - mtp.
7. Re-connect the mobile.
If windows doesn't install the drivers / the installed driver doesn't work, uninstall those and install working drivers manually-
How to install the drivers?
Install automatically- Run the exe file
Install manually (Recommended) - Device manager > Right click on the device > Update driver > Browse my computer >Let me pick > Have disk > Browse > Select the appropiate .inf file provided in each folder.
If you can't see mtp device under portable devices, try running the mtp driver exe file & reconnecting. However, adb fix is guaranteed. Good luck for MTP!
Download
adb version (boot only) - Drive / Mega
v2.1- Drive / Mega
v2.1 (stock)- Drive / Mega
v2- Drive / Mega
v1- Drive / Mega
Drivers.zip- Drive / Mega
Disable dm verity force encrypt
Credits & Links
Theme
Old TWRP
Kernel
Porting Guide
Disable dm verity & force encrypt
TeamWin Official
Android Image Kitchen
Changelog
Version 2.1
- Removed "Install twrp app" screen
Version 2
- Fixed empty area in Advanced options
- Fixed stock theme version error
- Fixed override font error
- Fixed all string resource errors
- Removed all other languages rather than English (Other languages have font problems. And I can't add more fonts because of limited partition size)
Any plans for further updates?
If yes may I suggest the following:
1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)
2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.
kenshinta said:
Any plans for further updates?
If yes may I suggest the following:
1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)
2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.
Click to expand...
Click to collapse
Actually I had to reset my whole computer & lost all my works. I made a list of best working gsi builds for both stock & custom rom. The gsis over stock rom didn't have graphics issues. And I also created other recoveries such as orange fox, Pitch black which were large to flash though. But I lost all of these
I will try to remove that prompt.
And will make a stock theme variant as well. Thanks
Stock theme variant added.
can't boot 64bit lineage 16
https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img.xz/download
basiotte said:
can't boot 64bit lineage 16
https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img.xz/download
Click to expand...
Click to collapse
That's gsi rom bro. They are not guaranteed to work