yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] yhrn:
Yes, it is. If you read a few pages back you'll see that PhilZ stated that this is a known glitch when releasing 5.13.9.
[Galaxy S 4 i9505 Android Development] MetaIIica:
is for encrypted Device in last Philz supported?

have a encrypted Device and must use TWRP 2.6.1.0 but this have any issue.
[Galaxy S 4 i9505 Android Development] gogua:
I just flashed philz_touch_5.13.9-i9505.zip, and when i run backup i get this:

Source file not found ( /data/philz-touch/philz-touch_5.ini)

Source file not found ( /data/clockworkmod/philz-touch.ini.bak)

**********

I can see that /data/clockworkmod path doesn't exits and path /data/philz-touch/ is empty

Backup ends succesfully , but when i see files from backup i see wrong dates.

thank you
[Galaxy S 4 i9505 Android Development] donalgodon:
Root Access Possibly Lost Fix?

THIS CANNOT BE UNDONE

1. YES fix root (/system/xbin/su)

2. NO do not fix

How do I fix this issue? I didn't have it on this recovery until I flashed another ROM (Google Edition) for testing.

It's super annoying, because it requires manual input and stops automated tasks.
[Galaxy S 4 i9505 Android Development] Phil3759:
Update your supersu to last version
[Galaxy S 4 i9505 Android Development] ixomon:
Quick update : flashed 10.2 successfully with the new version. No problems whatsoever. Backup seemed to be much quicker then before, I'm using simple compression with cwm format.
[Galaxy S 4 i9505 Android Development] donalgodon:
Sadly, this did not fix the problem.
[Galaxy S 4 i9505 Android Development] Phil3759:
Maybe your rom auto roots?

Try to answer yes to cwm
[Galaxy S 4 i9505 Android Development] donalgodon:
The strange thing is that both yes and no have no effect. I don't lose root. It just pauses and I have to manually back out and it reboots.

CM is fine. The GE ROM is what does it.
[Galaxy S 4 i9505 Android Development] Tanis64:
I'm not sure if that fits in here:

With my Galaxy S (I9000) running latest nightly build CM. Recovery comes with CM I think, the same warning appears after a CWM Backup, so I think it's related either to SuperSU or to the ROM, but not to the recovery.
[Galaxy S 4 i9505 Android Development] Phil3759:
Ensure supersu version is last 1.60 or 1.65
[Galaxy S 4 i9505 Android Development] donalgodon:
I have 1.65
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, probably your rom has auto root and doesnt do it properly
[Galaxy S 4 i9505 Android Development] Siwandroid:
I have the same issue on all omega too. on recovery each time i reboot/power off the phone he ask me that.
[Galaxy S 4 i9505 Android Development] gavin-phelan:
I'm still getting error messages once I boot to recovery
[Galaxy S 4 i9505 Android Development] Lightroom:
You use wrong pic, take a pic in status.

In your last pic tick on status and then show us your pic. :)
[Galaxy S 4 i9505 Android Development] damador:
cant get it on me2 and me2 omega - it says ok but phone hang several sec afeter and after reboot its still 3
[Galaxy S 4 i9505 Android Development] Schrotty35:
I have the same issus.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] Phil3759:
post a log, of error message if you want me to help
[Galaxy S 4 i9505 Android Development] InevitableDJ:
The custom status doesn't bother me as I'll be flashing custom Roms

I was just showing that triangle away with MDM and philz recovery works
[Galaxy S 4 i9505 Android Development] Schrotty35:
I have test now the restore option and working fine but is very slow.
[Galaxy S 4 i9505 Android Development] Phil3759:
Look, you report many issues, but you don't provide any details or logs when asked. I cannot do anything for you that way

Do not take it wrong, just think that I do not own an i9500, neither an i9505, but just an old i9100

1- provide logs

2- detail the error messages exactly

Now, for your error 7 issue, it is an assert command. Maybe you are flashing i9500 things on i9505. Just post here the log or the updater-script file you can find in the faulty zip you are flashing

