[T-Mobile HTC One (M8)] Sneakyghost:
If you check my thread here: http://xdaforums.com/htc-one-m8/development/progress-fuu-m8-t2813792, post #1, the error code descriptions, you'll see that its to do with the RUU recognizing the phone as not the right one. Image Error in this case refers to the whole ROM.zip inside the RUU, HTC just has some stupid naming things going on like also calling a "flash" a "flush" in its RUUmode flashing output. Same here. Image refers to zip. You're about to flash the wrong zip. Since you do have the correct RUU, something with your phone is not right.

Check these things:

- Are you S-ON? Then you need a RUU equal or higher version than what you currently run (OS line in Bootloader is determining this, not software/about).

- Are you S-OFF? Then check if you have the correct CID - you might have changed that in the past. SuperCID (11111111) will do the BEST job. Do that.

- Did you ever change your MID via available guides on XDA? Change it back to its TmoUS value (if you don't know what MID is and how to change it, you didnt do it).

- Did you launch the RUU while booted into android or while booted into fastboot? In Android, the RUU looks at the software version and device ID in Software/About, while booted to fastboot, it looks into the MainVer ("OS" line in Bootloader). Possible sources of error here: MainVer ****ed up from TWRP (yes it has a bug that actually deletes the partition containing your MainVer/OS line). In Android: You flashed some non-tmo ROM and the software version now reads something not TmoUS (TmoUS is always x.xx.531.x).

Solution strategies:

- If S-ON, go S-OFF, boot to fastboot, do: fastboot oem writecid 11111111 - this will make the RUU ignore both CID and MID mismatches!

- If S-OFF already, see above

- Try launch the RUU from the other starting point (e.g. if you tried from booted android last time, try again from within fastboot).

- If S-OFF, flash any TmoUS firmware package that includes a stock recovery, so you get back your MainVer, then run the RUU again from within fastboot.

Notes:

- While S-ON, there is NO way to restore the MainVer if it got killed by TWRP other than a RUU. If the RUU doesn't run because of this bug, you are screwed. You WILL need S-OFF.

- S-OFF and RUU (or my FUU for that matter) is always the easiest most painless and safest solution. Only downside is you loose warranty (if you unlocked via HTCDev). If you never unlocked via HTCDev, you may use Sunshine S-OFF to circumvent HTCDev which will later allow you to restore everything back to stock and remove any traces of your doings and HTC will have no records of your unlock, since your IMEI didn't get recorded at HTCDev. This is where reading a lot before starting to mess with the phone really pays off. Maybe with your next phone then. I believe you said you were unlocked already.

- Correcting bad drivers (no ADB and/or no Fastboot): most painless way is to download HTCSyncmanager, install, then remove again. The drivers will stay. Every other way on windows is pretty much a game of chance. Some get it working manually, the majority doesn't. HTCSyncmanager itself should not be installed while doing the S-OFF thing.

Risking that i am accused of aggressively advertising my thread, i can only suggest you guys head over there and read what we have found out the past years. Its a good starting point to get to know some basics and for the more advanced stuff, you at least know what to search for later.

Hope i could help.