I fixed it.. I re-locked my bootloader and ran an RUU program and it re-installed the stock ROM. Thank you so much for telling me what the problem with my phone was. I wouldn't have been able to find a solution. Out of curiosity what caused this? I saw someone else do exactly as I did step by step and the custom rom loaded. Maybe in the future I'll try again.. I heard it may be because Hboot is 1.57 when I need something below 1.40.
I was just looking up the RUU for you
I'm glad you got it.
Yes, I have the Evo 3d and it's the same thing. I'm not sure what the bootloader versions are for your device, but on the 3d, you need a lower hboot (which requires s-off) to flash non sense roms. Aokp doesn't use htc sense and likely requires a bootloader downgrade to be able to boot the rom.
So that's likely why it wouldn't boot even though you flashed the rom and kernel, your hboot was probably incompatible.
Then what happened was, you had flashed an incompatible kernel (boot.img) for your backup. You flashed the kernel that goes with the aokp rom so then your backup wouldn't boot. You'd have to flash the proper kernel that went with your backup.
I don't know if 4ext recovery is compatible with your device or not, but you might look into it. It uses a feature called "smart flash" that allows s-on users to flash the kernel with a rom from recovery. This means no more flashing the boot.img through fastboot.
Not every device is supported though, so you would want to look into that before flashing it to your phone.
Also, are you on the sprint cdma version? I wanted to pick through the RUU for the boot.img so that you can keep it stored on your pc for future need. For example after restoring your backup, if you would have been able to flash the boot.img that would have been it. A lot easier than running an RUU.
Especially since the RUU removes root and requires you to lock the bootloader.
If s-off is available for your device, I would recommend it.
Also if you can't get s-off or use 4ext you can boot your recovery in fastboot. You can boot your recovery into the phones memory which will allow you to flash the rom and kernel without having to flash boot.img seperately.
If you use command
fastboot boot recovery.img (recovery.img being the exact name of your recovery) it will boot your recovery. You can then flash a rom normal without a seperate kernel flash.
Gosh this is so much information it seems so complicated.. I really want to give a Jellybean ROM another go but I am afraid my father flipped a cow when he saw the red letters on my HTC.... Also, my Super SU is gone.. Does this mean I have to unlock the bootloader through the HTC Dev all over again?
