Big Block Jasper 256 and 512 Partial Dumps

[glaze83]

Noticed the xbr is only 1000 blocks long for these so I dumped  0 - 1000, patched the info into xbr, wrote it, and all is well.

Is there anything important I"m missing just dumping the first 1000 blocks? Is there a flashtool that opens it?

[scan]

just for clarify:
xbr for large block jasper is 1600 blocks (0x0000-0x0FFF)
so we can only dump first 64mb using command nandpro lpt: -w512 mydump.bin 0 0x1000

greetz,
scan

[l_oliveira]

Just to add to the injury...

Nandpro still saves the data it dumps from the 360 flash on small block format, even if it came from a large block flash chip.

So please DON'T try to flash back NANDPRO dumps with the infectus

[eyric101]

I take it there is no way to convert to large block format?  And is that the behavior of 2a and 2b?

[Goukihosi]

Not 100% on topic but I got 3 good reads from my 512MB Samsung using Infectus2
using the Infectus Programmer 3.9.9.0 After that I erased the nand, opened the
256/512 Xell .bin and tried to flash it but got 'Write Failed' and the nand was
not recognized anymore. After that, the Bad Flash recovery-method did the trick
and the nand was recognized again but I still got write failed and blankcheck failed
after erase. Turning verify off enabled writing but when the entire nand was flashed
the Xbox won't turn on anymore.

Any solutions as how to get this Xbox working again? Flash using lpt perhaps?

Regards, Gouki

[Arakon]

yep, that'll be the best bet.

[sasoseso]

tried to flash it but got 'Write Failed' and the nand was
not recognized anymore.
Regards, Gouki

try to disable write verify in infectus programmer setting

[Goukihosi]

Write verify enabled readnig to the nand once I used the bad flash recovery-trick.
But, no reaction whatsoever from the Xbox when trying to turn it on.

I just flashed using Infectus NAND Flasher 1.03 and the moment I plugged in
the powercable the Xbox's center led kept blinking but once I unplugged it
and put it back in it was dead again.

Opening the 528MB dump made by Infectus Programmer 3.9.9.0 in NAND Flasher
for checking yielded no errors and the image starts also with 2004 - 2008 Microsoft yadayada..

I'm far from a hacker but is it possible the dump is invalid or would parallel flashing be
a solution? Or, does anyone have another suggestion?

[bill16504]

I've been trying to dump a 512 nand with no success. The best dump, nandpro read up in to the 5000's but then I'll get the 0 reading error. Other attempts result in the 0 reading error, all at random locations. I'm using nandpro20b, command nandpro lpt: -r512 orig.bin . This isn't my first console. I've dumped/written a few others without a hitch. But this is my first 512. The others were all 16's.

So now I searching and I'm finding that you guys are saying I only need to dump the first 64 megs to use with xbr. So if this is in fact safe, would my commands be

-r64 orig.bin
-w64 xbr.bin

Sorry if this seems pretty simple minded. I'm good at following guides and good at researching, but I'm not too educated with hex, locations, etc.

[Gazcoigne]

command would be

-r512 orig.bin 0 1000

-w512 xbr.bin 0 1000

where first number is start offset zero and second number is end offset in blocks AFAIK its 1000 for 512 if i'm wrong then some1 will correct it.

[modslave]

Nobody in this thread has mentioned reading through Gentoo so thought i'd mention many people have had success this way myself included.
I only had to read the 1st 2mb over lpt then flash xell, boot gentoo and read nand straight to usb in about 1min.
Found it worked better with older version of usb drive and was also more reliable than lpt.