[jarmster]

swap drives, format drive....the 3.55 core_os has hdd_copy it writes to the hdd.

---just a though

[WalangAlam]

Originally Posted by judges I stand corrected. Of course you can go back to 3.6x if you use the flasher.

Hmm I was actually going to ask this. Got confused and had doubts when you said we can't go back to 3.6 if we downgrade to 3.55. So we could upgrade and downgrade several times by flashing our original dump right?

[butnut]

Originally Posted by calimba same error with the 0.2 version C:\....\teensy>NORway.py COM3 write flash.bin Pinging... Set SB to tristate STATUS_DRIVE: False STATUS_TRIST_N: True STATUS_RESET_N: True STATUS_READY: True STATUS_CE_N: False STATUS_WE_N: True STATUS_OE_N: True Resetting NOR... Ready. Sector 000000 (1/128) [M]... Traceback (most recent call last): File "C:\....\teensy\NORway.py", line 320, in <module> n.writerange(addr, data) File "C:\....\teensy\NORway.py", line 210, in writerange self.writesector(addr/2, data[:0x20000]) File "C:\....\teensy\NORway.py", line 177, in writesector raise NORError("Verification failed") __main__.NORError: Verification failed

I am having this same problem. How did you make it work?

[WalangAlam]

Does the length of the wires have any effect in the reading and flashing of nor? I'm planning to place the teensy outside the ps3 shell, make socket or something so I can plug and unplug the teensy outside the shell. Or maybe cut the wires in the middle and solder them again if I need to reflash.

nvm. I checked marcan post it seems ok.

[Dumbelek]

can anyone confirm this, patched CORE_OS_PACKAGE.pkg is very different (comparing byte by byte) from the decrypted original CORE_OS_PACKAGE.pkg. So before flash my nor can you pls check this out? Looks like when packing CORE_OS_PACKAGE.pkg file order changing (assuming).

These 2 pkgs must be the same byte by byte. (am i wrong?)
dCOS.pkg : decrypted,unpacked,unselfed,no change,selfed,packed "CORE_OS_PACKAGE.pkg"
odCOS.pkg : decrypted "CORE_OS_PACKAGE.pkg"

[toxie]

Originally Posted by WalangAlam Does the length of the wires have any effect in the reading and flashing of nor?

The length of the wires do have effect on reading and writing.
Correct me if i`m wrong, but by my oppinion the wire length up to 15-20" should be ok.

[jarmster]

Thats a bit long, lol
20" is damn near 2 feet

[judges]

Originally Posted by butnut I am having this same problem. How did you make it work?

He told me that he only got that error when the bluray drive was disconnected. Don't know whether it's related..
************* [ - Post Merged - ] *************

Originally Posted by Dumbelek can anyone confirm this, patched CORE_OS_PACKAGE.pkg is very different (comparing byte by byte) from the decrypted original CORE_OS_PACKAGE.pkg. So before flash my nor can you pls check this out? Looks like when packing CORE_OS_PACKAGE.pkg file order changing (assuming).

Yes, it's "very" different. Yes, file order is different. Have a look at the source if you want to know in detail: http://git.dashhacks.com/allps3tools...tools/cospkg.c
************* [ - Post Merged - ] *************

Originally Posted by WalangAlam Hmm I was actually going to ask this. Got confused and had doubts when you said we can't go back to 3.6 if we downgrade to 3.55. So we could upgrade and downgrade several times by flashing our original dump right?

Yes, you can.

[butnut]

Originally Posted by judges He told me that he only got that error when the bluray drive was disconnected. Don't know whether it's related..

I connected my bluray drive but I still get the same error.

The firmware dumps just fine but I can't write...

[jarmster]

Ok i got some wire today and layed it out. If your installing like judges, (which is a nice setup). You only need 10 inches to start. 10 inches is plenty as you can see