Updated the system version spoof to 4.25 to prevent accidental system updates --> at least from Game Discs ( internet/Sony communication is not blocked to allow future PSN access addition if possible, that's why you see the Update message when you try to Log-In to PSN ) so if anyone Insists to Update... go ahead, it's possible...
Please note that this CFW is an update to v:3.4 , it doesn't have any 3.56/3.60 keys like the EXPERIMENTAL CFW v:3.5
It is so stable and doesn't have any problem with Blu-Ray discs playback because the loaders are not patched like they are in v:3.5
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
While there are different models of the Nor and progskeet initially fit well only with some models, the guys are doing a great job raising the compatibility, creating management software as best as Winskeet and verifying all the problems that may arise, solving them as Roger has done like yesterday along with the help of other guys. (eussNL, etc.).
To quote: Last night I had the chance to try and downgrade a Slim Ps3 (JSD-001 board with Spansion NOR) version 3.70 to CFW 3.55 using Dospiedra's downgrade v2 patches.
I managed to get a clean dump of the NOR using my ProgSkeet (latest QT port used), created a patched Downgrade.bin image using the 6 patched files from Dospiedra and a hex editor, then I flashed the image to the PS3 NOR, dumped the NOR another time and verified that all was written fine.
Then I continued with the normal downgrade procedure, go into service mode, update using the 3.55_no_check.PUP, then exit service mode and all was good, it was back into CFW 3.55.
Here the problems started, I tried to start a game and I got the famous Trophy error, so I decided to update it to my personal Modified Firmware, so I started the update and after installing the firmware, the PS3 turned off by itself, I tried to turn it on again, It turned on for almost 2 or 3 seconds then turned off completely (No Screen Output, No Red Led either) so I knew-ed at this point that the PS3 was Bricked
N.B: this was never mentioned in any of the downgrade tutorials floating on the net, although this is a very important point to warn the users who are downgrading their Ps3 machines not to update using usual Modified firmwares unless the firmware have the LV1.self file patched to Disable all checks, anything else will result into a Bricked PS3, and this is not good at all especially if the Hardware flasher used to downgrade was removed from the Ps3's NOR or Nand Flash.
After doing some research and discussing the issue with my friend eussNL