yashsingh1/xdaforums huggingface dataset:
[Android Software Development] captain_nemo:
Hello @Phil3759, Please find the sources...

http://xdaforums.com/showthread.php?p=48190859#post48190859

Device Tree Sources:

https://github.com/varunchitre15/android_device_a110

Kernel Sources:

https://github.com/varunchitre15/thunderzap_canvas2_jb

Please let us know if in any other way we can help here..

Thanks.
[Android Software Development] shoey63:
To prevent "error7", can't default.prop in ramdisk be edited?
[Android Software Development] Ryuinferno:
Actually I do not own the device...it was tested by [MENTION=4675598]shoey63[/MENTION]...talking of that, [MENTION=4675598]shoey63[/MENTION], do you mind to unpack the boot.img and replace the recovery with Philz into the kernel I gave you? Cause the modules are kernel specific...
[Android Software Development] Phil3759:
That's the worst thing with the shared recovery/boot devices

But yes, you could just edit the device specific default.prop things
[Android Software Development] captain_nemo:
Hello @Phil3759 let me know if the Micromax A110 Sources are helpful for you and if you have decided to compile your latest recovery for this device.

Thanks...
[Android Software Development] shoey63:
Alright, I will try with your boot.img
[Android Software Development] Phil3759:
But these are cm-10.1 sources!
[Android Software Development] shoey63:
Using the modules, Exfat 32gb sd card shows up in recovery, but refuses to mount :(
[Android Software Development] Phil3759:
6.01.7 (07.12.2013)

This is a device specific update only
[Android Software Development] C00lBeanz:
Can you add clear ART cache? (Like clear dalvik cache, but with ART instead of Dalvik)
[Android Software Development] Ryuinferno:
ART .oat files are in /cache/dalvik-cache or /data/dalvik-cache as well...
[Android Software Development] Phil3759:
Thank you for the clarification since many are hammering just because dalvik was renamed to ART

if (confirm_selection( "Confirm wipe?", "Yes - Wipe Dalvik Cache")) {
__system("rm -r /data/dalvik-cache");
__system("rm -r /cache/dalvik-cache");
__system("rm -r /sd-ext/dalvik-cache");
ui_print("Dalvik Cache wiped.\n");
}

So, recovery wipes all of this when asked
[Android Software Development] Phil3759:
I started synchronizing to cm-11.0

This will mainly permit to support most recent devices that only have a cm-11.0 tree
[Android Software Development] tdhite:
I believe I know the issue -- it's called dork user! I'm fairly confident that, after trying to reproduce last night, and thinking about it, it was nothing more than a hold/move which was mapped to toggle screen in gestures (default). The only thing I can say is that I honestly would have expected the power button to revive the screen, but my suspect is another hold/move would have done it.

PhilZ still is the best recovery -- stable as a rock and full of features! Cripes -- doesn't get much better than that.

Now I have to figure out if it's compatible with the latest ViperOne ROM.
[Android Software Development] denizenx:
Hi, where do I download this?

Can't find a URL here
[Android Software Development] Ramondel:
Downloads are device specific, if you go to post 1 find your device forum, the download will be there.
[Android Software Development] captain_nemo:
Hello [MENTION=4666971]Phil3759[/MENTION], We don't have cm-10.2 sources till now...These are the latest approved one I provided you. Sources are not provided by OEM. Some Devs are creating by their own. I gave you varun chitre's sources for 4.1.2

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

You can have a look at these sources based on 4.2.2, though it has controversies

https://github.com/ajaybhatia/canvas2

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

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

Thanks..
[Android Software Development] Phil3759:
Well, sadly I have no time to port from scratch devices I do not own

All i need is a device tree i can build under cm-10.2

Without that, I cannot build

Again, I am very interested to test my new MTK fixes for boot/recovery
[Android Software Development] donmarkoni:
Hahaha... :laugh: I like your issue explanation. ;) I was pissed when I saw that and didn't want to answer. Why would one use this recovery if doesn't even know all the functions. :mad:

