yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] HaTrED_:
In my case:

show_nandroid_size_progress=1 + compression medium + MD5 -> 6:00m (1,717Mb)

show_nandroid_size_progress=0 + compression medium + MD5 -> 7:12 (1,717Mb)

show_nandroid_size_progress=1 + compression low + MD5 -> 8:06 (1,717Mb)

show_nandroid_size_progress=0 + compression low + MD5 -> 5:04 (1,717Mb)

show_nandroid_size_progress=0 + compression medium + Hide nan. prog.=1 + MD5 -> 4:30 (1,717Mb)

Restore time:

2:36m (OK!)

My reference:

recovery version: 6.8.07

show_nandroid_size_progress=1 + compression medium + MD5 -> 4:00m (1,717Mb)

When i get some more time, i'll do more tests!
[Galaxy S 4 i9505 Android Development] Phil3759:
Many thanks

At least it shows it is not my size check code

It is the default CWM logging code

I will fix it once for all, I hope
[Galaxy S 4 i9505 Android Development] KenHua:
I'm confused by the settings. I tried different combinations but it seems that whenever the progress bar is shown so would the file names. When I set the size progress to off and show the file name, the progress bar would still appear; and the backup is slow. I couldn't get a setting that only show file names. I tried the 4 permutations and that was what I got. Not sure what I was doing wrong...
[Galaxy S 4 i9505 Android Development] Phil3759:
Hiding all progress will override size stats setting obviously

When you show progress bar (+file names) and hide size stats, the logging doesn't change at all

I am going to add a setting to stop the logging of file names by default. Depending on the journalling used on devices it can kill backup/restore times to internal storage. If you use ROM Manager, you'll see an option to disable progress bar (so logging) to speed up things
[Galaxy S 4 i9505 Android Development] Socim:
Hi,

I don't know why but I can't do backup to external. My sdcard is SanDisk 64G and formated as ntfs. Is there any problem with the ntfs file system?
[Galaxy S 4 i9505 Android Development] Phil3759:
What idea did you have to try it?

You spotted a bug I hoped no one notice until later when I have time to fix it :D

NTFS is only read. Seems like kernel modules from sammy are read only despite enabling Read/Write flags when compiling kernel

I could have to drop to fuse as I have no idea if it is possible to fix while using kernel modules
[Galaxy S 4 i9505 Android Development] BillGoss:
Good point about the settings. This was thrashed out quite a while ago in version 5 of PhilZ.

I've updated my post to include the settings I used.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
:crying:

too bad you added this only now:

Normally, on new versions, those settings shouldn't impact speed

The only thing is when using backup to internal storage maybe afetr some changes to ext4 mount options, not sure, have to verify if something changed in that regard
[Galaxy S 4 i9505 Android Development] tdevaughn:
thanks phil, look forward to trying this on the AT&T S4. Just learned of your work and am running it on my Galaxy Nexus,

Keep up the great work!
[Galaxy S 4 i9505 Android Development] Marchintosh:
What's app Koush?
[Galaxy S 4 i9505 Android Development] Phil3759:
5.04.9: come one, this should make you happy, or it's getting so sick to remotely work on i9505 :p

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

If I can get a quick feedback, I'd be so grateful for the hours this phone took me

Target people are those having exfat issues with 64Gb cards: please post if it now mounts
[Galaxy S 4 i9505 Android Development] cbeckstein:
Full nandroid to external 64GB exFAT SD card just completed successfully (including generation of MD5 sums)

Still complaining about sd-ext problems in the beginning (cannot determine partition size) and right before MD5 is generated (no sd-ext found), but

we got a winner here!

Thanks again for the quick exFAT fixes
[Galaxy S 4 i9505 Android Development] Phil3759:
Thank you and all users who are testing and providing logs

That's how things can be fixed, as remember, I do not have the device to test, so entirely rely on your tests, which takes time and trials

Happy it works finally

By the way, there is still a small bug in original CWM that my recent changes revealed and reported for another device.

I will release the final 5.05.0 in a few minutes and go to rest a bit
[Galaxy S 4 i9505 Android Development] joshua.justice:
If I flash this and it didn't work I can just flash a different one over it with Rom manager can't I?
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, flashing what is not supposed to be flashed can be very risky, really

For example: flashing i9300 on n7100 will burn the display chip

Ask in your device forum maybe before tempting anything like this
[Galaxy S 4 i9505 Android Development] AMDPOWERFIST:
5.04.9 version has a weird bug.

Mounting external SDcard backup to /media/0 or normal /media and attempting to do a backup to external comes up with errors (on mine atleast)

i also tried to "report issue" again to create log for you, but it doesnt want to output a .log file anymore...?

Any ideas? i can provide more logs if i can get it working again.
[Galaxy S 4 i9505 Android Development] xologist:
So all I gotta do is flash the .ZIP with Odin in PDA?

Also, my phone is rooted, but with no custom ROM. Is that ok?
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, actually you are confusing internal/external

Only internal sdcard is /data/media

external_sd has nothing to do with /data/media

When you cannot provide a log, below command will pull it from ramdisk

adb shell
adb pull /tmp/recovery.log
[Galaxy S 4 i9505 Android Development] chubby65:
Yes mate it's ok
[Galaxy S 4 i9505 Android Development] Phil3759:
I removed all previous debug versions from download

Tomorrow, I will upload v5.05.0

As I said, mounting external sd can fail under some circumstances on last versions because of a bug in original cwm revealed by a change I did

exFAT for big sdcards is confirmed to work now, so expect a good build tomorrow hopefully
[Galaxy S 4 i9505 Android Development] AMDPOWERFIST:
ah ok my bad

i was getting a few errors when trying to backup to external source

keeps saying "Cant mount backup path"

however, a solution that does work:

Click backup to external source

keep getting error "Cant mount backup path"

Click "Delete from External SDCard"

Click "Backup to External Source"

and it works again....

something in the delete function allows it to mount to external SDcard

Anyways, i managed to get the ADB commands working while in Recovery.

Here is the script i produced. it also has the function above in it
[Galaxy S 4 i9505 Android Development] Phil3759:
Thanks

It confirms it is the bug I am talking about

I committed a fix for it on my github a few hours ago.

It will be fixed on next version. Just compiling now for all devices
[Galaxy S 4 i9505 Android Development] AMDPOWERFIST:
no problemo, thanks again for all your help and dedication Philz - we're all very appreciative of the time and effort put in to debug for a phone u dont even own !!!
[Galaxy S 4 i9505 Android Development] thunderserpent:
in TWRP there is a "mount modem" option, will this be included in this recovery as well?
[Galaxy S 4 i9505 Android Development] Phil3759:
For now, flashing modem in i9505 is not clear if we need only one partition. Until then i will keep it disabled. If you know a working flashable modem zip in recovery, post here and i will enable the feature. Also if someone has flashed modems with success, let me know
[Galaxy S 4 i9505 Android Development] daniello8:
Hi guys, sorry to nag .. I'm on faux kernel which doesn't support exFAT at the moment. The option is either go with FAT32 and live with the file size limit but have native suport or use NTFSmount and live with the fact that SD gets mounted with a short delay.

What I'm worried about is backing up the device.

I learned that this recovery is capable of splitting files into file-system-appropriate chunks. This is superb.

What I don't know is whether I can go with either FAT32 or NTFS or not. Will PhilZ Touch support both?

In this case I would go with FAT332.

Please shed some light :)

BTW: All this because I'm preparing mentally for my 64GB SD card which I ordered lately.
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.05.5

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

Still uploading. Please refresh devhost link in a few minutes

Hope this make all happy.

If not, I will revert to my previous patches related to mounting different fstypes, which were proven solid since I started this

No NTFS support for now
[Galaxy S 4 i9505 Android Development] Eyghon:
Phil, yesterday you answered someone, that your recovery contains koushs superuser app. What, if currently another superuser app is installed. Does it conflict somehow or does your recovery prevent installing a second su app?
[Galaxy S 4 i9505 Android Development] BillGoss:
I *did* include the log files which would show the settings. :cool:

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Socim:
Thank you so much [MENTION=4666971]Phil3759[/MENTION]. I got it.

I have used exfat previously but the file system was suddenly broken and I was not able to recover any data, so I thought I should try a journaling fs, and as I still need to transfer data with Windows, ntfs is the only solution.

I remember I was able to backup my data to this sdcard with my customized kernel on dalil, so I think it's possible to get the full access to ntfs partitions with following config:

CONFIG_NTFS_FS=y

# CONFIG_NTFS_DEBUG is not set

CONFIG_NTFS_RW=y

I will try to build a customized kernel for jfltexx in a few days, so most probably I can fix it by myself if you don't have time. :D Thanks for all your time and effort.
[Galaxy S 4 i9505 Android Development] Phil3759:
No because hide progress toggle is stock CWM: it depends on a file. The set state doesn't show in logs ;)
[Galaxy S 4 i9505 Android Development] Phil3759:
I already use those settings and it did not help

Please post your feedback once you try to compile on your own, I will appreciate it a lot
[Galaxy S 4 i9505 Android Development] Socim:
Thanks. I will.
[Galaxy S 4 i9505 Android Development] BillGoss:
:( Maybe it's time to get this value written out to the logs?

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, I could guess it since there are no file names in log. However, I thought you manually remove them for privacy as many do
[Galaxy S 4 i9505 Android Development] buachaille:
Where is the i9505 file on the download page. I can only see an i9500.
[Galaxy S 4 i9505 Android Development] phil.o:
Do you already noticed the thread title?

Look under 'jfltexx'.

°°° tapatalked °°°
[Galaxy S 4 i9505 Android Development] kfallz:
Well for whatever reason backup speed is, yet again, back to awesome xD

Did a backup earlier and I think it landed at 7:40 or around there, high compression to external sd, all stats hidden, 2.2gb after compression so quite a lot of stuff. Goodgood ^^
[Galaxy S 4 i9505 Android Development] Formhault:
I'm pretty sure it's under iPhone5S.
[Galaxy S 4 i9505 Android Development] MJD:
I have just downloaded 6.12.8 for i9505 (jfltexx). The md5 file says 5dab83b9e3dd8ef56e49342462fd2967 but the zip file says 35cca63ece6661341ad0dbf0f69b2548

Can you confirm that the zip is ok to flash?.

Cheers
[Galaxy S 4 i9505 Android Development] KenHua:
You are mixing up the zip checksum with the tar.md5 version. Your download and checksum are correct. The download site shows correct checksum too.
[Galaxy S 4 i9505 Android Development] Socim:
Md5 should be flashed via odin and zip for CWM.
[Galaxy S 4 i9505 Android Development] MJD:
Ha, sorry, what an idiot. That's what happens when you have no sleep. Cheers.
[Galaxy S 4 i9505 Android Development] Socim:
Tested.

6.07.9 + customized kernel on dalil: successful

6.12.8 + customized kernel on jfltexx: failed
[Galaxy S 4 i9505 Android Development] Crimsonsky360:
Please fix its..i cant change custom rom..it show Error status 7
[Galaxy S 4 i9505 Android Development] triathlete66:
didn't you read previous pages and FAQ?
[Galaxy S 4 i9505 Android Development] DSA:
Looks like you flashed this without reading a single line from the op
[Galaxy S 4 i9505 Android Development] Phil3759:
I did not get you

what is dalil?

Can I decrypt from your post that in fact, Samsung disabled NTFS write?
[Galaxy S 4 i9505 Android Development] Socim:
Dalil is a variant of Samsung S2 HD LTE, which is msm8660 based.

I am not sure where is the problem, can you please let me know if you have did any change about ntfs since 6.07.9?
[Galaxy S 4 i9505 Android Development] Phil3759:
No

On 6.07.9 it was working for jfltexx?
[Galaxy S 4 i9505 Android Development] Socim:
I'll give it a try.
[Galaxy S 4 i9505 Android Development] daibaron:
Thanks for this great work, Philz.

I am still having time & date issues like most of us here.

i tried checking Qualcom Daemon time and date it actually worked until next reboot.

But after it didn't work again.

6.12.8 Release
[Galaxy S 4 i9505 Android Development] Phil3759:
I will update FAQ with a how to

Search mean while

Just use the time offset trick
[Galaxy S 4 i9505 Android Development] franzyroy:
For me, I've not looked the date but the time works fine.
[Galaxy S 4 i9505 Android Development] KenHua:
May be I'm lucky but my date and time worked just fine. Just curious though how did you determine that "most of us here" had problem?
[Galaxy S 4 i9505 Android Development] sarbe:
Because it has been mentioned numerous times.
[Galaxy S 4 i9505 Android Development] BillGoss:
So if the people who have the problem mention it, but those that don't have problems don't mention it, then based on comments 100% of people have the problem?

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
LoL

+ they never answer any of my requests, nor provide a log
[Galaxy S 4 i9505 Android Development] sarbe:
Obviously not but nor did he say 100% of people have the problem only you have posted that. He's obviously not phrased his comment well, be it a language problem or just not thinking but there are enough smart arses on here who have nothing better to do than attack people's posts without you trying to be another one.
[Galaxy S 4 i9505 Android Development] KenHua:
It is a not question of language but a question of mindset. Prejudices don't help solve the problem; they tend to irritate the developers and slowed things down! It is best to be objective and specific when a problem is found. Cheers,
[Galaxy S 4 i9505 Android Development] Socim:
It doesn't work. Finally I realized that you include fuse in the recovery for celoxhd and I ported it for dalil. So even the ntfs partition was mounted as rw, but it can only modify files and is not able to create files and folders. Please refer to kconfig in /fs/ntfs.
[Galaxy S 4 i9505 Android Development] Phil3759:
You mean i can fix it or it is related to samsung kernel

In that case, i will drop to fuse for all ntfs needs
[Galaxy S 4 i9505 Android Development] Socim:
Yes I suppose it will work if you drop to fuse. :D
[Galaxy S 4 i9505 Android Development] Phil3759:
Thanks

I was hoping we can get write possible using kernel modules

I will drop to fuse-ntfs for all devices
[Galaxy S 4 i9505 Android Development] hawkerpaul:
For me, 6.12.8 has re-introduced the occasional hang when booting into recovery.

I didn't seem to get this at all in the previous couple of builds.

Anyone else getting this?

Is there a log I can post up if this happens again Phil?

And one small thing Phil. Far more often than not, I wipe cache along with dalvik cache. I've hardly ever wiped one without the other in the past.

Do you think it may be a good idea to include a "wipe cache+dalvik cache" option to save time?
[Galaxy S 4 i9505 Android Development] Phil3759:
There is a new fix i will release soon
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.13.1

- merge samsung ramdisk changes to fix random hang on boot
[Galaxy S 4 i9505 Android Development] KenHua:
Excellent! Booted up without hesitation. Very fast backup performance. Thanks for the great work!

Backup complete!

Backup time: 03:50 mn

Backup size: 1305.39Mb

Compression: 42.66%
[Galaxy S 4 i9505 Android Development] Sly955i:
Ok so I updated to the latest 6.13.1, did my first backup to my external SD card. Using low compression it took a total of 50 mins to back up my Wicked V10 rom.... Any ideas on how to speed the process up a little, I have tried removing progress bar and all from reading previous posts, any help would be awesome as I think this recovery is by far the best
[Galaxy S 4 i9505 Android Development] heblu:
Hi,

Why after I flash a new rom I cannot enter into recovery using vol up + pow + home button?

Tried with stock rom, phoenix, nameless rom.

If there is an option to reboot to recovery it works, but if the phone is off and I try to enter recovery, it doesn't work

Also I tried 3 different versions of Phils Touch

Thanks!
[Galaxy S 4 i9505 Android Development] Bejda:
Better way to manually enter into recovery on s4 is to just push volume up button right after the device start vibration,try and see if it's ok that way ;)
[Galaxy S 4 i9505 Android Development] CarlM34:
You are probably not getting it quite right:angel:

When phone is off....

Press and hold power + volume up

Phone vibrates and Samsung logo appears with red/blue writing in top left corner

Release Power button ONLY keeping volume up pressed

Second vibration and Samsung logo appears with red/blue writing in top left corner

Release Volume button

Should then boot to recovery

:):fingers-crossed:
[Galaxy S 4 i9505 Android Development] heblu:
Thank you very much for details and fast reply !!

It's working now, I did not follow these steps :)
[Galaxy S 4 i9505 Android Development] Bejda:
Frankly your phone vibrates > you just press volume up button and it's ok, works every time in any situation (boot,reboot,forced reboot).

Quiet and classy way lol.
[Galaxy S 4 i9505 Android Development] HaTrED_:
No more, no less! :good:
[Galaxy S 4 i9505 Android Development] brockyneo:
hi sorry if been asked before im setting up the time and date but everytime i restart phone it resets itself does this feature not work on the s4

thanks for the amazing recovery :D
[Galaxy S 4 i9505 Android Development] koko115:
Can i please to add delate battery stats ?
[Galaxy S 4 i9505 Android Development] Formhault:
It's useless. You don't need it.
[Galaxy S 4 i9505 Android Development] RK:
Just charge your battery to 100% and voila! Battery stats deleted!!
[Galaxy S 4 i9505 Android Development] greeny2010:
I got error like signature verification failed when flashing the rom. What's the cause?
[Galaxy S 4 i9505 Android Development] Phil3759:
it is not properly signed

Disable signature checks
[Galaxy S 4 i9505 Android Development] zeus85:
I get this this to when I disable signature checks it still does it is there anything I can do to sort it out or help with logs when I get today's cm11 nightly
[Galaxy S 4 i9505 Android Development] Phil3759:
humm,

maybe they updated the OTA signatures for their nightlies and we need a sync!

This sucks

Unless you are installing from cm-updater: I think the signature verification doesn't stick on reboot of recovery. You'll have to manually install the package from recovery AFTER you disable the signature check
[Galaxy S 4 i9505 Android Development] zeus85:
Yeah Its when I'm using cmupdater so iv been installing direct through recovery which never giver me any problems apart from that everything is great love the setup I don't mind installing through recovery just thought I'd let you know in case no one had reported this to you
[Galaxy S 4 i9505 Android Development] greeny2010:
How to disable the signature check? This happens when I use Odin or stock recovery.
[Galaxy S 4 i9505 Android Development] Formhault:
Install Zip -> Toggle Signature Verification.

Hmm... [MENTION=4666971]Phil3759[/MENTION]? I toggled signature verification and it showed Signature Check: Enabled. On a second touch, it got disabled. It's disabled by default?!
[Galaxy S 4 i9505 Android Development] Phil3759:
:good:

Sure I appreciate these small remarks

I just added a toggle for this

Will be implemented on next update

Maybe you skipped a tablet?

I

I

I

I

I

v

:D
[Galaxy S 4 i9505 Android Development] Phil3759:
My bad, you are true

After start, it is disabled when checking start up scripts.

Do not ask me why :p
[Galaxy S 4 i9505 Android Development] zeus85:
Forgot to check logs my bad il defo do it tomorrow and report back to you phil3759
[Galaxy S 4 i9505 Android Development] Formhault:
So you're from Turkey :)

Sorry for skipping today's shipping... You'll get your tablets in no time :silly:. Jokes aside...

By disabling signature verification, it's like we're bypassing the checks in the updater-script? That way, basically we'd be able to flash a file regardless (say, even if it's made for the One X, we would still be able to flash it - not like I intend to do that or anything like that... just an example - so hold your horses!)? :D
[Galaxy S 4 i9505 Android Development] Phil3759:
No, only for signed/unsigned zip files, basically, an integrity check before flashing a modified zip

All my files are signed for example
[Galaxy S 4 i9505 Android Development] greeny2010:
I can't even install the zip/tar file at all. Abort halfway after showing the signature verification failure. Using odin or chainfire recovery fpr the flashing. Have tried the various version listed.
[Galaxy S 4 i9505 Android Development] franzyroy:
[MENTION=4666971]Phil3759[/MENTION]

Hi,

I think you must to know this issue. do you think you could correct it? It works fine with the version 6.09.2 like Bejda said me.

Thanks 4 ur great work! ;)
[Galaxy S 4 i9505 Android Development] edzamber:
Subscribed :)
[Galaxy S 4 i9505 Android Development] franzyroy:
It's 4 me? If yes, I don't understand! :confused: Could you be more clear?
[Galaxy S 4 i9505 Android Development] edzamber:
No, its only to say i have Subscribed to this topic, like that i can have all notifications with Tapatalk and see thread into participate tab ;)

Posté via Pyrana v29 4.4.2 NA5
[Galaxy S 4 i9505 Android Development] franzyroy:
Ah OK... Sorry! ;)
[Galaxy S 4 i9505 Android Development] zeus85:
Finding update package...

I:Update location: /data/media/0/0/cmupdater/cm-11-20140213-NIGHTLY-jfltexx.zip

Opening update package...

I:read key e=3 hash=20

I:read key e=65537 hash=20

I:2 key(s) loaded from /res/keys

Verifying update package...

E:failed to open /data/media/0/0/cmupdater/cm-11-20140213-NIGHTLY-jfltexx.zip (No such file or directory)

I:verify_file returned 1

E:signature verification failed

I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.

I:using /data/media/0 for /sdcard

I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.

I:using /data/media/0 for /sdcard

E:Can't open /data/media/0/0/cmupdater/cm-11-20140213-NIGHTLY-jfltexx.zip

(No such file or directory)

Installation aborted.

I:setting up /data/media(/0) for /sdcard.

I:using /data/media/0 for /sdcard
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.15.4

Huge change log in main thread

You can save check signature state now for cm updater

You can also force using update-binary from zip to overcome bad status 7 errors
[Galaxy S 4 i9505 Android Development] franzyroy:
Is it possible that the last corrects this issue? It'll be sad to me to use another recovery... I like your work. :good:
[Galaxy S 4 i9505 Android Development] Phil3759:
I did not understand your issue!
[Galaxy S 4 i9505 Android Development] franzyroy:
When I install ShoStock rom with another recovery that the 6.09.2, like secondary rom in the DualBoot, I've modem and IMEI which are unknown. but it's only for the secondary rom, no issue with the first. With the 6.09.2, no issue!