yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] Phil3759:
Ah, I missed the error message you mentioned

Actually, this happens if your rom doesn't have this file:

/system/bin/time_daemon

or none of these 2: (if one of the below is present, it is ok)

/data/time
/data/system/time

It seems liek your ROM doesn't need time daemon!

Just do not set any time daemon option in that case
[Nexus 5 Android Development] Jax Teller:
I unchecked Qualcomm time daemon, rebooted to ROM, then rebooted back to recovery.

Time and date was right and no message appeared.:good:

---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------

[MENTION=2872010]rootSU[/MENTION] Does this mean that the next version will be AOSP based?:confused:
[Nexus 5 Android Development] danarama:
Yeah. I don't quote understand the particulars. It will still be built with cm parts but [MENTION=4666971]Phil3759[/MENTION] is fed up with muppets pushing changes to cwm source which he has to keep fixing and working around.. So he rebases the cwm part to AOSP.

I have NO IDEA what the repo will look like.
[Nexus 5 Android Development] sherlock5545:
Today I booted into recovery to flash a few things. Strangely it did not ask me for the passkey. I then proceeded to reset the passkey again. Rebooted, still the same. Does wiping the system have anything to do with it? I suppose not.
[Nexus 5 Android Development] Wakamatsu:
Deleting the file /system/.recovery_key.lok would leave you without a passkey. Flashing a ROM or wiping /system would do that.
[Nexus 5 Android Development] danarama:
Yes. Its all covered on page1
[Nexus 5 Android Development] sherlock5545:
Ah thanks, missed it. I apologise.
[Nexus 5 Android Development] danarama:
No probs

Can replace with flashable zip or Tasker to mv from backup on sdcard
[Nexus 5 Android Development] vobiscum:
Guys is possible change folder for GUI settings?

Now file ini is

/data/philz-touch/philz-touch_6.ini

Change in

/sdcard/clockworkmod/philz-touch_6.ini

Nandroid backup includes this.. if change GUI and restore old nandroid backup lose last configuration..

Many thanks..
[Nexus 5 Android Development] danarama:
Its backed up to sdcard

Just delete it if you're restoring old nandroid backups
[Nexus 5 Android Development] vobiscum:
Sorry man but not understand..

If change GUI settings, and check auto restore settings.. each reboot i have my GUI then made nandroid backup. After two days i change all GUI settings and i forgot to save new setting on sdcard for problem with kernel flash i restore nandroid backup in this case i lose my gui.

I ask this because if change folder for GUI on sdcard any changes on data/system/boot not modify recovery settings.
[Nexus 5 Android Development] danarama:
Why are you restoring a FULL nandroi d backup to change kernel?

Either reflash kernel or custom restore boot only.

In any case, all philz settings are backed up to sdcard. If you restore an old nandroid and restore an old settings file in data, simply delete it. The recovery will automatic ally find the backup file and apply the settings.
[Nexus 5 Android Development] vobiscum:
Ok wrong example.. [emoji12],also some kernel add some files on different folders and with restore only boot not delete they.

this backup is automatic each changes?
[Nexus 5 Android Development] danarama:
Yes
[Nexus 5 Android Development] x111:
came back on

"[RECOVERY][hammerhead] TWRP 2.7.1.1 touch recovery"

cause on

"hilZ Touch - 6.47.4 : Recovery LOCK"

flashing Slimrom it's like a hell and all the time some strange bags after installing.

And I'm not going to make full wipe before flashing (I'm not a masochist).

On TWRP, dirty flashing works just fine, no issues at all so far.

damn, so disappointed that I can't use this recovery in my Nexus 5 with Slimrom :(

very nice, ok bro I try do not come back,

do you wanna I will remove my experience about this recovery ?
[Nexus 5 Android Development] danarama:
Don't come in this thread and talk sh*t!

Its people like you who ruin XDA

For what its worth, I flash slim regularly using this recovery. The slim development team recommend THIS recovery. The only problem here is you!
[Nexus 5 Android Development] danarama:
I didn't say don't come back. I said don't talk sh*t

Delete your post if you want. Your terrible post will be immortalised forever in my quote.
[Nexus 5 Android Development] ROBSONMEG:
rootsu hi willl this work on ,y uk note 2 n7100 i already have philz 6.46.3 n7100 intsalled but i have not been able to find out if it is philz latest build and i would very much like the lastest build. and urs look great. many thnaks rob uk
[Nexus 5 Android Development] danarama:
No. Each recovery version is device specific
[Nexus 5 Android Development] Haidary.T:
Hey! I am having issues with time that I did not get before. Basically I load time daemon, turn on Day Light Saving Time and set the time zone to UTC -5 but it still puts me an hour back compared to the actual time. This did not happen on previous versions.

