yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] edwardtobia:
[MENTION=4666971]Phil3759[/MENTION] Any idea what I can do about my above issue Phil (http://xdaforums.com/showpost.php?p=46313201&postcount=2102)? I cannot get into recovery to revert back to an older version, each time I try to enter recovery it automatically starts installing todays CM10.2 nightly and I cannot cancel it, it then reboots the device automatically and gets stuck at the boot screen, I cannot get into the recovery menu? :( what can I do to solve this?
[Galaxy S 4 i9505 Android Development] Phil3759:
Flash twrp or stock recovery.img in odin. Not any cwm recovery or they will keep flashing your file.

Boot into twrp/stock recovery and format cache

Do not use the 5.17.6 any more. It can corrupt /data if you format it + / data/media from mounts and storage menu. That would need odin and pit file

Corruption of cache only can be fixed with the trick above flashing twrp or stock recovery.img or an older version than 5.17.6

Really sorry. Out of home to pull the file from devhost :(
[Galaxy S 4 i9505 Android Development] edwardtobia:
No worries mate thanks for getting back to me :)

I will flash TWRP via ODIN when I get home and format cache and then install an older version of your recovery!

Hopefully this works!
[Galaxy S 4 i9505 Android Development] aeroman:
understand, by me was Ausdim Kernel with Foxhound Rom installed.

no Problem mate, I like to wait for a new version of Nitro. :)

Greetings
[Galaxy S 4 i9505 Android Development] f100cleveland:
Wrong post
[Galaxy S 4 i9505 Android Development] Piretia:
Not working, installed the stock recovery but still the same :(
[Galaxy S 4 i9505 Android Development] Tanis64:
So 5.17.5 is safe?
[Galaxy S 4 i9505 Android Development] donalgodon:
I got it working by intalling 5.15.8

I had the same problem. Got stuck in an install loop from updating the latest CM Nighlty.

Since I didn't trust the final results, I ended up doing a clean install, just in case, but it worked for me.

Remove the battery, and enter recovery manually. It should work eventually, and you'll be able to format cache.
[Galaxy S 4 i9505 Android Development] Piretia:
No not working...same error :(
[Galaxy S 4 i9505 Android Development] Phil3759:
If you correctly flash twrp or stock in odin, it is impossible

On boot, they do not recognize extendedcommands file
[Galaxy S 4 i9505 Android Development] donalgodon:
[MENTION=4666971]Phil3759[/MENTION]

I'd also like to know: Is 5.17.5 safe, or should we stick with earlier versons?
[Galaxy S 4 i9505 Android Development] Phil3759:
5.17.5 is fine

It only missed the partition sdcard binary as i couldn't fit it in ramdisk

It is based on long proven ausdim stock kernel
[Galaxy S 4 i9505 Android Development] emilcioran99:
The .tar.md5 file flashed with ODIN works ok but I tried to install twice the .zip file from stock recovery (I9505 - stock XXUDMH8 rooted with Chainfire's CF) and get e-signature-verification failed.
[Galaxy S 4 i9505 Android Development] donalgodon:
Ummm...

you can't install it with stock recovery. You need to already have a custom/CWM recovery installed. You can (as you noted) install the recovery from Odin, but stock recovery will not allow you to flash a custom recovery.
[Galaxy S 4 i9505 Android Development] kfallz:
Flashed .5 before I cleared cache and dalvik for new kernel... getting the same error, everything seems to work though.
[Galaxy S 4 i9505 Android Development] donalgodon:
It does work fine. I just gave up on the idea of backups to external SD for now and just used the internal SD. Too bad that the space is so small.

Doesn't seem like koush is much interested in updating ROM Manager to properly support CM10.2 external backups. Maybe if you felt like it/had the time, you could squeeze out a little update hack to work around the issue with:

- Ausdim kernel base

- CWM 6.0.4.4

- 10.2 external backup ROM Manager support?

;)

FWIW, just backed up 2.7GB to internal SD in 2min. 32sec. with 15.7.5. Definitely faster.
[Galaxy S 4 i9505 Android Development] Phil3759:
Koush will update it once, he just takes his time

Remind me in 4-6 weeks please. My life will be less stressed and if Koush did not fix it, I can use existing ors-mount to do this
[Galaxy S 4 i9505 Android Development] starbucks2010:
I don't think that 5.17.5 is fine. At least I got same problems with it. The solution for me was to flash back 5.15.8 (cwm) and clean cache and dalvik. After that I rebooted the recovery andthere were no more error messages.

Best regards.
[Galaxy S 4 i9505 Android Development] donalgodon:
What problems did you have?
[Galaxy S 4 i9505 Android Development] Phil3759:
I use 5.17.5

It has no issues
[Galaxy S 4 i9505 Android Development] lahceneamine:
So basically, everything works but we cannot partition SDcard ?

If yes, i'm gonna flash it and test speed on exFAT 64 :)
[Galaxy S 4 i9505 Android Development] Phil3759:
speed is same as 5.17.6

Only partition sdcard won't work and also NTFS USB key will be loaded using fuse, so too slow for backups

Two minor issues no one would have ever noticed...

I will enable these 2 features when we get a working kernel
[Galaxy S 4 i9505 Android Development] lahceneamine:
So no need to flash it :)

Thank you again.

Sent from my Dark Domination S4
[Galaxy S 4 i9505 Android Development] starbucks2010:
I was on 5.15.8 since long time and this evening I just flashed 5.17.5. Right after recovery reboot it started to give me these error messages and under option to flash a zip file I didn't have the choise of external sd. The error messages when I tried to clear cache and dalvik were:

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

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

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

E: Can't open /cache/recovery/last_log
[Galaxy S 4 i9505 Android Development] Phil3759:
What a mess

I built many internal 5.17.5 versions

From size, I see the devhost one also has adam stock kernel

Removed it
[Galaxy S 4 i9505 Android Development] Phil3759:
5.17.5 and 5.17.6 cache issue

- flash a previous version of recovery from devhost

- reboot into recovery

- wipe cache
[Galaxy S 4 i9505 Android Development] putti71:
Hi PhilZ, I guess you mean 5.17.1 because I cannot find a 5.17.5 anywhere.
[Galaxy S 4 i9505 Android Development] sachs:
I had a big scare ... I installed 5.17.6 and tried to format to install a new rom (Mli). Nothing worked, froze and reboot ... I do not know how I managed to format the cache and installed the new rom ( thank God)

After, installed cwm 6.0.4.4 with SGS4 Flash. Now everything is fine, expecting some correction of his recovery.

I was very scared ... even smoked a cigarette and looks that do not smoke to years ...again...thank God...:eek:
[Galaxy S 4 i9505 Android Development] donalgodon:
I just tried to flash recovery-clockwork-touch-6.0.4.4-jfltexx from SGS4 Flash and it said the recovery was flashed, but when I rebooted the recovery, it was still PhilZ 5.18.5.

I just wanted to test it out.

Does anyone know why it didn't flash/overwrite the recovery-clockwork-touch-6.0.4.4-jfltexx?

Flashed a zip and it worked, but the plain/stock CWM is horrible compared to PhilZ. Bleh!

No thanks. I'll stick with 15.8.5 as long as necessary.
[Galaxy S 4 i9505 Android Development] Formhault:
Wait for a new kernel? You mean a new recovery kernel? Cause the kernel I know about is not bundled with the recovery on the S4 anymore :p

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] sachs:
It can be but it is what we have at the moment and works perfectly ... nothing scares ... but hopefully a stable version of Philz. Another thing is certain date in CWM.... is not in 1970 as was the Philz ...but I prefer the recovery Philz but also a stable version and no alarms :eek:
[Galaxy S 4 i9505 Android Development] vikash0513:
I habe installed philz touch 5.11.2 but i cant partition sd card to ext 4 in recovery which version does it works or do i need another recovery
[Galaxy S 4 i9505 Android Development] oliver005:
Guys, anyone tried Philz with latest leak 4.3 MI8 touchwiz version? I did the backup but when restoring - getting bootloop. Don't know if it's a rom problem or a recovery. Would like to know what version works with 4.3 leak.
[Galaxy S 4 i9505 Android Development] Phil3759:
cwm currently doesn't support backup/restore selinux context

