yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] boostermbkking:
i have flashed the 6.01.7 recovery and i do a backup, when i restore the backup, there are an error to restore data and my file are lost, why?
[Galaxy S 4 i9505 Android Development] Formhault:
Thought you managed to get it fixed :D by replacing, of course.

Sent from hyperspace

---------- Post added at 10:49 AM ---------- Previous post was at 10:48 AM ----------

Let's hope the consumer market and enterprise market remain SEPARATED :)

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] shoey63:
For the second replacement I asked for a credit to go towards Xperia Z. I don't regret it. No Knox and hard to brick. Just have to send Sony your IMEI to get bootloader unlock code, which "may" void warranty. Still better than Knox BS. Pretty easy to get everything back to pure unlocked stock.

The best thing is, despite not having a recovery mode, devs have worked out a way to load recovery into RAM on boot, and Philz recovery works perfectly on it:)
[Galaxy S 4 i9505 Android Development] Formhault:
What? No recovery? Lol.

Well, I wanted to get the Z1, too, but I ended up buying the S4. Should have bought the One better. Oh well, enough off-topic for that. I think we all learned our lessons and we'll be seeing each other next year, in the HTC One Two development community or something :silly:
[Galaxy S 4 i9505 Android Development] Phil3759:
I like sammy phones a lot

However, another reason for the Nexus series is the long support they get. Look at i9000, n7000, i9100, n7100, i9300...

They are all dead from updates probably while the Nexus S will fly with Kitkat
[Galaxy S 4 i9505 Android Development] shoey63:
True, my wife just got KitKat OTA on her Nexus 4:) (still unrooted - won't let me touch it:p)
[Galaxy S 4 i9505 Android Development] D4RKL04RD:
Hahahahaha good one xd
[Galaxy S 4 i9505 Android Development] Broli@666:
Can You tell me how or Where to find something?

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Android Development] Phil3759:
well, you just plug your OTA drive

And some thing should happen
[Galaxy S 4 i9505 Android Development] ph3n0mII:
+1, just plug it in, wait 2-3 seconds (depending on your usb drive) and it will be auto-mounted and available in all relevant menu's as a storage option to flash from/backup to, even has native NTFS support :)

I've found with USB OTG adapters, it can be better to plug the usb drive into the adapter before plugging in the adapter to the device, otherwise theres a small chance of mount failure, random disconnection or read/write failure/corruption.
[Galaxy S 4 i9505 Android Development] Formhault:
Now that... encourages me to actually use the NANDROID function again :) . So I can store those 2+ gigs per backup elsewhere...

But this whole SELinux thing frightens me. It's gotta be disabled, enabled etc...

I'm on SlimBean (4.3.1) right now, so... just to triple/quadruple sure... can I enable wherever that SELinux backup switch is and leave it like that, just in case? Regarless wether there IS meaningful SELinux data to backup or not...?
[Galaxy S 4 i9505 Android Development] Phil3759:
Soon all this will be sorted, when native selinux support is added into busybox

For now, on all my new recoveries, it is enabled by default

I strongly advise to leave it enabled
[Galaxy S 4 i9505 Android Development] ph3n0mII:
It's enabled by default in latest philz builds and you can safely leave it on, or enable it if it's not.

If recovery fails to find relevant SElinux content during backup, it will simply skip it and go on with the next bit.

I always leave it on just for the rare times when i fiddle with TW roms.

I'm on slim 4.3.1 too, never had a bad backup/restore.
[Galaxy S 4 i9505 Android Development] Formhault:
Great! I don't even know where inside the advanced settings of the recovery it is, so I won't even know how to disable it :silly: .

---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------

That's what I wanted to hear!

I'm about to fiddle with TW ROMs soon enough (soon = since early November :silly: ), so when I do, I wanna make sure two of my games DON'T lose data :rolleyes: .
[Galaxy S 4 i9505 Android Development] ranger4740:
I restored a previous backup backed up with 5.x version of philz I believe SElinux would have been disabled and restored using 6.x version with SElinux enabled and after restarting phone I had no IMEI and crapped my pants because I thought my phone stuffed up :eek: :eek::eek::eek:

I did notice an error message during restore about SELINUX but didn't think much about it.

I didn't even look anywhere for solution

I fixed it simply by doing a factory reset and restore with SElinux disabled much to my relief it fixed my unknown I ME I issue...
[Galaxy S 4 i9505 Android Development] ph3n0mII:
Ah that would have been scary. Now that ur on ver 6.x , maybe just enable it and make a fresh backup :)
[Galaxy S 4 i9505 Android Development] Formhault:
So, you restored a backup with SELinux enabled... and lost IMEI? Then restored with SELinux disabled and you got your IMEI back?

Then, what the hell is the guy below talking about? :D

*panicking*
[Galaxy S 4 i9505 Android Development] ph3n0mII:
If you restored a backup from v5 that was made with selinux disabled then restored from v6 with it enabled and had a problem (IMEI in this case), which was fixed by restoring it from v6 with it disabled (wipe in-between 'probably' wasn't necessary), then after that you could re-enable it again and take a fresh backup with it enabled, to future-proof things...unless you plan to restore with v5 again for some reason in the future :cowboy:
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Exactly the same thing happened to me.

I made a backup of MGA with a version of Philz that didnt have SELinux option (or at least had it disabled as default)

I subsequently updated Philz during MGA, and eventually installed the first 4.3 release.

I didn't like a few things in the 4.3 release, so reverted back to MGA and lost IMEI

After hours of panicing and trying various things that mostly involved trying to restore efs, I found the SElinux option in the settings in the then-current philz had SELinux enabled. I disabled it, restored MGA again, and all was well again!

Ever since, I have kept SElinux disabled (rightly or wrongly!) and have never been 100% sure what to set this to since :)

I'm now on Dejembey MKE 4.3 (TW), still on old MGA bootloader (pre knox etc)

So should SELinux be enabled or not?
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, selinux enforcement was introduced start of 4.3

So, obviously, if you restore a a 4.2 backup on 4.3 and vice versa, you break things

hopefully, once you have a backup of efs, you can always restore it
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Is the important point here being backing up a 4.3 ROM, or a backing up when on a 4.3 bootloader?

I'm on a 4.3 ROM but still on a 4.2.2 bootloader.

If its the ROM, perhaps the option could be set on the fly by each backup made in recovery by reading build.prop?
[Galaxy S 4 i9505 Android Development] Phil3759:
Update v6.03.1
[Galaxy S 4 i9505 Android Development] sarbe:
Hi guys I've been trying to sort out the wrong time and date in recovery, I tried removing the battery for a period of time but no joy, any suggestions?

Bump : Anyone have any suggestions?
[Galaxy S 4 i9505 Android Development] dimedropper:
Is there a root fix option in this custom recovery?

My S4 is stuck in the Samsung boot logo after flashing with the AOSP 4.4 v5 (and v6) ROM developed by another member here. One solution suggested is to do a root fix then reboot. But he was talking about TWRP and said to look for the same option in Philz recovery.

Also, if I flash with an official ROM do I lose custom recovery?
[Galaxy S 4 i9505 Android Development] cdzo72:
Oops sorry... didn't mean to thank... meant to reply...

To answer your questions. .. yeah I think there's a root fix option in the recovery and 2)... yes you will definitely lose root and recovery and custom kernel if you flash an official, untouched firmware
[Galaxy S 4 i9505 Android Development] loomis:
download link seems down... it says

It appears something went wrong...
[Galaxy S 4 i9505 Android Development] dimedropper:
How do I do that? Explored the different options in Philz recovery but not able to find root fix option.
[Galaxy S 4 i9505 Android Development] cdzo72:
In PhilZ settings it says Apply root or something like that
[Galaxy S 4 i9505 Android Development] ph3n0mII:
Does that mean people on 4.3.1 or lower roms probably shouldn't update due to the cm11 base?
[Galaxy S 4 i9505 Android Development] Phil3759:
It has nothing to do
[Galaxy S 4 i9505 Android Development] Tassos_i:
Installed and tried a backup. So far so good.

Hopefully, one day [MENTION=4666971]Phil3759[/MENTION] will install a stock TW SE Enforcing rom on his own I9505 (even if its knox counter trips), and will have the opportunity to see that backup times on exfat 64 in 6.0.x versions are 70%-80% bigger than in 5.18.x versions.
[Galaxy S 4 i9505 Android Development] kfallz:
Not just exfat, the same for me on an normal card. My last backup took 18min 30s, selinux added a bit extra but it was the move to 6x version that caused a huge increase, as per my previous posts.

