yashsingh1/xdaforums huggingface dataset:
[Android Software Development] danarama:
No there isn't but if you want to root, the Towelroot app may be able to help you now.

http://towelroot.com/

Hi [MENTION=4666971]Phil3759[/MENTION] - built and confirm extendedcommands are working well with the lock activated. adb and gui completely disabled during normal recovery boot too. Works great. Will update Nexus 5 now...

Thanks for this amazing effort.
[Android Software Development] tomatende2001:
It does not work. :( I will never again buy a phone that is not at least half a year is on the market! :( Then I'll probably use for a while my old Find 5 ... :(
[Android Software Development] diegons49:
Please, update for Moto X.
[Android Software Development] Jansxel:
[MENTION=4666971]Phil3759[/MENTION] So Far P880 Haven't Receive Update [emoji16]
[Android Software Development] EndLess:
Hello sir ....

I am a gr8 fan of u ... i have micromax a177 devices and i wana port ur philz recovery to it ..... plz permit me for porting ur philz recovery to my devices and give it to my fb group members .... :confused:
[Android Software Development] BabboDemonio:
You quoted the entire OP and you didn't noticed that there is an entire section for developers in which it's written " Adding*Full*PhilZ Touch version support for your device"?
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] i updated PhilZ Touch for golden today, adb not working anymore i had no problems on my last compiled...

i also disabled recoverylock again to be sure ...

Any idea?
[Android Software Development] NomadSpin:
request samsung galaxy exhibit t599 and t599v be added in here, and t599n be updated? plz

edit

I am looking for a flashable zip
[Android Software Development] meskes:
Could the device maintainer for the d2lte please fire off an update for platform, if it's ready? Anxiously awaiting to employ the new security features.
[Android Software Development] Groot:
You can always wait for it patiently ?
[Android Software Development] Phil3759:
[MENTION=2872010]rootSU[/MENTION]

on latest version, if users do not have a lock pass, adb will be disabled

I will push a fix later when I have time, sorry
[Android Software Development] Phil3759:
6.47.4 (23.06.2014)

Devs: please update because of the broken adb bug when no recovery lock is defined in 6.47.3

goo is migrating its servers. When done and when I have time to sync and update my device tree, I will release an update for selected devices. Probably same devices that were updated last time
[Android Software Development] danarama:
On it. Thanks
[Android Software Development] key1650:
Posting here because you didn't seem to see the post in Nexus 7 2013 flo thread.

I have noticed one problem in mounts and storage menu it lists all the partition's for formatting see pic.
[Android Software Development] Phil3759:
yes, if I compile flo again, I will disable them

Else, someone else has to continue compiling for flo

But for now, it is on my supported list
[Android Software Development] jurben:
OK. I see the point.

but then ... it seems my softkeys didn't function properly.

every press on any of my nav bar keys give 2 respons:

first key:

Key: 139

Key: 330

second key:

Key: 108

Key: 330

third key:

Key: 103

Key: 330

does below mean something: ? (from /cache/recovery/last.log:

W:minui: /sys/board_properties/virtualkeys.ft5x06_ts is 4 % 6

W:minui: /sys/board_properties/virtualkeys.ft5x06_ts: ignoring unknown virtual key type 102
[Android Software Development] Phil3759:
I should disable the bottom navigation bar in fact. Touch events are reported twice. You can only use 3 keys in that case. Will hide the bottom bar in next update
[Android Software Development] meskes:
[MENTION=4666971]Phil3759[/MENTION]: watching the work you guys are doing simply impresses me. I wish [MENTION=617884]Koush[/MENTION] would be willing to merge some of your features into his mainline CWM tree. Yes, I know you maintain(ed?) mainline CWM for him, BUT your product really does stand out among all others, especially now that you have some features that I'm sure a lot of us have been having wet dreams about. Thank you guys, for this.
[Android Software Development] Phil3759:
6.47.6 (24.06.2014)

Hopefully this should support virtual and capacitive keys on most devices

It also stops the touch events from interfering with the key prompt
[Android Software Development] Ramondel:
[MENTION=643734]Philz[/MENTION] can you please advise who is the owner of the KLTE forum, there have been numerous questions posted about updates to the recovery but no one answers. I do not know who the developer for the post is, any assistance that you can provide is greatly appreciated.
[Android Software Development] Android-Andi:
After sleep :) thanks a lot!

Gesendet von meinem GT-I8190 mit Tapatalk
[Android Software Development] ngochuy:
Please update for htc evo3D. Thanks :)
[Android Software Development] sq3htu:
Any update for GSM version of Galaxy Nexus i9250 (maguro)?
[Android Software Development] danarama:
Could it be possible to show and use capacitive keys, even if user chooses to disable them in the GUI itself? Would give more options for those who hide the keys in GUI
[Android Software Development] Schrotty35:
Hi can you add please Thermal Support in your Recovery for LG G2? Dr87 have make a custom twrp recovery with this great feature. You can look here:

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

Gesendet von meinem LG-D802 mit Tapatalk
[Android Software Development] joni2012:
Hello good work, from m7 ul no update?

Enviado desde mi unknown mediante Tapatalk
[Android Software Development] nikctsh:
Hey man, sorry for this noob question. I try to create a nandroid backup, so I boot into recovery and choose create backup into sdcard. However, instead of a flashable .zip file, I get a folder with a bunch of files. I feel uneasy because from what I remember, years ago when I created a nandroid backup on my motorola device it is a flashable zip file, not a folder. So here's what in that backup folder:

1) boot.img

2) cache.ext4.tar, cache.ext4.tar.a

3) data.ext4.tar, data.ext4.tar.a, data.ext4.tar.b

4) nandroid.md5

5) recovery.img, recovery.log

6) system.ext4.tar, system.ext4.tar.a, system.ext4.tar.b

Is this what supposed to happen when I make a nandroid backup using philz touch recovery?
[Android Software Development] Pons:
Pretty much. It makes a back up of each partition. And I've never owned a phone that doesn't do this.
[Android Software Development] Phil3759:
It is possible, but not sure desirable. Small displays could suffer from this maybe

wired

try to format to f2fs using mounts and storage

then:

adb shell
umount /cache
mount -t f2fs /dev/block/mmcblk0p24 /cache

post any errors

Could be your kernel implementation is missing something. Porting to 3.0 is officially experimental!

As you say, since it is only some users, probably something corrupting their cache partition
[Android Software Development] danarama:
Maybe an option?

Disable virtual keys (x)

Enable virtual keys for passkey (x)
[Android Software Development] Phil3759:
I really suppose that who disables them won't like to see them anyway

I don't feel like adding extra code there, really
[Android Software Development] danarama:
Ok.
[Android Software Development] ali.filth:
Do you know that "something" ? :D I mean, what are the factors that cause it after installing recovery :confused:

and sorry if excessive off-topic, how to restore or repair their corrupt partition or eMMC ?
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] after wipe cache i get CWM Logo in background

Gesendet von meinem GT-I8190 mit Tapatalk
[Android Software Development] Bhargav97:
LoL :D

Btw you can disable logo by going to PHILZ SETTINGS > GUI OPTIONS > CHANGE BACKGROUND IMAGE > TOGGLE ICON.
[Android Software Development] Phil3759:
yeh, it's ugly :D

Thanks for spotting it

Will fix asap
[Android Software Development] johnnyslt:
I run the mount cache command and it got mounted as f2fs.

mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/vold/179:65 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=
007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
[B]/dev/block/mmcblk0p24 on /cache type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,active_logs=6)[/B]

Maybe recovery doesn't know which to mount because they are declared twice? 1st in fstab as ext4, 2nd in extra.fstab as f2fs
[Android Software Development] Phil3759:
No, the file we need is /etc/fstab, generated during conversion and fstab loading

Please post your recovery.fstab, extra.fstab and exact result of this command:

adb shell
umount /cache
mount -t f2fs /dev/block/mmcblk0p24 /cache

Also, please post result of this command when recovery fails to mount /cache:

adb shell
cat /etc/fstab
[Android Software Development] johnnyslt:
recovery.fstab:

# Android fstab file.
# <src>	<mnt_point> <type>	<mnt_flags>	<fs_mgr_flags>
# load these in early-init instead

/dev/block/mmcblk0p22 /system ext4	ro,noatime,data=ordered,noauto_da_alloc wait
/dev/block/mmcblk0p23 /data ext4	noatime,nosuid,nodev,data=ordered,noauto_da_alloc wait,encryptable=footer
/dev/block/mmcblk0p24 /cache ext4	noatime,nosuid,nodev,barrier=1,noauto_da_alloc,errors=panic,journal_async_commit wait,check
/dev/block/mmcblk0p27 /devlog ext4	noatime,nosuid,nodev,data=ordered,noauto_da_alloc wait
/dev/block/mmcblk0p20 /boot emmc defaults defaults
/dev/block/mmcblk0p21 /recovery emmc defaults defaults
/dev/block/mmcblk0p31 /misc emmc defaults defaults

# sdcard
/devices/platform/msm_sdcc.3/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
/devices/platform/msm_hsusb.0/usb1 auto auto defaults voldmanaged=usbdisk:auto

#sd-ext
/dev/block/mmcblk1p2 /sd-ext ext4 rw defaults

extra.fstab:

/dev/block/mmcblk0p23 /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr,errors=recover wait,check,encryptable=footer,length=-16384
/dev/block/mmcblk0p24 /cache f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr,errors=recover wait,check

1:

~ # umount /cache
umount /cache
umount: can't umount /cache: Invalid argument
~ # mount -t f2fs /dev/block/mmcblk0p24 /cache
mount -t f2fs /dev/block/mmcblk0p24 /cache
~ #

2:

~ # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p24 /cache auto rw
/dev/block/mmcblk0p23 /data auto rw
/dev/block/mmcblk0p22 /system ext4 rw
/dev/block/mmcblk1p2 /sd-ext ext4 rw
[Android Software Development] Phil3759:
Enable compression to low setting

About speed, it depends on card formatting and brand. TWRP uses some buffering to improve things on lower quality cards, which cwm do not

Do not post same thing in many threads please
[Android Software Development] JEANRIVERA:
I'm sorry it won't happen again :o
[Android Software Development] Phil3759:
5.07.6 (05.07.2013)
[Android Software Development] zyclops1:
if i flash this recovery,is my device shows as custom,but not official :confused:
[Android Software Development] ztotherad:
hey philz any chance to support your recover for the i605?
[Android Software Development] marcel112:
Philz,

i got a i9505.

I flashed the latest : 5.07.6 .tar using odin.

In odin i cant get anything to change.

The only thing that's ticked is auto reboot...

I cant tick anything or tick off...

Flash goes ok, phone reboots, but in normal..

So i cant untick auto reboot.

Booting using 3 buttons, when i choose reboot i dont get the question: yes- disable flash recovery...

So..... when i want to turn in philz recovery i have to use 3 buttons....

Backing up stock rom now, but will i have philz after factory wipe and flash custom..... lets say liquid..?

What am i doing wrong?:good::good:

Marcel112
[Android Software Development] BillGoss:
I'm a new user to PhilZ, coming from TWRP and using ORS. I have some questions:

1. My TWRP backups are stored on /external_sd. How can I access them in PhilZ? I looked under the Advanced/TWRP menus and I cannot see how to specify the location of the the backups. PhilZ tells me that there are no files, which is true for the internal sdcard.

2. How can I specify that scripted backups should produce backups in TWRP format?
[Android Software Development] eRPeeX:
Read the faq on op 3
[Android Software Development] BillGoss:
Done that. The OP doesn't say that the named locations are the *only* locations supported.

Also there's no mention of wherever there's an option for TWRP formatted backups through ors.

So would the answers to my original question be:

1. You can't access TWRP backups on the external sd card

2. You can't create TWRP backups through ors

Sent from my GT-I9505
[Android Software Development] dragon36:
Just an FYI.. I couldn't build for the d2vzw. I don't know why kept having different weird issues. But decided to try the d2tmo recovery as partitions are the same and everything seems to run OK. I tried backup, flashing, and restoring and it all went OK.
[Android Software Development] Phil3759:
Provide a log

Check if you're missing it because /data/media/0 and the like
[Android Software Development] BillGoss:
Thanks. Your reply made me go back and I managed to find out how to restore TWRP backups from the external sd card.

What confused me was:

1. The menus are under Settings

2. You have to select options and then start a recovery job before it gives you the option to select the location.

But I found it, so I'm good with this.

Can you also please tell me if PhilZ supports creating *TWRP* backups via open recovery scripting (this was my second question) and if so, how to do it.

Creating CWM backups works just fine.

Sent from my GT-I9505
[Android Software Development] Phil3759:
No, I did not implement it

The idea was to offer a more customizable scripting language than extendedcommands for people that prefer cwm

Adding TWRP support is not a big deal though. I will add to my todo list
[Android Software Development] BillGoss:
Can I suggest that it be a setting in PhilZ and not something in the ors script so that scripts remain compatible across different recoveries (TWRP, PhilZ)

Sent from my GT-I9505
[Android Software Development] Phil3759:
Good idea in fact
[Android Software Development] Willy89:
Hi.

If somebody is interested, on my website i have trnslated all the features and stuff of this wonderful recovery in italian.

The translation is also availbale in other languages.

Have a look at it.

Phil, if you appreciate that, feel free to link it on your first post.

Bye.
[Android Software Development] praveenpgeb:
Plz port this for my xperia neo v,,,,,
[Android Software Development] denzel09:
Can you port to lg p760 l9? It has all two most famous recovery.

Thanks
[Android Software Development] Phil3759:
In what they are most famous?
[Android Software Development] denzel09:
For you? In what? Maybe cause they are oldest and best known?

Come on..

If you do not want it s not a problem.
[Android Software Development] Phil3759:
many thanks :good:

The issue is in /etc/fstab generation

I will fix it
[Android Software Development] Phil3759:
Please, to debug it, I need one more test:

can you try inverting the recovery.fstab and extra.fstab entries this way:

recovery.fstab:

# Android fstab file.
# <src>	<mnt_point> <type>	<mnt_flags>	<fs_mgr_flags>
# load these in early-init instead

/dev/block/mmcblk0p22 /system ext4	ro,noatime,data=ordered,noauto_da_alloc wait
/dev/block/mmcblk0p23 /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr,errors=recover wait,check,encryptable=footer,length=-16384
/dev/block/mmcblk0p24 /cache f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr,errors=recover wait,check
/dev/block/mmcblk0p27 /devlog ext4	noatime,nosuid,nodev,data=ordered,noauto_da_alloc wait
/dev/block/mmcblk0p20 /boot emmc defaults defaults
/dev/block/mmcblk0p21 /recovery emmc defaults defaults
/dev/block/mmcblk0p31 /misc emmc defaults defaults

# sdcard
/devices/platform/msm_sdcc.3/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
/devices/platform/msm_hsusb.0/usb1 auto auto defaults voldmanaged=usbdisk:auto

#sd-ext
/dev/block/mmcblk1p2 /sd-ext ext4 rw defaults

extra.fstab:

/dev/block/mmcblk0p23 /data ext4	noatime,nosuid,nodev,data=ordered,noauto_da_alloc wait,encryptable=footer
/dev/block/mmcblk0p24 /cache ext4	noatime,nosuid,nodev,barrier=1,noauto_da_alloc,errors=panic,journal_async_commit wait,check

And do the above steps include cat /etc/fstab

Let me know if it mounts that way

Seems your device cannot properly detect f2fs when fstab is set to auto
[Android Software Development] johnnyslt:
Well it still doesn't mount automatically, but etc/fstab looks good now.

1.

~ # umount /cache
umount /cache
umount: can't umount /cache: Invalid argument
~ # mount -t f2fs /dev/block/mmcblk0p24 /cache
mount -t f2fs /dev/block/mmcblk0p24 /cache
~ #

2.

~ # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p24 /cache f2fs rw
/dev/block/mmcblk0p23 /data f2fs rw
/dev/block/mmcblk0p22 /system ext4 rw
/dev/block/mmcblk1p2 /sd-ext ext4 rw

Just remember, I don't know if my kernel's f2fs implementation is working as it should.
[Android Software Development] Phil3759:
you are doing something wrong here

/etc/fstab should show auto in your case as soon as you have set an extra.fstab entry for /cache

What do you mean by "doesn't mount automatically"
[Android Software Development] johnnyslt:
I meant for /cache partition, which should mount automatically after recovery starts.

Yeah, sorry I've named by mistake extra.fstab to extras.fstab.

Now it shows auto

~ # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p24 /cache auto rw
/dev/block/mmcblk0p23 /data auto rw
/dev/block/mmcblk0p22 /system ext4 rw
/dev/block/mmcblk1p2 /sd-ext ext4 rw

~ # umount /cache
umount /cache
umount: can't umount /cache: Invalid argument
~ # mount -t f2fs /dev/block/mmcblk0p24 /cache
mount -t f2fs /dev/block/mmcblk0p24 /cache
~ #
[Android Software Development] Phil3759:
ok,

now in mounts and storage, format your /cache to ext4

reboot recovery and see if it mounts correctly

I want to know if only f2fs is affected or also ext4 (normally, ext4 should be fine with auto)
[Android Software Development] Phil3759:
many thanks

I will push a fix asap
[Android Software Development] DSA:
Johnny/philz

Now this is a development thread! The last page or two are a great read and giving me help too

Wish all XDA threads were like this..:highfive:
[Android Software Development] rameshsoma:
great work dude :good: .... i need help in fixing a bug can u phelp me with it?

great work dude :good: .... i need help in fixing a bug can u phelp me with it
[Android Software Development] Phil3759:
I pushed 6.47.7 with this commit that could fix your issue:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/39291f30f744ed83d44a7e3d1ebbef7f4e070a68

Now, /etc/fstab should always have the correct fstype when using f2fs/ext4 conversion

If auto mount /cache still fails when it is f2fs, post again exact recovery.fstab, extra.fstab, /etc/fstab and a recovery log

I have a feeling your issue is related to the try_mount code failing on your device for some reason
[Android Software Development] uberto.costanzo:
hi, please what is name for download recovery for i9505? thanks for reply
[Android Software Development] Phil3759:
What happens if you do not use extra.fstab?

Only keep recovery.fstab with ext4 entry. The f2fs will be auto-detected and mount options will be set to bare minimal. Could be an unsupported mount option by kernel implementation

edit: to debug the option that is failing:

adb shell
umount /cache
mount -t f2fs /dev/block/mmcblk0p24 -orw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr,errors=recover /dev/block/mmcblk0p24 /cache

and find the culprit option

let me know please
[Android Software Development] johnnyslt:
Indeed, it seems an option was the culprit

errors=recover

without it f2fs partitions get correctly mounted.

Thanks !

Now my next move is to find out why restoring data to a f2fs partition just stalls. Kernel needs some more work I guess...
[Android Software Development] Phil3759:
Thanks for the feedback
[Android Software Development] FlanjeUK:
jflte (jfltexx is no longer used)
[Android Software Development] Phil3759:
6.47.7 (25.06.2014)

This should be a stable build for the next devices update

I will be compiling for same previous devices

As always, encourage your repo and device maintainers to compile it for you if I don't

goo.im is ongoing a server upgrade. FTP access is disabled since near a week now. I will upload once fixed and notify here
[Android Software Development] joni2012:
Great work, no m7 update?

Enviado desde mi unknown mediante Tapatalk
[Android Software Development] danarama:
Did you read what you quoted?
[Android Software Development] joni2012:
Yes only m4

Enviado desde mi unknown mediante Tapatalk
[Android Software Development] GrandAdmiral:
Is the wifi fix supposed to take long to install?
[Android Software Development] meskes:
I'm not sure we know what you're talking about... I surely don't.
[Android Software Development] rlanza1054:
Hi all,

A quick question:

I am running on an old philz touch, along with CyanogenMod 11.

Can I just boot into philz clockworkmod and apply the updated .img file?

Or do I need to do a total wipe.

I'm currently on philz touch 6 version 6.12.8

Thank you!

Rob
[Android Software Development] danarama:
What img file?
[Android Software Development] Android-Andi:
Totaly forgot to upload for you alos :p

following your filename ;)

For P3100, P3110, P5100, P5110 and Golden as flashable zip & odinflashable *.tar.md5

http://www71.zippyshare.com/v/11925804/file.html
[Android Software Development] Phil3759:
can you do 6.47.7 :p
[Android Software Development] Phil3759:
6.47.7 Updated 69 devices:

You'll need to wait for goo to reactivate ftp access so that I can upload
[Android Software Development] SamsungIsBetterThanApple:
It doesn't support SGH-T959V?!

Sent from my SGH-T959V
[Android Software Development] Android-Andi:
I can rebuild latest PhilZ Touch on Sunday :)

Gesendet von meinem GT-I8190 mit Tapatalk

Edit:

You did already :p
[Android Software Development] rlanza1054:
Sorry if I left out any pertinent information.

I'm using a Asus TF300T tablet that is running CyanogenMod 11 version cm-11-20140625-NIGHTLY-tf300t

Its running on top of philz_tf300t_recovery touch 6 version 6.12.8.

I want to upgrade/install the latest version of philz recovery which according to goo.im is 6.41.6

It downloaded as a .img file.

Is there a way when booted into philz's clockworkmod recovery to upgrade/install this new philz .img file?

I'm sure it can be done when attached to a Windows PC via boot from recovery mode.

I would like to upgrade with the need for a total wipe.

Thank you.

Rob
[Android Software Development] danarama:
Hi Rob,

Thanks for your clarification. You do seem to have got thing's a bit confused though.

Firstly your ROM does not run on top of the recovery. They are both completely isolated operating systems. You run one or the other... It really doesn't matter what ROM is on the phone to update recovery, or even if there is a ROM at all.

Similarly, a ROMs data is irrelevant to the recovery instance - installing a recovery does not need you to wipe anything.

Wipes are for changing roms. The reason we wipe data is if a ROM has different settings stored in /data to what your previous ROM had, those settings in /data will conflict badly.

In regards to flashing img files, they can be done either via a Windows pc or via apps like flashify.

Hope this helps a little