And about ViperOne: sure it is! :good:
[Android Software Development] II GHOSTFACE II:
One would use this as a recommendation as many would give because as its mentioned a fantastic recovery. Not everyone must/will know all or even most the functions. As I'm for one who doesn't know all the functions nor need to but still use it as I like the opportunity to use a wide select of functions if the matter is needed/or if curious. This is the only recovery I've tried on this phone and don't plan to change because phil has created this masterpiece so I'm not even tempted by twrp or nothing.
[Android Software Development] tdhite:
What is not explained by even my own admission of probable user error, and implicit in this entire discussion, is that the backup should not have started on a hold/move operation, yet it surely did, and with the blank screen no one would know. So there's a 'there' in there somewhere if the developer cares to address it some day.

No worries. I take the comment to heart -- I've developed many products (enterprise, mobile and consumer level), and user error is always frustrating to developers.
[Android Software Development] Phil3759:
I could reproduce it on my device

You have to read the OP and read through the features/guide

This recovery supports gesture actions

By default, a long touch outside menus will turn off screen

However, on latest version, it seems sometimes, when screen is turned off, a next touch can wrongly validate a menu

I will fix it
[Android Software Development] II GHOSTFACE II:
My comment is nothing regarding the users issue but only the fact of "why would one use this recovery if doesn't even know all the functions" my point being its a great recovery and I don't know all its goodies but use it as its the best in my opinion. But I see that comment as if you don't know all its functions you shouldn't use it which is not the case.
[Android Software Development] aviwdoowks:
I found that the many input options were daunting when I first started the v5. But I am glad I can turn all those inputs off & leave just double tap.

It could come to us with safer mode enabled :o .

I wish the ini.bak was read from extSD or I had the option to choose as I use a SD swap & keep data/media zeroed out.

When switching to 4.4 roms & back to 4.1.2 the ini.bak is gone.

I think the original (cwmr) touch interface is flawed & deadly to use. Too easy to double touch your way to a formated sd card in a flash.
[Android Software Development] Phil3759:
the full touch mode in this recovery is largely secured

It is the only mode I use and i have 0 issues
[Android Software Development] aviwdoowks:
"Safer" was a poor choice, maybe just simpler.

The legacy of the original's interface, I believe, could haunt user's perception of your extensive & needed rework.

Especially in light of twrp's successful solution to the original's touch problems.
[Android Software Development] cnn888:
hi phil,

i have been using your recovery for my note 2. it was working fine until suddently i cant access my extsd from the recovery. it says error mounting extsd. tried to reflash the rom and the recovery but still i cant i access the extsd card. tried to reformat the sdcard into fat32/exfat, no luck.

could you help me please?

thanks.
[Android Software Development] NX01:
I would like to report a small bug; when I press 'Reboot System Now' there are 4 options;

- No

- Yes - Root device

- No

- GO BACk

I choose the 'Go Back' option and the phone still reboots :)

Info:

GT-I9505

Philz Touch 6 / v6.0.4.5
[Android Software Development] aviwdoowks:
I believe that is how Koush intended it. All versions do that. But I agree it should abort the boot. Maybe Phil.. can make it right. I am so used to it that way......
[Android Software Development] Phil3759:
6.02.1 (08.12.2013)
[Android Software Development] skatlyup:
Hi,

Really want to install this via Odin but in the instructions for installing:

"start odin3 and configure it as in picture below"

The picture doesn't show.

What settings should be selected and not selected?

Thanks.
[Android Software Development] tungkick:
can't you guide build phizl touch by untubu, i wan't build sky vega 870L, i port PhilZ Touch nexus 4 ok for sky a870l ok but Touch not workking.please help me thank.
[Android Software Development] Android-Andi:
What device do you own?

Make sure KIES

NOT

running, and

no

KIES process running in Background!

Run Odin as Administrator,

Choose philztouchrecovery.tar.md5 as

PDA

in Odin,

make sure "Re-Partition"

NOT CHECKED!

Auto-Reboot checked

Boot your device into Download-Mode

Connect with PC, MessageBox in Odin shows "Added!"

Press Start in Odin.
[Android Software Development] adearinn:
using XDA Premium 4 mobile app
[Android Software Development] electricsheepdreamer:
Pic link is broken.
[Android Software Development] youp20:
Hi, i have version 5 installed with omega 14. Can i backup EFS with it ?

