Topic: Wrote Bad Data To The Eeprom, Now What? (Read 526 times)

thesmj · « **on:** February 22, 2010, 06:01:00 PM »

In an effort to get my HDD's usefulness back after the august update, I followed the tutorial on getting the eeprom image off the xbox using the LPT port. Everything went fine. I copied the file off twice, and although there was one differing block between the two reads, I moved along with the hack thinking the mismatched data was in one of the backup kernels (which was stupid). The applications I used to read the image(s) had no problems with either file, so I figured I was in the clear.

After trying to get the HDD working again unsuccessfully a couple of times, I tried to "restart" the procedure by writing one of the originally read images back to the xbox. Now, I have a box which fails to boot at all - I get a red ring about 30 seconds after booting up the box, nothing on the screen.

Given that the two image files I read were so close (again, only a sector was different between the two) the cable itself must be fine, otherwise the image files would be filled with garbage. I figure if I had a known correct image I could simply place my CPU key etc into that and write it back to the board, resolving the issue.

Is this a sound plan? Is there anything else I should try first to fix the issue?

vb_encryption_vb · « **Reply #1 on:** February 22, 2010, 06:48:00 PM »

You should have dumped till you had no difference's....now your hating it and have a nice paper weight....

dharrison · « **Reply #2 on:** February 22, 2010, 09:22:00 PM »

It's really hard to give people advice when they are descriptive about what they do when they get an error, but don't give any information about the error itself.

I'll try to assist you the best I can from what you've said so far...

For one, if you are receiving 3 red lights, then yes, you will not have video output. You will only receive an error code on screen should you receive 1 red light. In order to determine your exact problem, you should try to retrieve your console's secondary error code, whilst it is red lighting. Google 'how to retrieve XBOX 360 secondary error code' and follow the steps.

But..

From just judging the fact that your console red lights after 30 seconds, I would almost guarantee that your console has a short somewhere. Check around your wiring and make sure you don't have any solder splashes or bridged points anywhere. If you are trying to boot your console with the cable attached, then remove it and try again. Blowing air over your console to remove metal shavings and loose wires can also help.

The reason I say this is because if it were a problem with the NAND, 99% of the time, the console will still boot even if the NAND is written with bad blocks on it. You would notice if it were a bad block problem, because it would do things like boot the opening animation and freeze, boot but some features won't work, or give you an E number error code on screen. Also, in some cases, you can receive red lights alternating with green lights, if the NAND is configured incorrectly.

So, try getting your secondary error code and go from there. Then, go to http://forums.xbox-scene.com/index.php?showtopic=484726 and figure out what your problem may be. Post your results here again if you need further assistance.

thesmj · « **Reply #3 on:** February 22, 2010, 09:34:00 PM »

Thanks dharrison. I'll get the secondary error code tomorrow. This is the first I've ever heard of such a thing so forgive me for not getting it already.

I doubt there is a short, since the box worked fine right up until I tried flashing the eeprom one last time. I'll check again through just to be sure.

thwack · « **Reply #4 on:** February 23, 2010, 04:30:00 AM »

Definitely check for shorts on the board. Also, if you dumped the NAND twice and there were errors, you can pretty much guarantee that when you try to write to the NAND you're also going to encounter write errors. If you're only writing small blocks back to the NAND (ie uncrippling) then you're less likely to get errors.

Did you check (assming you have a 16mb NAND) your dumps in Degraded? Also, there is a tool which will rebuild your NAND from a minimum of two dumps: NandCompare.

I would suggest:

1. Check your board for shorts.
2. Re-check your LPT wiring (are you using resistors/switching diode?). Also, don't do anything on the PC whilst it is dumping - this can cause errors.
3. Check your original dumps in Degraded - if the errors a re-alocated to the end of the NAND (ie block 0FE found @ 0x03FF) then this is normal. If not use NandCompare, and then check the result in Degraded for errors.
4. If you get a good dump from NandCompare, I suggest you should try to dump a couple more times from your bad NAND, and compare these - then at least if the files are identical you know you'll be able to write back to the NAND without error.

As a general rule of thumb (and this isn't 100% accurate) if you recieve a 0102 error code after flashing it's the standard RLOD, which x-clamp replacement/reflow/reball will cure. This is not related to the NAND flash. Any other error codes are a different matter.

Martinchris23 · « **Reply #5 on:** February 23, 2010, 07:17:00 AM »

From experience, the 30 second RRoD is normally caused by corruption in the CB/CD/LDV. Open the dump in 360 Flash Tool and check out the LDV values. Attach a screenshot if you can.

thesmj · « **Reply #6 on:** February 23, 2010, 10:15:00 PM »

QUOTE(Martinchris23 @ Feb 23 2010, 09:17 AM)

From experience, the 30 second RRoD is normally caused by corruption in the CB/CD/LDV. Open the dump in 360 Flash Tool and check out the LDV values. Attach a screenshot if you can.

Here's what I got. I checked both dumps, and they both had the same values.

(IMG:http://i780.photobucket.com/albums/yy86/thesmj/Untitled.jpg)

vb_encryption_vb · « **Reply #7 on:** February 23, 2010, 10:25:00 PM »

Non-Exploitable CB Versions (CD = 8453 for all of them)
Xenon: 1922, 1923, 1940
Zephyr: 4571, 4572, 4578, 4579
Falcon/Opus: 5771
Jasper: 6750

Nevermind your trying to get HD capabilities back not a JTAG.

This post has been edited by vb_encryption_vb: Feb 24 2010, 06:28 AM

Martinchris23 · « **Reply #8 on:** February 24, 2010, 06:47:00 AM »

QUOTE(thesmj @ Feb 24 2010, 05:15 AM)

Here's what I got. I checked both dumps, and they both had the same values.

IPB Image

Yep, there's definitely an issue there. You're on 8955 so there's no way your LDV should be 0 for all three values. Not only that, but you should have pairing data too.

Unless you have a valid dump which shows you what values these should be at, I can't see any way forward. If it was exploitable still, you might have been able to downgrade but that's out of the question.

thesmj · « **Reply #9 on:** February 27, 2010, 02:43:00 PM »

Here's my Nandcompare results. Since I don't have a 3rd dump I can't fix it.

(IMG:http://i780.photobucket.com/albums/yy86/thesmj/untitled2.jpg)

As you can see, there is only one non-matching block. This must have been an important block.

As for the secondary error code, I get a 0022 error, which based on my reading is a GPU error.

Is there anything else I can try? With the prices on new Arcade boxes being so low right now I'm tempted to just get a new one and scrap this for parts, but I'd feel like even more of a fool if I didn't try everything possible to repair this box first.

vb_encryption_vb · « **Reply #10 on:** February 27, 2010, 03:16:00 PM »

You at the end of the line....If you had that third dump (there is a reason we say get 3 dumps) you could have reconstructed the nand and possibly been fine. Like you said scrap this one for parts, well the dvd drive is good anyways, and get yourself an arcade.

thesmj · « **Reply #11 on:** February 27, 2010, 07:09:00 PM »

What if I were to take someone else's dump, take the block from it that mine has missing/damaged, and place the data into mine?

xBang360x · « **Reply #12 on:** February 28, 2010, 06:48:00 AM »

Have you at least tried to flash both dumps back to it and see if it works with one or the other...Maybe the one dump is bad and the other is fine...Worth a try before you make it a paper weight ...

vb_encryption_vb · « **Reply #13 on:** February 28, 2010, 07:42:00 AM »

QUOTE(thesmj @ Feb 27 2010, 09:09 PM)

What if I were to take someone else's dump, take the block from it that mine has missing/damaged, and place the data into mine?

No.

QUOTE(xBang360x @ Feb 28 2010, 08:48 AM)

Have you at least tried to flash both dumps back to it and see if it works with one or the other...Maybe the one dump is bad and the other is fine...Worth a try before you make it a paper weight ...

Try what this guy said.

Martinchris23 · « **Reply #14 on:** February 28, 2010, 12:20:00 PM »

QUOTE(xBang360x @ Feb 28 2010, 01:48 PM)

Have you at least tried to flash both dumps back to it and see if it works with one or the other...Maybe the one dump is bad and the other is fine...Worth a try before you make it a paper weight ...

The fact he's got LDVs of 0 and no pairing data in the NAND means neither would work. You could patch the NAND with the write data but you would need to know what it was.

QUOTE(thesmj @ Feb 28 2010, 02:09 AM)

What if I were to take someone else's dump, take the block from it that mine has missing/damaged, and place the data into mine?

You didn't say what information you saw when you opened them with Degraded.

Author Topic: Wrote Bad Data To The Eeprom, Now What? (Read 526 times)