[HTC One Max] DrPhant0m:
As a prospective HTC One Max owner on Verizon's network... I have some questions.

It seems as though this tool can *not* turn a stock Verizon HTC One Max into a rooted HTC One Max with unlocked bootloader and custom recovery... correct? (See post 76 and later)

I'm seeing that you need to unlock the bootloader first (which verizon will not let you do via HTC-Dev)... and the suggestion is to use the firewater method (which is independent of this tool). I looked into the firewater method, and it says you need an HTC-Dev unlocked device, or a working temproot. Can anyone comment on whether the "temproot" is the method to use for Verizon devices? How well does it work? The temproot instructions say "This method

may

allow firewater to work on a fully stock/htcdev locked device." so they don't seem very confident.

Next... I am aware that many new devices (My S3 included) now have a software "switch" that indicates that the phone has been rooted/unlocked/etc. Will this tool preserve this switch? (Tools for the S3 are able to preserve this switch) I don't see this explicitly mentioned in the OP. At least... it isn't mentioned in a way that I recognize. If I use this tool to perform a root/unlock... and then something unrelated happens that would mandate a warranty replacement from Verizon... am I able to put it back to "stock" without VZW knowing that I have modified it? Obviously, I take responsibility for bricking the phone software, but if I have problems with a broken earphone plug... I don't want Verizon to block my replacement because the phone is rooted.

Also... when all is said and done... will I have a permanent-root on my phone? And not a "bootstrap" or "temp-root" ? Long ago... I had problems with soft-bricking my Droid 2 Global... not being able to get into recovery... and having to flash a stock firmware (wiping EVERYTHING) using the Moto Dev utility to get it working again (equivalent to using an RUU file to flash the phone to "out of box" condition). I vowed to never have to do that again, and my Galaxy Nexus and Galaxy S3 haven't given me problems because I can always get into recovery, and I always keep a working ROM zip on my phone in case of emergency. Is this the case with the HTC One Max?

Related: I see in the first post, it is planned to add RUU support. Even if this feature is never included... am I still able to use some application to flash an RUU if I have need to? Or... am I SOL until RUU support is included in THIS tool? (This would violate my vow to never have to restore my phone via a manufacturer firmware file... but it's better than bricking the phone without a way back)

Finally... what's the outlook on continued development for this phone? I've gotten the "bleeding-edge custom ROMs" out of my system for the time being, and I'm running a cyanogenmod 11 snapshot (relatively stable build) on my S3. Will One Max owners consistently get compatible CM (AOKP, PA, etc) releases? For instance... I'm looking at http://wiki.cyanogenmod.org/w/Devices#vendor="HTC"; and I don't see the "One Max" Only Verizon's HTC One (not Max), device "m7vzw." I presume that they are not interchangeable... and I'm seeing elsewhere that I should be looking for "t6vzw" instead... which is currently not in the device list.

Sorry for the long post, and I apologize if any of these questions have been answered throughout the thread. I spot-checked a few of the pages, and scoured the OPs before writing. Thank you for your time and attention.