yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] danarama:
This recovery works fine so if a user has an issue, I'd rather had tried to fix it.
[Nexus 5 Android Development] prabs99:
Cannot restore backup

I keep getting an error when trying to restore a backup. I have the latest version of the recovery. I am attaching logs. The error occurs during restoration of data. Here is part of the log

Restoring data...

I:Formatting unknown device.

rm: can't remove '.' or '..'

rm: can't remove '.' or '..'

I:setting up /data/media(/0) for /sdcard/clockworkmod/backup/2014-06-07.16.48.26_11-20140526-NIGHTLY-hammerhead/data.ext4.tar.gz.

I:using /data/media for /sdcard

I:setting up /data/media(/0) for /sdcard/clockworkmod/backup/2014-06-07.16.48.26_11-20140526-NIGHTLY-hammerhead/data.ext4.tar.gz.a.

I:using /data/media for /sdcard

I:setting up /data/media(/0) for /sdcard/clockworkmod/backup/2014-06-07.16.48.26_11-20140526-NIGHTLY-hammerhead/data.ext4.tar.gz.b.

I:using /data/media for /sdcard

I:setting up /data/media(/0) for /sdcard/clockworkmod/backup/2014-06-07.16.48.26_11-20140526-NIGHTLY-hammerhead/data.ext4.tar.gz.c.

I:using /data/media for /sdcard

I:setting up /data/media(/0) for /sdcard/clockworkmod/backup/2014-06-07.16.48.26_11-20140526-NIGHTLY-hammerhead/data.ext4.tar.gz.d.

I:using /data/media for /sdcard

Press Back to cancel.

tar_extract_all(): Invalid argument

Error while restoring /data!

press any key to continue.
[Nexus 5 Android Development] danarama:
Nothing jumps out at me here. Perhaps [MENTION=4666971]Phil3759[/MENTION] can provide some insight.
[Nexus 5 Android Development] Koopa777:
Attempts are being made to bring F2FS to the manta, but there are some complications.

http://xdaforums.com/showthread.php?t=2015874&page=458

The fstab in the custom TWRP is failing to mount an f2fs partition, it doesn't work like in PhilZ. How exactly did you get the f2fs to mount properly?

The other topic is the process of bringing PhilZ 6.43.6 with F2FS compatability to the manta (Current version is 6.41.6). Are all necessary components on Phil's GitHub? Thanks!
[Nexus 5 Android Development] danarama:
Probably a question best placed in the development thread.
[Nexus 5 Android Development] bradm23:
Does anyone have a .zip of the 4.4.2 recovery that I can flash so I can accept the ota update to 4.4.3. Thanks!
[Nexus 5 Android Development] danarama:
You don't need it. Read the ota. Help desk thread on general.
[Nexus 5 Android Development] fatspirit:
OTA doesn't care about recovery you have. System files - the only thing that matters. Actually, OTA will overwrite your current recovery with the stock one (:
[Nexus 5 Android Development] danarama:
Which makes it a pointless endeavour. May aswell flash the rooted stock rom in full via recovery and be done with it ;) Its actually a quicker process
[Nexus 5 Android Development] morrigan91:
Hi guys...

Philz recovery is compatible with ORS ( Script open source recovery).. but when update ROM with Carbon Delta appear this error. (Photo)

After flash and reboot all work fine.

Is impossible to take log on recovery because script update is very fast and after get reboot.

Only for info is a script error or recovery error?

Post on Carbon Community

Carbon Delta INFO

Many thanks for support and reply
[Nexus 5 Android Development] danarama:
Its trying to mount /emmc - what does it think that is?

Logs are in /cache/recovery after a reboot.

Please delete your logs in /cache/recovery, then reflash and upload the new logs. put .txt on the end of the file names please
[Nexus 5 Android Development] morrigan91:
ok found LOG.
[Nexus 5 Android Development] fbf2201:
Or flash OTA zip through recovery - then flash custom recovery and SuperSU again (before reboot).

