[Galaxy S 4 General] Absolon:
Thank you!

Right now, all we have is the original rom, that is "normal" so I gess it's "dexed". I have no clue how to make it odexed, since what I understood it makes

the whole rom smaller?

The thing that worries me is the bootloader, since we only have the one with Knox in it and I don't know how other bootloaders work or are compatible.

But that means that we are locked into SELinux, right? So until having a "Knox-free" bootloader we can't do **** when it comes to customizing roms?

Because we can't add our own kernel or is there some code that Samsung have, because I found out that Samsung had a code-repo (wow), but

not for this phone yet.

I tripped the Knox-flag when I rooted it. Found no other way really. And I don't know if this is Knox-related or something else. I noticed this on the i9505

as well. I have space but when I try to install things it says that it's out of space and can't install it. The "funny" thing is if I push the install from the webpage

of Play it installs just fine so it's seems to be something preventing it?

I don't recall if I had it before or after Knox since I tripped Knox unknowingly on my other phone before we even found out what it was.

So I need to clean it out. Yes, /system is 76% full with the original. Since all I have done so far is just rooted the phone.

If someone has an I9505, can you do

1) df -k

The partitions (not counting the sd.) on I9506 are:

The root partition (/)

/efs

/firmware-modem

/data

/persist

/system

I'm too tired to write out a good coomand, but best is to use "find" and with some -printf options and then start to hunt.

Then we can compare the phones. The special parameters for SELinux are the next step. But this is a start to see how

The SELinux special parameters part is also something that I want to see, but I want to start with this.

Btw. On my Note 3 I got an "update" of the SELinux rules. Anyone else? (Will ask in the Knox-tread as well).

That is not rooted but totally plain vanilla and I didn't even noticed that there was an update function but got "update 16".

See my post: From Knox-thread

I read and read this night, and to just condense it since I write too long anway and I'm tired. Since the bootloader

is loading an SELinux, that won't boot if it's not compared with an unique X.509 cert in every phone and see if the

loader checksums we really get an virtual environment. That is the "wrong" feel I've had I think. And I think that we need

to sit down and test some things to verify this theory. Get some programs that can do some deep probing of the hardware.

If I'm right, and they have made a VM out of the phone we should probably notice it somehow, because it's easy. I looked,

SEAndroid that NSA created is a VM with Xen.

That means that the SELinux can just run in the background with it's processes that it will never show to you and you think

you have a rooted and Knox-free phone when you never have it since the bootloader loags a SELinux and makes a sandbox.

If's perfect. Unique id on each phone. Your signature on the papers with the serial numbers which identify you as the owner.

So perfect that I could cry if I was an engineer at Samsung...

/Abs