Edit: Had to reboot recovery to show the right time...Guess it's a problem of refreshing the time that's in the last version?
[Nexus 5 Android Development] danarama:
Daylight saving has never really worked properly on the Nexus 5. Just set your time zone and change your timezone by 1 when DST is in effect
[Nexus 5 Android Development] Haidary.T:
Is it possible that the ROM affects time in recovery? Every time I reboot recovery the time settings doesn't stick (when you set the time manually). I'm thinking this because the qualcom time daemon doesn't affect the time at all. Literally nothing changes when I enable it.
[Nexus 5 Android Development] danarama:
Use time daemon.
[Nexus 5 Android Development] Haidary.T:
I edited my post.
[Nexus 5 Android Development] danarama:
If you've started messing with manual settings when time daemon is on, no idea what happens. Not all roms use time daemon properly so I can't help.

Best setting is not use manual settings. Use daemon.
[Nexus 5 Android Development] Haidary.T:
I reset all recovery settings, rebooted recovery and only turned on qualcom time daemon. Still no effect. I guess it's broken in Chad's Velocity Rom :/
[Nexus 5 Android Development] danarama:
If its not working, your date and time says the year is 1970, yes?
[Nexus 5 Android Development] Haidary.T:
Correct.
[Nexus 5 Android Development] danarama:
Please set to time daemon, boot ROM. Reboot recovery. Confirm time is 1970, then reboot and upload /cache/recovery/last_log.txt
[Nexus 5 Android Development] Haidary.T:
There are multiple last_log (last_log.1, last_log.2) I guess I'll upload the one with no number since it seems it is the most recent one.
[Nexus 5 Android Development] danarama:
Looks like a ROM issue.
[Nexus 5 Android Development] bariz143:
How to get rid of this "0" folder. Never seen this before. When opening that folder i see clockworkmod folder. But i have always had my clockworkmod folder in root of SD and still have it there. Now i got 2 suddenly. Just saw this today when coming from Android L back to 4.4.4.
[Nexus 5 Android Development] danarama:
Ensure sdcard in recovery is set to data/media/0

If it already is, your question doesn't belong here. L messes with your sdcard. Its your responsibility to understand what its done and how to recover. Top tip - read the android L thread
[Nexus 5 Android Development] bariz143:
I fixed it. Flashed Android L again and reflashed recovery and it dissapeared. Thx
[Nexus 5 Android Development] adrman:
[MENTION=2872010]rootSU[/MENTION] The rom I'm currently running, Simple AOSP, has a OTA update utility via Open Delta. Supposedly, it only works with TWRP. Being curious, I decided to try it with PhilZ. The OTA update was successful, but I noticed a "installation aborted" fly by while the script was running. I took a look at the log file (attached). It seems as if Simple AOSP and SuperSU installed properly, but then two other installations for /emmc/OpenDelta/SimpleAOSP-4.zip and /emmc/OpenDelta/FlashAfterUpdate/UPDATE-SuperSU-v2.02.zip aborted. I'm assuming it's because it was emmc related, but I was just trying to understand what the script was attempting to do a little better. Any chance you could shed some light on it? Thanks.
[Nexus 5 Android Development] danarama:
It runs 4 commands. 2 for each install

-- Installing: /sdcard/OpenDelta/SimpleAOSP-4.zip

-- Installing: /emmc/OpenDelta/SimpleAOSP-4.zip

-- Installing: /sdcard/OpenDelta/FlashAfterUpdate/ UPDATE-SuperSU-v2.02.zip

-- Installing: /emmc/OpenDelta/FlashAfterUpdate/UPDATE-SuperSU-v2.02.zip

The file names are the same. The only difference is the location of the files. /sdcard exists. /emmc does not. Looks like whomever created the script tried to cover multiple bases but not sure why anyone would use /emmc as a mount point, on the n5 at least.

It wouldn't work on cwm though, no. Its just a developer oversight saying it only works on twrp. He is not acknowledging the existence of philz. What would be more accurate would be to say it doesn't work in cwm. ...and the reason for that is from 4.2 onwards, /sdcard is /data/media/0 so anything you download is in that path but cwm lazily uses /data/media as /sdcard so the file won't be found.

Hope this helps.
[Nexus 5 Android Development] adrman:
It did. Thanks for the explanation and clarification!
[Nexus 5 Android Development] danarama:
No problem
[Nexus 5 Android Development] aheeejd:
Wow, just a heads up for people who don't pay close (close) attention. I just got done typing a big long story here, as i was typing & looking at other threads i was in this morning, i found my mistake. I dl'd purity + rom, they i went to the code blue kernel thread, well, nit paying close enough attention i went into the wrong kernel thread for the L preview kernel, & i dl'd it & flashed. Wouldn't boot. So i thought maybe purity is caf, so back to recovery, wiped, flashed rom, caulkins non caf zip, then the kernel, wouldn't boot. Back to recovery, wiped, went to flash & now have the 0 folder, now in the rom of course i open rom toolbox pro file manager & sure enough, i open sdcard, & there's the new 0. Totally my mistake obviously, but how might i get it back, am i going to have to flash L preview rom, reflash recovery like the guy i quoted said he did. And/or, if i don't mind the way it is now, can i just keep it the way it is. I already fixed location of my TB stuff. Moved my color profiles. Any info appreciated.

Sent from my Nexus 5 using Xparent Green Tapatalk 2
[Nexus 5 Android Development] danarama:
It is not Philz recovery related. Please ask in the L Q&A Thread here: http://xdaforums.com/google-nexus-5/help/android-l-developer-preview-help-t2796217
[Nexus 5 Android Development] aheeejd:
Ok, sorry about that, I looked in here, & saw that guys post, & just threw my reply out there cause I was like hey, I got that issue, but thank you for the link good sir
[Nexus 5 Android Development] tsubus:
do you use stock CM11 device trees for this?
[Nexus 5 Android Development] danarama:
Yes, but not CM11 kernel.
[Nexus 5 Android Development] danarama:
Changes between 6.57.5 and 6.50.2

Fixes

-Potential failure to reboot

-Potential failure of TWRP backups

-Regression bug in Advanced menu

-Crash by calling ui_print or LOGE on early recovery init

-Wake-up screen could fail or take a few seconds to reset brightness

-Memory overflow potential issue

Visual

-Group all wipe otions under a same men

-Enhance menu titles

-Keep only mount and storage options in the corresponding menu

-Enhance highlight of virtual keys

-Tweak default recovery keys

-Don't show mount usb storage menu when it is not available

-Always show text in sideload mode

New

-enable screen capture through adb shell

-option to disable md5 from edify restore_rom command line

-support wipe_cache and clear_display edify script commands

Improvements and updates

-SuperSU 2.02

-use built in busybox tar instead of libtar

-drop fb2png binary support

-restore custom rom: preserve selinux attributes

-do not wipe /data/media on wipe_data recovery start command

-do not show mount/unmount /sdcard on /data/media devices …

-support more moint points for /data/media detection

-enhance code to toggle /data/media multi user support

-enhance code to mount auto file system

-do not double confirm formatting /data/media during ext4 <-> f2fs con

-optimize memory resources

-never confirm wipe in ors scripts

-mounts: match aosp sources
[Nexus 5 Android Development] Unb0rn:
Hey, [MENTION=2872010]rootSU[/MENTION], it looks like there is a bug in latest (6.57.5) recovery. I am unable to use "Install using Free Browse Mode"-any ZIP I select fails to install with "no such file or directory" error. Installing from /sdcard works fine. I've tried to re-setup free browsing mode-it had no effect.
[Nexus 5 Android Development] danarama:
Thanks for the report. I can confirm this issue, Latest commits don't seem to address either. [MENTION=4666971]Phil3759[/MENTION]
[Nexus 5 Android Development] Haidary.T:
Why is it that after an installation sometimes the "unmounting system" part takes a while and other times it's instantaneous even if it's the same zip file?
[Nexus 5 Android Development] danarama:
On the exact same zip file every time?
[Nexus 5 Android Development] Haidary.T:
It's pretty random. For example when I clean flash I go in this order: ROM, Dankoman's bootanimation, Gapps and then SuperSU. Sometimes SuperSU installs in a flash but other times it gets stuck on "unmounting /system and /data". This is not a SuperSU problem since it happens with Gapps and bootanimation quite often too.

---------- Post added at 02:11 PM ---------- Previous post was at 02:09 PM ----------

I shouldn't say "stuck" since it does complete the installation but only after like 5 seconds. It's odd.
[Nexus 5 Android Development] danarama:
I flash multiple zips at once but have never witnessed this issue.

Have you checked the update-scripts? What it says on the screen is not always what is happening so it may be something else randomly taking time.
[Nexus 5 Android Development] Haidary.T:
Most likely a non issue and just my OCD doing it's thing.
[Nexus 5 Android Development] Phil3759:
fixed in 6.57.9:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/0f529ecd0ef74ae69f422b5672c79bbb4fea4f60
[Nexus 5 Android Development] danarama:
Many thanks.for this..

