Big Block Or Small Block? Options

[pyro42]

long story short, my cousin bought a "jtag xbox" (turns out its actually a RGH >.<) and had it for a while, and just recently traded it to me. my cousin has a lot of n00b in him. so i'm going through trying to get everything up to date and configured correctly. and while trying to build a dashboad update with xebuild, i get this

CODE

***** WARNING: naddump.bin has a mixed controller LBA at block 0x30 (raw offset 0xc6000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x31 (raw offset 0xca200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3a6 (raw offset 0xf0cc00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3a7 (raw offset 0xf10e00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3a8 (raw offset 0xf15000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3a9 (raw offset 0xf19200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3aa (raw offset 0xf1d400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3ab (raw offset 0xf21600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3ac (raw offset 0xf25800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3ad (raw offset 0xf29a00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3ae (raw offset 0xf2dc00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3af (raw offset 0xf31e00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3b0 (raw offset 0xf36000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3b1 (raw offset 0xf3a200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3b2 (raw offset 0xf3e400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3b3 (raw offset 0xf42600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3b4 (raw offset 0xf46800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3b5 (raw offset 0xf4aa00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: naddump.bin has a mixed controller LBA at block 0x3de (raw offset 0xff3c00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!

so my guess is my cousin blindly followed some instructions at some point and flashed the wrong update. impressively enough, the system seems to work perfect, with the exception of the dvd drive reading all discs as video (could be unrelated) and no avatars. when i asked my cousin for the original nand dump, he said he had "the disc that came with it" but he's not sure where the disc is.

i've dumped the nand with xell and with flash360, and both give me the same errors in xebuild. the system does not show the internal flash MU like a big block is supposed to. the manufacture date is only one month after they started making v2, so that's not very helpful.


so is there any other way i can tell which board it is? if a jasper BB is flashed with a jasper SB nand, does it still show the extra MU?


is there something i could run that would try to dump more than 16mb of the flash? then if it errored out after 16mb, it would show it's a smallblock?

[pyro42]

i've also dumped the entire 20gb hard drive he included in case there was a backup there. no luck. (did find a nude of his ex GF as a theme.) apparently he will be home friday and should be able to get me the nand then. it just blows my mind there is no other way to tell which jasper it is.

[pyro42]

when i asked my cousin for the original nand dump, he said he had "the disc that came with it" but he's not sure where the disc is.

and he has still not found the disc. what's the worst that will happen if i flash the wrong jasper nand?

[vb_encryption_vb]

Open up flash360 and do a complete nand dump. Once you have the nand dump on usb put in pc and check file size.

512 = big block

256 = small black

16 = no internal memory

[pyro42]

Open up flash360 and do a complete nand dump. Once you have the nand dump on usb put in pc and check file size.

512 = big block

256 = small black

16 = no internal memory

perfect, thank you for that. i knew there had to be a stupidly simple way.