[crunchienuts]

Hi guys,
working my way through the downgrade and got a few things i need cleared up.

- PS3 Slim CECH2502 w/ NOR
- JSD001 Testpoints
- Teensy++ 2.0 w/ 3.3v regulator, 5v traces cut & 3v pads shorted

First things first..when I go and do a "norway.py COM3" command here is the result...

Pinging... Set SB to tristate NOR chip manufacturer: unknown (0x41) NOR chip type: unknown (0x414143) STATUS_TRIST_N: False STATUS_RESET_N: True STATUS_READY: True STATUS_CE_N: False STATUS_WE_N: True STATUS_OE_N: True Resetting NOR... Ready.

then when i turn on the ps3 and either do a "norway.py COM3" or procede to dump the flash with "norway.py COM3 dump flash.bin" this is the output

Pinging... Set SB to tristate NOR chip manufacturer: Spansion (0x01) NOR chip type: S29GL128 (0x7e2101) Checking sector protection... No protected sectors found! STATUS_TRIST_N: False STATUS_RESET_N: True STATUS_READY: True STATUS_CE_N: False STATUS_WE_N: True STATUS_OE_N: True Resetting NOR... Ready. Dumping NOR... 16384 KB / 16384 KB Done. [0:01:13.937000]

Now my multiple dumps are the right size & when i run them through norpatch they all result in the following

PRG0 version is 3.50 PRG1 version is unknown PKG0 version is unknown PKG1 version is unknown ROS0 version is 4.10 ROS1 version is 4.00

Now my problem is, that when i go for a "norway.py COM3 release" command, it successfully restarts the NOR however I am unable to turn on my PS3 (no video, can't use power button to turn off, video reset doesn't work, & yes, teensy is disconnected)

I was wondering if my problem could be related to the fact that my "STATUS_TRIST_N: False" output is causing the problem. Maybe it's preventing my PS3 from operating normally?

*NOTE* I am able to also successfully write the full 16MB to the NOR as well

Any help would be much appreciated =]

[nortnil]

Originally Posted by crunchienuts Now my problem is, that when i go for a "norway.py COM3 release" command, it successfully restarts the NOR however I am unable to turn on my PS3 (no video, can't use power button to turn off, video reset doesn't work, & yes, teensy is disconnected) .... *NOTE* I am able to also successfully write the full 16MB to the NOR as well Any help would be much appreciated =]

When you wrote the NOR were you writing a downgrade.bin or your original dump? If you wrote the downgrade.bin and then started having problems with no video, etc then there may be a problem with your downgrade.bin.

If that is the case try writing your original dump and see if that brings it back to life.

Also did you check your dump in a hex editor against the flash wiki to visually inspect the offsets? Flash wiki

Other than that I don't know. I am still struggling with my own problems currently.

[crunchienuts]

Thanks for the prompt reply!
I've had a bit of luck since last time

To answer your question I flashed my original dump just to see if it would write successfully. (which it did)

