[SuperSU] NoSpax:
Hello, new user here.

Since I stuggled with root on my Phone and somehow managed to maintain it, I thought, I 'd share you the stuff I did with you.

I put the TL;DR between hide, if you want to read the story behind my struggle anyway, you are welcome.

I am better with explaining stories then explaining things.

Spoiler content hidden.

TD;TR for those who didn't want to read the story:

I rooted my phone 2 times with Kingroot and finally wanted to switch to SuperSU.

After I accidentally broke Kingroot the first time, blocked it's Internet access and unrooted afterwards, I got stuck with a unrooted phone and Kingroot failed to root it.

I was lucky to fix that problem and rooted again with Kingroot.

After months, I used SuperSUME to change that. After SuperSU was installed, i made the mistake of unticking "Enable Superuser". Bad idea.

Tapping "Enable" again, it failed to update the su-binary. oh god. I unrooted again.

While traversing through my directories to start Kingroot again to root, I found my "shadow copy" of SU.

Wut? Shadow copy? Let me explain:

After my first unroot, I wanted to have a SU backup anyway

at all costs

, just in case I accidentally messup root again.

Now after hours I think I know why it doesn't work.. the normal way, of course.

I installed SuperSU, went into

/data/data

(or where ever SuperSU has its files) and took a look at them.

Unpacked the SuperSU APK on the PC and gathered all "needed" (I think were needed) files.

I hexedited the most SU binaries from SU to ZU and changed all other referenced binaries as well.

I am sorry about that, Chainfire. I was just testing things.

SU => ZU

SUpolicy => ZUpolicy

setup_su => setup_zu

99SuperSUDaemon => 99SuperZUDaemon

daemonsu => daemonzu

zygote => zugote

I had no idea what sukernel was for, so I left that out.

Why call it ZU? "Sun Tzu" thats why. Known as "Sunzi", he wrote Book about "the Art of War".

After I made sure everything is properly renamed and edited, I moved them onto my phone in the right directories required and chmod them.

I don't know much about that, I just copied the chmod numbers from Kingroot SU and some weird script I found on the web.

Tried to run it using JuiceSSH local terminal, and BAM!! the SuperSU box popped up.

But pressing "Allow" accepted it and nothing else happened.

It became stuck after ZU... it did nothing, but the daemon was running as daemonzu and daemonsu at the same time..

JuiceSSH popped up in SuperSU (while it told me the SU bin was outdated), though.

So I was on the right track, but a piece of the puzzle was missing, so I stopped delving deeper into it.

And forgot about it until about yesterday - where I disabled "Superuser" in SuperSU.

Midwhile the su binary changed from Kingroot SU to SuperSU SU.

Note: It should really ask "Do you want to disable Superuser? SuperSU will delete su binary" Yes/NO.

As I found those files, I started JuiceSSH and typed "zu".

This time, ZU somehow worked like it should.

It spawned a root shell. OMG...

I guess it somehow requires something else needed, which wasn't working while Kingroot was active.

I tried "Root Checker" and it failed. I had no "official" root. But still root available in JuiceSSH.

Somehow I managed to restore SuperSU to normal status. Guess this thing can latch onto an active root user or so.. no idea.

I even screenshotted this, cause I couldn't believe it. If you want, I can post those.

I have now a working second su on my phone, which is hidden from most apps.

But I think it is not perfect, it relies on something SuperSU does or installs during installation.

I apologize again to Chainfire for editing his stuff.

So, now my questions:

1. How can I make it perfect to run standalone, only using SuperSU as a GUI for (Allow/Deny)?

1b. Can we make it part of SuperSU? As a special function: "Install Stealth SU"?

2. Can we use that for something else? -> Probably for this? http://xdaforums.com/apps/supersu/suhide-t3450396

3. Why must the binary be called SU? I know it's for the most apps to do their job and somehow Linux standard.