yashsingh1/xdaforums huggingface dataset:
[Android Software Development] fantomel:
Hello Phil, i really like your work and i have used your recovery on many of my devices. I wanted to ask you if you can make one that supports a relative new model of phone, Alcatel One Touch Pop C7 that uses MT6582. Until now the only cwm found for it it's an old standard one 5.5.0.4 that can be generated from boot.img with MtkDroidTools.

I have posted here both of them : https://mega.co.nz/#!XUxF3Sqb!WCQOXGkCBPDIHhugzh3dHsX9zQWEux09SSss7al9pME
[Android Software Development] brian.houaiss:
[MENTION=4666971]Phil3759[/MENTION]

Too many changes from 6.25.7 to 6.25.9?

Thanks!

Ps. My bad, just read few posts ago.. ;)
[Android Software Development] milchmaennchen:
Hi Phil,

thanks for your work.:victory: I am using your CWM for Moto G and would love to see it for my HTC One Mini.

Could you possibly add this device? :fingers-crossed:

I would really appreciated this. Thank you.
[Android Software Development] DSA:
Read the second post
[Android Software Development] Phil3759:
HTC One Mini (m4)

http://xdaforums.com/showthread.php?t=2707387
[Android Software Development] Unjustified Dev:
[MENTION=4666971]Phil3759[/MENTION] what causes a recovery to be rotated incorrectly cwm to be exact on the nvidia shield.
[Android Software Development] forest1971:
Dear [MENTION=4666971]Phil3759[/MENTION],

I would like to implement latest touch recovery as part of a stock based custom kernel for Note N7000. Currently I am using a your old initramfs with Philz touch version 4.9.3.6.

Could you kindly help sharing the newer initramfs or give advice on how I can update the initramfs with latest recovery for N7000 please? There are latest recovery.img you have provided for us but I do not know how to make use of it. :o

Thanks so much for your great work :good::good::good: and with best wishes!

Forest,
[Android Software Development] shoey63:
[MENTION=4576973]forest1971[/MENTION]

I believe these scripts will help.

https://github.com/xiaolu/galaxys2_kernel_repack
[Android Software Development] Phil3759:
i personally couldn't on i9100

Kernel drivers. You have to find it in kernel sources or try the swap x/y flags in BoardConfig
[Android Software Development] dnle71:
Hi! [MENTION=4666971]Phil3759[/MENTION] can you add support for Xiaomi Mi2s? It has a dualboot feature and there's already a compiled one for the device but that was a month ago. Here is [MENTION=313770]m1cha[/MENTION]'s source https://github.com/M1cha/android_device_xiaomi_aries
[Android Software Development] forest1971:
Thank you Philz and Shoey!

If possible, please kindly help me to implement Philz Touch 5.

I have unpack initramfs with Philz Touch 5 from later Philz kernel-LT9 (using Chenglu's tool) for N7000, in the file in the link below. But for some reason cannot make it work in my kernel after keeping the same and trying different changes.

http://www.mediafire.com/download/ls7fmerrzu8xb8b/initramfs-from_Philz-LT9_for_N7000.tar(2).gz

Thanks a lot and best wishes!

Forest
[Android Software Development] k2wl:
@ Phil3759

can you update recovery for i9082 to latest.

and another thing, does your recovery support f2fs formating?

because i am on your latest recovery for i9082, v19.3.

it doesnt format by f2fs.

but i can see commits on github.

thanks
[Android Software Development] Bhargav97:
[MENTION=4666971]Phil3759[/MENTION] will rarely update recovery for all the devices now. Because of libtouch_gui, it's like everything is open sourced and so you or your device developers can make/update the recovery (Yes, with full version).

It would be nice if you take the initiative. :)
[Android Software Development] k2wl:
You mean , take philz repo and build normally?

so i can get philz recovery like i build cwm?
[Android Software Development] Phil3759:
yes, why build CWM when you can build this :D
[Android Software Development] YayYouFixedIt:
Ok i added a thread for the tf701 without touch.

http://xdaforums.com/showthread.php?t=2708724

Let me know if you want me to change anything. :)
[Android Software Development] forest1971:
Thanks [MENTION=4666971]Phil3759[/MENTION] and [MENTION=4675598]shoey63[/MENTION] again very much!!!

I have finally been able to make it to PhilZ Touch 5. Feeling great:victory::good::

Wonderful recovery PhilZ!:good::good::good::good::good:
[Android Software Development] kacrutzz:
hello [MENTION=4666971]Phil3759[/MENTION]

i've been using your custom recovery since galaxy s3.

but i've been missing your recovery after i change to sm-n900 until halaszk88 port it to our device and is working very well.

you can see that in http://xdaforums.com/showthread.php?t=2590320

[Kernel][30-03-2014]halaszk-UNIVERSAL5420

what i'm asking is could you consider to put his your to your first page of the thread and credit to him ?

thanks before, just want to share between two great developers

cheers
[Android Software Development] xperia_88:
m919

I got a lot of problems on my m919 with philz_touch_6.15.4-jfltetmo.zip (stuck, reboot) so I go back to philz_touch_6.00.8-jfltetmo.zip.

Any explanation ?
[Android Software Development] s3icc0:
I read Philz Touch 6.25.9 but for jflte there only is 6.25.4 available. Are you building or is there some problem?
[Android Software Development] danarama:
Perhaps halaszk88 should consider crediting phil? Not even a credit on his github

---------- Post added at 07:26 AM ---------- Previous post was at 07:24 AM ----------

Why don't you build? Why does everyone expect every version without them putting effort in? Phil is not magical. He cannot build every version for every phone. All the info to build is in post 2 so why not do yourself and phil a favour and build it yourself and send files to phil to upload
[Android Software Development] s3icc0:
Sorry buddy ... it was only question ... I am not complaining or blaming anyone ... so take it easy ... I am fine on 6.25.2 ;)
[Android Software Development] danarama:
Well its not really just a reply to you but to everyone that asks. And it is a serious question to all.... why not?
[Android Software Development] s3icc0:
Well I was reffering to the thread description where the newer version is stated ... I understand developers do it in their free time for free ... so even philz will say no more support for any device I will maybe ask for a reason, but what can I do about it? ... well nothing ... or learn to build myself (which is not the case)
[Android Software Development] danarama:
There is no clear policy on what devices will continue to be updated by Phil. One thing that has always been clear however is not every update is relevant to every device so people should not ask why device x has latest version. Phil may plan to update your device in the next few versions or he may not have chance to.

I do think it would be good though if as many people can offer to help support Phil in building for existing devices. It doesn't even have to be you. Your device forum has developers, right? So one of them could post here and learn to build Philz from the Master, then maybe Phil can spend more time on feature development, adding new devices and personal life :)
[Android Software Development] s3icc0:
well I take it as challenge :)
[Android Software Development] BadUsername:
Exactly, cwm and twrp don't give each update to every device, this seems like common sense to me.

I've been noticing much better results with this new method of allowing developers to compile the full recovery. Many developers are submitting their completed versions, it should be taking a lot of the headache away from distributing and allowing development on a larger range of devices.

If this truly gets as big as twrp and cwm, then this is the only method that could work without having an entire team building and hosting. I'm really glad Phil changed it up because it probably future proofed his recovery for any device.

It took a while for our device, but in about 4 months it's already becoming a favorite of our developers. It takes a lot for our developers to switch from twrp to another recovery. Considering how much most of them dislike CWM, it's truly a testament to how amazing Phil does on this project.

Probably too much detail, but thanks Phil, your work is truly amazing.
[Android Software Development] mcwurth:
Hi.

Sorry if this seems a noobish question, but I am rather safe then sorry: I want to update philz touch recovery. Currently I have philz touch 5 installed. Version 6.0.3.7. Do I simply flash the latest version on my s3 or do I need to do anything else first?

Thank you :)
[Android Software Development] II GHOSTFACE II:
Just simply flash it. Nothing more, nothing less.
[Android Software Development] shoey63:
[MENTION=4576973]forest1971[/MENTION]

Why not try Philz touch 6?

Edit: Here View attachment boot.img is the latest Cm11 boot.img compiled with Philz 6.26.1 for N7000. Just rename it to zImage, and work your unpack/re-pack magic ( with a bit of swapping) ;)
[Android Software Development] Sidewindr:
Hi Philz top recovery I must say :D I just have a comment with respect to f2fs, I think it is probably about time f2fs support was included in the recovery. At the very least the kernel and f2fs tools so we can use your recovery to backup and mount f2fs file systems and the tools so we can create f2fs file systems under your recovery.