For your error messages on boot: still waiting for a log or exact details of error message

For your restore issue: at end of restore, you should get stats about the time it took, just provide them + data size of your initial backup. Also, test other recoveries with same backup and see if mine is slower then report it

Writing 4Gb to sdcards is something rather slow

That way, I can give support and fix bugs
[Galaxy S 4 i9505 Android Development] :
we should really support PhilZ so he can get a new device :) sadly I can't try this right now but I would love to. I used your recovery on note ii and it was really good. and I know for sure it will be a beast here as well. kudos for your support
[Galaxy S 4 i9505 Android Development] Schrotty35:
The error messages on boot i have only the first time after flashing the latest recovery. Now i dont have the issus.
[Galaxy S 4 i9505 Android Development] hav0c:
The back and restore functionally is slow becasuse stock ROMs are huge. This does not have anything to do the this or any recovery. Backup and restore on Chenglu his recovery takes exactly the same time. Try flashing CM and make a backup. The whole proces takes about 2 minutes. That is because the ROM is only a few hundred MB.
[Galaxy S 4 i9505 Android Development] Schrotty35:
I think this recovery is now full working. I can make full wipe without erros and i can install Stock Roms without Status 7 error. Only CM and AOKP have this issus and this is not a recovery problem.

Thank you for you hard work. Here is my Beer for you: 08D07640XK4247126
[Galaxy S 4 i9505 Android Development] hav0c:
Have a few beers for your work PhilZ

2R424472WS685641E

Hope others will do the same..
[Galaxy S 4 i9505 Android Development] Fir3blade:
Can also confirm that everything is working.

We do have a fully working recovery, which is awesome!

Thank you!
[Galaxy S 4 i9505 Android Development] Phil3759:
Thanks a lot for your generosity :thumbup:
[Galaxy S 4 i9505 Android Development] androidizen:
Latest build is working great on my S4, no problems that I can find yet.
[Galaxy S 4 i9505 Android Development] slonn:
The Aroma file manager is not fully working. The touch controls are non-responsive.
[Galaxy S 4 i9505 Android Development] SunSide:
Hmmm....all are sending beer...? PhilZ will get drunk...! :laugh:

The pizza is on the way now.

Thanks for all the hard work and the time you are spending.
[Galaxy S 4 i9505 Android Development] pandorra:
backup on external sd card doesn't save on external sd card resp. a new folder doesn't show up. within CWM i can see the folder anyway. the folder name with date is working fine at least now...

here's the log: http://uploaded.net/file/26p1f19o

backup time on stock rom: 6:09 minutes

size: 2596 mb

€

a second try was successful. dunno what happened at the first try...
[Galaxy S 4 i9505 Android Development] Phil3759:
Look at /data/media/0 option
[Galaxy S 4 i9505 Android Development] donalgodon:
Nobody knows why or how to fix it?

Same thing happens with 6.0.3.6 CWM and PhilZ latest, so I'm a bit confused, because it does NOT happen on CM ROMs.
[Galaxy S 4 i9505 Android Development] Phil3759:
As I told you, ask you rom cooker to fix his script. It is either in int.d or in the kernel you use
[Galaxy S 4 i9505 Android Development] donalgodon:
Sorry. Will do. Thanks. :)
[Galaxy S 4 i9505 Android Development] norrie2204:
please help

hey guys i really need some help and advice please....i was on stock mh8 urooted with apps for a couple of weeks and decided to try some roms...i installed philz latest .tar recovery with odin and all was fine..i backed up my current rom last night and rebooted fine and left it till today i then installed echo rom after wiping and it wouldnt install wit E cant open echo (bad) so i thought ill restore my backup and re download echo but im getting md5 mismatch when i try to recover my backup...then i tryd to install liquid smooth and gapps with same result cant install bad im now re downloading echo and also stock mh8,,,i also can only get pc to recognise ex sd card when i try to mount sd ex in recovery it cant im really beginning to panic and i hope someone can help....please guys !!!!
[Galaxy S 4 i9505 Android Development] john0699:
[MENTION=4666971]Phil3759[/MENTION]

