I'm assuming that's because of the Android security model, rather than a limitation of the exploit itself?

edit: Apparently SETUID is disabled on Android:

  ... using kernel features that help block privilege escalation (e.g. NOSUID, NO_NEW_PRIVS).

source: https://lwn.net/Articles/609511/

also: https://unix.stackexchange.com/a/250806/95938