yashsingh1/xdaforums huggingface dataset:
[Android Software Development] aviwdoowks:
1)On my xt907 the ini.bak is in /storage/sdcard/clockworkmod. Yet the only cwm folder that I always maintain is /sdcard1. I & many others only save BUs to extSD so why is not my BU cwm folder also the "home" for Philz? With all the 412, 422, 43 & now 44 options users NEED to know their vital settings are maintained!

I even had a auto usb unmount which occurred coincident with a screen out which I try to keep disabled but it is to hard keep disabled without the ini.bak being read from sd ext.

BTW for many phones that have extSD cards, the default Android internal storage is a blooming nuisance.

I keep a sd swap in effect & keep internal storage at zero MB. But for Philz cwm folder.

The key point is: does a particular phone support a sdEXT card if so then the recovery should adapt.

2)The several, backup & restore > backup to.. options jump right to backing up when touched. How is that a verified input? Yet the when pressing back to cancel the "stop screen/results success " is easy to take as if the backup was a success. Happened 3 times where I thought I had a copy but I had actually miss selected the back on the bottom menu.

3) This is really just a note on how the above could really be changed to allow verification & Maybe a name option (I know that would be in another category of difficulty).

4)There are, at times, when a reboot will cause havoc if done at the wrong time.

Why not make it verified? To work normally, just like when install-recovery.sh is present? Yet when the ...sh is persent you get 3 options:

1)NO : reboot w/ ...sh active.

2)Yes: disable ...sh & reboot

3)go back, which does the same as 1

Choosing 3 should return the the main menu & not reboot.

I added these late btw,

5) partitions the can be formatted need to be Supported/saved: /persist, /firmware, /modem & etc.

6) support for all partitions necessary to run any particular phone, not the case with the msm8960 phones.

Thank You all for the Great recovery!
[Android Software Development] Phil3759:
Sorry, I can understand you are not native English, but some parts are yet hard for me to get...

For path of philz_settings.ini.bak: it can be done, but I am a bit lazy to do it. I would have to default to extra storage path, then if no backup found, look into internal storage. Then, people will come and ask to be able to chose from internal or extra storage. Probably best go would be a browse from path. But, since I added an auto-restore feature, it would have to make a priority between internal / external

To avoid any confusion, I decided to go with ONE backup file. The backup must be in a path existing on all devices: /sdcard

Backup: You have advanced backup restore options

We do not need to confirm yes/no everything, only vital parts. People want quick backups: touch and go

When you cancel backup or restore jobs, you get:

So I do not see how you get success. If you provide a log with success on cancel, I'd be really surprised

4 to 6: I did not get any part of it. I see no need to the partitions you cited except bricking the device

Modem handling is not supported on all phones because many have it locked or unusable. Phones that support it have it. If you miss a partition, post in your device specific thread
[Android Software Development] aviwdoowks:
I can understand you are not native English,

>Native.

but some parts are yet hard for me to get...

For path of philz_settings.ini.bak: it can be done, but I am a bit lazy to do it. I would have to default to extra storage path, then if no backup found, look into internal storage. Then, people will come and ask to be able to chose from internal or extra storage. Probably best go would be a browse from path. But, since I added an auto-restore feature, it would have to make a priority between internal / external

>Are you saying there is something I can do as a user with a SD card?

To avoid any confusion, I decided to go with ONE backup file. The backup must be in a path existing on all devices: /sdcard

> I do not see how having my ini stick all the time is worst.

Backup: You have advanced backup restore options

We do not need to confirm yes/no everything, only vital parts. People want quick backups: touch and go

When you cancel backup or restore jobs, you get:

> The notice in the stop screen is not that noticeable after a cancel, Red maybe?

So I do not see how you get success. If you provide a log with success on cancel, I'd be really surprised

>see above note

4)

> unintended reboot!

5 & 6) /persist in only on the msm8960 phone is it not?

It is not in the rsd xml.

As noted in the xt907 thread.

Why can they be formatted in Philz if there is no restore?

If you miss a partition, post in your device specific thread

Done previously

---------- Post added at 12:43 PM ---------- Previous post was at 12:35 PM ----------

I did some edits not quoted

