If I had the knowledge, I would write a clear, concise guide on how to root your ZMax but I don't.
One of the first rules of bug writing is to write the bug in a way so that someone that has never seen the app can easily regress the bug based on the way the bug is written. This way new Devs and QA Testers on the project know what's going on.
With all of the work the Devs put in to Rooting the Z, I'm surprised no one has bothered to write a clear, concise newbie guide, which is one reason why devices are getting bricked.
Example on the "simple" way to root from another thread: (The "How?" has been added by me)
Method 1 backup restore
1. Get su binary on sdcard (How?)
2. Make a backup of your system and boot (How?)
3. Run Restore from twrp(this restores your backup you just made) (How?)
4. Don't reboot yet
5. Mount system in twrp (How?)
6. Copy su binary from sdcard to /system/xbin/su (How?)
7. chmod 755 with twrp file browser (How?)
8. Copy install-recovery.sh to /system/etc/install-recovery.sh (How?)
9. Chmod 755 install-recovery. sh (How?)
10. Copy daemonsu /system/xbin/daemonsu (How?)
11. Chmod daemonsu 755 (How?)
12. Cleanup delete old ku.sud from /system/xbin (How?)
Delete /system/use/iku (How?)
Delete kingroot.txt in system folder
Reboot
Enjoy SuperSU
Tell me, what noob is going to understand how to perform most of these steps?
Not asking to be spoon fed, but when it comes to something as Rooting, which can Brick your device, someone with the knowledge can't take 5 minutes to write a clear, concise, step-by-step guide?
When I was into playing with Satellite Encryption, I would write clear, concise steps that someone that has never hacked encryption could easily do first time around and it was more detailed than rooting a phone.
Now, when it came to troubleshooting, I would point them in the right direction and see if they could figure it out as knowing your setup was the key to troubleshooting it, and everyone had a different setup be it sat box, switches, LNB's, etc....
But a phone is all the same. There are little to no variables.
Instead of answering numerous "how to" questions and posting "You're bricked, sorry" responses and having someone be without their only phone, wouldn't it make sense for someone with the knowledge to write a clear and concise Root how-to?
Hell, I used to even include screen shots when I was writing hacking sat encryption instructions for newbs.
For now, I will wait until the bugs are worked out and either an .apk is available or a concise how-to is written as I do not wish to brick my device as most of the instructions are outside of my scope of knowledge and by the number of people that have bricked their devices, it's outside their scope as well.
Also, with all of the control the user has over the Android OS compared to the iOS, I could see how Jailbreaking would be needed, but Rooting an Android doesn't have nearly as many benefits as JB'ing an iPhone IMO
Either way, I'll sit this one out until a more stable Root is available that doesn't require numerous tries to root.