Looks like your NAND dumps are ok, you should use 355patchcos.bin first - if that fails try applying the trvk patch. I haven't used the 3.41 patched COS yet. Are you sure you're patching from the right offset? C0020 - make sure the cursor is flashing at the beginning of that offset.
In flowrebuilder when you de-interleave the modified 256Mb image, you need to select your original NAND0.bin & NAND1.bin - then select your modified 256Mb image. This creates your modified 128Mb flash images.
You'll be left with NAND0.bin.new & NAND1.bin.new - flash these files back with Differential Flashing (no verify)
When it's complete, dump BOTH NANDs again & compare them against your NAND0.bin.new & NAND1.bin.new - any differences = bad flash/bad connections to NAND.
The reason I said downgrading 16Mb NOR consoles is the same for 4.00 as 3.7x, 3.6x etc is because this is true. I've downgraded BOTH NAND & NOR consoles on 4.00 firmware without problems. The 16Mb NOR console I did only required the first patch (3.55 COS) to 'black screen' the PS3 for FSM downgrading.
Last edited by mushy409; 01-23-2012 at 05:56 PMReason: Automerged Doublepost
Just looking at your patched dump... I can't understand how your NAND image is interleaved, but mixed up every 0x200 in sections... I'm re-downloading your original dump, then I'll patch it for you and re-upload the new image
that means, his NAND DUMP had badblock. and i am really sure thats came from SAMSUNG UOB. it has more than 2bad blocks after interleaved. and most of badblocks are in Core_OS area. that's the problem come.
- Flowrebuilder only do ECC not remaping BADBLOCK.... so remap the downgrade patch base from core_os dump.
- As long as BADBLOCK not store on Core_OS area, you are lucky to go