[One (M8) Android Development] Sneakyghost:
fastboot flash nameofpartition partition.img does NOT work anymore except for recovery and boot!

Instead: rename the mmcblk pieces into boot.img, recovery.img etc etc and then ZIP them up as outlined in my guides (oops not up yet but available through the M7 Thread linked in post 5!) the digest would be: use 7ZIP, use normal or no compression as profile, dont touch any other settings. Then you can flash that zip as firmware zip like outlined in Post #1

Please download the FULL STOCK package from me to get an idea of all the images in a RUU! You only need those mmcblk's which correspond to the ones in my FUll Stock package! PLUS the System.img which i always take out. Then you have your firmware.zip to restore. If you want to make it a RUU, drop it into my empty FUU structure and run ARUWizard and it will basically put your phone back to your dump-state the way i always imagined it but never did (had no use and was too scared to risk anything for no use).

The RUU's you linked are all for the china phone. Not sure what the point would be to make packages of them here. I will drastically cut down on what i do here compared to my M7 job.

There will be NO modified hboots anymore due to security questions

There won't be lots of ZIP's anymore, i won't hunt any down, just the major versions and what users link me to HERE. This is due to time constraints. I will be focusing more on helping team venom on their site.

I am probably ceasing to research a lot of info as that was most time consuming. I will convert the M7 infos to the M8 and add new vital stuff if any comes up but rely much more on people to send me these infos, not research too much myself. Just don't have the time.

Think this will mainly about the FUU for now and not much more.

[EDIT]

Added link to partition Layout List into post 4 - realized the RUU Image names are still missing in there. Not much help. Need to put them in. DT.img for example, not sure which partition that is. There is a few more like that, where i have the RUU Image Name but not the position on chip. Gotta figure those out before you can do a full RUU equivalent from your dump, mate. Help find out!

[EDIT 2]

data partition is not in RUU but needed, RUU has DZDATA_xxg.img and DZDATA_xxg.hdr files, which somehow tell the RUU how to restructure the data partition and contain the bloatware.

Hence, i am unsure if you can actually create an image from your data dump, which would be MASSIVE anyway. I suggest you take the DZDATA files from any other RUU like from my GSM or Sprint packages (on my AFH you see both sprint and gsm) and place them into your custom RUU instead of your data dump. They will work. No problem there.

[EDIT 3]

Quickly updated Partition Info in Post #4 with what i know, not much though, some things are to be said though: the whole bootloader and security stuff should be taken from a RUU, not a dump, as the risk is high that dumps contain Serial and IMEI and encryption keys from another device and that can ultimately brick your phone. I am not able to securely identify which partition images you should take from a RUU and which mmcblk's that would replace from your dump. Most definetely you need to have sbl1-1.img, sbl1-2.img, sbl1-3.img and pg2fs_spcustom.img from a RUU in there i would say. Not the Dumps. Everything thats not in a RUU needs to be taken out.

Sorry for thinking out loud here, might sound complicated. Just dont want to make another extra paper on how to create a custom RUU. maybe you go over to [MENTION=4139782]crushalot[/MENTION] and ask him too. If he did that already he can save me thinking about it too much :D

I have a HTC One S Special Edition (White 64GB) from HTC. It has a 999 marker. These phones are made for HTC's internal use and have no target market. Hence that weird Regional Code. That VIP community HTC Elevate hands out phones occasionally. Those have that code for example. Plus the TradeFair samples and such. You know, just phones HTC uses to showcase their products or phones they give away...