Like this you'll keep all your data and settings.
[Nexus 5 Android Development] danarama:
Well actually that is more steps.

Flash rooted stock zip = Boot recovery, flash zip

Flash OTA zip = Boot recovery, flash zip, flash recovery, flash superSU

Both methods keep /data intact. So why even bother with pesky OTA zips in the first place? Seems like a fools errand to me
[Nexus 5 Android Development] fbf2201:
I just got you wrong. With your "...flash the rooted stock rom in full...", I somehow had the factory image in mind (read over the "rooted").

nevermind...
[Nexus 5 Android Development] Koopa777:
For what it's worth, that always appeared for me, yet it always worked fine.
[Nexus 5 Android Development] Trel:
I'm curious, does this recovery have any benefits over TWRP if that's what I'm currently using, or are they similar enough that this is just a matter of preference?
[Nexus 5 Android Development] danarama:
Benefits are a matter of preference. At XDA, it's frowned upon to compare the work of different developers so try it and see. Features are listed in the OPs
[Nexus 5 Android Development] Trel:
I was more interested on what the difference in features might be. I have used both and other than layout I didn't see anything really different, which is why I was asking.
[Nexus 5 Android Development] danarama:
I don't know what features TWRP has.
[Nexus 5 Android Development] fatspirit:
TWRP has no incremental backup mode, for example.
[Nexus 5 Android Development] Trel:
That's a pretty nice feature, I could probably save a fair bit of space with that. Though I don't see that listed on the features for this either. Is it an undocumented one or is there a larger feature list somewhere other than the OP post?
[Nexus 5 Android Development] Phil3759:
It is a stock CWM feature since one or two years. I only list additional features over CWM

You have to set the dup backup format instead of tar/tar.gz
[Nexus 5 Android Development] CataHd:
Not sure if this is the right place place o ask but i have an issue with the recovery,it keeps telling me to update to latest binary and i think this is the problem that keeps me from using the ota updater in paranoid android,it doesn't let me to update the rom from the app in recovery!

Can someone help me?

Sorry if i asked in the wrong place!
[Nexus 5 Android Development] danarama:
Right place to ask.

That message appears to inform you that the binary in the zip you're flashing is outdated. It still flashes the contents.
[Nexus 5 Android Development] CataHd:
It never flashed :( keeps giving me installation aborted even in in stock CWM
[Nexus 5 Android Development] danarama:
Must be a problem with what you're flashing... That's not because of an outdated binary.

What are you trying to do?
[Nexus 5 Android Development] CataHd:
Now I'm on paranoid android and i want to update the rom with their ota updater and when it goes into recovery it doese the whiepes that need to be done automatically but when it comes to the update part it gives me instalation aborted :(

Maybe this log can help?
[Nexus 5 Android Development] danarama:
Yeah I can see the problem.

-- Installing: /sdcard/0/paranoidota/pa_gapps-stock-4.4.3-20140615-signed.zip
Finding update package...
I:Update location: /data/media/0/0/paranoidota/pa_gapps-stock-4.4.3-20140615-signed.zip
Opening update package...
E:Can't open /data/media/0/0/paranoidota/pa_gapps-stock-4.4.3-20140615-signed.zip
(No such file or directory)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/0/paranoidota/pa_gapps-stock-4.4.3-20140615-signed.zip")
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard

/sdcard on our device is /data/media/0 but in CWM in is /data/media

The updater is looking for /sdcard being /data/media (as hardcoded in CWM) so instead of looking for /sdcard/x, its looking for /sdcard/0/x or /data/media/0/0/x - which is a crappy manual work around (I believe CM delta does this too).

You could temporarily toggle sdcard to /data/media in Philz settings.

As to why it wont work in CWM I really dont know.
[Nexus 5 Android Development] Trel:
Ah ok, I'll have to bring up both feature lists (yours and CWM's) to see the full list, thanks :)
[Nexus 5 Android Development] Sc4ryB3ar:
Is there any difference between the ramdisk of 4.4.3 and 4.4.4?
[Nexus 5 Android Development] danarama:
No idea.
[Nexus 5 Android Development] danarama:
Changes between 6.47.3 and 6.43.6