Not a huge thing for me as I don't backup that often right now, but for people that does it has to suck big time.. Feels kinda strange also since it wasn't that long ago most of the releases focused on speeding up the back up time.
[Galaxy S 4 i9505 Android Development] Tassos_i:
What annoys me is the fact that every time me and you (and some other) report this problem, there are immediately one or two people that report the exact opposite (that is, same unbelievably small backup times between 5.18 and 6.0), leading [MENTION=4666971]Phil3759[/MENTION] to believe that backup times on I9505 are totally random. So hopefully, he'll make soon his own opinion.

In any case 15 mins for backing up 2.6 GB on exfat 64 is still acceptable, even if it was almost half so recently ...
[Galaxy S 4 i9505 Android Development] Phil3759:
From 5.x to 6.02.x there is a major step to cm-10.2 aka jb 4.3. And now, a few days later, with 6.03.x we're already on kitkat...

Things went a bit fast and I focused on upgrading the sources as it is vital to continue developement. Sadly, as always, we see that migrating from cm-10.1 to cm-10.2 took a huge effort for many devs and that it is far from being completed in a satisfying stable way. And now, the cm-10.2 branch is dead incomplete for most devices and cm-11.0 is raised up.

Nothing I can do about. Jumping on cm-11.0 wagon since the start should help ending up with a better achieved product on this branch.

To give you an idea about the efforts that are done here, try to install stock cwm and compare backup speeds to external storage...

This recovery does about 10x faster on exfat/ntfs

There is still room for improvement but for now it is delayed to support new phones and improve migration to kitkat

Neverless, I advise updating as the 6.x versions fix a lot of bugs.
[Galaxy S 4 i9505 Android Development] ph3n0mII:
hmm..I've never had a backup that took over 2 minutes..typical size of 2.3GB for 4.3 TW (Echoe or Omega) or 1.2GB for AOSP based

You's using compression?
[Galaxy S 4 i9505 Android Development] Formhault:
Ah, I see.

Well, I only plan to use 6.x for backing up and restoring purposes... so I should have no issues whatsoever, with the IMEI or God knows what else. Right?

*has never been so afraid to backup / restore in his life*
[Galaxy S 4 i9505 Android Development] kfallz:
I'm not saying you're lazy or a bad dev or anything, just wondering what might have caused this huge increase in backup times. And as I said, for me personally the increase is less important than newer versions with bug fixes and new and improved features, but for some people it probably sucks quite a lot.

Yes I do, and used it before too but the backup times were ~50% faster than they are right now. The size of the files are the same as before.
[Galaxy S 4 i9505 Android Development] Advancer:
A small contribution as a thanks for your time and effort bringing us the best recovery! Confirmation number: 88702813YT808203D. :good:
[Galaxy S 4 i9505 Android Development] David78130:
So generous.. ;)

From my Galaxy S4 tuned with CM11/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] sniperwolf64:
Hi, yesterday i tried to root my friend's S4 I9505 that was on MJ9 official firmware using philz latest recovery available, but then i got philz recovery without root dont know why? Any help? Thanks
[Galaxy S 4 i9505 Android Development] Phil3759:
Many thanks for your support
[Galaxy S 4 i9505 Android Development] Formhault:
A recovery can be flashed via Odin (so, without rooting the phone). This recovery does NOT root your phone; that is what (some?) kernels do.

Hope I am not wrong here. If I am... *rises shields, starts sobbing*

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] Bejda:
:)

I'd say first that main/commonly used ways to get root rights are often devices specific.

I come from i9000 (where recovery.img comes within boot.img) and indeed,there,main way (except One-click or others exploit methods that worked from time to time) to root device is to flash a custom kernel.

From what I understood many i9100 and probably many others devices users had the habit to install root automatically by flashing Philz, that's why we see sometimes some new i9505 users (or people just dealing with it temporarily to help someone else etc..) reporting by here their surprise that they don't get root rights in the process.

Main root method used on i9505 (still except some "exploit" that may arise here and there) is for sure Chainfire CF-Auto-Root (or just,once any custom recovery installed, flash an aosp based rom which will come with root pre-installed) BUT! ;) Since Philz 5.18.9(?) there's possibility to install SuperSu binaries from within recovery (under Philz settings I guess),only thing left is to install SuperSu app from market.
[Galaxy S 4 i9505 Android Development] sniperwolf64:
Thanks for the responses. Is it possible to flash a custom rooted rom from philz recovery even though there is no root or should i flash Chainfire CF-Auto-Root from philz recovery first then custom rooted rom?
[Galaxy S 4 i9505 Android Development] Phil3759:
To root your system, In settings menu, you have an option that will flash Chainfire SuperSU binary

