Print

[SHADOWSTRIKE1]

Hey, running into yet another problem.  So I got my Xenon's nand read.  The first .bin started getting errors from 1F1 all the way to the end, but my next 2 .bins were read just fine.  I opened up my nand2.bin and my nand3.bin in Total Commander, and it said they were identical.  So then I tried to open it up in Degraded 1.1, but then it just says "Couldn't read file"

I tried to open up the nand2.bin in 2 separate hex editors (HxD and Hex Comparison), and I cant find the 2004-2007 anywhere.  For that matter, all of my readouts look like this-

0x0000000 0002 0000 0002 0000 0002 0000 0002 0000 ................
0x0000010 0002 0000 0002 0000 0002 0000 0002 0000 ................
0x0000020 0002 0000 0002 0000 0002 0000 0002 0000 ................
0x0000030 0002 0000 0002 0000 0002 0000 0002 0000 ................
0x0000040 0002 0000 0002 0000 0002 0000 0002 0000 ................
0x0000050 0002 0000 0002 0000 0002 0000 0002 0000 ................
etc

It goes like that all the way through the file.  Did I get 2 bad nand dumps?

[p4r0l3]

Do you have a big block nand? I'm not sure degraded supports them

[SHADOWSTRIKE1]

I'm not sure what that means. My NAND came out to be like 1650 kb or something like that in size if that helps.

[SHADOWSTRIKE1]

Sorry for double post, there's no edit button.

Upon further research, I guess I discovered that Xbox's with internal memory are "big block nand".  

My Xbox is a November 2005 Xenon with no HDMI port and no internal memory, so that would be a nope.

It's just... I dont really know much about hex, but I think I do know that something is wrong if every single line of code is-

0002 0000 0002 0000 0002 0000

Could my diodes be bad?  They are faced correctly, I do know that.  I just don't know what could be wrong.  Perhaps if I changed the start value of the port95 to 1 instead of 2, would that do anything?