You can post the images here if the pictures they have in the thread don't seem to describe your problem.

Have you checked the LPT adress?

First try another pc, preferably an older one like a Pentium3 with XP.

If the above isn't an option try to measure the voltage between VCC and GND

Yes the chip could be damaged by static electricity(not that likely) or wrong connections earlyer, but there are a lot of reasons it wouldn't work so you have to check that first.

It won't win any prizes but the connections look pretty good.

If you look in the bios of the pc how is the LPT port configured?

Are you using a laptop or a PC?, can you try another pc?
If not can you measure the voltage over VCC and GND?
 

Sometimes you look to hard...and you cannot see it.

Could you make a picture of the backside of the programing pcb amd the lpt connector?

if you damage something just make a picture of it and it will be a lot easyer to help.

Pics of the cable?
Some info on the pc? (e.g. win7)

It's really hard to see on the picture if you scraped away to much(you should only scrape away the thin green laquer layer so that the copper is exposed)

If you didn't remove to much copper before soldering the drive is dead and you need a replacement drive/pcb(Printed Circuit Board), a clear indication of a dead drive is when the big chip on the PCB gets hot.

You can easely check your soldering using a Multimeter.

I hope you have the original DVDkey/bin

Did you use the original Xclamps or screws?

Sadely you need a new drive, or possibly a new pcb if you can get your hands on it (no gurantee tho)

What kind of sata controller are you using?
(Via perhaps?)

Maby i missed something but if you do the following wat will go wrong?:

1. Decrypt donor Falcon KV with donor CPU key.
2. Reëncrypt donor KV with actual CPU key.
3. Build Freeboot with actual CPU key.
3. Flash DVD drive with DVD key from donor KV and spoof OSIG.
(does Xelous spoof the dvd key?, if not you really should flash the drive)

Are you using the latest Dashlaunch?, try to rename the dashlaunch ini file on the HDD to see if the same problem happens.

Why would you try to change the dvd key?, thats probably the problem as you cannot change anything in the newer keyvaults!!!

Questions:
1. Lets get this sorted: If i understand the start topic correctly you want to update to the latest hacked freeboot dash, correct?(Maby you could change the topic name)
2. Do you have bad blocks in the nand?, where?
3. How are you flashing?, e.g. Nandpro LPT/USB, Xellous, Linux
4. If you flash back the 9199 version does the xbox work correctly?
5. How did you extract the files from the 9199 bin?, if 360 toolbox, did you change the settings and use the files from the ibuild directorys?
6. What kind of xbox are we talking about? e.g. Xenon
7. Did you remove the power after flashing?
8. If you flash again try to wait until you get an error, give it a minute or 4.
Answers:
The only parts of your original nand are located inside the Freeboot 9199 image, you can see those files as settings files and certificates, it isn't possible to recreate missing files but they can be replaced with working files for Freeboot.

Extracting files from the 9199 image, building a non hacked image with those and then extracting the files from that file will probably give you exactly the same files.

Xboxbreaker: With a non hacked SMC it should give you an error, looks more like a bad block or a bad keyvault(wrong extraction?)

If i understand you and the latest Freeboot readme correctly: 
Your old freeboot 9199 you are using now is probably the easyest way to get the files you need, it has most/all things you need.

As DDXCB stated KV, SMC, and SMC_Config and the new dash files are enough to build the newest Freeboot, you should be able to get those from the image you are trying to update(the 9199 you dumped a couple of times and checked), no reason at all to build an original or 9199 image.

You can use 360 flash tool 0.97 to extract all the needed files from your existing 9199 image, but dont forget to mark "Extract Ibuild compatible files" under settings - options and insert your CPU key under settings - keys before you do that.

The new dash files are floating around somwhere, probably somewhere near where you found the new Freeboot version. 

Fbbuild will substitute most needed files for you so that will not be a problem.

After that just follow the Freeboot readme and ask if you run into trouble.

U R right(I always use Hearders) but i really do not think the topic starter should try something like that...

Bozo pl: Good catch, but to small to be a problem, TS should remove it and make sure it doesn't happen again.

Hint:

You are not supposed to see any blank wire, and electrical tape......never use it!!!, i mean it!!

You can pick up some heat shrink tube at your local electronics supply shop, should make it a lot safer for the xbox.

Ok, seems i didn't catch some stuff when i had my sabbatical 
Thanks for the info.

Edit: fryc88 seemed to have figured out the problem, deleted my reply.

Cory: Why are you remapping to 3E0?, i always thought remapping started at 3FF backwards

 
Try to replicate it the way i did and do a compare..

If others want to try this maby we should make a different thread for this.