yashsingh1/xdaforums huggingface dataset:
[Android Software Development] danarama:
In recovery ROM has no effect. That statement is to illustrate that apps (and aroma is an app) acts differently on different Roma and kernels. You understand philz recovery uses a cm11 kernel for your device, yes? So if aroma acts differently between builds it is likely a compatibility issue between kernel and app and NOT recovery

No I won't read your logs. I am not the developer. But it is common courtesy if reporting a "bug" to share logs. But yes, would be nice if you stop "chatting" and wait for someone to look at your logs / build you latest version or simply move to TWRP like OP says.

---------- Post added at 11:53 PM ---------- Previous post was at 11:50 PM ----------

Its just default nexus 5 kernel with f2fs. Not a "good kernel"

Thanks for your support.

If I give you Dropbox.links would you mind uploading to goo one last time please?

https://www.dropbox.com/s/6m5lq3qjjb2v84b/philz_touch_6.57.9_RE-UP-hammerhead.zip?dl=0

https://www.dropbox.com/s/wrihfnoiqxidw7d/philz_touch_6.57.9_RE-UP-hammerhead.zip.md5?dl=0
[Android Software Development] GrayJack:
As Philz told a number of times - he uses original kernels only.

And kernel is part of Philz recovery. Sure he cannot change a code of kernel - but it is his decision. And I (common user) cannot change neither kernel, nor some code - I am using a ready product. And yes - I call it "recovery" - but sure I mean a whole product - not partition, code, kernel or whatever.

If Aroma cannot work with some part of recovery - it doesn't matter is it a problem with kernel or problem with implementation - it doesn't work. In this case we either remove "Aroma File Manager Support" from OP or trying to make things better - changing kernel, changing code or whatever.

As for logs - thank you for your suggestion - it was nice advice especially taking into consideration

Let's stop chatting about life - I don't think it's useful and I hope someone competent enough will give the answer on my question.
[Android Software Development] danarama:
No, he uses CM11 kernel as its based on CM11. Phil has no control over the source. And some builds need special kernels. Its clear you don't know what you're talking about.

It works in some cases and not in others. Phil openly said he cannot support it if it doesn't work so.stop going on about it. This is not the thread for "common user"..it is development thread and development is.over (read op). Please post in your s3 thread from now on

Oh shut up! Use TWRP.

Here's the deal, you stop quoting me and I'll stop talking to you. Thought I was rid of you when I dumped my s3 but no such luck. I'll ignore you and your annoying posts from now on
[Android Software Development] Chlorophyll:
can anyone pls reply which file i have to flash for sm n900/note 3 international edition..

pls reply..am confused...
[Android Software Development] danarama:
No official support.

Maybe this is what you're looking for http://xdaforums.com/showthread.php?t=2701644
[Android Software Development] aness zurba:
anyone knows how to fix wrong time and date?
[Android Software Development] jurben:
Go to settings and select right timezone settings.

If your device is qualcomm, you might have to set to use qualcomm date time.
[Android Software Development] Phil3759:
Update 6.58.0 / libtouch_gui 1.42

Thanks [MENTION=2872010]rootSU[/MENTION] for having spotted the misytpe bug

I optimized the code to have a min brightness defined value on compile time. Maybe more future proof as some devices do need now a max brightness value, and maybe some will need a custom min value too
[Android Software Development] ariefabuzaky:
How about unofficial philz recovery s5 lte-a g906, we have a problem that recovery cannot flash aroma installer.. thanks Phil

Sent from Mighty S5 G906s
[Android Software Development] Phil3759:
I consider Aroma as a dead project

It will be probably fresh meat with next android L update

For some devices, it still works, for many newer, it will be less likely to work

Most issues are related to the kernel graphic drivers in recovery and the mount paths

- either Aroma is updated

- or you start playing with your device kernel to make it work and repack recovery with it

I have no time to look into kernels for devices I do not own, and especially for an unsupported third party program
[Android Software Development] master64nl:
I am happy with this CWM PhilzTouch because I had bootloop with this vesion CWM. Flashing Philz one and problem solved.
[Android Software Development] 93Akkord:
I'm having trouble flashing a zip that I didn't have trouble flashing with an older version of Philz. None of the files from the Zip are flashed on the device, but the build.prop tweaks are added. My first assumption would be something faulty in the updater-script.

This is what is looks like.
[Android Software Development] danarama:
Can you provide the logs from /cache/recovery please?

Might be best to clear out that directory, flash the zip then get the fresh logs
[Android Software Development] 93Akkord:
Here's the log from the install.

http://pastebin.com/XTRNvcqF

Edit: Sorry.. just realized you wanted fresh. Let me know if they are still needed. I don't notice anything besides the install of that zip in the logs though.

Thanks!
[Android Software Development] danarama:
Well this seems to be the problem although not sure of the cause.

-------------------------------mount: no mtd partition named "system"minzip: Extracted file "/system/app/AudioEffectService.apk"

Maybe it needs to be /system not system
[Android Software Development] 93Akkord:
Would that cause all the other files to not be flashed as well?
[Android Software Development] danarama:
I would expect so if system isn't mounted correctly.

Although looking at the script again:

mount("yaffs2", "MTD", "system", "/system");

It has both,

You may need to mess about with the script, maybe remove "system," and see what happens. Trial and error is all I have to offer here. Not sure if someone else has more insight to the logs
[Android Software Development] Phil3759:
I'd avoid using anything from the guy that gave you such a package!

Since the Galaxy S, 4 years ago, I am not aware of any MTD device from Samsung!

The script is badly written, doesn't mount /data before working with it, uses bad syntax for mount, missing new lines...
[Android Software Development] judianmac:
I was trying to install The New Jedi V2 ROM ..ROM installed but would not boot..I was using CWM from February, would this have been the cause? I have a TMobile Galaxy Note 3. I was trying to read all the Notes on Philz but there are so many...I love your program..sorry to see it end.
[Android Software Development] danarama:
Would what have been the cause? No one can guess the cause
[Android Software Development] thereassaad:
[MENTION=4666971]Phil3759[/MENTION] please update my Note 2 recovery to latest update please
[Android Software Development] aeroman:
Omg :eek:

By me only 89 empty folders. ;)

Greetz

tapatalked with my GT-I9505.
[Android Software Development] ScottBroker:
How do we stop this? I always flash back TWRP because I cannot wait for the BU to take 45 minutes. Why is it almost 10 times as long than TWRP, and what can be done about it???
[Android Software Development] maranello69:
twrp caches the disk writes, cwn doesn't. there's nothing to do, buy a better card or switch to twrp ;)
[Android Software Development] danarama:
Do you have te same stupid folders the user you quoted had? Or is it because you have compression enabled? many reasons a backup takes a long time. Perhaps you could share your config?

I backup 3GB+ nandroids in about 5 - 10 minutes.
[Android Software Development] ScottBroker:
I do not have those empty files. I have a M919, I use the default settings on TWRP and Philz, Philz takes about 47 minutes, TWRP take 7 ish. I like Philz better, but need an efficient backup capabilities

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

could you share the settings you use to accomplish these BU times...???
[Android Software Development] danarama:
Have a look at compression settings. The higher the compression, the lower the speed. I dont think TWRP compresses by default?

---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------

Compression off
[Android Software Development] danarama:
Great post. Thanks.
[Android Software Development] aeroman:
The reasons are obvious and decisive for me. :good:

a little thought ..

I recently used this recovery (with exFat Support) for test purposes,

mean that it went faster there. You can give it a try, maybe it helps on your hard & difficult work. ;)

works NTFS Format with this Recovery, maybe all can with an 64GB Card switch to this format?!

Greetings
[Android Software Development] danarama:
Or FAT 32....
[Android Software Development] aeroman:
There is a way, :) prefer was ntfs, because data size limit & Encryption.

It was also my windows don't like, that would be the next problem with 64GB card.
[Android Software Development] Phil3759:
I plan to add ntfs
[Android Software Development] danarama:
NTFS and exFAT don't work with Linux. Only option is FAT32 for us, with 64GB card.
[Android Software Development] electricsheepdreamer:
Sorry for the late response, I somehow missed your post before.

It makes CWM/TWRP backups without the need to boot into Recovery (uploading it to some cloud service is optional as schedulling, etc..check its thread)

http://xdaforums.com/showthread.php?p=35271533

There seems to be some issue with exFAT formatted 64Gb cards on i9505 (as Phil mentioned before (nice avatar, BTW) and kantjer is making some tests in OBackup thread)

It's hard for me to comment on the issue itself. I formatted Sammy's 64Gb on Win7 PC as exFAT and it works like charm on S2 right from the start. TWRP and CWM backups from Philz Recovery and from the app, 5 mins/~2Gb backup size).

Regards.
[Android Software Development] Phil3759:
No, you can use exfat using either fuse or built in kernel modules like I do

