Littlebalup's Dual Boot firmwares

PS3 Littlebalup's 4.92 Dual Boot firmwares -

littlebalup

Developer
PSX-Place Supporter
cd_blocked-jpg.25433


  • Littlebalup's 4.92 Dual Boot firmwares

    Those firmwares only of use for current PS3 Custom Firmware user's was an idea originally crafted by @habib several years ago. The purpose was to give Custom Firmware user's a safe way to go online (such as playing your disc based games) without a risk of a ban for using a Custom Firmware.

    The Dual Boot (DB) firmware is nothing else but an Official Firmware (OFW) . The ONLY difference is that you can RETURN and INSTALL a (4.92+) CFW directly (without having to flash your NOR/NAND again). So this is only useful for those existing CFW user's. To review, basically you install this PUP when you want to be official (for doing things like using PSN) and then re-install your CFW PUP when you want your custom firmware abilities back, such as launching homebrew.

    The Dual Boot & Hybrid (DBH) firmware is nothing more than a Dual Boot firmware which includes the exploitable web browser. So the exploits (like HEN, flash writer,...) can be used. Or otherwise said, it is similar to an Hybrid Firmware (HFW) but with the ability to return to a CFW.

    Code:
    PUP MD5: A4BD118B52A8AC04E2E802B66AAD72FD
    
    
    Compatibility:
      Any PS3 already running a CEX custom firmware
    
    
    Features:
      - Made from 4.92 OFW (CEX)
      - All the features of the 4.92 OFW (CEX)
      - Same CoreOS files size and structure than OFW
      - Same PUP size and structure than OFW
      - Patched isoldr and spu_pkg_rvk_verifier to allow installation of any 4.92 or higher CFW (CEX)
      
      
    Installation:
      - Rename the "DB_4.92_littlebalup.PS3UPDAT.PUP" file as "PS3UPDAT.PUP"
      - On a FAT32 formatted USB storage device, create a folder named "PS3". Within that PS3 folder, create another folder named "UPDATE".
      - Copy the "PS3UPDAT.PUP" file to the UPDATE folder you just created.
      - Verify the MD5 signature of the "PS3UPDAT.PUP" file you just copied in the UPDATE folder.
      - Plug the USB storage device to your PS3 then install via [Settings] -> [System Update] -> [Update via Storage Media]
      - Follow the on screen instructions.

    Code:
    PUP MD5: 3C14A062FC7C60B8C195FA632BA6522A
    
    
    Compatibility:
      Any PS3 already running a CEX custom firmware
    
    
    Features:
      - Made from HFW 4.92.1 (esc0rtd3w Official)
      - All the features of the 4.92 OFW (CEX)
      - Contains exploitable webkit for e.g. HEN installation
      - Same CoreOS files size and structure than OFW
      - Patched isoldr and spu_pkg_rvk_verifier to allow installation of any 4.92 or higher CFW (CEX)
      
      
    Installation:
      - Rename the "DBH_4.92_littlebalup.PS3UPDAT.PUP" file as "PS3UPDAT.PUP"
      - On a FAT32 formatted USB storage device, create a folder named "PS3". Within that PS3 folder, create another folder named "UPDATE".
      - Copy the "PS3UPDAT.PUP" file to the UPDATE folder you just created.
      - Verify the MD5 signature of the "PS3UPDAT.PUP" file you just copied in the UPDATE folder.
      - Plug the USB storage device to your PS3 then install via [Settings] -> [System Update] -> [Update via Storage Media]
      - Follow the on screen instructions.

    Download: Littlebalup Dual Boot 4.92
    Download: Littlebalup Dual Boot & Hybrid 4.92



  • Littlebalup's 4.91 Dual Boot firmwares

    Those firmwares only of use for current PS3 Custom Firmware user's was an idea originally crafted by @habib several years ago. The purpose was to give Custom Firmware user's a safe way to go online (such as playing your disc based games) without a risk of a ban for using a Custom Firmware.

    The Dual Boot (DB) firmware is nothing else but an Official Firmware (OFW) . The ONLY difference is that you can RETURN and INSTALL a (4.91+) CFW directly (without having to flash your NOR/NAND again). So this is only useful for those existing CFW user's. To review, basically you install this PUP when you want to be official (for doing things like using PSN) and then re-install your CFW PUP when you want your custom firmware abilities back, such as launching homebrew.

    The Dual Boot & Hybrid (DBH) firmware is nothing more than a Dual Boot firmware which includes the exploitable web browser. So the exploits (like HEN, flash writer,...) can be used. Or otherwise said, it is similar to an Hybrid Firmware (HFW) but with the ability to return to a CFW.

    Code:
    PUP MD5: 01F196151B007D003D35746C81AAA98C
    
    
    Compatibility:
      Any PS3 already running a CEX custom firmware
    
    
    Features:
      - Made from 4.91 OFW (CEX)
      - All the features of the 4.91 OFW (CEX)
      - Same CoreOS files size and structure than OFW
      - Same PUP size and structure than OFW
      - Patched isoldr and spu_pkg_rvk_verifier to allow installation of any 4.91 or higher CFW (CEX)
     
     
    Installation:
      - Rename the "DB_4.91_littlebalup.PS3UPDAT.PUP" file as "PS3UPDAT.PUP"
      - On a FAT32 formatted USB storage device, create a folder named "PS3". Within that PS3 folder, create another folder named "UPDATE".
      - Copy the "PS3UPDAT.PUP" file to the UPDATE folder you just created.
      - Verify the MD5 signature of the "PS3UPDAT.PUP" file you just copied in the UPDATE folder.
      - Plug the USB storage device to your PS3 then install via [Settings] -> [System Update] -> [Update via Storage Media]
      - Follow the on screen instructions.

    Code:
    PUP MD5: 310D64F26382E2B1AA4377D33A3C2FE2
    
    
    Compatibility:
      Any PS3 already running a CEX custom firmware
    
    
    Features:
      - Made from HFW 4.91.1 (Joonie Official)
      - All the features of the 4.91 OFW (CEX)
      - Contains exploitable webkit for e.g. HEN installation
      - Same CoreOS files size and structure than OFW
      - Patched isoldr and spu_pkg_rvk_verifier to allow installation of any 4.91 or higher CFW (CEX)
     
     
    Installation:
      - Rename the "DBH_4.91_littlebalup.PS3UPDAT.PUP" file as "PS3UPDAT.PUP"
      - On a FAT32 formatted USB storage device, create a folder named "PS3". Within that PS3 folder, create another folder named "UPDATE".
      - Copy the "PS3UPDAT.PUP" file to the UPDATE folder you just created.
      - Verify the MD5 signature of the "PS3UPDAT.PUP" file you just copied in the UPDATE folder.
      - Plug the USB storage device to your PS3 then install via [Settings] -> [System Update] -> [Update via Storage Media]
      - Follow the on screen instructions.

    Download: Littlebalup Dual Boot 4.91
    Download: Littlebalup Dual Boot & Hybrid 4.91



  • Littlebalup's 4.90 Dual Boot firmwares

    Those firmwares only of use for current PS3 Custom Firmware user's was an idea originally crafted by @habib several years ago. The purpose was to give Custom Firmware user's a safe way to go online (such as playing your disc based games) without a risk of a ban for using a Custom Firmware.

    The Dual Boot (DB) firmware is nothing else but an Official Firmware (OFW) . The ONLY difference is that you can RETURN and INSTALL a (4.90+) CFW directly (without having to flash your NOR/NAND again). So this is only useful for those existing CFW user's. To review, basically you install this PUP when you want to be official (for doing things like using PSN) and then re-install your CFW PUP when you want your custom firmware abilities back, such as launching homebrew.

    The Dual Boot & Hybrid (DBH) firmware is nothing more than a Dual Boot firmware which includes the exploitable web browser. So the exploits (like HEN, flash writer,...) can be used. Or otherwise said, it is similar to an Hybrid Firmware (HFW) but with the ability to return to a CFW.

    Code:
    PUP MD5: 04EC80EDD3ED40359D203BFF3B28F608
    
    
    Compatibility:
      Any PS3 already running a CEX custom firmware
    
    
    Features:
      - Made from 4.90 OFW (CEX)
      - All the features of the 4.90 OFW (CEX)
      - Same CoreOS files size and structure than OFW
      - Same PUP size and structure than OFW
      - Patched isoldr and spu_pkg_rvk_verifier to allow installation of any 4.90 or higher CFW (CEX)
     
     
    Installation:
      - Rename the "DB_4.90_littlebalup.PS3UPDAT.PUP" file as "PS3UPDAT.PUP"
      - On a FAT32 formatted USB storage device, create a folder named "PS3". Within that PS3 folder, create another folder named "UPDATE".
      - Copy the "PS3UPDAT.PUP" file to the UPDATE folder you just created.
      - Verify the MD5 signature of the "PS3UPDAT.PUP" file you just copied in the UPDATE folder.
      - Plug the USB storage device to your PS3 then install via [Settings] -> [System Update] -> [Update via Storage Media]
      - Follow the on screen instructions.

    Code:
    PUP MD5: F059690E24A308FE98AF401CF037A793
    
    
    Compatibility:
      Any PS3 already running a CEX custom firmware
    
    
    Features:
      - Made from 4.90 OFW (CEX)
      - All the features of the 4.90 OFW (CEX)
      - Contains exploitable webkit for e.g. HEN installation
      - Same CoreOS files size and structure than OFW
      - Patched isoldr and spu_pkg_rvk_verifier to allow installation of any 4.90 or higher CFW (CEX)
     
     
    Installation:
      - Rename the "DBH_4.90_littlebalup.PS3UPDAT.PUP" file as "PS3UPDAT.PUP"
      - On a FAT32 formatted USB storage device, create a folder named "PS3". Within that PS3 folder, create another folder named "UPDATE".
      - Copy the "PS3UPDAT.PUP" file to the UPDATE folder you just created.
      - Verify the MD5 signature of the "PS3UPDAT.PUP" file you just copied in the UPDATE folder.
      - Plug the USB storage device to your PS3 then install via [Settings] -> [System Update] -> [Update via Storage Media]
      - Follow the on screen instructions.

    Download: Littlebalup Dual Boot 4.90
    Download: Littlebalup Dual Boot & Hybrid 4.90



  • Tested in:
    • CECH-2004B
    • CECHC04
 
Last edited:
question: with a DB is there a priority on which fw is the coldboot firmware? i'm interested in running this if i can always coldboot to cfw, but run ofw only in the few instances i want to sync trophies and such. does it matter which fw you set as your primary fw? thanks.
 
question: with a DB is there a priority on which fw is the coldboot firmware? i'm interested in running this if i can always coldboot to cfw, but run ofw only in the few instances i want to sync trophies and such. does it matter which fw you set as your primary fw? thanks.

DB 4.90 is an OFW that allows to *reinstall* CFW without having to use PS3Xploit Flash Writer 4.90 again.
DBH 4.90 is same as above, but HFW. It allows to install HEN, HAN, PS3Xploit tools, etc. Reinstall CFW when you want.

boot_fake_ofw_490.pkg is a MAMBA payload that boots your firmware with syscalls disabled like OFW, but you can return to CFW just entering to the System Update on XMB or re-enabling Cobra payload.

All these tools are intended for CFW only. HEN users cannot use any of them.
 
One question, for trophies sync, is Fake Boot process as safe as Dual Boot?

It is a different approach. Fake OFW payload is as safe as running CFW and disabling syscalls with R2+TRIANGLE.

Dual Boot firmware is technically a pure OFW which allows re-installation of CFW when needed.
You need to reinstall the firmware each time you need to switch between CFW and OFW, or swap HDD.
 
