Read your post too late. Work done so i will post it. Took me ages because when scripting fastboot oem rebootRUU with a flash zip command in succession, it always fails and it took me ages to figure out there needs to be a wait inbetween because fastboot oem rebootRUU doesn't seem to wait whereas the normal fastboot reboot contains a wait for device function somehow.
Here's the Flasher packed in a self extracting WinRAR archive:
LINK to HBOOT Flasher
13th of may 2013
- Added option 16: open CMD Prompt (to be able to quickly change CID when the zips refuse to flash...)
05th of may 2013:
-corrected an error in the script.
-inserted a confirm for S-OFF and Product at launch-time
If i understand this right, the RUU mode can also flash to p14 as splash, can't it? i mean the RUU would also update that part wouldn't it? So actually i can just adapt this script to flash the respective splash files but i would need to know how to name them correctly so its not flashing the p14 to p12 or some evil sh!t like that
would you know how that would look like correctly done?
The Hboot files all contain HTC__001 in the Android-info.txt file. I just had one user who could not flash them on his HTC__102 device.
If you happen to get error 42 wrong customer ID and get stuck in RUU Mode, please just run this command in CMD: "fastboot oem writecid HTC__001" and then repeat the hboot flash. It will be good then. Avoid rebooting the phone, just leave it stuck where it is and do the writecid command, then repeat the hboot flash. I updated the script so that option 16 opens a command prompt for you in the right place.
Also i forgot to point out this: the flasher script does NOT reboot the phone when its finished to give u a chance to see if everything worked good. You have to pick option 14 (reboot to bootloader) or 15 (reboot to system) afterwards to reboot. The green progress-bar on the phone will stop at about 3/4 of the way. That is normal! It only moves on when you do the reboot command!
It basically is to hold it there in case anything went wrong. If i had done the reboot automatically and say, the hboot got erased but not flashed, it would brick instantly. This way, you can catch errors and then decide to reboot if all went well.