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

To elaborate on this, backing up any NAND partition, physical or virtual, comes at no risk. All a backup is doing is "copying" files from that location to another (zip).

Restoring anything to NAND means you are overwriting crucial files so as with flashing anything,.there is always a slight risk of if what you're flashing / restoring is incomplete, a required file may no longer exist. There's nothing new about that.

If the backup is allowed to run it's course naturally, the integrity of a backup should not be questioned. Never use a backup that failed or the phone turned off during its last step etc. Just apply logic.

Now obviously each efs is unique and cannot ne generated from a backup of another phone so always keep multiple backups of your efs across multiple devices if you can (some on your phone, some on your computer. NEVER restore someone else's efs as you'll overwrite your unique data.

None of these risks are unique to philz. Efs backup implementation is very simple command line stuff. Rather, these are generic risks. Philz implementation is no riskier than any other

Do NOT restore an efs backup unless you have to. These backups exist so when all is lost and somehow your efs got screwed, you have a chance of recovery. The only reason I restored my efs was a test to check the restore function was safe for you guys.
[Nexus 5 Android Development] fbf2201:
[MENTION=2872010]rootSU[/MENTION]

Shouldn't be the thread name changed to 6.19.7 updated 2014-03-06?
[Nexus 5 Android Development] danarama:
Yes probably.
[Nexus 5 Android Development] danarama:
Compiled 6.20.6
[Nexus 5 Android Development] danarama:
Compiled and tested 6.21.2 - Just waiting for an upload to goo, hopefully this weekend.

FYI, I won't be compiling every build. I will skip builds that do not add /alter functionality to the Nexus 5 for obvious reasons.

I will only compile if we have:

New or updated Features relevant to N5

Bug Fixes

Code clean-up or libtouch_gui shouldn't affect the user experience. I don't want to keep bugging Phil to upload trivial builds to goo.im - so please don't get disheartened if not every version number from Philz master thread makes it to N5
[Nexus 5 Android Development] danarama:
Upload in place and title updated.
[Nexus 5 Android Development] amirsh77:
Hi [MENTION=2872010]rootSU[/MENTION],

There is a bug in v6.21.2 : after mounting the USB OTG flash I can explore it and select folders but when I want to flash a zip file a blank black screen appears and nothing happen and didn't appear and let to select YES option, but when I roll back to v6.20.6 everything is ok without any problem, would you please fix this, thanks. ;)
[Nexus 5 Android Development] kimnux:
+ 1

나의 Nexus 5 의 Tapatalk에서 보냄
[Nexus 5 Android Development] danarama:
My USB OTG is at home today so I can't test until tonight. I'll have a look then to confirm it.

No changes have been made in my build environment between the 2 versions so not sure what this will be. Not sure if [MENTION=4666971]Phil3759[/MENTION] has reports of this in other 6.21.2 devices

Thanks for the info guys
[Nexus 5 Android Development] aheeejd:
I had similar issue, not using USB OTG, but I would wipe, flash rom, flash gapps, flash kernel, flash supersu, then a font, then some blacked out gapps, & like 3 different times, I would go to flash supersu & the screen would go dark, like they said above, & then recovery would pop back on. And like the list of what I already flashed was gone, it was like philz rebooted itself, but it didn't. So something is up. Hope it's somewhat clear what I wrote. Back on previous & all good. Thank you.

Sent from my Nexus 5 using Xparent Red Tapatalk 2
[Nexus 5 Android Development] Phil3759:
[MENTION=2872010]rootSU[/MENTION]

If you can reproduce the bug, please compile with this file:

http://d-h.st/Fzg

Reproduce the crash and post a log

It happens on a a few devices, I have no clue why without that log

You must enable verify md5sum so that the log will be useful
[Nexus 5 Android Development] danarama:
Will do, thanks.
[Nexus 5 Android Development] danarama:
[MENTION=4666971]Phil3759[/MENTION] - I reproduced the error and recompiled with your updated advanced functions however, I turned md5 verification on and the issue didn't occur. I turned it off and it did. The log won't be much use I think but at least we know it only happens when md5 verification is off.

Anyway attached logs with and without md5 on...
[Nexus 5 Android Development] Phil3759:
Thank you for the help

I am getting a bit mad about it

On some devices it is the opposite of your finding

On i9505, I never got the issue

On i9100, it is random and hard to reproduce

I am not yet sure about the cause
[Nexus 5 Android Development] danarama:
No problem...

I'll update the thread about it. It's a strange one and only came in with last commits.

Thanks for your help.
[Nexus 5 Android Development] Phil3759:
6.21.9 sources online

Hope it fixes the bug of md5 verify/check
[Nexus 5 Android Development] danarama:
Many thanks. Will compile tonight and test in the morning.
[Nexus 5 Android Development] spevil07:
Hi, have someone tested to flash in philz over an OTG Cabel/USB Stick combination?

For me it doesn´t work!

I can see all files but when i would like to start the progress it crashes and the recovery is rebooting. :(

With twrp is it working.
[Nexus 5 Android Development] danarama:
Always read the last 2 pages of a thread and search before posting. If there is a new release, read the last 5 pages. If you do this now, maybe you'll find an answer!

Yep, does. Will zip and send to you.
[Nexus 5 Android Development] Phil3759:
No more bugs?
[Nexus 5 Android Development] danarama:
I haven't found any bugs... I can flash from USB OTG Fine. No black screen... MD5 sum is working on and off.

I've uploaded zip+md5 to dropbox, I'll pm you the link.

Or, I can give the dropbox link in this post if you'd prefer some testing from other users before upload?
[Nexus 5 Android Development] danarama:
Testers needed please.

https://dl.dropboxusercontent.com/u/20471345/Nexus 5/Philz_Recovery/6.21.9.zip

Unzip before flashing. Text USB OTG flashing with / without md5 enabled please...
[Nexus 5 Android Development] amirsh77:
I flashed it and has no problem any more, USB OTG flashing goes fine ! Just something ... should the MD5 file that you zip with recovery zip file match the MD5sum of zip file in recovery? Because the don't match... The MD5 that you upload is 31ef6b718350a3e6d0fd6e890f71f980 , but the one that 6.21.9 recovery made is 6dd08ffd29dc995ba0ea60ac7ac603bc , Did I something wrong? Sorry for being novice !!! Thanks a lot :good::)
[Nexus 5 Android Development] danarama:
Super, thanks for feedback...

If a coupel more people would confirm please, that would be great.
[Nexus 5 Android Development] amirsh77:
I edited my previous post, please read it again thanks
[Nexus 5 Android Development] danarama:
Where did you get 31ef6b718350a3e6d0fd6e890f71f980 from?

The md5 I uploaded is 6dd08ffd29dc995ba0ea60ac7ac603bc
[Nexus 5 Android Development] :
Tried this recovery out and I really like it. Just don't tell people that you really like "PhilZ Touch". People might misinterpret that. Lol. :)
[Nexus 5 Android Development] refedit:
Will test when at home with OTG Cable
[Nexus 5 Android Development] danarama:
Thanks very much.
[Nexus 5 Android Development] refedit:
you're welcome(de nada) ;)

Edit:

No problems here to w/ OTG
[Nexus 5 Android Development] amirsh77:
Sorry forget it!! You are right I did something wrong, so sorry :p
[Nexus 5 Android Development] aheeejd:
I flashed the newest & it's working great, as I said before, I don't use the USB otg yet, but I was having that glitch while flashing roms, kernels etc. Between rom, kernel, supersu, gapps, font, & a couple blacked out apps, the glitch seemed always to happen around fourth item flashed. But now is fixed, thank you guys!

Sent from my Nexus 5 using Xparent Green Tapatalk 2
[Nexus 5 Android Development] net.cat:
I cannot flash the latest cm11 nightlies... Help :(

Sent from my Nexus 5
[Nexus 5 Android Development] danarama:
Going to need more information than that...
[Nexus 5 Android Development] net.cat:
It returns me some error regarding "ro.bootloader" . I googled it this morning and this should be related with the fact that the CyanogenMod team modified the minimum required recovery version, if I'm not wrong. Infact I'm not the only one experiencing this problem :(
[Nexus 5 Android Development] danarama:
This recovery is built on latest version of cwm. Please let us know what cyanogen "expects" as the "minimum required version"

Please also post your cache/recovery logs
[Nexus 5 Android Development] warhead1978:
It isn't the bootloader? You need the bootloader for 4.4.2, go to cm11 thread there is a flashable zip to update.

MfG
[Nexus 5 Android Development] aheeejd:
I've seen quite a few posts, like in PAC thread & elsewhere that people who haven't upgraded to HHZ11k bootloader are not able to flash the rom. Could this be the issue, I'm just guessing, I got my N5 in Jan or Feb & already have that bootloader & I've not had any issues.

Sent from my Nexus 5 using Xparent Red Tapatalk 2
[Nexus 5 Android Development] danarama:
I've added the below to the Recommendations section in post 3. I created the script so all the OTG flash issues could be worked around, but it was fixed too fast :) but it is still useful -

By the way, waiting for next Philz code release before compiling so for now, we still have the test build in this post
[Nexus 5 Android Development] net.cat:
Strange... It worked well so far. Can you link me this thread? Thanks

Sent from my Nexus 5
[Nexus 5 Android Development] danarama:
cyanogenmod thread is in Original android development. Not hard to find with CTRL+F, although you can just fastboot flash the bootloader from the factory images from google, which would be a good idea to keep on your computer anyway
[Nexus 5 Android Development] warhead1978:
http://xdaforums.com/showthread.php?p=51163116

Yes, since the latest nightly there is a new check in the update script that you have to update the bootloader.

Sorry for OT

MfG
[Nexus 5 Android Development] danarama:
No problem. Thanks :)
[Nexus 5 Android Development] Sc4ryB3ar:
How can we tell if we have this boot loader version already, and if we need to update or not?
[Nexus 5 Android Development] warhead1978:
If you get error 7 and the CM nightly update stop, you have the old one ;)

MfG
[Nexus 5 Android Development] m4rk84:
Hey after updating my boot loader and installing PAC Philztouch can't Mount data or anything... So I can't restore back ups etc. After a quick scan and search I can't find a solution. Any help appreciated...

Edit: my bootloader is now HHZ11K

Edit two: it has righted itself. :banghead:

No idea how or why but if anyone can shed light on it so I can prevent it happening again, great. If not, meh at least I can use recovery again!
[Nexus 5 Android Development] aheeejd:
Also, power button & volume down takes you to bootloader, down near the bottom it says bootloader version,

Sent from my Nexus 5 using Xparent Red Tapatalk 2
[Nexus 5 Android Development] warhead1978:
Had you reboot recovery after bootloader update?

MfG
[Nexus 5 Android Development] m4rk84:
Yep. Still running smoothly at the minute :cool:
[Nexus 5 Android Development] danarama:
Should be an upload of 6.22.7 in the next couple of days. Includes the OTG USB "black screen bug" fixed (as in the test release) and [MENTION=4666971]Phil3759[/MENTION] and [MENTION=4464223]McKael[/MENTION] have introduced qualcomm screenshot support (fb2png). Tested and working!

Watch this space.

..well not THIS space, but the thread title will change when it's available.
[Nexus 5 Android Development] danarama:
Thread title updated
[Nexus 5 Android Development] danarama:
6.23.7 uploaded thanks to [MENTION=4666971]Phil3759[/MENTION]

- Better error checking to avoid segfaulting

- really hammer lazy developers (report outdated binary in ui print)

- Use legacy property environment if old update-binary

- fix fb2png flag to be enabled by default

- fix potential unsafe thread code

- Disable gesture actions during md5 checks as they are not thread safe

Also, for the few of you using my md5 creation script in post 2, I re-uploaded it. It makes md5 of anything with .zip but actually, it also makes md5 of .zip.md5 so if you already have md5 in folder, it md5's the md5 haha. Anyway, fixed that.
[Nexus 5 Android Development] danarama:
Added benefit being op gets @ tagged / mentioned a lot so would be better you don't have to respond to too many.

Thanks for your kind words.

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

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
[Nexus 5 Android Development] Striatum_bdr:
Thanks for this [MENTION=2872010]rootSU[/MENTION], having the best recovery on our device is a great step.

Hope it'll handle Omnirom delta update scripting. Let's see tomorrow with next build
[Nexus 5 Android Development] danarama:
Let me know...

:)

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

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
[Nexus 5 Android Development] resynx:
Very nice recovery!! Thanks so much :)
[Nexus 5 Android Development] casonswag:
Finally! Thnaks used this on my n4
[Nexus 5 Android Development] PhillyCheez:
Sweet. I'm using it now.
[Nexus 5 Android Development] alahkel:
I'll definitely try this one :)
[Nexus 5 Android Development] GavinMazey:
This is nice. Just flashed DEC 12 cataclysm and all went well. Thanks
[Nexus 5 Android Development] v0dKa.mL:
Can't download someone has a mirror?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Android Development] ximaginex:
Trying this out now, but I just wanted to say that you sir are a genius. I've been searching for a way to dual recovery twrp and cwmr because I wanted the features of TWRP with the compatibility of CWM. You have achieved this through your custom recovery in the simplest way possible. The recovery has so far surpassed my expectations, with custom coloring and the ability to backup and restore from ANY NANDROID FORMAT. Yes guys, you can backup and restore from any recovery format with this custom recovery. I'm looking forward to your progress with this recovery, with all of its customization and features.

Edit: Right now there is no backup of EFS (says N/A). Will there be support in the future?

Edit 2: Custom color of battery and time does not change when pressed. Not important but just a heads up.

Edit 3: Has anyone gotten aromafm to work? I'm having a little trouble with it.

Edit 4: Got aromafm to work by mounting data partition from within recovery and then using adb from my computer:

adb push aromafm.zip /data/media/clockworkmod/aromafm/aromafm.zip
[Nexus 5 Android Development] Striatum_bdr:
Yes!

You can add it's fully compatible with Omnirom OTA, including the flash after update feature.

Congrats to Phil and you guys.
[Nexus 5 Android Development] CitizenX:
Download is down for me too... :(
[Nexus 5 Android Development] casonswag:
Running real good so far nice features on deck
[Nexus 5 Android Development] Phil3759:
I will look at efs

Battery clock have their own colors. They stick to red on low power

Read faq how to use /data/media/0 instead of deprecated /data/media
[Nexus 5 Android Development] danarama:
Tested download and seems OK.

EFS is a little different on N5 as it has no dedicated efs partition as some other devices do, so may need some work. This is only the first build.

Battery / clock colours working here...

Shouldn't have to ad push. Simple download as per faq

Thanks for confirmation....
[Nexus 5 Android Development] A10Loogie:
USB Mount?

I will admit up front that this may completely be user error. When I select Mounts and Storage--->Mount USB Storage it does nothing. What I expected to happen was that my internal SD card folder would be mounted as a drive un my computer. This has been the behavior with CWM on past devices. IS this an issue or does it have to do with the way the N5 sets up the storage folders?
[Nexus 5 Android Development] danarama:
Mount USB storage is really for external SD cards, which we don't have. I'm not aware of this working on CWM on any of the FUSE filesystem devices, but happy to be shown otherwise. What past devices are you referring to?

The problem with FUSE devices is that /sdcard is not a partition, rather it is a folder within the /data partition so to mount that would be not easy.
[Nexus 5 Android Development] Rykochet:
Mine actually crashed and didn't let my phone reboot. I had to go in and manually install the nightly.
[Nexus 5 Android Development] A10Loogie:
I tried Mount Data as well but it didn't seem to do anything either. My GS2 had an external SD, but when I mounted it in CWM it would mount both the internal and external SDs as separate drives. That was very convenient. I've been having a ton of issues with the Android File Transfer with the N5. It worked fine with the N4 though. Trying to find a decent workaround for copying files to/from the device.
[Nexus 5 Android Development] danarama:
Mount /data mounts the /data partition within recovery. This would allow you to use adb.

Sgs2 was not FUSE. It had a dedicated /sdcard partition

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

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
[Nexus 5 Android Development] Phil3759:
just looked at your OP

Known issues: needs an update ;)

Time fix: any reason you recommend time offset trick?

The QCOM Daemon option will maintain recovery in sync with ROM
[Nexus 5 Android Development] danarama:
Whoops. Updated

That's from when it was first released although, I never got daemon working.
[Nexus 5 Android Development] Phil3759:
under stock rom?

did you try this:

- reboot into rom, sync time

- reboot into recovery, enable the qcom time daemon fix

- reboot into rom, sync time

- reboot back into recovery
[Nexus 5 Android Development] danarama:
I shall give that a go tomorrow.
[Nexus 5 Android Development] Unb0rn:
If I try to enable "Qualcom time daemon", it looks like recovery cannot find time_daemon in /system/bin because of /system being unmounted on recovery startup. Mounting /system through adb, exporting lib path and running daemon manually works fine. Is there any workaround?
[Nexus 5 Android Development] Phil3759:
I am interested in a log

System should be mounted then unmounted on start if you enable the option
[Nexus 5 Android Development] danarama:
Attached last log.
[Nexus 5 Android Development] Phil3759:
that means your actual rom doesn't have a proper time_daemon implementation

code is looking for 2 paths:

/system/bin/time_daemon
/data/time

If one of them is missing, it will fail

What ROM are you on?
[Nexus 5 Android Development] danarama:
I have /system/bin/time_daemon but I do not have /data/time

I am on SlimKat.
[Nexus 5 Android Development] danarama:
I do however, have /data/system/time....
[Nexus 5 Android Development] Unb0rn:
I have exactly the same issue (I'm using PAC ROM) time_daemon is in correct location, but /data/time is actually /data/system/time. Copying it in /data and setting permissions worked but I guess recovery won't set correct time if I'll change it in ROM.
[Nexus 5 Android Development] Phil3759:
ask the slimcat guy to use a proper time_daemon implementation in /data/time

I never encountered a qcom time_daemon implementation using that path

Now, if I there are official such daemons, I can add a check exception to that path

Also, is the /data/system/time folder you have empty or it contains time files updated when time is in sync?
[Nexus 5 Android Development] amirsh77:
I'm the same as you on MahdiRom.
[Nexus 5 Android Development] Phil3759:
if you actually just create the folder /data/time and keep it empty, time should be correctly sync

If not, it means the time_daemon implementation in your ROM is broken. Your ROM cooker should fix in that case

However, I am very curious as if the /data/system/time path is official or just a broken implementation

If it is official, I can add it to the check exceptions to give native support to such ROMs

However, I am not going to add it if it is a broken rom implementation
[Nexus 5 Android Development] danarama:
It just has 2 files called ats_1 and ats_2...with pretty much nothing in them.

Do you have any documentation surrounding how qcom time daemon should be implemented? I can't just go to the team and say "hey, you're doing it wrong" ;)
[Nexus 5 Android Development] Phil3759:
if the files are empty, it means his time_daemon is broken

To simplify it to the maximum (so not technically precise):

Qcom doesn't set time into the chip. It is disabled in kernel sources

Some kernels enabled it, but it is not recommended by qcom, so shouldn't be done

Instead, they use a time_daemon which stores time info data related to the chip into 2 files located under /data/time

On load, the daemon checks the files and sets the time based on internal chip clock. If you delete the files before rebooting, you'll be back to epoch time (1970...)

For proper implementation,check this commit:

https://github.com/CyanogenMod/andr...mmit/700d79bdd0920365bfdd5094e89a5806d0b49c01

And also browse that rc file to get how to load the time_daemon service in rom

So, at the end, as I suspected, it has no sense I add it to exceptions. That path is probably a fall back as the daemon is not properly loaded I guess

Sure you have not to be rude with rom maker, just ask him, suggest him kindly. If he thinks I am wrong and has an advice, I'd be glad to fix things on my side
[Nexus 5 Android Development] adrman:
I'm on Bixie's Rooted Stock ROM and also have data/system/time.
[Nexus 5 Android Development] Phil3759:
An empty folder won't make it a proper implementation
[Nexus 5 Android Development] Unb0rn:
It's not empty for me(PAC ROM, which is, AFAIK is based on CM) It has ats_1 and ats_2 files. According to init.rc it stores rtc time offsets. It looks like most ROMs for hammerhead have only /data/system/time...
[Nexus 5 Android Development] Phil3759:
and and what's inside those files?
[Nexus 5 Android Development] danarama:
I think Symlinking is working for me... but it is an hour incorrect.
[Nexus 5 Android Development] Unb0rn:
They look like binary files 8 bytes long.

Init.hammerhead.rc from CM's github tells they store rtc time offsets

Here
[Nexus 5 Android Development] danarama:
They are the right files...
[Nexus 5 Android Development] Phil3759:
:good:

[MENTION=2872010]rootSU[/MENTION] said they are empty files, that's why I supposed it is a broken rom

Now, if it is not the case, it is another story

Well, maybe hammerhead binaries put it there

Is it same on stock ROMs?
[Nexus 5 Android Development] danarama:
I said "with pretty much nothing in them" but perhaps I should have been more clear. They had a couple of random chars in them and now kowing they're binaries, that makes sense.

EDIT > Really dont understand whats going on. I symlinked /data/system/time to /data/time and used daemon in recovery. It actually picked up todays date and the time (although the time was one hour ahead).

I've removed the symlink but Even if I reboot, change to RTC Offset, reboot, change to daemon, it still picks up todays date and the time (slightly incorrect). How come? I created /data/time as a folder but it doesnt get populated. cant figure out where its getting time from now.

Maybe having /data/time allows fallback to /data/system/time?

EDIT 2 > Yep, delete /data/time "cant find time daemon".

So how is the daemon actually working? recovery looks for /data/time as dir and if exists uses time_daemon. Does time_daemon write AND read from ats_1 and ats_2?
[Nexus 5 Android Development] Unb0rn:
According to google sources they are...

Here
[Nexus 5 Android Development] adrman:
Please pardon my omission. It contains ats_1 and ats_2.