Creating Freebot from 70Mb NAND dump

[RedFarmer]

Following Martin C's advice of just dumping the first 70Mb from a 256Mb Jasper gives me problems.

http://www.team-xecuter.com/forums/showthread.php?t=65004

When I try to create a Freeboot image through JTAG Tool it tells me the image is of an incorrect size. I can kind of understand why it doesn't like the file-size, but how can I then create a Freeboot image from these kind of dumps?

 

[TilVl]

Cause it's not a full image.

Extract your KV and config. Use Jtag tool to download a full image. insert KV and config. Then make freeboot.

 

[keil423]

just dump the whole nand. It takes longer but I'm sure in your case you'll get better results. You should always have a full nand dump before writeing over it anyway. That is your fall back after all.

 

[Martin C]

Following Martin C's advice of just dumping the first 70Mb from a 256Mb Jasper gives me problems.

http://www.team-xecuter.com/forums/showthread.php?t=65004

When I try to create a Freeboot image through JTAG Tool it tells me the image is of an incorrect size. I can kind of understand why it doesn't like the file-size, but how can I then create a Freeboot image from these kind of dumps?

Don't use JTAG tool.

Download the Freeboot tool from bestpig.fr. Don't worry, the app is in english too. I did a 512MB Jasper from a 70MB image 2 days ago with no problems.

 

[RedFarmer]

Cool! Thanks!

I've used bestpigs tool once before when i was going to update another JTAG from 9199 to the 12611 dash.

I'm not sure, maybe i should start another thread but i made a full dump on this console (before i read what you mentioned about bestpigs tool) and got some bad blocks (i also got them when making 70Mb dumps).

As these were outside of the "critical area" and the dumps matched aswell as 250 errors probably is pretty common on big blocks i just went ahead writing Xell, getting CPU key, creating Freeboot and writing it back. I'm a bit unsure about error 210 though.

Now, when i start the console i get the boot anim and then it goes to E71 with secondary code 1013. I can however enter Xell by pushing eject on my DVD.

Examining the dump in Flash360 gives a kind of strange block remap. How come it redirects to 0x1FF? And, reading the NAND never gave me an error on block 0x0178 like mentioned below.

Hints?

Thanks!

 

[Martin C]

BB NANDs have a different bad block reservation:

http://www.free60.org/NAND:Bad_Blocks

 

[RedFarmer]

Aah! Perfect! I read it and I got it!

I had no luck with Bestpigs tool. That one also said the NAND-size was incorrect.

However, I remapped BC0 to FF8, BC1 to FF9 and so on and now it works! I was confused about big block consoles using larger block sizes and not just an increased number of 16k blocks. If a second bad block would pop up it would of course be another 8 16k blocks that would remap to FF0 and up.

Martin, you keep saving me and I keep learning. Added rep to you!

Thanks!

 

[Martin C]

..and I think I've just worked out why your NAND dump was the wrong size.

Why are you still using NANDPro 2.0b? Download 2.0d and try that instead

 

[RedFarmer]

Oh crap! LOL!

I actually have v2.0d but i read the NAND through JTAG Tool 3 which seem to include an older version. I will replace it with the new version

Follow-up questions. What would 2.0d do different in this case? Would it read the NAND in 132KB blocks instead of 16KB?

 

[Martin C]

I think it still supports big block NANDs, but is a better version.

http://www.xbox-scene.com/xbox360-tools/NandPro.php

I'm thinking that maybe the last time I did a 70MB dump I manually built using fbbuild - you only need a hacked JasperBB, decrypted kv and decrpyted smc-config.bin. Your 70MB dump is no longer required.