PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!

Home PS4 News - Latest PlayStation 4 and PS3 News

January 13, 2011 // 8:12 pm - Just under a week ago we reported on news of a successful PS3 downgrade from 3.55 to 3.41 Firmware, however, it ended up not being reproducible until a PS3 3.55 to 3.41 Firmware Downgrader arrived today courtesy of solidpsycho through a guide from AmazingLarry.

Download: Lv2diag_355 / PS3 3.55 Downgrade (3.41)

To quote: Here is a patched 3.41 that allows you to downgrade. I patched the info0 to 356, and I also used Warrens method to bypass the br drive during the update. I have tested this on both of my PS3's and haven't run into any problems.

3.55 Downgrade has been confirmed on both FAT and SLIM consoles.

Please note you CANNOT use these files if you bought a PS3 that came stock with FW 3.50. DO NOT DO IT. STOP NOW.


You may want to download geo's 3.55-jb and install that and blackb0x ftp if you have not, it will be very useful for the next bit.

Blackb0x FTP server 1.2: Blackb0xFTP for 3.55 FW

If you have a fat PS3 with 256MB NAND you will need to back up your dev_flash folders, as you WILL LOSE BLURAY PLAYBACK. (on my FAT model i restored the DRL1 and DRL2 files in del_flash(2?) I did get to however keep all of my signed 3.55-jb homebrew, and it all works in retail mode except of course backup managers)

If you have a Small NAND SLIM or FAT console it would be a good idea to do one or both of the following:

In the XMB perform a system backup to save installed Homebrew you may have and gamesaves etc.. to an external device (i did this with my slim and it worked perfectly, all my installed signed homebrew from 3.55-jb works in retail 3.41 now)


make a COMPLETE backup of your HDD on your ps3 using ftp, although i dont think installed packages can be moved back over simply by ftp. i only tested the first method.

And now to downgrade:

You will need a downgrader dongle, search the forums for a DIY or buy one, or get an android/iphone, or an ipod nano, etc...

1) Unplug or switch off your console and then switch back on or plug back in.

2) While still OFF connect your Jailbreak/Downgrade device and press POWER then quickly Eject, you PS3 console should turn itself off automatically

3) OPTIONAL - Turn your PS3 on to verify you are in Service Mode (you will see a big red box, you can't miss it) then turn your PS3 back OFF

4) Place the lv2diag.self (FILE 1) from the archive and the PS3UPDAT.PUP (3.41 FW) from the archive on the root of a usb device and plug into the rightmost port on your console (dev_usb0)

5) Power on your PS3 with the usb device in and have a coffee, it can take a few moments for the PUP to install, your PS3 will turn off automatically

NOTE: if your system seems unresponsive and the light just stays green for ten minutes or more you need to use a different usb stick. i've had sporadic results with several different sticks.

6) Power your ps3 back on, you should still be in service mode, check your FW version now to verify you have downgraded successfully. Turn Off

7) Remove previous archive files from usb stick and now place lv2diag.self (FILE 2) on the root of your usb stick

8) Place usb stick in rightmost port of your PS3 (dev_usb0)

9) Turn PS3 back on with usb in place, it should turn itself off very shortly after.

10) Turn your PS3 back on and go through the configuration again.

5C3B09C7FB0655D3F8852D3AAD778025 PS3UPDAT.PUP (3.41 FW)
099F33A7967F99E91C07E870FD78B3DB Lv2diag.self (FILE 1)
7A20BFDAE65EEFB47A4425DB1B52DCDE Lv2diag.self (FILE 2)

All done!

Thanks mathieulh, solidpsycho, and everyone else.

Below is a video from PSGroove (linked above) and from Quakes69:

Log: Notice "os version = 03.4100" 8 lines from the bottom.

[Register or Login to view code]

Finally, from rms:
The downgrade process

Ok, so today's topic is on how the service mode updater works, and why it does what it does, and what the updater logs on /dev_usb000 mean.

[Register or Login to view code]

This means that the manufacturing_updater_for_reset.self file was started successfully, and it found a PS3 update file on the drive, and it set the polling interval so the SELF can retrieve the file using some poll() like function. Now, here's where updaters diverge. Older PS3s use NAND and newer PS3s use NOR and vFlash. vFlash is where the flash device is actually the hard disk. If vflash is enabled, you get this in the updater log:

[Register or Login to view code]

What this means, is that its creating 3 regions, 1 FAT16, that's where the dev_flash directory is, and one UFS partition, along with another raw. If you're using NAND, you'll see:

[Register or Login to view code]

What's happening here is that it's formatting /dev_flash, dev_flash2, and dev_flash3 as FAT16, and flagging the other 2 regions as ROS, both backup and current Core OS. If one uses NOR, they will see:

[Register or Login to view code]

What's happening is here that the regions on the hard disk are abstracted to the fake devices dev_flash2/3 and dev_flash, along with the 2 ROS regions. Remember, the header stays static, but the 7,340,000 byte part is replaced. ROS is never formatted. Then UPL.xml.pkg is read and then the updater enumerated which packages to install. It first starts with Package revoke, which is stored as trvk_pkg0/1 in NOR/NAND, then it updates Core OS, followed by VSH and all of the tarballs it has. Then, the updater updates the Bluray drive Revoke list which it calls "Bul-ray". Here's another place where the 2 PS3 types diverge:

[Register or Login to view code]

Here, we can see that the BD revoke list is also updated, but on NAND, since the dev_flash3 files were wiped, we have the out of sync situation. Then the program revoke list is flashed as trvk_prg0/1. On NOR consoles, the BD drive firmware is also flashed:

[Register or Login to view code]

After this BD firmware is also updated. Following that, MultiCard firmware is flashed, followed by Bluetooth firmware, then we see that the SYSCON is patched with the 4864 byte firmware update. Then, the updater does some postprocessing on the system to finalize firmware installation, then verifies the firmware. We then see the output of the log, the final installed system information, along with updater time:

[Register or Login to view code]

PS3 3.55 to 3.41 Firmware Downgrader is Now Available!

PS3 3.55 to 3.41 Firmware Downgrader is Now Available!

PlayStation Follow us on Twitter, Facebook and join us at our new site WWW.PSXHAX.COM!

#62 - moahmedkamal87 - January 16, 2011 // 6:46 am
moahmedkamal87's Avatar
what about if i have bought a ps3 with a 3.50 preinstalled, what do i have to do to play games not signed any help for that?

hackers are thinking in breaking the old consoles not thinking in breaking newer ones.

#61 - Omarion - January 16, 2011 // 4:27 am
Omarion's Avatar
Thanks for the help

#60 - maxwell200072 - January 16, 2011 // 4:22 am
maxwell200072's Avatar
Quote Originally Posted by Omarion View Post
If my Fat PS3 60Gb got bricked during the process, is there a way to fix it and go on with the process? or is it over for the console and it's useless? I haven't started with the downgrade yet cause I want to make sure that if something goes wrong, If I can go back and fix it or I will have to get a new PS3. Thanks in advance.

You should be able to put the original 3.55 fw and the first file of the downgrade (Lv2diag.self) on the root of usb and reinstall if something goes wrong. I have already tested it worked for me. hope that helps.

#59 - Omarion - January 16, 2011 // 3:44 am
Omarion's Avatar
If my Fat PS3 60Gb got bricked during the process, is there a way to fix it and go on with the process? or is it over for the console and it's useless? I haven't started with the downgrade yet cause I want to make sure that if something goes wrong, If I can go back and fix it or I will have to get a new PS3. Thanks in advance.

#58 - PS4 News - January 16, 2011 // 3:33 am
PS4 News's Avatar
See here for them, some mirrors may be dead but others work:

#57 - jpnn80 - January 16, 2011 // 3:26 am
jpnn80's Avatar

Could you tell me where to get the old modified downgrade 3.41 PUP and the old "Lv2diag" ?

#56 - MakeItRain896 - January 16, 2011 // 12:34 am
MakeItRain896's Avatar
if i have a 160gb Slim ps3 model CECH-2511A and came with fw 3.41 pre-installed, could this work??

#55 - Red 13 - January 15, 2011 // 9:03 pm
Red 13's Avatar

I had some of the same problems, flashing green power light, then red. Then i went back and read some more, i was using the wrong pup, the old modified 3.41... When i used the new modified pup, every thing worked perfect

But i wanted to install the original 3.41, true the recovery menue. But that didn't work, because the pup used to do this downgrade is fw 3.41 signed as fw 3.56. Probably to get the fw3.55 to accept it.

But this was easy to fix, i just used the old modifyed downgrade fw3.41 pup, and the old "Lv2diag".

So no i am able to "update" to the originale fw 3.41 true the recovery menue. And update to newer fw than 3.41, tru the XMB, if that is needed.

#54 - picman12c508 - January 15, 2011 // 8:16 pm
picman12c508's Avatar
I have a E3 Card reader , and am on 3.55GEO CFW , i have the new 3.55 LV2diag files , and 3.41 PUP files , do i just use the same e3 .bin file i used to put 3.50 into service mode or do i need a new e3 file?

Many Thanks.

OH BTW: my PS3 Slim came with 3.40 on it. so afaik it should be ok.

#53 - MrCoolSpan - January 15, 2011 // 1:04 pm
MrCoolSpan's Avatar
I got it to work, I had to use another..