SuperCID not accepted by RUU; unlock token rejected by phone. Bricked? - HTC EVO 3D

Hello Evo3d forum!
I've had a GSM 3D for over a year now, and love it. Decided to try rooting/flashing a little while ago, and unfortunately have gotten myself into a fix.
Here's a TL;DR of the problem:
Bootloader "relocked", SuperCID not working for RUU's, [previously working] HTCDev unlock token rejected by phone.
I have no idea why a SuperCID wouldn't work with an RUU (I thought the point was to be able to use any RUU?), or why my unlock token/code would stop working. I did a lot of searching, and it seems that a invalidated unlock token is a common problem for people who had their motherboards replaced, but this is not the case for me. My token file worked for me just a few hours ago, and there was no hardware-fiddling since that time at all. Did the RUU's do something to the bootloader?
I'm wondering if I've soft-bricked my 3D...
Full problem description:
On HBOOT 1.53.0007; S-ON
Unlocked successfully via HTCDev, flashed ICS Sense-based ROM successfully.
Decided to downgrade to 1.49.xxxx since many other ROMs seem to require it, and getting S-OFF would be easier with a 1.49 HBOOT.
Figured using a pre-ICS RUU should do the trick (in retrospect, this was probably a mistake).
Acquired apparent pre-ICS RUU (RUU_Shooter_U_hTC_Asia_TW_1.23.709.4_Radio_10.55.9020.00_10.13.9020.29_M_release_211198_signed.exe)
Relocked bootloader via "fastboot oem lock"; started RUU .exe.
RUU fails, returns "Error 131: Customer ID error"
SuperCID phone from HTC__044 to HTC__001 (second mistake - I forgot to unlock the bootloader before doing this)
Phone accepts new CID, retry RUU; still Error 131
Decide to screw it and just use an ICS RUU to reset phone, and pursue some other method of downgrading hboot
ICS RUU (previously worked multiple times) gives error 131
Attempt to reset CID from HTC__001 to HTC__044
CID writing appears to work, but phone reverts to HTC__001 after rebooting.
Figure bootloader lock is preventing CID writing, so attempt tp unlock via HTCDev token
Unlocking failed with "remote: unlock token check failed" error. Attempt multiple times; all fail.
Attempt to boot into recovery (TWRP), fails; RUU's appear to have wiped the partition (You'd think it'd check the CID before doing anything..)
Here's the commandline input/output for resetting CID. My input is in blue, relevant output is in red:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[COLOR="blue"]fastboot oem readcid[/COLOR]
...
(bootloader) cid: [color="red"]HTC__001[/color]
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot getvar all[/color]
(bootloader) version: 0.5
(bootloader) version-bootloader: [color="red"]1.53.0007[/color]
(bootloader) version-baseband: 11.25.3504.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.707.1
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) product: [color="red"]shooter_u[/color]
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG8630000
(bootloader) cidnum: [color="red"]HTC__001[/color]
(bootloader) battery-status: good
(bootloader) battery-voltage: 5770mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 10e127f0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.492s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem writecid HTC__044[/color]
...
(bootloader) shooter_u_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) Start Verify: 3
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 1.409s]
finished. total time: 1.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem readcid[/color]
...
(bootloader) cid: [color="red"]HTC__044[/color]
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot reboot-bootloader[/color]
rebooting into bootloader...
OKAY [ 0.202s]
finished. total time: 0.203s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem readcid[/color]
...
(bootloader) cid: [color="red"]HTC__001[/color]
OKAY [ 0.006s]
finished. total time: 0.007s
For unlocking the bootloader:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot flash unlocktoken Unloc
k_code.bin[/color]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
[color="red"]FAILED (remote: unlock token check failed)[/color]
finished. total time: 0.156s

---

Phew! I've managed to find a solution.
The answer to this conundrum was to obtain, and use another unlock code from HTCDev. That unlocked the bootloader, and hallelujah, everything became flashable again (well, as much as can be an S-ON 1.5+ HBOOT -_-' ).
I really thought I was a goner, for a few hours, though.
I can only deduce that this problem was caused by the RUU's screwing with the bootloader, and somehow changing its unique ID; possibly due to the interruption caused by mismatching CID's. If this really is the case, then that's some ridiculously bad exception handling by the RUU program.
So yes, if you come across this problem, the solution is to head to htcdev.com and follow the instructions to unlock the bootloader again (submit identifier code > receive unlock_code.bin > flash token to phone via fastboot). Then reflash recovery and ROM.
Hope this helps someone!