I have had to switch to TWRP with f2fs on my TF700T and I have to say I don't and have never liked it .. :(
[Android Software Development] forest1971:
Thanks buddy! Will try. :fingers-crossed:
[Android Software Development] Phil3759:
If you succeed in booting new versions on old jb 4.1 kernels for i9100 and n700, please let me know. My quick trials failed and i had no time to work on it.
[Android Software Development] Phil3759:
1- Advanced / Report Error

2- if it is not possible because of the sdcard not mounted:

adb pull /tmp/recovery.log

3- you can just boot into recovery, reproduce the error, reboot to main system and attach contents of /cache/recovery
[Android Software Development] ali.filth:
may I add more devices again phil? :)

Send from my Pager using xda-developers app
[Android Software Development] Phil3759:
Sure, just let me know about their threads and download links. I will pull commits from your git
[Android Software Development] ali.filth:
Ok..thanks

Send from my Pager using xda-developers app
[Android Software Development] thehacker911:
Phil3759:

Where are the hidden all the terms? In what kind of file should I seek? Reboot System Nown, Install Zip etc.

I want to translate it into German

Thank you very much
[Android Software Development] Phil3759:
extendedcommands.c, advancedcommands.c, recovery.c, header files...

Just search in sources
[Android Software Development] manan001:
i hope, waiting for samsung galaxy grand 2 SM-G7102 (ms013g) philz kernel.. and CWM.. .
[Android Software Development] v_superuser:
Here's something!

I:Checking for extendedcommand & OpenRecoveryScript...
I:Skipping execution of extendedcommand, file not found...
I:Skipping execution of OpenRecoveryScript, file not found...
mtd: successfully wrote block at 0
I:Set boot command ""
mtd: successfully wrote block at 0
I:Set boot command ""
mtd: successfully wrote block at 0
I:Set boot command ""
Rebooting...
I:Volume /sdcard is not idle, current state is 0
W:failed to mount /dev/block/mmcblk0p1 /sdcard vfat (Too many symbolic links encountered)
mkdir: can't create directory '/sdcard/': Too many symbolic links encountered
E:Cannot write to /sdcard/clockworkmod/.recovery_version
[Android Software Development] sdeft:
I am having a strange problem. I made recovery with make recoveryimage but when I boot into recovery the default background is distorted. The strange thing is that if I take a screenshot from within recovery the screenshot appears fine on my PC. My device is huashan. What am I doing wrong ?

Here is a screenshot taken from another phone

https://dl.dropboxusercontent.com/u/103997937/cwm_bg.jpg
[Android Software Development] Phil3759:
Post your recovery.fstab

Try

TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
[Android Software Development] v_superuser:
Here's the device tree, I'm on a slow internet connection so can't fetch exact link. :)
[Android Software Development] Phil3759:
Where is device tree?
[Android Software Development] v_superuser:
Oh, sorry, it didn't got pasted. O.o

Anyways, broadband restored so, here's the recovery.fstab that I used:

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

boot /boot mtd defaults defaults
cache	/cache yaffs2 nosuid,nodev,barrier=1 wait,check
userdata	/data yaffs2 nosuid,nodev,noauto_da_alloc,barrier=1 wait,check
misc /misc mtd defaults defaults
recovery /recovery mtd defaults defaults
system	/system yaffs2 ro,barrier=1 wait,check
devlog /devlog mtd defaults defaults
/dev/block/mmcblk0p1 /sdcard vfat defaults voldmanaged=sdcard:auto,check
/dev/block/mmcblk0p2 /sd-ext ext3 defaults voldmanaged=sdcard:auto,check

And I suppose, this commit/recovery.fstab might fix it(I used this one in TWRP) - https://github.com/vaibhav121/cm10_htc_pico/commit/d429a45367dc733d1de7a2aba22d718cec6a33e3
[Android Software Development] Phil3759:
you must comply to vold use

/dev/block/mmcblk0p1 auto auto defaults voldmanaged=sdcard0:auto,check
#debug: comment below line until storage mount is fixed
#/dev/block/mmcblk0p2 /sd-ext ext3 defaults voldmanaged=sdcard:auto,check
[Android Software Development] v_superuser:
Ok, I'll try this, but I need some explanation on this, The log says "W:failed to mount /dev/block/mmcblk0p1 /sdcard vfat" and you commented the line that shows mounting of the sd-ext? How will that help? :)
[Android Software Development] Phil3759:
reading ALL my code will help
[Android Software Development] sdeft:
Tried but now I get nothing on screen but the sony logo. However I can tell that phone is in recovery mode via adb command.
[Android Software Development] Phil3759:
I think sony uses:

TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"

else, your kernel is in RGB 256 and you have no fix except editing your kernel drivers

However, most Sony devices use RGBX_8888, so it should work

Do not forget to clobber or remove all minui intermediates before recompiling with that flag
[Android Software Development] tareq_0:
Where is the last virgin 6.26.1 ?

أرسلت من GT-I9300 بإستخدام تاباتلك
[Android Software Development] danarama:
Wrong forum?
[Android Software Development] ianarellano:
what is the latest version of philz?
[Android Software Development] enigma1981:
JustArchi has compiled us a version of 6.25.0 over in our i9300 thread :)

If that thread doesn't update then the main version updates are irrelevant fur our device.

Swyped from my Galaxy SIII using Tapatalk Pro
[Android Software Development] tareq_0:
Is this the last virgin?

أرسلت من GT-I9300 بإستخدام تاباتلك
[Android Software Development] danarama:
Its a version not a virgin. 2 different things. Don't worry, plenty of virgins left.

Latest version for each device is found in the link in the device thread. Check there. Not every phone gets every version.

---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------

The one in the thread title and in the change log on page 1 of this thread.
[Android Software Development] danarama:
haha no worries.
[Android Software Development] rootlinux:
All this talk about virgins. :)

This thread gets even more exciting. LOL
[Android Software Development] sdeft:
Spot on! "RGBX_8888" fixed it.

By the way when you install the recovery where does it look to restore previously saved settings on devices with both internal & external SDs (sdcard0 & sdcard1) ?

Tried changing below in recovery_settings.c but I don't think it works

struct CWMSettingsIntValues auto_restore_settings = { "auto_restore_settings", 1 };
[Android Software Development] Phil3759:
recoverysettings.h
[Android Software Development] sdeft:
I guess you mean to make a change in recovery_settings.h as below

#define PHILZ_SETTINGS_FILE "clockworkmod/philz-touch_6.ini"

Will build and try again.

One other thing I couldn't figure is how do you set default values in some parameters before you build. For example for menu_height_increase. Are they encoded or something ?
[Android Software Development] danarama:
libtouch_gui?
[Android Software Development] Phil3759:
Settings place:

It is always primary storage. In advnaced_functions.c

Defaults: it is in the libtouch

You can always bundle your builds with a custom settings file you inject during zip install

Just add a shell script to not overwite user settings for people that are updating. For new install, your custom settings are copied
[Android Software Development] sdeft:
Yes I forgot...and libtouch comes as binary.

So if I inject the philz-touch_6.ini during install to the correct location the recovery will read it provided the auto restore settings is also set, correct ?
[Android Software Development] Phil3759:
Main path is /data/philz-touch

Inject it there after checking if no file exists
[Android Software Development] Phil3759:
Galaxy S5 Final

http://xdaforums.com/showthread.php?t=2706253
[Android Software Development] gr8nole:
[MENTION=4666971]Phil3759[/MENTION]

Latest builds for Galaxy Tab 3 (7in) lt02wifi and lt023g.

