[randuev]

Originally Posted by jeerum is there possible downgrade 3.72 with teensy? i have 3.72 and it looks little different, have made 5-8 dumps, all has same md5 checksum

your data lines are ***xored, i wouldn't flash until you get a right dump. those strings should read "asecure_loader" and so on

check your data lines. you must have a short somewhere.

[djhazee]

I am getting some weird behavior. I used the downgrade v2 files and was able to get the ps3 to boot again, however I get stuck at a message "Cannot Start. The correct hard disk was not found". I am wondering if I patched the files correctly. I can send someone my original flash dump if they want to try editing it for me. Any suggestions?

[jeerum]

Originally Posted by randuev your data lines are ***xored, i wouldn't flash until you get a right dump. those strings should read "asecure_loader" and so on check your data lines. you must have a short somewhere.

thanks, i have already removed teensy and give a try on my ps3 slim :D
seems my dia-002 mobo with this nor dont like teensy.

[Dudshl]

Originally Posted by jeerum thanks, i have already removed teensy and give a try on my ps3 slim :D seems my dia-002 mobo with this nor dont like teensy.

I had DIA-002. It likes teensy and was successfully downgraded.

[djhazee]

Successfully downgraded! I think the "Noob Tutorial" could use some work. Here is what I ran into that held me back:

1) If you get a hard drive error, make sure your HDD is plugged in all the way! (Doh!)
2) You need a jig to put the PS3 into factory mode (I used PSGrade with my spare teensy 2.0).
3) Use the SECOND file in the lv2diag_355 folder.

Big ups to the scene and to judges for his NOR flasher!

I would also suggest this tutorial:

[portals94]

Is there are any solution to flash SEM-001(NAND 2x Samsung K9F1G08UOА-PIB0) via teensy ++ 2.0 ?

[butnut]

Originally Posted by judges ...It's been confirmed to write successfully to Samsung K8Q2815 using "writeword" and "writewordubm" modes. -- judges

Man I need to get another teensy...

Thanks for doing this judges.

[Dumbelek]

Hi,

I have DYN-001 board and I was waiting for Samsung support. According to ps3devwiki DYN-001 has Samsung nor but I have Spansion nor (I learnt today). I hope this wont be a problem.

I would like to ask something about wiring, cant we just connect wires with silicone?

[jeerum]

can someone patch my nor dump for me?
my own pc is broken and i'm too noob in ubuntu.
thanks1

[rick#2]

Hi, hoping someone out there can help me out.

First, big thanks to judges for sharing his work with the community!

Here's a copy of the ROM dump from my DIA-001/CECHH (Spansion S29GL128N90TFIR2-NOR 16MB) era PS3:

http://dl.dropbox.com/u/22632665/flash.bin

Now, here's a copy of the ROM I wrote to my PS3 via NORWay v0.4R12:

http://dl.dropbox.com/u/22632665/NORdowngrade.bin

Both the original, unmodified dump (flash.bin) and the 3.55 downgrade-ready patched dump (NORdowngrade.bin) looked pretty good to me at a glance in a hex editor, but I must admit that I am new to PS3 patching/hacking.

It seems I've now got a rather expensive paperweight, as when I turn it on, it acts as though NORWay hasn't "released" it; ie: green light but no video output. (And yes, I did run NORway with the "release" argument after I was finished writing). I've tried using an Arduino Mega2560 flashed with PSGrade to put the PS3 into Factory Service Mode but no dice, it just remains on the green light on startup with no other activity or video output. Unfortunately, I only have one Teensy++ 2.0 and now, after some buggering around, I must have fried it as it is no longer recognized as a Serial Device in either Windows or Linux, so I've ordered another one but it will take a few weeks, and in the meantime I'd like to see if anyone can point out where I went wrong.

I was pretty confident that my original dump was good before I dove into writing a modified version into the PS3's ROM because I was able to obtain perfectly matching dumps five times in a row, but the "norpatch.exe" utility was not able to identify my ROM dump as a system running 3.70, rather I get this:

PRG0: 3.55
PRG1: 3.50
PKG0: 2.10
PKG1: unknown
ROS0: unknown
ROS1: unknown

I'm thinking something corrupted somewhere along the line, but not exactly sure where. If this is the case, I've accepted that I've probably irreversibly bricked my PS3 after writing over my original, untouched ROM with my modified attempt at downgrading without a proper backup but am hopeful that there is a small chance that I can salvage the data unique to my PS3 and patch it into a "stock" 3.70 ROM dump.

Could anybody give me some suggestions?