yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] CNexus:
Clean to install a new rom option, it wipes system, cache, dalvik, and data (but not internal sdcard)
[Sprint Samsung Galaxy S III] kingarthur72076:
Thanks...

I also have some old files from some other roms that won't delete on the internal rom(last time I tried). What would I need to do to clean up the empty folders
[Sprint Samsung Galaxy S III] prboy1969:
If you are certain they're from a previous Rom, you can use a file explorer to delete them.

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] Swamphound:
... or if there's nothing on your internal card/storage you have to have (like backups) wipe it too. When I go from ROM to ROM, esp. Between AOSP & TW I accumulate a lot of junk and an internal wipe is like cleaning house. You can back up all your files to your laptop and restore what you need.
[Sprint Samsung Galaxy S III] kingarthur72076:
Tried it again...yes I used file explorer but still can't delete the 2 folders. Next ROM install I'll try formating internal storage
[Sprint Samsung Galaxy S III] Mr. Struck:
Did you set read/write permissions for the file explorer? On ES File Explorer it is something that has to be enabled before performing root actions. Also, have you tried connecting to your computer via USB and deleting the files that way? Just brainstorming here.
[Sprint Samsung Galaxy S III] kingarthur72076:
Just checked file explorer...no permissions options. Maybe I'll try ES explorer. I also tried connecting the phone to the computer...still can't delete them.
[Sprint Samsung Galaxy S III] Mr. Struck:
Has been my file explorer of choice for years now. To set permissions, open the app, press the top left icon (looks like a phone in front of a globe), choose "Tools" and then "Root Explorer." Grant Superuser permission when that pops up, then choose "Mount R/W" from the menu that pops up. Change both toggles from "RO" to "RW" and you should be set.
[Sprint Samsung Galaxy S III] kingarthur72076:
Okay...I'm a idiot. I was using the stock my file explorer. I loaded the file explorer in the play store and checked root access...that worked.
[Sprint Samsung Galaxy S III] kaos420:
So when I go into recovery I see this "error could not unmount data after data/media setup"

Anyone know how to fix?
[Sprint Samsung Galaxy S III] Swamphound:
Not sure if you'll find your answer here but read over #5 in FAQ:

http://xdaforums.com/showthread.php?t=2201860
[Sprint Samsung Galaxy S III] prboy1969:
Just had to do a bunch of flashing on a device with CWM Touch Recovery. After using having been using Phil's Recovery for the past few weeks, it's a very noticeable difference. I would say that CWM Touch is good for the average user, that does not do a lot of flashing. But if you like to flash Mods, and try different Roms than Phil's is the Recovery you want to be using.
[Sprint Samsung Galaxy S III] J. Terrell:
^^^ +1000

SPH-L710, CM11, Kt747, OKJ.
[Sprint Samsung Galaxy S III] Swamphound:
+2000! Got a vzw LG G2 coming to test and the first thing I checked when deciding was whether or not there was a Philz recovery for it. :thumbup:
[Sprint Samsung Galaxy S III] houseofkrazeesstl:
Is there anything special I need to do to install on a stock KitKat? I just updated to it after re-flashing an older stock rom to get KitKat.
[Sprint Samsung Galaxy S III] houseofkrazeesstl:
Is there a new download link & MD5? The link in the OP isn't working.
[Sprint Samsung Galaxy S III] Mr. Struck:
Being able to use Philz is an important factor for sure! You should post sometime in the "other devices" discussion thread so we can get your take on the G2.:good:
[Sprint Samsung Galaxy S III] Swamphound:
You got it. Look me up in the Philz LG G2 thread.
[Sprint Samsung Galaxy S III] Mr. Struck:
Will do! That phone does seem to be the best one available right now, looking forward to seeing your opinion.
[Sprint Samsung Galaxy S III] fishingmedic:
Has there been a fix for the screenshot issue? I've been following the thread but have not seen anything to date.TIA
[Sprint Samsung Galaxy S III] Mr. Struck:
I know this has been touched on before, but the only thing I miss about TWRP after switching to this recovery is the ability to name backups before making them as opposed to after. It is a pretty minor thing, but is there any way that can be implemented? Like I said, minor issue, and definitely NOT complaining, Philz has been unbelievably awesome for me!
[Sprint Samsung Galaxy S III] Phil3759:
I plan to add a keyboard, in the bottom of my dream list, if I ever have time