Now, you will be rooted but all apps will have free root access, no notification

You go in Play Store and install SuperSU apk, you will have root gui prompt.

For all other root questions -----> FAQ
[Galaxy S 4 i9505 Android Development] Formhault:
When I first got this phone, back in late August I think, I stood up until 3 AM to root it, flash recovery and a custom ROM. Only AFTER I found out Odin can flash regardless of root presence. :silly:

I demand I get my 3 hours of Googling back!
[Galaxy S 4 i9505 Android Development] hanspampel:
New version 6.03.4 is up. Thx Phil.:good:

But dont search for 6.03.5. There is only a 6.03.4 for our S4.;)

Downloads
[Galaxy S 4 i9505 Android Development] Phil3759:
6.03.4 ---> 6.03.5

Lucky you S4 guys, you bought me the phone

:good:
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Flash Abyss kernel, reboot, then flash your current kernel back on
[Galaxy S 4 i9505 Android Development] spevil07:
Hi, i am on Echoe Ultra Slim, i cant make any backups to internal or external sd.

"Error while backing up boot image!" is the message from philz ecovery.

Why? Many people have that error!!
[Galaxy S 4 i9505 Android Development] sir adem:
Thank bro????
[Galaxy S 4 i9505 Android Development] kfallz:
Since 6x, that doesn't seem to work anymore :/
[Galaxy S 4 i9505 Android Development] Mkhant30:
Hi bro, it's still working.. Just check my attachment for proof as I done a few hours ago. All the time & date are correct Just haven't tried restoring from this bkup.
[Galaxy S 4 i9505 Android Development] Phil3759:
Time bug affects ALL recoveries for new Qualcom phones, include LG, new Note 3...

They require a custom time_daemon we have no sources for

I have a few ideas but little time for it now
[Galaxy S 4 i9505 Android Development] spevil07:
Did you have an idea for my problem? It's a few posts before.

www.echoerom.com

EchoeRom ultra_Slim by adl & Spevil
[Galaxy S 4 i9505 Android Development] Rintenfinten:
Hi! I am having exactly the same problem as described above by spevil07!
[Galaxy S 4 i9505 Android Development] miro_i:
I am unable to install Philz Touch. Tried with Odin when phone is in download mode. It flashed successful and reboot, but did not enter recovery. Log below:

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.03.4-jfltexx.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
[Galaxy S 4 i9505 Android Development] ranger4740:
You only say your phone reboot.

How did you actually reboot phone?

Did you reboot after your phone was off (battery pull) while pressing and holding volume up and power button?

If you did not do this then you need to do some research on basic usage of rooted phone.

If you did do that, then try reflashing recovery again, I had to do that the very first time I flashed phillz recovery.
[Galaxy S 4 i9505 Android Development] miro_i:
Ranger, phone reboot by itself after Odin completed the flashing process. Install instruction says:

It did not auto-reboot into recovery but started the OS.

If i try to boot in recovery it displays

RECOVERY BOOTING

RECOVERY IS NOT SEANDROID ENFORCING

Set Warranty Bit : recovery

and stays at this screen with Samsung Galaxy S4 logo
[Galaxy S 4 i9505 Android Development] nabelo:
Install Zip won't work anymore

Hi,

since i installed 6.03.1 i can't install any zips.

Every time i try i'll get a "assert failed" --> Status 7 Error.

Installing the latest PAC nightlies is failing every time now because of this error.

Rolling back to the prior working "6.01.7" wont work, because i'll get the same error if i try.

Anyone can help me out here ??

Regards,

Manuel
[Galaxy S 4 i9505 Android Development] Phil3759:
Recoveries built under cm-11.0 (kitkat) cannot flash old roms if they do not fix their update-binary

Two solutions:

- you manually remove the assert lines from updater-script in your ROM zip file

- you ask your rom cooker to release his ROM with a new update-binary

I did not dig into the issue, but it could be related to kitkat using enforced selinux permissions
[Galaxy S 4 i9505 Android Development] Phil3759:
no logs no more support
[Galaxy S 4 i9505 Android Development] nabelo:
Thank you for the quick reply.

Removing the assert lines completely is working fine.

Thnx for the heads up....

Regards,

Manuel
[Galaxy S 4 i9505 Android Development] Phil3759:
Spare my time:

Use the THANK YOU button for this :angel:
[Galaxy S 4 i9505 Android Development] spevil07:
Hi, i am on Echoe Ultra Slim, i cant make any backups to internal or external sd.

