yashsingh1/xdaforums huggingface dataset:
[Android Software Development] hachamacha:
Addition (due to cm11 changes last week) for falcon builds which are now "ghost" builds:

Patch for boardconfig/BoardConfig.mk:

~/cm11$ diff -urN bootable/recovery/boardconfig/BoardConfig.mk.orig bootable/recovery/boardconfig/BoardConfig.mk
--- bootable/recovery/boardconfig/BoardConfig.mk.orig	2014-09-17 12:45:22.720833226 -0700
+++ bootable/recovery/boardconfig/BoardConfig.mk	2014-09-17 12:34:53.639524595 -0700
@@ -867,6 +867,13 @@
TARGET_SCREEN_WIDTH := 720
BRIGHTNESS_SYS_FILE := "/sys/class/backlight/lcd-backlight/brightness"

+#Motorola Moto X ghost: unified moto_ghost [TMO (xt1053), US Cellular (xt1055), Sprint (xt1056), GSM (xt1058), VZW (xt1060), VZW Droid Maxx-Dev Edition (xt1080)]
+else ifneq ($(filter $(TARGET_DEVICE),ghost),)
+ TARGET_COMMON_NAME := Moto X ($(TARGET_DEVICE))
+ TARGET_SCREEN_HEIGHT := 1280
+ TARGET_SCREEN_WIDTH := 720
+ BRIGHTNESS_SYS_FILE := "/sys/class/backlight/lcd-backlight/brightness"
+
#Motorola Moto X: unified moto_msm8960dt [TMO (xt1053), US Cellular (xt1055), Sprint (xt1056), GSM (xt1058), VZW (xt1060), VZW Droid Maxx-Dev Edition (xt1080)]
else ifneq ($(filter $(TARGET_DEVICE),moto_msm8960dt),)
TARGET_COMMON_NAME := Moto X ($(TARGET_DEVICE))

I just built and tested 6.57.9 for ghost (which could either be Motorola Moto X series or a Sony device - have to look up which one). Seem to be fine but required lzop package for compression.

Anyway: As I was noticing before, the CM11 tree is messier than usual (yikes!) so that if you just do a repo sync, you will probably have to get rid of device/Motorola/qcom-common, and/or msm8226-common depending upon whether your building falcon or ghost (old msm8960dt). Of course, it's a messed up couple of .mk files that cause the problem and I'm guessing that someone on cm11 will fix these, but for now, it's a mess.

Anyway, new msm8960dt device name is cm_ghost as per my patch above. Falcon is still falcon but requires some cleanup after a sync to build. I'll probably submit the cm11 patches if I don't find them under review yet.
[Android Software Development] danarama:
Hi [MENTION=4666971]Phil3759[/MENTION] - please upload N5 6.57.9 to goo.im when you get time :)
[Android Software Development] BigBugHmb:
Same for N8000 Plz… ;)

(and a new one? E.g. the new SM-T805?) :D
[Android Software Development] danarama:
Really sorry - i forgot to post the links...

http://d-h.st/FXm

http://d-h.st/TmQ

Edit... Uploaded already. Sorry I didn't mean to make you to go and find the links.
[Android Software Development] Demibrot:
Hi Phil

I have a problem with my external SD card not being detected by Philz Touch.

I'm running Philz Touch 6 (6.15.6 - i9505 cm_jflte) on a Samsung Galaxy S4 Value Edition I9515, which is basically the same as I9505, except for the touch drivers (still works just have to use the buttons)

My SD card is a : San Disk Ultra | class 10 | 32GB

I used partition wizzard to make a primary FAT32 partition ()

The SD card can be detected by my pc via as mass storage

and in my phone under thses directories:

/storage/extSdCard

/mnt/extSdCard

/mnt/media_rw/extSdCard

My internal storage is seen as:

/sdcard

/storage/sdcard0

/mnt/sdcard

and I guess this one /storage/emulated/0

help would be much appreciated
[Android Software Development] danarama:
Please post logs at least.
[Android Software Development] Demibrot:
My bad didn't think about that. I suppose you are talking about this philz_recovery.log?

Or are there any other helpful logs?

View attachment philz_recovery.txt
[Android Software Development] danarama:
Have a look in /cache/recovery

Although it does list your sdcard there

recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
1 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
2 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
3 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
4 /preload ext4 /dev/block/platform/msm_sdcc.1/by-name/hidden 0
5 /efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs 0
6 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata -16384
[B] 7 /storage/sdcard1 auto /devices/platform/msm_sdcc.2/mmc_host/mmc2 0
7 /storage/sdcard1 auto /dev/block/mmcblk1p1 0[/B]
8 /storage/usbdisk auto /devices/platform/msm_hsusb_host/usb 0
8 /storage/usbdisk auto /dev/block/sda1 0
9 /tmp ramdisk ramdisk 0

Does it also have problems with USB disk?
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION] Updated bacon device, please upload to goo, when you have time.

philz_touch_6.57.9-bacon.zip
[Android Software Development] iqbal Khan:
can this cwm is supported lg p765? help me
[Android Software Development] Saalschlacht:
Hello there... Is there a Version for gt-i9295 meanwhile?
[Android Software Development] Pow_2k:
FYI, it looks like we've experienced similar with the unified moto_msm8960 although I haven't been able to figure out if it is exactly the same as chautruongthinh reported. I can't tell if the pixels are being set but just not backlit, this screen is super dark. This occurs at least on the 6.57.5 build by Orphee. I had posted my findings in the moto_msm8960 thread prior to finding chautruongthinh's report pages back in this one. While from what I can tell from my quotes above this isn't a PhilZ problem directly I thought it would be worthwhile to share in the main thread that others have seen similar blackouts/"hangs". I have found I can use the gesture to toggle the screen off/on to get the screen to appear. As PhilZ already thinks the screen is on the first gesture turns it off (again), then the second gesture will turn it on. Of course only works if you know what gesture is set up (if any) for your screen toggle and if you have the menus set to a height that still allows some gesture space at least at the main menu.

If the more knowledgeable minds have any input on how I can assist with either correcting the build for my device or even others let me know.
[Android Software Development] Demibrot:
/storage/sdcard1 is displayed as /storage/extSDCard when I look that directory up

I found this log in /cache/recovery:

last_log : View attachment last_log.txt

btw. What do you mean with USB disk? Note that I bought my phone recently and barely have any knowledge about android's file structure and system in general.
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION]

Case:

Backup failed,

Flashed a file from sideload without issue.

In background still the android-fail picture, the picture does not update.

Send from OnePlus One using Tapatalk
[Android Software Development] danarama:
It doesn't matter what its called in android. /storage/extSdCard doesn't really exist. Its just a mount point. The mmc part is what matters. It could be called /storage/circusclown in android and /storage/monkeyjuice in recovery as long as they both point to the same physical location.

So you cannot backup or install zips from the external card? What about people with the phone the recovery is meant for?

It may be that your phone is more different than you think
[Android Software Development] danarama:
Hi [MENTION=4666971]Phil3759[/MENTION] - about the hammerhead screen dimming issue (goes black instead of dim) I have just confirmed that 6.50.2 my last official build) worked properly so as [MENTION=3247155]fatspirit[/MENTION] mentioned, its only 57.5 and 57.9 that's affected.

I used same prebuilt kernel in all these builds but completely updated cm and philz source to build 57.x

Please could you give me some hints as to what I can do to debug / find source of the issue?
[Android Software Development] Phil3759:
As I do not own the phone, you'll have to reverse the commits step by step and tell me when it started
[Android Software Development] danarama:
OK will do. Suppose I'll start with anything display related. Will probably take some time but will let you know.

Thanks.
[Android Software Development] Phil3759:
Seems many are hammering and crying in their support threads about updates

To make it clear, I added announcement to head of OP: "End Of Support"

I also update project status: No Longer Updated

As I mentioned before, I have a lot of new important projects in my real life. I am very happy to abandon this project for real life alternatives.

CWM is a dead project for now, until some dev resurrects it. I was about to do, until these new projects came.

Current version will probably work a while for many devices. Some devices with new ROM installers could have issues. Just use TWRP or the CM Simple Recovery

If the current version works for you, there is no reason you don't use it though. No need to ***** in all threads because it doesn't work for you. Just move on to other alternatives.
[Android Software Development] Siberian Tiger:
Thank you for your countless hours of coding!!!

And good luck with the new projects ☺

ST
[Android Software Development] BigBugHmb:
Thats ok, thx and good luck in your real life.

I think some of the people don't ask for a NEWER version, (6.57.9 is good for a while i think) but for that actual version on used devices like S5 or N8000. Nothing more…

But it's ok, real life gets first!