I'll build tomorrow... Nearly bed time now
[Nexus 5 Android Development] danarama:
Changes between 6.57.9 and 6.57.5

Fixes

-Fix Free Browse mode

Thanks to [MENTION=4666971]Phil3759[/MENTION]
[Nexus 5 Android Development] fatspirit:
Display turns off even if corresponding option is turned off. 57.5/57.9
[Nexus 5 Android Development] danarama:
Are you sure? Did you disable dim screen delay also?

Dim goes black too. But digitiser still is active. Can you please do more thorough testing to let us know which it is and after how long it goes off, whether it is off or dim....
[Nexus 5 Android Development] fatspirit:
Dim option turns screen off (tested in the dark environment), Off option doesn't work at all - dim option was disabled during that test. Screen turns off according to the dim timer, digitizer works, but I don't know, how exactly should I wake phone up - chaotic mode was used.
[Nexus 5 Android Development] danarama:
[MENTION=4666971]Phil3759[/MENTION] - are you familiar with this behaviour?
[Nexus 5 Android Development] Phil3759:
I never heard about this. Some kernels have issues with off mode and brightness level. However, if disabled in settings they will never enter in action magically
[Nexus 5 Android Development] danarama:
I'll do some testing with older versions to see if I can identify when it started.
[Nexus 5 Android Development] Basche:
I had the same issue, but when I pressed the volume up or down button the screen came back on as nothing happened. This has a occurred when doing a backup. I'm using opticharged purity with code blue kernel and on ART
[Nexus 5 Android Development] albuntu:
Guys? Need some help. I've encrypted my device yesterday. Today i wanted to flash a zip but the recovery is not able to decrypt the partitions. Does this work with Philz recovery?

Sent from my Nexus 5 with Tapatalk
[Nexus 5 Android Development] danarama:
Philz recovery can't decrypt your files. If it could, encryption would be pretty pointless
[Nexus 5 Android Development] albuntu:
That means I need to switch to TWRP? Or can I somehow sideload my zip-files?

Sent from my Nexus 5 with Tapatalk
[Nexus 5 Android Development] danarama:
Yes you can either sideload or switch to TWRP. Or decrypt.
[Nexus 5 Android Development] Unb0rn:
In fact, it would be really cool feature (anyway, you should know password to decrypt anything even in TWRP), and MTP porting from TWRP would be awesome too ;) I've tried to put forward this idea in main thread, but never received any answer )
[Nexus 5 Android Development] danarama:
There are no new features being added. The CWM platform is currently dead. We may get some bug fixes here and there, but please don't expect anything.
[Nexus 5 Android Development] adrman:
Wow. Just took a look at the main thread after quite some time. That's too bad, but given the amount of work, certainly understandable from Philz' perspective. Thanks for all of your work on hammerhead.
[Nexus 5 Android Development] Волк:
Wait, what? Does that mean that there will never be another Philz ever? Or do you plan to start...from scratch?
[Nexus 5 Android Development] danarama:
All I do is compile philz code. Phil was about to start work porting recovery onto an AOSP base instead of cwm base but teal life is taking over. Maybe someone else can take over that or maybe in future, Phil comes back but right now - now new features maybe bug fixes
[Nexus 5 Android Development] reddvilzz:
Is there an option to format partition from f2fs back to ext4 in philz? Because it seems I can't find it anywhere :(
[Nexus 5 Android Development] danarama:
Yes, it's in exactly the same place as you migrate to f2fs
[Nexus 5 Android Development] reddvilzz:
Is the steps are the same as going from ext4 to f2fs?
[Nexus 5 Android Development] schyzo001:
Hi all,

I have the N5 with L preview, so back to the stock recovery.

I wanted to flash with philz_touch_6.57.9-hammerhead.zip, but the stock recovery does not have a flash feature.

I tried to use adb sideload, but the answer is "signature verification failed"

Do you know how I can proceed ?

Thanks for your help.
[Nexus 5 Android Development] danarama:
Flash it using Fastboot as per the usual way.

...Or if you're rooted you can use flashify.

In both instances, you'll need to flash the .img file from within the zip
[Nexus 5 Android Development] danarama:
I've fixed the screen dim = black issue, but I can't upload to Dev host for some reason.

I'll keep trying.
[Nexus 5 Android Development] efan3719:
Dev host is giving me problems too. Haven't been able to upload anything all day. Not sure what's going on.
[Nexus 5 Android Development] fatspirit:
Is it ok today?
[Nexus 5 Android Development] danarama:
I'm at work.
[Nexus 5 Android Development] danarama:
OK took an age but re-uploaded files are there.

They have the same file name, so download the ones with the October date

http://d-h.st/users/rootsu/?fld_id=34576#files
[Nexus 5 Android Development] kronflux:
just out of curiosity, what's the benefit to using your build over say, my own build which I've just compiled?

and by that, I mean, I seem to recall something about you using a different kernel than CM "Stock" kernel?(if so, which kernel are you using?)

are there any other tweaks you've made to your sources that would differ from a "vanilla" compile of PhilZ Touch with latest CM sources?
[Nexus 5 Android Development] danarama:
There's no benefit except my build is official oh and I use a prebuilt f2fs kernel.

The only tweaks I've made are to the device tree, which you can learn from the Philz development thread.
[Nexus 5 Android Development] kronflux:
thanks for replying! Yeah, I think I may look into f2fs and see what sort of benefits it provides. Maybe I'll end up recompiling with another one.

I just figure where development has come to a hault on both CWM and PhilZ, that I'd compile a "final" build for my own use. so far on stock kernel it works great, so I may not even bother with a recompile. *shrug* we'll see how lazy I am :)
[Nexus 5 Android Development] danarama:
Well you can however, of course, this here is already a final build :p
[Nexus 5 Android Development] Notorious:
Hello i just bought a nexus 5 and it just came in today and i plan on using Philz since ive had it on previous devices. I was looking through the general threads and see that corrupt partitions is a common thing on this device. I believe i saw they become corrupt when wiping in recovery? Would using " use rm- rf instead of formating" help in anyway to avoid possible corruption of the data partition or any in general? I bought this used on swappa so cant do warranty ect so just want to make sure i avoid the corruption issue :). Any information would be appreciated
[Nexus 5 Android Development] danarama:
Its actually quite uncommon. The most common is cache and usually that's because with stock it takes an age, people panic and pull power half way through.

Philz uses rm -Rf anyway. As much as people like to think it, there's not a lot of use wiping cache anyway. And its an easy fix.
[Nexus 5 Android Development] danarama:
Development on this recovery has ceased. If you have any problems, please move to TWRP.

All the best to [MENTION=4666971]Phil3759[/MENTION] for all his hard work bringing this to us. Please join me in wishing him the best in his future endeavours by thanking this post; http://xdaforums.com/showpost.php?p=56388388&postcount=5700
[Nexus 5 Android Development] wedgess:
Thread closed @ the OPs request ^^
[Nexus 5 Android Development] Echse27:
Thank you Phil3759...

AromaFM works fine in Version 1.91..... great work ....

It´s a really great tool to rescue data when system is buggy or bricked.....

Greetz... Echse...

P.S. Screenshots are not really important but it would be a useable "nice to have"...
[Nexus 5 Android Development] Phil3759:
Very interesting in fact :good:

However, you still rely on specific kernel patches...

For me, the effort to port all sources to CWM is limited as only a little devices / devs probably implemented it

My time is sadly very limited
[Nexus 5 Android Development] Baphometa:
That is very sad news indeed. Any chance you could offer to the dev of multirom what he would need to implement the features into your recovery? I don't mean to be pushy but I am sure I'm not the only one who doesn't want to choose between their favorite recovery and the very thing my flash addiction needs. :)

Thanks either way for making the best damn recovery I've used on every phone it's been released for since the good old g1 :)
[Nexus 5 Android Development] Phil3759:
You can ask tassadar

Since he coded it for TWRP, he knows well the sources to port to CWM if he wishes AND have time

For CWM, it would be easier if all the coding was C and not c++

I really have no time to follow those sources and port them. I can help though in merging to CWM if author wants
[Nexus 5 Android Development] Baphometa:
Thanks I'll message him see if that is something he would be interested in
[Nexus 5 Android Development] danarama:
Edit > that's twice now tapatalk posted in the wrong thread for me :/
[Nexus 5 Android Development] Phil3759:
For further feedback on this, please post in main dev thread

Multi boot was always something interesting me, however, I was each time distracted by other stuff...

I would rather look at a simpler less intrusive way, recovery wise, giving kernel devs more freedom
[Nexus 5 Android Development] airbat:
Hey, first jour recovery is awesome ;)

But, yes there is always a but ^^ , i have the date/time issue as everybody. How can we solve this issue ? It is really anoying ...

Thx in advance.
[Nexus 5 Android Development] danarama:
Please read this thread. Answered already

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit