Littlebalup's Dual Boot firmwares

PS3 Littlebalup's 4.92 Dual Boot firmwares -

There's no issue installing DB 4.91 from CFW 4.90.
Depends on how you define losing your jailbreak. DB is 99.9% identical to OFW, so it will not allow you to run homebrew, backups or anything that real OFW doesn't allow, so in that sense, yes, you lose the jailbreak. However, unlike real OFW, you will be able to reinstall CFW without going through bgtoolset again, so in that sense you don't lose the jailbreak - it's just one PUP install away.
DB, being virtually identical to OFW, will not allow you to set the QA flag, therefore you can't downgrade to 4.90 directly, however you can switch to 4.91 CFW and then set the QA flag and downgrade to 4.90 if you wish. Not that there's any reason to.
Alright, thank you for your reply! I thought I'd be worse like doing all the process of the Ps3Xploit website all again! I was planning to sync my trophies before updating to CFW 4.91, but I guess I'll rather still waiting for CFW 4.91.2... Still useful info! Now, I'll keep this in mind in the future. I appreciate it!
 
Alright, thank you for your reply! I thought I'd be worse like doing all the process of the Ps3Xploit website all again! I was planning to sync my trophies before updating to CFW 4.91, but I guess I'll rather still waiting for CFW 4.91.2... Still useful info! Now, I'll keep this in mind in the future. I appreciate it!
It's really not needed to flash DB just to sync trophies, you can just disable syscalls and sync - unless you have any hacked trophies, in which case flashing DB or even OFW will not help you - you must delete them if you want to avoid a ban.
 
It's really not needed to flash DB just to sync trophies, you can just disable syscalls and sync - unless you have any hacked trophies, in which case flashing DB or even OFW will not help you - you must delete them if you want to avoid a ban.
No, I don't have have any hacked trophies. I just want to be a bit cautious.
 
No, I don't have have any hacked trophies. I just want to be a bit cautious.
If syscalls are disabled then it doesn't really matter afaik, but it's your decision.

BTW a couple more trophies you have to delete first (even if you flash OFW / DB)
* If you've played pirated digital games (RAPs downloaded from the Internet) then you have to delete them. Syncing a trophy of a digital game that's not in your store purchase history is a dead giveaway that it's pirated and therefore that your console is modded.
* If you have played any beta or otherwise non-retail builds of games then you have to delete any trophies associated with those two. Reason is that sometimes the trophy list changes during development and this might lead to you trying to sync a trophy that doesn't exist in the final release, again giving you away as having a modded console. Also early betas sometimes use different product ids than the final build, meaning you'll be attempting to sync trophies of a game that doesn't even exist, which can also get you banned.
 
If syscalls are disabled then it doesn't really matter afaik, but it's your decision.

BTW a couple more trophies you have to delete first (even if you flash OFW / DB)
* If you've played pirated digital games (RAPs downloaded from the Internet) then you have to delete them. Syncing a trophy of a digital game that's not in your store purchase history is a dead giveaway that it's pirated and therefore that your console is modded.
* If you have played any beta or otherwise non-retail builds of games then you have to delete any trophies associated with those two. Reason is that sometimes the trophy list changes during development and this might lead to you trying to sync a trophy that doesn't exist in the final release, again giving you away as having a modded console. Also early betas sometimes use different product ids than the final build, meaning you'll be attempting to sync trophies of a game that doesn't even exist, which can also get you banned.
Oh, that's nice information! I appreciate it for letting me know. BTW, so if I have trophies of those kind of games you mentioned, how would I delete them? Would I just have to delete the games, maybe go to my user folder on a file manager, with Apollo Save Tool in some way, and/or maybe something else?
 
Last edited:
Oh, that's nice information! I appreciate it for letting me know. BTW, so if I have trophies of those kind of games you mentioned, how would I delete them? Would I just have to delete the games, maybe go to my user folder on a file manager, with Apollo Save Tool in some way, and/or maybe something else?
Evilnat CFW already has the ability to delete trophies baked in (just highlight the trophy and click triangle and there will be a delete option in the menu). Or you can just delete all trophies at once through the debug settings menu.
That said - I don't have any pirated digital games, and I use a separate user account for betas, so I can't tell you whether just deleting the trophies one by one is sufficient (maybe someone else could). Might be better to just delete the user account and create a new one to start fresh, or if you're super paranoid you can factory reset by formatting the HDD, but either way you lose all the trophies and saves you haven't synced yet.
 
It's very cumbersome to "edit" trophies, and it's impossible to do that after you've synced them with your PSN account.

I wouldn't bother with that as the most tiny, little mistake, could render your whole PSN trohpies locked for future updates forever. I've "destroyed" some test PSN accounts while experimenting with trophy's timestamps and such, with absurd dates (like getting a Platinum a year before getting the first trophy). After lots of editing and syncing, I've got error 80022D00, unable to sync any trophies on that account.

Also, hacking trophies on PS3 will never result in a ban as NiQ stated. Sony has other, more robust and thorough ways to find out if you are using their services from a hacked device. Trophies don't move the ban needle at all.
 
So I finally had time to look at this today. I have QA flags enabled, but when I try to install the Dual Boot + Hybrid Firmware from my HDD using Settings > System Update > * Update via System Storage (/dev_hdd0/updater/01/DualBoot-Hybrid_4.91.PUP) I get the following error:

Error: 61% Complete - "The data type is not supported. (80029C9C)"​

My question is, can we install this firmware in this fashion? I see the brief instructions call to install from USB drive, but this would be more ideal as this is my setup:

  • Local HDD: /dev_hdd0/updater/01/<Various PUP Installers>
    • Use Case: Once on Custom Firmware, I can migrate to any other CFW's easily (if they support this feature).
    • Various CFW's
    • Dual Boot Firmware's
  • USB Drive: /PS3/UPDATE/PS3UPDAT.PUP (EvilNat 4.91.1 [CEX])
    • Use Case: Once on Dual Boot or Dual Boot + Hybrid I can revert back to CFW
Additional Details:
  • Model: CHECHA01
  • HDD: Upgraded to 1TB HDD
  • Current FW: EvilNat 4.91.1 (Updated 03-12-2024 [11.14pm])
    • I had D-PEX variant installed, but I "Convert to CEX" which mean I think I am on PEX now.
  • CEX/DEX: Network > * Custom Firmware Tools > CEX2DEX > Show Information:
    • Firmware: 4.91 CEX
    • IDPS: Original
    • TargetID: CEX
    • VSH: DEX
    • XMB Host: CEX
    • Debug Settings: DEX
  • QA: Network > * Custom Firmware Tools > QA Tools > Check QA Flags
    • QA Flags are enabled

For me, this appears in the XMB. I confirmed that Evilnat 4.90 doesn't seem to have the issue.

I also confirmed this issue appears to be present on 4.91.2 [PEX] [BETA 1].

Workflow that appears to be working:

  • Internal HDD: Evilnat 4.91.1+ [PEX or CEX] > Evilnat 4.90.1 [CEX] > littlebalups Dual Boot + Hybrid 4.91
    • This allows to move to OFW type OS.
  • USB Drive: 4.91.2 [PEX] [BETA 1]
    • This allows me to revert back to latest CFW.

@Evilnat , I also confirmed this issue appears to be present on 4.91.2 [BETA 2] [PEX].
 
Can i use this dualboot on every version of evilnet's latest betas? Thanks in advance
This replaces any CFW you might have. If you use this and then want to go to CFW again you need to reinstall it. The only difference is that DB (unlike OFW) will not require you to go through bgtoolset again.
 
Hey there @littlebalup so I'm trying to jailbreak my ps3 right now and whilst running the pyps3 checker I've come with a warning of SKU identification and I need help what do I do???
 
It is not needed to format drive. Just delete everything related to homebrew. Every pushlist, cache, db entry, custom folders etc.

So have to delete the folders created by cfw, could move the backups copies to another folder like the "saves or any ofw folder and then move them back when return to cfw,
'cause some backups are very heavy and I don't have space to save them elsewhere.
or is it not recommended?
 
So have to delete the folders created by cfw, could move the backups copies to another folder like the "saves or any ofw folder and then move them back when return to cfw,
'cause some backups are very heavy and I don't have space to save them elsewhere.
or is it not recommended?
I'm pretty sure that was a sarcastic remark. I don't think it's realistic to find every single file, directory, pushlist, cache and db entry created by homebrew. It's very difficult and the chance of missing something is very high.
You might want to get a 2nd hard drive for DB. It should be possible to switch between two HDDs on the same PS3 as long as they're both from the same firmware version (4.91 in our case). Just make sure you don't accidentally insert the DB HDD when CFW is installed so it doesn't create any CFW stuff on it.
But tbh, a 2nd hand PS3 costs ~$100 these days and a lot of people just buy a second PS3 and keep it on OFW for PSN.
 
Back
Top