I just wanted to clarify that these 2 images do the same thing and they are just alternative soldering points for the Jasper motherboard. If there is no difference which one you do, I may go with the one where I dont need to completely take out my motherboard.





P.S. I have done 3 full dumps of my 512MB through lpt and have been reading and reading while its been dumping to make sure I do everything correct. I had 3 error 250's when dumping, here is my log:



When comparing these through Hex Workshop, they are pretty close but not identical. When comparing through Nand Compare v1.2 it says "1 non-matching block(s) found D44". I tried dumping D44 by using "nandpro lpt: -w512 d44.bin D44 1" and did that 3 times then compared them and they all matched, so I wrote them to the nand.bin and nand2.bin and compared again in Nand Compare, but it still said the same thing about D44.

I have dumped the first 70 MB through lpt and also dumped the first 70 MB from one of the full nand dumps and compared those which were identical so I am not sure what else I can do to get 2 identical full 512 MB dumps or if I am safe with what I have.

I'm not an expert on this since I've only done my Xenon, but I'm pretty sure that I read that those are alternative points. Someone else can chime in to correct me if I'm wrong. As for getting identical dumps, you can try following vintage_guitar's tutorial here to dump your NAND through gentoo/lflash. It's both the fastest and most reliable way to dump your NAND. The link doesn't seem to work correctly, but it's post #60.

you need to take out the motherboard whether your using the point on the rf board or the point on the rfboard connector (bottom of the motherboard).



i use this one

Turns out I was using Nand Compare v1.2 which did not give the correct hex value for bad dumps on big block jaspers. I updated to v1.3 and gave a different hex value for the bad block. I re-dumped it 3 times and compared them, then added this to my nand.bin and nand2.bin both full 512MB dumps and they were then identical.

I proceeded with the 2nd image in my post and soldered to that point, wrote the xbr, wrote the kv and config then booted the xbox and it started perfectly. turned it on with the windows button on my remote and got my CPU key and DVD key. Now to try and figure out what I can do from here

Thanks everyone

Hey guys, I'm on my third jasper 512 Nand dump and I'm getting an error 250 on block 6d8 with all three full dumps in nandpro. That's the only read error I get. My question is...what do I do next?

I can't open the bin in any of the available apps because it appears that it isn't supported. Should I dump 70megs of the bin, then try to open that up in one of the tools? I believe block 6d8 is in the first 1000 blocks.

Should I try to remap that block? Each time I re-read it, even just the block itself, it still gives me an error 250. I really want a pristine NAND dump with no read errors, how would I go about getting that to happen? Please let me know, thanks all!

Some NANDs just have bad blocks and I don't think theres anything you can do about it.

Out of the 5 systems I have done so far 2 came back with 1 bad block that I couldn't read, write, or erase.

Just use bad block remapper and you are good to go. Even though your NAND has bad blocks you can still put the original flash back on and it will be fine because the blocks are bad no matter what.

I have tried it before and it has worked.

The block remapper tool is part of nandpro? Is it a seperate util I can grab from the "usual places?" If so, remember what it's called? lol

dear god full 512 through LPT. You can just dump first 64megs with large block NANDS.
XBR is 1000 blocks, so thats all you need for restoration purposes.

nandpro lpt: -r64 nand.bin

what I always do, once you get that

nandpro nand.bin: -r64 rkv.bin 1 1

nandpro nand.bin: -r64 cfg.bin EF7 2

then;

nandpro lpt: -w512/256 xbr.bin

will only write the size of XBR so 1000 blocks. Saves alot of time
without a USB setup

What if you have a bad block in the first 1000 blocks though? What's the bad block remapper tool called?

im pretty sure all the bad blocks are pushed to the end. but dont take my word for it

I have a bad blocks problem too, ill start another thread for it since its not on the subject.

this is very interesting. in have a 512 nand and and it's taking eons to dump my nand.

can anyone confirm that this works? and why, until now, they havent update the guide in dumping large blocks?

need your thoughts..

Most people cant edit posts, so the Tuts wont get updated. But there are a dozen Tuts out, some with the info that you can do it like that.
Id read the kv / cfg straight from the nand a couple of times untill they match, since you have the lpt cable attached anyway and it only takes a few secs.

i see.

since i dont think im going back to the original.. can i just do what u did?

dump the kv & cfg a couple of times.. then compare it.. then inject it on the downloaded xbr?

Make a backup of the first 64mb too.
The only problem with this method is:
If you have bad blocks at either 1 or EF7 you will be f**ked.
I always make a full backup (with a usb flasher)

hmnn.. i did dumped my nand once (completely) and there is no bad blocks.

am i good to go with this process?