See recommendations at the bottom of the 3rd post for details on recovery lock...

- add recovery lock with passkey on start (secure your data from recovery intruders)

- fix segfault during shell nandroid backup/restore commands

- enable progress display during "adb shell nandroid backup/restore" commands

- enhance and fix bugs of progress display during install/nandroid... operations

- nandroid restore: fix progress bar animation when md5 verify is enabled

- nandroid md5: fix progress bar was not reset for each file

- nandroid md5: fix .android_secure md5 sum was never generated or checked

this could cause md5 check to fail under some circumstances

- limit logging to console in adb shell nandroid and mount commands

- fix detection of real fstype (pointer to in the scope char array bug)

- disable useless sd-ext warnings and errors
[Nexus 5 Android Development] Phil3759:
You are doing an Amazing work [emoji106]
[Nexus 5 Android Development] danarama:
Me??

I didn't do anything :( just test.

Hey, could you please upload latest version to goo please ?

http://d-h.st/users/rootsu/?fld_id=34576#files
[Nexus 5 Android Development] kufikugel:
Passkey...great addition...we just talked about it some time ago :)
[Nexus 5 Android Development] danarama:
Yeah it's great. I've been wanting this for some time. The implementation by [MENTION=4666971]Phil3759[/MENTION] is much better than what I had imagined.
[Nexus 5 Android Development] sherlock5545:
So the passkey is a pattern of six taps on the navbar keys, right? I just set up one. Really a great addition. How secure is it, though? I've got the boot loader locked using Boot Unlock.

Sent from my Nexus 5
[Nexus 5 Android Development] danarama:
Navkeys if you use them but also hardware buttons.

It's very secure. No GUI, no OTG no adb.
[Nexus 5 Android Development] FunDionysus:
Unable to install fresh version of recovery

