yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] ibm_A3:
Is there anyway to flash this custom recovery from the samsung's original recovery?if got knox to 0x0 and dont want to flash anything with odin...
[Galaxy S 4 i9505 Android Development] CarlM34:
No
[Galaxy S 4 i9505 Android Development] Bejda:
Let's say there's way to root your device without triggering knox flag and then to use sgs4flasher app to install Philz recovery (.tar or extracted recovery.img) but you'll end up with knox 0x1 once done anyway so..

[MENTION=4129455]Formhault[/MENTION],

You deserve a good spanking and be forced to use your device in recovery mode only for two days lol

Philz doesn't come with Aroma fm bundled,to launch it directly from recovery via gesture or menu (yep,it exists already ;) ) you have to do a little thing which is precisely explained on Philz main thread.

I won't explain much, your first homework will be to go there and find out how-to by yourself :)
[Galaxy S 4 i9505 Android Development] Phil3759:
All this is explained in main thread that no one reads.

Browsing a bit the GUI Settings and trying to understand their use is also a minimum in my opinion.
[Galaxy S 4 i9505 Android Development] phileasx:
Just flashed to latest Philz touch 6.05.6 for I9505,

It's awesome, the touch recovery is easy to use and great UI. Thanks a lot for the development works!
[Galaxy S 4 i9505 Android Development] BillGoss:
It all works nicely. Thanks for the fix.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Formhault:
Given the "huge" ammount of time I spend in the recovery (just wiping / flashing in case there is something to flash), the ammount of knowledge I already have is enough. But finding out about new stuff is always welcomed :) .

Will do read on that and... sorry :/
[Galaxy S 4 i9505 Android Development] Phil3759:
np

I just think it is "dangerous" to use a recovery without knowing its functions

I do my best to make it safe on default settings, but an educated user is still the best protection against data loss ;)
[Galaxy S 4 i9505 Android Development] Phil3759:
Time bug fix: the situation

As you know, I never bothered to look at this as I was not affected. Seems like old kernel could let us force write the time on some circumstances, which is not the case of new cm-11.0

Just loading time_daemon reset my clock and I am now affected like all of you

I am not going to look how to make my clock working like before for now as I am not sure how safe it is, since disabled by Qualcom

Good news: I managed to fix the time bug in recovery using [MENTION=3084245]Chenglu[/MENTION] approach

Bad news:

if you reboot into ROM, you can get randomly a broken time issue. To fix it you have to enable data or wifi. The time broken will only happen if network/data/wifi are disabled. In the case of Whatsup, you'll have to kill it and restart it after time is in sync

If you do not use flight mode when rebooting from recovery to ROM, you are not concerned

a little worst bug: if, while in recovery, you reboot into recovery from its menu, time will be broken in recovery, no fix is possible. Then, if you enter ROM, you'll have, like above, to activate network, data or wifi

I see no other fix for affected people, all recoveries for all these new Qualcom devices are affected

Let me know what you prefer. At least, when entering recovery and doing backups, you could have a valid time

edit: only good news seem left now :D
[Galaxy S 4 i9505 Android Development] stillbeer:
only good news seem left now :D[/QUOTE]

Super !

Can't wait to try it !

Thanks man !
[Galaxy S 4 i9505 Android Development] miro_i:
I am unable to install the recovery. Any help please?

After installing with Odin, attempt to enter the recovery by volup + home + pwr does boot the phone but not enter in recovery.
[Galaxy S 4 i9505 Android Development] hanspampel:
It was posted sooo many times here in this thread. No need to hold home, only vol typo when you reboot. And the other thing was answered here too. Use the search here in this thread.
[Galaxy S 4 i9505 Android Development] supertomi:
Vol up, just after the vibration

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Android Development] hanspampel:
Whoops typo.:eek:
[Galaxy S 4 i9505 Android Development] Formhault:
I... don't think I fall in that category. I know the basic functions, of course...

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] gabi11:
Hey,

Just want to be sure before making a backup.

Currently I'm on latest Philz 6.0.7.1 with 4.2.2 rom (MGA) and old bootloader.

I want to make a backup before flashing 4.3.

Currently SElinux is enabled by default. Should I leave it that way? I read that when switching from 4.2.2 to 4.3 the restore process can cause problems.

I've searched the thread and also read the main one but still not sure about what I should do... :what:

Btw, one more question- I'm gonna backup to ext sd (FAT32) so chose tar.gz format and low compression. I read that it should speed things up...

Are those settings ok or there is something I should change?

Thanks a lot!
[Galaxy S 4 i9505 Android Development] Phil3759:
I advise to always keep selinux enabled for backups. That's why I set it on as default

If restore fails, just disable it

It doesn't alter the backup process, just adds extra info to it

On restore, you are free to restore with or without these extra selinux data
[Galaxy S 4 i9505 Android Development] Vessina:
Hey philz dont know how it happen.. But im on present now again.. Sometimes when I was doing a backup, saw that cache folder not was all empty.. 2 folders, one of them backup and recovery the other.. Last one have a lot of log files from recovery.. I killed those folders, booted on recovery and voilá.. I traveled on time again to 2013.. Can u confirm this for back in time bug Philz??
[Galaxy S 4 i9505 Android Development] Phil3759:
It is more complex than that

Nothing to do with cache, it is the time daemon

I am still fighting to find a universal fix

Not easy as what works on some devices causes issues on others

But I think I came with something good

Hold for a few minutes

I am pushing something for you
[Galaxy S 4 i9505 Android Development] BillGoss:
[MENTION=4666971]Phil3759[/MENTION]: I like all the work you've done to get to the latest version. The only think that is missing, from my perspective, is the backup speed we had in 5.18.

Here are times from two backups of the same ROM taken back-to-back (6.07 first to give it the advantage of a cooler phone):

6.07.1: 4:44 min

5.18.9: 3:11 min

Logs:

https://www.dropbox.com/s/5am69ti9ro9e6fy/last_log_6.07.1.txt

https://www.dropbox.com/s/a45q3b61fk33lfp/last_log_5.18.9.txt

If 6.07 had the same speed as 5.18 it would be perfect!

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Thank you a lot for your tests + logs

Sadly, the main difference between the two seems to be vold updates

I remember that on latest cm-10.2 builds, despite using the same stock kernel and exfat modules, speed was slower by that 30% reported and you found

Moving to cm-11.0 with same prebuilt kernel, then with cm-11.0 kernel did not solve it I see

So, what ever I can do (use stock kernel, stock exfat modules...) won't fix it

One of cm team members is working on a speedup engine when doing compression. Maybe once I implement his work in progress, it can speed up things

It is on my to look at list, so will do once I have time
[Galaxy S 4 i9505 Android Development] Phil3759:
v6.07.6 Final

Time Fix for affected users

This should be a one time fix

Now, if time is not fixed on first attempt, reboot to main ROM, sync in time, reboot into recovery and apply patch again

If you apply it twice, you'll break it. Redo above steps in that case

The first one with broken time that tests it, please give your feedback
[Galaxy S 4 i9505 Android Development] OzBoy1:
Tried it and worked first time. Daylight saving offset doesn't seem to work. Thanks Phil great work.
[Galaxy S 4 i9505 Android Development] Phil3759:
This is great

DST should be auto adjusted or you'll have to apply fix again.

Whenever your clock in recovery is out of sync, just reapply fix to sync with ROM
[Galaxy S 4 i9505 Android Development] Tassos_i:
This did not fix MY time bug, where recovery time goes forward an extra 3 seconds every day, since two months now.

On the other hand, it made random stick reappear in recovery boot.
[Galaxy S 4 i9505 Android Development] Phil3759:
For the 3 seconds, either Qualcomm can help or once we have data or wifi in recovery to sync time :D

When clock goes too much off, reapply the fix AND ALL THE STEPS

You must boot into ROM, sync time, reboot into recovery, and immediately apply fix

What actually happens is that if you wait 1 minute, your recovery time will be 1mn offset

I am not sure how the Qualcomm clock works and if recovery has its own and how time_daemon informs the chip

Time Daemon writes a time offset probably to 1970 that it applies on boot

Also, seems like there is a sort of memory in the chip for that offset. That's why when phone is off, the time is kept. However, time is not hardly written in chip

This is the only way I found to have a proper fix, persisting over reboots, no need to load the daemon on every start and surviving after reboot to recovery option from recovery

Now, hopefully it will satisfy most of you. If not, just give a detailed feedback of what's wrong
[Galaxy S 4 i9505 Android Development] iron@ss:
OK guys and girls... it's Christmas, so you can ridicule me all you like as I have developed a mind blank on this next question...

I have always used nothing higher than PhilZ 5.15.8 because every version after that will not allow me to back up to my extsdcard in ROM Manager. I get the message... "E: unknown volume for path [external_sd/clockworkmod/backup/2013-12-24-16.21.25"

I know I may be missing something blindingly obvious but I'll be blowed if I know what it is! I am home to Mr Thicky of Thicky Street, Thicky Town, on this one.

So, flame away or point me to the answer please. Anything, so long as I can use the most recent release of PhilZ via ROM Manager for a backup/restore to my extsdcard. :confused:
[Galaxy S 4 i9505 Android Development] cdzo72:
I haven't used ROM Manager in more than a year so I don't remember... but can you change the path to extSdCard instead of external_sd?
[Galaxy S 4 i9505 Android Development] hawkerpaul:
I never use rom manager neither.

I've never been certain what relationship the recovery has with the kernel since the s4. On the s2 they came hand in hand and recovery came with the kernel (eg. Siyah, philz, nimphetamine, neak etc). On the s4 they install separately but they are still obviously closely linked.

Extrrnal_sd is the problem butty.

I'm confused how it works on older versions of philz.

One your rom has booted it sees the external sd card as /storage/extSdCard, and not the older way how it was referenced (external_sd)

Is there an option in rom manager to point to the correct place?

If not and you're on a kernel that supports init.d (eg. Mkf talexop, not mke) then you could put a script in /system/etc/init.d to link /external_sd to the correct place. I can never remember which way around the ln command should be so you will have to Google it to be sure.

Eg.

ln -s /storage/extSdCard /external_sd

Or

ln -s /external_sd /storage/extSdCard

I'm sure there will be a much slicker solution off phil but this temporary fix may see you right the meantime.

Merry Christmas to you butty, and to you all

:D
[Galaxy S 4 i9505 Android Development] phileasx:
flashed to the time fix version 6.07.6, :)

seems my phone is display time correctly. just wondering besides backup time does this bug affect anything else?
[Galaxy S 4 i9505 Android Development] iron@ss:
Thanks for the replies cdzo72 and hawkerpaul.

ROM Manager is set, as always, to backup to... /storage/extSDCard/cloclworkmod/backup. There is no other option in ROM Manager, other than internal storage, to change the backup path. As mentioned, this works fine on all versions of PhilZ, up to and including v5.15.8. After that though, it does not recognise that path and I get the message in newer PhilZ releases... "E: unknown volume for path [external_sd/clockworkmod/backup/2013-12-24-16.21.25]".

I have tried changing the storage in PhilZ by going into recovery > Advanced > Storage set to /data/media and it only changes to Storage set to /data/media/0 which is when I get the above message when backing up. Incidentally, if I choose internal storage in ROM Manager, it backs up fine to the SDCard.
[Galaxy S 4 i9505 Android Development] bushgegner:
Why do I get errors using your recovery when trying to install latest MIUI?

Strange is that the normal CWM doenst´t show me the errors.

Errors are in build.prop and error message is error 7.

Can I fix this this by myself?
[Galaxy S 4 i9505 Android Development] Bejda:
I'm trying rom manager right now (got paid version, don't really know why..), when I go under settings and tick "use external storage" it switches from /mnt/shell/emulated/clockworkmod/.. to /storage/sdcard1/clockworkmod/.. ,i can't see any option to point path manually and if I launch a backup it just reboots to recovery and does nothing.

Anyway maybe you're Rom Manager app carry on old data's/settings,maybe a clear app's data or a fresh install will change the path shown for extsd?

And..sorry I would hate to get such "answer" but I have to ask :o What's the point using Rom Manager for backups when it works perfect with many options from recovery itself?

And personally I don't often use cwm backups but I once used this tool: http://xdaforums.com/showthread.php?t=2040507 that worked perfect also.

You probably have good reasons huh, just to know more ;)
[Galaxy S 4 i9505 Android Development] iron@ss:
Thanks for your reply Bejda!

I am using the Premium version of ROM Manager also. I wiped cache and data and uninstalled ROM Manager and re-installed it and I still only get the options of either... /mnt/shell/emulated/clockworkmod/. or /storage/extSDCard/cloclworkmod/backup and no /storage/sdcard1/clockworkmod/.

You are correct there is no option to change the path. However, using Root Explorer, I have discovered that I do not have /sdcard1/ under storage, only /emulated/, /extSDCard/ or /sdcard0/

I had OBackup installed at one time, as well as OnLine Nandroid, and it ceased to work on Android 4.3 and I'm guessing, on 4.4. I am also the author of the Rooting and PhilZ Dummies Guides on Android forums and ROM Manager keeps it simple for noobs to start with. However, because of this issue that I have experienced since v5.15.8, this is the latest version I am linking to for Android 4.2, 4.3 and 4.4.
[Galaxy S 4 i9505 Android Development] Bejda:
Oh,i forgot to precise i'm on CM based rom,that makes the difference between us for external storage path sorry.
[Galaxy S 4 i9505 Android Development] iron@ss:
No problem. Thanks for replying. Basically, what it boils down to, for me, is that ROM Manager works across Android 4.2.2, 4.3 and 4.4, so long as I use PhilZ v5.18.5. This makes it easier for my Dummies Guides, mentioned previously. As I also mentioned, it could just be me at home to Mr Thicky and I'm missing something blindingly obvious that would work on all 3 Android platforms with ROM Manager. :D
[Galaxy S 4 i9505 Android Development] Bejda:
I have a touchwiz rom as primary rom,was thinking about this:

PhilZ Touch 5 Quick Guide

How to select your .android_secure path

In Custom Backup and Restore operations, you can select the target/source for android.secure or disable it

In stock backup/restore operations, include those started with ROM Manager, you can also force a target/source for .android_secure

basically, recovery will check first external storage for a .android_secure folder. If it doesn't find it, it will look in internal storage

If you want for example .android_secure to be in internal sd, just delete .android_secure folder from external sd and ensure there is a .android_secure folder in internal sd

for external sd, just ensure there is a .android_secure folder in it. It will be chosen what ever is the internal sd state

I have .android_secure folder on sdext but same story:

http://pastebin.com/qbCTZkEn

I see some reports stating it worked for the last time with cwm 6.0.3.6 but not since then..
[Galaxy S 4 i9505 Android Development] Phil3759:
Happy Christmas to all

Any news about fix time feature for people with bad time?
[Galaxy S 4 i9505 Android Development] Bejda:
No problem on my side, time has always been correct..

Wish you all,with a little advance I know, a happy new year 1971!

;)
[Galaxy S 4 i9505 Android Development] joiN85:
Abyss kernel solve time problem. It work for me! ;)

http://xdaforums.com/showpost.php?p=46249230&postcount=18
[Galaxy S 4 i9505 Android Development] Badwater55:
How shall the time fix be visible?

Upper right corner shall display the correct time or do I need to make a backup and check the time tag of the backup in the file system?

I am on 4.2.2 MGA (old bootloader) applied time fix several times, always boot into ROM in between ; upper right corner still shows worse time :(
[Galaxy S 4 i9505 Android Development] Phil3759:
Really wired, seems it works for some and not for others
[Galaxy S 4 i9505 Android Development] Seth25:
I see what you did there... ;)

Anyway, about the time issue, I don't have it, never had, but I don't understand what the problem is. Will the backups not work if the time is not correct?

MERRY CHRISTMAS everyone!!!
[Galaxy S 4 i9505 Android Development] Sir.Nry:
The backup will still work, it's just "annoying" ^^

My time is also still bugged after applying the fix severales times.. don't know why
[Galaxy S 4 i9505 Android Development] Mkhant30:
My backup time is correct after applying Abyss kernel. Thx for your recovery.
[Galaxy S 4 i9505 Android Development] phil.o:
Wrong thread...

°°° tapatalked °°°
[Galaxy S 4 i9505 Android Development] buedi:
Same situation and issue for me since many versions.

Anyways, thanks for the support phil.
[Galaxy S 4 i9505 Android Development] freakerload:
I want to use fix permissions cant find it… No more in the recovery?
[Galaxy S 4 i9505 Android Development] phil.o:
Exactly. It was removed few versions ago.

°°° tapatalked °°°
[Galaxy S 4 i9505 Android Development] 0kti:
+1

Send from my Galaxy S4 powered by KitKat
[Galaxy S 4 i9505 Android Development] zicovsky:
Not working for me, Phil.

1. Tried going into rom to sync and applying fix several times (not consecutively, always went back to rom to re-sync) and the time at upper right is 1 hour back (with DST ticked).

2. Adding time offset takes time back instead of adding it forward.

3. Made a nandroid and still shows 1970 (Is there a way to easily see the full date without doing a nandroid? I must be blind)

Happy 1971, folks.
[Galaxy S 4 i9505 Android Development] phileasx:
Hi Philz,

Today I encounter once recovery bootup hang, had to long press power button to reboot. 2nd try was able to bootup. on ver6.07.6

Not sure if this could be a bug. Is there anything need to set before flash recovery to newer version?

Thanks a lot
[Galaxy S 4 i9505 Android Development] HaTrED_:
+1

It happens to me randomly...

Sent from my S4, another Galaxy!
[Galaxy S 4 i9505 Android Development] theluke79:
Rooted i9505 Jamal 2367 v11

Hi,

I am on Philz Tpuch 6.0.4.5, I want to updated to the lastest version, BUT no matter what I do, the Recovery is just NOT updating, it keeps the actual version.

I get NO error codes whatsoever from the device.

:crying:

Thanks!
[Galaxy S 4 i9505 Android Development] hanspampel:
6.0.4.5 is the version of CMW not the versionof PhilZ. Check under PhilZ Settings-->About. You see now the build version 6.07.6 or whatever is on your device.
[Galaxy S 4 i9505 Android Development] GlossGhost:
Is 6.07.6 stable? You guys seem to be reporting strange issues.
[Galaxy S 4 i9505 Android Development] gerardo87:
+1 me too :(

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Android Development] hawkerpaul:
I've experienced random boot hangs to get into recovery too, but it only seems to happen when entering recovery from the power menu of the rom (dejembey+wanam xposed). I've also noticed it seems to take longer to get into the recovery menus the time it does work. I first noticed this since the first v6.

I've never seen it hang when entering recovery via a power down and power+vol-up.
[Galaxy S 4 i9505 Android Development] HaTrED_:
I've that feeling to...

Sent from my S4, another Galaxy!
[Galaxy S 4 i9505 Android Development] phileasx:
Thanks for the sharing, I remember the time it hang was reboot recovery from the 4way power menu too.

Cannot be sure because I seldom use power button combination.. it did take a while to bootup the recovery menu tho.
[Galaxy S 4 i9505 Android Development] yhrn:
Tired it several times but I won't work for me, sorry. Happy new year, guys and girls!
[Galaxy S 4 i9505 Android Development] Riskytwin:
+1

Not working for me either

Risky's my name
[Galaxy S 4 i9505 Android Development] nikerossxp:
on version above 6.00.8 can't flash latest PAC rom - different device identity.
[Galaxy S 4 i9505 Android Development] Phil3759:
This is built on cm-11

If ROM comes with older update-binary, you cannot flash it. Author has to fix his rom package for that

Try also latest 6.07.9
[Galaxy S 4 i9505 Android Development] nikerossxp:
ok, thanks.
[Galaxy S 4 i9505 Android Development] kuljit55:
Which version of PhilZ recovery is most stable for 4.2.2 stock sammy roms that are knox free and on old bootloader? Thanks
[Galaxy S 4 i9505 Android Development] Formhault:
I am still on SlimBean, and will not switch to 4.4 ROMs just yet. So... Which is the latest recovery version I can use without losing the ability to flash files that have the obsolete (so to say) update binary? 5.x.x... something... perhaps?

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] Phil3759:
It is in changelog

I think 6.03.x started on cm11. I do not have my logs right now for exact build
[Galaxy S 4 i9505 Android Development] BrunoSlivar:
How to restore just 'data' from my backup?
[Galaxy S 4 i9505 Android Development] BillGoss:
Use custom restore and untick all the boxes except data.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
[MENTION=2911853]BillGoss[/MENTION]

Sadly, the performance control commit just merged into official cwm did not bring what I was hoping for

Actually, by using 4 cores it is causing the phone to get very hot and my backup time for 3.5 Gb increased from 13 to 28 mn on exfat and from 10 to 23 mn on internal storage

I really have no big clue how to get back those 30% time enhancement

Can you do again a test of speed like you previously did, but this time disabling all progress bars and size stats?

Maybe they changed something at the graphics level which can slow down things
[Galaxy S 4 i9505 Android Development] BrunoSlivar:
I do that and i got all rom not just data. I will try. I just wait for v19 from omega
[Galaxy S 4 i9505 Android Development] gabi11:
Hey,

I've searched but didn't find a clear answer.

What are the best settings for fastest backup in those parameters:

1. Compression- some kind of an ideal mix between size and speed.

2. External/internal- I have a 32 GB Samsung class 10 fat 32.

Roughly, what are the differences between backing up to internal or external?

Thanks!
[Galaxy S 4 i9505 Android Development] Phil3759:
I advise low

The remaining is up to you
[Galaxy S 4 i9505 Android Development] BillGoss:
I'm using scripts for both CWM (extendedcommand) and TWRP (ORS) so I ran the tests for both. I have no progress or stats shown and the backups go to the external sdcard

6.07.6:

1. CWM: 05:41 mn

2. TWRP: 05:37 mn

5.18.9:

3. CWM: 03:47 mn

4. TWRP: 03:34 mn

Logs: https://www.dropbox.com/s/6wxwghphajlqkm2/backup_logs.zip

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Formhault:
Indeed :D . Just checked the main thread.

So yeah, guess I'll flash 6.02.1 and stick to it until I move from SlimBean :D

EDIT : Whoops, 6.02.x is nowhere to be found.

EDIT2: By looking at the changelogs, there's nothing I'd be missing out on, so I can just as well flash 6.01.7.