[Galaxy S 4 i9505 Android Development] Bejda:
Hi, "unknown baseband&imei" problem with this rom from what I understand is just that it's another Touchwiz 4.4 rom still using set_perms but...well I'm accumulating many interrogations lately i guess it's time to ask :)

Need for touchwiz 4.4 roms to use set__metadata to be flashed with Philz appeared with 6.09.6,personally i expected that it would be the case with any Philz version since first custom TW 4.4 roms so i wondered why it was still ok (no unknown baseband&imei) with 6.09.2 and not since 6.09.6 ..only thing i could think about that could be related was the swap update-binary feature that if i got it right is meant to allow users to flash indistinctly 4.4 and previous android versions roms with same Philz recovery version? But for me it seemed like two different stories (swap update-binary & set__metadata) so i wonder here again..

Why only since 6.09.6 version and not since Philz is based on CM11 kernel sources? (don't remember clearly where I caught this,when others ask me why that set__metadata need only with Philz and no others recovery my answer, without knowing much as you can see, is that it could be due to the fact Philz is based on CM11 kernel but I'm really not sure of anything and unable to give more details..)

So:

1:

1_a: First did i understood right the swap update-binary feature lol? And additionally is it now really introduced since 6.15.3 version with " toggle for fall back to pre-built update-binary"? I didn't tested/tried to understand things by myself on this side,sorry.

1_b: Am i near from anything true with my CM11 kernel base answer to those wondering "why only Philz requires set__metadata to flash this rom?" and if right then why set__metadata required for 4.4 touchwiz roms only since 6.09.6 and not before? Is it finally really related to the swap update-binary feature in a way?

1_c: You just said in the answer i quoted that set__metadata should be required by any recent cwm version but users flashing TW 4.4 rom with set_perms updater-script don't face unknown baseband&imei issue when they use latest stock cwm (6.0.4.4 at the moment for jfltexx).

Is it cause it's still 6.0.4.4 while your is 6.0.4.7?Something else?

Btw (question came to my mind while typing) maybe things will be more clear/expected when custom kernels used these roms will have Samsung 4.4 sources available?

2:

I have mixed feelings about " Fix potential chmod failures" (since 6.09.6)..

Understand me, what i love with your recovery is that it's an ambitious project if I can say,i mean (not sure how to say it in english) it "pushes things forward" and we learn a lot by using it and following its development. That "Fix potential chmod failures" participate to this philosophy I'd say and anyway updater-scripts shouldn't have set perms failures but i wonder about its utility vs issues reports it can trigger from users and (sad part) others users misinformed statements and answers such as "don't use Philz/switch to another recovery" that I'm already fighting as much i can here and there (people use or advise recovery they want of course, especially if they're not able to keep themselves informed about the tools they use but such misunderstandings and unfair statements makes me really sad lol).

Is it worth it that Philz recovery "takes the blame" for cwm zip creators errors?

Stuffs like a perms set on file that doesn't exists in the zip shouldn't produce big problems anyway?

And, just to give a personal related issue, i'm not very skilled with updater-script and tend to prefer keep learning by creating my own cwm zips but i sometimes use an application named ZIPme (specifically for TitaniumBackup,unlike TitaniumBackup built-in update.zip feature it can restore my paid TitaniumBackup version with settings and all..saves me some time and data plan after a wipe data if I'm without wifi). Well app is pretty well done,really handy for many stuffs,but there's sometimes a little mismatch : it will set perms to let's say /data/app/com.keramidas.TitaniumBackup-1.apk when file is actually named com.keramidas.TitaniumBackup-2.apk.. not a big deal it seems,it apparently works fine anyway but then since 6.09.6 version the zip throw out an error and doesn't installs.

Do you think this feature, still as it fits well Philz philosophy imho, could be kept but toggled on/off or maybe better keep the debug part (apparent on recovery.log) but not fails the zip installation?

3:

Not your problem but i'd like to know a little more and don't really know where to ask..

I wonder how one can script manually set__metadata lines in his updater-script,i mean it sounds difficult lol.

From what i understand Aosp/CM builders have the hand on updater-script before they start compiling but big part of it (perms on files/folders) is produced automatically no?

Touchwiz rom cookers on their side edit their updater-script manually..

I searched (a very little with my very limited knowledge,guess I'm spotted now lol) but didn't find any related documentation..

Well all this isn't a very big deal on my daily Philz recovery usage, I'd just like to understand things better and grab the occasion to express my appreciation about Philz project overall "philosophy" (can't find better word) :)