[nortnil]

Does anyone have a download for the NORway v0.4 beta? The link earlier in the thread is now dead.

[judges]

Originally Posted by nortnil Does anyone have a download for the NORway v0.4 beta? The link earlier in the thread is now dead.

I've added the link for v0.4beta12 to the very first post of this thread..

-- judges

[nortnil]

Awesome, thanks judges.

I am planning on getting this installed tonight. If I want to program my teensy with psgrade to get into service mode will I have to completely de-solder all of the connections? Or is it possible to de-solder some or none and just reprogram it where it is installed?

Thank you.

[judges]

Originally Posted by nortnil Awesome, thanks judges. I am planning on getting this installed tonight. If I want to program my teensy with psgrade to get into service mode will I have to completely de-solder all of the connections? Or is it possible to de-solder some or none and just reprogram it where it is installed? Thank you.

Added a link to the first post to a modified psgrade. It runs at 8MHz and Teensy's LED has been disabled, so that it doesn't mess with PS3's data lines while being installed. In other words: you don't have to de-solder anything. Sometimes it doesn't enter FSM at the first try, but just keep on trying, it's working.

[nortnil]

Thank you once again.

I have a DYN-001 board with a Samsung K8Q2815UQB-P14 chip. I am planning on using CrackMyDay's alternative power method. In this case am I still okay to leave the 3.3v line from the NOR soldered to the Teensy? Or should I disconnect that line before using the custom psgrade you attached?

Also when he refers to the 3.3v pad in his guide I'm assuming he means the VCC pad. Is that right?

Thank you.

[nortnil]

I was able to get several clean dumps and finally figured out how to patch a downgrade.bin... I think.

I was able to get the chip to erase, but now my problem is writing. Using any of the three write commands always results in a failure at 8192 KB with the following errors. Any input would be greatly appreciated. Thank you.


************* [ - Post Merged - ] *************

Originally Posted by nortnil I was able to get several clean dumps and finally figured out how to patch a downgrade.bin... I think.

So apparently I haven't figured out how to create a downgrade.bin. I was able to successfully flash back to my original dump and boot the ps3. Good to know those dumps are in fact 100%.

I did notice that using the command writeword to rewrite my original flash.bin the writing was sluggish right up to the 8192 KB point. After that it flew through the last half of the file. I am guessing this has something to do with the first flash chip being written to and the second flash still being clean from the erase?

[judges]

Originally Posted by nortnil I did notice that using the command writeword to rewrite my original flash.bin the writing was sluggish right up to the 8192 KB point. After that it flew through the last half of the file. I am guessing this has something to do with the first flash chip being written to and the second flash still being clean from the erase?

This sounds more like the second half of the nor hasn't been erased at all. That's why the 2nd half of your patched flash couldn't be written, but your original dump could be written completely (actually there isn't any writing done, if the data from your flash file and the data on the nor are identical. That's why it's so fast, it's basically just reading).

You can try to erase your nor again, wait some minutes after erasure, power-cycle your ps3 and dump again. Check your dump. It should only contain 0xFF.

[nortnil]

Originally Posted by judges This sounds more like the second half of the nor hasn't been erased at all. That's why the 2nd half of your patched flash couldn't be written, but your original dump could be written completely (actually there isn't any writing done, if the data from your flash file and the data on the nor are identical. That's why it's so fast, it's basically just reading). You can try to erase your nor again, wait some minutes after erasure, power-cycle your ps3 and dump again. Check your dump. It should only contain 0xFF.

This is exactly what is happening. I did a erasechip, NORway no longer recognized the flash chip, repowered PS3 and plugged in USB cable, initiated another erasechip, repowered PS3 again, and dumped an erase.bin.

The .bin is half 0XFF and the other half original data. Is there anyway to force erasechip to get the second half? I tried telling it to erase at a specific offset, but it didn't seem to get the command.

[judges]

Originally Posted by nortnil This is exactly what is happening. I did a erasechip, NORway no longer recognized the flash chip, repowered PS3 and plugged in USB cable, initiated another erasechip, repowered PS3 again, and dumped an erase.bin. The .bin is half 0XFF and the other half original data. Is there anyway to force erasechip to get the second half? I tried telling it to erase at a specific offset, but it didn't seem to get the command.

After you did an erasechip, did you wait a couple of minutes before issuing any other command? Wait like 3 minutes and then do a "norway.py comx". It should recognize the chip. Maybe the function just thinks it's done with erasing, but actually it's still working.

You can also try a manual sector erase. Try "norway.py comx erase 0x800000". Dump afterwards and check whether the first couple of kb at 0x800000 have been erased.

[nortnil]

Originally Posted by judges After you did an erasechip, did you wait a couple of minutes before issuing any other command? Wait like 3 minutes and then do a "norway.py comx". It should recognize the chip. Maybe the function just thinks it's done with erasing, but actually it's still working. You can also try a manual sector erase. Try "norway.py comx erase 0x800000". Dump afterwards and check whether the first couple of kb at 0x800000 have been erased.

I did wait a bit, but I didn't wait a full 3 minutes. Each time it was telling me it took around 45 seconds to actually erase. Through persistence I was able to get it to do a full erase that took a minute and a half. That resulted in a completely erased dumped. I was able to successfully write the downgrade.bin I created earlier. It was in fact incorrect, but I got your message on how to properly set everything up. I will try again tonight and post back.

Thanks for the heads up on the erase and then offset. For some reason I was using erasechip offset. If I run in to trouble again I think that will be most helpful.