SamyGO

OK. Your repair scenario:

1. You need to make deXORed images. Read here. Use exe.img.enc and appdata.img.enc from patched firmware
2. Next you have to do all what gem0237 did. Use xor tool he attached.
3. Here is wiki page with instruction.
You can skip step10 or ignore error if you get.

sure on pc.

From log we can see that your images are flashed successfully.
But you have got error with phyton, it is bad, you have written wrong images and got errors.
Try dexor images once more, use xor tool it's simpler than python.
Extract xor.zip to c:/temp and copy exe.img.enc, appdata.img.enc next to extracted file.
Then start console navigate to temp dir and run tool by entering Flash files you get again. Maybe you can use another USB flash disk?
Remember, do not cycle on unmount step, you need it unmounted only once. Be carefull by entering commands, here you did mistake: Make sure you use small L letter in bml not digit 1 and mount appdata to bml9, not 8 ok? Anyway, not this is your problem.
Do not play with u-boot.bin and other, you have successfuly restored it already, you need only exe.img and appdata.img.
If you do not get success i can make those images for you.

The message you see is sent from the secured boot loader. Something went wrong with your MAC (hash of kernel against actual kernel image). So the secured boot loader refuses to load the kernel and hangs. I don't see a solution by software here. Sorry.

You tried to install T-CHL7DEUC means your Modal is CI device. Does it really CI or CI+?
I don't aware if CI device have such an security check?
I am suspecting about installing wrong firmware. (CI instead of CI+)

Smartsmurf, does u-boot can't help here?
Doesn't it executed before loading linux kernel?
Could trying external firmware might be a solution?

From log code is see, you have used not the latest 0.3.2.2 version ( i renamed it to 0.4 due radical security improvements and re-uploaded to sourceforge) witch checks firmware version and type on usb matching to version on TV (from /mtd_rwarea/Version* file).

Very bad. I almost 100 percent sure you have CIP device and your firmware was T-CHLCIPDEUC.

FFB IS NOT FOR CI+...

n1ghty
Write your full model number with letters at the end.( eg LE46B650T2P ...)
Give us all log files (syslog.log, debug.log) to inspect...

If you have TV with original T-CHL7DEUC and it is CI+ then it`s really warning for us...
I can`t believe that TV with this fw is CI+. Here is an mistake by choosing firmware.
When TV has been bought?

Now about solution. Here is only one chance (very low chance)...
Try enter u-boot according wiki manual, but here is no 2 sec bootpause to enter bootloader menu in CI+...
But who knows, might you get success.
Use link to wiki from my signature.

I really think, TV is totally bricked, you need to call Service (TV is under warranty and it should be repaired)

Until latest version (updated on 7. feb 2011) FFB did not check for users fouls by choosing right firmware to their TV, it checked for supported fw version on USB, but 0.4 does.
TV won`t accept firmware on USB if firmware name differs in ID file on TV and USB. (i checked on my TV with a lot of firmwares with different "stupid" fouls.) That`s the main difference between this bugfix from 0.3.2 to 0.4. I`m a bit to late with this fix, we have a victim

I removed earlier versions from download from all sources, only 0.4 left (checked code, looks ok)

I think MakingDumps, inspecting log files is mandatory if you do not know is your device CI or CIP. We could add code to let user know what type of TV he has...