yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] Phil3759:
No need to extract it that way:

You go into the Advanced menu, then use the report error menu

It will save a log to /sdcard/clockworkmod/philz_recovery.log

That log can be accessed when you boot in main ROM. Just be sure to use a root explorer to access /data/media if you did not enable /data/media/0 path in Advanced menu
[Galaxy S 4 i9505 Android Development] AMDPOWERFIST:
aha gotcha

i already enabled media/0 as i read it earlier somewhere in the thread.

ill do a backup now, and straight after report error then add the logs here for you.

report back in a minute:
[Galaxy S 4 i9505 Android Development] Phil3759:
No need for now as it won't help me much except seeing that something is overwriting my variable in memory :confused:

I am compiling a new debug version

Also, you can cancel the backup when it starts, as the message error is at the start, so no need to wait for it to end
[Galaxy S 4 i9505 Android Development] AMDPOWERFIST:
oh well here it is anyways.

Now i know how to do it, ill test all the versions to iron out any kinkz
[Galaxy S 4 i9505 Android Development] Uhu911:
I am having the same error. Nor recovery and boot partition size. (will it make a backup nontheless or is the backup unuseable?)

Backup to SD only works with exfat and not fat32 am I right?

My SD Card is formatted in FAT32. The last step of regular backup seems to hang itself.
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.17.9 ** Beta **

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

It is under the beta folder

This version should fix backup/restore issues of 4.3 new ROMs

Test and report
[Galaxy S 4 i9505 Android Development] Formhault:
My bothering question was, in fact... what is inside that SELinux thing. What possibly could rely in there. :D

For example, in the ROM you got things like apks and ringtones and stuff... In the SELinux context you have... hyperdrives and such? :D

I assume this is getting annoying. Sorry about that...

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] BillGoss:
I tested 5.17.9 to backup and restore cm 10.2 (4.3.1) and it worked OK. There were some errors issued, see https://db.tt/NL8c2wES, but they didn't appear to have any effect.

Both 5.17.7 and 5.17.9 did not do a clean system reboot (I had to do it twice) and they didn't preserve previous logs - they simply overwrote last_log.

I use TWRP format for my backups.
[Galaxy S 4 i9505 Android Development] KenHua:
5.17.7 is still the best to me

I was very happy with 5.17.7. Seeing Phil working so hard I thought the least I must do is to give the 5.17.9 Beta a try. The result was a bit of a set back with backup time double that of 5.17.7 i.e. about 10mins. I reverted back to 5.17.7 and did another backup just to be sure. This time i changed the compression from "Fast" to "Med" and the backup time improved further to 4mins and compression improved from 37% to 40%.

I9505; ROM: Deodex Stock MI1; Kernel: Adam 1.6+; Show Nandroid Size (x);
[Galaxy S 4 i9505 Android Development] Phil3759:
This is expected as backing up selinux context is actually done using an extra step routine

Once tar sources are modified in cm busybox, things should be faster. I will look at enhancing current code to see if we can speed up things

I see some crash in your logs there. When did the crash / pseudo reboot happen exactly? I tried a twrp backup and couldnt reproduce the issue. Could be some selinux errors on restoring system!
[Galaxy S 4 i9505 Android Development] Borfas:
before work perfectly. latest CWM PHILZ TOUCH have very very bugs !!!!!
[Galaxy S 4 i9505 Android Development] Phil3759:
Oh my god

And what are those very very bugs?

Do not use beta versions to just report this

Latest non beta is perfectly working. If you find a bug, report is precisely with a log

Stable:

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

Beta

http://d-h.st/users/philz_touch/?fld_id=25841#files
[Galaxy S 4 i9505 Android Development] vikash0513:
Can't make ext4 partitions on sd-ext :crying:
[Galaxy S 4 i9505 Android Development] Phil3759:
Actually you can

But, you won't be able to use it in recovery for now

New cm-10.2 vold doesn't support second partition on external storage

I will look at it how we can enable it again
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.18.0 ** Beta **

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

I tested on latest cm-10.2 Nightly 11 oct 2013 build

My log is attached

It perfectly backed up/restored selinux context

After restore, 4.3.1 ROM is working perfectly

Reboot to system from recovery works without issues

MH1 leak users should give this a try too as it should backup and restore perfectly, I hope
[Galaxy S 4 i9505 Android Development] vikash0513:
I am not using cm-10.2 but omega v12
[Galaxy S 4 i9505 Android Development] Phil3759:
It is recovery. Nothing to do with rom
[Galaxy S 4 i9505 Android Development] vikash0513:
Ow okay phil can't wait untill It is fixed
[Galaxy S 4 i9505 Android Development] boostermbkking:
i have foxhound 2.0 rom and asdmin kernel, why with 5.17.7 recovery when i do a nandroid backup the date and time are wrong?its 1970... why?
[Galaxy S 4 i9505 Android Development] sydknee:
On 5.17.7 got a nandroid time of 18 mins. Compression no. Tried to change the compression setting but nothing happens, just reverts back to no....

EDIT: Ok, sorry to spam this thread. Just realised didn't change the backup format first. Doh.
[Galaxy S 4 i9505 Android Development] BillGoss:
After I restored the backup I rebooted the system using the menu item. But it didn't, so I rebooted it again, then it worked.
[Galaxy S 4 i9505 Android Development] svenk:
Hello,

Reading here the last few days, I finally decided from 5.14.7 to the new 5.17.7, and I'd like to share my experiences:

1. Date and time problem:

With the older version, out of five runs into recovery I had one with the wrong time, four runs showed the correct date and time. So it was not a regular thing for me. When the wrong time showed, I just had to re-boot into recovery and the correct time was set most likely.

However, with the new current version, I had the wrong time every time I booted into recovery. This is when I first decided to do the CMOS reset, pulled the battery and waited 12 Hours and 9 Minutes. But that did not solve the problem: the time still was incorrect. I noticed that this time, on normal reboot, I got the wrong time for some seconds, too, until the system managed to fetch the correct time from the network. Apparently, something had been actually reset, but it did not affect recovery time.

Then I tried the method to flash Abyss kernel, boot into Android, delete file 01abyss, and re-flash Adams kernel 1.6 knox-free (which I had installed previously). This method finally worked.

One remark: 01abyss was not locatd in /system/etc/init.d but in /res/misc, as somebody before already stated. I deleted that one with root explorer before I flashed back Adams kernel.

2. Backup speed:

I made a backup to my external FAT32 formatted 32Gb SD card, med compression, MD5 sum on, Hide Progress ( ) and Show Nandroid Size (x): The original size of 4642Mb resulted in a backup size of 3060Mb, which took 17:03 Minutes to complete.

I think this is a great performance. However, I did not try restore anything and hope it will work when I need it ;)

I would very much appreciate if Titanum Backup would soon learn to deal with compressed nandroid backups, however... Does anybody know if an when this will be the case? Or should I stick to non-compressed backups?
[Galaxy S 4 i9505 Android Development] BillGoss:
Some more information. The reboot problem only happens when restoring from the external SD card (/storage/sdcard1). And it happens for both TWRP and cwm backups.

Also, the failed reboot turns the screen black and after a short time recovery restarts. The phone does not go through the normal reboot process (no vibration, no Samsung splash screen).

The other thing I noticed is that after the failed reboot, the backup and restore menu list is missing all the /storage/sdcard1 items, only the /sdcard items are listed.

In case they are of any help, here are the logs for the restores for both TWRP and cwm, for both external SD card (.esd) and internal sdcard (.sd). https://db.tt/Bv00KxPD

Update: the same reboot issue happens with 5.17.1 as well as 5.17.7 and 5.18, so I guess this is related to the cm 10.2 ROM (20131011, 4.3.1) as i don't recall this happening on previous ROMs with 5.17.1. But I may be wrong.
[Galaxy S 4 i9505 Android Development] Phil3759:
Thank you

Seems like some crash either in vold or in exfat modules

Do you remember what version started with this? Prior to 5.17.9 ?
[Galaxy S 4 i9505 Android Development] JackYack13:
Will this work if I'm using the leaked 4.3 firmware from samsung (XXUEMJ3)?
[Galaxy S 4 i9505 Android Development] Phil3759:
Test and report. It should

Ok, could reproduce it. Thank you. Seems after restoring /data, minivold is crashing. I will look at it
[Galaxy S 4 i9505 Android Development] svenk:
Regarding the Date/Time issue: I searched the forum for "RTC" and found this interesting thread:

http://xdaforums.com/showthread.php?p=30522425

For whom it might interest. The issue already existed for the S3 apparently. According to that post, if the RTC is written to at least once, it will show the correct date/time. However (what I did not quite understand) it might happen that, when written to more than once, you may lose modem connectivity because it gets out of sync (how, if you only write the correct time?). This seems to be the reason why Abyss kernel repairs the recovery time (by writing RTC), and why only few kernels actually write to the RTC.

Btw. if you are affected, you do not only have wrong time in recovery but also when you boot in airplane mode.
[Galaxy S 4 i9505 Android Development] Phil3759:
I stopped to write to rtc as it caused many issues previouly
[Galaxy S 4 i9505 Android Development] svenk:
Well, Abyss kernel writes to RTC, and the issue it caused for me was that I do now have correct time and date in recovery ;)

But I flashed back Adams kernel afterwards. Which btw/ I only had to flash because with rooted stock kernel I do not have Wifi. Strange things happen with this phone...
[Galaxy S 4 i9505 Android Development] Phil3759:
This was hard to track

Had to flash all versions until found the source. It is caused by vold crashing as I supposed. The cause is volume was busy and vold cannot support that (vold bug in cm-10.2). However, volume remaining busy is the main cause to fix. I found why. I'll fix it on next update
[Galaxy S 4 i9505 Android Development] BillGoss:
I totally agree. I've never seen problems with time and rebooting on other devices. I'm convinced that there are some low-level design issues with the S4. Fortunately the S4 runs really well once it's booted up.
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.18.2

Download:

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

Hope this is a final version. I tested it largely

Many thanks [MENTION=2911853]BillGoss[/MENTION] for your last report. It let me fix a few bugs
[Galaxy S 4 i9505 Android Development] KenHua:
I installed 5.18.2. Data/Time is running fine, just as before. Did a backup run and the speed was good. Below is a summary of my backup time of a few recent versions:

5.17.1: 25 mins

5.17.7: 5 mins

5.17.9: 10 mins

5.18.2: 6 mins SEL: Off

Ref: Phone: I9505; ROM: Deodex Stock MI1; Kernel: Adam 1.6+; Show Nandroid Size (x); Compression (Med) Size: 3.2GB >> 1.9GB

Will keep the latest version for its improved features and stability.

Thanks a million to Master Phil

Update:

For whatever that's worth I ran three more tests on 5.18.2 with some different settings:

1. Compression High: 9:37mins / 39.7% compressed

2. Compression Fast: 3:21mins (It surprised me but that's what I got -- New benchmark for me!) ***** / 37.4% compressed

3. Compression Fast to ExtSdCard (Class 10 FAT32): 5:53mins

Compression Ratio between Fast and High is very close: Difference is only about 2% pts
[Galaxy S 4 i9505 Android Development] BillGoss:
Problem fixed - thanks. Now all it needs is for the restore process to keep the previous last_log and not overwrite it, and reduce some of the logging so that it doesn't produce a 1.12 MB log (compared to the 11 kB backup log) :D

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
last_log is always overwritten, it is expected

however, logs are rotated and 5 logs are always kept. That's how Koush did it

What is exactly your issue if I am missing something?
[Galaxy S 4 i9505 Android Development] BillGoss:
The rotation doesn't happen so the log prior to the restore is lost.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] z-vet:
[MENTION=4666971]Phil3759[/MENTION]: DST is broken here. I installed Abyss kernel to fix time issue. It went fine, but now checking DST in options add 1 hour to real time.
[Galaxy S 4 i9505 Android Development] fredphoesh:
oodear

Using Odin, (just R reset time and reboot set - NOT partition) I am getting this fail message

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

and now cannot boot the phone or get to recovery mode...

any ideas what to do? I think my phone needs to be re partitioned, I have had similar things to this previously

tx

Mark.
[Galaxy S 4 i9505 Android Development] starbucks2010:
Why you didn't try to flash the new version using cwm? What are Odin benefits over cwm?
[Galaxy S 4 i9505 Android Development] Phil3759:
Strange, can you explain me how to reproduce this?

I tried to reboot into recovery 5 times, and after each reboot I do:

adb pull /cache/recovery

I see the pulled logs rotating perfectly on each reboot

backup/restore logs are huge because CWM logs every processed file. On new version, completely disabling the logging (Hid Progress) won't affect speed a lot, less than 1 mn difference
[Galaxy S 4 i9505 Android Development] fredphoesh:
Hi mate,

I dont think I ever had a white cable, but I will try another one, just tried another computer with the same result.

I also tried flashing stock rom, and got a failure too... I cant get to recovery mode either, it now says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" but kies sees the phone but cannot connect.

I'll try another cable, tx

Mark.
[Galaxy S 4 i9505 Android Development] pitcher85:
Actually many people (including me) had problems when flashing with 'just' an USB cable.

Often I forgot the cable fact, tried flashing --> didn't work. Then I got remembered to use the original USB cable and it worked without problems.

And next time, just use the flashable zip file of PhilZ recovery ;)
[Galaxy S 4 i9505 Android Development] fredphoesh:
holy crap,

third cable, second computer, different USB slot, second attempt... WTF maybe I have a virus on my PC's or something... really odd.

Tx
[Galaxy S 4 i9505 Android Development] Formhault:
Lots of strange things happening with USB cables. But only when it is put in the context of a Samsung smartphone...

I mean look at how bad the phone charges via another cable. Chances are 3 out of 5 are not according to Samsung's liking and won't be able to deliver enough current and... well... Gotta love Samsung :)
[Galaxy S 4 i9505 Android Development] eak1080:
its basically casue samsung is maxing out the usb 2.0 spec with their cable
[Galaxy S 4 i9505 Android Development] Formhault:
What do you mean? USB2.0 is USB2.0.

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] BillGoss:
Here's what I did (using TWRP format)

1. Backup and reboot into ROM

2. Check contents of /cache/recovery. Log from the backup is last_log. Previous restore is last_log.1:

-rw-r--r-- root root 51 2013-10-12 09:55 last_install
-rw-r----- root root 11869 2013-10-16 07:00 last_log
-rw-r----- root root 1180577 2013-10-15 15:34 last_log.1
-rw-r----- root root 1179785 2013-10-15 15:05 last_log.2
-rw-r----- root root 11761 2013-10-15 14:51 last_log.3
-rw-r----- root root 11350 2013-10-15 07:56 last_log.4
-rw-r----- root root 20830 2013-10-14 17:11 last_log.5

3. Restore backup and reboot into ROM.

4. Check contents of /cache/recovery. Logs not rotated, current last_log is for the recovery and backup log is lost:

-rw-r--r-- root root 51 2013-10-12 09:55 last_install
-rw-r----- root root 1238871 2013-10-16 07:07 last_log
-rw-r----- root root 1180577 2013-10-15 15:34 last_log.1
-rw-r----- root root 1179785 2013-10-15 15:05 last_log.2
-rw-r----- root root 11761 2013-10-15 14:51 last_log.3
-rw-r----- root root 11350 2013-10-15 07:56 last_log.4
-rw-r----- root root 20830 2013-10-14 17:11 last_log.5

Thanks for explaining why the recovery log is so large. I can live with it.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
backup log is copied into backup folder normally, verify it is there please and let me know

I will try to reproduce the rotation issue on backup/restore

Thank you again for detailed info
[Galaxy S 4 i9505 Android Development] Ritchiejoe:
Hey Phil

I am currently using the 6.0.3.7 version of your recovery, Suddenly every time I try to restore back up i am always getting an md5 mismatch error, Any ideas?

Is the newest version stable enough? I may flash if it is :)
[Galaxy S 4 i9505 Android Development] Phil3759:
You probably disabled md5 and now it is enabled. Either disable md5 check or regenerate it in recovery
[Galaxy S 4 i9505 Android Development] torque7:
Can I flash 5.18.2 version of your recovery in galaxy grand duos, because in galaxy grand's thread last version is 5.15 and it doesn't fully recover from backup.
[Galaxy S 4 i9505 Android Development] hisname:
are you kidding me? you are in the wrong thread
[Galaxy S 4 i9505 Android Development] BillGoss:
Log file in the backup directory is only ever produced for CWM backups. I checked that they are there. But none are ever produced in the backup directory for TWRP backups. And I have backups going back a month where this is the case.

Please note it's only on recovery (TWRP - I haven't tested CWM as I don't use that format) that the rotation doesn't occur on 15.8.2. It's fine on backups.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Ok, more clear now. Will try to reproduce it
[Galaxy S 4 i9505 Android Development] fredphoesh:
It does not make "logical" sense to me either, I mean, there are several connectors, and a cable between them, and if they are all working and the connections are not faulty, then every cable shoud be very close to 100% identical... but the reality is they are not, not by a long shot... go figure. I do not understand that!
[Galaxy S 4 i9505 Android Development] Solark:
Anyone have issue when trying to wipe dalvilk cache or format cache, system, data, sd card, etc?

Same about data/factory reset clean for a new rom i have always a error about the card on the philz_touch_5.18.2-i9505

And i must use old version :(
[Galaxy S 4 i9505 Android Development] Phil3759:
Ok

For log copied to backup folder in twrp mode, I will add the feature

For your rotstion issue, this is what happens to you:

- check logs order in main system

- reboot into recovery and do a backup with cache included

- you reboot into system and verify logs: they are rotated compared to first check you did

- you reboot into recovery: rotation happens on recovery start . You can verify it by adb pull /cache/recovery

- you do a restore: bang, cache restored!!!

- back to system ---> seems like you lost rotation but in fact it is the restore

Rotation happens on start of recovery for debugging in bootloop issues mainly when porting new devices
[Galaxy S 4 i9505 Android Development] Formhault:
I guess it comes down to the actual wires inside the cable. The copper's density changes over time (even very slightly, like, say, 0.001% change in the material itself)... and Samsung seems to have implemented a method to detect those changes, thus rating cables bad, which would otherwise work perfecty with another phone...

I just thought it's only about charging. If it also affects USB transfers... well, it's not only about charging. Flip the finger @ Samsung, don't be shy! :)

There was a huge thread on XDA dedicated to this... but I can't find it. http://forums.androidcentral.com/samsung-galaxy-note-2/258969-note-2-picky-about-usb-cables.html will suffice, though, as it provides the minimum of info on this matter. It is for the Note 2, yeah, but it's the same case for the S4. And probably for the Note 3, I guess.

I'm using a cable that came from a Samsung Galaxy Gio / Young / S2 (it's the same cable, anyway) and it works perfectly. 5 other cables (including the stock one that came with my S4 two months ago) are acting up. :)
[Galaxy S 4 i9505 Android Development] BillGoss:
Duh! I should have realized that restoring the cache would, in fact, restore the cache and it's directories. :o

You don't need to change things to write the log to the backup file - I don't find it useful and the log in cache/recovery is all that's required.

Thanks for clearing all of this up. Which now means ... 5.18.2 is fine!

I love your responsiveness and continual improvement of a great product.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Thank you. I also appreciate your support and detailed bug reports.

By the way, I also had to browse the code to realize the cache restore was the cause. First, I thought cache was unmounted thus temp log lost.

I also do not find these logs useful, so will spare 2 lines of code for the twrp mode ;)
[Galaxy S 4 i9505 Android Development] gogua:
Hello Phil

I'm running you Last versión and backup dates are wrong. Also in 5.17.7

Anyway to fix it?

Thanks
[Galaxy S 4 i9505 Android Development] svenk:
Hello,

One question: I guess Philz Touch does not support device encryption (has been asked before but not answred as far as I see). I browsed the internet and found that there are some problems wrt/ device encryption, e.g. problems with updating firmware, or nandroid backups. There seems to be a version of TWRP rcovery (2.6.1.0) which seem to support encryption, but newer ones (2.6.1.1+) seem not to.

Has anybody tried to do a Nandroid backup on an encrypted device? Sources differ about if this is actually possible. Some state that encrypted partition will not be mounted at all in recovery and therefore not backed up. I guess that without decrypting or factory reset, a restore will not be possible either. Depends on which partitions are actually encrypted...
[Galaxy S 4 i9505 Android Development] Siwandroid:
Using the lastest recovery, got issue during full wipe...

It say:

unable to create data/media

cannot mount data

this kind of stuff :(
[Galaxy S 4 i9505 Android Development] svenk:
http://xdaforums.com/showpost.php?p=46242505&postcount=2065

Remark: For me, 01abyss was not locatd in /system/etc/init.d but in /res/misc.
[Galaxy S 4 i9505 Android Development] Mack_75:
Have a question too: does Screenshot possibility is implemented again?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] Pard0ned:
Did you format data and data/media?

I had that exact same issue months ago, Phil said he'd fixed it though. I haven't been up for trying as the only way to fix it was reflash stock rom in Odin along with the proper pit file. :(
[Galaxy S 4 i9505 Android Development] Phil3759:
Normally that was fixed as I now use kernel from google edition sources

I tried my self without issues

Many people on older or the error version 5.17.6/5.17.5 and they should update