Database Info

[RECOVERY][TOUCH] TeamWin Recovery Project (TWRP) 2.3.2.1 [UPDATE!]

{
"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"
}
Are you tired of scrolling through huge lists of files in ClockworkMod with the volume rocker?
Don't you wish there was a recovery with a graphical interface and controlled using the touchscreen?
Team Win Recovery is just that!
Built by TeamWin from the ground up based on AOSP recovery, it has a themeable GUI with touch interface, file manager, keyboard, terminal emulator and much much more...
NEW VERSION 2.3.2.1!
Note: A few devices experience random reboots/shutdowns in recovery with the latest version. If this is the case for you, use version 2.2.1 which is completely stable.
Features
Graphical touchscreen interface with buttons and drag-to-scroll!
Compressed backups that can save you up to 50% disk space
Ability to choose which partitions to back up and which to restore
Custom names for backups, rename and delete backups inside recovery
Integrated Terminal Emulator
Install queues allow you to install multiple zips in one go (e.g. CM9 zip together with gapps zip)
Easy one-button cache & dalvik cache clearing after an installation
Recovery settings are saved to the sdcard and persist through reboots
File Manager that allows you to move, copy, delete and rename files and change their permissions
Battery percentage indicator, charging indicator and clock (set your timezone in settings!)
Reboot into download mode (bootloader)
ADB support
Sideloading for automated ROM install: http://teamw.in/ADBSideload
Detailed logfile
Themeable
Download
2.3.2.1 as installable zip
http://www.mediafire.com/?6i91q2lvez9bj9p
Click to expand...
Click to collapse
Install by copying the zip file to your sdcard, booting into recovery (VolumeUp+Power) and then using "install zip from sdcard" ("apply update form sdcard" on stock recovery) to install it.
2.3.2.1 as flashable image file
http://www.mediafire.com/?ji7z7yznh25zjjp
Click to expand...
Click to collapse
Flash using broodplank's Quickflasher. Connect phone via USB, start sgsflasher_x86.exe, activate "Flash a new Recovery", select the twrp2.2.1-recovery.img and press "Start Now".
Please pay particular attention to this:
Some zips may no longer work in TWRP 2.3 if the developer is using an out-of-date update-binary. If this is a problem for you, please use TWRP 2.2.1 (download link in post below)! Zips can be fixed by replacing their old update-binary with this one.
Click to expand...
Click to collapse
FAQ
I installed this but my phone keeps booting into recovery over and over again.
You need to re-flash your bootloader as described here.
Click to expand...
Click to collapse
Can I use TWRP to restore my CWM backups?
No. The only way is to convert your uploads like this: flash CWM, restore a backup, flash TWRP, create new backup, repeat.
Click to expand...
Click to collapse
Where is my external SD card?
The external SD is under /emmc (as is standard for all CyanogenMod-based ROMs). The internal SD is under /sdcard.
Click to expand...
Click to collapse
What is the size vs speed tradeoff for compressed backups?
For my test, compression shrunk the total backup size by 43% and took 1.4 times longer.
Click to expand...
Click to collapse
Can I use this to flash CyanogenMod9?
Yes!
Click to expand...
Click to collapse
Can I use this to flash XYZ ROM?
Yes!
Click to expand...
Click to collapse
The clock shows the wrong time!
You need to set your timezone under Settings -> Time Zone. The setting is saved in a config file on your sd card so you only have to do this once.
Click to expand...
Click to collapse
My .zip file won't install!
Turn off signature verification!
Click to expand...
Click to collapse
Can I mount my SD cards on my PC in recovery?
Yes, but only one at a time. Go into the Mount menu and select which card to mount with the "Use external SD" or "Use internal storage" radio buttons. Connect your USB cable and press "Mount USB storage".
Click to expand...
Click to collapse
How can I restore single apps (and/or their data) from a TWRP backup?
Use TitaniumBackup, it supports TWRP! In Titanium Backup, open up the menu and select "Extract from Nandroid backup...". It will list all your TWRP and CWM backups and allow you to restore as many apps and their data as you want.
Even though all TWRP backup files carry the extension .win, they are either tar archives or filesystem images. System, data, cache and .android_secure are backed up as tar archives or gnu-zipped tar archives if compression is enabled. You can rename those .win files to .tar (.tar.gz if compressed) and extract them like a regular archive. Boot and recovery partitions are backed up as .img files using dd.
Click to expand...
Click to collapse
I have tried to test all recovery features and they all seem to work. I successfully flashed several different ROMs and performed backups and restores. However, there could still be bugs lurking somewhere - if you find one please report it!
Screenshots
Credits
TeamWin - Everything here is their work, I only provide a precompiled binary for our device. Particular thanks to Dees_Troy from TeamWin for his help.
arco - For the config files for our device.
Disclaimer
Do not install this if you don't know what you are doing. Incorrect flashing of a recovery can lead to a hard brick! Bugs in the recovery could result in data loss so always have a backup! I am in no way responsible for anything you do to your phone and offer no guarantees.
For Developers
TWRP has an optional companion app called GooManager. It offers a frontend for the goo.im archive which hosts ROMs and the gapps. Unlike CWM and ROM Manager, it is completely free, developers can upload their ROMs to goo.im and users can easily flash them with GooManager. It would be awesome if developers started uploading their ROMs there!
To take screenshots inside the running recovery, use adb to dump the framebuffer and then use ffmpeg to convert the raw image to a jpeg like this:
adb pull /dev/graphics/fb0
ffmpeg -vframes 1 -vcodec rawvideo -f rawvideo -pix_fmt rgba -s 480x800 -i fb0 -f image2 -vcodec mjpeg fb%d.jpg
Click to expand...
Click to collapse
Sources:
- TWRP2 github
- arco github with BoardConfig.mk etc. for I9001/ariesve
- Configuration parameters for TWRP in BoardConfig.mk:
Code:
DEVICE_RESOLUTION := 480x800
TW_INTERNAL_STORAGE_PATH := "/sdcard"
TW_INTERNAL_STORAGE_MOUNT_POINT := "sdcard"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"
TW_DEFAULT_EXTERNAL_STORAGE := true
TW_FLASH_FROM_STORAGE := true
This is a straight, unmodified compile of TWRP2 sources. TWRP2 is made available under the Apache License 2.0.