Thanks.
[Android Software Development] Phil3759:
uploading :good:
[Android Software Development] Pons:
[MENTION=4666971]Phil3759[/MENTION] just ran down an issue with a ROM (and it's probably not the only one out there), that it doesn't have the setuid for /xbin/su so root was improperly detected. Also, su was in two places in the ROM zip, xbin and bin. TWRP handles this well, and fixes dev error that should be fixed in the updater-script. But have you thought about handling this more gracefully in PhilZ? That way PhilZ doesn't get unnecessarily blamed, and takes care of the user? I found the relevant TWRP part so you can see what I'm talking about, but I haven't gone through it with a fine comb yet:

https://github.com/TeamWin/Team-Win-Recovery-Project/blob/twrp2.7/twrp-functions.cpp#L559
[Android Software Development] Phil3759:
Actually i already improved stock cwm code for that following Chainfire directions

By detect, what do you mean?

- Recovery is nagging on exit that root is not properly applied while it is?

Or

- the rom, when flashed has no proper root?

If it is 2nd case, it is because rom dev is not aware of new kitkat requirements to inject supersu daemon

If first case, it could be recovery
[Android Software Development] Pons:
By detect, I mean close to your 2nd case, that rom has no root (not proper or improper, but no). And this (in this case) is not because of new Kitkat requirements, but because of an incorrect updater-script. The su binary wasn't configured properly because it didn't have a set uid and it was in both /xbin/su and /bin/su.

This was because of an incorrect updater-script. In this case, PhilZ was doing exactly what the updater-script said, but that was incorrect and breaking ROM root. TWRP on the other hand, was detecting and fixing the error (by applying setuid, proper permissions, and making sure only /xbin/su existed and deleting /bin/su).
[Android Software Development] Phil3759:
I see

That was what i said. Many release things they do not understand and do not even think to make an effort and fix their bugs

I even saw su in /sbin at root

I am not sure i want to fix such things. Rom maker should

However, i think su installer i use, from Chainfire, should properly do this. If user roots from Philz Settings menu, it should fix such crap
[Android Software Development] migui0401:
¡¡¡PYRAMID!!!

Is there any hope for Pyramid users to get this fabulous recovery working in our phone?
[Android Software Development] ali.filth:
Htc pyramid??

Send from my Pager using xda-developers app
[Android Software Development] migui0401:
Yes!
[Android Software Development] ali.filth:
Ok..just wait..I'll try make it for you..and you must be a tester.. :D

Send from my Pager using xda-developers app
[Android Software Development] migui0401:
Good :good: I'll be tester :D
[Android Software Development] Gold_Phenix:
Please somebody port this recovery to Xperia S. Or tell me how port this recovery?

Wysłane z mojego LT26i przy użyciu Tapatalka
[Android Software Development] Pons:
Good point. The recovery really shouldn't do anything that isn't asked of it. However, maybe add (or rather, enhance) a check that detects if root is properly done. I vaguely recall you had a check for

the daemon. I'm mobile and joy looking at the code, so I could be wrong. But that's why I said enhance, as in add to the check (su proper locations and permissions), then prompt the user that root is probably broken and offer to fix it. I'm just spitballing an idea here.

Edit: and while the fix root option might work (I haven't tested it), the user doesn't know it's broken till after they boot into rom. Right now, they reboot into recovery, flash the rom, find out that root is broken. Then most users will just go ahead and flash their superuser zip of choice (or fix root in recovery). With the check of root I'm proposing, it'll be reboot into recovery, flash rom, then get notified that root is broke;would you like to fix? (maybe add a notice to inform the rom dev of broken root), then fix root and reboot into rom. Sorry, brainstorming here. I'll try to check out the code and see how easy/feasible it will be. Hopefully this weekend, but still moving so no promises.
[Android Software Development] sdeft:
Thanks Philz. It worked.

I noticed that when you perform a "Wipe Data/Factory reset" for the first time it takes very long during or after the formatting of /cache partition. In plain CWM there is no such delay. I had a look in recovery.c related section, tried a couple of things but couldn't figure out what is causing this. What do you think ?

Also the extra code you added for erasing .android_secure from secondary storage looks like it is trying to delete it twice (in recovery.c).
[Android Software Development] Phil3759:
not sure, maybe I look at it once
[Android Software Development] Phil3759:
Here's the commit I made 5 months ago to add suid detection after Chainfire advised me:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/699bee74b028a390a47105e4d3dfb89e909dfc06

Sure we can add some code to detect if there is a stupid su under /system/bin

Many cookers still inject it in /system/bin despite it was always a bad idea. Some even inject it in both bin and xbin or symlink them. That was working in pre 4.3 roms, but not anymore. In any case, it has no sense and I never understood why they do it. Or, let's say, I figured out they just have no clue and copy paste their updater-script code since years without trying to understand things...

Anyway, I am going to commit a quick fix and let you review it
[Android Software Development] Phil3759:
[MENTION=2910818]PonsAsinorem[/MENTION]

It wasn't too hard:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/ae5e455159de9dc862ee42c785b508ab3fa075f8

Let me know if it is what you are expecting