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!

Follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 CFW forums for the latest PlayStation 3 scene and PS4 Hacks & JailBreak updates with PlayStation 4 homebrew.

#72 - Ares1983 - January 18, 2011 // 4:56 pm
Ares1983's Avatar
I succesfully downgraded my PS3 Slim (CHECH2004B Datecode:9C) today from FW 3.55 to FW 3.41 with the use of this thread & ecliPS3 (Woot!!) I noticed that my PS3 didn't switch off automatically when i activated the factory service mode, manually it did & worked as usual.

Many, many thanks for givin' me back control over my own console. Sony should back off as long as they SELL consoles. Acting up like they rent them...

#71 - ps3haze - January 18, 2011 // 6:07 am
ps3haze's Avatar
Well that is not really 'your own way' that is how the actual downgrade works

But I understand why you thought that, I've been reading for days and it is hard to put all the info together in one place. But that is exactly what you need to do.

When you downgrade from 3.55 you actually upgrade to 3.56 which is a 3.41 spoof. Then after you use the old 3.50 downgrade to bring it to 3.41 using the modified pup. After that you can use the recovery menu to force flash OFW 3.41 on the PS3 and then ur done. Long way around but it works...

happy downgrading everyone.

#70 - roochops - January 18, 2011 // 6:01 am
roochops's Avatar
i am having trouble, i have a PSBreak dongle and have downgraded from 3.55 to 3.41 and seems ok.

i don't have an install option in the game menu, and have been told that i have only downgraded not jailbroken.

how can i jailbreak? do i need a mHex file?

can you help?


#69 - kakashimario5 - January 18, 2011 // 4:49 am
kakashimario5's Avatar
exactly how can i use a android phone as a downgrade dongle?

i have the htc evo 4g. so how can i use my android phone as a downgrade dongle?

#68 - dyceast - January 17, 2011 // 11:28 am
dyceast's Avatar
Is ths "downgrader dongle," just psgrade? The same file to downgrade 3.50 ?

#67 - dno1 - January 17, 2011 // 7:44 am
dno1's Avatar
Quote Originally Posted by dno1 View Post
I just did a downgrade but I can not update anymore. I get the error code: 8002F169

What does this mean? and how can I fix this?

I made my own way to update after downgrade: Downgrade normally with 3.55 downgrade pack. After being downgraded 'downgrade/reinstall' the 3.41 pup file from the 3.50 downgrade pack.

After this pup is installed you can update again

#66 - churchill12 - January 16, 2011 // 6:09 pm
churchill12's Avatar
Can i use any usb-stick or do i need a special kind of usb-stick. because the green led is on for 1 second it doesn't have time to read anything.

it doesn't work with my normal usb-stick.

#65 - jpnn80 - January 16, 2011 // 5:21 pm
jpnn80's Avatar
Just do the downgrade process to 3.41 with those old files:

#64 - churchill12 - January 16, 2011 // 4:12 pm
churchill12's Avatar
I have the same problem as you can you tell me how i can get into the normal state?

i can't find the tip from red 13 on page 6...

#63 - jpnn80 - January 16, 2011 // 7:20 am
jpnn80's Avatar
Quote Originally Posted by maxwell200072 View Post
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.

Unfortunately it does not in my case, as after I downgraded to 3.41 spoofing 3.56, and tried to reupdate to OFW 3.55, my PS3 started to blink the green light without completing the update.

Now each time I restart it, even with the OFW 3.55 and Lv2diag.self plugged in usb for downgrade, my PS3 just lights on with green for a few sec, then shuts down in red.

Does anyone know if and how I can get to receovery menu from the state my ps3 is in ?

ok never mind, thanks to Red 13 tip on page 6 to use old files for downgrade, I was able to take back my ps3 in running state, and then I could even reupdate to OFW 3.55 through system menu, without getting the error code 8002F169 mentioned by dno1 on page 4 after having used the new files for downgrade.

So if the old files allow to reupdate to 3.55 unlike the new ones, what's the point in using the latter ?