Next updates will
[Galaxy S 4 i9505 Android Development] eak1080:
Hey Phil, love that your patching/fixing things in the official CWM :)

I still (and always) prefer your recovery but when im browsing the Cm gerrit its nice to see the fixes shared.
[Galaxy S 4 i9505 Android Development] zukri90:
What is the latest and stable build? Thanks.
[Galaxy S 4 i9505 Android Development] donalgodon:
5.17.1 is the latest, both it and the one before it, 5.15.8, which I use, for CM specific issues, work fine. The faulty builds due to kernel related issues were removed by the dev.
[Galaxy S 4 i9505 Android Development] Formhault:
And what context is that gonna be?

I mean I know SE is Security Enhanced... but... I thought that comes within the /system partition (as part of the ROM, that is).

:confused:
[Galaxy S 4 i9505 Android Development] Tanis64:
SELinux is a combination of boatloader, Kernel and OS in the SGS GT-I9505 context.
[Galaxy S 4 i9505 Android Development] KenHua:
I was very happy with 5.17.6 because of its great backup performance -- the speed was comparable to that of TWRP. Unfortunately I had to follow the advice and downgraded it back to 5.17.1. My backup duration now is back to about 25 minutes instead of about 6 minutes, which 5.17.6 (and TWRP) gave me. Hopefully the issues can be resolved soonest so that we can enjoy this best of the best Recovery. Thanks
[Galaxy S 4 i9505 Android Development] Formhault:
Combination of... Mmmmkay...

So... We will be able to backup the bootloader? :/

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] Tanis64:
Not with the recovery I think , maybe with a tool like QPST (Qualcomm Product Support Tools) but therefore my knowledge didn't last.
[Galaxy S 4 i9505 Android Development] wonsky21:
Guys, sorry fot ot, but where I can find cwm 6.0.4.4 flashable zip for i9505?

GT-I9505 | SlimBean 4.3 build 1.6
[Galaxy S 4 i9505 Android Development] Formhault:
This is the main CWM thread for S4 I9505.
[Galaxy S 4 i9505 Android Development] pitcher85:
Really OT, but here.

Edit: Sorry, of course these are .img files, but just use SGS4 Flasher.

Edit2: You can try these or these flashable zips.
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.17.6 fixed - CWM 6.0.4.4

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

- this has the "Nitro" fix

- using pigz is much faster now in my tests (-4 mn on 3.4 Gb, but will depend on your card speed)

- /cache corruption is fixed

I put in beta as I did not add ntfs support for now

I need users with exfat 64Gb cards to say if this version mounts their exfat card.

Once I have the info, I will release final with ntfs support and Selinux support for new 4.3 ROMs

All credits will follow on final release

just try backup to exfat cards, you'll die before it completes !

Stock CWM fails miserably in this as it uses fuse
[Galaxy S 4 i9505 Android Development] pitcher85:
I know, I am using your recovery since a while ;) Thanks and keep your good work up!
[Galaxy S 4 i9505 Android Development] dave_p_b:
[MENTION=4666971]Phil3759[/MENTION]

Link doesn't work. Think it should be: http://d-h.st/users/philz_touch/?fld_id=25841#files
[Galaxy S 4 i9505 Android Development] Tanis64:
Sure the image in that zip is actual?

I just install that from beta folder and compilation time in about say:

Build on October 9 08:35

Is this the actual beta you want to upload?

Regards Christopher
[Galaxy S 4 i9505 Android Development] dave_p_b:
Tested on exfat 32Gb. (does this count?)

1) Backup 4Gb 6.50 Min,

2) Clear cache works ok.

3) Restore 4Gb 5.41 Min.

Do I need to include /preload in my backups? I did out of habit from my S2 days.

Restore /preload fails with error mkfs.ext4 unable to do something (not sure the exact error message, sorry)

I've unticked backup /preload now. Unless someone tells me I need it.

Cheers.
[Galaxy S 4 i9505 Android Development] Phil3759:
it is actual, changes are in ramdisk, it is not recompiled

Great, it is really Nitro :D

I still need a feedback from exfat 64Gb cards. I made a small change that I could need to revert as previouly, on early builds, they failed to mount if modules were not loaded from a /system path

I will wait for a feedback from someone with 64Gb card in exfat format. No need for speed tests, just if you can browse it from recovery
[Galaxy S 4 i9505 Android Development] aeroman:
Now works fine your Nitro Build, by me all a bit performant! (Menus, UI)! :thumbup:

I tested Backup to my Samsung exFat 64GB Card (without Restore),

with all Nandroid Progress & Size On, needed for that 3890MB --> 7.20min.

That's a very good Value, even faster as Twrp (by me.) ;)

Wipe Cache & Dalvik Partitions works again fine.

Thanks for the good work, I send you next days a Donut. :)

Regards

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] Phil3759:
Great and thank you

It should be faster than TWRP now as I use exfat kernel modules while TWRP drops to fuse (however, fuse implementation in TWRP is much much faster than stock CWM as they use buffering of tar writes. However, that buffering could be responsible of some users issues: speculating here)
[Galaxy S 4 i9505 Android Development] a66fm:
i can also confirm that 64gb exfat card is accessible through the beta recovery
[Galaxy S 4 i9505 Android Development] daniello8:
newer versions break zipinstaller functionality .. what paths must I enter now?
[Galaxy S 4 i9505 Android Development] SmartFreak:
ExFat 64Gb card working fine, no issues with beta version
[Galaxy S 4 i9505 Android Development] Phil3759:
cwm 6.0.4.4 uses new paths:

external_sd is now /storage/sdcard1
[Galaxy S 4 i9505 Android Development] daniello8:
Thanks ..

storage/sdcard1

works!
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.17.7 Final

Should be online soon, uploading, same path

It adds ntfs through ko module (you can try with an OTG USB cable)

Lowest brightness value you can set is now 10 instead of 25
[Galaxy S 4 i9505 Android Development] KenHua:
Great improvement !!!

HOORAY!!! My backup time of over 3GB to Internal Storage improved from 25mins in 5.17.1 to 5mins in 5.17.7! Thank you very very much for the GREAT WORK and the HARD WORK! Respect! :good:
[Galaxy S 4 i9505 Android Development] Phil3759:
5.17.7 (12.10.2013)

Change log compared to previous buggy 5.17.6

I am now using a stock i9505 google edition kernel compiled from sources by [MENTION=3562083]wanam[/MENTION]

This fixed size, root, ext4 corruption and ntfs/exfat issues

Many thanks to [MENTION=3562083]wanam[/MENTION] for his support in this last vesrion :good:
[Galaxy S 4 i9505 Android Development] JohnnyBlack10:
How save phil ui like background color setting? Every reboot always back to default ... pink :(... but I wanna black.
[Galaxy S 4 i9505 Android Development] sarbe:
I changed mine to black and it stays black.
[Galaxy S 4 i9505 Android Development] lahceneamine:
Will the speed be the same as previous version ? Or have you managed to get it done ? :D
[Galaxy S 4 i9505 Android Development] Phil3759:
Speed is what you ever dreamed ;)

This should be the most stable and faster recovery for i9505

It only misses Selinux context for backup/restore of 4.3 ROMs, but this should be fixed soon
[Galaxy S 4 i9505 Android Development] lahceneamine:
I'm gonna test then report ;)

And euh I Love You Man :fingers-crossed:

Edit :

Back Up of 6343 Mb on exFAT 64gb Class 10