Thanks,
[Android Software Development] danarama:
This is the development thread. Your question doesnt appear to be development related. User queries belong in device specific threads

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Android Software Development] Android-Andi:
repo updated? advanced cwm shows advanced 6.01.5
[Android Software Development] killerbyte:
How do I figure out which S4 I have?

I live in South Africa, got my device through Cell C. I have the GT-I9500 with the Exynos processors. But all the recoveries listed for the S4 above are for the GT-I9505 models.

Would really love to install this recovery but I don't want to brick my device.
[Android Software Development] Phil3759:
I will, but changes are little and device specific. Others are at ramdisk/kernel level
[Android Software Development] danarama:
All supported devices are in post 1. Click the i9500 link

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Android Software Development] Phil3759:
v6.03.1: Migration to cm-11.0 branch completed

cm-10.2 is dead, sadly

However, I am not updating soon all devices, only those that need it because of bugs or no cm-10.2 tree

Last released recoveries for devices that got a 6.x version is more than enough

So, do not hammer for updates

[MENTION=2872010]rootSU[/MENTION], I will look at Nexus 5 device
[Android Software Development] haybill:
Hi [MENTION=4666971]Phil3759[/MENTION],

Not sure if you want us to post general comments in this thread or device specific- anyway, been a lot of chat recently on the Ditto DN3 ROM v.3.1 thread about problems using v.6.0.0.8 when installing with Aroma- folks are recommending going back to v.5.15.0 to avoid issues.

What's your opinion, please??

Just noticed that there is an update after 6.0.0.8 (6.0.21 , I think it was) anyway have downloaded that since chances are you have ironed out any minor issues.

Personally I preferred 6.0.0.8 due to fix for constant request to repair my root which was obviously already OK.

So, thanks for all your excellent work as usual, man.
[Android Software Development] katinatez:
Trying to create a .ors file to wipe everything, kind of like a superwipe. Can I use wipe S for wiping system?
[Android Software Development] katinatez:
My next question is how to set ors directory to sdcard1 & multi_flash to sdcard1?
[Android Software Development] Phil3759:
Ors can be set in misc nandroid settings

Multiflash, you create folder in external storage and remove it from internal
[Android Software Development] katinatez:
This is how I say Thanks, Confirmation number: 6T7839272H804750J

Last Question. How to set default backup format to TWRP format?
[Android Software Development] Phil3759:
Thank you for your generosity.

Sadly, default backup format cannot be set to twrp for now

I could add it in the future
[Android Software Development] danarama:
Thanks [MENTION=4666971]Phil3759[/MENTION] - I moved home last weekend so I haven't had chance to get my 13.10 build environment tested with official CM / CWM sources yet...
[Android Software Development] Android-Andi:
I compiled Advanced CWM 6.03.1 using CM11 Source.

SlimBean 4.3.1 Stable 2.2 flashing without problems,

flashing blackhawks-NEXT-kernel gives "assert failed: (...) Status7"

flashing the kernel (worked before on cm10.2 source compiled recoverys). i got the same error after compileing twrp on cm11 sources.

Any Idea?

recoverylog here: http://pastebin.com/zugMYXUy
[Android Software Development] Phil3759:
If your device recovery has the proper assert, it could be the update-binary. It was updated in kitkat. Old update binaries cannot be installed in kitkat based recoveries

He must use an update-binary from cm11 nightlies
[Android Software Development] Android-Andi:
Ah ok... but that sucks :p i can´t flash CM10.1.3 too :p

If it´s up to the updater-binary means that all recovery´s compiled on CM11 source are not able to flash older roms and files... ?

removeing the getprop from updater-script works to flash the kernel... i couldn´t find any differnts between cm10.2 and cm11 source in that direction... build.prop is the "same" :/

i know that busybox not working on CM11 for p31xx... something to do with it?

do you have the same issue on your device?

Edit:

Or something to do with this from log?

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /preload during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!

Edit2:

Changeing the updater-binary worked too (instead of removeing all "assert(getprop xxx") from updater-script)

On CM11 compiled recovery´s won´t support "old" Roms and Flashable files with old updater-binary or with "assert(getprop xyxx)" in updater-script... that´s sad because not all files and roms will get an update :/ i am sure not everyone understand how to make the changes... this will make the recovery not that "universal" as it should be (that´s what i think).

