[RAZR HD Android Development] Fanarkle:
Here are the bits from the guide and FAQ that might be relevant:

How to select your .android_secure path

In Custom Backup and Restore operations, you can select the target/source for android.secure or disable it

In stock backup/restore operations, include those started with ROM Manager, you can also force a target/source for .android_secure

basically, recovery will check first external storage for a .android_secure folder. If it doesn't find it, it will look in internal storage

If you want for example .android_secure to be in internal sd, just delete .android_secure folder from external sd and ensure there is a .android_secure folder in internal sd

for external sd, just ensure there is a .android_secure folder in it. It will be chosen what ever is the internal sd state

Custom Backup and Restore menu

This is one of the most powerful features of this recovery.

It is made completely open source code, built from sratch. Just keep credits headers and give proper credit if you use them

You can select which partitions you want to backup or restore

You can choose your .android_secure source and target or even disable it

You can set it to reboot directly after job is done

backups will go under the folder clockworkmod/backup (please move all contents of custom_backup folder used in previous versions to the default backup folder in cwm)

TWRP backups go under stock TWRP/BACKUPS/device_id folder and will be automatically recognized by TWRP

Custom Restore Menu allows you to restore from any of the stock clockworkmod backups, the custom backups or the TWRP backups

efs is backed up under clockworkmod/backup/.efs_backup

- efs must be selected alone for backup in cwm mode

- it will create 2 copies: a tar and raw img backup using cat/dd command

- to restore efs, under Custom Restore menu, select efs only and toggle between tar and .img

- restore .img format is advised, but tar will work under most circumstances

modem.bin files can be named any_thing.bin and must go under clockworkmod/backup/.modem_bin

- with that, you can flash modem.bin files that come with official firmware (may need unlocked devices for some models)

if you disable md5, your backups will no more be recognized by stock cwm builds. Look at next step to regenerate md5 for stock cwm compatibility. Otherwise, all stock and custom backups are backward compatible with stock cwm (except special partitions like preload, recovery, modem and efs which stock cwm doesn't support)

you can now recreate md5 sum for any backup you want. Use with caution!

2- I backed up my data and I cannot find it when I boot into phone

Stock CWM and CM Updater app are using a non conventional linking for internal storage: internal storage is linked as /sdcard/0

PhilZ touch supports true /sdcard paths by linking it to either /data/media or /data/media/0

/sdcard/0 has no meaning in PhilZ Touch unless you set it to /data/media

By default, if a folder /data/media/0 exists, PhilZ Touch will default /sdcard to it, else it will use /data/media.

The advantage is for all stock +4.2 users: they can directly access their backups from /sdcard, while in main system and see them on PC in MTP mode.

You can override that setting in Advanced Menu and force it to /data/media or revert to /data/media/0

I recommend moving all your old cwm path to /data/media/0/clockworkmod and set sdcard to /data/media/0 unless you are switching between stock CWM and this mod or you need CM Updater app

To sum it up: for stock +4.2 rom users, keep default (/data/media/0). For CM users, if you frequently use CM Updater to flash in recovery, force /data/media

3- I come from stock CWM/TWRP and PhilZ Touch cannot see my backups

Read Answer 2

I was unable to restore from within PT 6.48.6 until I went into the Advanced Menu and forced /data/media. Also, if you only have issue with .md5 you could regenerate it from the custom backup and restore menu.