[zeruel85]

Yes!!!

I use ProgSkeet 1.2 as the source power supply and magically I have identical dumps, for both the nands!

I verified them and are ok, statistics and all is good, but I have 3 bad blocks in one nand, and 1 bad block in the other.

[3absiso]

Originally Posted by zeruel85 Yes!!! I use ProgSkeet 1.2 as the source power supply and magically I have identical dumps, for both the nands! I verified them and are ok, statistics and all is good, but I have 3 bad blocks in one nand, and 1 bad block in the other.

it is your choice to continue with the downgrade or stop.
but i suggest verify every important address in the dump, if you decided to continue with it

[Sarah1331]

^^ agree or be 100% there correct dumps

They sound rite for a b NAND
I'd continue and hope it works if not flash the orig dumps back

To go down the remap route


Sent from my iPhone 5 using Tapatalk

[stdule]

If you remove nands chip you have to watch the temperature and use flux if it is too hot it can damage the chip, so maybe you're different flash because the chip is damaged.

[Abkarino]

Originally Posted by zeruel85 Thank you Abkarino, I shorted VCC 12 pin with 37, and GND 13 with 36 pin. The nand is fed to both side (I always did that). Now I want to try with Teensy and NANDway Beta, I'm curious...

You are welcome, i did this also first and NAND does not work fine.
So just use double wire from progskeet to nand socket for both Vcc and Gnd so it must work fine for you.
or try to use another thicker wire and test it.
Another option just try another PC or USB port since progskeet fail in some USB ports.

[zeruel85]

I've just sent an email for Dump Checking Thread. I think they are good, but when I use FlowRebuilder to interleave the two dumps into a unified one, it says to me that there is 1 bad block on the first nand, and 3 bad blocks on the second one.

@stdule :
I'm not a newbie...

[underwurlde]

^ the reporting of bad blocks in FlowRebuilder threw me for quite a while. I had 0 bad blocks in NAND1 and 7 (!!) bad blocks in NAND2.

However after having them verified (thanks @Sarah1331 ) they actually proved OK. Then patched and re-programmed them with the patched.bin and now my PS3 lives again!

Andy

[zeruel85]

Originally Posted by underwurlde ^ the reporting of bad blocks in FlowRebuilder threw me for quite a while. I had 0 bad blocks in NAND1 and 7 (!!) bad blocks in NAND2. However after having them verified (thanks @Sarah1331 ) they actually proved OK. Then patched and re-programmed them with the patched.bin and now my PS3 lives again! Andy

I use FlowRebuilder v4.2.3.0 and the union goes well, but it says to me about the bad blocks.

So, I don't understand if I can continue with patching the unified dump and then de-interleaves it into two separate new ones, or I cannot proceed.

Please, can you give me more details?

I've already tried to patch the unified dump and no errors occured, statistics are very good, and also I can de-interleave it into two new 'flash BIN' files. But I don't understand what happens if I flash the two nands with these two new patched BINs. Do I have to remap the bad blocks or not?

[3absiso]

Originally Posted by underwurlde ^ the reporting of bad blocks in FlowRebuilder threw me for quite a while. I had 0 bad blocks in NAND1 and 7 (!!) bad blocks in NAND2. However after having them verified (thanks @Sarah1331 ) they actually proved OK. Then patched and re-programmed them with the patched.bin and now my PS3 lives again! Andy

Did you remap bad dumps or what?
since the bad block are a headache if in wrong place.
your help is appreciated?

[zeruel85]

How can I verify if my bad blocks are in the CoreOS area or not?

From what I understand, reading some materials found online, if the bad blocks are out from the CoreOS area there is no problem and I can proceed, right?

Inviato dal mio GT-I8150 con Tapatalk 2