Hello, can you make please a tar.md5 file from the newest Recovery?!

Thanks

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] Mkhant30:
Hi,

Hope anyone guide me how i could install Philtouch 5.13.9.zip from stock recovery as I used to flash from Odin .tar file. One more question, will it be compatible with ROM manager?

Thanks in advance,

Mkhant30
[Galaxy S 4 i9505 Android Development] timberwolf60:
Uzipped it you will have recovery.img and put it in internal sd card, then flashed it by sgs4 flasher.

Send via i9505 using Tapatalk,

ROM: Stock I9505XXUBMG5

CSC/Modem: OLBBMG1(STH)/DXUBMG5

Kernel/rec: Stock/Phil 5.07.6

SuperSU Pro 1.65, 64GB exFAT Card
[Galaxy S 4 i9505 Android Development] Mkhant30:
[MENTION=914973]timberwolf60[/MENTION]

Thanks a lot for advice :). Can it work on Rom manager?
[Galaxy S 4 i9505 Android Development] hanspampel:
Take a look at here mate. Ive made one for a couple of days.
[Galaxy S 4 i9505 Android Development] timberwolf60:
Unziped philz_touch_5.13.9-i9505.tar.md5 and you have recovery.img. I used sgs4 flasher for flashing recovery and it worked.

Send via i9505 using Tapatalk,

ROM: Stock I9505XXUBMG5

CSC/Modem: OLBBMG1(STH)/DXUBMG5

Kernel/rec: Stock/Phil 5.07.6

SuperSU Pro 1.65, 64GB exFAT Card
[Galaxy S 4 i9505 Android Development] Hawke84:
Hi, +1 to this, i also get the wrong dates on backups and when the phone boots the time is wrong for a while...
[Galaxy S 4 i9505 Android Development] gogua:
I solved, filling time zone in philz settings and saving. The time zone was wrong when i flashed philz recovery.

try it
[Galaxy S 4 i9505 Android Development] Hawke84:
thanks, but ive tried that. for some reason it thinks the date is 1970!
[Galaxy S 4 i9505 Android Development] gogua:
When you saves settings, do you get /data/clockworkmod/philz-touch.ini.bak ,
[Galaxy S 4 i9505 Android Development] Hawke84:
yep i get that when i do backup, but i cant find it when i navigate there using file explorer when ROM boots.

just tried TWRP and it does the same so seems that its storing the time and date somewhere that recovery is reading. any ideas?
[Galaxy S 4 i9505 Android Development] gonsa:
Has anybody tested this?

Aroma-2.70RC2.zip

It is coming in the new Omega V11.
[Galaxy S 4 i9505 Android Development] kantjer:
yes
[Galaxy S 4 i9505 Android Development] SeaFargo:
The Official CynogenMod don't install

Just to report that the Official CynogenMod do not install with this recovery, while install regulary with the original CWM.

In any case congrats for the wonderful work.

I wonder so know why it doesn't work on a such popular ROM.

Kind regards.
[Galaxy S 4 i9505 Android Development] donalgodon:
Yes, it does. It works perfectly fine with the latest version, even when using the CM Updater. Not sure what problem you had, but I think it's probably that you forgot to change the data path to media rather than media/0

That will give you problems. Once you set it, you'll be fine.
[Galaxy S 4 i9505 Android Development] SeaFargo:
I'll for sure give it a try. Effectively I had Storage Set to media/0

I've tought that this "Storage Set" does not affect the installation from zip file. :confused:

Thank you very much for the kind reply. ;)
[Galaxy S 4 i9505 Android Development] BillGoss:
Actually, this recovery (5.13.9) works perfectly for me with official CM.

Perhaps you mean that it doesn't work with the CM Updater?

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Cyanogenmod is sticking to a dirty /sdcard/0 non sense hack

