[Galaxy Tab S2 Android Development] engine95:
Oh boy. This is gonna be a novel. ;)

SEAndroid kernel or recovery - means nothing. It just didn't pass Samsung checks/hash

This will show if you /system root.

SuperSU 2.74 as I know of:

SU as a systemless root, in a nutshell, rebuilds the ramsdisk with SU in it. So it's in the kernel now. Just like the old ICS and older root methods. But when it rebuilds the ramdisk, it re-hashes the numbers so they match and pass the checks. Which removes the SEAndroid warning.

Thing is, if you do this too many times, it will not work. (I think I may have figured out why, but haven't had time to look into it).

init.d

I'm pretty sure that when systemless root is rebuilding the ramdisk, it's disabling init.d somehow. (Again, I haven't had time to look into it yet) But using /system root, everything is fine.

/system root vs systemless root

I don't know why everyone thinks they have to have systemless root? /system root is tried and true and EVERTHING works. If you look at the DL's for /system root, there is still quite the demand for it. And I'm sure it will be an available option once Chainfire gets things squared away. Right now it's grayed out.

systemless root back in the ICS days was easy and didn't modify the kernel much at all. And everything worked back then. But now, with security being such a big deal, it's creating a lot of problems. Hash checks and hash numbers strung all throughout the ROM. (My memory may not be the most accurate on the ICS and prior Androids. But it's close)

What I see is a nightmare and a lot more work to build the kerenls. Right now we can and just have the SEAndroid warning. But if the ROM has been rooted prior to installing the kernel, things get messy. The numbers don't match anymore. And, depending on how everyone roots. systemless or /system.

Kernels

SU is getting into the kernel with systemless root. It's actually quite invasive from what I've seen with 2.65. Idk about newer versions. But from a building standpoint, it's not the easiest thing to do right now. I've redone the kernels 3 times so far. And I don't know if they should have root already or not. That hasn't helped figuring things out.

Estrong and other apps saying no root or not working

Again, /system root will make everything work. Maybe the devs of these apps are lacking updating. But maybe the other apps don't check root good enough? Something to think about.

I've written the dev of Estrong a couple times in the last month. No response and one update since.

I've already had to redo stuff as things progress with M and root. And it's getting very confusing. Having to deal with different root methods and getting things to work for everyone. Not an easy task.

I don't know why, or if you're the only one having issues installing the "Maker" on the 810. As far as I know, you are the only one. Many others have had no problems and are using xposed. 710, 810, 815 installs that I know of so far.

So what I would again suggest, is go with /system root and flash the init.d kernel. Everything should be fine then.

Then, when the dust settles with root and M, we can move on.

Sorry for the novel, but maybe it'll help you figure things out. :silly:

(I might have repeated myself a few times but I'm not editing this thing. Plus, I may have reworded things to make better sense.)

The Rom is only for the 710

The "Maker" is for everyone. It's all in the OP