tk_saturn

You're slipping Fast, he'll still need an LPT port to program the USB flasher. The only advantage is you can use a PCI expansion card based Printer Port to program the USB Flasher. However, there is a program which can change the ports which NandPro uses, i've no idea it that will allow it use a PCI expansion card Printer Port.


Quite normal. You can get motherboards with half blue half silver tops too. It's just where they source components from different manufacturers.

I have an old thread with a few MB photo's, and you can see it's normal http://gbatemp.net/t259392-2-xbox-360-jtag...de-2-jasper-pro

There is only one method of truely determining the motherboard revision, and that's by the SMC version. As it is, you clearly have an early Falcon motherboard which you can tell from the photo. On the underside of the motheboard, you'll likely find foam pads on the RAM.

You've seriously butchered those heatsinks though.



That's wrong, unless you've found a way to rehash type 2 Keyvaults.

Will never happen, Microsoft hasn't made the same mistake with their cryptography as Sony.

The person responsible for the KK/ JTAG hack, TMBInc is anti piracy. No one has yet to figure out how he got the 1BL key, he has said no interest in hacking it further.

No one with the necessary skills wants what you want. Because the JTAG hack was abused and people used it to host modded lobbies and cheat, it did a lot of harm to the XBOX and Live. There's a whole forum built around this, se7ensins. After now what's happened to the PS3, as an online console it's finished. All the cheaters and modders will all jump ship to the PS3, PSN will be full of 9 year olds running modded games and aimbots etc.

Presumably the discovery of the flaw in the cryptography was aided by the PS3 JB which have allowed hackers to learn a lot more about the inner workings of the console. The JTAG hack has been around in it's previous form since 2007, and they have much more access to the XBOX than the JB allowed on the PS3. So if it was going to happen it would have by now.

The JTAG hack is perfect. They have full access to the console and hypervisor, you can pretty much do what you want with the console. The JTAG hack was patched by Microsoft before it was even released; as the hack was announced on the day it was patched it's suspected that TMBinc gave MS knowledge of the hack before it was released. There are enough JTAG consoles around for those who want them, but not enough for it to go mainsteam. So Microsoft doesn't go out of their way to block them from playing the lastest games etc, they seem content that they've patched the JTAG exploit. Instead they are far more concerned with DVD backups.

There is no one cause of the E74 RROD. It's been suggested that MS used a brittle type of lead free solder which breaks under extreme heat and the associated expansion/ contraction, it's also been suggested the X-Clamps can warp the motherboard under extreme heat from the metal casing not being perfectly flat. Both of those will only be an issue if there's excessive heat, which is common on the first revision console.

It's known the E74 RROD issues cost Microsoft over $1 billion in repair/ replacement bills. Any issues with solder would have been quickly fixed as it would have saved them $$$ in repair bills. As for the X-Clamps, they were still being used on the RROD free Jaspers and are still used on the Slim's. So I really doubt the X-Clamps were the cause of the issues. On a first generation console the CPU tends to run as hot or hotter than the GPU, the CPU uses the same solder/ X-Clamps yet doesn't suffer from failure.

XBOX360 consoles can be very reluctant to speed up their fans to keep the noise down, by default they run at 40%. An original XBOX360 console doesn't increase the fan speeds until the GPU reaches ~083°C, and won't shutoff from overheating until the GPU reaches 110°C or the ED-RAM reaches 117°C. It is possible even on a retail console to change these temperatures at which the console will increase the fan speeds, it's been suggested that if you keep the GPU under 60°C it should be relatively safe from E74 RROD/ GPU Failure particularly if this was done from early in the consoles lifespan.

The second revision of XBOX360 included an additional heatsink on the GPU to reduce the temperatures, however dust is still a severe problem. It's not so much the dust on fans which is an issue, dust clogs up the fins on the heatsinks which prevents them from moving air. On a 3 year old console which has seen a fair amount of use, this will be effecting the temperatures enough for it to massively increase the chance of E74 RROD.. You need to strip the console down and get the hoover out to remove the dust, compressed air wont help and if anything could make it worse.

Then there's the other big issue, the GPU's were fabbed by TMSC. TMSC were responable for Nvidia's GPU Failures, and it's believed this same issue effects the XBOX360's GPU from the same period. It's known that many GPU's on consoles which E74 RROD are done for, reballing/ reflowing/ towel trick doesn't always work. many people believe this to be the true cause of the RROD issues.

Then you have the 3rd issue, underneath the GPU heatsink is not only a GPU but also the ED-RAM both of which generate heat. It's known that in some cases there can be a slight height difference between the dies, and thanks to poor/ poorly applied thermal paste the ED-RAM runs hot. By simply replacing the thermal compound, i've had a console (3 years old) which saw a drop of 8°C on the GPU, and 21°C on the ED-RAM (fans @ 100%). I've also noticed the thermal compound they use sees a slighlt dropoff on consoles which are 3+ years old

Jaspers, The last revision of the old style console is known to be pretty much free of the E74 RROD issues.

"Retail consoles which came with 2.0.7371.0 have the CB/CD patched and are not JTAG'able" I'm certain of that, I have a JTAG from 19-06-2009 Lot 0925x, and even that had 2.0.7363. I've also had 2 consoles from Lot 0924x along with 3 from 0923x and likewise all had 2.0.7363.

If you had a console which originally shipped with dashboard version 2.0.7363 or earlier (and manufactured before the cut off point), then updating those to 2.0.7371.0 wouldn't effect wether or not they are JTAG'able. But if they came from the factory with 2.0.7371, the CB/CD would have been patched preventing it from running the 4532 kernel.