I truely support /sdcard as /data/media/0 and offer a toggle to switch to /data/media for cm compatibility

Most people prefer the default true /data/media/0 to have their files visible in main ROM under MTP mounting in PC
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.14.5 for i9505 released

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

It is a massive nandroid code rewrite to merge cm-10.2 new wrapper

To enable compression, you have to go again under Misc Nandroid Settings and choose the tar.gz format

I added a new "fast" compression mode too

Now, you can also backup and restore /data/media to external storage

Test deeply and report back

Soon a final version for S4 family
[Galaxy S 4 i9505 Android Development] putti71:
When I choose compression, only fast compression is working, there is nothing else to choose anymore. Now I am running the fast compression, let's see how this works

Sent from Telegraph
[Galaxy S 4 i9505 Android Development] SunSide:
When i boot in recovery,i can go through the options fast,low,Med,High...after that i can only choose fast.When i want another compression option i first have to reboot to recovery again :)
[Galaxy S 4 i9505 Android Development] Tassos_i:
2 quick remarks

In Misc Nandroid settings, once you've understood that you have to add the step of choosing tar.gz, if you start toggling the "compression" line, then after 4 hits, it gets stuck to "fast".

The backup time on exfat 64 under 5.14.5 "fast" is more than 50% bigger than under 5.13.9 "low" :confused: (under same device temperature). Unfortunately, I can not directly compare 5.14.5 "low" to 5.13.9 "low", as it is stuck to "fast", but I do not expect miracles, I think 5.14.5 is really slower on my exfat 64.
[Galaxy S 4 i9505 Android Development] zencooler:
Thanks Phil,

It's brilliant as always!

The backup time with default options to external exFat 64GB SD takes: 18:48 min for 4,788 GB size.

Fast enough :)

The only issue is the clock problem. Still not solved, but I have to check clock after next restart or flash again. Last version has been solved after this.

Regards!
[Galaxy S 4 i9505 Android Development] putti71:
Just made a backup : 55 minutes to extSD

for 3.18 gb

Sent from Telegraph
[Galaxy S 4 i9505 Android Development] DroidRevenge:
Compression?
[Galaxy S 4 i9505 Android Development] putti71:
Fast compression

Sent from Telegraph
[Galaxy S 4 i9505 Android Development] Phil3759:
Speed is unchanged and still depends on data size, compression, number of small files and mainly these exfat 64 Gb cards

Disable compression and disable size progress if you are affected

It is not final version and I am looking at this speed issue

About the toggle compression bug. I am looking at it
[Galaxy S 4 i9505 Android Development] Phil3759:
Ok

Found the bug, caused by a == instead of =

Basically, if you toggle it upto fast, real compression value will be extremely high explaining speed issue

After a reboot, it will be effectively set to fast.

So, just set it to fast, reboot recovery, and keep it as is

I will fix in next update

Thank you for having spotted this
[Galaxy S 4 i9505 Android Development] SeaFargo:
Still can not install CynogenMod with it

I have always the same problem installing CynogenMod.

I wonder to solve the problem in order to find my mistake and can use this recovery as my defaul recovery.

I did this:

Phone: Galaxy S4 GT-I9505

Stock OEM ROM: I9505XXUBMGA_I9505ITVBMH1_I9505XXUBMGA_HOME.tar.md5

Recovery: philz_touch_5.11.2-i9505.tar.md5

Rom to install: cm-10.2-20130917-NIGHTLY-jfltexx.zip uploaded to the phone by MTP and positioned as is, in the root of the internal storage.

I did boot philz_touch_5.11.2-i9505 and:

- Wipe Data/Factory Reset

- Whipe Cache Partition

- Whipe Dalvik Cache

- Install Zip

- Choose zip from sdcard

then I have to enter in 0/ because of your suggestion to change "Storage Set to /data/media"

- cm-10.2-20130917-NIGHTLY-jfltexx.zip

After the installation process, reboot.

The boot fails:

After the Samsung GT-I9505 logo, the screen goes black and then nothing happens.

I had to push the power button and hold to start the system again.

Where is my mistake?

With CWM_6.0.3.6_Non-Touch_GT-I9505.zip the installation is completed successfully And cm-10.2 boot up regulary.
[Galaxy S 4 i9505 Android Development] David78130:
No mistake, Could you try "clean install for a new rom" before flash cm10 ?

From my Galaxy S4 tuned with CM10.2/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] SeaFargo:
Already did it ... Nothing..

Strange isn't it? ...
[Galaxy S 4 i9505 Android Development] David78130:
Sure, try with the jfltexx version 5.11.0

From my Galaxy S4 tuned with CM10.2/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] kieeps:
I used 5.13.9 and it worked fine to install probam atleast. Before that version only jfltexx versions worked for aosp roms and i9505 versions was for TW roms.

But i recall philz say he found the problem in the policys of the stock recovery source or something so no more separate versions ;)
[Galaxy S 4 i9505 Android Development] Phil3759:
PhilZ Settings / About

And verify you really have latest version
[Galaxy S 4 i9505 Android Development] radmarsh:
I also am getting the wrong dates. Well try the cmos reset.

Thanks for your work Phil
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.14.6

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

This version adds a lot of fixes to touch events handling, key repeat, blank/dim screen timers...
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.14.7

We should be done for tonight ;)
[Galaxy S 4 i9505 Android Development] BillGoss:
Use the Philz version 5.13.9 or later. 5.11.2 was notorious for cm issues.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] donalgodon:
I had a bad download. Sorry, please ignore.
[Galaxy S 4 i9505 Android Development] Hawke84:
How do I do CMOS reset? I've searched and not found anything
[Galaxy S 4 i9505 Android Development] radmarsh:
I read somewhere take the battery out for twelve hours...nit sure if it's true but I'll give it a go
[Galaxy S 4 i9505 Android Development] Phil3759:
Was reported to work by many. Strange asvi never encountred this bug. Very few people seem affected from downloads/reports ratio. Probably some roms as we need a binary to set time

Will look if I can include it in ramdisk but recovery partition is very tight on free space
[Galaxy S 4 i9505 Android Development] starbucks2010:
Try to re-download the ROM. Maybe it was a bad download.
[Galaxy S 4 i9505 Android Development] Hawke84:
Ive seen it on other recoverys not just your its present on TWRP too, i cant get rid of the bugg, may have to send back to samsung.

FYI was using Omgea ROM before I went back to stock but going back to stock still didnt fix it
[Galaxy S 4 i9505 Android Development] kantjer:
I'm not sure it's ROM related. I'm also on Omega and don't have the time issue anymore.

