as youve found,the unlimited team is very adiment about their directions being followed exactly,and their tools not being incorporated into all in one kits. with the complexity of new phones,the processes are very intricate,at the least. any varience,while may work in some cases,can get you into trouble.
if ladyx's advice was to run an ruu,then that should get you up and running.
from the info below,you need the correct ruu. you canot update backwards on an s-on device(from 1.14 to 1.13) so we need to find an ruu for 1.14.652.0.
Update from image version 1.14.652.0 to image version 1.13.652.2.
My phone went back to the bootloader screen, and where it says "RELOCKED" at the top, it says right below that "SECURITY WARNING" now
What now?? lol
failing that,you can always re-unlock your phone with the original token. the
security warning is what happens when the bootloader is relocked on custom firmware,and nothing to be concerned with. the ways out are:
1)run a full,signed ruu
2)re-unlock.
i *think* you are stuck on jpbear's custom boot image. if you cannot find an ruu to run,you can try this:
-pull the boot image from your rom onthe PC. put it into the folder containing fastboot(c/android if you followed htcdev directions)
-reunlock bootloader
-flash the boot image with this command:
fastboot flash boot imagename.img
(assuming the boot image to just be named 'boot':
fastboot flash boot boot.img)
-launch or boot to your recovery
-full wipe and reflash rom
-cross fingers
-reboot
only try this as a last resort,as i am not a member of unlimited.io and you should make every attempt to do take the course of action recomended by them first.
im off to work,so i dont have time atm to help you guys look for the ruu,but brian is good at tracking them down. ill try and watch in case you guys have further questions