Over 27000 downloads as of November 17th! Rock on!
Changelog:
2.3.2.1
- Small bugfixes
2.3.1.1
- Fixed keyboard not working for backup rename bug
2.3.0.3
- Faster boot
- Much faster permission repair
- Charging indicator (only updates once a minute)
- Major code rewrite to C++ and Jelly Bean base
- ADB Sideload functionality - for automated ROM installs, see http://teamw.in/ADBSideload
- USB storage mounting now mounts both internal and external sd cards simultaneously
2.2.1
- Small bugfixes
- Trying to fix the random shutdown bug that happens on some devices
2.2.0
- Integrated Keyboard
- Set custom backup name
- Terminal emulator
- Rename files in file manager
- Set file permissions using octal notation in file manager
- Rename and delete backups
- Restore menu has switch for internal/external SD
- Fixed timezone names
- Wipe external SD option
- Wipe battery stats and rotation data options removed (Google says it's unnecessary. You can still do it manually/with apps if you want.)
- Fixed themes not loading bug
2.1.8-fix
- Fixed USB storage mounting
2.1.8
- Initial release for the Galaxy S Plus
Old Downloads:
2.3.1.1 as installable zip
http://www.mediafire.com/?l78dskdap2xghd7
2.3.1.1 as flashable image file
http://www.mediafire.com/?hhqmgmqq3a37q7s
2.3.0.3 as installable zip
http://www.mediafire.com/?ld9iupspojsdmq2
2.3.0.3 as flashable image file
http://www.mediafire.com/?zqwou2f353n945p
2.2.1 as installable zip
http://www.mediafire.com/?0ufe8dcv5kkajay
2.2.1 as flashable image file
http://www.mediafire.com/?aknf6rjpxj16wrv
2.2.0 as installable zip
http://www.mediafire.com/?6nb6clnwn9w1247
2.2.0 as flashable image file
http://www.mediafire.com/?7afs5n39nbkop22
2.1.8 as installable zip
http://www.mediafire.com/?9bh66rw6uqbt9tm
2.1.8 as flashable image file
http://www.mediafire.com/?km077vhodky7rsb

Cm9 compatible ?

UpGado said:
Cm9 compatible ?
Click to expand...
Click to collapse
Yes!

no problem in cm9？ example.. wifi .BT....because arco recovery fixed some problem in cm9
Sent from my GT-I9001 using XDA

Ezekiel1998 said:
no problem in cm9？ example.. wifi .BT....because arco recovery fixed some problem in cm9
Click to expand...
Click to collapse
This is a Recovery, not a ROM!
A recovery is a small bootable operating system on a seperate partition on your device. Changing your recovery does not in any way affect your running system. And when booted in the recovery you don't have access to WiFi or Bluetooth anyway.
The reason FeaMod does not work with CM9 is because it was compiled with a wrong list of partition sizes. I compiled this using arco's CM9 repository, so it has exactly the same settings, kernel config etc. as the CM9-compatible CWM that arco compiled.

looks awssum shall try flashing an xperimental.zip
Sent from my GT-I9001 using Tapatalk 2

Is this somewhat related to cmw touch recovery ?

Awsome work!!!
Sent from my GT-I9001 using XDA

In restore it is showing nothing....can anybody else confirm it?
Sent from my GT-I9001 using Tapatalk 2

You must make a backup with teamwin recovery. Maybe you can copy your CWM Backup into the Teamwin recovery folder for restore your backup.
Sorry for my english.
Gesendet von meinem GT-I9001 mit Tapatalk

Awesome thanks for your work
Sent from my GT-I9001 using Tapatalk

wow...nice recovery... thanks for your work!!

This is RECOVERY it has nothing to do with any of the ROMS !!! RESTORING BACKUP from other RECOVERIES is not recommended, it will end up bricking your phone! NEVER RESTORE BACKUP WITH DIFFERENT VERSIONS OF RECOVERY, EVEN IF IT IS MADE FROM SAME SOURCE.
RECOVERY cannot be "compatible" or "incompatible" with ANY of ROM distro's.
Restoring someone's nandbackup (CM9 with arco recovery, for example) on own phone is other story.

BzArEx said:
Is this somewhat related to cmw touch recovery ?
Click to expand...
Click to collapse
No, it was developed from scratch by TeamWin. It is also open source and completely free unlike CWM touch which you have to buy.
You can read more at the official project website: http://teamw.in/project/twrp2

F**k the system . AMAZING WORK!!!!!!

Yay!
Awesome work! I was waiting for a touch recovery!
btw, can we flash CWM over this afterwards, just in case i want to restore a CWM backup later on?

Awesome work bro....
Sent from my GT-I9001 using xda premium

sidsweb said:
btw, can we flash CWM over this afterwards, just in case i want to restore a CWM backup later on?
Click to expand...
Click to collapse
Yes, you can change recoveries without a problem.
For arco's CWM flash this zip file and then reboot the recovery. Later in CWM you can just flash the TWRP zip, reboot recovery and you're in TeamWin Recovery again.
This is also how I suggest people migrate their backups (if really necessary): Install and reboot into CWM, restore a CWM backup, install and reboot into TWRP, perform a backup, repeat.

Works great, just installed Arcos build 4 with your Recovery.
Awesome!

[AOSP] 4.1.1 JellyBean for Herotab C8

DISCLAIMER I (or any contributor) cannot be held responible in any way for any sort of damage caused for using this ROM or its derivatives.
This is the AOSP-based Android 4.1.1 Jellybean ROM using custom kernel 3.0 for Herotab C8/Dropad A8/Haipad M7/iBall Slide and compatible tablets.
The Herotab C8 and its siblings are one hackable device; It supports Android 2.2, 2.3, 3.0, 3.2, 4.0, and 4.1. It runs on a single-core Samsung S5PV210 1Ghz Processor and 512mb RAM. Pretty low spec, however with the right tinkering it can be one powerful device.
What works:
Display
Hardware acceleration
Touchscreen (thanks violet's ft506 driver and przemo27 for figuring the alternate data format)
Audio\Microphone (thanks to Asure's CM7 build for audio HAL; and mg3100's details on kernel)
Wi-Fi (thanks to violet's ar6000 driver and jolocotroco for locating source for a wpa_supplicant8 dependency)
Bluetooth
Accelerometer (thanks to Asure's port of mango210 kernel)
Battery Indicator
USB Host
USB OTG
Camera
Market, GoogleApps
Root
What does not work:
HDMI
3G dongle
(NOTE This list is not exhaustive; this build is still a Beta and not intended to be a daily driver)
Steps for flashing (using script; this will make 512MB system, 256MB cache and 1GB data partition and erase your existing settings and apps):
Extract the archive. You will get two files, one will be a GZipped tar (.tgz) and other the kernel (zImage). Copy these to the root of an external SD.
Download the attachment posted here and extract them to the root of the external SD. You should now see 6 files in the root of the external SD. (utscript, utscript_sd, utscript.sh, zImage.debug, zImage, rootfs.tgz).
Insert the SD card and boot your tablet using Menu+Power. This will flash your tablet.
Steps for flashing (using custom recovery):
Extract the archive. You will get two files, one will be a GZipped tar (.tgz) and other the kernel (zImage). Copy these into a folder (path muwst have no spaces) in your external SD card.
Boot into custom recovery.
Go to "Advanced", then "Partition SD card". Select partition sizes (make sure system partition > 320MB) and wait for it to format the partitions. Existing settings and apps will be lost.
[You can skip this step if your tab's system partition is > 320 MB]
Now return to the main menu, and select "Flash ROM". Give it the path where you stored the ROM in step 1. Wait for it to flash the ROM.
Return to main menu and select "Shutdown".
Turn on your tablet normally, and enjoy!
Links:
http://www.embedupload.com/?d=85OERSGVNV (Embedupload)
NOTE: I didn't make this ROM. The guys over at slatedroid did it, so credits all go to them. But you can thank me for sharing

Custom recovery for herotab c8
DISCLAIMER. Use this at your own risk. I will not be responsible for any damage\brick caused by using this recovery.
Currently this is a Beta and all functionality has not been thoroughly tested.
This is a custom recovery modeled on CWM recovery (built on the custom kernel based on Urbetter's source) for Herotab C8/Dropad A8/Haipad M7/iBall Slide i7011/Coby 7024 and equivalent tablets. It should also work on Coby 8024/1024 tablets.
The recovery is built to be compatible (as much as possible) with existing firmwares (stock as well as custom) and patches (again stock as well as those found in custom ROMs). The reason you might want to use this recovery to flash is that:
Its safer (bootloader, etc. are not touched so greatly reduced probability of bricking)
It does not erase your data partition (so Apps and Settings are carried over)
It maintains your existing partition layout (you can change if wanted)
In order to try this recovery,
Download BootExtRecovery.zip attached to this post.
Download the recovery zip from the GitHub link below
Extract both zip files to the root of an external SD card.
Boot your tablet using Menu+Power
This will boot the recovery externally (i.e. unless you actually do something using the recovery, your tablet will be completely unmodified). After the recovery boots and menus work, you may flash the recovery into your tablet (using "Partitions and Storage" menu). Flashed this way, the recovery can be booted into whenever both your SD cards don't have a "utscript" file (otherwise the script is executed instead of starting recovery).
Download: https://github.com/namko/midRecovery/downloads
Source: https://github.com/namko/midRecovery
Key assignments:
Herotab C8/Dropad A8/Haipad M7/iBall Slide -- HOME to select, MENU/BACK to scroll
Coby 7024 -- HOME to select, POWER to scroll
Function list:
Flash ROM - Flashes the ROM on SD card (external or internal) located in a specific folder.
This does not erase 'data' partition. If you downgrade Android, make sure to erase the 'data' partition (or at least erase dalvik-cache from advanced menu) for maximum compatibility.
This does not repartition the internal SD, so if you want a different layout, make sure to change before flashing.
This flashes only the kernel (no other partition e.g. logo, recovery, boot arguments, boot loader)
Apply patch/update - Prompts you to select a patch/update to apply.
Wipe data/factory reset - Erases the 'data' partition. This is equivalent to doing a factory reset.
Wipe cache - Erases the 'cache' partition.
Backup/Restore - Create a new backup (system = firmware, data = your settings/apps) or restore a previously created backup. Essentially this is a NANDROID backup.
Partitions/Storage - To backup or flash individual partitions (e.g. logo, kernel, recovery, boot arguments, bootloader, etc.)
Advanced - To repartition the internal SD card, erase Dalvik-cache, view log, etc.
You can flash ROM (or apply updates) from .ZIP files as well; but it doesn't support the "standard" format because they sometimes contain executables that must be executed to properly apply the patch.

Fixes and patches
Kernel fix (just update it via recovery -> apply patch/update -> update kernel):
http://www.4shared.com/zip/M_ZcGiSF/zImage.html
Wifi Patch:
http://www.4shared.com/zip/3T9hUxnt/wifipatch.html
Here's a patch implementing changes suggested by jolocotroco. To apply this patch:
Extract the zip into your external SD card (anywhere)
Boot into recovery
Select "Apply patch/update"
Select the extracted file ("wifi.patch.tgz")
Reboot after applying patch
It is also possible to apply the patch using adb. Remember to stop WiFi first. This will apply the patch and reboot your device.
adb push wifi.patch.tgz /mnt/sdcard
adb shell
su
mount -o rw,remount /
mount -o rw,remount /system
stop wpa_supplicant
stop hostapd
tar xvf /mnt/sdcard/wifi.patch.tgz -C /
reboot
Click to expand...
Click to collapse

bump

don't work
no one of this patch is recognized by the recovery...
also the kernel update is not a tgz file...
maybe i did a mistake?

j.valeron said:
no one of this patch is recognized by the recovery...
also the kernel update is not a tgz file...
maybe i did a mistake?
Click to expand...
Click to collapse
It should work, what steps did you took to install the kernel?

Custom Recovery for C8/A8/M7
I nearly forgot this. Sorry.
DISCLAIMER. Use this at your own risk. I will not be responsible for any damage\brick caused by using this recovery.
Currently this is a Beta and all functionality has not been thoroughly tested.
This is a custom recovery modeled on CWM recovery (built on the custom kernel based on Urbetter's source) for Herotab C8/Dropad A8/Haipad M7/iBall Slide i7011/Coby 7024 and equivalent tablets. It should also work on Coby 8024/1024 tablets.
The recovery is built to be compatible (as much as possible) with existing firmwares (stock as well as custom) and patches (again stock as well as those found in custom ROMs). The reason you might want to use this recovery to flash is that:
Its safer (bootloader, etc. are not touched so greatly reduced probability of bricking)
It does not erase your data partition (so Apps and Settings are carried over)
It maintains your existing partition layout (you can change if wanted)
In order to try this recovery,
Download BootExtRecovery.zip attached to this post.
Download the recovery zip from the GitHub link below
Extract both zip files to the root of an external SD card.
Boot your tablet using Menu+Power
This will boot the recovery externally (i.e. unless you actually do something using the recovery, your tablet will be completely unmodified). After the recovery boots and menus work, you may flash the recovery into your tablet (using "Partitions and Storage" menu). Flashed this way, the recovery can be booted into whenever both your SD cards don't have a "utscript" file (otherwise the script is executed instead of starting recovery).
Click to expand...
Click to collapse
Github:
https://github.com/namko/midRecovery/downloads
BootExtRecovery:
http://www.4shared.com/zip/HxPitG3B/BootExtRecovery.html

mid recovery is not working on 8024
the recovery is not working on 8024, i have just a black screen...
please help
Sorry it is working...

Now we have Jelly Bean 4.2 form SlateDroid
Please refer for the following hyperlink
http://www.slatedroid.com/topic/42771-romcm101android-421-build-1/
[WORKING]
- Audio
- Video
- Wifi
- Touchscreen
- Most regular things
[NOT WORKING]
- Bluetooth
- 3G

awesome will try it on my dropad A8 its a shame hdmi is not working

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRMMG1tLUxRMWM&export=download
aromafm_beni.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusc204SHRZdTBucHc&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Fit, Tool/Utility for the Samsung Galaxy Fit GT 5670
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
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

i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!

Rminsh said:
i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!
Click to expand...
Click to collapse
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.

Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail

jemail said:
Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail
Click to expand...
Click to collapse
Yep...you're correct.
It won't boot into system.
I finally figured out that it is a problem in androidarmv6 sources. You can see change #6205 if you want.
It was maybe fixed just 4-5 days ago by androidmeda and I'll be again making the recovery and give you all for testing.
This is not only problem of your device but it is also there in: tass, gio and beni.

Bhargav97 said:
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.
Click to expand...
Click to collapse
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327

Rminsh said:
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327
Click to expand...
Click to collapse
It works perfect just in the sense: It reboots to system successfully. It lacks Aroma file manager also. And, Aroma file manager with that original green colour doesn't come with armv6 sources nor it will come if you download from original thread.
I'll be fixing reboot to system soon.
That recovery doesn't even have Touch, GUI options and all that.

UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.

Bhargav97 said:
UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.
Click to expand...
Click to collapse
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail

jemail said:
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail
Click to expand...
Click to collapse
It reformates the partition to the state in which it was in your backup file. The working of this PhilZ Recovery will be the same way as your CWM 6.0.4.7 works. Nothing different except features.

Tested, worked fine with aroma file manager. Flashed cm 11 has no error.
Keep your work
Here is temporary flashable zip file

As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail

jemail said:
As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail
Click to expand...
Click to collapse
1) I don't have your device but in my Galaxy 5 it works fine. I make backup (have an sd-ext and has some stuff also inside) and then restore it and everything is still fine. Link2sd still detects it as ext4. Even if it's a bug, it is not related to my PhilZ Recovery but to the androidarmv6 sources and I maybe can't do anything for it (don't have time to submit a patch for review...maybe I don't have that expertise too).
2) Which logo you mean? The one with Big Green Android? I would prefer to keep it that way...don't wanna make it lean more towards an unofficial build. However, I won't be able to do it (even if I want to) right now because my PC is busy and I can't compile on it right now.
Once I get my PC free, I'll make TWRP for your device and provide a final (final for some time) update for PhilZ Recovery (less probability though for PhilZ update).

When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?

Harpratap said:
When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?
Click to expand...
Click to collapse
Aroma installer's dev OR miui rom's dev is lazy to update the update-binary. KitKat requires new update-binary because Google changed the way getprop worked uptil Jellybean.
TWRP? I don't think I've made a TWRP for Galaxy Fit yet.
I wanna tell you only one thing: You are using everything from latest KK branch: PhilZ Recovery and TWRP (maybe you're talking about the one of Galaxy Mini), so please take some time to read on: What all Google changed in recovery with KitKat. Your int-ext script is suffering from old update-binary for sure.

MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusVmZUN2UxdHFtaWs/edit?usp=sharing

Awesome!
All gui and touch functions work properly.
Flashed a zip and everything works fine except reboot system and power off.
Both of them simply reboot into recovery.
Will report other bugs if found.
And nice job :good:

A little bug. Fixed it.
https://drive.google.com/file/d/0B5c3gpyMBJusSk41Q002c3lneUk/edit?usp=sharing
Give me feedback. Everything else like: screenshot double-tap shortcut for aroma fm (read first two posts to understand), GUI options, etc are especially needed for testing. Post some screenshots also.

[NANDROID] Stock 5.0.2 (Lolipop) Android Galaxy Tab 10.1 T530NN

I am making available the Nandroid backup of the Samsung Galaxy Tab 4 10.1 T530NN. I searched the net and did not find this available in any format. I have tested this and it will work if installed properly. This Backup will probably work in other Recovery packages, but has only been tested in TWRP 3.0.0-0. You're welcome to re-install any Recovery you wish afterward.
Instructions:
1) Install TWRP 3.0.0-0 (Use the Matisse variant for the T530NN) and boot directly into Recovery.
2) Backup your current configuration. This process WILL wipe everything!
3) Using Android File Transfer or ADB, upload the folder from the expanded Stock_5.0.2_Nandroid_LRX22G.T530NNUEU1BOJ3.zip file to the folder /TWRP/Backup/<your device's serial number>/ of either the Internal Storage, or SD Card, whichever you did your Backup to in step 2..
4) Select Wipe to wipe the Data, Cache and Dalvik partitions.
5) Still in TWRP Recovery, select Restore to restore the Stock_5.0.2_Nandroid_LRX22G.T530NNUEU1BOJ3 package. This will overwrite Everything! You can probably get by with selecting only the System, but I saved everything to be sure to get a full reset to stock.
6) Reboot into Recovery again to allow TWRP to make adjustments to the System to keep it rooted.
7) Reboot into System. This will take you through the initial setup to activate your Gmail account and such.
8) Install SuperSU from the Play Store to complete the Rooting. If you'd rather render the tablet un-rooted, that option is in SuperSU's Settings.
I hope I posted this correctly. If not, I welcome admins to properly chastise me.

