Hi guys,
I decided to try to flash my old skool phat PS3 (CHECHC03 - 60GB - NAND) today using the tools on ps3exploit.
I was about to lay out the steps I took - which were all correct as far as I could tell - but then when double checking a few things I came across something really strange, and obviously the reason for the brick.
Basically, I am certain I copied the flash_485.hex from from the 'NOR_NAND_writer_release_2.0.2_PS3Xploit' release zip (taken from the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) site) to the root of my USB stick (I hadn't downloaded any other version).
I updated my console to 4.85 HFW and then followed the steps to flash the 'flash_485.hex' to the NAND via
http://**ps3xploit.com >Domain no L...ps3xploit.me =new)/hfw/writer/index_nand.html
This was a success and completed fine. I then did a NAND dump.
However, I just checked the MD5 of the flash_485.hex on the USB stick and it's:
87EDEDE8D72530CD4951A16C2B2335F1
NOT 2D74B066E7453E6B1336E36C410FB1EB as it should be!
The thing is, the file in the releases zip that I copied it from DOES show that correct MD5!?
The odd thing though is the date and time of the one from the releases zip is 31st of August 2019, 09:20:43...
The date and time of the one I copied to the USB stick is 31st of August 2019, 09:20:44!! One second later.
They are exactly the same size.
I am baffled what has happened here unless some very odd file corruption took place when copying!?
Anyway, after powering down the console it will now not power up - getting stuck with a flashing red light so it's hard bricked (I am assuming). Gutted.
From what I'm reading I have very few options here other than to just get a new one and maybe sell this one for parts? I know there are hardware flasher options but not sure if that would be viable here with only having a .hex dump AFTER the flash writing stage?
I know I'm basically screwed but thought I'd ask - especially on the very strange MD5 / date anomaly.
Thanks, and thanks to everyone who has worked on these incredible exploits. I was so close to success though a *huge* reminder to double check everything - especially MD5 hashes!!
Just to add, it is most definitely a dodgy USB stick. The MD5 changes whenever the stick is mounted! Windows have found errors on it as well. Typical as I only changed to it from a 16GB stick as the initialisation phase kept failing on the writer page.
Live and learn...
I decided to try to flash my old skool phat PS3 (CHECHC03 - 60GB - NAND) today using the tools on ps3exploit.
I was about to lay out the steps I took - which were all correct as far as I could tell - but then when double checking a few things I came across something really strange, and obviously the reason for the brick.
Basically, I am certain I copied the flash_485.hex from from the 'NOR_NAND_writer_release_2.0.2_PS3Xploit' release zip (taken from the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) site) to the root of my USB stick (I hadn't downloaded any other version).
I updated my console to 4.85 HFW and then followed the steps to flash the 'flash_485.hex' to the NAND via
http://**ps3xploit.com >Domain no L...ps3xploit.me =new)/hfw/writer/index_nand.html
This was a success and completed fine. I then did a NAND dump.
However, I just checked the MD5 of the flash_485.hex on the USB stick and it's:
87EDEDE8D72530CD4951A16C2B2335F1
NOT 2D74B066E7453E6B1336E36C410FB1EB as it should be!
The thing is, the file in the releases zip that I copied it from DOES show that correct MD5!?
The odd thing though is the date and time of the one from the releases zip is 31st of August 2019, 09:20:43...
The date and time of the one I copied to the USB stick is 31st of August 2019, 09:20:44!! One second later.
They are exactly the same size.
I am baffled what has happened here unless some very odd file corruption took place when copying!?
Anyway, after powering down the console it will now not power up - getting stuck with a flashing red light so it's hard bricked (I am assuming). Gutted.
From what I'm reading I have very few options here other than to just get a new one and maybe sell this one for parts? I know there are hardware flasher options but not sure if that would be viable here with only having a .hex dump AFTER the flash writing stage?
I know I'm basically screwed but thought I'd ask - especially on the very strange MD5 / date anomaly.
Thanks, and thanks to everyone who has worked on these incredible exploits. I was so close to success though a *huge* reminder to double check everything - especially MD5 hashes!!
Just to add, it is most definitely a dodgy USB stick. The MD5 changes whenever the stick is mounted! Windows have found errors on it as well. Typical as I only changed to it from a 16GB stick as the initialisation phase kept failing on the writer page.
Live and learn...
Last edited by a moderator: