Print

[oper8r00]

Most likely JTAG-able. Just dump the NAND and check the CB version

Exploitable CB versions:
1888, 1902, 1903, 1920,1921: exploitable xenon

[brandogg]

If it hasn't been repaired by Microsoft since June 2009, then it's 100% JTAG'able. The only way you get unexploitable CB values is from repaired consoles or new consoles with 7371 made after June 2009.

[snnorlaxx]

So, tagged the box and dumped the nand, read it in degraded:

CB version 1888  LDV 0
CD version 1888
CE version 1888
CF(0)         7363 LDV 8
CF(1)         6717 LDV 7

Should be good to go.

Also had 1 read error:
 
Testing LPT device address:0378
Using LPT device at address:0378
Flash Config: 0x01198010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: nand1.bin
Reading
Error: 208 reading block 3FF

if I plan on installing freeboot, do I have to deal with the bad block ?

[brandogg]

I don't think that's actually a bad block, just a read error. Dump again, specifically that area of the NAND, if it comes out clean, then you can probably just inject the clean block into your first dump (saves a shit-ton of time since you're using LPT). That is the last block on the NAND though, and typically you would remap a bad block in that area if you had one in an earlier spot...you'll probably be just fine leaving it as is.

[thwack]

Run the dump through Degraded - it's the only real way to tell if the block is bad or the read (although this does sound like a read error). The block in question is one that's reserved for re-allocation for other bad blocks, so running this dump through Degraded to see is essential - if there's other bad blocks on the NAND and one has been allocated to 3FF, and you've got no good read of it, you may screw your 360....

[thwack]

Then you're good to go - as said, that block is purely for re-allocation. On a side note - the last piccy isn't a bad dump, it's just that the NAND has a physical bad block, and it's been re-allocated by the 360 to 3FF (you'd need to reallocate it for FreeBoot/XBR). A bad dump wouldn't have the reallocation part (ie the 'xxxx found at xxxx'). If that were the case, it'd mean somethings wrong with your reader/writer.

Just out of interest (and don't try it if you can't be arsed), have you tried just reading out that one block? ie:

nandpro lpt(or usb): -r16 test.bin 0x3FF 1

Just to see if it still errors?

[thwack]

The bridge won't effect the NAND read/write - I wonder if it's just literally that the end block on your NAND is bad, and Degraded for some reason doesn't see it as a bad block. You will definitely be ok with your dumps though, as there's no data present on those blocks on your NAND

[thwack]

Sadly no - Tiros would be the person to ask over at XH for code specifics

[snnorlaxx]

So I tried reading just that sector, no joy.

C:\Nand_pro>nandpro lpt: -r16 nand1.bin 0x3FF 1
NandPro v2.0e by Tiros

Testing LPT device address:0378
Using LPT device at address:0378
Flash Config: 0x01198010
Block Size: 16KB Block Limits: 0x0003FF..0x0003FF
File: nand1.bin
Reading
Error: 208 reading block 3FF

[thwack]

You're fine - sounds like a bad block issue, as said, so long as nothing is reallocated to that block, JTAG away

[snnorlaxx]

Yup tagged it last night, all is good !
thanks again.