Dual Firmware

From PS3 Developer wiki
Jump to: navigation, search

Hardware Based[edit]

NOR/Nand Piggybacking[edit]

This method involves physically soldering another flash chip ontop of the existing flash packages, soldering the legs pin for pin (piggybacking). You will lift both #CE pins and provide a switch between them to select the appropriate flash chip, of which each will have a different firmware.

E.g.: http://www.elotrolado.net/hilo_la-dual-nand-fat40g-ya-es-una-realidad_1650176 / http://www.ps3hax.net/2011/07/dual-ps3-nand-on-40gb-phat-ps3-working/

other example (non PS3) : http://electro-music.com/forum/post-85678.html#85678

Reset pin for NOR[edit]

After looking into this some more, Simply switching the #CE pin may not be sufficient as the chip is still operating and can interfere with the bus. However, it appears that whilst the #reset pin is tied low, all input/output pins on the flash are in a state of high-impedance. We should be able to simply ground this pin to disable that chip, rather than lifting the #CE pin.

EDIT: it seems it is sufficient to use only CE# as several tests (some on this very same page) prove.

more than 2 (virtually limitless)[edit]

Theoretical there is no limit to the amount of flashchips you can stack and CE switch (practical limit is the space to stack, length of wiring and real use for that many FW versions). Using a 48 step rotaryswitch and stacking 47 Flashchips (1x47 for NOR / 2x 1x47 for NAND) parallel to the original one, its even possible to make a 48-boot system (just remember you have to have a seperate harddrive for every selected flash firmware version).


This method relies on the fact that SYSCON has 2 EEPROM banks, and a "recovery mode" flag that can be set to load a recovery firmware located in the ros0 region of the flash.

By pulling the backup_mode pin low or high, you can aparently switch eeprom banks in the SYSCON EEPROM. In the second bank, you would have the recovery mode flag set, thus loading firmware from the ros0 region on flash.

Increased size NOR Flash[edit]

This method relies on entirely lifting the existing NOR flash chip and planting a 256mbit chip, you could lift Address pin 23 and have a switch to tie this low or high to switch banks. A compatable samsung k8p5615uqa chip (datasheet)

This looks like it could work, as per the spansion and samsung charts, when using autoselect commands etc, it does not care about the state of pin 23. So there should not be any interference.


128mbit and 256mbit chips don't have the same ProductID.

This ID can easily checked by SONY to avoid the principle even if the VendorID is the same.

VendorID = Unique manufacturer ID

ProductID = Unique device ID

ie. :

SPANSION S29GL128P - VendorID = 0x01 & ProductID = 0x7E 0x21 0x01

SPANSION S29GL256P - VendorID = 0x01 & ProductID = 0x7E 0x22 0x01


Firmware hash checks[edit]

Firmware hash checks are located on SYSCON EEPROM, aparently these checks are run within Indi info manager on LV1. These compare the hashes stored in syscon with the files stored on flash. If the checks fail, the console does not boot (RLOD). We could get around this by using dual-banking on SYSCON or by patching the checks out.


Only a single version of VFlash is stored on flash in NAND consoles, and a single copy is stored at the beginning of the PS3 hard drive on NOR consoles. Because the firmware stored here doesn't match that stored on flash, you would have to reinstall the rest of firmware everytime you switch. We could possibly overcome this limitation by patching the storage manager to redirect vflash to another region of the hard disk.

Software based[edit]

Using graf_chokolo's payload[edit]

In graf_chokolo payloads, there is a payload that can be used to load an alternative lv2_kernel.self

You have to save the alternative lv2_kernel.self on flash and use the payload to make lv1 load it.

See Graf's PSGroove Payload

Quoting graf_chokolo

Guys and be careful with store_file_on_flash.c and replace_lv2.c payloads. 
With store_file_on_flash.c i’m able to store a new file on FLASH memory where CORE OS files are stored from PUP. 
If you do not know what that means then don’t play with this, it could brick your PS3, but it’s safe to use when you know what you do.
With both of those payloads i’m able to boot a patched lv2_kernel.self from FLASH without flashing PUP, i just store a second lv2_lernel.self
on FLASH, then patch System Manager in HV which is reponsible for booting GameOS and boot custom LV2 kernel from 3.41. 
You don’t need NOR flasher if something goes wrong:
just reboot HV and your original lv2_kernel.self will be booted again

The same way you could boot lv2_kernel.self from dev_flash. 
Just patch path to lv2_kernel.self in System Manager and point it to lv2_kernel.self stored on dev_flash


  • Same as above and this could ONLY be used with a lv2_kernel.self compatible with you actual lv1.self
  • You can only customize lv2_kernel.self and below


There is master hardware based different for every PS3. It is said that some have managed to get ahold of it. Being able to sign in a higher privilege would give us the ability to create a bootloader that would allow us to load any firmware previously patching it.

This would be the best solution, having a bootmii like bootloader with recovery options, but it is also the most farfetched.

Manual dualboot 3.55 & 4.x with 2 flashdumps and 2 harddrives[edit]

(old longer guide is on talkpage)

Preparation in short[edit]

Getting original and downgrade to 3.55[edit]

  1. Dump the flash and make sure it is useable for downgrade to 3.55
  2. Patch it for downgrade
  3. Reinstall (Factory Service Mode) the prepatched PUP (e.g. Rogero V3.7 (mirror / MD5:8f8166b25d6bed891f292c77de5c4b28)

for noFSM, use 9.99 downgrader instead: MD5:b67747f529d047d63151786544a58b50 ) and reboot (normal mode) to make sure it works fine

  1. Redump the flash to make sure it has filled both ROS0 and ROS1 (they will differ as one will be the prepatched from the previous step, while the other will contain CoreOS from the installed PUP) and keep this as '3.55-swap.bin' together with the used harddrive '3.55.HDD'.

Getting latest[edit]

  1. Update (normal or recovery mode) to the latest firmware you want to use (e.g. 4.x) and reboot (normal mode) to make sure it works fine
  2. Dump the flash and keep this as '4.x-swap.bin' together with used different harddrive '4.x.HDD'.


When you want to boot to 3.55[edit]

  1. Reflash '3.55-swap.bin' and insert harddrive '3.55.HDD'.

When you want to boot to 4.x[edit]

  1. Reflash '4.x-swap.bin' and insert harddrive '4.x.HDD'.

Swap Solutions[edit]

Solutions for swapping/connecting the flash[edit]


Ghetto rigs[edit]

TSOP Clip/Probe[edit]

TSOP sockets[edit]



TSOP Clip/Probe[edit]

TSOP sockets[edit]

Solutions for swapping / externalise the harddrive[edit]

Internal tray with eSATA connector[edit]

External cradle with SATA uplink[edit]

Remember: You still need an eSATA (cradle) to SATA (PS3) cable

DIY / cheap solutions[edit]

Alot of the above mentioned solutions can be made DIY.

SATA Switches[edit]

Switching SATA harddrives:

RAID enclosures with eSATA port[edit]

they must serve the storage as uniform storage device on a single port (not software RAID, relying on host)

Not useable devices[edit]

Devices that state that host must support Port Multiplier (PM) specifications won't work, e.g.

Publications based on this article page[edit]