yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] danarama:
Hi,

Firstly, i'm a big advocate for not using ROM manager. I personally think it's better to use recovery natively.

To restore the backups, you have a few options

1)Ensure there are no spaces in the file name

2)Turn off Md5 checksum verification in recovery (restores without checking md5)

3)Manually regenerate md5 using terminal commands*

*

md5sum /sdcard/clockworkmod/backup/backup-name/* > /sdcard/clockworkmod/backup/backup-name/nandroid.md5
[Nexus 5 Android Development] ZooBaAr:
Thanks for that, just a pita , nothing lost really i just have to tweak new install all over.

Rom manager uses CWM and it stores the backups in a protected area that I notice Philz does not use or seem to have access too as all the Philz in-recovery nandroids are stored in emulated sd. Even moving my previous backups, Philz does not recognize them.

Is this normal?

Also so far the date fix has stuck, only had to redo it once so far and after i redid it the backup i did before I changed date was gone. It was dated 1970 xxxx. NOrmal?

Thnks

zoo
[Nexus 5 Android Development] danarama:
Lets not talk about "emulated". This will cloud the issue.

Pre 4.2 android that had fused sdcard, the /sdcard was mounted in /data/media.

Post 4.2 android that had fused sdcard, the /sdcard was mounted in /data/media/0.

So you see, its not that CWM stores its backups in a "protected area" at all. Its just they never bothered to make CWM intelligent enough to detect /data/media/0. In short, CWM is antiquated, using an outdated (and frankly, wrong) location to store it's backups.

Philz will restore cwm backups fine so long as they're in /data/media/0/clockworkmod/backup.

Nothing should every be "gone". 1970 date is normal before setting the time
[Nexus 5 Android Development] Phil3759:
No, PhilZ can see both places

Just toggle them in Advanced menu, but it needs a reboot to take effect
[Nexus 5 Android Development] danarama:
Not simultaneously and for a 4.2+ device shouldn't be necessary.

CWM users migrating to Philz should move their backups to /data/media/0 and never use CWM again.
[Nexus 5 Android Development] .A.J.:
Is there a trick to getting the changed date/time to stick. I tried the first two options in the time/date change menu and neither work for me. The first does nothing and the second gives me a Qualcomm daemon not found notification. I'm sure that I'm just missing something obvious. Any help would be appreciated.
[Nexus 5 Android Development] Phil3759:
FAQ updated today...
[Nexus 5 Android Development] euki69:
EFS backup

hey guys i noticed theres no EFS option when performing a backup, but I noticed they mentioned EFS on PhilZ's thread. I want to do a backup on one N5 and restore on another so I wanna make sure it's safe to do so on here :o

thank you!
[Nexus 5 Android Development] Phil3759:
I think I asked once for it:

I need the partitions lines from fstab
[Nexus 5 Android Development] euki69:
I'm sorry but I don't know how to get those lines :x does it auto backup efs? im trying not to
[Nexus 5 Android Development] jwhyte:
EFs backup is not an option with philz.

But it's always safer just to set everything up again.
[Nexus 5 Android Development] euki69:
Thanks very much! I've had several RMAs (dead pixels and even had one shipped to me with a open gap on the backplate O.o) so I'm sorta tired of transferring data and setting everything from scratch..

I'm doing some researches.. and I was wondering if it's generally okay to backup "system" to a identical N5? I keep getting conflicting answers..

edit: Scratch that, I found the answer. I should be able to
[Nexus 5 Android Development] jwhyte:
I would let [MENTION=2872010]rootSU[/MENTION] answer that one.

I am a flashaholic so set mine up clean a couple times a week.
[Nexus 5 Android Development] danarama:
I couldn't find the info in fstab.

Yes, fine
[Nexus 5 Android Development] Phil3759:
maybe just ask some dev in your forums to post the fstab entries for your efs

could be you need 2 partitions for that like many new devices
[Nexus 5 Android Development] jwhyte:
I wouldn't even patch it in too many people have already restored it to RMA devices.
[Nexus 5 Android Development] danarama:
It looks like 2 partitions but couldn't find corresponding entries in fstab. At least no fstype

But as mentioned, people bricking with EFS restore on. TWRP due to many RMA users. I think the flashable zip method is sufficient.
[Nexus 5 Android Development] Striatum_bdr:
Here is the script used in an efs backup zip:

# backup partitions

/sbin/busybox dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/tmp/efs1.img;

/sbin/busybox dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/tmp/efs2.img;

cd /tmp;

If I'm correct they are not in standalone partition.

And of I'm correct again, we are not on a Samsung device, are there really issues with efs? It's a psycho drama on Samsung but here...
[Nexus 5 Android Development] danarama:
Yes, I've already provided this information but it is not enough. We need fstype, but the flashable zip you probably got this from (which is probably the same one I did) is fantastically doing the job anyway.

I have only seen EFS go wrong on Nexus 5 because people restore EFS from older RMA device so what does that say? ;)
[Nexus 5 Android Development] Phil3759:
I can easily add it but I need the fstype to make the code universal and not only specific

I will work later on a a raw mode as fstype for all devices to use dd or cat

Then, it will be easier to add
[Nexus 5 Android Development] Phil3759:
Update 6.19.3

Based on latest source updates

It uses back the cm kernel, hope they fixed graphic glitches

else, let me know
[Nexus 5 Android Development] danarama:
Glitches remain I'm afraid :(
[Nexus 5 Android Development] Phil3759:
They suck

I will revert to stock kernel

Check my git

I will upload later changes needed with new dbtool things
[Nexus 5 Android Development] danarama:
Will check your git and test compile with stock.
[Nexus 5 Android Development] Phil3759:
Uploading a new 6.19.3

revert to stock kernel to fix graphic glitches
[Nexus 5 Android Development] danarama:
Updated Title and Changelog with new version.
[Nexus 5 Android Development] :
Hello,

I just flashed for the first time the last update of this recovery (I was using the "classic" CWM since a long time), I must say I'm impressed with the customizations :good:

Great work, thanks Phil3759 and rootSU ;)
[Nexus 5 Android Development] danarama:
Glad to see you onboard. It's all Phil's work. I'm just the thread maintainer. I'm about ready to compile Phil's work from now on so hopefully he can have more time to himself :)
[Nexus 5 Android Development] cicciolon082:
I noticed that the option "include /preload" into "Misc Nandroid Settings" shows N/A (no way to change)...is it good to make a Nandroid backup for Nexus 5 without including preload??? Thanks!
[Nexus 5 Android Development] danarama:
We don't need /preload

Here is a full partition list for the N5

lrwxrwxrwx root root 1970-01-15 02:15 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-15 02:15 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-15 02:15 abootb -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-15 02:15 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-15 02:15 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-15 02:15 crypto -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-15 02:15 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-15 02:15 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-15 02:15 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-15 02:15 imgdata -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-15 02:15 laf -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-15 02:15 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-15 02:15 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-15 02:15 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-15 02:15 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-15 02:15 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-15 02:15 pad -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-15 02:15 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-15 02:15 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-15 02:15 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-15 02:15 rpmb -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-15 02:15 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-15 02:15 sbl1b -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-15 02:15 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-15 02:15 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-15 02:15 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-15 02:15 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-15 02:15 tzb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-15 02:15 userdata -> /dev/block/mmcblk0p28
[Nexus 5 Android Development] cicciolon082:
And what about SE Content? Is it needed? Thanks!
[Nexus 5 Android Development] danarama:
Only the default settings are "needed". Out of the box you do not need to change any settings to get a useful backup.
[Nexus 5 Android Development] drdoulittle:
I have made Backup with flashlable.zip for TWRP or CWM.

adb command for efs.img ( Backup 1,2)when you have Problem with TWRP or CWM.

adb shell

dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1

dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
[Nexus 5 Android Development] danarama:
Yes its same
[Nexus 5 Android Development] Phil3759:
try this to get fstype

adb shell
/sbin/blkid /dev/block/platform/msm_sdcc.1/by-name/modemst1
/sbin/blkid /dev/block/platform/msm_sdcc.1/by-name/modemst2

and give output

I suspect they are emmc partitions like boot and recovery

Can you browse their contents
[Nexus 5 Android Development] Phil3759:
add to my previous post:

TWRP uses this (emmc)

/efs1 emmc /dev/block/platform/msm_sdcc.1/by-name/modemst1 flags=backup=1;display=EFS
/efs2 emmc /dev/block/platform/msm_sdcc.1/by-name/modemst2 flags=backup=1;subpartitionof=/efs1
[Nexus 5 Android Development] danarama:
It doesn't give an output in recovery.

In Android on my ROM. blkid is actually in /system/bin and /system/xbin which both also give no output.
[Nexus 5 Android Development] Phil3759:
probably emmc

Will add to my to do list

actually, since you plan to compile your self, read my guide in adding extra partitions support to nandroid menu

by editing fstab, you can easily add the two partitions for efs

the mount point will be different, but it has no impact

in fstype, specify emmc
[Nexus 5 Android Development] danarama:
Yep, will do....

I've just kicked off a build so thats a job for tomorrow.
[Nexus 5 Android Development] lolmachine4:
That might be a really stupid question, but I coudn't find the answer with a quick google search, and the toggles in the recovery itself weren't very clear to me...

So, I want to set the default backup-path to /sdcard/clockworkmod/backup. Whenever I create a backup, it gets stored to /mnt/shell/clockworkdmod/backup.

How can I change that behaviour or isn't that possible? The toggles I found that I found to sound related didnt do anything when pressed, and I couldn't enter the specific path anywhere either.

It's probably a really stupid question and I'm pretty sure I missed some basic knowledge here, so I apologize.
[Nexus 5 Android Development] danarama:
You need the setting to be toggled to /data/media/0 however on the Nexus 5 it should default to this anyway. Please supply screenshot of backup location

But /sdcard is the same as /data/media/0 is the same as mnt/shell/emulated/0 is the same /mnt/sdcard
[Nexus 5 Android Development] danarama:
Can you just help me clarify something please?

So in:

/bootable/recovery/boardconfig/BoardConfig.mk

I put:

EXTRA_PARTITIONS_PATH := "/efs"

and then iin:

/build/target/board/generic/recovery.fstab (which is the only one I have), I must put:

/dev/block/platform/msm_sdcc.1/by-name/modemst1 /efs1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst2 /efs2 emmc defaults defaults

because in:

/device/lge/hammerhead/fstab.hammerhead

all the other "by-name" partitions are listed like:

/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /radio emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sdi /sdi emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/imgdata /imgdata emmc defaults defaults

although currently in the recovery.fstab, I only have:

# mount point	fstype	device

/system	ext4	system
/cache	ext4	cache
/data	ext4	userdata
/sdcard	vfat	/dev/block/mmcblk0

Which I wasn't quite expecting...
[Nexus 5 Android Development] Phil3759:
by recovery.fstab I mean the file used as fstab

In your case, device/lge/hammerhead/fstab.hammerhead

Normally, only these would be needed:

EXTRA_PARTITIONS_PATH := "/efs"

fstab.hammerhead, add:

/dev/block/platform/msm_sdcc.1/by-name/modemst1 /efs1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst2 /efs2 emmc defaults defaults

Please, ensure you have a working backup of your efs before trying this
[Nexus 5 Android Development] danarama:
I really hoped you would say that. Thanks :)

Yeah I have. I'll take another just in case and compile this tonight...

Thank you!
[Nexus 5 Android Development] Phil3759:
good

let me know please

Without even compiling a new version, you can repack existing by changing fstab with default mount point:

/extra_part1 and /extra_part2

They are enabled by default
[Nexus 5 Android Development] danarama:
I'd already mka clean...

It's compiling now anyway. Always nice to check in the morning if it built.
[Nexus 5 Android Development] Phil3759:
Don't do that mka clean and clobber ****

Just remove your device output folder or ideally, every thing except kernel ob intermediates

When you're trained, you'll be able to remove just the intermediates you modify

Your building will be much much faster, just a few minutes
[Nexus 5 Android Development] danarama:
We'll get there eventually. Sorry for taking up so much of your time.
[Nexus 5 Android Development] Phil3759:
happy to help motivated people ;)
[Nexus 5 Android Development] .A.J.:
rootSU & Phil3759,

I apologize for interrupting your conversation but I was reading the thread and just wanted to take a moment to thank the two of you for all the effort you put into this thread & more importantly the actual recovery.

So, Thank you both very much!! Great work!
[Nexus 5 Android Development] danarama:
I love Phil's work. Its really solid and great to use with many features. If theres any way I can help to relieviate the burden on developers to support multiple devices, then I am happy to do so. In this case, hopefully even maintaining the the thread is one less thing to worry about.
[Nexus 5 Android Development] Febby:
Amazing recovery. Can't live without it on my android addiction! Just wanted to say its working flawless on my nexus. ;)
[Nexus 5 Android Development] danarama:
[MENTION=4666971]Phil3759[/MENTION] - I did a custom backup of efs and it generated 2x 3MB images as expected. Restored (in raw mode apparently) and all appeared successful. I'm not sure there's any way to know for sure as the timestamp changes on all "by-name" filesystems at boot.

However, my phone is still working....

In custom backup, the nandroid menu shows extra_ part1 and extra_ part2 as 2 separate options. Is that normal?

I:found device mmcblk link: '/dev/block/platform/msm_sdcc.1/by-name/modemst1' -> '/dev/block/mmcblk0p12'
I:/efs1 backup size (/proc)=3Mb
I:found device mmcblk link: '/dev/block/platform/msm_sdcc.1/by-name/modemst2' -> '/dev/block/mmcblk0p13'
I:/efs2 backup size (/proc)=3Mb

>> Free space: 3073Mb (23%)
>> Needed space: 6Mb

>> Backing up /efs1...
Backing up efs1 image...
Backup of efs1 image completed.

>> Backing up /efs2...
Backing up efs2 image...
Backup of efs2 image completed.
Generating md5 sum...
[Nexus 5 Android Development] Phil3759:
Great, you added efs backup/restore support :good:

However, if you defined:

EXTRA_PARTITIONS_PATH := "efs"

It shouldn't show that way in menu, but

Backup efs1 (x)
Backup efs2 (x)
[Nexus 5 Android Development] danarama:
Yep, I did define:

EXTRA_PARTITIONS_PATH := "/efs"

...and it shows as:

Backup efs1 (x)
Backup efs2 (x)
[Nexus 5 Android Development] Phil3759:
It is by design yes

You expected like twrp that you have one efs option that will backup both efs1 and efs2 ?

I did not do as i thought it a way to add preload, misc... Without having to recompile but just edit fstab with extra_part1... A simple repack does the trick that way
[Nexus 5 Android Development] danarama:
Ah that's good. Wanted to check I hadn't done something wrong.

I only used TWRP for about 3 minutes on my S3. I didn't really play much... Not to my taste really. But on S3 for Philz, there was only a single efs partition with single backup option, so I didn't know on Nexus 5 what I expected to see with 2 efs partitions. Now I know though :)

Yep no problem. When there's a new Philz build, I will compile with this option....

Can you please add to EXTRA_PARTITIONS_PATH := "/efs" to /bootable/recovery/boardconfig/BoardConfig.mk in your repo?

Quick github question (I have an account but I don't really use it)... Can I "watch" your repo and will that notify me when you have new builds? Is that possible?
[Nexus 5 Android Development] lolmachine4:
Thanks for your reply.

As I said, it was a totally stupid question - I simply did not realize the toggle has multiple options when pressed more then once. After reading your post I figured out it would work like other settings too, touch it multiple times. Stupid me... Thanks!
[Nexus 5 Android Development] danarama:
Ah gotcha. Ok.
[Nexus 5 Android Development] Phil3759:
if you watch it you'll get notified, yes

I will add needed changes to fstab and recovery sources
[Nexus 5 Android Development] Phil3759:
Update 6.19.6

- added efs backup/restore

Huge thanks [MENTION=2872010]rootSU[/MENTION]

This way you can relax a bit until you get used to compile/repack

Next major updates will have a full repo sync, so will let you continue compiling for the device :good:
[Nexus 5 Android Development] danarama:
Thanks [MENTION=4666971]Phil3759[/MENTION] - updated thread particulars
[Nexus 5 Android Development] cmdmilitia13:
1st of all great work & its nice to have people workin together. I just did a backup with the new recovery everything flawless like always but I cnt seem to find backup efs? I went to custom backup but the option is not there,I might of overlooked it?? I went thru all the options..I see that now we can format efs tho.. Dnt flame me lol..
[Nexus 5 Android Development] fbf2201:
I couldn't find it either.

But anyway great job so far. [MENTION=4666971]Phil3759[/MENTION] for developing and [MENTION=2872010]rootSU[/MENTION] for maintaining this thread.
[Nexus 5 Android Development] danarama:
Backups from Philz go to /sdcard/clockworkmod/backup.

It just depends if you set philz to /data/media or /data/media/0 (n5 /sdcard is /data/media/0 but official CWM puts it in /data/media)
[Nexus 5 Android Development] refedit:
Hey guys.

I'm having some issues with USB cable and charging and I think if I wipe everything, may solve those issues.

My Q is, am I able to SIDELOAD ROM with OTG cable?

regards and thx for great work on this Excellent recovery!! :good:
[Nexus 5 Android Development] danarama:
When you plug an OTG USB stick into the device, extra options such as "install zip from" and "Backup to.." become available.
[Nexus 5 Android Development] refedit:
so I don't even have to SIDELOAD nor rename ROM file to UPDATE.zip to flash, right? :good:
[Nexus 5 Android Development] danarama:
Sideload is something completely different.

It works the same as flashing a zip from SDcard
[Nexus 5 Android Development] tsubus:
Can't find option for efs in custom backup of latest version 6.19.6. Anything I should be enabling in the options perhaps?
[Nexus 5 Android Development] danarama:
Hmmm. I hadn't flashed it because I had built my own so kept that, but you're right - it's not there. [MENTION=4666971]Phil3759[/MENTION] can you re-up please? Or I can just re-compile later...
[Nexus 5 Android Development] Phil3759:
wired

recompiling now...
[Nexus 5 Android Development] Phil3759:
update 6.19.7 :cyclops:
[Nexus 5 Android Development] danarama:
It's the same :/
[Nexus 5 Android Development] Phil3759:
wired

I am a bit stuck here :eek:

How you got it working ?

fstab:

/dev/block/platform/msm_sdcc.1/by-name/modemst1 /efs1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst2 /efs2 emmc defaults defaults

bootable/recovery/boardconfig/BoardConfig.mk

EXTRA_PARTITIONS_PATH := "efs"
[Nexus 5 Android Development] danarama:
Yeah although you may need "/efs" instead of "efs" in BoardConfig:

#Google Nexus 5 (LGE) - hammerhead
else ifeq ($(TARGET_PRODUCT), cm_hammerhead)
TARGET_COMMON_NAME := Nexus 5
TARGET_SCREEN_HEIGHT := 1920
TARGET_SCREEN_WIDTH := 1080
BRIGHTNESS_SYS_FILE := "/sys/class/leds/lcd-backlight/brightness"
EXTRA_PARTITIONS_PATH := "/efs"

Then fstab:

/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /radio emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst1 /efs1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst2 /efs2 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sdi /sdi emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/imgdata /imgdata emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst1 /efs1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst2 /efs2 emmc defaults defaults

I have uploaded in a zip incase there is formatting issue.
[Nexus 5 Android Development] Phil3759:
LoL

I wrote a code and forgot how to use it

Have to update my guide

Sure i need /efs
[Nexus 5 Android Development] Phil3759:
reuploaded 6.19.7
[Nexus 5 Android Development] fbf2201:
Efs backup is there now :thumbup:
[Nexus 5 Android Development] danarama:
Yup. Thanks [MENTION=4666971]Phil3759[/MENTION]
[Nexus 5 Android Development] ddloco:
how safe is this option I'm a person who RMA a nexus 5 already because my few was corrupted I don't wanna go through that again
[Nexus 5 Android Development] danarama:
Define "safe"?

It backs up and restores efs.
[Nexus 5 Android Development] ApriliaM3:
Thread cleaned... back on topic thanks guys.
[Nexus 5 Android Development] Jason78729:
Just installed this recovery and I'm very impressed. Great work and no issues with custom backup or any other features I've tried so far. Thanks