Not a big deal as my modified GUI already can handle gesture actions, however, it is a lot of work to start with

We're also running low on space for many recovery partitions. So, adding jpeg support is a priority before even thinking at this
[Sprint Samsung Galaxy S III] Mr. Struck:
Oh, like I said no biggie, certainly not a deal breaker! Please keep up the good work, your recovery is getting a ton of love over on Android Forums for rooted Virgin Mobile and Boost SGS3 users.
[Sprint Samsung Galaxy S III] kookykrazee:
I finally got my S3 to install PhilZ, awesome let me say, love the touch aspect of it, wishing it was bigger font for my fat fingers but I can work with that. What I am curious of. After I installed PhilZ I updated to CM11 nightly build, from 1210 and now if I use the CM updater it reboots, like I accustomed to with 10.1 and 10.2 but it reboots into recovery and then prompts me "am I sure I want to install untrusted file" I confirm yes and then it reboots without installing. Any ideas?
[Sprint Samsung Galaxy S III] Mr. Struck:
I don't have an answer to your main question, but you can customize how large each line is in the interface, which is like changing font size in a way. I upped mine to accommodate my fat fingers, among many other user interface tweaks available.
[Sprint Samsung Galaxy S III] kookykrazee:
Thanks for the info on the UI, I hadn't had a chance to go in and look through those options. Now just to figure out the cmupdater booting directly to PhilZ instead of installing the update. I figured out a temporary way to get around this, just go back a screen, do it as install zip, manually, and the CM11 nightlies install fine.
[Sprint Samsung Galaxy S III] Eric4753:
Do you have a logo of your recovery program I could use in a signature?
[Sprint Samsung Galaxy S III] CNexus:
I don't, but I bet [MENTION=4666971]Phil3759[/MENTION] could whip one up or maybe even has one handy that he could give you
[Sprint Samsung Galaxy S III] Eric4753:
Thank You
[Sprint Samsung Galaxy S III] Mr. Struck:
All of us on Android Forums who utilize XDA as well are absolutely obsessed with Philz Touch and recommend it non-stop. Thanks to Eric4753, we are looking for a more visual way to display our preference for Philz Touch.
[Sprint Samsung Galaxy S III] monke30butt:
A quick question. .....I flashed the comadose mod & lost root as a result, I rerooted with PhilZ here but Philz gave me a prompt about it was removing SuperSU. I cannot find any super user app in my phone now. The app I had came prepackaged in the All In One rom. Does anyone know what PhilZ replaced SuperSU with? I started to download SuperSU from the market but icon is different & didn't want to duplicate super user apps if one is already there. I do have root access right now.

What did PhilZ do?
[Sprint Samsung Galaxy S III] Mr. Struck:
You need to flash the SuperSU zip version 1.80 from recovery.
[Sprint Samsung Galaxy S III] Eric4753:
any updates with the logo?
[Sprint Samsung Galaxy S III] averyboots:
HELP!!

Ok, so I was going to upgrade from MOAR 6.1 to MOAR 7.0.1 and many comments said to use Philz Touch recovery, so I flashed it over TWRP and did a backup and then the wipe to install new rom, but I believe Philz created a new folder (sdcard1) and I couldn't find the zip file in the files listed, so I was going to just reboot to find it and move it but it said I lost root and did I want to root the phone. I said yes and hit reboot and I have been stuck on the boot screen for the last hour! Can someone please tell me how to get my phone unstuck so i can go back to recovery and load the backup.:crying:

---------- Post added at 11:23 PM ---------- Previous post was at 10:26 PM ----------

Ok, I guess I paniced! I got it back up however the back up I made for moar will not load from Philz recovery, but I had another one that did load from when I used CMW recovery.
[Sprint Samsung Galaxy S III] fishingmedic:
Forgive my ignorance in advance, first time user of PhilZ recovery. Used it to flash MOAR 7.0.1 yesterday, wiped data and factory reset, does that wipe internal SD card as it says to flash to a new ROM, I assumed it wiped everything? If not how do I go about doing that in PhilZ? I moved important stuff to my external SD card, flashed, set up, but now there is still older items on my "phone" when I connect to my pc to transfer files back to the phone.
[Sprint Samsung Galaxy S III] dreigle:
Where do you go to fix permissions? I've been thru every menu and don't see an option for it
[Sprint Samsung Galaxy S III] Swamphound:
There's no option for that with Philz. You can do it with the ROM manager app.

Sent from my VS980 4G using Xparent Green Tapatalk 2
[Sprint Samsung Galaxy S III] Phil3759:
New home:

http://goo.im/devs/philz_touch/CWM_Advanced_Edition
[Sprint Samsung Galaxy S III] milky1112:
Just wanted to say Thanks. Just got around to flashing this recovery on my phone after putting it on my sisters S3, Really digging it over all. So thanks for the hard work. :D
[Sprint Samsung Galaxy S III] averyboots:
I tried to install through Philz and the install was aborted. I get an error message that it can't locate the file. Am I doing something wrong?
[Sprint Samsung Galaxy S III] jdelano:
how are you attempting to install?

you should just download the zip for d2spr, copy to sd card, boot to current recovery and flash the zip from the location you placed it on your SD card, then reboot to recovery
[Sprint Samsung Galaxy S III] prboy1969:
Just wanted to say thanks for the best Recovery I've ever used :thumbup: . The latest release is working great.

TEAM MiK MikROMs Since 3/13/11

---------- Post added at 07:59 PM ---------- Previous post was at 07:57 PM ----------

Make sure to verify the MD5 checksum before flashing.

TEAM MiK MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] bigwillyg:
Oh sweet, an updated version. What changed?
[Sprint Samsung Galaxy S III] averyboots:
I just downloaded the zip and tried to install from within the recovery. I will try copying to sdcard and flashing from there. Thanks!!
[Sprint Samsung Galaxy S III] sickboy82:
You sure it was the zip and not a tar file?
[Sprint Samsung Galaxy S III] averyboots:
Yes, positive...
[Sprint Samsung Galaxy S III] chuckenheimer:
I'm seeing an issue that may be more related to permissions than Philz Recovery but here goes:

E:Can't open /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't open /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

E:Can't open /cache/recovery/last_install

E:Can't open /cache/recovery/last_install

Was curious what may be causing this display when I boot into recovery? Anyone have any ideas? Thanks!
[Sprint Samsung Galaxy S III] Phil3759:
Format cache
[Sprint Samsung Galaxy S III] marcran75:
Since I've updated the recovery won't let me add a custom background. It reads the photos but when I click to apply them the screen goes blank for a moment and then still shows the same screen.
[Sprint Samsung Galaxy S III] shababhi:
switching from TWRP

Can I flash this zip from the TWRP or will that cause a soft brick since there will be two custom recoveries?
[Sprint Samsung Galaxy S III] bigwillyg:
Sorry meant to quote, not like.

To quote the highlander "there can be only one". If you flash from twrp, next time you go to recovery it will only be philz.
[Sprint Samsung Galaxy S III] shababhi:
Thank you.
[Sprint Samsung Galaxy S III] prboy1969:
One of my all time favorite movies. Liked all of them actually. Really liked the series also. At one time I owned the swords.

