PS3 4.84.3 STARBUGED (w/ COBRA 8.01) - New update in from Habib

Following the introduction of 4.84 STARBUGED CFW for the PS3, which also gave us the introduction of Cobra v8.0x from developer @habib, Has now followed up that cfw release with 4.84.3 STARBUGED (w/ Cobra 8.01) that contains some more candy for the scene. As the developer has provided new features once again with this update with the ability to Hardcode Kernel Plugins, which can be useful for things like MAMBA (a Cobra Alternative) as it can not be ran as a kernel plugin. Down below you will see the technical aspects of what this update has provided from Ps3 CFW Developer @habib.​

-STLcardsWS​

What's New STARBUGED Features

• 
  
  4.84.3 Starbuged + Cobra v8.01 CFW
  Starbuged = Starbucks Release + Rebug Seasoning​
  
  What's New in 4.84.3?
  
  1. Hardcoded kernel plugin
  2. Whole kernel 8mb is RWX including kernel alloc. you can use sc15 alloc, copy payload and execute like that as well but its better to use opcodes for kernel plugins
  3. Fixed minor bug in non cobra sc15​
  
  what does it do?
  
  • it loads plugins from /dev_hdd0/boot_plugins_nocobra.txt and boot_plugins_kernel_nocobra.txt
  • it fixes issue where nocobra and hdd format will make ps2 not work on bc/semi-bc
  
  what plugins can do?
  
  • load mamba and isolate cobra functions, modify it. e.g ps3mapi without cobra. i hate cobra being bloated with homebrew blockers etc
  
  for devs:
  
  • for mamba payload hdd0 is already mounted, prefer to load your code in main() instead of using the cellfsutil hook...regardless mamba works 90%
  • also dont forget to remove dev_hdd0/tmp/loadoptical flag for bc and semi-bc ps3
  
  NOTE: cobra plugins will NOT work when cobra disabled
  
