yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Phil3759:
looking at kernel dmsg could help you spot an issue

Hard to debug without a device in hands

Also, the fact that your brightness doesn't change in recovery while in adb shell with the echo command means there is an issue

Did you try to use higher brightness values than 255, like 1000 or 3000
[Android Software Development] chautruongthinh:
- Why i not got this problem with CWM & CWM advance edit??

- I will try set 1000 - 3000 to brightness, i hope it can fix!!
[Android Software Development] Phil3759:
because they do not use the brightness path which defaults to kernel built value
[Android Software Development] chautruongthinh:
I tried to remove brightness path in my device tree and i got blackscreen with CWM.
[Android Software Development] Phil3759:
because in your device tree, it is used when compiling kernel drivers probably

try to grep for the board/device config flag in your device tree and kernel tree to see where it is used and how

Also, here are relevant parts in my sources:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0-beta/libtouch_gui/touch_gui.h#L59

And try to comment this line and recompile after a clobber:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0-beta/libtouch_gui/gui_settings.c#L1337
[Android Software Development] chautruongthinh:
You can see my dmesg here: http://pastebin.com/WUfJ0eHu

and recovery.log here: http://pastebin.com/6Zr0wHv1
[Android Software Development] Phil3759:
Comment the line i mentioned above
[Android Software Development] chautruongthinh:
I can't fix my problem!! :(:(
[Android Software Development] Phil3759:
Kernel dmsg shows a few led errors

Commenting that line and compile after clobber disables brightness action on start up

Maybe it is something else...

Hard to say without device. Try to disable any qcom time daemon and password check too

Else only commenting a few features step by step will help find the issue
[Android Software Development] chautruongthinh:
You can see the brightness path of my device:

./sys/devices/f9966000.i2c/i2c-10/10-0060/leds/pan_tm_led:
brightness

./sys/devices/leds-qpnp-f54ff600/leds/led:rgb_blue:
brightness

./sys/devices/leds-qpnp-f54ff600/leds/led:rgb_green:
brightness

./sys/devices/leds-qpnp-f54ff600/leds/led:rgb_red:
brightness

./sys/devices/leds-qpnp-f54ff800/leds/led:flash_0:
brightness

./sys/devices/leds-qpnp-f54ff800/leds/led:flash_1:
brightness

./sys/devices/leds-qpnp-f54ff800/leds/led:flash_torch:
brightness

./sys/devices/mdp.0/qcom,mdss_fb_primary.169/leds/[COLOR="Blue"]lcd-backlight[/COLOR]:
brightness

./sys/devices/msm_sdcc.1/leds/mmc0:::
brightness

./sys/devices/msm_sdcc.2/leds/mmc1:::
brightness

./sys/devices/qcom,camera-led-flash.84/leds/torch-light:
brightness

I don't what path is right!!??

+ I tried use Philz Touch of A910 for A900 and it work great!! Pantech Sky A900 is using IPS LCD and A910 is SuperAmoled LCD.
[Android Software Development] danarama:
Hi [MENTION=4666971]Phil3759[/MENTION] - Found a "bug" on 6.50.2 - ot sure if you have seen this before.

Unfortunately I don't have a log as I tried erasing /cache to see if the issue would go away.

I am the Microsoft Exchange Administrator where I work and I thought I would test the remote wipe feature. I've tested before but wanted to see if anything had changed since our upgrade.

Anyway, I sent the remote wipe command and the device booted to recovery. After the time daemon starting message, the android icon and progress bar popped up for about 0.2 seconds. It then rebooted and repeated in a constant loop. No amount of adb or fastboot commands could cause android to boot. I thought this would be due to a script in /cache/recovery/ so I erased it but the loop continued.

In the end I had to fastboot flash TWRP which executed the wipe and allowed me to boot. I was then able to flash philz back and restore my nandroid. Nothing lost in the end but it was pretty painful

Have you seen this before?

Really sorry I havent got a log. Perhaps I can try it again sometime when I'm feeling brave if you need.
[Android Software Development] Phil3759:
Try

/sys/devices/mdp.0/qcom,mdss_fb_primary.169/leds/lcd-backlight:brightness

Logs should be saved in an incremental way. Yes, I'd really like a log + the exact scrip you sent to cause the recovery loop

And please, update to latest version before testing it
[Android Software Development] danarama:
I'll try and build at the weekend.

I've no idea what the script contains. Its just whatever Microsoft has built into the exchange server
[Android Software Development] chautruongthinh:
- You can see my new recovery.log: http://pastebin.com/4ePbtVEs

- I used path:
[Android Software Development] Phil3759:
since CWM is affected on bad paths, the issue is in kernel or selinux permissions

You really have to debug it step by step digging into the sources

I cannot help more here
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION] I was able to fix the usb-otg, but my question is directed at the extra.fstab directions on post 2. I already have f2fs patched into kernel so all I need is this flag? And I dont need this repo here if its in the kernel correct?

TARGET_USERIMAGES_USE_F2FS := true

https://github.com/PhilZ-cwm6/android_system_vold/tree/cm-11.0

And The extra.fstab shown below is for recovery to load f2fs file system faster? Can you explain this? Or anyone?

/dev/block/sda1 /storage/usbdisk auto default default

/dev/block/platform/msm_sdcc.1/by-name/system /system f2fs ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check

Will be posting another update zip, later tonight.
[Android Software Development] chautruongthinh:
I'm sorry for wasting your time. But really, I do everything that you guide me but the results still failed!! I still need your help! :(
[Android Software Development] danarama:
He can't help you debug a kernel or selinux for a device.. This problem is specific to your device. [MENTION=4666971]Phil3759[/MENTION] is the Philz recovery developer, not the whatever-your-phone-is developer.

Ask in your device Q&A section for developer help.
[Android Software Development] danarama:
[MENTION=4666971]Phil3759[/MENTION] - Rebuilt to latest sources and remote wipe worked no issue - so, sorry to waste your time!

I willr elease the latest version to Hammerhead community. Looking at git commits, mainly improvements are back end since 6.50.2... Would you agree? Maybe my changelog should just say "backend efficiencies and improvements" unless there is something there you deem significant for user experience?
[Android Software Development] katinatez:
[MENTION=2872010]rootSU[/MENTION] I built with latest sources. Where is this remote wipe option?
[Android Software Development] danarama:
No, No, it's a remote wipe option in Microsoft Exchange Server, for ActiveSync connected devices (Android E-mail client). On the previous Hammerhead build 6.50.2, recovery went into a failure loop. But with latest sources, it carries out the wipe as expected
[Android Software Development] katinatez:
Oh OK, I don't use Microsoft Exchange but its a good reason to switch now.

Can you explain the extra.fstab the purpose of adding f2fs entries? I posted a couple of post above.

Thank you
[Android Software Development] ALcAtRas500:
Recovery Wiko Rainbow

I have creat a recovery with your tool but after creat and reboot it don't want to start up.

Logs an recovery i have upload.

I hope for help :cyclops:
[Android Software Development] danarama:
I didn't add anything for f2fs in extra.fstab

Only change I made is:

TARGET_USERIMAGES_USE_F2FS := true
[Android Software Development] Phil3759:
The flag is enough

By default, mount options will be set to bare minimal

You cannot use all ext4 mount options with f2fs. To optimize your mounted f2fs partitions, you can specify customized f2fs mount options in extra.fstab

If you look at git commits, you'll see there is a lot fixes and enhancements since 6.50.2

I really have no time keeping the change logs on xda, since they are on git anyway
[Android Software Development] katinatez:
Then my extra.fstab is correct?
[Android Software Development] danarama:
[MENTION=4666971]Phil3759[/MENTION] - please upload latest hammerhead to goo.im

http://d-h.st/5aJ

http://d-h.st/knz
[Android Software Development] remotehugger:
I have a VM S3 - currently using 6.41.6/6.0.4.8 - I don't think this is latest Philz for my phone - can someone please point me to which is the latest for my phone - thank you -

VM GSIII/jdsingle76's deodexed NDC 4.4.2/stock kernel ?
[Android Software Development] danarama:
What's the model number?
[Android Software Development] remotehugger:
knew I should of put that in there - DOH ! sorry about that - its SPH-L710 - stock/rooted/deodexed -

VM GSIII/jdsingle76's deodexed NDC 4.4.2/stock kernel ?
[Android Software Development] danarama:
Yeah that's the latest version for your model. [MENTION=4666971]Phil3759[/MENTION] hasn't got time to build, upload and manage threads for every device. It may be worth asking in your Q&A forum to see if you can find someone to compile it on Phil's behalf. Basically since all the initial dev work has already been done by Phil, it just needs someone who knows how to compile CWM from CM11 sources to take it onboard, although it's all changing to AOSP seeon, so not sure what that will mean for those of us building from source.
[Android Software Development] remotehugger:
OK cool - thank you for your help - I will ask over in my Roms thread if there is anything he can do - thanks again !!

VM GSIII/jdsingle76's deodexed NDC 4.4.2/stock kernel ?
[Android Software Development] danarama:
What I really meant was post a q&a thread asking if ny developers would like to get involved :)
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION] New updated bacon recovery

Changelog

Faster boot

Fixed usb-otg

Updated f2fs commits

Now every feature works on this bacon recovery, no more bugs!

Also have you read or heard of twrp new feature in 2.8.0.1 mtp? Would you consider porting this over to your recovery, when you have time?

Thanks
[Android Software Development] nicesoni_ash:
Aroma file manager is also working without any graphic glitches? Just asking, if not no issues. ;)

_____________

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

Fueled by 7000mAh ZeroLemon Battery
[Android Software Development] Phil3759:
Happily, I got new important projects in my real life.

My time is actually very limited and I can no more maintain this project as I did till now.

The main reason is the probable dead of official CWM and the poorly coded official cyanogenmod simple recovery.

There is only one option left: making the recovery independant of CWM/CM-SR. This involves spending huge time except if it is merged with an official ROM.

Porting all to C++ and breaking with CWM/CM-SR was on my plans. However, because of the above mentioned issues and the limited time I have for the next months, I am renouncing to this.

I could be back in a few months if I can afford it. However, for now, I do not plan to make any new major update, except maybe small commits whenever needed

Thanks to all who supported this project and hope someone else pops up and takes it further
[Android Software Development] danarama:
Thanks for all your hard work! I wish I had skills enough to help take things forward. Good luck for the future mate
[Android Software Development] ykkfive:
some problems observed, couldn't find related posts here

1. sometimes when the partition is formatted, the recovery freeze for a few minutes, and the process cannot be killed. I can see in the log the formatting is done already

2. when the data partition is mounted manually, it fails to install any zip by saying something like cannot mount partition. need to unmount data before installing zip
[Android Software Development] ykkfive:
thanks a lot for this recovery. its the only one I use since day one

good luck
[Android Software Development] devilmaycry2020:
someone can make CWM 6.0.5.0 Advanced Edition / PhilZ Touch 6.57.5 for xperia TX, please. thank you very much
[Android Software Development] Phil3759:
A quick update to not leave things half broken:

Update v6.57.8 / CWM 6.0.5.1 / libtouch_gui 1.41

- fix for ROM OTA updates generating two install scripts (openrecovery + extendedcommands)

- merge CWM updates to selinux permissions for init services

- fix adb for 3.10 kernel
[Android Software Development] radz_:
Wheres the link for jflte? Website is mixed up..

Thank you for the update mate
[Android Software Development] danarama:
He has updated the code. He didn't say he compiled it for every device
[Android Software Development] dolorespark:
Thanks for saying this publicly - it confirms my initial impression of the existing codebase. It's also liberating for those of us who have thought about making significant changes but felt compelled to stick with existing "standards" for compatibility's sake.

I've already demonstrated that it's possible to build PhilZ Touch from an AOSP source tree with the addition of just a few CM repos (see posting 5361 earlier in this thread). Whether any of us can recreate your version of recovery without relying on the CWM repo remains to be seen - but I'm sure at least a few of us will try.
[Android Software Development] rolandvrielink:
is the latest version 6.57.8 working good??
[Android Software Development] Phil3759:
Sure it is possible. You can even keep CM repo or move to Omni or whatever.

However, since the recovery is not part of any team, a huge work must be done to keep updating it whenever the repos and mainly device trees are updated.

The worst part is that users need to add custom flags to their device tree and repos to compile it since they will never be merged to official repos. I have no time to maintain such a project on my own. I also have no time to try joining a team to officially maintain it.

That's why I left it compatible with CWM and stopped at the point where I was about to move to C++. That would break many devices (custom graphics, custom key board files, custom recovery UI file...). Moving to OmniRom sources was another option, but it would need customizing even more repos. The simplest would be to move to C++, keep CM repo as a base and customize the needed repos and device trees.

Anyway, the real life events I got in the last few months are the most important factor in my decision.
[Android Software Development] rogersb11:
Thanks for everything you have done for and to hero all of us. Sad, BUT I'm thrilled you are happy with the decision, I'm sure you will excel at anything you choose. I'll try to help if I can but my android knowledge base is still expanding from not much LOL. Best wishes [MENTION=4666971]Phil3759[/MENTION], we will miss you. Thanks again
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] PHilZ Touch 6.57.8 for Golden, P3100, P3110, P5100 and P5110 as flashable ZIP and Odin-Flashable *.tar.md5

https://www.androidfilehost.com/?fid=23622183712471557
[Android Software Development] katinatez:
bacon device updated

philz_touch_6.57.8-bacon.zip
[Android Software Development] yusopa:
Did you try this update man.
[Android Software Development] katinatez:
Yes I am running it now, but have not tested all functions, fresh out of the oven.
[Android Software Development] twobats1:
Het Phil3759, thanks for all your work and time and a GREAT recovery! Best of luck in your new endeavors!
[Android Software Development] chautruongthinh:
[MENTION=4666971]Phil3759[/MENTION]

- I fixed success philz touch for A910 (VEGA IRON2):laugh:

- I really thanks your help!! Thank [MENTION=4666971]Phil3759[/MENTION] very much!!
[Android Software Development] SoonerLater:
Install via ODIN - What Version of ODIN?

What is the correct version of ODIN to use to install Philz Recovery? Where is it available for download?
[Android Software Development] Phil3759:
can you give me a feedback what was causing your black screen at the end and how you fixed it?
[Android Software Development] danarama:
Any version with support for your model of Samsung phone. Just get the latest from Samsung's website
[Android Software Development] Phil3759:
I uploaded all release updates to goo: falcon, moto_msm8960dt, golden, bacon, P3xxx, P5xxx

However, goo seems to have issues refreshing the files

Will ask them on IRC
[Android Software Development] chautruongthinh:
My device tree & your source are good! Stock kernel has the problem, so i merged stock kernel with caf kernel and the problem was fixed!!
[Android Software Development] Phil3759:
as i thought, a broken brightness path in the kernel

thanks for the feedback
[Android Software Development] chautruongthinh:
I many thank your support!! :good:
[Android Software Development] katinatez:
Same problem with my device, switched out the kernel and everything works!
[Android Software Development] jurben:
Almost same problem with my device. Kernel from ota update (KK 4.4.2) doesn't work in my PhilZ Recovery. Have to use old stock kernel (JB 4.3 stock rom), although the main system is KK 4.4.2
[Android Software Development] katinatez:
Start using prebuilt kernels until you find one that works. I used maybe 4 different kernels then on fifth I got lucky with omni source kernel worked for me.
[Android Software Development] chautruongthinh:
[MENTION=4666971]Phil3759[/MENTION]

Twrp recovery has mtp mode!!

I hope you will add it to your recovery!!
[Android Software Development] donmarkoni:
It has

not working

MTP mode. It would be good to have it, but what's wrong with adb push? ;)
[Android Software Development] chautruongthinh:
- Mtp mode work great with my device!!;)

- I can use adb push but the end user can't do it!! MTP mode is very useful for user.
[Android Software Development] donmarkoni:
Damn your device. :) J/K

Well, cause this is xda-developers and not xda-over-entitled-users I must say I don't care. ;)
[Android Software Development] danarama:
It has not been implemented in any recovery AFAIK. I asked Phil about this before. He said he hasn't time to look at such things and I doubt very much that has changed. He said if anyone was "crazy" enough to try it, it would be TWRP dev. But he hasn't AFAIK
[Android Software Development] BigBugHmb:
Comes the new latest Philz version for S5 and the other devices, too? (Expl. N8000)

Plz… ;)
[Android Software Development] SoonerLater:
I am trying to install Philz Recovery via ODIN per the instructions from the top post, to wit:

boot into download mode

start odin3 and configure it as in picture below

[IMG="Pic from Top Post"]http://img545.imageshack.us/img545/8229/image272j.png[/IMG]

connect phone in download mode to PC via USB

press start to flash the tar.md5 package

normally, phone should auto-reboot into recovery.​

My i337 is rooted and the bootloader is unlocked (I think - see below).

[IMG="screenshot 1"]http://i.imgur.com/Q2GkOQF.png[/IMG][IMG="screenshot2"]http://i.imgur.com/K5B87nG.png[/IMG]

However, when I try to do this, it fails:

[IMG="Odin screnshot"]http://i.imgur.com/iPpyWyi.png[/IMG]

The log in Odin says:

<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jflteatt.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jflteatt.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

What am I doing wrong?
[Android Software Development] hachamacha:
Apparently I must have built the wrong version for my last falcon build, so I just fixed it, links in OP are correct now. Oops.

OH yeah: Thought I'd mention it, although I suspect this must have been noticed already: When building Motorola that uses qcom-common, it appears that for at least "falcon" builds, that qcom-common has been integrated into another common in the CM11 tree (which is a complete mess right now) so to build for falcon, you have to delete ./device/motorola/qcom-common (-rf) and then put it back for say, msm89* builds.

Edit: Just read a new mod on a cm11 wiki that said that msm8960dt is kaput and "ghost" is the new name. I'm building it right now. That is only for .. moto x's and some sony devices. There is still a problem with having qcom-common in the tree during falcon builds but maybe a mod to one of the vendor.mk files will fix that.
[Android Software Development] yishay:
Philz recovery for Optimus 4x HD

Hello

Don't use the 2 last versions, the touch is not working correctly.
[Android Software Development] SoonerLater:
Don't use the last two versions of Philz Touch?
[Android Software Development] Android-Andi:
No problems on Tab2 and S3 mini.

Send from OnePlus One using Tapatalk
[Android Software Development] danarama:
Nexus 5 fine too
[Android Software Development] javvadi:
PhilZ Touch 6.48.4 not able to format Cyanogen Mod 11 Nightlies

PhilZ Touch 6.48.4 not able to format Cyanogen Mod 11 Nightlies. Odin does not detech my N7100. I'm stuck.

formatting /data

formatting /cache

formatting /sd-ext

E: unknown volume for path [/sd-text]

formatting /sdcard/ . android_secure

formatting /storage/sdcard1/ . android_secure...

E: unknown volume for path [/sd-text] is this the issue? can anybody help?
[Android Software Development] danarama:
Sd-ext is a partition you manually create on your removable sdcard. I sincerely doubt you have done this so the error would be normal.

Try posting in your device thread for help from users with the same phone
[Android Software Development] Phil3759:
6.57.9

- fix install in "Free Browse Mode" from non vold managed volumes
[Android Software Development] danarama:
Many thanks. For this

.
[Android Software Development] yishay:
The problem is on Philz recovery for Optimus 4x HD.

For other devices, I don't know.
[Android Software Development] danarama:
Good job we're all mind readers then! Perhaps you should post in the Optimus 4x HD thread so everyone knows what you're talking about.