- Time : 19:05

- MD5 Off

- No Compression.

- Show Nandroid Size OFF.

- Hide Progress ON.

:)
[Galaxy S 4 i9505 Android Development] kuljit55:
Hi i want to install the original clockworkmod recovery for my 19505, is this the official one? Theres quite a few clockworkmod recoveries in the posts e.g. theres a 6.0.3.2 one somewhere.

Also is it possible to flash this with the sgs4 flasher app?
[Galaxy S 4 i9505 Android Development] wonsky21:
Read few posts back :)

Edit: Here

http://xdaforums.com/showpost.php?p=46401026&postcount=2149
[Galaxy S 4 i9505 Android Development] Riskytwin:
Does this new philz recovery version solve the date issue (1970)
[Galaxy S 4 i9505 Android Development] kuljit55:
[MENTION=3673848]wonsky21[/MENTION]

So from the link you have gave me there are 2 files there, i found the cwm 6.0.4.4 touch version on this link

http://d-h.st/1WM

Is this the one i can flash with the sgs4 flasher? Also do i extract it 1st to get the .img file for the sgs4 app to find? Thanks
[Galaxy S 4 i9505 Android Development] wonsky21:
Check your PM, it isn't polite to talk here about cwm ;)
[Galaxy S 4 i9505 Android Development] Phil3759:
Not bad for 6.3 Gb

However, I am sure that if you enable compression you will get smaller time as there will be less data to write

In latest version you should keep "Hide Progress ( )" and "Show Nandroid Size (x)" as they do not impact time and add you great visual progress

Please at others: stop spamming thread with non related stuff. Waste of time for me as I am monitoring thread for support

There are FAQ and General sections for this

Hope you understand
[Galaxy S 4 i9505 Android Development] Formhault:
I am very curious what this SELinux content might actually contain. Can you elaborate, please?

Cause for all I've known so far, it was something that needed to be implemented both in the ROM and kernel - so that's /boot (or wherver the kernel goes) and /system partition, right?

Okay :(
[Galaxy S 4 i9505 Android Development] OzBoy1:
Wondering if the new update now supports MI8. Read through and saw it had some sound issue's when installing. Then it appeared to have this issued fixed but wasn't restoring, with a note from Phil stating the next update would fix. I am wondering if this is the update, couldn't see anything in the change file to indicate this.
[Galaxy S 4 i9505 Android Development] Phil3759:
I was not targetting you, but all the talk about stock cwm and third party apps...

No, when I will add selinux context support, I will mention it clearly
[Galaxy S 4 i9505 Android Development] Formhault:
I know you were not targeting me specifically. I just said that, in the context where I asked something somewhat unrelated in terms of bug reporting and such... :p

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] Phil3759:
selinux context is some extended file permissions in 4.3

currently cwm tar command doesn't support them
[Galaxy S 4 i9505 Android Development] Formhault:
Okay. But I thought that SELinux thing is a security enhancement and, thus, is gonna be implemented in the ROM/kernel... So... When you back up ROM/kernel... isn't everything that is in there backed up? That's what I don't get :eek:

Or is SELinux a restricted portion in those partitions (ROM/kernel) that a simple backup won't include unless specially crafted to do so...?

And again. What content will be in that SELinux... thing...? What kind of data? :confused:

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] Stefan1980:
Best recovery i have tryed, for GT-I9505. OP thank you very much!
[Galaxy S 4 i9505 Android Development] squabbi:
It works great! I've made a backup and restore just fine. :)

---------- Post added at 03:54 PM ---------- Previous post was at 03:52 PM ----------

I think its the recovery issue. I remember on my Note that Philz recovery cannot flash CM10 or AOKP roms. TWRP and CWM can do it fine. :\
[Galaxy S 4 i9505 Android Development] Phil3759:
This has no sense. The issue was fixed for note and s2 months ago

If you have an issue, post a log with your question
[Galaxy S 4 i9505 Android Development] victorator:
Phil I got a screenshot from one of the forum members (under 10 posts so he can't post here). Maybe this will help:
[Galaxy S 4 i9505 Android Development] Phil3759:
Nice bug :D

A log would help a lot here

Anyone else having the issue? Also anyone else having it display correctly without errors for /boot and /recovery?

Create a backup. Once done, go to Advanced / Report Error

Zip and attach here the philz_recovery.log file you get in /sdcard/clockworkmod folder

This should help me to spot the issue

Edit 1: i found why it fails to get size of recovery and boot partitions. However, the wired display i did not get clearly. Really need someone with the issue to provide a log
[Galaxy S 4 i9505 Android Development] g-one-ger:
Hey phil here is the log i got the same error as written above...

http://db.tt/GkwdRm5z

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] Phil3759:
Page not found!

Zip it and attach here
[Galaxy S 4 i9505 Android Development] proctologist:
I managed to download it ok. Zipped and attached.
[Galaxy S 4 i9505 Android Development] Phil3759:
Wired :confused:

I see the the reason about recovery and boot being skipped from size stats (I will just change MTD names in fstab), and that's not a bug, just a missing feature

However, those non sense chars mean the char variable is not properly initialized with used "" before an strcat. I see no other cause.

However, in my setup, provoking that situation gives me perfect output in backup stats with missed partitions correctly displayed!

I will release an intermediate fix only for that variable. Once fixed, I will add recovery and boot size detection

Really wired
[Galaxy S 4 i9505 Android Development] Phil3759:
For people with above issue during backup, test this version

http://d-h.st/uWC

This will not remove the skipped partitions message, but should fix the corrupted text display

Please test and let me know if it fixed it or not + a log
[Galaxy S 4 i9505 Android Development] AMDPOWERFIST:
WoW what a sick recovery !!!

Great job Philz - you da man !!!

---------- Post added at 10:39 AM ---------- Previous post was at 10:04 AM ----------

Just attempted a backup

Mine has the exact same error

/boot

/recovery

Unknown partition size (2) :n ;9|

This is with using version:

philz_touch_5.04.0.1-i9505.zip

No idea how to get log files from a recovery, but if you teach me how, i will supply.

Update - I have found "Show Log" in the menus, but that just prints on screen, doesnt save a *.log or *.txt file on the phone (as far as i am aware, i am back into the android OS having a look now)

Update2 - found your post earlier in the thread

attempted to adb pull /tmp/recovery.log

Keep getting Device Offline message

doing a google search to figure out how to fix this.
[Galaxy S 4 i9505 Android Development] nicekit:
i am a bit confused here...

so i should flash the philz_touch_5.03.7-i9505.tar.md5 file first via odin 1.85

then update the philz_touch_5.04.0.1-i9505.zip via the CWM?
[Galaxy S 4 i9505 Android Development] OrionBG:
The official version is 5.03.7 You should try it first!

If you have the problem that have been reported some posts above, then you try 5.04.0.1 to see if it will fix it.
[Galaxy S 4 i9505 Android Development] Phil3759:
It is ok if you report it still there with 5.04.0.1

I can fix it, but I need to know where the variable is modified to output that garbage. Only the i9505 seems affected. I just want to understand where it is modified before I fix it

I will release a tracing release that logs the variable state to track where it is modified "illegally"

To post a log: Advanced / Report Error

You get a philz_recovery.log file in /sdcard/clockworkmod

zip it and attach here

I will release another version. By the way, 5.04.0.1 is full stable and was scheduled for release until you spotted this bug. You can use it as it fixes some issues. Next releases will be debugging
[Galaxy S 4 i9505 Android Development] AMDPOWERFIST:
If its possible Philz,

Add straight under the view log a "save log" function in your recovery, which stores it in the SDCARD or ext-sdcard and i will provide as many log files as you want. I have attempted the ADB connection multiple times, and it seems either my ROM or Kernel (which ever it is) is affecting it to be "Offline" all the time. So ADB connection via USB to extract logs wont work for me.