NTFS is possible too using fuse

However, for NTFS, you'll need a ROM supporting NTFS or use third party init.d alternatives
[Android Software Development] danarama:
< < < < <

I'm talking about my Linux computer :p
[Android Software Development] electricsheepdreamer:
FAT32 then :)
[Android Software Development] kantjer:
A backup on my 32GB sd took about 6:30 min and on my 64GB exFAT formatted sd over 24 minutes :eek:
[Android Software Development] Phil3759:
fuse is for Unix and was ported to Android, which is linux based

So, you can the same way as in Android. But obviously, who wants exfat or NTFS on linux!
[Android Software Development] danarama:
Exactly ;)
[Android Software Development] DSA:
Read the first post :rolleyes:
[Android Software Development] rogersb11:
Maybe actually look and you'd find one that's very close latest. Or build it yourself. Or maybe read
[Android Software Development] shoey63:
[MENTION=507649]devs[/MENTION]

**ALERT**

Do not repo sync your cm11 repo if you haven't yet built 6.58.0!

You will not get a working recovery image due to their recent changes.

You have been warned....
[Android Software Development] yuweng:
Just built it two days ago & it was all right, the culprit is this commits, temporary solution & i've just build it, confirmed it boots . . . :cool:

cd ~/cm11/build
git checkout [URL="https://github.com/CyanogenMod/android_build/commit/f27c277c4f191ebdbad3b7f58ffc3a086d032f4a"]f27c277[/URL]
[Android Software Development] danarama:
From what date? Any details on this? I repo sync'd day before 6.58 - when I made the fixes in 6.58 in previous version and built fine

Edit > Didnt see above.
[Android Software Development] 3lo0sh:
dude can you build it for nexus 5
[Android Software Development] yuweng:
So many DEVs has already made so many guides/ tools/ distro, its so easy nowadays to build one yourself, refer to this thread for more infos . . . :good:
[Android Software Development] danarama:
????

I sincerely hope you're joking!

I am the Nexus 5 maintainer!!!
[Android Software Development] 3lo0sh:
Lastest version in nexus 4 is 6.57.9

And i will not download 20GB from cm source sense there is already one sync it ?
[Android Software Development] danarama:
So do you even know why you're asking for 6.58.0? Do you know the difference between 6.57.9 and 6.58.0? I think you don't

..and you said Nexus 5 first time, not Nexus 4.
[Android Software Development] 93Akkord:
What would be a good way to go about fixing this? I've been trying to find a good guide on creating my own updater-script or even a brand new flashable zip, but all guides I've found are from years ago and are poorly written.
[Android Software Development] danarama:
Download a good popular ROM and look at their script.
[Android Software Development] 3lo0sh:
Sorry, I mean Nexus 5 (my keyboard is junk -_-) but i like having lastest things and you can't belame for that ?
[Android Software Development] danarama:
In 6.57.9, it was reported in the Nexus 5 thread that instead of screen dim after time of inactivity, screen goes blank instead. I looked at the code and fixed the issue. recompiled 6.57.9 and re-uploaded the files with the fix. I then told Phil about it, who then built new version 6.58.0 with only that fix.

So on other devices, difference between 6.57.9 and 6.58.0 is screen dim fix.

On Nexus 5, no difference between 6.57.9 and 6.58.0 if you get it from the links in my thread.
[Android Software Development] remotehugger:
this has probly been addressed but what would I need to do to get the latest version of Philz for my phone ? Virgin Mobile S3 running 4.4.2 NDC - any direction, suggestions or ideas would be awesome !

VM GSIII/jdsingle76's deodexed NDC 4.4.2/stock kernel ?
[Android Software Development] danarama:
The official stance is, if the version you have works, keep using it. If it doesn't - use something else. The project is no longer maintained, so unless your device had a maintainer that was not the original dev, maybe they can update - if not, well unless you're going to learn to do it yourself, nothing is going to happen
[Android Software Development] andrew.mackew:
@op

Thank you very much for the recent improvements! Sounds really exciting!

I wonder if is there any update for t0lte and hlte? Or anyone could point me out a link for an updated release for both since I didn't find it.
[Android Software Development] danarama:
Read post directly above yours. Same.answer
[Android Software Development] danarama:
Whatever version is linked in OP is the latest version for each phone. No new versions will be compiled unless someone for your device will do it. This project is no longer maintained. There will be no newer versions.
[Android Software Development] Phil3759:
Update to developers: v6.58.4

