Lol he flashed a kernel I made for a completely different device, the Samsung Galaxy Player 5
Now, let's see just how badly you screwed up your phone. My kernel for the Samsung Galaxy Player 5 flashes the kernel image onto the mmcblk0p11 partition since that partition is the boot partition on the Galaxy Player, and it flashes the kernel modules onto the Galaxy Player's system partition, which is mmcblk0p13. In other words, your Sensation's mmcblk0p11 and mmcblk0p13 partitions have just been corrupted since they now have data on them that isn't supposed to be there. The boot partition and system partition on the Sensation are mmcblk0p20 and mmcblk0p22, respectively; they are not mmcblk0p13 and mmcblk0p11. The partitions you just nuked serve a different purpose on the Sensation and I'm not sure what that purpose is. I just extracted a list of all the partitions that Android sees on my Sensation when it's booted up, and mmcblk0p13 & mmcblk0p11 weren't on the list. This *could* mean that mmcblk0p13 & mmcblk0p11 are crucial to booting up the phone or the bootloader; I don't know because I don't know what functions the mmcblk0p13 & mmcblk0p11 partitions serve.
In summary, your mmcblk0p13 and mmcblk0p11 partitions have been nuked and I don't know what you can do about it. Are you able to boot to the bootloader at all?
16 years old and still not even close to being the youngest developer/user on XDA
Cortex-A optimized Linaro toolchains from Christopher83