The newer dash updates blow the e-fuses, which are required for the Jtag hack.
From all news so far, it is incredibly unlikely that we will be able to perform something like the Jtag on newer consoles, as well as simpler solutions being ruled out entirely.
From all news so far, it is incredibly unlikely that we will be able to perform something like the Jtag on newer consoles, as well as simpler solutions being ruled out entirely.
just because its "All Version Motherboards" doesnt mean its all DASHBOARD revisions... and most likely it is not.
as far as i remember, its the new nand dumper from team xecutor... that it.
as far as i remember, its the new nand dumper from team xecutor... that it.
What good it would be? It's to assist those who do have exploitable motherboards. Motherboard is not the same as dashboard or CB version.dsrules said:
all motherboards has different dashboard revisions, some are JTAGable some are not
and this says it's a JTAG solution for all motherboards
well, just 2 more weeks before it's out, just wait and see
and this says it's a JTAG solution for all motherboards
well, just 2 more weeks before it's out, just wait and see
I do not doubt it is a JTAG chip for all boards (they probably just vary where you throw wires) but the trouble is that the CPU has efuses in it which can be burned by software- with enough you can make a number that can be read and as such disallow old software* (why we can not JTAG every system).
*physically you can downgrade all day long and nothing would happen, as soon as you try to boot though it would lock up when it detects the old version running.
To this end we need a new exploit (unlikely- the security model means it can only come from a limited amount of places and MS has done a reasonable job at locking them down), a way to bypass efuses (what people are largely focussing on with low voltage glitching and superclocking), the crypto to be broken (given it is stuff used worldwide every day but many different things to the 360 this is extremely doubtful) or for the keys to be leaked/divined (not likely- MS knows well what would happen then and probably locks them down tight)
*physically you can downgrade all day long and nothing would happen, as soon as you try to boot though it would lock up when it detects the old version running.
To this end we need a new exploit (unlikely- the security model means it can only come from a limited amount of places and MS has done a reasonable job at locking them down), a way to bypass efuses (what people are largely focussing on with low voltage glitching and superclocking), the crypto to be broken (given it is stuff used worldwide every day but many different things to the 360 this is extremely doubtful) or for the keys to be leaked/divined (not likely- MS knows well what would happen then and probably locks them down tight)
Similar threads