This is just a source update to make it possible to compile PhilZ Touch after doing a repo sync that merges latest CM changes to the build core
[Android Software Development] werty100:
it give my this error with lastes PhilZ sources under BBQLinux

Export includes file: external/e2fsprogs/e2fsck/Android.mk -- /home/werty100/cm11/out/target/product/p8/obj/RECOVERY_EXECUTABLES/recovery_e2fsck_intermediates/export_includes

Export includes file: external/e2fsprogs/misc/Android.mk -- /home/werty100/cm11/out/target/product/p8/obj/RECOVERY_EXECUTABLES/recovery_mke2fs_intermediates/export_includes

make: *** No rule to make target 'mount.exfat_static', needed by '/home/werty100/cm11/out/target/product/p8/obj/EXECUTABLES/recovery_intermediates/recovery.o'. Alto.

make: *** Se espera a que terminen otras tareas....

Export includes file: external/e2fsprogs/misc/Android.mk -- /home/werty100/cm11/out/target/product/p8/obj/RECOVERY_EXECUTABLES/recovery_tune2fs_intermediates/export_includes
[Android Software Development] eris23:
My mako build of the full rom failed with: system/out/target/product/mako/obj/SHARED_LIBRARIES/audio.primary.msm8960_intermediates/audio_hw.o' failed (possibly due to change to allow audio during boot animation) -- but "mka recoveryimage" worked (I also reverted the f27c277 commit).
[Android Software Development] Phil3759:
ensure you do a repo sync before

Mainly this one:

https://github.com/CyanogenMod/android_build/commit/71f0b849800995322c4752d5919761a278680d64

and these 2:

https://github.com/CyanogenMod/android_build/commit/fddc5f4357768d269b83e37712b3d2b5edfe0bca

https://github.com/CyanogenMod/android_build/commit/1cdf80b5bce1b85f67828b8edc167b6c6db85428

probably not affecting recovery and has nothing to do with my sources. The CM tree must be broken temporarly
[Android Software Development] yuweng:
i don't understand why all newbies don't tell you the whole story . . . :silly:

i did found out when NOT using BOARD_USE_NTFS_3G := false then the build is all right, with it, it'll give below error . . .

Export includes file: bootable/recovery/updater/Android.mk -- /home/yuweng/cm11/out/target/product/MediaTek/obj/EXECUTABLES/updater_intermediates/export_includes
make: *** No rule to make target 'mount.ntfs-3g', needed by '/home/yuweng/cm11/out/target/product/MediaTek/obj/EXECUTABLES/recovery_intermediates/recovery.o'. Stop.
make: *** Waiting for unfinished jobs....
[Android Software Development] werty100:
Disable BOARD_USE_NTFS_3G := false works but give my same error also aplaying new changes

target thumb C++: libminivold <= system/vold/VolumeManager.cpp

target thumb C++: libminivold <= system/vold/CommandListener.cpp

/bin/bash: -: No existe el fichero o el directorio

build/core/binary.mk:432: recipe for target '/home/werty100/cm11/out/target/product/p8/obj/STATIC_LIBRARIES/libminivold_intermediates/VolumeManager.o' failed

make: *** [/home/werty100/cm11/out/target/product/p8/obj/STATIC_LIBRARIES/libminivold_intermediates/VolumeManager.o] Error 1

make: *** Se espera a que terminen otras tareas....

/bin/bash: -: No existe el fichero o el directorio

target thumb C++: libminivold <= system/vold/VoldCommand.cpp

build/core/binary.mk:432: recipe for target '/home/werty100/cm11/out/target/product/p8/obj/STATIC_LIBRARIES/libminivold_intermediates/CommandListener.o' failed

make: *** [/home/werty100/cm11/out/target/product/p8/obj/STATIC_LIBRARIES/libminivold_intermediates/CommandListener.o] Error 1

/bin/bash: -: No existe el fichero o el directorio

build/core/binary.mk:432: recipe for target '/home/werty100/cm11/out/target/product/p8/obj/STATIC_LIBRARIES/libminivold_intermediates/VoldCommand.o' failed

make: *** [/home/werty100/cm11/out/target/product/p8/obj/STATIC_LIBRARIES/libminivold_intermediates/VoldCommand.o] Error 1

make: *** wait: No hay ningún proceso hijo. Alto.

vold need fix?¿
[Android Software Development] ksio89:
Hi, I've installed this recovery onto LG-E975, and when I choose "install ZIP from sdcard, I can't see anything in /sdcard partition, only the /clockword folder which contains my stock ROM backup is visible. I had the regular CWM 6.0.4.7 recovery installed by FreeGee (Mako unlock) before flashing this new recovery, and i could see my files and folders in storage/sdcard0 normally. Do I have to mount the /sdcard partition or something like that? Thanks in advance.

Forgot to mention i'm using the version 6.57.9-e975 of this recovery.
[Android Software Development] danarama:
/data/media read FAQ
[Android Software Development] ksio89:
OK, thanks for the help. I read the FAQ and on recovery menu I set /data/media as /sdcard, now I can see all files and folder. The issue is now that I can't flash a certain package (a script in zip extension which creates a flashable EFS partitions backup also in zip format), the following message appears:

"Using legacy property environment for update-binary... Please upgrade to latest binary". The installation apparently finishes fine, but when I check the folder where the supposed package was to be placed in it's empty. Is there anything I could do to install this package? Thanks in advance.
[Android Software Development] danarama:
Legacy environment is just a warning and doesn't effect the flash. How are you checking the folder?

What android version do you run?
[Android Software Development] ksio89:
Running Jelly Bean 4.1.2 on LG-E977 (identically the same as E975). I read this on FAQ, don't know if this has something to do:

"Start of v6.02.2, recoveries are based on cm-11.0 (KitKat) device tree."

My intention is to perform an EFS backup (and flash the package with EFS partitions) and know for sure that I can flash modem from my device. Then i will perform some wipes and install a custom ROM based on stock 4.4.2, but I'm not sure if I'll be able to flash these files after installing this ROM, if something gets corrupted. The installation completes fine but the file does not simply get created in the expected folder, it's like is blocking the creation of such package. I could create this package just fine with stock CWM 6.0.4.7. Thanks in advance.
[Android Software Development] danarama:
Have you used the efs package before?

Please upload cache/recovery log and updater-script
[Android Software Development] Phil3759:
Yes, i was about to fix this but completely forgot about it

Same issue for any "optional" dependency
[Android Software Development] ksio89:
Yes, I've used. Flashed a custom ROM, got no network signal, then I installed this EFS package via recovery (stock CWM 6.0.4.7) and my signal was restored. I have a flashable modem package which is installed the same way.

I'm afraid I won't be able to perform this with this recovery, though.

Okay, I have attached both files. I changed extension to txt so it can viewed on the internet browser itself. I found this excerpt on last_log from /cache/recovery folder:

Everything is Ok

mv: can't create '/sdcard/EFS_Backup/efsbackupflashable.zip': Permission denied

mv: can't create '/sdcard/EFS_Backup/efs1.img': Permission denied

mv: can't create '/sdcard/EFS_Backup/efs2.img': Permission denied

run_program: child exited with status 1

Backin'up EFS and creatin' flashable zip...

script result was [Finished.]

This log actually refers to the 2nd script which I tried to use to create the package containing the backup. As I've stated, it used to work just fine with stock CWM.
[Android Software Development] danarama:
You haven't at any point copied all your data off and back on to your sdcard via adb have you?

Also, does /sdcard work in android? Can you take photos for example?
[Android Software Development] ksio89:
Nope. Yes, sdcard works fine and I can take photos. I just flashed this new recovery because I read that it was more compatible with recent custom ROMs. Do you know how would I revert to the stock CWM recovery? The stock CWM recovery was installed via FreeGee, which is an app which unlocks bootloader from LG devices and enables a custom recovery to be installed. Thanks for the help.
[Android Software Development] danarama:
Don't go back to stock cwm. Its antiquated. Get TWRP for your device if you can

I don't know why you've got this issue on this recovery. You may get better response from people in your device thread. Its linked in post 1. Otherwise change to TWRP
[Android Software Development] ksio89:
Okay, no problem. I'll post my questions there or find an alternative way to perform these backups and restore them. Thanks for the help, anyway, mate :svetius:
[Android Software Development] Phil3759:
The issue seems in your shell script

Can you post contents from this file in your zip?

backupefs.sh

Something wired in there probably
[Android Software Development] ksio89:
Okay, this is the code there:

#!/system/bin/sh

# make dirs
/sbin/busybox mkdir -p /sdcard/EFS_Backup/;

# 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;

# 7z file
/system/xbin/7za a -tzip /tmp/efsbackupflashable.zip *.img META-INF/;

# move files
mv -f efsbackupflashable.zip /sdcard/EFS_Backup
mv -f efs1.img /sdcard/EFS_Backup
mv -f efs2.img /sdcard/EFS_Backup