[RECOVERY] - TeamWin Recovery Project [REDFIN] [OFFICIAL]

[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
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, 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.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Device Config: https://github.com/bigbiff/android_device_google_redbull
GitHub - bigbiff/android_device_google_redfin
Contribute to bigbiff/android_device_google_redfin development by creating an account on GitHub.
github.com
If others thing don't work, please report the issue and let me know.
Download here:
Test9: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test9-redfin.img
- fix cpu temperature display
- turn off openaes
- MTP: fix 100% CPU
- fix perms for last_log.gz
- one click flash option to keep twrp when updating boot in recovery - thanks @Nebrassy
You need to install a kernel with built-in touch drivers such as ElementX-P5.
First, install ElementX-P5, the use the install ramdisk recovery option in the Install menu to install the TWRP image.
https://build.twrp.me/test/redfin/twrp-3.5.0-0-test1-redfin.img
Please ignore the -10 in the version string when fastbooted into TWRP. I am hoping to get the a11 TWRP branch working in a10 trees.
Test 2: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test2-redfin.img
Test 3: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test3-redfin.img
Decryption and backup restore working. Tested with April Firmware.
Test 4: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test4-redfin.img
Enable MTP. Fix /sdcard bind mount to /data/media/0
Test 5: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test5-redfin.img
Add partitions: misc, boot and persist. Enable repacking into ramdisk. Tested with ElementX-P5.
Test 6: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test6-redfin.img
Fix repacking twrp into recovery. You need to install a kernel with built-in touch drivers such as ElementX-P5.
First, install ElementX-P5, the use the install ramdisk recovery option in the Install menu to install the TWRP image.
Test 7: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test7-redfin.img
Fix wiping Titan M chip. Fix decryption hanging on lineage-18.1 when booting TWRP.
Test 8: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test8-redfin.img
Fix reboot to recovery from fastbootd.
http://twrp.me

Nice work!
Once the encryption element is fixed I will definitely be rocking this!!

Nice to see this, good job on working TWRP for this Device. Thank you.

Is there only the img build. No zip file? How to stay on twrp without zip?

This boots on a pixel 4a5g, but touch controls and adb do not seem to work. Do you think it would take a lot of code changes to enable it on the 4a 5g? The two phones share kernels for what it's worth.

Its possible to root android 12 with this?

Was able to boot to it on the pixel 5. Look forward to the progress! Thanks!

mistermojorizin said:
This boots on a pixel 4a5g, but touch controls and adb do not seem to work. Do you think it would take a lot of code changes to enable it on the 4a 5g? The two phones share kernels for what it's worth.
Click to expand...
Click to collapse
Can you provide me a copy of dmesg?

gogixx said:
Is there only the img build. No zip file? How to stay on twrp without zip?
Click to expand...
Click to collapse
This is a fastboot image only.

bigbiff said:
Can you provide me a copy of dmesg?
Click to expand...
Click to collapse
To get a dmesg, I need to use ADB (which doesn't work while booted into TWRP). So would this capture the info you'd need - boot into TWRP, reboot by holding power button, get a dmesg when it boots?
EDIT: so I'm trying to get it this way but the dmesg.txt comes out blank for some reason

mistermojorizin said:
To get a dmesg, I need to use ADB (which doesn't work while booted into TWRP). So would this capture the info you'd need - boot into TWRP, reboot by holding power button, get a dmesg when it boots?
EDIT: so I'm trying to get it this way but the dmesg.txt comes out blank for some reason
Click to expand...
Click to collapse
Unfortunately that would be from the android kernel. I didn't realize adb wasn't working for you. Are you using windows?

bigbiff said:
Unfortunately that would be from the android kernel. I didn't realize adb wasn't working for you. Are you using windows?
Click to expand...
Click to collapse
yes, windows 10, latest adb drivers. when it boots to TWRP it doesn't recognize that any adb devices are connected.
when booting to android though, I can access ADB without problems

bigbiff said:
This is a fastboot image only.
Click to expand...
Click to collapse
Thank you.
What's the proper installation process (how-to) to flash TWRP on the P5/redfin ?

unibombz said:
Thank you.
What's the proper installation process (how-to) to flash TWRP on the P5/redfin ?
Click to expand...
Click to collapse
There is no flashing of it. You would just boot in to it via fastboot boot *twrpimgfile.img

VivisClone said:
There is no flashing of it. You would just boot in to it via fastboot boot *twrpimgfile.img
Click to expand...
Click to collapse
Thank you for clarifying that it is not flashed to the recovery partition and only booted to when you need TWRP features via
Code:
fastboot boot twrp-3.5.0-0-test1-redfin.img

I was able to get touch working on the 4a5g using these commands:
fastboot flash boot twrp-3.5.0-0-test1-redfin.img
fastboot boot ProtonKernel-pixel5-v1.1.img
ADB Still didn't work. The log said couldn't mount storage. Under "mount" I could check every box except the last two (storage and external storage or sdcard I think).
the backup menu is very different looking than i'm used to. instead of being able to select which partitions to backup, there's only one option - "super (vendor, system, system ext...etc)" The only partition that's not listed there is the boot partition. Also, storage says 0mb . Not sure if it would have backed up anything.
Is it able to make backups on the Pixel 5? Can I get you any info (using the TWRP terminal or file manager mayber) to help development?

mistermojorizin said:
I was able to get touch working on the 4a5g using these commands:
fastboot flash boot twrp-3.5.0-0-test1-redfin.img
fastboot boot ProtonKernel-pixel5-v1.1.img
ADB Still didn't work. The log said couldn't mount storage. Under "mount" I could check every box except the last two (storage and external storage or sdcard I think).
the backup menu is very different looking than i'm used to. instead of being able to select which partitions to backup, there's only one option - "super (vendor, system, system ext...etc)" The only partition that's not listed there is the boot partition. Also, storage says 0mb . Not sure if it would have backed up anything.
Is it able to make backups on the Pixel 5? Can I get you any info (using the TWRP terminal or file manager mayber) to help development?
Click to expand...
Click to collapse
The super partition and other partitions you can backup as byte images. However most of these can be restored from the stock firmware. I am working on decryption right now. I am not sure what to do about adb unless you can pull logcat and dmesg for clues for the 4a5g.

Thanks for this TWRP image.
Side loading works.
TWRP does not read the internal storage... Any ideas?

vandyman said:
Thanks for this TWRP image.
Side loading works.
TWRP does not read the internal storage... Any ideas?
Click to expand...
Click to collapse
Yeah. Encryption in A11 is Wip like Op specified.

Is there the ability to resize system partition?