Dumped orig. NAND with Bad blocks, can`t rewrite it back. Falcon CB:5771

[techboy]

Hello everyone. Sorry to bother you, but I`m in dead end and can`t scratch out.

Is this 0xCB block unique for all falcons or it is crypted with CPU key? Can i barrow it from donor`s dump?

In addition, please someone can give me dumped 0xCB block from Falcon to compare it with my dump.
nandpro orig.bin: -r16 blockCB.bin CB 1 or nandpro lpt: -r16 blockCB.bin CB 1

I hope I can swap it with my CB hole in rebuilded image.

Thanks in advance guys, give me some lights.

According to Degradded my console is:
Falcon
CB Version 5771 LDV 0
CD Version 8453
CE Version 1888
CF(0) Version 7371 LDV 3
CF(1) Version 8955 LDV 4

For detailed information:
I dump my NAND from Falcon 3 times and flash it with injected XBR. Then I realize that my console is unexploitable CB:5771.
When I compare my 3 dumps, saw a lot of Bad blocks, but it was late.
I rebuild an image with NandCompare from 3 dumps and down bad blocks to 2 blocks.

Code:

1024 block(s) in nand image
1 non-matching block(s) found
CB

One was 0xCB block other is 0x343 founded at 0x3FF(I think this is an empty block)
When I flashed with rebuilded image, i get E79 error again with 1 red light.
Now my only exit is to fix and flash back my origin dump. However, I have a 0xCB hole in it.

Sorry for my Bad English

[maximilian0017]

1st step is to dump the nand 3 times and COMPARE.

Did you remove the diodes before booting the original dash?

If the Nand dump is screwed then you are too, the NAND is encrypted with the cpukey you are out of luck until they find a new hack (if they ever do find one).

[techboy]

1st step is to dump the nand 3 times and COMPARE.
As the biggest part of the NAND is encrypted with the cpukey you are out of luck until they find a new hack (if they ever do find one).

yep, I was compare it, but who to see the Bad blocks at them 


With these burned eFuses I`m losing my hope. With latest dash, I can`t get XELL, but HELL gets me. 

I extract 0xCB block from my 3 dumps and half of them had zeroes {from begining until offset 00000F17} and other part has HEX data {non understandable, so I think crypted like you say}. Is this a normal? They match, when I compare them.


Is your 0xCB block contains zeroes? Can you check it please. I`m trying to understand is my faulting suspect is this F%&*#ng block.

[maximilian0017]

Comparing is checking every character of a file with another.

If images have multiple different bad blocks you hava a very bad image and you will probably not get it to work.

Maby you could insert the cb block from your org2 dump into the repaired dump, maby this will help.

[techboy]

Compared 0xCB blocks in 3 dumps, they are same.
I already tried to inject it in flashed with rebuilded image NAND. It`s doesn`t seems to work.

 Same E79 error with 1RROD, secondary code 1033 "Dashboard Error - Couldn't start xam.xex: probably a file system corruption, it could also be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it."

I`m out of ideas.

[maximilian0017]

Only block 343 was bad so all the other bad blocks are multiple errors in your NAND dump, unless a new hack is found you are Fubar'ed (f***ed Up Beyond All Repair)

Sell for parts or wait on a new hack...

[techboy]

Thanks for explaining and supporting maximilian0017 that was bad starting with xbox exploiting for me.
The lesson was learned!   


Will wait and hope lightening soon.