[zoom33]

ok i'm back with bad news, it doesn't work ...

the script is deleting the bad block so the output file is 135036 Kb
was before 135168 Kb

here is what I'm doing manually with an hex editor:

$5FA6000 is beginning of bad block
$5FC6FFF is end of bad block

$5FC7000 is beginning of next block
$83FFFFF is the last byte of the last block

copy data from $5FC7000 <--> $83FFFFF to $5FA6000

it means that block 1023 is the same as block 1022

am i right or wrong ?

My question now is does the dump have some kind of ECC or checksum ?

[3absiso]

Originally Posted by Effleurage @zoom33 nandway.py remapbadblocks top_nand.bin new_nand.bin remapped_new_nand.bin top_nand.bin is the NAND with the bad blocks on the top new_nand.bin is any dump you have of the replacement top NAND. remapped_new_nand.bin is the output that you should write to the new NAND. what is does is to find all the bad blocks on top_nand.bin, find all the bad blocks in the new_nand.bin and create new file remapped_new_nand.bin which you should flash to your new NAND.

What is the second "new_nand.bin"? i do not get it.
so this script is done after patching the original dump and separate it it into top and bottom dumps? ad it is done for both top and bottom dumps?

[Effleurage]

Originally Posted by 3absiso What is the second "new_nand.bin"? i do not get it. so this script is done after patching the original dump and separate it it into top and bottom dumps? ad it is done for both top and bottom dumps?

top and bottom should be treated separately. this is not related to whether you patched the NAND or not. you can call this script - "NAND copy". it overcomes the problem of bad blocks which are found (during manufacture or later) in the NAND.

What the script does is:
1. strip all the bad blocks from src_nand. (again - it can be either patched or not).
2. find all the bad blocks in tgt_nand - that is why i need new_nand.bin
3. remap data we have in (1) to the tgt_nand using what we found in (2).
************* [ - Post Merged - ] *************

Originally Posted by zoom33 ok i'm back with bad news, it doesn't work ... the script is deleting the bad block so the output file is 135036 Kb was before 135168 Kb here is what I'm doing manually with an hex editor: $5FA6000 is beginning of bad block $5FC6FFF is end of bad block $5FC7000 is beginning of next block $83FFFFF is the last byte of the last block copy data from $5FC7000 <--> $83FFFFF to $5FA6000 it means that block 1023 is the same as block 1022 am i right or wrong ? My question now is does the dump have some kind of ECC or checksum ?

ok,

first of all, I fixed the script - so you can take it from the hjudges/NORway repository and retry.

what you did seems right to me (all the calculations). the only thing that is a) in case you have several bad blocks, and b)missing is the remapping to the new NAND.
If the new NAND doesn't have any bad blocks - you are fine. otherwise you have to remap

[3absiso]

Originally Posted by Effleurage top and bottom should be treated separately. this is not related to whether you patched the NAND or not. you can call this script - "NAND copy". it overcomes the problem of bad blocks which are found (during manufacture or later) in the NAND. What the script does is: 1. strip all the bad blocks from src_nand. (again - it can be either patched or not). 2. find all the bad blocks in tgt_nand - that is why i need new_nand.bin 3. remap data we have in (1) to the tgt_nand using what we found in (2).

Please bier with me;
so the trg_nand is the same as the src_Nand but different naming

EDIT:
so first we have to find the bad blocks using the following command
NANDWay.py badblocks Filename (input.bin)

Then use the produced file in the following command to remap the bad blocks
NANDWay.py remapbadblocks input.bin NewNand OutputFile

[Effleurage]

Originally Posted by 3absiso Please bier with me; so the trg_nand is the same as the src_Nand but different naming

say you have two NAND chips. src_nand and trg_nand. you have a dump of both NANDs: src_nand.bin and trg_nand.bin. you want to copy all the contents of the src chip to the target chip.
you run remapbadblocks src_nand.bin trg_nand.bin flash_to_your_trg.bin

the new file flash_to_your_trg.bin is the output that can be flashed to trg_nand.

Originally Posted by 3absiso EDIT: so first we have to find the bad blocks using the following command NANDWay.py badblocks Filename (input.bin)

you don't need to find the bad blocks - it's just another utility that dumps all the bad blocks in a NAND dump. all you need to do the copy one nand chip to another is to use remapbadblocks.

Originally Posted by 3absiso Then use the produced file in the following command to remap the bad blocks NANDWay.py remapbadblocks input.bin NewNand OutputFile

the commands are separe. you need only the second.

[3absiso]

Originally Posted by Effleurage say you have two NAND chips. src_nand and trg_nand. you have a dump of both NANDs: src_nand.bin and trg_nand.bin. you want to copy all the contents of the src chip to the target chip. you run remapbadblocks src_nand.bin trg_nand.bin flash_to_your_trg.bin

will it looks i am rusty or what;
i will put a case here and you say what to do
I have a NAND PS3, dumped the bottom Dump and the Top Dump. i merged the two dumps, made sure the Dump is ok, patched the Dump, and separated it?
so now i have

1- Original Dump:
- Top Dump (Top-original.bin)
- Bottom Dump (Bottom-Original.bin)

2- Patched Dump:
- Top Patched (top-Patched.bin)
- Bottom Patched (Bottom-Patched.bin)

so the top Dump has Bad blocks (no matter how much are they)

what would be the Command to remap the bad dump?
sorry for being a noob here
I will not ask these questions if i have one Dump with bad blocks in my hands

[Effleurage]

Originally Posted by 3absiso will it looks i am rusty or what; i will put a case here and you say what to do I have a NAND PS3, dumped the bottom Dump and the Top Dump. i merged the two dumps, made sure the Dump is ok, patched the Dump, and separated it? so now i have 1- Original Dump: - Top Dump (Top-original.bin) - Bottom Dump (Bottom-Original.bin) 2- Patched Dump: - Top Patched (top-Patched.bin) - Bottom Patched (Bottom-Patched.bin) so the top Dump has Bad blocks (no matter how much are they) what would be the Command to remap the bad dump? sorry for being a noob here I will not ask these questions if i have one Dump with bad blocks in my hands

it's ok. maybe we just don't understand each other.

it's OK - perfectly OK to have bad blocks in a NAND dump. flowrebuilder takes care of all the bad blocks - actually - this is the reason why on rescramble you have to supply the original dumps.
so explain why on your scenario you would like to remap and what do you thing it should do and we go from there.

[3absiso]

Originally Posted by Effleurage it's ok. maybe we just don't understand each other. it's OK - perfectly OK to have bad blocks in a NAND dump. flowrebuilder takes care of all the bad blocks - actually - this is the reason why on rescramble you have to supply the original dumps. so explain why on your scenario you would like to remap and what do you thing it should do and we go from there.

let us say when i flash the Patched dump the PS3 get brick but when i put back the original Dump it works ok?
so i remap to avoid bricking my PS3?

[Abkarino]

Originally Posted by Sarah1331 @Abkarino do you fancy telling me how you fix without the patched pup or is would you prefer I research and work it out myself? Sent from my iPhone 5 using Tapatalk 2

No problem but first send me a RSOD dump then I will fix it for you to see your self.
Just PM with a link for RSOD dump then I will upload the working version for you after I fix it.

[Sarah1331]

Originally Posted by Abkarino No problem but first send me a RSOD dump then I will fix it for you to see your self. Just PM with a link for RSOD dump then I will upload the working version for you after I fix it.

Not got one to hand try explane if you want (please)