Good luck and thank you for all!
[Android Software Development] jurben:
Wish you success and happy life in your real world.
[Android Software Development] shoey63:
Thanks for everything Phil, it's been an amazing journey. From 2.7.0 to 6.57.9 :thumbup:
[Android Software Development] Phil3759:
the issue is that on some devices, current version could become outdated when they get new ROMs, mainly on huge changes like from JB to KitKat, but not only
[Android Software Development] temasek:
Thanks Philz for your work.

Been a pleasure to have your recovery on all my devices.

Good luck to your future projects.
[Android Software Development] abhibnl:
Thanks philz for your great contribution to this community. Philz recovery was the first recovery i ever flashed on my i9300 and still it'a the only one i'm using right now. Wish you all the luck for youe future endevaours and i hope to see you on the forums again soon, well if someone magically picks up n develops cwm in accordance with the new roms.

Sent from Galaxy S3 Powered by Temasek + Boeffla
[Android Software Development] oscar the grouch:
Thanks Phil. I will probably use this for the foreseeable future. my device hasn't been updated officially in years. You do outstanding work sir. much much thanks.:good:
[Android Software Development] muccioli:
Hi Phil,

I tray to flash philz_touch_6.57.5-moto_msm8960.img in my Razr xt 925 4.4.2, but i dont know recovery is not flash. When load in recovery mode, load original recovery, Android System recovery <3e>

KDA20.117

My bootloader is unlocked.

I try it via minimal ADB and Fastboot. Everthing is ok, i think.

Some idea what's happening?

Thanks.
[Android Software Development] jurben:
Try asking in your device thread.
[Android Software Development] yuweng:
Thank you so much & best of luck in your future undertakings, my Master Shifu . . .

Hmm, i wonder if Koush is interested to take over since he is no longer with cm . . . :cowboy:

Or may be any of these Top 10 custom ROM would like to make PhilZ Touch their official recovery . . . :cool:

Hey, anyone of you here know any DEVs for these Top 10 contact them & see if they are interested but final decision is of course up to Phil3759 . . . :fingers-crossed:
[Android Software Development] pgflying:
who can make the Philz touch for ZTE redbull V9180? Thankyou very much.
[Android Software Development] danarama:
I know some of the slim devs, however I doubt they have any time to put into the project and even if they did, I don't know what phil's thoughts on that would be.
[Android Software Development] Asce1062:
Flipped screen

:crying: Hi philZ I've managed to correct flipped screens on P705 and P700 ( on the recovery )... is there a way to correct flipped screen for the Aroma File Manger?? also dissable virtual keys by default(not required since we have hardware keys) :fingers-crossed:
[Android Software Development] bovirus:
Which are the specific folder in

https://goo.im/devs/philz_touch/CWM_Advanced_Edition/

for Asus Nexus 7 and Samsung Galaxy S4 I9505?
[Android Software Development] danarama:
Please have a look at post 1. There are links to each device thread there. If you read the links, each one gives you the codename for each device. Deb, flo, grouper etc. That's what the folders are called.
[Android Software Development] varun.chitre15:
[MENTION=4666971]Phil3759[/MENTION]

Hi Phyto,

I have managed to port the recovery to Android One devices(all three of them)(common for all)

Here is the link to the thread

http://xdaforums.com/crossdevice-dev/android-one-general/sprout-philz-touch-v6-57-9-t2887574

Please add the recovery image and thread link to OP.
[Android Software Development] 5vision:
Xperia M/M Dual USB storage mount BUG

Hi PhilZ,