• 
  
  
  STARBUGED FEATURES:​
  • FEATURE – COBRA 8.01 (Enabled by default)
    • Background running plugins at boot time (sprx)
    • ISO Support: PS1/PS2/PS3/PSP/DVD/BluRay (Split ISO support on FAT32 drives)
    • Network Support: PS1/PS3/DVD/BluRay /PKGs
    • Blu Ray Movie region free functionality NTFS HDD Support (prepNTFS, or multiMAN Required to scan contents)
    • PS2 ISO Support for BC (HW) / non-BC (SW) Consoles
    • Syscall 11 – Cobra lv1 Peek
    • Syscall 15 – Allow execution of any LV2 internal function
    • PSNPatch stealth plugin support
      • ***ISO rips are required to get 100% support, for ex) after disabling syscalls, games like Call of Duty will not be able to play unless you use ISO rips, please DO NOT expect everything to be fully functional when you are disabling the built-in features from COBRA. Folder rips are NOT compatible with PSNPatch's stealth mode due to its ability to disable COBRA's disc-less feature for folder JB rips****
    • PS3MAPI support, allows you to attach process on both CEX/DEX via its own API app.
    • Backup Protection Removal, Add full PS3 Backup support on all multiMAN/sMAN/webMAN,IRIS manager forks and Managunz.
    • Allow modification on Syscall 6/7/8/9/10/11/15.
    • Burned/Burnt optical media support for PS1/PS3 Games on All models
    • Homebrew blocker – blocks homebrew access while Syscalls are disabled
    • Added in v8.00 Run payload with Kernel privileges - Added option to run payload with kernel privileges like ps vita skprx. this is a big thing! one can make hooks, printf to socat, do whatever they feel like they need to do. at the current time only one payload is supported at a time. in the future i might increase this
    • Added in v8.00 Boot times speed improved - as there is no stage1.
    • Added in v8.00 PS2 bc and semi bc consoles wont load iso when cobra disabled - disable cobra using opcode)
    • Added in v8.01 Added support for dynamic memory payloads, 5 of them can be started from "/dev_hdd0/boot_plugins_kernel.txt"
    • Added in v8.01 toolchain updated to support dynamic address loading.
      Added in v8.01 For applications, you can also mount em, and unmount em separately
  • FEATURE – Full Polish support for XMB/PS2 Emu (Provide full Polish character support)
  • FEATURE – Cinavia protection fully disabled (Supports optical media/bd iso, AACS must be decrypted)
  • FEATURE – Homebrew store compatibility (Downloading debug signed packages is now available on retail CFW.)
  • FEATURE – PSN/SEN Accessibility (PSN /SEN Accessible , until the next OFW update)
  • FEATURE – XMBM+ Compatibility (XMB Manager Plus developed by Team XMBM now supported via standalone pkgs.)
  • FEATURE – HAN Toolbox Compatibility (HAN Toolbox Support added for testing HAN Signed pkgs on CFW)
  • FEATURE – Enhanced Remote Play (This unlocks the limitation of working apps/games for remote play, by disabling SFO flag check)
  • FEATURE – In Game Screenshot (Allows taking screenshots in Game
  • FEATURE – QA Token compatibility
  • FEATURE – OtherOS++ support enabled (Use Rebug Toolbox to Boot OtherOS with different LV1 patches)
  • FEATURE – Package Manager (Replacement for the standard 'Install Package Files' option)
  • FEATURE – FSELF compatibility (Fake Signed ELF is supported)
  • FEATURE (Optional) Toolbox 02.03.00
    • TOGGLE XMB CFW SETTINGS Enable or Disable mysis's XMB CFW settings plugin v0.1. The feature is available via Network Column on XMB after Enabled.
      
    • TOGGLE COBRA MODE: COBRA mode ACTIVE by default, this option can toggle COBRA mode to enable COBRA 8.00 payload on boot
      
    • TOGGLE QA: Enable/Disable QA flag. Enable for easy downgrade and other extra features on all 3.55-4.84 CFW.
      
    • TOGGLE RECOVERY MODE: Enable/Disable Recover Mode flag. When enabled your PS3 will reboot into Recovery Mode.
      
    • LOAD LV2 KERNEL: Load lv2_kernel.self.[KERNEL_NAME] from USB or /dev_hdd0
      
    • BACKUP/RESTORE XREGISTRY: Backup or Restore the PS3 system settings from USB
      
    • RESIZE VFLASH/NAND REGIONS: Resize VFLASH/NAND Region 5 to allow install of OtherOS.
      
    • INSTALL PETITBOOT: Install Petitboot to VFLASH/NAND Region 5 from USB.
      
    • SET GAMEOS BOOT FLAG: Sets the GameOS boot flag. Use this if your PS3 is having trouble booting PS2 titles after running OtherOS or is accidentally sending you back to OtherOS when trying to enter recovery mode.
      
    • CREATE PACKAGES FOLDER ON PS3: Create /dev_hdd0/packages folder or your PS3 to be used with Package Manager.
      
    • EXPORT HYPERVISOR LV1 MEMORY: Save LV1 memory to dev_usb000 or dev_usb006 or dev_hdd0 if usb is not found.
      
    • EXPORT GAMEOS LV2 MEMORY: Save LV2 memory to dev_usb000 or dev_usb006 or dev_hdd0 if usb is not found.
      
    • EXPORT FLASH TO FILE: Backup your current NOR/NAND to file on dev_usb000. Takes about 45secs for NAND
      
    • DUMP EID ROOT KEY: Dump your eid root key.
  • FEATURE – XMB CFW settings v0.1a (Optional)
    • XMB Icons for various CFW tasks, available in Network Column (on XMB) Simply select and the task is executed!
      
    • Settings – Toggle COBRA
      
    • Dump Tools – Klicense, File Secure ID, IDPS, Disc Hash keyService Tools – Display Minimum Downgrade FW Version, Rebuild Database, Check File System, Entering Recovery Mode (NOR Models Only)
      
    • Advanced Service Tools – Entering FSM (!!!DO NOT Install FW while on FSM that may lead RSOD!!!), Remarry BD drive and RSOD fix
  • PATCHED – Appldr: LV2 memory hash check is disabled (Memory protection on LV2 is disabled in higher level)
  • PATCHED – LV1: Disable System Integrity Check (Safe to use with mismatched COREOS/SYSCON versions or if PS3 is not QA enabled)
  • PATCHED – LV1: Undocumented function 114 (Allow mapping of protected memory)
  • PATCHED – LV1: Skip all ACL Checks (Needed to allow booting of OtherOS)
  • PATCHED – LV1: Peek and Poke support (Unused LV1 call 182 and 183)
  • PATCHED – LV2: Peek and Poke support (LV2 Syscall 6 and 7)
  • PATCHED – LV2: Peek and Poke support for LV1 (LV2 Syscall 8 and 9)
  • PATCHED – LV2: LV1 CALL System call (LV2 Syscall 10)
  • PATCHED – LV2: Allow execution of any LV2 internal function (LV2 Syscall 15)
  • PATCHED – Recovery: Prevent accidental OFW update while on Recovery mode
  • PATCHED – VSH: Allow Unsigned act.dat and *.rif files
  • PATCHED – VSH: Disable NEW PSP DRM Check (Allowing unsigned PSP pkg contents on 4.75 or higher CFW)
  • PATCHED – VSH: Disable Epilepsy Warning for Faster Boot-Up Speed

Download (& Source Code): 4.84.3 STARBUGED​

 

The issue with MGS HD Collection's BD MOVIE not being played happens on all conditions. (I also tested folder method)

The guy's another issue with MAMBA+PSNPatch throws 80010516 happens on every game runs



Not sure, sk1e payload loads fine and MAMBA loader hasn't been tested.

View attachment 15623

View attachment 15626


by the way IRISMAN freezes when webMAN's loaded while COBRA's active.

The screenshot above was taken while webMAN's disabled.

Strange. IRISMAN on COBRA with webMAN loaded works fine for me.

 

Strange. IRISMAN on COBRA with webMAN loaded works fine for me.

webMAN also loads fine for me using MAMBA + IRISMAN, except that I only use CEX.

 

by the way IRISMAN freezes when webMAN's loaded while COBRA's active.

Strange. IRISMAN on COBRA with webMAN loaded works fine for me.

IRISMAN 4.84.2 on 4.84.3 STARBUGED with COBRA enabled, webMAN loaded works for me.
Also works with webMAN not loaded.
What doesn't work is IRISMAN's "Network Games (via webMAN)".

 

webMAN also loads fine for me, except that I only use CEX.

Probably I loaded too fast since webman likes to freeze any apps while it's scanning contents. I usually turn off contents scan when testing firmware and this time I didn't.

 

@aldostools, any thoughts about this:

The problem is with Mamba/PRX Loader when I try to launch a game after PSN Patch plugin has disabled CFW.

It fails with "An error occurred durring the start operation (80010516)"

 

Probably I loaded too fast since webman likes to freeze any apps while it's scanning contents. I usually turn off contents scan when testing firmware and this time I didn't.

I wonder if the black screen in DEX is caused by webman, a wrong offset in payload_481dex.c, MAMBA_484D.bin or payload_484D.bin. There are too many variables involved and I only have tested it in CEX.... plus I'm not at home.

@aldostools, any thoughts about this:

I don't have a clue... To reduce variables in your issue, I suggest to test the game offline without disable the syscalls and without psnpatch loaded.

 

I wonder if the black screen in DEX is caused by webman, a wrong offset in payload_481dex.c, MAMBA_484D.bin or payload_484D.bin. There are too many variables involved and I only have tested it in CEX.... plus I'm not at home.

Yeah this reminds me the days when I was porting all the missing DEX payloads. Mamba has always been a nightmare. I will check it myself later.

 

Yeah this reminds me the days when I was porting all the missing DEX payloads. Mamba has always been a nightmare. I will check it myself later.

THANK YOU VERY MUCH! I appreciate it.

 

The issue with MGS HD Collection's BD MOVIE not being played happens on all conditions. (I also tested folder method)

By the PS3 standards is not a BD movie, is a PS3 game with additionally video content
It can be seen in this table: https://www.psdevwiki.com/ps3/PARAM.SFO#CATEGORY

Is using the path dev_bdvd/PS3_CONTENT/VIDEODIR/
And the XMB knows about his presence by reading the https://www.psdevwiki.com/ps3/PS3_DISC.SFB#Hybrid_Flags

A normal game (containing an executable EBOOT.BIN and a firmware update) uses the flags "gu", but this game probably is "guV" (or "gVu")

The other flag "v" (in lowercase) is used only for the real bluray films... but only exists in veeeeery few bluray films
Usually the standard discs for bluray films doesnt follows this file/folder structure at all (doesnt have the PS3_DISC.SFB or any other file related with the PS3, all this is a sony invention related with the PS3 but not much successfull)

Anyway... what i think is there is some problem we are dragging since lot of time ago with some of that folders/structures of the PS3 games that are not correctly detected by the "mounting" methods used in backup managers

What i said about the folders PS3_GM01, PS3_GM02, PS3_GM_03, etc... is an obvious example of this problem, actually if i remember right there was some versions of iris that was not even able to "mount" them and display them in XMB
The first people that reported this problem was the ODE users, because they was able to make a correct backup of the disc files by using a PS3 drive connected to a PC (with that 3k3y adapter that removed decryption "on the fly")
After that estwald made some kind of "patch" in iris to allow that folders to be displayed on XMB... but it seems that patch is not used when iris does a backup of the disc

So... dunno, but it looks like the amount of disc contents "mounted" to XMB is "sensitive" to the hack used to mount it
For the folders PS3_GM01, PS3_GM02, PS3_GM_03 simply was "missing" in old versions of the backup managers
And for this disc of metal gear with a video content it could be happening that is mounted, but dragging some problem

I remember to backup and load correctly other games with video contents before though, not sure if it was a god of war game, but i did everything with iris and i had videos displayed in XMB video column and working fine

I couldn't access the XMB when the Multiman message appeared. I only got: turn of controller, turn off system (the menu which normally shows when long-pressing the PS button).

Anyway... makeps3iso is still making the ISO, 37.5 GiB so far.

A short press of the "PS" button should make appear the "XMB ingame" with the screenshot icon
The menu you mentioned appears only by a long press of "PS" button (around 2 seconds needed)

 

A short press of the "PS" button should make appear the "XMB ingame" with the screenshot icon
The menu you mentioned appears only by a long press of "PS" button (around 2 seconds needed)

I was saying that short-press invoked the menu that is usually shown on long-press. This is not unusual if is presses while a message is shown.

@sandungas, see attached archive for
PS3_GAME/PARAM.SFO and PS3_DISC.SFB. You can find the file list in http://jonnysp.bplaced.net/info.php?file=ird/BLES01419-CFB77A1E2522029A9E3FB268F6219D87.ird

 

I was saying that short-press invoked the menu that is usually shown on long-press. This is not unusual if is presses while a message is shown.

Ok, now i got it, i thought you was doing long presses only
I never noticed it before, but i guess what is happening is multiman is using the firmware functions to display an "official like" warning screen, and the "xmb ingame" refuses to load if there is a warning screen active

 

@sandungas, see attached archive for
PS3_GAME/PARAM.SFO and PS3_DISC.SFB. You can find the file list in http://jonnysp.bplaced.net/info.php?file=ird/BLES01419-CFB77A1E2522029A9E3FB268F6219D87.ird

Hmmm, is really an hybrid disc game+video
The files and folders that usually doesnt exists in a PS3 game are the standards of a bluray film (not related with sony or playstation, all bd players can load them)

The PS3 reads the flags in PS3_DISC.SFB ("gvu"), and mounts the video in XMB because the presence of the "v", and uses the SFO in this path for it:
dev_bdvd/PS3_VPRM/PARAM.SFO

Thats the interesting SFO btw (not the SFO inside PS3_GAME, that is standard)
But at this point that SFO is not going to solve the problem though
And i dont know if this kind of backups have some problems, now im looking at psdevwiki and it seems someone (probably myself) added some notes about this but i dont remember other people reporting about them

 

If you want to take a look at it, I attached it.

 

I just mentioned the SFO inside PS3_VPRM folder because is a rarity, but is not related with the problem

I think the problem is a bit the same of what happens with folders PS3_GM01, PS3_GM02, etc... just because are "rare" so it was easy to miss them when developing the backup managers... also the first games using them was released years after the PS3 launch day (can be considered something "modern" that probably didnt existed in older versions of the firmware)

But now that i realized is really a game+movie disc im thinking maybe they are right and is related with video regions, dunno
Is loaded like a bluray movie so all restrictions of standard bluray video applyes

 

The issue is that ps3 assumes aacs encryption is the backup manager is sending ps3 disc type to cobra. To fix this managers can add check if the iso has BDMV folder and add section either to mount as bd movie or bd ps3

Currently it can only do one thing at a time. That's because the disc type is faked to bdr otherwise aacs encryption will take place and error out

FYI @aldostools

 

So I did some testing myself, I built the US rip with both makeps3iso and 3k3y's isotool w/ IRD, and all the result were the same as @noname99zzz 's result.

FWIW I also tested ISO from makeps3iso and 3k3y Isotools with IRD. The results were same as before.

The issue is that ps3 assumes aacs encryption is the backup manager is sending ps3 disc type to cobra. To fix this managers can add check if the iso has BDMV folder and add section either to mount as bd movie or bd ps3

Currently it can only do one thing at a time. That's because the disc type is faked to bdr otherwise aacs encryption will take place and error out

So the choice is to mount the ISO as either a Blu-ray game disc of Blu-ray movie disc but not both?

 

FWIW I also tested ISO from makeps3iso and 3k3y Isotools with IRD. The results were same as before.


So the choice is to mount the ISO as either a Blu-ray game disc of Blu-ray movie disc but not both?

For now no because the ps3 assumes the normal bd-rom drm but I shall take a peek at it in near future

 

The issue is that ps3 assumes aacs encryption is the backup manager is sending ps3 disc type to cobra. To fix this managers can add check if the iso has BDMV folder and add section either to mount as bd movie or bd ps3

Currently it can only do one thing at a time. That's because the disc type is faked to bdr otherwise aacs encryption will take place and error out

FYI @aldostools

Im wondering... right now with the actual implementations in cobra/mamba and backup managers... if we try to make a backup of that disc with irisman/multiman the files from BDMV are going to be decrypted incorrectly ?

 

Im wondering... right now with the actual implementations in cobra/mamba and backup managers... if we try to make a backup of that disc with irisman/multiman the files from BDMV are going to be decrypted incorrectly ?

I'm not entirely sure.
Normally aacs stays when actual bd is backed up In Multiman.
How such game would work is no aacs and mounted as bd on cobra opcode

If aacs present it won't work properly. So mount must be done as bd so cobra send as bd-r so no aacs is assumed. Correct playback

 

The issue is that ps3 assumes aacs encryption is the backup manager is sending ps3 disc type to cobra. To fix this managers can add check if the iso has BDMV folder and add section either to mount as bd movie or bd ps3

Currently it can only do one thing at a time. That's because the disc type is faked to bdr otherwise aacs encryption will take place and error out

FYI @aldostools

To mount the game as BD movie, it's just needed to place the ISO into /BDISO instead of /PS3ISO

The ISO can be copied to both folders in case it's required to launch it also as game for some part of the content of the disc. If it's first copied to /dev_hdd0/PS3ISO then that ISO is copied to /dev_hdd0/BDISO, the second copy will be a shadow copy and won't use the extra hdd space and when scanned will appear listed on both categories: PS3 and BD/DVD folders.