Here is what is going on behind the scenes, according to xda user 's5610'
1) Script crashes moto_crypto.
2) Factory recovery gets replaced by May 1 kernel.
3) Reboot to recovery, but there is kernel instead - it gets booted, and we got vulnerable to Towelroot system under May 1 kernel.
4) We do root job, then quit.
5) Factory recovery returned back.
6) Script starts moto_crypto.
7) Normal system start, as if nothing happened.
W/o moto_crypto crash trick the kernel isn't stable + has no rw rights. Also there are few lines changed in giefroot's *.sh + custom install script. What exactly changed, and what for - I don't know, being not dev )
And ATTACK found out the exploits they are using...
It's using the CVE-2014-7911 exploit
>
Please Login or Register to see this Hidden Content
Please Login or Register to see this Hidden Content
And CVE-2014-4322 exploit:
> Please Login or Register to see this Hidden Content
Please Login or Register to see this Hidden Content
Sooo... it looks like it may be a working root exploit, however, I'm gonna still call bologna on the BL unlock. A root exploit and a BL unlock are miles apart without the bad TZ partition.