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

thesmj · « **Reply #15 on:** February 28, 2010, 12:54:00 PM »

Anybody have a working link for degraded? I can't seem to find it on xbins.

thwack · « **Reply #16 on:** February 28, 2010, 12:56:00 PM »

Yep - no pairing data or LDV values is very,very bad. Also the fact that you can't decrypt the kv etc and use this to at least try to mend the NAND leaves you with little choice sadly.

Personally - scrap the 360 and sell off the drive, case etc and put the money towards a new arcade (IMG:style_emoticons/default/sad.gif)

*ninja edit* Degradeds there- development.

This post has been edited by thwack: Feb 28 2010, 08:56 PM

Martinchris23 · « **Reply #17 on:** February 28, 2010, 01:46:00 PM »

QUOTE(thesmj @ Feb 28 2010, 07:54 PM)

Anybody have a working link for degraded? I can't seem to find it on xbins.

Ok - here's where you went wrong: You MUST run your NAND dump through Degraded before doing anything else with it. 360 Flash Dump Tool won't tell you if there's a bad block (relocated or not). There was a wiki page for Free60 and I personally updated it with instructions on using Degraded. If it makes you feel any better, I learned the hard way too and had to scrap a perfectly good 360 because the first guide I found didn't mention Degraded at all. You'll need to hexedit the NAND dump and change the 'Microsoft' part to '2004-2005' before you can open it with Degraded, but let me know what you actually get.

thesmj · « **Reply #18 on:** February 28, 2010, 11:08:00 PM »

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

Again, both dumps show the same data.

I'm really surprised both dumps have the same bad blocks. I would expect a problem with the cable or soldering to show up with random bad blocks/data, always different with each read.

Martinchris23 · « **Reply #19 on:** March 01, 2010, 01:27:00 PM »

No - that's fine. You have bad blocks but they been remapped so will not be the cause of the problem.

Open your NAND dump again with 360 Flash Dump Tool, but run the program as Administrator to see if it gives you anything more. You're seeing LDVs of 15 and 14 which is more like what I was expecting to see. I would say your dumps are fine according to Degraded.

If you want me to look at it, upload one of the dumps via transferbigfiles.com (RAR it up for CRC checking) and email me the link (email in my signature). I'll open it here and let you know.

xBang360x · « **Reply #20 on:** March 01, 2010, 03:12:00 PM »

Thats why I said to try and flash it again but instead use his 2nd dump as the 1st one seems to be the bad dump..It shows non matching blocks and not bad blocks..Always worth a last resort...

thesmj · « **Reply #21 on:** March 01, 2010, 03:21:00 PM »

QUOTE(xBang360x @ Mar 1 2010, 05:12 PM)

Thats why I said to try and flash it again but instead use his 2nd dump as the 1st one seems to be the bad dump..It shows non matching blocks and not bad blocks..Always worth a last resort...

Already tried that. Same result.

I'll post up the dumps tonight once I get home. Thanks for all the help guys!

EDIT: Just a thought - I'll try writing one of the dumps back on the box, and re-dumping it back to see how/if it changed. It could be a problem with writing the data back to the box, while it's reading fine.

This post has been edited by thesmj: Mar 1 2010, 11:24 PM

thesmj · « **Reply #22 on:** March 01, 2010, 08:26:00 PM »

Martin - sending the file now in .rar format. I'll try writing/reading the file off the xbox to see what I get.

Martinchris23 · « **Reply #23 on:** March 02, 2010, 12:29:00 AM »

Downloading them now - I'll let you know how I get on.

EDIT: The good news is there's nothing wrong with your dumps:

(IMG:http://img40.imageshack.us/img40/1545/nand2.jpg)

Must be your setup not reporting data correctly.

If it's not working after you write it back via LPT, reflashing via a USB SPI flasher should give you better results.

This post has been edited by Martinchris23: Mar 2 2010, 08:40 AM

thwack · « **Reply #24 on:** March 02, 2010, 04:00:00 AM »

Seems to be a write error then - you could try flashing it back in smaller chunks, reading back each one as you flash them and check them.

thesmj · « **Reply #25 on:** March 02, 2010, 11:28:00 AM »

Perhaps the problem is to much resistance con the cable? Is it that important to have the diode on the "motherboard" end of the cable and not the LPT end?

I'm using a 15-foot CAT5 cable, so the quality of the wire/connection should be ok. I could try less resistance on the cable by changing out the resistors, or I could move the diode closer to the motherboard if that really matters (which I doubt).

I wrote my whole nand dump to the xbox again, and then went and re-read it off to a new file. I havent' had the chance to compare the files yet but I plan to tonight.

Martinchris23 · « **Reply #26 on:** March 02, 2010, 11:30:00 AM »

QUOTE(thesmj @ Mar 2 2010, 06:28 PM)

I'm using a 15-foot CAT5 cable

WHAT!!!!

Are you serious? Your cable length should be less than 1m long. If you can, get it to 30cm. This is where you'll experience problems if your cable is this length.

thesmj · « **Reply #27 on:** March 02, 2010, 11:44:00 AM »

Heh, ok. I'll shorten it to a couple feet and let you know what happens.

xBang360x · « **Reply #28 on:** March 02, 2010, 03:43:00 PM »

QUOTE(thesmj @ Mar 2 2010, 01:44 PM)

Heh, ok. I'll shorten it to a couple feet and let you know what happens.

I would say that is your problem..I would dump it again after shorting the cable..My cable is about 7 inches

thesmj · « **Reply #29 on:** March 02, 2010, 04:00:00 PM »

QUOTE(xBang360x @ Mar 2 2010, 05:43 PM)

I would say that is your problem..I would dump it again after shorting the cable..My cable is about 7 inches

That's the plan.

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