[RECOVERY] [02/02/12] ClockworkMod [5.0.2.0 and 5.8.1.0] ~Touch Version Added~

[RECOVERY] [02/02/12] ClockworkMod [5.0.2.0 and 5.8.1.0] ~Touch Version Added~ - myTouch 4G Android Development

{
"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"
}
All credit for this software goes to the dev (Koushik Dutta and anyone else on his team).
** Nandroid backups made on previous versions of CWM cannot be restored in CWM 5.0.x.x. So if you have backups made in versions 2.5.x.x or 3.0.x.x, you will not be able to restore them once you've upgraded. **
HOMEPAGE
ClockworkMod.com
DOWNLOAD
Standard recovery
Link: recovery-clockwork-5.0.2.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: a5aea82ec2ad7b836c9c179fce0d520d - To verify, use ManD5 or the below ADB commands:
Touch recovery
Link: recovery-clockwork-touch-5.8.1.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: 687998d5093878147256c10ae9e98e5a - To verify, use ManD5 or these ADB commands:
Code:
adb push recovery.img /sdcard/recovery.img
adb shell md5sum /sdcard/recovery.img
INSTALLATION
- Via the ROM Manager app (version 4.4.0.3 or newer required)
- Via terminal emulator:
Code:
Move recovery.img to the root of your sdcard
Start the terminal app
su (press enter)
flash_image recovery /sdcard/recovery.img (press enter)
reboot recovery (press enter)
- Via fastboot (ADB installation and engineering bootloader version 0.85.2007 required):
Code:
Move recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode
Connect your phone via USB to your computer
fastboot devices
fastboot flash recovery recovery.img
CHANGE-LOG
5.0.0.1 through 5.0.1.0
Backups now use tar over yaffs for everything except mtd partitions. Backup speed improved.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type.
New color scheme
Status bar when backing up working again
Backing up of .android_secure working again
5.0.2.0
Bug-fix: root no longer lost on rom restore
5.8.0.9
Touch version - initial release (beta stage)
5.8.1.0
Major bug fixed (recovery.fstab malformed)
I'm not in any way responsible if something happens to your device. I'm simply posting this as a courtesy to the community.

I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.

mackster248 said:
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
Click to expand...
Click to collapse
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?

Ace42 said:
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Click to expand...
Click to collapse
As far as I know, the jump was made straight from 3.0.2.4 to 5.0.0.1. I have yet to see a changelog, but if anyone finds one, I'll add it to the OP. After poking through the menus, nothing obvious stood out, so it seems to be a bug fix and "behind the scenes" release.

-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!

Thanks for the heads up. Just flashed via rom manager without any issues.

I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...

epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not quite sure if that's a bug. Since there's a lot of internal changes, I'm assuming the path it takes from Android to CWM has changed. So maybe that's why we're stuck at the splash screen.
But that's not too big of a problem. So far it's much faster than the previous versions.

WOW! I just did a backup of my current Rom and it literally took like 1 minute! It's WAY faster now.

epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.

<EDIT EDIT>
lol wrong forum.

updated to 5.0.0.1. seems pretty neat.

This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium

coupetastic-droid said:
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!"

I also added the info from his Google+ page to the OP.

Any information on whether other built in tools such as sdparted were updated too? I have been having a lot of trouble with my SD card (I couldn't get it to format through sdparted because of some error I can't remember) and the option to partition your SD card through ClockWorkMod Recovery 3.x didn't allow to set EXT to a size of 0. I was able to partition my card the way I wanted through sdparted after flashing the new 5.0.0.1 recovery, but was curious as to whether there was a change within the recovery img that allowed me to finally partition the way I wanted or if the change was something else that caused my SD card to start functioning correctly.

bstapley said:
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
Click to expand...
Click to collapse
+1 Same here
Sent from my HTC Glacier using XDA Premium App

Ace42 said:
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!"
Click to expand...
Click to collapse
just did a restore and everything went perfectly fine. thanx.

I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Sent from my virtuous doubleshot glacier using XDA App

darksoul0013 said:
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Click to expand...
Click to collapse
Shouldn't be a problem. Nothing was changed that would make affect how a ROM is flashed.

Related

[NST][CWR][RC2] Clockworkmod based Recovery - fixed backup issue