DB 4.90 is an OFW that allows to *reinstall* CFW without having to use PS3Xploit Flash Writer 4.90 again.
DBH 4.90 is same as above, but HFW. It allows to install HEN, HAN, PS3Xploit tools, etc. Reinstall CFW when you want.

so in other words, if my entire gaming setup is only running ISOs i've ripped with multiman, then db is probably not the option for me?? because it seems like the coldboot default here is ofw, which disables homebrew.

(for context: i'd been running cobra cfw since 4.88, but i've been running hen for what feels like the past 6 months, because i installed ofw on top of my cfw to sync some trophies, thinking i could just go back to cfw, only to find out that the bg website had been taken down after the fact, so for the past several months i've had to deal with having to activate hen every time i turn on the unit, and i just want a coldboot solution to go back to being able to run isos off the bat without having to do anything extra.)
 
so in other words, if my entire gaming setup is only running ISOs i've ripped with multiman, then db is probably not the option for me?? because it seems like the coldboot default here is ofw, which disables homebrew.
I think you misunderstood the term dualboot of this firmwares, when the console boots there is not a selector where you can choose to boot on DB firmware or CFW, thats not how it works

To make the jump in between the DB firmware and CFW you need to preform a complete firmware installation, and after that you only have one firmware

In other words... there is not a "coldboot default" because there is only 1 boot mode
The feature you thought about being able to boot the PS3 in 2 different firmwares (with a selector, a switch or whatever... and without need to install or rewrite any firmware file) is something that was discussed since many time ago but there is not any easy way to do it
 
I think you misunderstood the term dualboot of this firmwares, when the console boots there is not a selector where you can choose to boot on DB firmware or CFW, thats not how it works

To make the jump in between the DB firmware and CFW you need to preform a complete firmware installation, and after that you only have one firmware

In other words... there is not a "coldboot default" because there is only 1 boot mode
The feature you thought about being able to boot the PS3 in 2 different firmwares (with a selector, a switch or whatever... and without need to install or rewrite any firmware file) is something that was discussed since many time ago but there is not any easy way to do it

no i entirely get that you have to manually swap with a fresh re-install of the fw. i was just wondering if i can have my primary on board fw be the cfw, and swap (re-install) to ofw for the like once every 2 months i want to do that. he just made it sound like your primary fw would be ofw, but maybe i misread that.
 
There is no such thing here like "primary firmware" and "secondary firmware" because there is only one firmware. CFW called Dual Boot is OFW with the exception where patches was needed to be applied to allow user back to CFW without web exploiting. You can reinstall any other CFW and this CFW how often You like and how often write cycles on flash can handle. ;) If You will install OFW, You will be unable to install CFW again using only USB, including CFW Dual Boot.

You cannot switch between OFW and any CFW. And You cannot switch between let's called it "OFW mode" and "CFW mode" because it doesn't exist and cannot be made without serious hacking of boot loader, which no one yet ever made.
 
Last edited:
DB is really needed mainly for safe PSN access. It's not super common but people have been banned even with syscalls disabled. If you install DB and factory-reset your PS3 (thereby removing all traces of homebrew from your console) it should be nearly impossible for any game to tell the difference between that and OFW, even if the game itself scans your console looking for jailbreaks.
Well, you could say that since flash writer is locally hosted and can't just vanish without warning like bgtoolset then maybe just using OFW and reflashing again to go back to CFW is slightly safer as far as it comes to PSN... but slightly is the key word, and for that tiny bit of extra safety you'd have to reflash your console if you want to go back to CFW, which is never totally safe, e.g., you might end up with a brick if you were unfortunate enough to lose power during the flash process.
 
It is not needed to format drive. Just delete everything related to homebrew. Every pushlist, cache, db entry, custom folders etc.
 
Back
Top