1)On my xt907 the ini.bak is in /storage/sdcard/clockworkmod. Yet the only cwm folder that I always maintain is /sdcard1. I & many others only save BUs to extSD so why is not my BU cwm folder also the "home" for Philz? With all the 412, 422, 43 & now 44 options users NEED to know their vital settings are maintained!

I even had a auto usb unmount which occurred coincident with a screen out which I try to keep disabled but it is to hard keep disabled without the ini.bak being read from sd ext.

BTW for many phones that have extSD cards, the default Android internal storage is a blooming nuisance.

I keep a sd swap in effect & keep internal storage at zero MB. But for Philz cwm folder.

The key point is: does a particular phone support a sdEXT card if so then the recovery should adapt.
[Android Software Development] r_hippy:
Has this been considered?

I searched high and low.
[Android Software Development] Phil3759:
1 to 3: Things will change as settings file will be probably copied to /cache/recovery to avoid useless partitions mount on every boot. That's important for devs to debug. Only one backup file should exist to simplify code on my side. One backup = One path. Most phones do not have extra storage, we now support USB OTG to complicate things. All devices do have an sdcard and most people do not wipe their /data/media

Now, I can try to add an option to search for backup in extra storage if not found in internal storage. Will add to my to look at list, but not sure

About /persist: I will add it to non mountable / non format-table partitions

Go Back in prompt on reboot options: it was fixed a few commits ago. You'll get it when I update recovery for all devices
[Android Software Development] Phil3759:
no because you need to kill current repo to build this device

I do not have enough resources to maintain 2 separate repos

You need official cwm support on device trees or devs sharing their source changes and adding easy reverse patching to the repo
[Android Software Development] Mr.Tom82:
No it was aimed to c1nd3r.

And OK, I only know that my s2 get a recovery.img flashed. If it contains also the running kernel - don't know it.

But as I said before, the recover.img is stored somewhere and so we can access it and also write to the store. Possibly it is to much work and complicated - so we need to use a other "secure" place.

And for all ppl who say, that it is not secure - one question : is your front door to 100% secure?

When someone has access to the phone and time he will surely find a way - same on your front door.

But ppl who have a limited time will most fail.

Gesendet von meinem GT-I9100 mit Tapatalk
[Android Software Development] tetakpatak:
[MENTION=4666971]Phil3759[/MENTION] you are “the beast", mate....

(a good one) :)
[Android Software Development] shoey63:
Copy philz.ini file to sdcard1 and copy it back when needed.

Use double tap option if you are having problems with accidental validation.

Make sure you see the message "cancelling, please wait.." when cancelling a backup. (keep pressing back button)

It is not possible to support every partition for every device, and the ability to format them is a recipe for disaster :eek:
[Android Software Development] aviwdoowks:
Double tap is only for the menu/lines not bottom keys.

If I disable the keys I get unconfirmed BUs!

Format exists for /persist & /firmware but no bu support! That is the problem. Unwary users see the format commands & use them!
[Android Software Development] NowenUI:
[MENTION=4666971]Phil3759[/MENTION], please make this recovery for HTC One X+ :angel: pleeeese

We really need this wonderful recovery!!

Regards, NowenUI
[Android Software Development] Gho5t_Dog:
You haven't read post #2, have you?
[Android Software Development] danarama:
No he hasn't but we're all supposed to be ignoring those who don't read now ;)
[Android Software Development] Phil3759:
6.10.2 (20.01.2014)

New device:

- HTC One X+ (enrc2b)
[Android Software Development] shoey63:
Seems he didn't need to. He asked, and a couple of hours later, he received :D
[Android Software Development] Phil3759:
LoL

That's why I asked to ignore them

it clutters the thread and waste of time opening it to read if something important

it makes requesters continue asking since they are finally given what they want without searching

I still check requests to see if a device has an official or non official cm repo

Ignoring forces them to look elsewhere

This time, the device tree was recently ported to cm-11.0 officially. He got luck :D
[Android Software Development] MrHomebrew:
Appreciate all the hard work.

I noticed there is a Dual booting/Dual Recovery of this for the Galaxy Tab 3 8.0 did you contribute to making it? Or was it another developer who continued on with your work?
[Android Software Development] metaphz:
Having issues flashing PhilzRecovery with TWRP on a Galaxy Tab 3 8.0 aka T310. Any advice? It's telling me wrong device, I've tripple checked the OP in the Tab sub forum and I've picked the corresponding download with device. It won't let me attach a picture here to show all the errors.
[Android Software Development] gudjer:
Hi there,

which your version should I flash on stock 4.1.2 in order to root and install Kitkat ROM?

Thanks!
[Android Software Development] danarama:
None. This is a recovery. You don't flash on roms.

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

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] ameinild:
I always flash recovery using Fastboot - then you can also just boot to the recovery without flashing it permanently to test it.
[Android Software Development] aviwdoowks:
Is not this a case where the updater-binary in twrp is old?

Get the latest twrp.

The binary is here

http://xdaforums.com/showthread.php?t=2591372
[Android Software Development] adammasri:
Hello, can u port the cwm for Lenovo A850?thanks
[Android Software Development] Phil3759:
I am working on a time fix, thanks to [MENTION=617634]dougiebee[/MENTION]

After that, I am updating all devices before starting to work on a touch module and leave most porting to device owners/maintainers
[Android Software Development] danarama:
3 fantastic pieces if news in one, well rounded post!

*hands up* Official N5 maintainer please? :)
[Android Software Development] titanic_fanatic:
[MENTION=4666971]Phil3759[/MENTION], before your next build for the celoxhd, can you please sync with my upstream repo, your fork is missing 3 of my commits which fix the vibrator in recovery.

https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commits/philz-recovery-cm-10.2

Thanks kindly ;)

P.S. Should this have been asked in my device thread? If so, I appoligize and will note it for next time ;)
[Android Software Development] c1nd3r:
Use Recovery Tools app to flash the new recovery.

Sent from my HTC One Dev Ed
[Android Software Development] metaphz:
I used Odin to flash PhilzRecovery over TWRP and everything went well.
[Android Software Development] danarama:
Nope. Its development related!

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

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:
Np, you're welcome

I think i added your repo to my custom xml. But will ensure i did. Thank you
[Android Software Development] Phil3759:
You mean this branch?

https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commits/philz-recovery-cm-11.0
[Android Software Development] titanic_fanatic:
Yes, that's it ;) thanks Phil.
[Android Software Development] Phil3759:
I see you use google usb vendor id

You have working Mount USB storage?
[Android Software Development] titanic_fanatic:
Yes, it's working. I sometimes have issues while in the ROM, but never in recovery.

Thanks for pointing that out. I'm going to play around with that to see if I can get a more solid connection while in the ROM.
[Android Software Development] Phil3759:
I am curious how it is working

You use google generic usb drivers?
[Android Software Development] AndroZeek:
[MENTION=4666971]Phil3759[/MENTION]

Please post a CWM for Spice Coolpad 2 Mi-496.

We have in Chinese but we Need it in ENGLISH. Thanks
[Android Software Development] sumit227:
I was used chotu's touch recovery then I flashed philz recovery but now I am getting problem I have flashed awesome beat and s4 weather widget it shows installation success but those apps not shown in my app drawer I don't understand plz help
[Android Software Development] ameinild:
2 things:

1) Are they even supposed to show an icon, and:

2) Is this in any way related to the recovery?

I'm not trying to be a **** here, I'm trying to make sure that you get an answer in the right place... :) :confused:
[Android Software Development] titanic_fanatic:
I haven't tested in Windows, but on my Linux box, I have the android.rules file setup as suggested on the Google page for initializing build environment. I think that all of the vendor usb id's are present in that file and wonder if that's why it works. Would I just change the vendor id to the Samsung id or do I also need to change the product id as well?

I'll test on my Windows later on when I'm done working in Linux ;)
[Android Software Development] Phil3759:
Give it a try on windows and let me know please

Both should change in init.rc
[Android Software Development] DreamFX:
any possible way to get f2fs support for the i605? i see in the 5x change logs it was added but even using 6x latest version on i605 it will not read f2fs.
[Android Software Development] Phil3759:
for that you need a kernel that supports f2fs

I do not plan to start to add that fs on kernels. If your rom maintainers do, it will come to recovery

Else, you have to ask some dev in your device forum to compile a kernel with f2fs and repack recovery with it
[Android Software Development] Phil3759:
6.10.6 (23.01.2014)

Update pushed to i9505
[Android Software Development] DreamFX:
I don't want f2fs for kernel. We need an i605 f2fs recovery. The problem is I use Devils Kernel for the T-Mobile version of the Note 2. He made a kernel and recovery with f2fs support. The only problem is the kernel works just fine for Verizon variant(i605) but the recovery does not work right for i605. It only works right for T-Mobile phones. So I can flash the kernel it works great but I can't use f2fs because i605 doesn't have a recovery for it. :( As far as I can tell their isn't really any active devs working on recoveries anymore for i605 they have moved on to other phones. It would be so sweet to try f2fs!!!!
[Android Software Development] Phil3759:
There are 2 steps:

recovery must in fact be compiled with an f2fs flag. That I can do

you must repack my recovery.img and replace kernel I use with yours

Now, about step 2:

- are you able to repack it yourself?

- if not, someone must do

- after that, report if it even boots my recovery since I build on cm-11.0 tree and your f2fs kernel, if repacked on stock, will fail to load a Kitkat recovery

- if after repack everything works fine except f2fs part, I can compile a special version with that flag

Else, it is just a waste of time
[Android Software Development] DreamFX:
I use CM11 with Devil Kernel found here http://xdaforums.com/showpost.php?p=49691392&postcount=7116. As far as repacking recovery.img I have heard of it but wouldn't even know where to start. I know this would be very popular for use i605 folks because a number of us use T0lte kernel on i605 rom. But with no recovery that supports f2fs we will all be stuck...We all love your recovery and would love to see a f2fs update. I can test or help with anything that I can but I'm far from a dev.
[Android Software Development] aviwdoowks:
Edit:

These are few in number, seems the flashing process risky, not sure this means anything at all...

Xt925 & 926, hard bricks now, read only system partitions & 4.3 or 4.4 custom roms.

Caused by twrp 2600 or cwmr 6044 where in each occurrence, an xt925 & 926 system partition got changed to read only!

Does anyone have any thoughts on how to fix or how it could have happened?

One user is trying http://xdaforums.com/showthread.php?t=2551113 as a fix.

They both failed or stalled in rsd @ system.img
[Android Software Development] Phil3759:
Ah, [MENTION=4196889]DerTeufel1980[/MENTION] is providing an amazing support there

Once I move to standalone libtouch modules, the upgrade would be open to all devs

I have sadly little time to do this for a device I do not own. There are also changes to the fstab file system to do. Basically, the recovery won't let you revert to ext4 unless you flash another recovery. Making it switchable needs huge code changes I do not have time to look at or consider for now

Only tasks I plan for now:
[Android Software Development] DreamFX:
thanks for your quick replies. i totally understand.
[Android Software Development] ameinild:
:good::good::good: :victory:
[Android Software Development] andrew.mackew:
Oh, such awesome news! (- update all devices) This sounds really great! I am excited to have this new version. Thank you very much PhilZ. Oh, PhilZ, please, keep up your excellent work for our N7105 (t0lte) and I9300 too.
[Android Software Development] titanic_fanatic:
Hey Phil, mount usb storage works in Windows ;)
[Android Software Development] erickwill:
+1
[Android Software Development] danarama:
Hi [MENTION=4666971]Phil3759[/MENTION] - Nexus 5 doesn't seem to.have backup EFS option in custom. I assume because older nexus devices don't have efs as a partition, it is not an option however, nexus 5 does have efs as a partition. What Info do you need to add it?

/dev/block/platform/msm_sdcc.1/by-name/modemst1

/dev/block/platform/msm_sdcc.1/by-name/modemst2

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

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:
I need the fstype too
[Android Software Development] jordin1128:
[MENTION=4666971]Phil3759[/MENTION] anyway to add a "wipe internal storage option" on the next update?
[Android Software Development] danarama:
Is there an easy way to find out? Its not in mount.

Cant we just dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/tmp/efs1.img;

dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/tmp/efs2.img

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

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:
5.05.7 (30.05.2013)
[Android Software Development] kenzolo:
how can I increase speed of restoring a backup ?
[Android Software Development] timberwolf60:
It will need about 15 minutes for a 3 gb+ backup file to complete. More importance was the backup file can be used for restoring. Speed was not a big deal.

Send via i9505 using Tapatalk,

ROM: PYRANA 1.3 lite, Phil 5.05.5

superSU 1.30, 64GB exFAT Card
[Android Software Development] port76:
can I use v5.0.5.7 on galaxy s4 19505 ?:what:
[Android Software Development] timberwolf60:
Yes, specifically for i9050 s4.

Send via i9505 using XDA premium,

ROM: cf auto rooted ME2. CWM

superSU 1.30
[Android Software Development] Phil3759:
5.05.9 (31.05.2013)

Hopefully, this should be the last minor update/bug fix before moving to next big features (dual boot support, some basic theme support, insecure scrolling option as requested by some...)

All devices will be progressively updated in the next days

New devices support will be completely stopped until todo list is a bit shortened

Only special requests filling these conditions will be looked at: http://xdaforums.com/showpost.php?p=41572323&postcount=180

So, please, do not spam my PM box with useless requests for new devices if you did not fill above conditions

Sorry, but I am really running out of free time with this
[Android Software Development] Shark_1979:
Please make a version for Samsung N7100;)
[Android Software Development] shoey63:
Go here http://xdaforums.com/showthread.php?p=34983286
[Android Software Development] Shark_1979:
I not found new version 5.05.9...:(
[Android Software Development] thatotherguy..:
Can anyone just answer my question, since this works on HTC one m7, will it work on sprint version?
[Android Software Development] DJBhardwaj:
You're doing an amazing job [MENTION=643734]Philz[/MENTION]. I appreciate all the hardwork and time that you're putting in.

Especially, I adore the fabulous UI and color combination that you provide.

[MENTION=684050]users[/MENTION]: If you're new here and your device is supported, don't spend even a second more to read. Just hit the download and flash it!
[Android Software Development] Phil3759:
5.06.0 (01.06.2013)

Another minor update to the source. Pushed for i9505

Remaining devices will be updated during next week
[Android Software Development] mw86:
Thanks Phil im a fan on the i9500.
[Android Software Development] cowsquad:
Awesome touch recovery . well done job
[Android Software Development] tsubus:
This recovery is by far the best for the s3
[Android Software Development] nocoment07:
for when samsung galaxy s3 mini I8190N ?
[Android Software Development] ChitownWingMan:
Please forgive me if this has been posted elsewhere but I searched this thread and google and didn't find and answer?

Is there a version of this that will work on the T-Mobile USA Galaxy S3 (SGH-T999)?

If yes, which version should I download?

My main issue is that the latest ClockworkMod Touch downloaded from clockworkmod.com for this phone (6.0.3.1) does not support exFat and I have a 64GB SDXC card installed, formatted exFat.

Thanks in advance...
[Android Software Development] Phil3759:
Download this firmware from sammobile.com: T999UVDMD5

Extract the zip and rename included tar.md5 to tar

Extract from the tar the recovery.img file

Attach it here

And, I will release a repack for your phone
[Android Software Development] ChitownWingMan:
I have attached the file as per your request

Thank you very much!!!!
[Android Software Development] milkybeans_chocolate:
Sincere request for making Philz Touch on i9000

Hey Sir Phil, could you please make your awesome recovery work on the International Samsung Galaxy S 1 (i9000).

I have tried to download the Roms from samfirmware, but after i have extracted the .tar files, i could not find any recovery.img.

The below recovery.img is extracted from the CWM backup of SlimRoms, which is based on CM 10.1. Also attached please find a copy of boot.img.

Please let me know if you got problems. I would like to be of assist anytime.:cyclops:

MANY THANKS!
[Android Software Development] Phil3759:
well, my code would need some rework to support same current efs backup mode on 2 partitions. Will do once

For fstype, check maybe the fstab file on stock boot.img or recovery.img
[Android Software Development] TemporaryTester:
I see that the changelog for 6.10.6 has changes for the Galaxy S4 and its US variants, but I can't find any updated versions of the US variants' recoveries since 6.08.9.

Are there versions that exist for these devices?