"Error while backing up boot image!" is the message from philz ecovery.

Why? Many people have that error!!

My log is attached as txt.
[Galaxy S 4 i9505 Android Development] Phil3759:
You see, a log is always needed :thumbup:

The issue is in the way he names his rom mainly the & symbol. Only non special chars should be used. I do clean bad formatted rom names but I missed the &.

I will fix the issue in recovery, but you can just edit build.prop in your rom to fix it
[Galaxy S 4 i9505 Android Development] spevil07:
Please fix it, the problem have a lot of people and i dont know if they all can edit the build prop. ;)
[Galaxy S 4 i9505 Android Development] Phil3759:
Rom cooker should do ;)

But I will
[Galaxy S 4 i9505 Android Development] spevil07:
That's clear my friend. Me and a very good friend are the cooker, but a lot of people must change the build and I don't know if they can do it. ;)

It's much better than you can fix this. :P

www.echoerom.com

EchoeRom ultra_Slim by adl & Spevil
[Galaxy S 4 i9505 Android Development] Bejda:
If it really urge you could provide edited build.prop via cwm zip i guess,I once made this for someone unable to do it manually it seemed it went fine.
[Galaxy S 4 i9505 Android Development] Phil3759:
6.03.8 (13.12.2013)

[MENTION=2911853]BillGoss[/MENTION]

A nice change list for you, my friend ;)

Let me know what do you think of this new stuff

Your TWRP backups can now be set to default with direct access

Custom Backup and Restore functions are now part of main menu and need much less unfriendly navigation
[Galaxy S 4 i9505 Android Development] BillGoss:
I really like that you've made the format specification a nandroid setting and that you've removed layers of menus.

As you'd expect, I selected TWRP as my default in Misc nandroid settings.

However, a backup or restore, as opposed to a *custom* backup or restore, still use the clockworkmod folder instead of the TWRP one. And backup, as opposed to a *custom* backup, creates a CWM backup not a TWRP one (based on the contents of the directories).

I would have expected that, having set the format to TWRP, *all* backup/restore functions would use TWRP format and folders.

Here are:

Logs of the backup https://www.dropbox.com/s/yuti3mepl697rl8/6.03.8-last_log.txt

Listing of the clockworkmod directory https://www.dropbox.com/s/zu59te0csw90njh/CWM.txt

Listing if a TWRP directory https://www.dropbox.com/s/gnadtswqo9kjj0c/twrp.txt

ORS backups work fine.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] hawkerpaul:
As menu structures are currently being discussed, I've often wondered that historically with all cwm recoveries, wipe dalvik has always been placed the advanced menu. Why is this? It's probably because wipe cache is part of stock recovery whereas wipe dalvik is not. I think it would be more logical to group it next to wipe cache at the top level menu perhaps.
[Galaxy S 4 i9505 Android Development] Phil3759:
Seems a bug in fact :good:

custom backups are overriding twrp mode priority

I will fix it

Yes, I agree, maybe I move them
[Galaxy S 4 i9505 Android Development] KrAzYtHeBoY:
In last philz touch versions in flashing new zip show error. on all zips

assert failed: getprop

(Status 7)

installation aborted...

Testing Philz Touch 6.03.1 to recent versions...

please fix it!

NOTE: Im flashing in "OdinV3" philz touch 6.01.7 and work OK! 6.03.1 and up NOT WORK!

thanks
[Galaxy S 4 i9505 Android Development] Phil3759:
Nothing to fix

You cannot flash old zips with assert

Remove line or ask cooker to update his update-binary

Both you can do yourself
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.04.0

[MENTION=2911853]BillGoss[/MENTION]

I quickly tested backup/restore in default and custom modes

This should be a proper build
[Galaxy S 4 i9505 Android Development] sir adem:
Thanks Phil3759 :laugh::laugh:
[Galaxy S 4 i9505 Android Development] sarbe:
Hi Phil can you tell me why I can't backup modem etc it says not available.
[Galaxy S 4 i9505 Android Development] Phil3759:
in i9505 it is complecated and often fails ---> disabled
[Galaxy S 4 i9505 Android Development] BillGoss:
Tadah! It now works as expected. Nice work.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
:good: for the feedback

You're my main debugger for ors/twrp

It's a while now that I wanted to simplify all those tasks but never found time

GUI should be much more user friendly now and the custom backup/restore better accessible