[incognita]

Originally Posted by liranantebi First of all, I would like to thank judges for his wonderful work on the NORWay project and for releasing the sources. I have created a new project, based on his project which uses the Teensy++ 2.0 hardware to flash (read/erase/write) the PS3 (and xbox 360) NANDs. The project is in it's alpha stage. I have already succeeded in flashing xbox 360 NANDs as well as the ps3 NANDs. I'm doing it for experimental purposes but if anybody would like to comment and test - you are more than welcome and i will be happy to assist / support / help. the project is currently located in github, branched from the master NORway branch and named "NORway-and-NANDway".

I am very interesting in that and I have a couple of NANDs PS3 in which I want to try it. I think "judges" was creating something like that maybe you both can work together
I have a question, if you could answer me I will be able to try it
I don't understand very well your readme, are you saying we need an external power supplied?

Thank you very much and I am sorry for my bad english.

[guerrierodipace]

Originally Posted by liranantebi the project is currently located in github, branched from the master NORway branch and named "NORway-and-NANDway".

is this yes?
https://github.com/liranantebi/NORway-and-NANDway
thanks

[judges]

Originally Posted by liranantebi First of all, I would like to thank judges for his wonderful work on the NORWay project and for releasing the sources. I have created a new project, based on his project which uses the Teensy++ 2.0 hardware to flash (read/erase/write) the PS3 (and xbox 360) NANDs. The project is in it's alpha stage. I have already succeeded in flashing xbox 360 NANDs as well as the ps3 NANDs. I'm doing it for experimental purposes but if anybody would like to comment and test - you are more than welcome and i will be happy to assist / support / help. the project is currently located in github, branched from the master NORway branch and named "NORway-and-NANDway".

That sounds great! Really appreciate that you took initiative and started implementing that yourself. Thumbs up!

Unfortunately I currently have very little spare time due to various projects on the job, so I did not had the time yet to have a look at it.

Also I was working on this myself and did plenty of changes to the current code base (proper Windows client, USB based on LUFA, etc). But more about this via PM.

-- judges

[liranantebi]

Yes. This is the location, guerrierodipace.
You are more than welcome to try it out, incognita.

You can have a look @ bailey's guide for instructions for the NANDs with progskeet. Use teensy NANDWay for reading writing.
I do not yet know how to 'crash' the PS3 with NANDs as the progskeet does. With the NOR it's easy - you pull the TRISTATE low (afaik).
So other powering options are:
1. Use external power - the teensy 3.3v regulator is not enough. you must use external source that have enough current (it's ~1.8A).
2. extract the NANDs from the motherboard and do offline reading.

I don't have a 360 clip yet - so i will be happy if someone would like to try it out with a clip.

The NANDWay.py script is straight forward:
info - extracts the id from the chip
dump - dumps the entire NAND contents to the local disk
write - writes and verifies everything.

I also would like to get NAND dump with bad blocks to test (i just need the dump). you can see that a NAND have bad blocks with flow rebuilder. it's ok for a NAND to have bad blocks. usually they are mapped during manufacturing and can develop over time.

future features:
1. Teensy should be powered from the PS3. How do I crash the NAND ps3?
2. Bad blocks. skip bad blocks as the ps3 does. the information is stored in the spare area - so most probably sony didn't erase it. i just need to have one dump with bad blocks in order to understand how to identify.
3. Differential write. writing+verifying is very slow. Differential writing can improve write time dramatically and avoid writing to un-needed places.
4. read/write parts of the NANDs. Like what NANDPro for the xbox does.

[raiden@consoleopen]

Giving my 2 cents to this amazing project...

I don't like to solder everytime so many wires, i built with guerriero a zif socket shield (adding pictures later).

There was something odd reading this thread, everyone has tristate High (or True) on norway.py output, in fact my dumps where fine on Spansion P but the device was unknown, Samsung P was instead recognized correctly... So i looked up to F7 (tristate) on teensy, it wasn't connected anywhere, i supposed giving 3,3 volt to it could change the identification problem (couldn't write with unknown spansion but could write with recognized samsung, odd!), after that connection spansion was recognized but not entirely (s29gl128 text wasn't there, ) and dumping wasn't valid anymore (random bits)... Again something fishy, i supposed tristate introduced some kind of noise to 3,3 volt line (generated by regulator 1086-33), added 100 nF capacitor between 3.3 volt and ground, magically s29gl128 appeared in the identification output and dumps were correct once again.

Ended that way ? No

Happy and sure to got it right i started writing, it fails with every single command (write, writeword, writewordubm), tried erasechip also, i'm investigating now, error occurs after a certain percentage of completion, i presume it's related to insufficient current to the nor, added 10k resistor between F7 and 3,3 volt line, gonna test later and let you know...

While waiting i'm writing with progsh1t 1.0, 10 hour to wait for spansion + zif shield, sh1tty chip...

ok, i can confirm something... zif + norway, if correctly wired, dumps fine even without identification itself (without tristate wired), will investigate nor writing problem next spansion on my hands.

please post schematic for nandway, testing zif socket here if posted

[zeruel85]

I tried NANDway with Teensy + zif socket nand, no success. The nand isn't recognized (Unknown Chip Manufactured) and the dump doesn't start. I use an external power supply for the nand, and the 3.3V regulator for the Teensy. I also put a 10 kOhm pull up between VCC and R/B, but without success (always not recognized).

[liranantebi]

Hi zeruel85,

Thanks for trying this out.
Either you are using an external power supply or you are using the USB power supply w/ the 3.3v regulator.
From my own experience, the 3.3v is sufficient for stand-alone configuration.
Please make sure that the wires are good and you have good contacts.
Also:
1. Make sure that you are using Samsung K9F1G08U0A-PIB0
2. Discard the external power supply. Use the USB power supply only with the 3.3v reg to drive both teensy and the NAND.
3. Discard /RB signal. It is ok if it's connected (and pulled up) but the NANDway can handle without this signal.
4. Make sure you are using the latest binaries from the Github/NANDWay project (updated).
5. Make sure that your wires are not too long and that you have good contacts. The protocol between Teensy and the NAND controller will not work if a signal is missing. test it with continuity meter and even see some values with a scope.
6. try also to connect 0.1uf cap between the Vcc and Vss as close as possible to the NAND chip.

I hope this helps. Please let me know if you need further assistance. You can also PM.

[zeruel85]

Unfortunately, I only have Samsung K9F1G08U0B-PIB0 in my hands. I want to try with Teensy++, because WinSkeet and ProgSkeet 1.2 don't do identical dumps with these 'type B' nands.

Thank you for your great work and also for your quick support!

[liranantebi]

Hi zeruel85,

I believe they are the same in terms of interface (maybe read id requires one more byte - but it's ok). It's still manufacture:EC device:F1. I will be happy to assist, but let's start by eliminating all the other stuff that I've requested (single 3.3v power supply, connectivity, conductivity, no shorts).

[DebugBrain]

Originally Posted by zeruel85 I tried NANDway with Teensy + zif socket nand, no success. The nand isn't recognized (Unknown Chip Manufactured) and the dump doesn't start. I use an external power supply for the nand, and the 3.3V regulator for the Teensy. I also put a 10 kOhm pull up between VCC and R/B, but without success (always not recognized).

What kind of external power supply are you using?
The external power supply must have at least 1800mA of power for recognize correctly the nands