Just updated N5 from 443 with 444 OTA (via link in OP). I flashed the OTA via custom recovery (PhilzTouch6 6.15.4 custom recovery (CWM 6.0.4.7). On reboot Android launched normally, Settings > About Phone reports Android v. 4.4.4, and apps appear to behave (limited testing)

However, from the bootloader menu (which shows fastboot mode; secure boot -enabled; lock state -unlocked) when I choose Recovery Mode, observe a small android icon (lying on its back) with red triangle with exclamation mark. So it appears the OTA update somehow killed my custom recovery install. Reading the OP I did not see that this would be an issue (scenario B).

So just downloaded updated PhilzZ from link on OP of this thread.

philz_touch_6.47.3-hammerhead.zip

(updated 6/21/14)

Following instructions here:

http://xdaforums.com/google-nexus-5/general/guide-nexus-5-how-to-unlock-bootloader-t2507905

Connected to ADB, and below is report copied from CMD window:

C:\Download>fastboot flash recovery recovery.img
sending 'recovery' (11538 KB)...
OKAY [ 0.578s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
finished. total time: 0.750s

Any ideas why the recovery it will not install?

Has anyone else yet installed this 06-21 recovery update via ADB?

---------- Post added at 07:53 PM ---------- Previous post was at 07:00 PM ----------

FYI re-attempt to install failed again

However, successfully installed latest TWRP

C:\Download>fastboot flash recovery openrecovery-twrp-2.7.1.1-hammerhead.img

sending 'recovery' (13586 KB)...

OKAY [ 0.641s]

writing 'recovery'...

OKAY [ 1.125s]

finished. total time: 1.766s

---------- Post added at 08:01 PM ---------- Previous post was at 07:53 PM ----------

OK, it was pointed out to me the PhilZ update was a zip and not an image file. Thus my issue. :silly:

So now, with TWRP installed, I can install Philz Touch and test out. Thanks!
[Nexus 5 Android Development] fatspirit:
There was a much simplier and even pc free method (:

1. boot into recovery

2. Install OTA

3. Install supersu (right after the 2)

4. reboot

5. install supersu from play

6. install flashify from play

7. install PhilZ

8. reboot

9. profit
[Nexus 5 Android Development] Koopa777:
ADB was not working in recovery on 47.3, Windows wouldn't even see the device, even though it showed in the ROM and Fastboot. 43.6 works when I flash it.
[Nexus 5 Android Development] FunDionysus:
Downloading apps from PlayStore (or manual Playstore app updates) via my cell data connection is not working (I posted issue in a general help thread). Thus was not able to download superSU from PlayStore. (I just discovered a previous zip version on the PC which I could have used).

Thanks for the hint about Flashify. Once I get the issue with PlayStore back working will give it a whirl.

---------- Post added at 09:27 PM ---------- Previous post was at 09:15 PM ----------

After launching the latest PhilZ, running adb devices on the PC does not appear see the N5. Does that mean I cannot do a sideload with PhilzTouch ?

Nevermind: In PhilZTouch, Install Zip > Install from Sideload

gets the process working.
[Nexus 5 Android Development] danarama:
There will be a fix soon. For some reason if you haven't got a passkey , adb is disabled.
[Nexus 5 Android Development] danarama:
Fix uploaded.
[Nexus 5 Android Development] gialakias:
One question. Does it have the cwm recovery flash recovery disable after ota?
[Nexus 5 Android Development] fatspirit:
:confused:
[Nexus 5 Android Development] gialakias:
Well, let be clear it up. When I ota update with cwm recovery, it asks when I reboot that I am gonna lose my custom recovery and if I want to disable the original recovery flash. Is it present in this recovery?
[Nexus 5 Android Development] vin4yak:
If you're asking whether the OTA update will remove the custom recovery, then the answer is YES. You just need to re-flash Philz once again.
[Nexus 5 Android Development] gialakias:
Well I know everything about that. I am asking a different question if you can understand. If you had cwm recovery you would have seen it.
[Nexus 5 Android Development] fatspirit:
No questions asked. I clearly understand what you have meant.
[Nexus 5 Android Development] sherlock5545:
So does ADB only work if I'm on recovery now? I mean, if I have the passkey on, do I have to tap it in before using ADB?

Sent from my Nexus 5
[Nexus 5 Android Development] fatspirit:
That's exactly how recovery lock should work.
[Nexus 5 Android Development] sherlock5545:
Yeah I know, that's why I was asking. Thanks ;)

Sent from my Nexus 5
[Nexus 5 Android Development] danarama:
CWM recovery detects install-recovery.sh as a means to overwriting recovery and asks if you want to remove it.

Obviously on the nexus 5, this same script is often used to grant root at boot so we would not wish to remove it as root wouldn't work. We also would not wish to be informed every time we enter recovery, so yes - this can be disabled.

Yes. Previous bug was no adb unless you have and enter passkey so those who didn't set, couldn't use adb at all
[Nexus 5 Android Development] gialakias:
Thanks for the answer. I am using this feature in every ota, that is why I am asking. I full unroot, then I apply the ota, so then I preserve the recovery and I don't need a pc to return to root-stock with custom recovery. I know I can flash superSU after ota and have root BUT, the 4.3 ota in nexus 4 had 2 reboots when it was applied so if you flashed superSU in the middle it was causing a bootloop. So your answer if I understand right is that this feature exists in Philz's if I don't have root?
[Nexus 5 Android Development] danarama:
Basically if you set "verify root on exit" it will look for install-recovery.sh and if there is no root command within it, will ask you if you want to disable recovery flash. It will then ask you if you want to root the ROM too.
[Nexus 5 Android Development] danarama:
Oh by the way everyone [MENTION=4708115]sherlock5545[/MENTION] - the passkey is only supposed to be hardware buttons. Navbar at boot will be removed in next version due to double key entries.

Please re-do your passkey with hardware button's only (vol up, down and power)
[Nexus 5 Android Development] sherlock5545:
Thanks will do so immediately. By the way, just being paranoid, but what happens if one of the hardware key fails. Does the recovery become inaccessible?

Sent from my Nexus 5
[Nexus 5 Android Development] danarama:
Boot into android and delete the passkey file.

If you also cannot boot into android , you'd need to unlock your bootloader so keep your stuff backed up.
[Nexus 5 Android Development] Haidary.T:
Is it possible to remove the big vibration after a backup is done? Turning off vibrator in GUI settings doesn't seem to help.
[Nexus 5 Android Development] aheeejd:
I actually find the vibration after backup/restore quite useful.

Sent from my Nexus 5 using Xparent Green Tapatalk 2
[Nexus 5 Android Development] Sc4ryB3ar:
If we toggle back to ext4, will that wipe the SD card again?
[Nexus 5 Android Development] danarama:
no there isn't

The toggle just toggles on migration ability. .. It's formatting you would need to do to actually migrate back to ext 4 and yes, formatting erases the files
[Nexus 5 Android Development] garzacorporations:
I've installed the latest recovery and restored my nandroid and now I've the folder 0 with everything inside folder. I thought that was an old recovery problem.

EDIT: Almost fixed, now I only have an 0 folder with a clockworkmod folder inside and I cannot delete them.
[Nexus 5 Android Development] danarama:
Where in relation to /data/media?
[Nexus 5 Android Development] garzacorporations:
In my root folder I've sdcard and storage that goes to the same place. Inside them I've emulated and sdcard0 that goes to the same place. Inside them I've 0 and legacy that goes to the same place. And finally inside them I've my sd folders and files and a folder 0 that cointains a folder called clockworkmod that is empty and I cannot delete it.

/storage/emulated (here is the sd root) -> 0/clockworkmod
[Nexus 5 Android Development] danarama:
What I'm asking is do you have /data/media/0 or /data/media/0/0?

Also were you on Android L at any point?
[Nexus 5 Android Development] garzacorporations:
Yes I was on L and factory restored everything including SD before restoring my nand. No, I don't have /data/media
[Nexus 5 Android Development] danarama:
You must have /data/media. It is impossible to not have it because /sdcard is mounted to /data/media/0

Before flashing L you must wipe your full /sdcard. Known issue with L. This is not related to the ancient /0/0/0/0 bug of cwm.

You'll have to mount /data in recovery and use adb to move and delete your files if they're in the wrong place. Please ask in the L q&a Sticky thread if you get stuck.. Just to reiterate, this isn't a recovery issue
[Nexus 5 Android Development] Jason78729:
Has anybody had any issues with the clone the ROM to zip feature? Mine makes the conversion but gets error when trying to make the actual zip file.
[Nexus 5 Android Development] danarama:
Whats the error? Got any logs?

Edit > my test zip was created ok. But it doesn't flash anything in /system when I flash it... It says completed on screen but log shows issue with missing boot.img.md5 and assert failed

[MENTION=4666971]Phil3759[/MENTION] - something I need to change in source?
[Nexus 5 Android Development] garzacorporations:
Yes, it's in /data/media/0 and there is the other 0 folder /data/media/0/0/clockworkmod

I've restored my phone to stock KitKat and then restored my KitKat nandroid. So its like never used L
[Nexus 5 Android Development] danarama:
You'll have to use adb to delete the additional directories

mount /data

cd /data/media/0

rm -Rf 0

Backup your sdcard first incase you typo
[Nexus 5 Android Development] Jason78729:
Please see the attached recovery log. I'm running the dev preview of Android L. Let me know if you need anything else.
[Nexus 5 Android Development] danarama:
Thanks. Just says error making zip unfortunately
[Nexus 5 Android Development] garzacorporations:
Should I do it on CWM Recovery or with the system loaded?

EDIT: Doesn't matter I did it. Thank you ^^
[Nexus 5 Android Development] onesolo:
I also faced the same problems comment above.. big mess with the 0 legacy on sdcard!!!!

I first flash the L preview with the flash-all.bat... but then I began to switch between nandoids and it completely messed my sdcard!!!

One time I was on the L preview, I went to the recovery (philz) and it simply did not find the directory where my (4.4.4) nandroid was!!! But it was there...

I had to flash the 4.4.4 factory image and then move the nandroid back to my nexus and then I was able to restore it...

I don't understand why is not possible to have on the philz recovery something that can change the backup directory...

Any ETA for a fully compatible philz of L preview version ?
[Nexus 5 Android Development] danarama:
Theres so much wrong with your post, I don't know where to start.

1) It's not a Philz issue. It's an L issue... L changes the /sdcard. It is your responsibility to wipe data and sdcard between swapping between L and official android releases

2) It is against the rules to ask for ETA

3) L is not a n official release. No one will release "L compatible recovery"

4) Stop using !!!!!!

5) if you're not going to follow the advice in the sticky threads, DON'T FLASH IT

Simple and end of conversation!
[Nexus 5 Android Development] yyz71:
Way too many quotation marks:rolleyes:
[Nexus 5 Android Development] vobiscum:
Hi guys.. there's a particular reason why with "clean to install a new rom" not wipe boot partition(kernel) and why is not present in wipe menu?

I remember in old nexus devices this option was possible.

Many thanks.
[Nexus 5 Android Development] danarama:
It's just an image. It doesn't need wiping anyway. It can just be replaced with another image... Unlike system which is unpacked into multiple directories
[Nexus 5 Android Development] vobiscum:
Thanks man, but if rom script not replaced boot image what's up? Kernel CAF with AOSP ROM or reverse ?

Only for info I would not brick my device..
[Nexus 5 Android Development] dechronic:
As rootSU said, there is no need for that but if you still want to wipe it before you flash another kernel you can boot into the bootloader and use the following command while connected to a laptop/computer.

fastboot erase boot

Note: It can only be run on an unlocked bootloader, You will only be able to boot into the bootloader or recovery after running the command.

If you have a custom recovery installed, you can always run the flashable unlocker to unlock the bootloader without wiping the data. That is why it is a good idea to use the latest Philz Recovery which allows for an access password to prevent unauthorized access to the phone data.

---------- Post added at 04:22 PM ---------- Previous post was at 04:15 PM ----------

If you have a custom recovery installed you can always sideload a different kernel if one doesn't work.

If it is a flashable zip

In Philz Touch Recovery it is under Install Zip -> Install zip from sideload

Using adb from a computer run:

adb sideload /path_to_kernel/kernel.zip

If it is an image (e.g. boot.img)

Boot into bootloader

Using fastboot from a computer run:

fastboot flash boot /path_to_boot_image/boot.img
[Nexus 5 Android Development] danarama:
All ROM.zips flash boot.img so that is not an issue.

Great thing about images is when flashed, they replace everything in the partition.. Example, factory system.img, userdata.img

The problem with ROM.zips is that /system is a directory in the zip and not an image. If the script does not firmware / delete the contents of the /system partition, its possible that some things get left over and this is the reason we have clean install option
[Nexus 5 Android Development] vobiscum:
thanks to all for the answers

another question also happens to you that after wipe cache or dalvik cache appears toggle background icon (Rom Manager logo)?
[Nexus 5 Android Development] danarama:
Yeah thats a bug. It's fixed in the latest source code but I didn't want recompile just for that.