Removing R6T3: Is this necessary if you all-ready have your CPU key? Once the fuses blow you still have your CPU key so what is the reason? People with dual Nands?
Also does the latest freeboot with dash 9199 still blow the fuses? or does it workaround the fuse check?
Removing R6T3 (or bridging u6t1/u6t2) is a safety measure for accidental updating. If you update with R6T3 in place, you will burn a fuse and loose jtag possibilities. If R6T3 is removed it will not burn a fuse and you can still use the jtag hack.
Media updates: I watch a lot of films/ TV shows from external media. If i use a retail xbox to download the codecs on the same HDD will It be ok on the Jtag (id rather not connect to XBL atall). Does anyone know where they are stored on the HDD incase I get a different drive and just want to copy the codecs over?
Can't help you with this as I don't know.
Updates from game media: I'm still a bit confused about this. Do games only contain Avatar and Game updates, or do they also contain Dash updates? For example, next year, could I brick the console by allowing a new game to update to the new "Kinect" dash (assuming I haven't used a new freeboot)?
Same answer as to removing R6T3 applies. If you update with R6T3 removed you will be good (after reflashing). With R6T3 in place you will lose the hack, but your console will not be bricked as you could easily restore your nand backup with some adjustments as fuses will be burned.
HDD: Can a HDD/Avatar thats being used on a Jtag cause a retail console to get banned? Say for example I swap the HDD to play XBL on a stock console? and that HDD contains homebrew data such as emulators and Xexmenu? (I'll prob keep homebrew on an external usb memory anyway, just curious)
This might happen. However it is best to just keep jtag and retail separated.
USB flasher on 64-bit windows: I had windows in test mode, and after a lot of digging found what I thought were correct drivers for the flasher, but windows 7 still doesnt want to install them even in test mode (complains about signing), so I know im doing something wrong, ended up on different computer. Anyone know exactly what driver it is? Is there a signed driver available?
See answer from AD.