{
"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"
}
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data. Make a backup before you try anything described here!
Making a backup with CWM only includes the following partitions: boot, system, data, cache. It doesn't include the /rom partition which contains data thats unique for every device. Use this backup method to make a full device backup.
Please do not use the restore backup function to restore backups made with versions prior and including RC1. They are faulty and restoring them damages an important bootfile of your nook. It isn't important with which version you restore, if the backup was made with Beta1, Beta2 or RC1 it will fail! Please read http://forum.xda-developers.com/showpost.php?p=19945955&postcount=37
Changelog:
RC2
changed mount options of the boot partition (fixes the bad backup issue)
updated sources to the newest ones from CM
some internal changes for the screen refresh
RC1
reboot recovery in the advanced menu is now working
boot to recovery is now a bit faster
switched to automated build environment
moved some files to the appropriate place
Beta2
Added page refresh after pushing back or select buttons, to get rid off the ghosting. Still not perfect, but good enough for a recovery.
Beta1
First release
Hi,
after some trying and hacking I was able to build a working Clockworkmod based recovery for the Nook Simple Touch.
It is still a beta-version, but everything I tested (backup, restore, mount USB, install zip) works.
If you want to try it, just write one of the imgs from the sd_xx_clockwork-....zip to a SD card with at least the capacity mentioned in the filename. Put the card in your N2E and reboot. Do not write these images directly to the Nook, it will brick your device permanetly!
To replace the standard recovery of the N2E, copy also the install_cwm_recovery_xx.zip to the sdcard, boot into CWM and use the install zip from sdcard option to install it (it just replaces uRecRam and URecImg in the /boot partition, so you can also do it manually, if you want).
There is really no need to install CWM on the device as long as you aren't developing and need it constantly. Please keep in mind that replacing the stock recovery will remove the restore function, that can be triggered by pressing the two lower buttons (or by eight failed boots). Restoring the stock recovery with install_stock_1.1_recovery.zip will bring back this function.
How to boot into recovery:
Power down the N2E
Press the power button for ca. 3 seconds, so that the device boots (you don't have to hold the power button after the 3 seconds)
As soon as the display changes to the "read forever" screen , push and hold the lower left and the lower right button until the screen changes again
Wait until you see the recovery
If you want the standard recovery back, use the install_stock_1.1_recovery.zip (See next post).
Button layout:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Known bugs:
after restoring the boot partition, most of the times the recovery ends in an unresponsive state. The nook has to be rebooted by holding the power button. This is not affecting the restore!
"reboot system now" doesn't work always (sometimes you have to power cycle), experienced it only when booting from SD
Reboot to recovery by using adb reboot recovery doesn't work. (needs a new adbd binary in the uRamdisk)
DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, lost data. Make a backup before you try anything described here!
Credits go to:
koush, author of Clockworkmod recovery http://www.clockworkmod.com/
Cyanogenmod-Team, for their great build environment and the Nook Color recovery
The people who wrote Noogie (SD-Card is based on Noogie) http://nookdevs.com
Tyler Montgomery (IOMonster) http://nookdevs.com , buildenv for bootable OMAP-SD-Cards

Useful update.zip's
rom_backup.zip
Makes a backup of all the files that are on the /rom partition. Saves it to the SD-card /backup/rom_backup.tgz.
This partition contains some important data, that is unique for every device (serial, MAC, ...).
install_stock_1.1_recovery.zip
Installs the recovery from the stock 1.1 update.
MinimalTouch
Automatic Rooting + Gapps by eded333
install_remount_commands.zip
Adds the commands systemrw (remount /system rewritable) and systemro (remount /system readonly).
If you have useful update.zip's that should be included here, please let me know.

Great work
I see you listed "install zip" as one of the features tested, does that mean we can create update.zip's and run them trough cwm?

ros87 said:
I see you listed "install zip" as one of the features tested, does that mean we can create update.zip's and run them trough cwm?
Click to expand...
Click to collapse
Yes, you can create update.zip's and run them trough cwm, install zip works fine. That should make some of the rooting guides and changes of the framework easier.

mali100 said:
Yes, you can create update.zip's and run them trough cwm, install zip works fine. That should make some of the rooting guides and changes of the framework easier.
Click to expand...
Click to collapse
It sure would!
I noticed that regular update zips use "update-script" while the B&N files use "updater-script", do both work?

ros87 said:
I noticed that regular update zips use "update-script" while the B&N files use "updater-script", do both work?
Click to expand...
Click to collapse
I think update-script is the old, no longer supported file-format. As far as I know CWM (since version 3) only supports updater-script with an updater-binary (that interprets the script). I only tested the latter.

make it fully working without ghosting and we have the base for custom roms, this is simply great.

very good news.
I hope, a step closer to CyanogenMod or other custom Rom...

Would it be possible to resize the image to fit in a smaller uSD?

Thanks for taking the time into making this tool available for the NST, this opens the possibilities even more for our ereader

met67 said:
Would it be possible to resize the image to fit in a smaller uSD?
Click to expand...
Click to collapse
Yes that should be possible, I almost fell of my chair when uncompressing the archive
I'm guessing he just smacked the files onto his 2GB card and made an image of it
But yes it's a problem beyond SD cards, I have my Ubuntu VM on a SSD with limited space so 2GB is not a small issue for me
With that said, there's a limit as to how small a fat32 partition can be, but 64MB is doable.

user4242 said:
make it fully working without ghosting and we have the base for custom roms, this is simply great.
Click to expand...
Click to collapse
I don't think a recovery is a good base for a custom rom. If you want to build one, use the update to 1.1 as base, you should be able to install it with this recovery.
met67 said:
Would it be possible to resize the image to fit in a smaller uSD?
Click to expand...
Click to collapse
Yes it is, I made it that big because I wanted some space for the backups. I will add an 128MB version tomorrow, when i upload a new beta with less ghosting.
ros87 said:
I'm guessing he just smacked the files onto his 2GB card and made an image of it
Click to expand...
Click to collapse
I haven't µSD-cards that small

Very cool! Do you expect to submit this upstream and have it supported in ROM Manager?

mali100 said:
I haven't µSD-cards that small
Click to expand...
Click to collapse
Showoff!, 2GB is my biggest one, kinda the crown of my collection

FletchF said:
Do you expect to submit this upstream and have it supported in ROM Manager?
Click to expand...
Click to collapse
Once it's stable and well tested, yes.
By the way, does someone know how the reboot to recovery from a running system works on other devices? Does this work on the Nook Color?
"adb reboot recovery" and "reboot to recovery" from CWM just cause a normal reboot to android.

mali100 said:
Once it's stable and well tested, yes.
By the way, does someone know how the reboot to recovery from a running system works on other devices? Does this work on the Nook Color?
"adb reboot recovery" and "reboot to recovery" from CWM just cause a normal reboot to android.
Click to expand...
Click to collapse
There's some trickery going on in u-boot:
When BootCnt is >= 8:
Code:
"checkbootcount=\
if fatload mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4; then\
calc.l *0x81c00000 + 1 0x81c00000;\
if itest.l *0x81c00000 < 0; then\
echo Bad Boot count (Fixed);\
mw.l 0x81c00000 0 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4;\
fi;\
if itest.l *0x81c00000 > 7; then\
echo Boot count exceeded;\
echo Forced to boot into recovery mode for Factory Fallback; \
mw.b 0x81c00000 0 0x200;\
cp.s \"boot-recovery\" 0x81c00000 0xd;\
cp.s \"recovery --restore=factory --update_package=MISC:factory.zip\" 0x81c00040 0x3d;\
mw.b 0x81c00048 0xa 1; mw.b 0x81c0005a 0xa 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 BCB 0x200;\
mw.l 0x81c00000 0 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4;\
else\
echo Boot count OK;\
fi;\
fi" \

mali100 said:
Once it's stable and well tested, yes.
By the way, does someone know how the reboot to recovery from a running system works on other devices? Does this work on the Nook Color?
"adb reboot recovery" and "reboot to recovery" from CWM just cause a normal reboot to android.
Click to expand...
Click to collapse
On the NC running CM7:
Boot to Recovery from Rom Manager - works
Boot to Recovery from CM power menu - works
reboot recovery from adb - works
Reboot to Recovery from CWM - boots to CM

ros87 said:
There's some trickery going on in u-boot:
When BootCnt is >= 8:
Click to expand...
Click to collapse
Thats not what i meant. Other android devices allow it to boot from a running system directly into the recovery and I would like to know what function or switch is used for this. Or do you think they just set the boot-counter to 8?

FletchF said:
On the NC running CM7:
Boot to Recovery from Rom Manager - works
Boot to Recovery from CM power menu - works
reboot recovery from adb - works
Reboot to Recovery from CWM - boots to CM
Click to expand...
Click to collapse
Ok, thanks for the info.

mali100 said:
Thats not what i meant. Other android devices allow it to boot from a running system directly into the recovery and I would like to know what function or switch is used for this. Or do you think they just set the boot-counter to 8?
Click to expand...
Click to collapse
No, but the recovery is almost certainly not called directly.
What other devices are doing I cannot say, but on the NST you write your intentions to BCB and then reboot methinks

[TUTORIAL (UPDATED!!!][Unofficial CWM Recovery 5.0.2.6][ROM Manager]Work together

WARNING!
THIS NO LONGER WORKS FOR VERSIONS 4.8.184 and up.
It will continue to work as long as you don't mess with it or reflash your recovery if it's already working for you but for newer versions or ROM Manager it's even easier!
Alquez now has Unofficial Official Support!!!
For newer versions simply do the following to allow full functionality in ROM Manager and ROM Manager Premium:
1/ Flash Alquez's Unoffical 5.0.2.6 ClockworkMod recovery
2/ Install ROM Manage from the marketplace
3/ Click on Option 1 to flash CWM recovery in ROM Manager
4/ Choose "Upsupported Device"
5/ Choose "3.x"
6/ You're done!
Video Tutorial And Proof it works here.
First off. Some warnings!
*This generally works but you COULD possibly have to do a nandroid restore of your system so BACK up before you attempt!
*This DOES NOT allow you to flash downloadable ROM's from within Rom Manager!!! There are no downloadable roms for the Wildfire S. The one's you see will be for the HTC Aria!!!
*This does not allow you to use the experimental and other CWM Recoveries available from within Rom Manager!!!
What this does do:
*Allows you to make PROPER format Nandroid backups that will work in programs like Titanium Backup, etc (Although TBP now has support for "exotic" CWM files like CWMU 5.0.2.6.
*Allows the following features in Rom Manager:
-Reboot Into Recovery (Will boot into 5.0.2.7 though)
-Install ROM from SD Card
-Manage And Restore Backups
-Backup Current ROM (The most important as this method creates a by the book Nandroid backup unlike creating one from inside Unofficial 5.0.2.6)
-Fix Permissions
-Partition SD Card
How to achieve this trick and where it came from:
*Credit for the this trick goes to Insink72 and myself. Insink72 played around in Rom Manager and it started working for him. He managed to remember at one point he flashed the HTC Aria image so I figured out what he did and made it a confirmed process that can be replicated if instructions are followed.
What you are going to do is to install Unofficial CWM Recovery via hboot, install ROM Manager, then through ROM Manager leave some HTC Aria ghost code in place that enables some functions lost in the ported Unofficial version while keeping the majority of your recovery as Alquez's Unofficial 5.0.2.6
ROM Manager is going to think, and in a way it's right, that you actually have 5.0.2.7 installed.
Ready?
1/ Download Alquez's Unofficial ClockWorkMod Recovery 5.0.2.6
2/ Place the PG76IMG.zip file on your SD card's root folder
3/ Power down.
4/ Remove and replace battery
5/ Press Volume Down and Power at the same time to boot into hboot
6/ When it finds the PG76IMG.zip press volume up to flash it and reboot the phone.
7/ Boot to the OS and download Rom Manager from the Android Market and install it.
8/ Run ROM Manager
9/ Choose the first option "Flash ClockworkMod 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"
}
10/ From the list choose "HTC Aria"
11/ When done power down again
12/ Remove and replace battery
13/ Press Volume Down and Power to boot into Hboot
14/ Press Volume Up to AGAIN flash Unofficial 5.0.2.6 recovery
15/ Reboot phone and go into operating system (At this point look at troubleshooting below if it doesn't boot)
16/ Rename or remove the PG76IMG.zip from your SD card's root folder (I rename mine to CWMPG76IMG.zip and leave it there)
17/ Go to Rom Manager. It should say you now have 5.0.2.7 installed
That's it! You inserted the remaining code required to backup your rom from ROM Manager!
To verify it choose "Backup Current ROM then click ok. it should reboot to the ghosted bit of 5.0.2.7 code in ugly green and pink and start making a NANDROID backup followed by an auto reboot.
If you reboot into recovery it should boot to the nicely coloured 5.0.2.6
Troubleshooting:
If your OS gets stuck on the boot splash screen (not very likely but can happen):
1/ Power Down
2/ Remove the PG76IMG.zip from your SD card using a card reader and and computer or via fastboot USB in the phone
3/ Replace SD card and replace battery
4/ Volume down and Power to get to Hboot then enter recovery 5.0.2.6
5/ Wipe Data/Factory Reset
6/ Mounts and Storage/Format System
7/ Advanced/Wipe Dalvik Cache
8/ Backup and restore/Restore your last backup made before the freeze.
9/ Reinstall ClockworkMod Rom Manager from Android Market
Good to go!
PLEASE CLICK THANKS IF THIS HELPED YOU!

Hi there. Tried this trick and it works...but...when i select Reboot to recovery in ROM Manager it boots 2.5.0.7 by CWM and when via Bootlader 2.5.0.6 by alquez. Is it normal?
UPD
I've readed tutorial carefully and found an answer

morozzkin said:
Hi there. Tried this trick and it works...but...when i select Reboot to recovery in ROM Manager it boots 2.5.0.7 by CWM and when via Bootlader 2.5.0.6 by alquez. Is it normal?
Click to expand...
Click to collapse
Says that right in the tutorial. Yes it's normal.
*Allows the following features in Rom Manager:
-Reboot Into Recovery (Will boot into 5.0.2.7 though)
Click to expand...
Click to collapse
If you liked it please click thanks.

Thanks, worked like a charm

Nice tut. Correct me if I'm wrong, but if you have the unofficial installed, can't you just hit settings in ROM manager and manually override as an aria?
Sent from my HTC_A510c using Tapatalk

I put the PG76IMG.zip on Sd card, but didnt work.
"Main version is older
Update faild
Press power button to reboot."

I put the PG76IMG.zip on the SD card, remove-insert the battery, start-vol_down
but on the screen there are the error:
C I D incorrect!
Update Fail!
Press <POWER> to reboot.
My phone is S-On, unlocked by HTC-dev, and rooted with supertool v3
how i can install the recovery?!?!
thx for answer

Nice tutorial man! Ty

ares7610 said:
I put the PG76IMG.zip on the SD card, remove-insert the battery, start-vol_down
but on the screen there are the error:
C I D incorrect!
Update Fail!
Press <POWER> to reboot.
My phone is S-On, unlocked by HTC-dev, and rooted with supertool v3
how i can install the recovery?!?!
thx for answer
Click to expand...
Click to collapse
s-on means its locked, u didn't unlock it properly ... thets why u get cid error...

b02 said:
s-on means its locked, u didn't unlock it properly ... thets why u get cid error...
Click to expand...
Click to collapse
Uh, s-on is still there after unlocking. Bootloader unlock does NOT give S-OFF.
via HTC Wildfire S powered by CM7.2

ah, my bad then... then its not fully unlocked if u cant put recovery ?

b02 said:
ah, my bad then... then its not fully unlocked if u cant put recovery ?
Click to expand...
Click to collapse
You CAN put recovery, roms and obv root. Only sim lock is there and u cant flash radio if u have unlocked by htcdev.
via HTC Wildfire S powered by CM7.2

Sorry for my misunderstanding.
I'm really confused, and maybe this reply is OT, but i don't have understand if
i can use Clockwork on WFS ( in the market version i don't see the WildFire S phone)
and,
the real problem, i don't know how i can FULL DUMP the actual original rom present in my phone.
If i have understand well, i can't install the recovery because my phone have S-ON, but i can install other rom.
In this case i can install a new rom, but i can't make a full dump.
It's correct?
Sorry again for OT reply, and thank you very much for your patience

ares7610 said:
Sorry for my misunderstanding.
I'm really confused, and maybe this reply is OT, but i don't have understand if
i can use Clockwork on WFS ( in the market version i don't see the WildFire S phone)
and,
the real problem, i don't know how i can FULL DUMP the actual original rom present in my phone.
If i have understand well, i can't install the recovery because my phone have S-ON, but i can install other rom.
In this case i can install a new rom, but i can't make a full dump.
It's correct?
Sorry again for OT reply, and thank you very much for your patience
Click to expand...
Click to collapse
You can use clockworkmod with htcdev unlock, you only need to download the one from alquez and flash it in bootloader or with fastboot.
If you got it you can backup yours and flash new roms with it.
This tut here is just a little hack to get rommanager and clockworkmod work together even if it's not officially supported.
Swyped from my desire s far away from my pc

I put the PG76IMG.zip on Sd card
"Main version is older
Press power button to reboot."
Update faild

New tutorial and video tutorial and proof of the new Rom Manager full support working in first post...

d33ps1x said:
New tutorial and video tutorial and proof of the new Rom Manager full support working in first post...
Click to expand...
Click to collapse
Cool update from clockworkmod.

*se-nsei. said:
Cool update from clockworkmod.
Click to expand...
Click to collapse
I tested backup , reboot to, restore, install zip from, and they all work great.
This is definitely cool.

superuserx said:
I put the PG76IMG.zip on Sd card, but didnt work.
"Main version is older
Update faild
Press power button to reboot."
Click to expand...
Click to collapse
Extract the recovery from the zip file ans flash it via fastboot flash recovery recovery.img

I have the ROM Manager with CM7, but I don't really get why it's here... Sounds like the recovery mode? Will I keep my settings/apps/etc if I install a new update or a new ROM?

[i317-i317M][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch 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
It also adds a full touch interface a completely configurable GUI
Since many requests to port it to i317/M, here it is finally released
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
I would appreciate a screen shot from your device, mainly under GUI options or custom backup menu where you select partitions
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
i317 (t0lteatt)
i317M (t0ltecan)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse

Recovery (.zip) packages instructions
They come in the form of .zip files that can be flashed in cwm recovery
Download philz_touch_xxx.zip file
Put the previously downloaded philz_touch_xxx.zip file on your sd card
Boot into recovery (volume up+home+power)
Select "Install zip" and browser to your downloaded zip file.
Now select the philz_touch_xxx.zip fileyou copied in previous step
You will have PhilZ Touch Recovery flashed
Odin packages instructions
They come in the form of .tar.md5 file
boot into download mode
start odin3 and configure it as in picture below
connect phone in download mode to PC via USB
press start to flash the tar.md5 package
normally, phone should auto-reboot into recovery.
If it reboots into android and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
{
"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"
}
<< Root your phone and reset Yellow Triangle >>
Once in recovery, flash the attached Root_SuperSU.x.xx.Only-signed.zip file to root your phone
If you want root + busybox: flash Root_SuperSU.x.xx-Busybox.1.20.2-signed.zip file
to remove yellow triangle, use TriangleAway

Before asking for support:
Make sure your issue is recovery related
All external sdcard issues: first format in PC with primary partition, tons of people are formatting as logical and come cry
Reproduce your issue and while in recovery:
Go to Advanced / Report Error
Copy the /sdcard/clockworkmod/recovery.log and attach it here
Give detailed info about your issues
Without these, there is little chance I can help you, so, do not get mad if I do not answer
Click to expand...
Click to collapse
Request a build for a new device:
Go to sammobile.com
Search for your phone
Download the +1Gb last firmware file (ideally unbranded and in any case a European version)
Unzip downloaded file
Rename the tar.md5 file into .tar
Extract from the tar file the boot.img and recovery.img files
Post them here with exact file name of the file you downloaded from sammobile (exp: N7100XXDLL7_N7100OXADLL4_XEF.zip)
Post a link to your phone specifications, ideally, a comparison between your phone and the n7100
If they do not share same hardware, ensure there is a cm10.x source for your phone (Optional if you do not know how to check it)
You got a 100% chance for an answer and 90% chance that I release it
Click to expand...
Click to collapse

Since i317 has its own forum, I am splitting its recoveries from my previous n7100/n7105 thread
Please also take a look and read some of the last pages here, as most of your questions would be answered
http://forum.xda-developers.com/showthread.php?t=2028103
Keep thread clean for only things related to this specific recovery
Do not clutter with general support questions, kernel/ROM general issues...

interesting might try this out tonight once i get home.

Re: [21.02.2013][PhilZ Touch][i317/M]4.63 Touch Enhanced CWM 6.0.2.8-exFAT-ext4-Root
Installed and works great. I really like the layout style. Just made a back up to ext sd and like how fast it was. Advance options are nice also. Thanks!
Sent from my SGH-I317 using xda premium

I would like to get some clafificaiton about what Support for TWRP means - does this mean if I flash the Touch Enhanced Recovery - I can restore nandroids that I made on TWRP?
SOrry if that is a NOOB question - but I just wanted to be sure - to avoid doing something stupid -

Re: [21.02.2013][PhilZ Touch][i317/M]4.63 Touch Enhanced CWM 6.0.2.8-exFAT-ext4-Root
mocsab said:
I would like to get some clafificaiton about what Support for TWRP means - does this mean if I flash the Touch Enhanced Recovery - I can restore nandroids that I made on TWRP?
SOrry if that is a NOOB question - but I just wanted to be sure - to avoid doing something stupid -
Click to expand...
Click to collapse
Actually it is a fair game, you can:
- backup in TWRP format to migrate from cwm to TWRP
- Restore from TWRP backups to migrate to cwm
Backup in TWRP format is always done in the multi volume format. Restore supports both. At the end, migration should be smooth.
If you find bugs, always post a log before requesting support please
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
Actually it is a fair game, you can:
- backup in TWRP format to migrate from cwm to TWRP
- Restore from TWRP backups to migrate to cwm
Backup in TWRP format is always done in the multi volume format. Restore supports both. At the end, migration should be smooth.
If you find bugs, always post a log before requesting support please
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
This is simply awesome - I look forward to using this and can see there are a lot of advantages this offers -but I want to do a lot of reading first so I am sure I understand how to use it - really cool stuff...thanks!

mocsab said:
This is simply awesome - I look forward to using this and can see there are a lot of advantages this offers -but I want to do a lot of reading first so I am sure I understand how to use it - really cool stuff...thanks!
Click to expand...
Click to collapse
Restore of TWRP backups was tested by i9300 users and reported fine too. I personally tested for i9100 too
Only part I am still unsure and need feedback is android-secure restore...

Small update
New in PhilZ Touch v4.64
fix: when disabled, virtual keys would still show for a fraction of a second on start
Click to expand...
Click to collapse
v4.64
i317/i317M
cwm: http://www.mediafire.com/file/348v6u3hcx5n793/philz_touch_4.64-i317M.zip
odin: http://www.mediafire.com/file/ckx6cvjjtcz09jn/philz_touch_4.64-i317M.tar.md5
Click to expand...
Click to collapse

Awesome recovery. I find it to be on par with TWRP except for the backups. TWRP has a better setup for backups letting you compress and select what partitions you want to back up, including EFS. This recovery seems to have flawless USB storage mounting though, which TWRP doesn't have. That saved my ass tonight.

Re: [23.02.2013][PhilZ Touch][i317/M]4.64 Touch Enhanced CWM 6.0.2.8-exFAT-ext4-Root
DeMiNe0 said:
Awesome recovery. I find it to be on par with TWRP except for the backups. TWRP has a better setup for backups letting you compress and select what partitions you want to back up, including EFS. This recovery seems to have flawless USB storage mounting though, which TWRP doesn't have. That saved my ass tonight.
Click to expand...
Click to collapse
You can have all the custom settings and selective backup and restore under the Custom Backup and Restore menu
And it supports TWRP backup and restore too...
Sent from my GT-I9100 using Tapatalk 2

That's insane. This recovery just became my daily driver.

DeMiNe0 said:
That's insane. This recovery just became my daily driver.
Click to expand...
Click to collapse
Thanks
Next updates will even make it nicer

Just installed on my Note2 and wow. This thing is so quick and smooth. Hats off to the devs. :good:

I've been running with this recovery now for a few days and all I can say is WOW! This is an amazing recovery; hands down the best i've used for android period. Phil took the best parts of CWM and TWRP and mashed them together in a sexy recovery image.
http://forum.xda-developers.com/donatetome.php?u=4666971
Click that donate button; you know you want to!

New in PhilZ Touch v4.87
v4.63 ---> 4.64
fix: when disabled, virtual keys would still show for a fraction of a second on start
v4.64 ---> 4.87
Backup and Restore:
menu Custom Backup and Restore can now be accessed in main Backup and Restore menu
support restore backups from /sdcard/0 (Android 4.2) in custom jobs and TWRP mode
add support to sd-ext ext4 partition on external storage
menu to delete custom and TWRP backup images
auto-reboot option for custom backup and restore jobs
set .android_secure path in custom jobs
smart auto detect android_secure for stock CWM backup and restore operations
fix preload was selectable in TWRP jobs (even if would not actually be processed)
progress bar is no more overwritten by text
time and battery stats are shown and refreshed during nandroid operations
on successful or cancelled nandroid jobs, user background icon is restored
on cancelled nandroid jobs, progress bar is correctly reset and user background icon is restored
User configurable gesture actions
gestures: double tap, long press/move, long press/lift, slide left, slide right
always vibrate on long press/move action validation
actions: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
GUI
default black theme without background icon
toggle clock and battery on top
header title will be auto-shortened to not overwrite battery and clock on lower res devices
battery and clock will truly refresh indications every 15 sec
user configurable dim screen timer
user configurable turn-off screen timer
manually adjust brightness (stock kernel doesn't support lower than 65, but recovery binary will accept 25 on custom kernels)
when double tap mode is selected, you now really need to double tap the same menu to validate it
menu Set Time Zone moved to GUI settings
fix Moscow UTC time
Misc
add support to sd-ext ext4 partition on external storage
Move Clean before instal new ROM menu to Wipe Data/Factory Reset menu
fix /system was left again mounted after start up and showing log
Click to expand...
Click to collapse
I need some testers please for some of the features introduced:
- android_secure correct support
- sd-ext support
- any of the above listed new features you'd like to report about
I am pausing a bit on this one, to get users feedbacks and maybe support some new devices
After that, I am doing multi-boot and full GUI scroll revision
Download links
v4.87
i317/i317M
cwm: http://www.mediafire.com/file/eao2fga7ta3sd3d/philz_touch_4.87-i317M.zip
odin: http://www.mediafire.com/file/cdqmd5owgr0hhd7/philz_touch_4.87-i317M.tar.md5
Click to expand...
Click to collapse

When I try to make a custom backup no matter what partitions I choose, I get an "Error while backing up *PARTITION NAME HERE* image!" error. Does this for the TWRP backup option as well.

Re: [03.03.2013][PhilZ Touch][i317/M]4.87 Touch Enhanced CWM 6.0.2.8-exFAT-ext4-Root
Can someone punt new to a help section or user manual so i can read how to convert from twrp to cwm and vice versa. Thanks
Sent from my GT-N7105 using Tapatalk 2

[RECOVERY][N8000/N8013]CWM 6.0.4.4{Fully Working}

Downloads And Q&A
Downloads :
1.IMAGES
N8000-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
N8013-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
2.TAR FILES
N8000-CWM-6.0.4.4.tar Build #1 {For Odin}
N8013-CWM-6.0.4.4.tar Build #1 {For Odin}
Change Log :
Build #1 Fully Working.Whats To Do In Future Build ?
Enable Touch .
Add OTG Support.FAQ:{Please Read Before Posting}
Q: OMG ! Recovey Not Booting What To Do ?
Alease Dont try entering recovery first time from advanced power menu just do it the hard way
Q:My Device is not getting read by windows ?
A:Uninstall all drivers that you installed for the device .Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.

For Later Use

it can't mount the external sd

iRoNX said:
it can't mount the external sd
Click to expand...
Click to collapse
seriously i did not notice such error, i will see what i can do tomrrow Thanks

First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.

Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
Well thats odd :/ are you sure you have n8000 build not n8013 as i am recovery fine

Yes, i'm pretty sure. I've tried to do this few times via both terminal and odin. Now will try one more time...
UPD: I've repacked the img file with the tar archiver+ put md5 checksum (tar.md5) and flashed it with odin successfully.
And like iRoNX said it can't mount extSD: "error mounting /storage/sdcard1"
UPD2: The recovery from similar thread have another issue: cannot format "/data" and cannot explore internal flash )))

Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
+1.
The Odin tar file is not OK. Although I did not get a bootloop, the indicator on phone in download mode goes to the end and then stays there at "NAND write". I has to disconnect the phone and reboot manually, and my old version of CWM was still there (phew!). The .img files and dd worked fine.
Thanks anyways for this update !!!! It worked to get me on JB 4.4 !
Update: When phone is powered off and charger connected, upon starting there is a garbled green image that comes on for several seconds - most likely the battery charging icon - and then the phone will start up. It was not there before flashing 6.0.4.4. Anyways my phone does start up........

Tar file not working.. gets stuck at "Nandwrite"

Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip

zedomax said:
Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip
Click to expand...
Click to collapse
Way to go, champion !!

Flashed but the external SD card doesn't work
Sent from my GT_N8000

ODIN Image file attached.
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L

SD cards problem
Hello again,
Within this version of CWM, the SD card problem seems to be only for the 64g cards as tested on my N8013. However, after you flash the Rom you'll using, there is no problem with 64g cards outside of CWM recovery mode.
Smaller sized cards 32g and less will mount fine while you are in CWM recovery mode.
Cheers,
L

lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Not working for me... says img. file is invalid. then ends.

Love it. Thanks.

lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Anyone confirm this as working?
Edit: Not working. Odin says invalid.

missing file
I seem to have lost my \efs folder, and in searching for a solution one of the steps I'm told to take is to flash "N8000-CWM-6.0.4.4.tar". However, it doesn't seem to exist anywhere (now that goo is gone), other than in this thread and the version here seems to be broken. Does anyone have the N8000 version of the .tar file?

Boot-loop, can't wipe device.
Hey everyone. I'm not exactly sure what happened, but it seems that my GT-N8000 is on the fritz again. The device was screen-off this morning (I left home) and when I came home it was in a reboot loop.
I jumped into recovery (CWM v6.0.4.4) to try to wipe both cache and dalvik (both successful) and rebooted. Same bootloop.
So then I decided to wipe the storage and reinstall the ROM (Gnabo v8 is what I had been running). When I attempt to "wipe data/factory reset", it says "formatting data . . ." and then reboots into the bootloop again.
Then I thought that maybe it was wiped, so I attempted to flash Gnabo. It installs successfully (Installing update, blue bar goes across, "Enjoy!" and "Install from sdcard complete."), however, when the installation starts, I get the first box and then it sits for almost 2 minutes before the blue bar appears, fills in just a few quick seconds, and then displays the completed message. It seems to me that the installation and the blue bar should be taking longer, but what do I know. Anyway, I rebooted (No, don't fix ROM flasing stock recovery on reboot), then back into the bootloop. So I'm still losing.
I don't know if it's related, but some months ago I had something similar happen in that the device was in a bootloop and it turned out that it had somehow lost the /efs folder. I had restored that (thanks XDA forums!) and it had been working fine since about June 2015.
I'm starting to think that my memory has gone bad, and that I basically have a 10.1 inch paperweight. Suggestions? Thanks for any help you can provide.

[DEV][callisto] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.27.9

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.27.9
for Galaxy 551 / GT-I5510 / callisto
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 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.27.9)
https://docs.google.com/file/d/0B5c3gpyMBJusbWk2U1k3OWxRMEk/edit
aromafm_callisto.zip (v1.91)
https://docs.google.com/file/d/0B5c3gpyMBJuscnQyN28xZWNKeEE/edit
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.

: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.
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

Thank it is nice recovery working like charm.

@Bhargav97 at the time of updating OTA , recovery didn't boot in system always boot back in recovery. I didn't face such problem before with your recovery.

UPDATE:
Changelog:
-PhilZ sources updated to 6.23.8 (26.03.2014)
-CM-ota compatibility fixes.
Please give feedback especially on cm-ota.
Download link updated in first post.

No luck booting back in recovery not booting in system.

Ansh2000 said:
No luck booting back in recovery not booting in system.
Click to expand...
Click to collapse
Will see to it. It's working for all devices. What's wrong? I'll try to figure it out.

@Bhargav97 any fix, recovery booting normally in system only problem occur when flash ota patch automatically.

@Bhargav97 you would like to compile TWRP for callisto.
Thanks in advance.

Ansh2000 said:
@Bhargav97 you would like to compile TWRP for callisto.
Thanks in advance.
Click to expand...
Click to collapse
I would have done it until now but you wasted my enough time in PMs. You asked the same question in 3-4 PMs. And now, here. I already started work on TWRP for armv6 devices. I first did it for Galaxy Mini. Now, I'm making it stable. Once, it gets stable, I'll make it for other devices and the last would be your device. Because, I don't see many people using this Galaxy 551 and moreover you wasted my time in PMs, so...keep waiting

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/0B5c3gpyMBJusUnZnUEc1MW9iQlk/edit?usp=sharing

Thanks for your hard work. Recovery is not booting in system always booting back in recovery except that every thing working like full philz recovery.

Ansh2000 said:
Thanks for your hard work. Recovery is not booting in system always booting back in recovery except that every thing working like full philz recovery.
Click to expand...
Click to collapse
Bhargav97 have done fixing and told me to compile.
Here is the fixed version:
https://docs.google.com/file/d/0B5c3gpyMBJusbWk2U1k3OWxRMEk/edit
And the Aroma File Manager:
https://docs.google.com/file/d/0B5c3gpyMBJuscnQyN28xZWNKeEE/edit

@Bhargav97
@chraso
Thanks, every thing is fine now booting normally on system.

Any update is coming ?

I'm posting this new version updated 16-04-2014
PhilZ-Touch v6.41.6:
https://docs.google.com/file/d/0B5c3gpyMBJusZjBnLU5ER0RvMWc
Need feedback for specially the Hardware & Virtual on-screen keys.

@chraso all hardware and virtual on screen keys working correctly and now virtual keys got transparent but philz touch background doesn't work.

Any news? As the latest Callisto ROMs require a changed recovery (b/c of partition layout), these PhilZ recoveries won't work anymore, right?

steve8x8 said:
Any news? As the latest Callisto ROMs require a changed recovery (b/c of partition layout), these PhilZ recoveries won't work anymore, right?
Click to expand...
Click to collapse
I don't have a PC nowadays so I don't think there will be any updates (atleast for the time being). You can use CWM for flashing CM11 builds and PhilZ Recovery for older ROMs. Should be alright (?)
I think unpack-repack of kernel and fstab (replacing from latest CWM) might work but I'll need somebody's help that can unpack-repack in their PC.

I'm getting:
# flash_image recoveryonly /sdcard/recovery.img * - permission denied
if I su, then run the command I get:
flash_image recoveryonly /sdcard/recovery.img
Any Solutions?

Develop Bugs

welcome