all CWM versions after 6.0.4.5 have the same "USB storage mount" BUG on Xperia M/M Dual devices. It was fixed in the version 6.0.4.5 (Changelog in this thread: http://xdaforums.com/show....php?t=2481864) and works fine, but it doesn't work with all these versions 6.0.4.7/6.0.4.9 and PhilZ Touch 6.50.6. I think this fix was forgotten and this BUG is persistent in all newer versions - please check.

Greetz, 5vision
[Android Software Development] marcjuh:
Tnx philz for all youre work and countless hours you put in all kinds of phones...hope you do a great job an happiness as you did in phones...succes. ..

÷÷÷ tapatalked Galaxy S4 ÷÷÷÷
[Android Software Development] Phil3759:
Yes, many people do not imagine the amount of work it was to maintain so many devices + the sources + a really filled life
[Android Software Development] GrayJack:
I want to restore only /data/media having a full custom backup (with /data/media in it).

So I go to custom restore and check media only. Then I gave to go to the place where backup is stored - and which file should I choose? There are datamedia.ext4.tar, datamedia.ext4.tar.a etc. So - I can:

1. Choose any file (not necessary datamedia, it could be system.ext4.tar - the recovery will try to find necessary file in this folder by itself.

2. Choose datamedia.ext4.tar - and the recovery will continue with all other parts (tar.a, tar.b etc) automatically.

3. Sequentially choose datamedia.ext4.tar, then datamedia.ext4.tar.a etc - till the end.

What is the right way? Please advise.
[Android Software Development] danarama:
I don't know what you mean by restoring datamedia or what that even means as I have no idea what device you have. Only familiar with HTC, Samsung and Nexus but when you do a custom restore, it then shows you all the files in the backup, regardless of what you picked to restore. Press one to confirm your restore.
[Android Software Development] GrayJack:
My device was shown in my signature.

But your answer is good, it actually means my p.1 :)

Thank you.
[Android Software Development] danarama:
Tapatalk doesn't show signatures. When in had an i9300 , there was no backup called datamedia :$
[Android Software Development] GrayJack:
Sorry, man, but you are not right!

Actually I have tested cache and data formatted in f2fs and because lack of support in some apps (Mobile Odin for instance) I've decided to revert back.

Because standard backup doesn't include /data/media I have to perform custom one.

But the space at extSdCard is limited, so I have performed a backup with data only, copied this backup to PC, and then performed /data/media only - and copied that one to PC also.

I am planning to format partitions back to ext4 and restore "standard" backup, and then - /data/media connecting recovery to PC in Mass Storage mode.

So here is a listing of my first and second backups:

27.09.2014 20:10 8*388*608 boot.img
27.09.2014 20:10 8*388*608 recovery.img
27.09.2014 20:10 0 system.ext4.tar
27.09.2014 20:14 1*000*000*000 system.ext4.tar.a
27.09.2014 20:15 412*029*440 system.ext4.tar.b
27.09.2014 20:16 0 data.f2fs.tar
27.09.2014 20:18 1*000*000*000 data.f2fs.tar.a
27.09.2014 20:20 1*000*000*000 data.f2fs.tar.b
27.09.2014 20:22 1*000*000*000 data.f2fs.tar.c
27.09.2014 20:24 1*000*000*000 data.f2fs.tar.d
27.09.2014 20:26 1*000*000*000 data.f2fs.tar.e
27.09.2014 20:28 971*030*016 data.f2fs.tar.f
27.09.2014 20:28 0 cache.f2fs.tar
27.09.2014 20:28 166*912 cache.f2fs.tar.a
27.09.2014 20:28 0 preload.ext4.tar
27.09.2014 20:28 7*168 preload.ext4.tar.a
27.09.2014 20:28 33*554*432 modem.img
27.09.2014 20:38 840 nandroid.md5
27.09.2014 20:38 8*573 recovery.log

28.09.2014 00:54 0 datamedia.f2fs.tar
28.09.2014 00:56 1*000*000*000 datamedia.f2fs.tar.a
28.09.2014 00:58 1*000*000*000 datamedia.f2fs.tar.b
28.09.2014 01:02 1*000*000*000 datamedia.f2fs.tar.c
28.09.2014 01:05 1*000*000*000 datamedia.f2fs.tar.d
28.09.2014 01:07 1*000*000*000 datamedia.f2fs.tar.e
28.09.2014 01:09 1*000*000*000 datamedia.f2fs.tar.f
28.09.2014 01:11 790*882*816 datamedia.f2fs.tar.g
28.09.2014 01:20 438 nandroid.md5

So as you can see datamedia files exist. I just omitted f2fs extension to avoid some misunderstanding.
[Android Software Development] jurben:
That last file select has no effect. That page actually is only confirmation page that show the content of backup folder you selected before. (You can select anything to confirm.)

Sorry, it was answered ... [emoji9] [emoji9]
[Android Software Development] danarama:
I had the piece of crap S3 for 13 months with no backup of data/media, but you are right and I am wrong, I still had the S3 for a massive 1 month after data/media backup was added to it.
[Android Software Development] steventrannn:
There's 2 zip files for this recovery: .zip and .zip.md5. Which file do I need to download to flash from recovery?
[Android Software Development] danarama:
There is only one zip. The .zip.md5 is not a zip. Its an md5 sum used to confirm the .zip is not corrupt
[Android Software Development] steventrannn:
Thanks for clearing that up for me.
[Android Software Development] ariefabuzaky:
Hi iam facing problem with aroma installer using unofficial cwm from this thread http://xdaforums.com/showthread.php?t=2807639

Anyone can fix this .. thanks

Sent from Mighty S5 G906s
[Android Software Development] katinatez:
The way to fix that is the recovery dev has to use omni source kernel ( pre-built ) and compile philz recovery. I have first hand experience with my device; had the same issue until I figured it out.
[Android Software Development] bangdes:
HTC Desire 300 please...
[Android Software Development] Android-Andi:
Everything mentioned in OP. Also read last pages about the future of PhilZ Touch.

Good luck!

Send from OnePlus One using Tapatalk
[Android Software Development] GrayJack:
Strange situation and I have no idea what to do.

There is two versions for GT-i9300: official 6.48.4 and unofficial 6.57.5 from arter97. Neither works good.

1. I cannot open with official one /data/data in Aroma Filemanager - it hangs on. Unofficial works OK.

2. During custom backup with unofficial one strange bug exists. Official one proceeds OK.

So looks like there is a real need to find someone who will compile latest Philz Recovery for our device - and it would be nice to include f2fs support.
[Android Software Development] danarama:
Why not ask arter97?
[Android Software Development] GrayJack:
Certainly I have asked him - and you can see it simply following the link I've provided in my previous message.

But as you can see there is another bug - and that's why I've asked about compiling recovery with latest sources hoping it is free from both.
[Android Software Development] danarama:
Yep. Arter just needs to type "repo sync" and whammo, he has latest sources. Then he types "mka recoveryimage" and whammo, latest recovery built. Don't really need to get anyone else involved
[Android Software Development] nicesoni_ash:
Well he replied that he will release updated recovery with latest repo with his next kernel version so just wait for his next release.

___________

Sent from my "GT-I9300/1+1" powered by Temasek/Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Android Software Development] GrayJack:
Sure, I hope latest sources are free from both bugs.

By the way some time ago nobody believed me there is a problem with Aroma Filemanager. I am happy this problem was solved at least in the end of Philz Recovery development.

And also - can someone answer me? I understand it possibly requires to dl 100 Mb of data - but maybe someone has time and Internet bandwidth for it.

This problem exists since early versions of recovery - and exists still.

When I try to install csc_sec.zip extracted from official firmware cache.img - it never installed. Here is an example of such csc_sec.sip.

Recovery tells me there is an obsolete updater-binary - so I updated it and now installation performs OK - but anyway in fact /system/csc is not flashed.

What am I doing wrong? I've tried to disable signature check - it doesn't matter. In the same time official recovery as well as Mobile Odin installs csc_sec.zip even with obsolete version of updater-binary.
[Android Software Development] danarama:
Philz still flashes with obsolete binary. Just warns you it is out of date.

If you have issues with flashing, please provide logs. No one will follow links to other threads. Post them here.

Aroma file manager issues arent philz issues. Aroma is a bonus.
[Android Software Development] remotehugger:
OK, so thats why when flashing it says "please update to latest binary" - cuz I'm using an older philz - everything still flashes OK so I haven't switched to anything else - I really like philz -

VM GSIII/jdsingle76's deodexed NDC 4.4.2/stock kernel ?
[Android Software Development] danarama:
[MENTION=4666971]Phil3759[/MENTION] I know this is a "dead" project, but you said to let you know if I found the source of the screen dim issue.

Issue is screen is blank not dim on dim timeout.

Cause is touch_gui.c, line 995

apply_brightness_value(0);

Change to:

apply_brightness_value(10);

...Resolves the issue. This change was introduced in commit:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/75d135c8d27db7302b94f42c86566fbdef19abea?diff=split

I would expect this affects more devices than Nexus 5
[Android Software Development] GrayJack:
OK, log file is attached.

As for Aroma - I could believe it is Aroma issues if the problem were present in all versions of Philz recovery.
[Android Software Development] danarama:
Different ROMs different kernels, apps act differently. Fact! You'll get no aroma support here.
[Android Software Development] GrayJack:
When booted into recovery I have no idea what is effect of ROM and kernel. If partition or fs is broken - it's broken - and I can play with any recovery and any version - I cannot open it. But when I see something like buffer overflow because of huge number of files - it's a matter of recovery where Aroma works.

But forget about Aroma - as I said the problem were solved in later versions. Can you advise something on my log you have asked to provide? As far as I see there is 0 downloads - so looks like we are chatting here with no intention to make something better.
[Android Software Development] Phil3759:
Thanks, i will update the sources. The cause is kernel related. Most good kernels should ignore any too low value and stick with device min