yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, then not my fault

As I said a few posts above, I see, and CF is saying it more and more, that Samsung is choosing the way of completely locking things

If they decide to release locked bootloaders for international users, we're locked until someone unlocks this :p (see how many lock in my sentence!)

I think I read something about new ROMs, start of MH8 have semi-locked bootloaders and new ROM checks for system modifications. As soon as you modify kernel, recovery or some system files, they cut some functions

Just like parents punish their children to stop watching DORA

I won't look at these, it's not my competence and I have no time for such projects

I work on recovery, others will look at these new locking things probably
[Galaxy S 4 i9505 Android Development] diddsen:
what the hell makes samsung with us?

This is just unreal :(

very unhappy things... but you´r right, not your fault ;) ... very annoying because I always used your philz
[Galaxy S 4 i9505 Android Development] donalgodon:
I feel like an idiot because I vowed after the S3 to never buy another Samdung device. Fool me twice, shame on me.

Nexus 5 where are you?
[Galaxy S 4 i9505 Android Development] BillGoss:
Warning: OT post!

I bought the S4 because it has an external SD card, a non-Exynos CPU, brilliant screen and lots of memory.

And I run CM 10.2 on it. I think this is a far better proposition than a Nexus.

Sent from my GT-I9505 now Free
[Galaxy S 4 i9505 Android Development] donalgodon:
Yeah, I guess it's a bit off topic, but my point is that I hope PhilZ will be offered on the Nexus or the Oppo N1, because this Knox crap is the last straw for me, and I don't even have a Knox bootloader. It's just the principle of the whole thing, because it hampers development.
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, seems there's a little hope

I figured out a way to keep vold while ensure we mount exfat volumes with kernel module on devices compiled with a kernel supporting this

Now, I need someone to test these on version 5.15.8 (last stable) + EXFAT sdcard, to see if they can confirm my findings:

In my own tests with 3.7 Gb, Methods 1 (11 mn) and 2 (8 mn) are very fast, and Method 1 is even faster despite the enabled compression

Methods 3 and 4 kill the performance completely adding up to 25 mn time

Seems like the key factor is the default cwm logging mechanism more than my stat commands for size

Or, it is the screen refresh killing performances

I will dig into these when someone can confirm my findings

Many thanks
[Galaxy S 4 i9505 Android Development] dave_p_b:
@Phil3759

Tested with 32GB exFat, backed up 3.7GB.

Test 1) 7.20 Min

Test 2) 5.30 Min

Test 3) 41.06 Min

Test 4) 32.46 Min
[Galaxy S 4 i9505 Android Development] Phil3759:
You're great

So quickly

Thank you a lot

It could be we have something to fix

It corroborates my results, except compression is a little slower with you, that we'll see later. Probably second core turned off in recovery
[Galaxy S 4 i9505 Android Development] Formhault:
Hey [MENTION=4666971]Phil3759[/MENTION]

Totally unrelated to recovery question here... but perhaps you can provide a reliable answer. I wanna format my 16GB microSD (class 10) to exFAT. What allocation size unit should I be using?
[Galaxy S 4 i9505 Android Development] Phil3759:
Format in recobery under mounts and storage. I added the function for this. It will set default for your card size. Under windows, set default
[Galaxy S 4 i9505 Android Development] charlle:
test results

Hi,

first, i would like to thank Phil3759 for his GREAT work.

i did a partial test, only for test 1 & 2.

Tested with 32GB exFat (Samsung pro), Abyss Kernel 1.6.1. backed up 3.7GB.

test 1 - 6:15 min - no charger

test 2 - 10:19 min - with charger

so it seems a lot faster than the "old" methods...

a question about this backup with no MD5 checksum, will it be OK to restore in other recoveries as well? is there any risk not to perform this checksum?

Thanks
[Galaxy S 4 i9505 Android Development] dave_p_b:
Out of interest, Initially, I started doing the tests in Philz 5.15.0 (by mistake!). I thought I would finished the tests off. Same parameters as before, 3.7GB.

Test 1) 6.44 Min

Test 2) 5.28 Min

Test 3) 29.56 Min

Test 4) 28.57 Min

Hope this is helpful. :)

Note: I also notice the backups take considerably longer if the phone is plugged into a charger. This has happened several times. I think this has been mentioned somewhere before.
[Galaxy S 4 i9505 Android Development] sachs:
.... what advantage in exFAT format? thank you
[Galaxy S 4 i9505 Android Development] DroidRevenge:
googling around...

http://en.wikipedia.org/wiki/ExFAT
[Galaxy S 4 i9505 Android Development] Phil3759:
Thank you all

Seems the stat for size is not the main issue but either stock CWM logging or screen refresh

I will need to make some tests to see where's the issue, but hopefully we get finally faster backups

If you add md5, it will be a bit longer obviously since it has to read through the 3.7 Gb backup again to complete md5 hash. However, it would take much less than total backup time since read speeds are much faster. With md5, we should achieve less than 10 mn for this 3.7 Gb

The phone won't be faster though, as it seems a hardware issue also

About md5, google for the use of it. Stock CWM cannot restore without md5 hash. However, PhilZ Touch lets you build the md5 later if you need them. Look a bit into menus
[Galaxy S 4 i9505 Android Development] neophyte1983:
Not sure if i am right but i maybe found out that booting first time in cwm will make 0x1 knox Warranty status.

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] charlle:
Thanks. will look into this...
[Galaxy S 4 i9505 Android Development] tata_brada:
If you have new bootloader and knox s**t it is very likely and reported from some users.
[Galaxy S 4 i9505 Android Development] diddsen:
by me philz also does the annoying thing with knox 0x1 :(
[Galaxy S 4 i9505 Android Development] mitky82:
Wow.... i can't restore my backup now :( stuck on data and from 1 hour noting move on screen with latest version 5.15.8... i try again and same thing... any other way to wake up mu phone with that backup?!
[Galaxy S 4 i9505 Android Development] silentscreamer:
:rolleyes: obviously you are ... 'Knoxed out' by a locked bootloader and Samsung Knox/SaFe

https://www.samsungknox.com/overview/technical-details

... just read, then kinda party, if you feel like :cool:

:mad: ...and no, at time there is NO way back :(
[Galaxy S 4 i9505 Android Development] mitky82:
If that is for me i know for knox, but that not was the problem. I restore backup yesterday and no problem many times, after 4.3 with new bootloader. But i dont remember what version was using because i use sgs4 flasher and recovery was on sdcard, now i wipe data and they gone from them and flash newest. Maybe problem is with new versions, ill try now with some 5.10 they are too many and... And my backup is from DMH8 version

EDIT: yes ! newest version was problem. Now i flash 5.10.8 and all is fine, im on nex step after data restoring... :) phone boot up and all is fine now. Ill use only 5.10 versions from now.
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.17.1 stable - CWM 6.0.4.0

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

Change log is huge, will post later

I largely tested, include backup efs, delete my efs partition and restore it. Some sweating here, first trial on this S4 :D

I fixed what ever I can think about, include format to ext2 and ext4, Aroma to see USB OTG storage and exfat volumes on the new cm-10.2 vold, backup restore, size detection of all partitions...

Backup speed is unchanged for now, same as 5.16.x cm-10.1 builds. I will fix the logging thing slowing down exfat backups on a next update
[Galaxy S 4 i9505 Android Development] nfribeiro:
Can anyone please tell me what is the best way to fix the problem of the wrong time/date on the revovery?

I read that we should remove the battery for 12 hours but others say it won't work.

Thanks in advance.

Enviado do meu GT-I9505 utilizando Tapatalk 4
[Galaxy S 4 i9505 Android Development] donalgodon:
There's nothing simple on your end that can be done to make ROM Manager use the new cm-10.2 vold so that backups mount external SD properly, is there?

I wrote the dev about it, but got no response. I use this feature often, as it makes backups and restores very quick and easy.
[Galaxy S 4 i9505 Android Development] nightranger73:
If you want something simple think you should try onandroid script with orange backup. You can make nandroid backups while you use your phone without need to reboot in recovery.

Rom manager has always had lot of problems.

One of the first backup tool for android but not the best

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Android Development] shoey63:
If you want sweating, you should try restoring TA (EFS equivalent) partition on Xperia Z - anything goes wrong and the device HARDBRICKS:eek:
[Galaxy S 4 i9505 Android Development] cdzo72:
Been on vacation since last Friday so I just skimmed through the thread and saw the new 5.17.1... well I downloaded it and flashed it... rebooted recovery and lo and behold... I saw that my time was correct. Mind you that I've tried ALL the trucks mentioned in the thread and nothing has helped... it was 6:29 pm here and recovery said 0:29 with no timezone change... set it to -6 for Central America and when it said 18:29 I was so happy I almost cried....

Thank you Phil!
[Galaxy S 4 i9505 Android Development] RATOz:
v5.17.1 working with Knox bootloader (MI8).

:good:
[Galaxy S 4 i9505 Android Development] Phil3759:
Provide a log at least on failure to flash. Maybe it is just a /data/media/0 thing you need to set

Look in Advanced menu. CM doesn't use /data/media/0 in recovery. PhilZ Touch offers both options and defaults to /data/media/0 so that you can see your internal storage files when mounting with MTP in main ROM
[Galaxy S 4 i9505 Android Development] hailmary:
U serious?
[Galaxy S 4 i9505 Android Development] neophyte1983:
Installed new update and still it is 1970 when cwm makes a logfile. Clock incorrect date incorrect :(

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] donalgodon:
Not sure if this log will help, but I already have data set to media, not media/0 because CyanogenMod updater works fine with your recovery that way.
[Galaxy S 4 i9505 Android Development] sarbe:
Which version did you make the backup with? Try an earlier version. Have you renamed the backup?
[Galaxy S 4 i9505 Android Development] Phil3759:
I do not see what kind of log is this

If ROM Manager is the issue, you have too provide a log when you install a file through ROM Manager

The log you provided is through manual install

And, in the case of that log, it is your ROM installer or Aroma Installer they are using
[Galaxy S 4 i9505 Android Development] donalgodon:
I tried to use Aroma to get the ROM Manager log file but it froze. On reboot, the temp file is gone. If I can get it to work, I will post the log here. Thanks for your help.

Edit:

Arrrgh. Can't get the log. I tried copying it in Aroma to the external SD, but when I reboot, it's not there.

Any suggestions?

Here's what the screen says after I try to use ROM Manager with 5.17.1:
[Galaxy S 4 i9505 Android Development] Nicotin3:
5.17.1 is best one so far.

On ext 64GB exfat card .

11:12 min

4009Mb

Compression 29%

Thank you.
[Galaxy S 4 i9505 Android Development] gabrielrf:
anyone know if i flash this recovery on new galaxy s4 bootloader i gonna void the know to 0x1 ?
[Galaxy S 4 i9505 Android Development] neophyte1983:
Yes you do 0x1.

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] BoBCatRoM:
install kernel abyss that reactivates writing RTC (Real Time Clock)

Inviato dal mio SM-N9005 con Tapatalk 2
[Galaxy S 4 i9505 Android Development] lahceneamine:
Will I tautomaticaly reset the RTC ?

And please since I use AdamKernel, can I just flash Abyss, reboot only the recovery and flash Adam again ?
[Galaxy S 4 i9505 Android Development] BoBCatRoM:
Install abyss 2 reboot, check time and data...reboot and install other kernel.... I have done so.....works :)

Inviato dal mio GT-I9505 con Tapatalk 2
[Galaxy S 4 i9505 Android Development] Saleen NS:
Working for me too.

Thanks mate.

Problem is solved :)

Wysłane z mojego GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Got my hands on something nice:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/3788de16121801f002f9a5264f1ff635b88a3c00

Seems like some changes I had done to display backup stats caused a huge hammering that i9505 couldn't support

Probably a mix between display buffering/refresh and writing operations

Next update will get you amazing speeds (like when you hide all progress) while having all display options enabled

And, the most important, phone is incredibly less hot after a backup
[Galaxy S 4 i9505 Android Development] lahceneamine:
Great news then :fingers-crossed:
[Galaxy S 4 i9505 Android Development] Tamsy:
Worked for me too (on GOLDENEYE 8.0 with PhilZ Touch 5.17.1):

- Booted into CWM.

- Installed latest Abyss Kernel.

- Rebooted ROM.

- Rebooted back into CWM. It now shows the correct time and date.

- Rebooted back into ROM and deleted 01abyss file in /system/etc/init.d.

- Rebooted back into CWM and installed ADAM kernel 1.6 KNOX FREE version.

All good now.

Thanks for the hot tip, BoBCatRoM!
[Galaxy S 4 i9505 Android Development] aeroman:
1+

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] z-vet:
I don't see init.d in /system/etc, what should I do?
[Galaxy S 4 i9505 Android Development] hanspampel:
Then you didnt installed the abyss kernel.
[Galaxy S 4 i9505 Android Development] Tamsy:
angelom on his website for the Abyss Kernel recommends to delete the file "01abyss" which gets installed into the directory "/system/etc/init.d" when moving away from Abyss Kernel to another Kernel.

You need "Root Explorer" or some other file manager (with root access) to see/delete that file.
[Galaxy S 4 i9505 Android Development] z-vet:
Strange: found this file in /res/misc. Can't delete it though, I have root access and filesystem is mounted RW, but Total Commander fails each time. Any thoughts?
[Galaxy S 4 i9505 Android Development] shoey63:
Try deleting in recovery/aroma file manager
[Galaxy S 4 i9505 Android Development] z-vet:
This time it worked, thanks.
[Galaxy S 4 i9505 Android Development] marcel112:
Posted in severell recovery thread: when i reboot the phone... Lately i cant het it to boot full without power plugged in. Keeps rebooting , on Sammy text or bootimage or....tried full battery. Different battery... Cwm recovery... Twrp recovery...anyone van help me? Will philz solve?
[Galaxy S 4 i9505 Android Development] Tanis64:
This could be the battery or the SIM Card.

Even if you tried different battery. There are a couple of threads in the German Android Forums about defective batteries. I self have had one, with the defective battery I can boot till I have to enter the SIM pin. After that the phones power off. With charger plugged in this didn't happen. So I take a closer look to my battery, it was slightly blown up, this is a clear sign for damage on a lithium ion battery. I think Samsung is aware of this problem after a call at the service center they send me a new battery, and everything is perfect again.

If the battery looks normal, have you tried a different SIM or booting without SIM card ?

Regards
[Galaxy S 4 i9505 Android Development] sachs:
+1...not found
[Galaxy S 4 i9505 Android Development] colang:
worked 100 % here Thank you
[Galaxy S 4 i9505 Android Development] marcel112:
Thanks for your reply..will look closer at your tips and try...thumps

Edit: tried 3rd party battery...now no problems booting.. But cant see the fail in original battery. Can i just call or ask Samsung for replacement or...?
[Galaxy S 4 i9505 Android Development] Mack_75:
Slide left for Screenshot

Maybe someone could helt me. I tried to make a screenshot in CWM but cannot realy do ("screen capture failed"). There is a folder called "screen_shots" under clockworkmod-folder on my internal and external sd card. Any idea what settings i have to choose to get the possibility?
[Galaxy S 4 i9505 Android Development] BoBCatRoM:
I forgot.... if you do not use Abyss :D

01abyss deleted files in / system / etc / init.d.

so is perfect ...:good:

Thx Tamsy
[Galaxy S 4 i9505 Android Development] Riskytwin:
Great job Phil!

Thank you for this incredible tool!

Last night I made the 1st nandroid backup on my brand new S4 and everything went fine excepte the name of the backup folder:

1970-01-04.04.10.28_JDQ39.I9505XXUDMH8

Why?
[Galaxy S 4 i9505 Android Development] aeroman:
Hey guys is this last update for cm or tw Roms?

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] CarlM34:
Worked on my TW ROM (leaked 4.3)
[Galaxy S 4 i9505 Android Development] aeroman:
Here too on my Tw Rom 4.2.2. :D

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] ElRongMcBong:
Hey Phil...

It's that normal:

If i want format /preload, i gets this error...

"

E: format_volume: make_ext4f4fs failed on /dev/block/mmcblk0p27

Error formatting /preload!

"?
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.17.5 CWM - 6.0.4.3 (F1 Nitro speed fix) :D

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

The final stable is here

The menus are changed because of the new vold code in cm-10.2: you can hotplug USB key

Now, backup of 3.5 Gb to internal storage, all stat options enabled, takes around 3 mn (same speed as stock CWM)

Backup to exfat external storage of same data is extremely fast too, around 10mn and maybe less if you have a faster card than my old one

Do not forget to enable all progress stats again in Misc Nandrodi Settings. I tested for you: speed change is about a few seconds only now with or without them

Big thanks to [MENTION=3562083]wanam[/MENTION] for providing latest kernel to fit this

Also, [MENTION=2661222]xiaolu[/MENTION] for his vold changes to support exfat through ko modules
[Galaxy S 4 i9505 Android Development] donalgodon:
[MENTION=4666971]Phil3759[/MENTION]

Still trying to get the log to you.

I used Aroma to find the log successfully, and it's where the above says it would be, but when I copy/save it to external SD, it's gone on reboot. Can you please tell me how to get it saved properly so I can send it to you? :confused:
[Galaxy S 4 i9505 Android Development] Phil3759:
check your /data/media things

And, more than a log, I need description of your issue?
[Galaxy S 4 i9505 Android Development] donalgodon:
It's that same issue I described before where using ROM Manager fails and says:

I'm using the data/media option, not data/media/0

Your recovery flashes fine, works with CM Updater, etc., but backing up with ROM Manager gives me this error when I select "Backup current ROM"

It simply reboots into recovery, then fails as noted above.

5.15.8 works perfectly. No errors.

I found the recovery log file. Here's what it contains:
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, from your previous log, it shows ROM Manager uses external_sd, old cm-10.1 path

It will probably update once when koush does. That's not a recovery issue
[Galaxy S 4 i9505 Android Development] donalgodon:
So, there's no way around it until Koush updates ROM Manager?

What should I ask him to fix to make this work, just to be specific?

Just saw that he's already updated CWM to 6.0.4.4, btw.
[Galaxy S 4 i9505 Android Development] aeroman:
Your Nitro fix works fine here with my 64GB exFat card. :good:

Tested with All progress stats on, (no comp.) backup of 3850mb, result was 8.24 min, before was ca. 58-85min.

Good work mate. :)

Regards

Gesendet von meinem GT-I9505 mit Tapatalk 4
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.17.6

Download

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

Do not forget to say thank you to [MENTION=3562083]wanam[/MENTION] for providing the kernel

And, also, [MENTION=395758]ausdim[/MENTION], for what you got till now thanks to his kernels. Without him, it wouldn't have been possible to use all this recovery features till now

Taking some coding pause now, for real

[MENTION=2278462]donalgodon[/MENTION]: ask him to fix ROM Manager to support cm-10.2 recoveries external storage path. He will know very well what is it

I can easily fix it on my side, like I do for gooManager. However, I see no use of it, since Koush will fix his app once for sure
[Galaxy S 4 i9505 Android Development] donalgodon:
Sorry for being dumb, but does that mean that it should work okay in the meantime if I backup to internal instead of external?

Edit: Answered my own question by trying. Yes, it does. :silly:

Thanks for your help and all your hard work. This is the BEST recovery there is. Period.
[Galaxy S 4 i9505 Android Development] Vihru:
so.. cm 10.2 not booting with this newest Philz Touch.. what i did wrong?
[Galaxy S 4 i9505 Android Development] Tanis64:
With 15.17.6:

CWM Backup from Recovery includes Preloads

All Stats activated ín Nandroid Settings

Compression 0,00%

5.854.609.761 bytes in

16:47 min.

Thanks for that great release!

Regards
[Galaxy S 4 i9505 Android Development] Mack_75:
trying to wipe dalvik = shutdown my phone, wipe cache is ok, backup to external is possible (v5.17.6)
[Galaxy S 4 i9505 Android Development] lzk123:
On 5.17.6. After backup to external sd, I tried to wipe cache and this error appeared.

Formatting /cache...
Cache wipe complete.
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
press any key to continue

After that I tap the screen and it brings me to the menu. But the recovery hangs. Tapping the screen produces vibration, tapping the bottom navbar produces vibration too and highlights the respective buttons pressed. But the menu portion hangs.

Here's the log:
[Galaxy S 4 i9505 Android Development] echohack:
I got the same

Formatting /cache...

Cache wipe complete.

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

press any key to continue

So I went back to 5.15.8 and I'm getting same message.
[Galaxy S 4 i9505 Android Development] aeroman:
same Error what i have, after wipe Cache and try wipe Dalvik, by me the unit shuts off.

I'm for first back to v5.15.8. Maybe that tlast Updates only for CM or there is something wrong with Mountpoints?!

Regards

---------- Post added at 12:54 PM ---------- Previous post was at 12:49 PM ----------

you must after flash again v5.15.8 reboot your Recovery, and then wipe cache & Dalvik!

After this runs all again fine by me. ;)
[Galaxy S 4 i9505 Android Development] edwardtobia:
Im on CM10.2.

I updated to 5.17.6 and then installed todays nightly via OTA (09/10/2013) and now my i9505 will not boot, it gets stuck at the galaxy boot screen.

I have tried to re-enter recovery to revert my recovery version and every time I try to boot into recovery it goes straight to installing the CM10.2 update and I cannot cancel it, and then reboots and gets stuck again, I cannot get into the recovery menu to flash an older recovery version.

What can I do to fix this? :/ is there any way to fix this without ODIN as I am not home until later on tonight :(
[Galaxy S 4 i9505 Android Development] Mack_75:
perfect, no longer errors, thanks
[Galaxy S 4 i9505 Android Development] Phil3759:
Sounds bad

Seems like the corruption of ext4 partitions caused by [MENTION=3562083]wanam[/MENTION] kernel.

[MENTION=395758]ausdim[/MENTION] kernel being from google edition, it was the way I fixed the issue a couple months ago.

Please stop using current version 5.17.6

I will wait for a new kernel. Sadly, previous [MENTION=395758]ausdim[/MENTION] was perfect but it is now too big for cm-10.2 builds

We'll have to wait for a kernel