Like I mentioned earlier, I was having this issue for about a week on both PhilZ and TWRP. While on PhilZ I flashed something (can't remember if it was a Rom or something else) and when booting back into recovery after that the time issue was solved and never came back, this was about 2 months ago.
[Galaxy S 4 i9505 Android Development] Hawke84:
ive done everything i can think of to resolve ive gone back totally to stock and its still present so going to send it away for warenty repair :(

ive even flashed back original bootloader and CSC but no change, only partition i didnt touch was EFS
[Galaxy S 4 i9505 Android Development] MRDOCA:
Hey bro did all that to. Only way that fixed it was to reset the cmos. Take battery out for 12 hours. After I did that I started the phone up and the time was still wrong lol but after it set it was fine after.

Swyped on my Omega driven I9505
[Galaxy S 4 i9505 Android Development] Hawke84:
thanks, i'll give it a go and report back! i'll leave it till tomorrow morning!

wonder why its doing it, gotta be a low level software issue. if there is room on the RAMdisk maybe it would be good to have something to stop it from happening..
[Galaxy S 4 i9505 Android Development] Phil3759:
Cmos reset fixed it for most

I will look at the binary if it can be embedded into ramdisk
[Galaxy S 4 i9505 Android Development] putti71:
This morning I put the latest version onto the device and it took only 23 minutes to take a backup of 3.1gb. That's great! Yesterday s version took 55 minutes.

Sent from Telegraph
[Galaxy S 4 i9505 Android Development] yhrn:
Would be great. I've had the time issue since I got the phone about a month ago, I just didn't report it as it was a known issue. It happens about 50% of the times i get into recovery.
[Galaxy S 4 i9505 Android Development] starbucks2010:
Be careful with the repair. It might come back to you with the new boot-loader without the possibility to go back to any ROM without the Knox warranty void 0x1 issue.
[Galaxy S 4 i9505 Android Development] Hawke84:
thanks for the heads up, yeah thats what im worried about but my carrier firmware isnt on the new BL yet so might be ok. fingers crossed i wont need to sent it away!
[Galaxy S 4 i9505 Android Development] svenk:
Me too...
[Galaxy S 4 i9505 Android Development] Hawke84:
Left my battery out for 12 hours to try to clear CMOS but no joy still 1970 :( will try for 24 then maybe send it back to Sammy but sounds like a few people are getting so might wait see what Philz can cook up. Thanks for all the support
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.14.9 (Final?)

I stopped completely using time_daemon hack for time. It seems, unlike early kernels, the current one doesn't need this

I have time perfectly working without loading anything from ramdisk

I also played with time_daemon: force loading it in adb shell triggers the 1970 date bug. However, on reboot, all is gone

Previously, we used time_daemon on boot then it was killed before recovery loading. However, it could maybe survive for some of you

Now, it will not be loaded at all. Let me know what happens

Probably a 5.15.0 for very small cosmetic changes will be the final version to push to all devices

After that, I will focus on cm-10.2 to add USB OTG support
[Galaxy S 4 i9505 Android Development] lahceneamine:
What Happens for me, is that it's not showing the correct time :)

It shows me 16:09 instead of 00:55 (UTC +1)

- WanamLite 1.5

- AdamKernel 1.6

I'm gonna do a backup in my exfat card and let you know the results (around 5467 Mb)

---------- Post added at 01:19 AM ---------- Previous post was at 12:56 AM ----------

Condition :

- Tar + gzip

- exFAT 64Gb Class 10

- No progress at all.

- FAST comprission.

- 5467 Mb

========

Results

- 23:29 Mn

-3957.36 Mb

- 27.62% Compression (Like A HIGH level ?)
[Galaxy S 4 i9505 Android Development] Phil3759:
Really wired

Will play a bit with time daemon and see if I can embedd it in ramdisk
[Galaxy S 4 i9505 Android Development] Idebutterpiep:
Need help flashing Philz Touch on I19505

Bought new I9505 and want to flash Philz Touch. Tried the last different Touchez zips 5.14.5,. 5.14.6 and 5.14.7, on my SD card but they didn't flash my phone. Before I had a S2 I9100 and flashing was no problem from recovery mode..

My Phone; I9505 XXUBMGA

I9505 OXEDMH6

I9505 XXUBMGA

Question

1:

Before I enter in Recovery I see a green Android with a red triangle in it and then I see the recovery menu. Hardly unreadable, because of the little letters.

I choose install zip from Sd card. Can find the zip on the Sd Card. And install.

During install I see I think three red lines, but cannot read them, because they move very quickly and the letters are so little.

Then i can go back to recovery, boot again and nothing happened. My phone is the same as before flashing. No Philz Touch.

Somebody can tell me what I do wrong.

Question

2:

Can I flash my GT I9606 with the new firmware I9505XXUDMH6_I9505VDSDMH6 using Odin the same way I did as on the I9100 without wiping and losing my data?

I appreciate your help.
[Galaxy S 4 i9505 Android Development] Fauert:
Hi , unpower your piece. Load v5.14.9 TAR in PDA in Odin . Go too download mode ( Power+Volume Down) flash Philz . Tada ... :good: