yashsingh1/xdaforums huggingface dataset:
[Android Software Development] tetakpatak:
No, you are not the only one.

I highly appreciate, admire this feature.

It is essential thing for us, who use f2fs :D

tetakpatalked from Nexus 7 flo
[Android Software Development] abhishek 9650:
help me plz

hi guys

i have spice mi 436 smartphone with stock recovery and android 4.2

i want to install recovery on my device .

i have mtk 6572 device

with mobile uncle tools

and plz tell how to install it
[Android Software Development] Phil3759:
To all developers: stick to 6.30.1 until i update thread

My git is currently work in progress, include 6.30.2
[Android Software Development] hachamacha:
6.30.1 is up for moto_msm8960:

Reverted 4 changes that made up 6.30.2. Sorry about that.
[Android Software Development] buggerritt:
I'm confused. Does this mean to not use 6.30.2?

On the grid via GoldenEye+Domination +Wanam Xposed enhanced l337 on AT&T's 4G LTE network.

Wurrrrrrrrd!
[Android Software Development] hachamacha:
Yeah, it reverts to the new ./recovery/libtar/.. again and apparently is in 'fixing/testing' mode, so might not restore some ROM/Devices /data partition correctly. I never saw 6.30.1, but got to it by reverting the 4 little changes in 6.30.2.
[Android Software Development] eris23:
I reverted my mako build to 6.30.1.
[Android Software Development] andrew.mackew:
[MENTION=4666971]Phil3759[/MENTION]: Your work is awesome and pretty much appreciated, however we are missing your updated recovery for t0lte and i9300. Could you please update those devices since there is no developer working with? Thanks in advance.
[Android Software Development] manan001:
Does this work on samsung galaxy grand 2 SM-G7102

Chipset MSM8226

Device Type. MS013g
[Android Software Development] peter.neilmann:
+1

I make your words mine.
[Android Software Development] caspertechno:
black screen!

I downloaded this and tried to flash it using Odin on my GT I9100, it got stuck on Nand Write!

Luckily I was able to boot into download mode and flashed Jeboo kernel! then I copied the zip file and tried again! it is being installed but when I boot to system, I'm getting a black screen. Please help!

PS: My S2 is running stock rom with root!
[Android Software Development] yuweng:
n00b coder here, looking at these codes here & here makes my head spinning uncontrollably . . . :laugh:

Thank you so much Phil3759 for constantly improving Philz Touch . . . :good:

As Phil3759 says here so go away & go compile your own, there are already tons of guides when success then follow the instructions here, REALLY its not that hard . . . :D

Try BBQLinux . . . :good: Let him/ her concentrate on improving the sources . . . :o Whoops, sorry i donno Phil3759 is a he or a she . . . :laugh:

When i come to know a particular DEV at XDA that i respect/ admire i'll do profile checking to get to know them better . . . :cowboy:

Is this the same Phyto Wardt . . . :o
[Android Software Development] manan001:
Are I asked because supported device are listed on first page so asked such question..
[Android Software Development] maleksa:
Meizu MX3

Can you please add support for meizu mx3? Mx3 users still don't have custom recovery :/

Thank you!
[Android Software Development] Gho5t_Dog:
Have you read post 2? You can do so yourself. ;)
[Android Software Development] Pons:
[MENTION=4666971]Phil3759[/MENTION] since certain kernels (most? I never looked) are not compiled from source, but are default stock kernels, we might have to move away from this sooner. Unless it's magically already supported, but here's some relevant commits for the m7 variants:

block: support volname for HTC devices with proc/emmc support

m7-common: use by-name paths for partitions in fstab

Edit: unless CWM/PhilZ is backwards compatible. I'm just not sure how the kernel will handle it since it's prebuilt/unknown (to me).
[Android Software Development] anagramgenius:
Cannot find the recovery for Xperia ZL

Cannot find the recovery for Xperia ZL:confused:
[Android Software Development] pmorales:
[MENTION=643734]Philz[/MENTION]

I am using in my S5 Exynos SM-G900H, your 6.27.6-k3gxx, and while in recovery the only drive it sees is the internalSD, nothing with externalSD neither OTG, so no backup/restore nor zip flashing from those invisible drives. What do you suggest I could do? Thanks in advance Phil.
[Android Software Development] reynierpm:
Can I use this release in Moto G GPE (Falcon)? How I flash in stock acquired phone? Any guide or help?
[Android Software Development] Pons:
I do see a release for the falcon in the OP. Check out your device's forum for rooting and flashing recoveries. The answer is probably there.
[Android Software Development] danarama:
Please post in the official device thread. This is the development thread.
[Android Software Development] acabreram:
is this available for xperia Z1 Compact D5503 (amami)??

Thanks!!
[Android Software Development] danarama:
What does post 1 say?!
[Android Software Development] shoey63:
Xperia users who want Philz recovery on their device can get it here

All you need is stock kernel plus root.

If you want it on a custom kernel, extract Philz from the install package for your device and follow this guide.
[Android Software Development] Polloos:
Thanks for your work [MENTION=4666971]Phil3759[/MENTION]!

I'm compiled Philz recovery for LG L9 and work for all variants (p760,p765,768 and p769)

LG Optimus L9

My source with a commit for support LG L9: Philz_touch_cwm6

Internal sd not work, only change extra.fstab for work or another file also?
[Android Software Development] yuweng:
Been playing with voldmanaged for the past few weeks so i'm good at hunting for fstab v2 . . . :laugh:

Trial & error with your vold.fstab may be it can mount both sdcard while at recovery . . . :fingers-crossed:
[Android Software Development] acabreram:
But that is dual recovery and i would like jus philz cwm. How can o get it? Thanks!
[Android Software Development] shoxxy:
My Friend yuweng Posts a very easy way HERE , so EVERYONE !!! could with only a few steps build his own Philz Touch from Source ;)

Regards :highfive:
[Android Software Development] tetakpatak:
Despite that fact it will quite for sure work just as normal recovery.

tetakpatalked from Nexus 7 flo
[Android Software Development] metaphz:
I have an older version installed 6.08 to be specific. I want to update to 6.19 to have the latest. I downloaded the lt01wifi package for my Galaxy Tab 3 8.0 SM-T310. Do I Odin this or just flash the zip in PhilZ?
[Android Software Development] Phil3759:
I have no m7

Are you sure stock kernel doesn't handle it?

Could be only a cm kernel bug

Their kernels for the variants are buggy and slow. At least they were for months

Please adb shell in recovery and just try virtual path
[Android Software Development] rmleloup:
Did this with and without the auto reboot.

Auto reboot, goes into OS not recovery.

Root is pre verified working. (Using cpu overclocking tools, no frills, setcpu, etc, they asked root with super user, worked).

Trying to use Odin3, v3.09. Supposedly I get "passed" after it fully boots into the OS, but not true when trying to get into it...

I've done without reboot, and let it sit there for 5mins straight. (Not a new OS, so would expect 10-20seconds, not 5mins to succeed). Tried the Vol+, Home, Power trifecta, and no dice, shows the following info below..

In blue I get "recovery is booting"

In red directly below "recovery is not seandroid enforcing".

After which it reboots again, samsung logo and goes to standard boot.

Please advise suggestions. I am using the following .tar.md5

philz_touch_6.12.8-hltecan.tar.md5

I have the N900W8 model note 3. Canadian model. (Nice phone btw).

I have previously removed the microSD card, (64gb) just in case that may interfere, as it did my S1 way back... (old smaller models).

Looking forward to your educating me in betterment. :)

- RMLeLoup
[Android Software Development] danarama:
Please post in your device thread. You need help from your peers with the same phone not the recovery dev
[Android Software Development] ruadus:
Stuck at boot after flashing recovery

Hi,

I just flashed the latest version on my Galaxy Note N7000, when I was rebooting, it asked me to fix root, I said yes. Now it won't boot, it stuck at the logo screen "Galaxy Note N7000".

It' can't access also to the recovery.

Any advise please?

Thanks

----------------Resolved----------------------

I've downloaded PhilZ-cwm6-XXLT4-OXA-4.93.6.tar.md5 and flashed it with Odin, it resolved my boot issue.

don't know why it happend but at least it's resolved.
[Android Software Development] Darian71:
Forgive me if I too am posting in the wrong thread, but there's not alot of feedback in my ROMS Liquid Smooth 3.0.

I recently updated to your latest recovery for my d2lte. Amazing work again my friend and I thank you for all your hard work and dedication. I'm just wondering, why I am now getting the message after each flash of their nightly saying "please update your binary", I've never messed with updating a binary, unless it is talking about updating my super su. And I also now receive the root not detected after pressing reboot, and am asked of i want to apply root. I press yes, apply root each time and I suppose it does because my device runs fine. Any feedback would be greatly appreciated, and if I need to take my questions to my forum I surely will. Thanks. ✌
[Android Software Development] hachamacha:
Probably in the wrong thread. When I test my fresh builds of Philz Touch recovery, one of the things I do is install a nightly cm11 ROM I don't normally use, and it nearly always asks me (UPON BOOT) to update a) SuperSU binary and b) Busybox binary, or it does so when I use something that uses them (like say .. Titianium Backup or Root Explorer). BUT: That's only upon boot into the cm11 ROM, not during recovery.

My main question for you was "Does it tell you this message (which seems pretty vague) in Philz Touch recovery?" . If it does, then what is the exact wording? My guess is that since is that over the last few versions the recovery has become conscious of whether the ROM you're flashing is using an up to date "updater-binary" script. I suppose it could be that, and to get rid of that message, the ROM developer has to get up to date with the rest of the android world. Tell the developer of the ROM if that's the case, so in his thread. - cheers.
[Android Software Development] rmleloup:
I used the Odin method he described thoroughly, and used the one he provided for my phone, entirely separate from the phone specific thread, but his work itself. Would like to learn more directly from OP regarding this.

- RMLeLoup
[Android Software Development] sshafranko:
Need help please. Im on TMO N3 using hlte 6.25 installed through recovery tools. Every time I restore a backup or flash a new rom with a full wipe I get this at boot. Also happens with TWRP 2.7. Much appreciated.
[Android Software Development] Pons:
[MENTION=4823274]Darian71[/MENTION] [MENTION=2658922]hachamacha[/MENTION]

http://xdaforums.com/showthread.php?p=52138483
[Android Software Development] Darian71:
Yes, I'm on Philz Touch 6.26.6, it tells me after I choose the zip to be Installed, Philz Recovery says "installing update", then tells me it is updating binary, then please update your binary and finishes Installing the zip. When I press reboot system, it immediately goes to a screen that says "root not detected, would you like to apply root", and has the options to choose no or yes.
[Android Software Development] hachamacha:
Check out the post above yours in reply to yours and mine and explains the problem.

It's by [MENTION=2910818]PonsAsinorem[/MENTION]:
[Android Software Development] sshafranko:
Basicaly the simple anwser is update to 6.26.9 and your problem will be gone.
[Android Software Development] Darian71:
Was thinking the same thing, however, the d2lte only shows my current version uploaded on the 15th of April. I don't see version 6.26.9. Unless it was in the github and I missed it.
[Android Software Development] Pons:
Check your device's thread. Maybe you have a different maintainer. Or compile on your own. Phil can only do so much.
[Android Software Development] cassinni:
will flashing this recovery increase knox? i am 0x0 now and want to stay with that
[Android Software Development] FlanjeUK:
Flashing any custom recovery on a knox enabled handset will trip knox...
[Android Software Development] mltan_bdo:
CWM Recovery

Hi there, is this recovery SELinux support?

I want to install pawitp ROM CM11 for GT-I9082....
[Android Software Development] Darian71:
I use this recovery on my Galaxy Grand duos i9082L and it works just fine. Here's the updated link now maintained by xenon92. He does alot of development for the Grand.

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

[RECOVERY] [OFFICIAL] [CWM v6.0.4.8 Advanced] Philz Touch [v6.27.4]
[Android Software Development] shoxxy:
flipped screen

Hey.... :highfive:

I (we) have the following Problem on different MTK Devices :

i have to flip every recovery for my device, i am trying This and This way to flip the screen. the Touch function i flip succesful with " flip flags " from your recovery.

it works so far but only when we press the Virtual keys, the "inverted" screen is shown for a short moment, when pressing another place on screen it works normaly and very fine !!!!!

i could confirm that problem is on different MTK Socs !!! when this is fixed for me, i have an very very nice Working Philz on my MTK !!!!

THX alot for this awesome Work !!!!

{ Sorry for Bad English }

Best Regards !!!!!!
[Android Software Development] hachamacha:
[MENTION=4666971]Phil3759[/MENTION]:

Recently I decided to create some up to date builds for old devices of mine, a galaxy nexus(toro) and also have done the msm8960dt unified build (which is OK). The toro 6.30.1 build doesn't boot after install, just sets at the power-up screen with the lock on it. I used the template of the zips you made for 6.19.3 for the .zip version, and replaced recovery.img with mine (6.30.1). I also build CWM stock without problem. No errors in either build, but neither boots on the toro phone. It's all done from a completely clean install on Ubuntu 14.04 which I'm testing out.

As you've said before "You missed something" is likely the case ;) I'm curious if you've got any notes or memory of something special that needs to happen to produce a good build for the nexus. Restoring is easy. I just get to fastboot, do a flash of 6.19.3 and it's good again. It's already in BoardConfig.mk so I'm hoping the #defines are correct. I've got no logs right now but am rebuilding the stock CWM once again to be 100% that it does or doesn't work.

Thanks.

Edit: I just got CWM stock to work on my last build. I hate to admit it but I think I've gotten some builds confused during the copying process at the end. Made a script and possibly renamed it but forgot to edit it doh! Trying a build of Philz Touch now.

Last Edit: I've got Philz Touch built up to date for the galaxy nexus. I think it was some silly copying the wrong device's output file type of mistake.
[Android Software Development] ddhernandez:
Philz Touch can't moun external sd

Hello. When I enter to install Zip then Choose zip from / external_sd I can't acces. There's no problem with sd card. i can acces it with file explorer, i can listen to music and view photos and videos. I can transfer files from the pc to the phone. The sd card works fine. And I'm sure, the zip file is in the memory card.

I change philz for CWM 6.0.4.7 and still have the same problem. I even use another sd card. I can't figure out what the problem is.

Here are screenshots from Philz Recovery and the recovery log

View attachment 2723410

Hope someone can help 'cause want to install a rom in my Galaxy Core.

Thx!!
[Android Software Development] haybill:
Hi [MENTION=4666971]Phil3759[/MENTION]

Sorry to probably repeat a request [ not that I have read a previous request but chances are good that someone will have asked before...] is there any chance of your porting your Touch Recovery for the International version SM N900 Note 3?

I see that Halaszk has done the job--is this the one you would recommend--or do you plan, in the future, to make a version?
[Android Software Development] meskes:
Um... A kernel is compiled with every ROM, unless you make the decision not to include the sources...
[Android Software Development] Phil3759:
someone needs to release a usable device tree first

I have no time for that as I do not own the device and users feedback is very rare to develop something on it
[Android Software Development] haybill:
Thanks for the info--cheers.
[Android Software Development] Phil3759:
6.40.1
[Android Software Development] Bhargav97:
[MENTION=4666971]Phil3759[/MENTION],

Good job with updates!

However, Here comes some conflicts/problems with Custom Key Mapping:
[Android Software Development] Phil3759:
update your custom keys file

https://github.com/CyanogenMod/andr...mmit/2cc22971e40a0ffc7849cdf09dc96916c22136e0

those functions were removed from cwm now
[Android Software Development] matrixzone:
[MENTION=4666971]Phil3759[/MENTION]

Hope we get d2lte updates this time
[Android Software Development] Pons:
That's not correct. For one, I was referring to this and CWM recovery, not a ROM. And two, you can set the compile process (whether a ROM or recovery) to use a prebuilt kernel versus a compiled with kernel.
[Android Software Development] hachamacha:
[MENTION=4666971]Phil3759[/MENTION]:

I don't think they need their own threads but you can decide.

Moto's are yet untested builds, so no links until later this week when I get one. Nexus is something I had laying around so they are tested and OK.

I've got a few scripts setup to do the syncs and keep them up to date (well, at least maybe weekly). Also: The moto_msm8960 thread is up to date on 6.40.1.
[Android Software Development] mathew1234:
How do we backup efs on this.. (Using lg g2)
[Android Software Development] manan001:
tried to compile but getting error can anyone help me .. i have a request if you can help us to create on custom recovery for samsung galaxy grand 2 SM-G7102... it has 4.3 JB
[Android Software Development] Phil3759:
6.40.6 - Stable

Mainly for developers porting new devices to make life easier

BRIGHTNESS_SYS_FILE is now optional flag and can be detected or error silent out if it fails to detect

Galaxy S5 Exynos decided me to do this. Also, many people that wanted to compile, the BRIGHTNESS_SYS_FILE was a too tough thing for some
[Android Software Development] reynierpm:
Can I install this on Moto G GPE?
[Android Software Development] Walmer:
Hi,

Can I just flash the lasted zip using the default recovery of my S4 GT-I9500??
[Android Software Development] ali.filth:
hi [MENTION=4666971]Phil3759[/MENTION] ,

last night I asked Ahmad Amarullah / [MENTION=402300]amarullz[/MENTION] (AROMA founder) about how to flip the screen on AROMA file manager and he gave me a little advice.

this is my first change : test 1

but not working, and I made ​​a second change : test 2 but still the same result.

maybe you have little idea for this :D

thanks
[Android Software Development] Phil3759:
Maybe you are not talking about same thing

By flip we mean x/y axis coordinates. Not in any manner flip screen from portrait to landscape

That is done at kernel level

The flip/swap coordinates is only a touch driver workaround
[Android Software Development] yuweng:
[MENTION=4666971]Phil3759[/MENTION], i use this TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID flag & got error . . . :o

Tried it at Android.mk but no effect, MTK devices has no serial no. so TWRP backup folder is named 0000000000000000

ifeq ($(TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID), true)
LOCAL_CFLAGS += -DTW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID
endif

When enabled by default at Android.mk Line131 then got below error . . .

bootable/recovery/advanced_functions.c: In function 'find_file_in_path':
bootable/recovery/advanced_functions.c:373:5: warning: implicit declaration of function '__popen' [-Wimplicit-function-declaration]
bootable/recovery/advanced_functions.c:373:8: warning: assignment makes pointer from integer without a cast [enabled by default]
bootable/recovery/advanced_functions.c:385:2: warning: implicit declaration of function '__pclose' [-Wimplicit-function-declaration]
bootable/recovery/advanced_functions.c: In function 'get_device_id':
bootable/recovery/advanced_functions.c:3424:9: error: 'for' loop initial declarations are only allowed in C99 mode
bootable/recovery/advanced_functions.c:3424:9: note: use option -std=c99 or -std=gnu99 to compile your code
bootable/recovery/advanced_functions.c:3424:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
build/core/binary.mk:512: recipe for target '/home/yuweng/cm11/out/target/product/MediaTek/obj/EXECUTABLES/recovery_intermediates/advanced_functions.o' failed
make: *** [/home/yuweng/cm11/out/target/product/MediaTek/obj/EXECUTABLES/recovery_intermediates/advanced_functions.o] Error 1
make: *** Waiting for unfinished jobs....
[Android Software Development] Phil3759:
Thanks for the details

I just committed 6.40.7 which fixes all the recovery warnings and your compile error

About TWRP backup folder, it is the way TWRP does and I need to stay compatible so that TWRP recognizes backups done with PhilZ Touch
[Android Software Development] Miguelost:
nice work philz, but you can add a feature "protect with password"

put a password to access recovery function (and prevent other person flash a rom in a stolen phone)
[Android Software Development] geokilla:
Will Grouper be part of the next update? It is outdated and missing some crucial features. Plus CWM backup and restore does not seem to work properly.
[Android Software Development] Bhargav97:
[MENTION=4666971]Phil3759[/MENTION],

UPDATED ARMV6 BATCH to 6.40.1

Download links:

galaxy5

gio

tass

cooper

beni
[Android Software Development] Phil3759:
You could fix your background issue?
[Android Software Development] Bhargav97:
Noup. I was very busy, so... :(

Koush background: FINE!

Solid Colors Background: FINE!

Toggle Icon: FINE!

Only problem is: PhilZ Default Background. Rebooting after setting this background gives us a SOLID BLACK background.

I changed from GUI Preferences > Change Menu background > Choose from sdcard and now it works fine! I used the bg that is in your sources.

fyi: screenshots are from Galaxy 5.

So I'll have to give a "philz-touch_6.ini.bak" file and the theme file and the custom_res folder in a flashable zip? OR any other way?!

About Bugs:

The PhilZ-Default BG bug mentioned above. Partially can be fixed as i said.

NONE except some layout fixing like: progress bar while install/backups, android progress logo while install/backup, etc are not well fitted and progress bars are just not working. All these didn't work / was same way faulty in stock CWM. So, your recovery can't be blamed. Battery, Brightness, Time, Screenshot, AROMA FM (now with original colors!!), gestures, Hard-keys and everything's working.

BTW, doesn't screenshot gesture OR any other gestures work while install/backups?

Awesome Recovery...I had to say! this recovery made all armv6 devices alive! I just used it in my Galaxy 5 (finally got JTAG done) and it rocks! :good:

I changed my ARMv6 threads to XDA-DevDB and have added you as a contributor. You can always EDIT project and first post. :)

P.S. Forget everything I said about that Android Logo...Just forget it....Nevermind it. ;) :D
[Android Software Development] Phil3759:
What is your device screen resolution ?

Wired background works on manual selection and not on start after compile. Seems for me a missing background/flag or something similar on compile time

Check the ramdisk output on your cm/out/project/device/recovery/root/res/images/stitch.png

It should show the pink PhilZ Touch background, else something went wrong during compile time

Gestures are disabled outside menu screens for safety reasons (to not break backups/installs under some circumstances)
[Android Software Development] tetakpatak:
SGS5? Full HD (1920x1080)

tetakpatalked from Nexus 7 flo