TEAM MiK MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] marcran75:
Anyone? I've converted the photos to .png format and moved them to custom_res folder and it still won't work. I've even reset to default settings and cleared caches. Suggestions?
[Sprint Samsung Galaxy S III] Phil3759:
Try with one from this:

http://d-h.st/users/philz_touch/?fld_id=28702#files

If it works, than your png encoding is not supported. Try in that case to change png encoding format
[Sprint Samsung Galaxy S III] CNexus:
Just got back from my vacation. Will update the OP now :thumbup:
[Sprint Samsung Galaxy S III] marcran75:
I actually have 2 GS3's and I used the same .png files on my other phone that still has the last version of philz and they worked perfectly fine. I'll try the samples now and update.

Just flashed the droidicon sample and now recovery has two separate menu screens overlaying one another and some of the droidicons are overlaying some of the text. I've attached links to some photos.

https://www.dropbox.com/s/l1zxjmr0srf1zcb/IMG_20140107_124827.jpg

https://www.dropbox.com/s/6dnbq5142lr00dw/IMG_20140107_125017.jpg

https://www.dropbox.com/s/jorth68v3h65hqe/IMG_20140107_125034.jpg

---------- Post added at 07:32 PM ---------- Previous post was at 06:33 PM ----------

just flashed droidicon sample and now recovery has 2 nenu screens overlaying one another and some of the droidicons are overlaying some of the text. I've attached links to some photos.

https://www.dropbox.com/s/l1zxjmr0srf1zcb/IMG_20140107_124827.jpg

https://www.dropbox.com/s/6dnbq5142lr00dw/IMG_20140107_125017.jpg

https://www.dropbox.com/s/jorth68v3h65hqe/IMG_20140107_125034.jpg

I've tried rebooting and resetting recovery settings and now I cant get rid of this and since I've reset GUI the menu height is much smaller and now recovery is ineligigable and unusable. PLEASE HELP!
[Sprint Samsung Galaxy S III] Phil3759:
Well, that shows it works perfectly LoL

Just resize your pic to your screen res :rolleyes:
[Sprint Samsung Galaxy S III] prboy1969:
Was starting to question where you'd wandered off to :p . Hope you had fun:) .
[Sprint Samsung Galaxy S III] marcran75:
???? I dont understand how the text from a menu screen appearing over the top of the previous menu text is normal but ok. I figured out how to reset it though. Thank you for a great recovery though. I obviously don't know what I'm doing with regard to changing the background but everything else works great. Thank you.

---------- Post added at 09:24 PM ---------- Previous post was at 09:13 PM ----------

and I don't think rolling your eyes is an appropriate or encouraging response to someone who obviously doesn't know as much as you do.
[Sprint Samsung Galaxy S III] Phil3759:
The pic was so crappy that I thought those persistent menu texts were some reflections from your screen

Try to be more clear with your questions. I thought you cannot change background and I saw you could without any issue, else I tend to completely ignore the posts

Anyway, if it really looks like that then it is wired. Could be a buffering issue

Anyone can confirm?
[Sprint Samsung Galaxy S III] CNexus:
Lucky charms
[Sprint Samsung Galaxy S III] Naddict:
Thread cleaned of self-righteousness and posts that do nothing but continue the trolling rolling.

Why do that in here folks? Why not just report the offender/offending post and move on?
[Sprint Samsung Galaxy S III] marcran75:
Apologies
[Sprint Samsung Galaxy S III] wilberfan:
Rename Backups?

Congratulations on the slickest recovery I've ever used! :)

One question (forgive me if this has been asked before?): Is it possible to rename backups after they're created? I tried that once on an old phone/different recovery, and the md5 errors kept me from being able to restore something! I had to reinstall completely from scratch. Oy.
[Sprint Samsung Galaxy S III] WindowsSucks:
You can disable md5

Sent from my SPH-L710 using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy S III] Phil3759:
+1

But you can also rename folder without issues if you do not use unusual chars
[Sprint Samsung Galaxy S III] XxTeXx07xX:
NICE

Great work as always! Thank you cnexus :d
[Sprint Samsung Galaxy S III] shekinahsmoke:
new version: 6.12.8
[Sprint Samsung Galaxy S III] CNexus:
Thanks [MENTION=3836275]shekinahsmoke[/MENTION], OP updated! :thumbup:
[Sprint Samsung Galaxy S III] bigwillyg:
I love the smell of fresh recoveries in the morning
[Sprint Samsung Galaxy S III] wilberfan:
Used it last night to flash the new Carbon! :)
[Sprint Samsung Galaxy S III] prboy1969:
:D

TEAM MiK MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] Mr. Struck:
Best recovery there is, nothing else even close in my opinion!! One of the first questions I ask people looking for problems to be solved is "What is your recovery?" I also don't understand the people who say "XXX ROM wouldn't flash properly using TWRP/CWM" when I just assumed it was common knowledge to use Philz!!
[Sprint Samsung Galaxy S III] prboy1969:
[MENTION=4666971]Phil3759[/MENTION] and [MENTION=4645794]CNexus[/MENTION] latest version is working great :) .
[Sprint Samsung Galaxy S III] marcran75:
I'm seeing ppl reporting (myself included) the following error when flashing 4.3:

format ( ) expects 5 args, got 4

(status 7)

Installation aborted

I had to revert to 12/31 build to fix.
[Sprint Samsung Galaxy S III] noles4life50:
Working great with 4.4.x roms, haven't tried any 4.3 since flashing the recovery though
[Sprint Samsung Galaxy S III] liquidy:
Im having the same issue with 4.3

---------- Post added at 03:45 AM ---------- Previous post was at 03:38 AM ----------

Im having the same issue with 4.3
[Sprint Samsung Galaxy S III] Keyz450:
is it safe to update to 6.12 from 6.00 and read my 6.00 backups?
[Sprint Samsung Galaxy S III] noles4life50:
Yes
[Sprint Samsung Galaxy S III] AproSamurai:
So from skimming through the thread, Stock 4.3 is unable to flash with the most recent iteration of the recovery, correct?

Was that always the case on previous versions if you were leaving 4.4.x to 4.3, or is it a new occurrence?
[Sprint Samsung Galaxy S III] Phil3759:
It's all in the FAQ

If devs fix their updater-script, it is all fine
[Sprint Samsung Galaxy S III] CNexus:
The thing is, this is the only recovery that that issue had popped up on

If we edit the updater-script, then it will not work on any other recovery besides this, and on nothing but the latest version.
[Sprint Samsung Galaxy S III] Phil3759:
Because other recoveries are ages behind, it doesn't mean PhilZ must follow them :D

Official CWM

As you see from this link HERE, your Sprint S3 is still on old cm-10.2, and was not updated

TWRP

Depends on who builds it for you.

Now try to compile it from latest sources and you'll face same things

For any proper Cyanogenmod Kitkat ROM, it should work perfectly

For all other ROMs, cookers should evolve

Sadly, there is no way to go back
[Sprint Samsung Galaxy S III] CNexus:
Ok...I guess I'll change the script for my roms when at least TWRP gets updated, because there's really no point in anyone using CWM when there's Philz available (or we can just convert them haha)

Until then I'll suggest that people use the 12/31 build to avoid having to switch back and forth for different roms
[Sprint Samsung Galaxy S III] Phil3759:
If you look at this line:

https://github.com/PhilZ-cwm6/Team-Win-Recovery-Project/blob/twrp2.7/updater/install.c#L208

You'll see that any compiled TWRP with new update-binary will have the issue

Now, what's happening is:

- CWM decided to fix the assert for device name by detecting old update-binary in zip files and replacing them with new one

- TWRP did not do that

So, basically:

- Using any new TWRP with old update-binary in zip, will fail on assert for device name commands

- In TWRP, removing the assert for device name line, will fix it

- In CWM, you will not have any assert error for device name, as we drop back to a new update-binary

- In CWM, any zip with old update-binary will be hacked to run new update-binary, however, obviously, updater-script is kept

- In CWM, we end up with a harder to fix issues, as old commands do not run well with new update-binary files

I will add an option to disable this fall back scenario so that users have to only deal with assert lines for device name
[Sprint Samsung Galaxy S III] Mr. Struck:
Thank you [MENTION=4666971]Phil3759[/MENTION] and [MENTION=4645794]CNexus[/MENTION] for a very informative exchange, I especially like the response from Phil in post #265! Philz Touch has made a believer out of me, after being a long-time user of TWRP, I now absolutely swear by Philz. Doesn't hurt that I prefer to be on the "latest and greatest" Android build and generally never revert back to an older build number anyway, so keep up the good work guys!
[Sprint Samsung Galaxy S III] CNexus:
I'll update my roms then when TWRP 2.7 gets released/I find time to compile it
[Sprint Samsung Galaxy S III] Phil3759:
Well, you should really:

- remove your 2 years old update-binary

- replace with a new uptodate update-binary

- take time to fix your scripts to properly work on new update-binary: no chmod/set_perm of non existing files, format command with 5 arguments

- you make all people happy any you are not 2 years behind

All ROM devs should just do this. Why people use years old files is beyond me

update-binary is the core of installers, and should be updated regularly
[Sprint Samsung Galaxy S III] CNexus:
I use whatever's available and at hand. If that happens to be a 2 year old update-binary that's just a small part of the zip (can be replaced with a script that using unzip) then that's what happens. I don't try to use an old update-binary, but there are larger things to pay attention to than making sure the update-binary is updated
[Sprint Samsung Galaxy S III] 1BadWolf:
What ^^^he^^^ said. Every bit of it. :thumbup:
[Sprint Samsung Galaxy S III] Phil3759:
Not to make it a debate, but I do not agree with you

If you want to understand why, try to look at these commits:

https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-11.0/updater

Installers permitting set_perm failure are + 2 years old as it was fixed at that time.

If you take time to see what are those commits, you'll get it why it can be important to update.

Anyway, let's close this debate as it is complete non sense and out of topic
[Sprint Samsung Galaxy S III] shekinahsmoke:
debate
[Sprint Samsung Galaxy S III] Phil3759:
Update 6.15.4

Check huge change log

It comes with an updated FAQ ;)

It has a new option to make flashing outdated scripts easier

FAQ Updated:
[Sprint Samsung Galaxy S III] trancoss2:
Thanks for tour work.

Enviado desde mi GT-I9300 mediante Tapatalk
[Sprint Samsung Galaxy S III] XxTeXx07xX:
Flashing now. ;) glad I subscribe to this....

---------- Post added at 07:15 PM ---------- Previous post was at 07:09 PM ----------

Download failed ????
[Sprint Samsung Galaxy S III] mholloway:
Just down loaded.i will flash soon.
[Sprint Samsung Galaxy S III] XxTeXx07xX:
I dont see how. I have tried several times even on labtop n failed downloading every time..... :(
[Sprint Samsung Galaxy S III] noles4life50:
Use a different browser or a download manager, Firefox for android downloaded it fine
[Sprint Samsung Galaxy S III] XxTeXx07xX:
Thank you exactlt right. ScriptManager was my file explorer... Uninstalled and work like a charm
[Sprint Samsung Galaxy S III] prboy1969:
will DL, and flash as soon as I'm home. Thank you :)

TEAM MiK MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] wyelkins:
Thanks, Phil!

Is there any way you can add an option to the d2spr recovery like a check box that signifies that this device is Boost or Virgin Mobile. Then during script processing, if it sees d2spr, it will not allow the status 7 error?

This would save us having to modify the script before flashing.

Thanks for your attention to this.
[Sprint Samsung Galaxy S III] CNexus:
Well if you're using this recovery, getprop should return d2spr from the default.prop included with this recovery