Whoot?
JTAG needed soldering as well :-)
And as you stated yourself: "You just flashed a NAND Image..." How would you flash it without soldering Wires? :-)
So after all... nonsense.....
the jtag exploit is the same exploit used in the kk exploit but patched into a nand image, not into a game iso, once the nand is flashed you no longer need to write it, you no longer need any wiring except some jumpers no extra logic, no extra active hardware, its a true softmod and easier than to rgh and why you have instant boot, rgh requires some discreet logic (external cpld- active hardware) to glitch the cpu at a very specific time to make it think its has pass the encryption check , when it really doesn't, then boots into your unsigned code to disable it, jtag bypasses this check directly by a bug in hyper visor itself, Microsoft has made jtag impossible with a system update(note that blowing cpu fuses actually changes the cpu hardware/logic and how it runs internally, which the jtag hack depended on pre-4552 dashes) .
either way microsoft has much time and experience in software development (since 1975, back when pong was the hottest console) the point is that you don't even regard the dash when jtagging or rgh since the exploits happen before the dash is launched, it exploits the hypervisor, which you can think like when windows used to use ms-dos before the NT kernel, windows was the frontend (aka your dashboard), but ms-dos is in the background actually calling the shots (360 hyper-visor), so you have two "oses" with one you never see since you don't have any reason to need to (hypervisor) and one your actual os (dashboard), this isn't a Nintendo console, these are essentially small form factor PC's, more expensive hardware, more R&D money. I think Nintendo purposely leaves their systems weak since they directly profit from console sales, and you'd likely have a spike in sales if you have cfw available (then patch once you buy it, hoping you lose cfw, and have to go back to gamestop until its rexploited), microsoft do not profit from direct console sales and don't really NEED to (xbox is not Microsoft's breadwinner anyway), they recoup losses through paying for their online services and software, thus having a console that is secure is more important for them since they don't make profit unless people buy services or games, the 360 entire boot/execution process is encrypted, and any software modification is watched by the hypervisor so anything not permitted (ANY unsigned/unencrypted code/data) will refuse to run since it breaks encryption and the chain of command, this is why nintendo console are easy as fuck to softmod since its encryption is not strong, and those console are built at a lower cost.
Microsoft will actually learn what hackers have done in the past and move forward with it, even with the xbox one if it was exploited you most likely could not do anything but run homebrew, and since the hypervisor is built into the hardware (360 was in software) i wouldn't be surprised if they put a flag that when unsigned code is executed, it flags your system and even if the console was made stock probably would ban you next time you log in, and could tell microsoft hey someone hacked it and they'll release a patch, since everything that happened on the 360 will not happen on xb1. makes me think if they waited on announcing the RGH until the one was released it may have been susceptible to that aswell, and since it wasn't Microsoft can figure out how it worked and patch it going forward, which is why alot of "exploit artists" don't release them immediately.