Anyhow, I resoldered the E7 (Tristate #) line and managed to get Norway to display "STATUS_TRIST_N: True" and the PS3 now boots to the "Press the PS Button screen" and I am able to turn it off also.

Now I'm not exactly sure what the implications of my "STATUS_TRIST_N: False" from before means on me. But will I have received a bad dump because this output was false the first time? I also did a full write using the original dump back to the PS3 under this False state.

I will go ahead and check my dump using the Flash wiki you mentioned.

Anyone care to shed some light?

[nortnil]

Edit:

I thought I was having a problem when everything was working exactly as it should have. I didn't realize that when I went into FSM before installing the CFW I wouldn't have anything displayed on my screen and the console would shut down if there was no USB drive supplied with the PS3UPDAT.PUP and Lv2diag.self.

When I tried booting with the USB drive the console stayed on and showed sings of reading from the flash drive. I left it on for about 15 minutes, but it wouldn't turn off. I eventually turned it off and rebooted. It went to my CFW and showed the red box that I was still in FSM.

I used the second Lv2diag.self and exited FSM no problems.

THANK YOU JUDGES!!!!! I literary could not have done this without you! Where is the donate button?

[nortnil]

Originally Posted by crunchienuts Thanks for the prompt reply! I've had a bit of luck since last time To answer your question I flashed my original dump just to see if it would write successfully. (which it did) Anyhow, I resoldered the E7 (Tristate #) line and managed to get Norway to display "STATUS_TRIST_N: True" and the PS3 now boots to the "Press the PS Button screen" and I am able to turn it off also. Now I'm not exactly sure what the implications of my "STATUS_TRIST_N: False" from before means on me. But will I have received a bad dump because this output was false the first time? I also did a full write using the original dump back to the PS3 under this False state. I will go ahead and check my dump using the Flash wiki you mentioned. Anyone care to shed some light?

When I flashed back to my original dump it booted back like nothing ever happened. I honestly don't know enough to know what the "Press the PS Button screen" means for your situation after flashing back to the original dump.

When it flashed back did it seem to write really quickly? Unless you did an erasechip the write command should be looking for changes and only flashing changes to the NOR and not flashing the whole image. My only guess is if the original dump were somehow wrong then flashing it back may have written over some previously good sectors which now results in the press PS screen.

I wish I were more help, but I'm still figuring this out too. Judges has been consistently responding to me first thing in the morning, so hopefully he can both of us later.

[crunchienuts]

Sorry to mention but i should have pointed out that the PS3 was stuck in an update boot loop due to a broken bluetooth module. It was giving error 8002F1F9. So I'm guessing the press PS button is a sign of progress as it's not trying to update itself anymore.

When i flashed the original dump back to the PS3 it definately wasn't quick. Chip was not erased and it did behave in a way like you mentioned.

I cross-referenced the flash page with my dump and although I didn't go through all the addresses, the dump does in fact look like a good clean dump. But again just want to make sure of what I'm doing before I do any real damage.

On another note, I did try the 8Mhz Teensy Psgrade .hex file to see if I could get in Factory Service Mode but to no avail. Havn't pursued it any further so not sure what to do there. I left my Teensy the way it was (3.3v reg, 5v pad traces cut, 3v pads shorted) and plugged it into the rightmost USB port but it doesn't seem to jig the PS3 and continues to just boot to the "Press the PS Button"

[judges]

Originally Posted by crunchienuts Sorry to mention but i should have pointed out that the PS3 was stuck in an update boot loop due to a broken bluetooth module. It was giving error 8002F1F9. So I'm guessing the press PS button is a sign of progress as it's not trying to update itself anymore.

You'll probably need a special CFW that has BT disabled. Check out this post, euss created an MFW task specifically for that: http://www.ps3hax.net/showpost.php?p...&postcount=136

Originally Posted by crunchienuts When i flashed the original dump back to the PS3 it definately wasn't quick. Chip was not erased and it did behave in a way like you mentioned. I cross-referenced the flash page with my dump and although I didn't go through all the addresses, the dump does in fact look like a good clean dump. But again just want to make sure of what I'm doing before I do any real damage.

Sounds like the hardware part is running fine. Since norpatch recognized ROS0/1 of your dump, it should be okay. There's always a slight chance for the dump to still being corrupted, but it's very unlikely, because the ROS areas are the largest part of the NOR and if those are correct, at least all of your data and address lines are working 100%. And there's no way to check to entire content..

Originally Posted by crunchienuts On another note, I did try the 8Mhz Teensy Psgrade .hex file to see if I could get in Factory Service Mode but to no avail. Havn't pursued it any further so not sure what to do there. I left my Teensy the way it was (3.3v reg, 5v pad traces cut, 3v pads shorted) and plugged it into the rightmost USB port but it doesn't seem to jig the PS3 and continues to just boot to the "Press the PS Button"

Did you do the power/eject sequence to enter fsm? Check this out: http://www.ps3devwiki.com/wiki/Boot_...F_manufacturer

And give it a couple of tries, it doesn't always work the first time. Don't know why, but my E3 fsm jig also doesn't enter fsm all the time. Doesn't seem to be a Teensy problem.
************* [ - Post Merged - ] *************

Originally Posted by nortnil THANK YOU JUDGES!!!!! I literary could not have done this without you! Where is the donate button?

Good to hear that everything's working out fine for you. A "Thanks" is enough donation..

[nortnil]

Originally Posted by judges Good to hear that everything's working out fine for you. A "Thanks" is enough donation..

Then THANK YOU!!!! AMAZING WORK!!!!

I also didn't notice until after I opened my console to push the button on the Teensy you added a "bootloader" command to NORway.py to flip to the bootloader and reprogram it with the psgrade you adapted. Very helpful, wish I had seen that earlier. Nicely done.

[crunchienuts]

UPDATE

In response to judges post, I continued the firmware downgrade under the assumption my dumps were fine.

Loaded the PSgrade .hex file onto the teensy again with everything still soldered (3.3v regulator included). Plugged that into the PS3 and after giving the "Power then quickly press eject" trick, it entered FSM after about 3-4 tries. I think my issue before was that I had no idea about the mentioned trick.

Proceded to downgrade with the USB, and everything went without a hitch. For the record, I did also use a patched CFW to bypass the update errors I was having.

Not sure if it might be of any help to anyone or if it even makes a difference, but I actually tied the Teensy's GND point to every ground listed in my JSD-001 diagram (theres about 10). I realise now, I could probably have gotten away with just 1 or a couple, but goes to show itll still work nonetheless and I was getting consistent dumps each and every time.

big THANKS goes out to judges for some exceptional work!

[judges]

I've just released NORway v0.4 (see first post). Basically it's the same as v0.4beta12, just with updated readme's, change-logs, etc. Just needed to make a cut before starting to work on new features and improvements. You'll see those in the next v0.5beta...