Print

[Midnight Tboy]

Hiya.

after many hours of bashing my head against the wall - finally got the jtag to start dumping the nand,

Amazingly every dump has compared fine (using FC at dos prompt only so far)..That was 2 full dumps, and 2 dumps of using command "nandpro lpt: -r3 c1.bin" ...however each time I get the error

"Error: 250 reading block 5D"

I am concerned as presumably when dumping that small part of nand suggests its in a critical area.

The guide I am going by advises to post in forums if bad blocks occur

help please...so close yet so far lol

I've just ran the nand in Infectus Nand Checker and the info is


Size - HY27US08281A-X360
Data - 512
Spare - 16
Pages - 32
Blocks - 1024
Position - 5

Total Pages : 32768
Bad Pages : 2
Empty Pages : 1466

I've just pressed Detailed Log too

it says

Bad Block at 0x17FA00
Bad Block at 0x17Fc10


how come that shows 2 blocks but nandpro only said 1 bad block?

[Midnight Tboy]

update.......


well I think I've got Degraded working, by searching for a 1BL key as used in the timing attack, ticking Valid, and then setting "File System Start" to 39  (are these values ok to use tho or are they specifally for the timing attack and NOT to be used for this?

With the settings like that anyway, degraded does at least let the bin file load

The info says

CB Version 1903 LDV 0
CD Version 1888
CE Version 1888
CF(0) Version 7357 LDV 8
CF(1) Version 7363 LDV 9
Note . Bad Block @ 0x5D
Note : Block 0x5D found at 0x3FF


so is this ok and how do I proceed from here - as I'm stuck knowing what to do with bad blocks and really want to make sure before go any further

hmmm nope that doesnt work -

when I press "Build Downgrader Image" to see what would happen I get ""Couldn't Find FS mfgbootlauncher.exe""


arrgghh

[Midnight Tboy]

ah - looks like have to use app Bad Block Mover instead?  So many of these programs tho - which is newest/best/recommended :-s

[norm360]

You could move the block manually. See this thread - http://forums.xbox-scene.com/index.php?showtopic=698328

Or like me use Bad Block Remapper, simply load your good image and it should detect the bad block, then load up your xbreboot image to patch.

This post has been edited by norm360: Jan 21 2010, 04:58 PM

[Midnight Tboy]

cheers mate - I'll have a go at doing it both manually and the bad block remapper software  Can't hurt to learn both things  Will then FC too afterwards to make sure my manual way has worked

[Midnight Tboy]

hmmmmm well I've followed the manual way to the letter

ie

nandpro xbr.bin: -r16 block5d.bin 5d 1
nandpro xbr.bin: -w16 block5d.bin 3ff 1

Did that twice (obv using a 2nd copy of the xbr.bin) , and compared them to make sure no accidental typo first time round.

I then did similar in Bad Block Mover (v1.0)....Opened the file it detected the block 5d no problem.

When I press to repositioned the blocks

it reads the 5d data, then writes back 5d data to the offset (0x0107BE00) which I presume is 3ff.

It then says "zeroing block ID at offset 0x0017FA00"

I'm guessing then that its deliberately blanking the data in that block.

Now when I file compare that file to the one I made manually it scrolls with a load of detected changes??


Sooooo........obv I can't compare the 2 directly that way....but in that case....which is the best file to use??  the one with the zeroed blocks at 5d, or the one I made manually which in theory still then has the data held at block 5d aswell as 3ff?

Want to make sure I pick the correect one, as if/when it comes to using the 360 flashing program directly off the 360 in future - to prevent any potential problems.  As I plan to remove my lpt cable once finished and use the 360 flashing tool in the future...as the lpt cable tbh is craply made by me and wont last 5 minutes once the case is closed (IMG:style_emoticons/default/smile.gif)

This post has been edited by Midnight Tboy: Jan 21 2010, 06:33 PM

[norm360]

Either one is good. Because when you write the image back to the flash it will fail when it comes to block 5D anyway, same as when you tried to read it.

The reason you see differences is because you didnt blank the block when you did it manually.

Dont forget to patch in your rawkv & rawconfig.

This post has been edited by norm360: Jan 22 2010, 07:39 AM