Latest recoverys compiled on CM10.2 source can flash "everything" (incl. KitKat Roms) wich makes them more userfriendly and much more "universal".

Would be great if there is another way to fix this issue...
[Android Software Development] BadUsername:
Hey Phil,

Just wondering if you could possibly support the Verizon galaxy s3 (d2vzw). We had an unofficial port from the T-Mobile variant, but the thread is pretty much dead now with no activity from the OP. We have the 5.15 version, and we recently have cm11 support and that recovery won't work with kit-kat.

I'm not sure how easy it is to port over, if it's easy enough I would like to learn how to do it, but I'd need help knowing where to start and what to change specifically.

Thank you! it really is the best recovery I've used.
[Android Software Development] Phil3759:
I see there is an official cm tree for it

Will add it to my to do list
[Android Software Development] Phil3759:
That's exactly what I told you in fact

Sadly, I have no clue and no time to look at the issue

It is probably related to the new changes in bootable/recovery/updater
[Android Software Development] Praxisi:
Could an option to exclude specific directories in a list or from a file be added for Nandroid backups?

I particularly wish to exclude my Nexus 7 storage directory for regular backups, and exclude Nandroid backup directory when I want to backup storage.
[Android Software Development] houseofkrazeesstl:
Where is the download link? I cannot find it...
[Android Software Development] Android-Andi:
links to all supported devices in first post,download links in device specific threads.
[Android Software Development] Somcom3X:
Phil I can't install the 4.4 touch says assert fails. Kind of like the issue a few posts up
[Android Software Development] Phil3759:
6.03.5 (11.12.2013)

[MENTION=2872010]rootSU[/MENTION]

Check PM in few minutes
[Android Software Development] Phil3759:
Nexus 5 is [MENTION=2872010]rootSU[/MENTION]

:D
[Android Software Development] danarama:
Thank you for this! It's really excellent!
[Android Software Development] erickwill:
WOW! Thats great, thank you for keep your work up! Looking forward to get this updates for N7105 and I9300 soon! :)

God bless ya!
[Android Software Development] madvj:
I am on sprint version and on MK2 official rom, How can i flash the latest recovery? i was only able to download the zip file which i cannot flash. Any odin package?
[Android Software Development] TonyStark R.I.P.:
Phil, does your "touch recovery" work in the same way as OUDHS touch? It is a full touchscreen swipe

Thank you
[Android Software Development] Setialpha:
May I request philz touch for the Galaxy Tab 3 10.1 (P5210, the x86 one)?

There's already CWM: http://xdaforums.com/showthread.php?t=2432467

and TWRP: http://xdaforums.com/showthread.php?t=2442915

but philz is just muuuuuch better (and I'm using it on my ARM devices). I know there isn't much afford for x86 devices...
[Android Software Development] Siberian Tiger:
Nope it is a lot better. I guarantee you!!!

If there is a Philz recovery for your phone don't hesitate to flash it ;).

You won't be disappointed.

XDA Moderator
[Android Software Development] tOrNadO™:
[MENTION=4666971]Phil3759[/MENTION] Is it possible to make one of these for Xperia S?
[Android Software Development] danarama:
Yes possible. Read post 2

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Android Software Development] aviwdoowks:
On the msm8960 moto phones, for example, I can load Rom Manager on my xt907 & load the xt897 Q recovery. Then flash philz from there.

I wonder if any of the sg s2 recoveries in RM could provide the same convenience? But you need to be sure. Maybe someone has done it.
[Android Software Development] Phil3759:
Hopefully no :D

This is full touch, real full touch + kinetics + secure touch = no validations by error

I was about to release it and got a great support from devs. However, it would mess all my current device tree and I am low on resources to keep in sync with two versions. The time is the most limiting factor.

For now, I stick to devices with stock cm compatibility. However, cm team is working to add x86 compatibility, so hopefully one day...
[Android Software Development] TonyStark R.I.P.:
Sorry for the inconvenience
[Android Software Development] Phil3759:
see pictures in OP here:

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

Bottom virtual buttons can be hidden if you do not like them, in GUI Settings

They just offer an additional comfort to full touch. Some users prefer them
[Android Software Development] danarama:
Read FAQs and check settings. Post user issues in your device thread

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Android Software Development] TokedUp:
Hey Phil! Thanks for this awesome recovery! I'd like to put a vote in for S3 VZW 4.4 version if I may. Thanks again!
[Android Software Development] Phil3759:
Galaxy Note 3 - N9005

Alpha!!!

http://xdaforums.com/showthread.php?t=2567283
[Android Software Development] Setialpha:
I see, but that sounds good, I mean you don't read anything regularly about cm-x86.
[Android Software Development] Phil3759:
6.03.8 (13.12.2013)
[Android Software Development] Saluco:
Hi

i am on Galaxy note 2 using Philz recovery 5.15 in combination with Phoenix Rom 15.7 (JB 4.3)

i am encountering an error when im restoring a backup ERROR WHILE RESTORING /data tahat i didnt had before and this happens even with backups that i restored previously without problem

i copied the backups to another sd card (to be sure is not a card problem) and internal card and the same error appeared

as a mention i use High compression (since im a backup freak and i do a lot of backups)

i did a thorough chkdsk on sd card...no errors found

ill attach the log here

error at some

tar: can't make dir data/data/com.samsung.android.writingbuddyservice: I/O error

tar: can't create directory 'data/data/com.samsung.android.writingbuddyservice': I/O error

tar: can't remove old file data/data/com.samsung.android.writingbuddyservice/lib: I/O

EDIT :

even xda wont upload the log :)))

Upload Errors

philz_recovery.log:

Invalid File....i renamed to txt ;)
[Android Software Development] Phil3759:
you are out of space in data

Will add to my todo list
[Android Software Development] Saluco:
TNX I noticed that after i used Superwipe from Android rev which wiped my internal sd card to i restored without problem

whats the solution for future...move apps from internal to sd card ???

second

your recovery v6 sd fix or not doesn't recognize external sd card.../ cant mount aam i missing something ?? (i read that new cwm doesn't recognize some about new file structure or something...i didn't understand very well)

Edit: and BIG TNX FOR (very fast and prompt) SUPPORT
[Android Software Development] Phil3759:
Update 6.04.0
[Android Software Development] hypnz:
Phil when you update the repo of the devices doesn't update automatically?
[Android Software Development] Phil3759:
https://github.com/PhilZ-cwm6/philz_touch_cwm6/commits/cm-11.0
[Android Software Development] Mokka1:
sorry wrong thread
[Android Software Development] danarama:
This is the development thread. Not user support thread. Please see links in post 1 to supported devices. Follow link to your device and post there

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Android Software Development] tdhite:
Sprint HTC One: m7spr or m7wls

Working lately testing many ROMS and really want to stick with PhilZ because it is very, very trustable. However, most of the ROMS (actually all) I've been working with (e.g., InsertCoin, ViperOne ...) list ro.product.device as m7wls.

PhilZ (or is it the underlying CWM?), on the other hand, sets ro.product.device to m7spr, even though it keeps both ro.product.name and ro.product.board as m7wls.

The most recent TWRP sets the device to m7wls, which is obviously different than PhilZ's value. What that causes is to load certain ROMs, we have to load TWRP instead of PhilZ because the ROMs expect the value of m7wls. Indeed, the build.properties of the ROMs I've been checking all use m7wls as the value.

Is there some particular reason PhilZ sets the device to m7spr uniquely (whereas name and board remain m7wls)?
[Android Software Development] Phil3759:
Probably an issue with your cm device tree

Will see if they fixed it
[Android Software Development] Gold_Phenix:
Can you add full support last cwm in app from 1st post clockworkmod premium to my phone lt26i locked bootloader I always want install last cwm or twrp recovery now I have cwm v 6.0.3.2 .Sorry for my English. I'm from Poland.

PS. I buy this app in google play if you add full support lt26i locked bootloader :) . I only want install allays latest cwm or twrp recovery.

Wysłane z mojego LT26i przy użyciu Tapatalka
[Android Software Development] Phil3759:
Note 10.1 2014 LTE

http://xdaforums.com/showthread.php?t=2570829
[Android Software Development] TokedUp:
Will any other of the S3 variants in the OP work for VZW?
[Android Software Development] danarama:
S3 variants are not compatible with each other. Think about it, it needs a kernel... are the other variants' kernels compatible?

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit