E73 and E74 means that the smaller die on the GPU part are faulty (EDRAM).

Sometimes reballing solves that issue because the cracked balls are the ones which supply the EDRAM die with power. But the two dies are attached to the GPU substrate with (can you guess ?) solder balls again. Then it's sealed with some special epoxy which is heat resistant...

If the balls broken aren't the ones that connect the mother board to the GPU body, then it's the balls that connect the dies to the GPU body. And the overheating the GPU is exposed to under normal operation does stress it in a whole, not just the connections to the motherboard.

Hence why it's aways best to replace the GPU with a new part. But yes that's an extra cost not everyone are willing to pay.

No we aren't.

If you had the GPUs replaced at first the units would be still working. Make sure they put new parts.

And man, it's only fair that you pay again, because you opened them.

It's not freeboot what prevents you from modding the keyvault. All consoles after the Zephyr have their keyvaults hashed and signed with cpu key to prevent "unbans" and region changing.  ver .30 had that patched out but that code caused profile corruption.

Anyway, besides region changing tinkering with the KV brings nothing good as mostly people will use it to do bad stuff on live.
Eventually MS may start to ban accounts instead of consoles (In case of JTAG consoles) if people abuse too much.

http://www.xboxhacker.org/index.php?topic=15059.msg110427#msg110427

As certain things can cause the system to not report errors and sit idle, I'd like to point you would like to know that.
Read that post with attention and you will understand what I mean. It might look like it has nothing to do with your problem, but it actually does if you're dealing with an non hacked system.

If you can get an 1st batch Halo ODST disc, it comes with 7371 dash. Update with that.

I think I remember comments about the boot loaders being hashed with the CPU key after an certain version (Zephyr or Falcon) in combination to the original 1BL key (that for 100% retail/legit non tampered images.)

So I suppose fixing that without the CPU key would be a bit ... hairy ...

I have an Jasper here which is with the same problem as yours (0022 after a few seconds) but because of remembering reading this bit about the CB/CE being hashed with CPU key I never  thought of putting an donor CB/CE in it.

Why you don't try getting FreeBoot 0.32, all the support files for Jasper and then with an arbitrary CPU key value generate an *ORIGINAL* dump ? You could then try that on your system.

I have an 8955 Xenon here I happen to know the CPU key and I had images made with freeboot (9199) work in it correctly.

Non non non.

I bet you have a unit which the cover does not match the chassis /motherboard....  Check the system information screen and see if the S/N match with the chassis sticker (close to the frontal USB ports) and the external Case sticker with the barcode.

Yes... Try to reflow it and after that, if it works, put an massive heatsink on the GPU.

Then, move the DVD drive to outside and be happy.

The guy might want to keep the MU as it is, you know... That kind of stuff has "colectible" value even.

4 years ago some SONY employee forgot a memory stick loaded with recovery software into a customer's PSP.

Back then who would suspect that an modified battery were used to make the PSP boot from the memory stick slot ?

Also, the memory stick contents were destroyed because people thought that dumping the files would be enough.

To read the MU on the PC he could download Datel's XPORT360 software, which includes an usable driver for the MU.

The board is too damaged for the system to stay stable for a long while.
I suggest a thermal mod like this for you to attempt:

Outside:


Inside:


That (or a similar mod) should extend the life of your system for a little bit.

100% fault free method:

Insert disc
Install disc
Run NXE2GOD
Voila.


Why would you need to FTP an iso to the console it you have the disc stored somewhere ?    (lol)

Now, seriously, back to the FTP issues... It would be useful that everyone posted which FTP software they use on the PC side.

An MU reader is something super simple, really.
I picked up an dead xenon motherboard, took the MU slot from it, split in 2 parts and from that I made 2 cables:




To convert 5v to 3.3v I used:


The other 3 wires go straight.

Dump might be corrupted ... 

Have the JTAG port install checked. Sometimes adding a diode from pin 4 to pin 7 instead of a jumper helps to alleviate the issues with the JTAG operation.
The diode is connected with the cathode (side with a painted stripe in) facing the pin 4 direction. 

This for sure reduces the random 3RL issues with 0020 in a few Falcons.

By now this sabrax guy is probably receiving some nice and beautiful Cease and Desist letter from Microsoft... 

This is not the first time production/service software leaked. Neither will be the last.

Usually, BAD KEY = WRONG CPU KEY.

Flash the XELL hack in it and grab your CPU fuses dump (it shows on the screen or if you use XELLOUS it will be saved as txt in a pendrive you plug in) so you can get the CPU key from that.

If you're absolutely sure your CPU key is correct, you have an corrupted keyvault. And then you have an reason to be worried.

I don't understand why you guys mention that XBR is less buggy than freeboot. In fact XBR was a quick fix for the 2 nands problem but seriously, XBR is just a ugly hack to make  an ready made generic flash image usable on all consoles.

It has more bugs than freeboot due to requiring more patches (freeboot uses an custom tailored image for each keyvault/security files/cpu combo thus requiring less patches made to the kernel).
It could be that your security files are somehow damaged causing your console to behave oddly.

Have you tried using donor files yet ?

Ibuild complains about corruption within the file 360flashtool extract fine but I believe the file output by it is still encrypted with the original console HMAC(CPU-KEY), not ?


We can get that easily here. If needed I can even make a machine here from 1888 and then update to the needed kernel so we can obtain the file (dash.xex)

Which tool one use for this job ?  I have tested ibuild but it complains about files being wrong (it only works for the version it was made for, not ?)
Is there a generic tool to build an arbitrary kernel version nand ?

No issue.


I suggested that to TmEE but then we would still like to pursue an solution for this.