PS3 PlayStation 3 FAQ (2023) WIP

STLcardsWS

STLcardsWS

Administrator
Still a work in progress
help contribute in the comments below
​
​
Can my PS3 Model Install Custom Firmware (CFW)?

How to Install / update to a new CFW from CFW?
  • On a USB storage device, create folders:." PS3" then Inside that folder, create another folder named "UPDATE"
  • Now place the downloaded CFW PUP and be sure to name it as exactly "PS3UPDAT.PUP".
  • So on root of your USB Storage Device you should now see the file structure as. PS3/UPDATE/PS3UPDAT.PUP
  • now from the XMB you can goto System Update and update via USB Storage. If done right you will see your CFW appear for installation.
  • DO NOT HAVE PS3 GAME DISC IN THE DRIVE (IT WILL READ OFF DISC INSTEAD OF USB DEVICE)
  • Verify the MD5 Checksum of the downloaded CFW PUP file before installation.

Can i access PSN on CFW or PS3HEN?
  • Yes, but there is a ban risk in doing so, but you can reduce those risk (but always a risk).
    • Using noPSN version's of Media Apps (like Netflix, Amazon Video, ect..) can use the noPSN version's that are available here (from @esc0rtd3w website). These are the official media apps that remove the PSN login requirement. So no ban risk when using the noPSN version's created by the scene as you do not have to login to PSN use these services. (NoPSN)
    • Disable CFW syscall's - This temporary and disable CFW/PS3HEN patches, this is not fool-proof it can be effective in some games and not effective in other's but does help reduce the risk of ban. Various apps/plugin offer disabling of CFW syscalls (webMAN MOD is a great option)
    • DualBoot FIrmware (CFW user's only) - Want to play your PS3 disc games or your PSN purchased games, then using a DualBoot (DB) firmware is a very safe way to play that content on PSN, as DB firmware is Official FIrmware, but unlike OFW. It allows user's to return to a CFW when they reinstall the PUP. (no exploit needed, thus this is only useful for CFW User's to DB firmware back to CFW)
    • Tips, Respecting the network is how to best avoid a ban, do not do things other system's can't do. Don't Cheat !!! Don't use mods online and you will avoid a ban, but there is still a risk you do everything right and respect the network and get banned, So use PSN at your own risk!!!!

How do I Emulate Retro Games on my PS3, what are the best emulator options?

Where can i find PS3 Homebrew / Plugin's to download?

What is COBRA (COBRA CFW)?
  • Learn more about the COBRA payload >HERE<
What is MAMBA ?
  • Learn more about the MAMBA payload > HERE <

What is CFW/ CEX / DEX / PEX / REX noBD / noBT / CFW / DB FIRMWARE ?
  • OFW - Official Firmware
  • CFW - Custom Firmware
  • MFW : A old term meaning modified firmware (same as CFW, but MFW builder was used for creation of firmware)
  • HFW - Hybrid FIrmware - Same as OFW, with just a simple re-injection of a previous webkit exploit patched from 4.82 re-injected in later OFW 4.83+, the great thing about this injection it still allows for an installation on an unmodified system on OFW, used most often with PS3HEN installation's. .
  • CEX - Refers to Retail Firmware (what is installed on all PS3 Sold to public)
  • DEX - Refers to Debug Firmware (the officiial debug test firmware for official developer's)
  • REX - Refers to a CFW type created by Team Rebug, that is a hybrid of CEX and DEX firmware which create's REX. ,
    • D-REX: Same as REX for installing on DEBUG console.
  • PEX - Refers to a CFW type created by Evilnat, that is like REX but use's an earlier 4.84 DEX (Ported to 4.89) which creates PEX
    • D-PEX Same as PEX for installing on DEBUG console.
  • noBD - A Special CFW (for broken hardware (Blu-Ray Drive in this case)), that patches out the drive so the console can be used without the drive think of it as the "The PS3 Digital Edition". Without this patch those damaged console's can not launch or leave the XMB, even things that are stored on the HDD, so if your console is not reading disc and not launching anything from the XMB, it might just need a noBD firmware.
  • noBT - Just like the noBD firmware, this is no BlueTooth.
  • Standard CFW: This is your normal base CEX custom firmware with no extra payloads (such as Cobra or Mamba) provides homebrew support and backup capabilities.
  • Cobra CFW: This is a standard cfw but also contains the Cobra payload with expanded features (background plugin support / ISO Support / NETISO support / ect..)
  • DB Firmware - This is a Dualboot firmware for CFW user's this is exactly like OFW, but with a small modification for CFW. It's OFW for CFW user's as it allows you to return to a CFW later on without the need to Jailbreak or exploit the system again. This can be very useful when playing your disc games online and want to be cautious of a PSN-ban for using a modded system .

How do i use any PS3 Game Save?

The PS3's media player does not support various format's is there any other alternative or homebrew app's for playing media?
  • Yes, Movian (once known as Showtime) is a Homebrew Application for the PS3 that can play most audio and video formats on the PS3. See here for more details about Movian. Note there is a standlaone version and also a version that works alongside multiMAN.

Any homebrew or mods to help keep my PS3 from overheating?
  • Yes, there is various homebrew that will monitor the internal temperatures of the RSX/CPU and also adjust the internal fan's speed accordingly to maintain a desired speed, webMAN MOD dynamic fan control is a popular option for his feature, but there are a number of ways to monitor the temps and/or control the internal fan with a variety of methods used, but our suggestion is using the PS3 plugin webMAN MOD.

Can I take ScreenShot of Games & of XMB using the PS3?
  • Game Screenshots: Taking Screenshot's while In-Game can be very easy when the firmware has the feature of "In-Game Screenshot Unlocked" as when your in the in-game XMB you can scroll to the PHOTO column and see the feature labeled as "Save ScreenShot". In OFW this is a feature that is seen in some games but locked in other's, in cfw's this features unlocks it for all. NOTE: it will work in some homebrew, but some homebrew does not play nicely with the in-game XMB,
  • XMB ScreenShots: This can be done using webMAN MOD by two way's (via wMM Wiki)
Button Combo (PAD Shortcut): on the XMB pressing "L2 + R2 + SELECT + START" = Capture XMB screenshot (full edition only)
Web Command in a browser connected to the same Wi-Fi network as your PS3 you can enter in your address bar " YourPS3 IP Address/xmb.ps3$screenshot/<path+filename> - capture XMB screen and save it to the specified path" TIP: Some games allows capture using PS + START or press PrintScreen key on USB keyboard.​


Possible to Stream media (& play games) from a remote server to the PS3?

Split PKG installation for packages (.pkgs) larger then 4GBs?

CDDA Audio Support for PS1 Games? (via Aldostools)
  • If you are using ISO or BIN without a CUE file, you won't get the CDDA sound.
  • If you're using a multi-part bin image with a CUE file, you need to merge the bins in a single bin file.
  • Another common issue is the pregap or incorrect tracks time in the CUE file.
  • Very few psx games need a PPF patch to play properly. Most of them play fine with the correct BIN format and CUE file

Can using a SSD cause issue on the PS3?
  • Yes, not all SSD are compatible, it's not known completely so there is no list. You usually do not see much in performance gain's. so its not wise to use a SSD in the PS3, (1)

Which is better CFW or PS3HEN?
  • For most user's the features are very comparable, if you are a developer or an advance user or just want every feature possiable then Custom Firmware offer's the most robust feature set as its a full Jailbreak where as PS3HEN is a Homebrew Enabler. They are both very good exploits for the PS3, You can see a comparison of the two exploits here . PS3HEN runs on all models, PS3 CFW does not run on all models.

Tip' Using the Dynamic Fan Control in webMAN
.Help contribute to this FAQ...
 
Last edited:
@STLcardsWS do you know any detailed faq about Cobra/Mamba? i'm writing some guides for my PS3 Pro MOD and i couldn't find any detailed faq about all cobra/mamba features.
 
LuanTeles said:
@STLcardsWS do you know any detailed faq about Cobra/Mamba? i'm writing some guides for my PS3 Pro MOD and i couldn't find any detailed faq about all cobra/mamba features.
Click to expand...
Nothing completely organized but i can give you some details more so on Cobra, but as i am sure you now days cobra and mamba feature wise are very close.

Here is an overview i put together recently. I am sure i am missing something :)
General Overview (see spoiler below for changelog's)
  • PRX plugins at boot time (sprx) - (Run in background)
  • Kernel Plugin Support
  • Game ISO Support: PS1/PS2/PS3/PSP/
  • Video ISO Support DVD/BluRay
  • Blu Ray Movie region free functionality
  • Split ISO support on FAT32 drives (4GB limitation, split ISO do not need merged play like unsplitted ISO's)
  • Network Support: PS1/PS3/DVD/BluRay in ISO and Remote Installation of PKGs
  • NTFS HDD Support (prepNTFS, or multiMAN Required to scan contents)
  • PS2 ISO Support non-BC (full software emulsion) Consoles
  • PSP ISO SUpport on all PS3 (using Cobra Launcher, not all games work)
  • PS1/PS2 Improvements
    • Improper PSX region patching
    • Cobra opcode to bypass automatic detection of video mode and force specific video mode
  • PS3MAPI support, allows you to attach process on both CEX/DEX via its own API app.
  • Optical media (Burned/Burnt) support (PS1/PS3 Games for all Models)
  • These are just some of the features Cobra brings to your CFW (see full changes below in the spoiler since the community took over the project


Change's the community has made since v7.0 (Clean Source Code Release)
v8.4 (not 100% if that is complete 8.4 changelog)
  • - Blacklist access to homebrews NP0APOLLO / NP00PKGI3 when CFW syscalls are disabled
  • - PS3MAPI changes by @OsirizX used for Dynarec
  • - Libcrypt Support for PS1 games (LSF/SBI files).
  • - PSX Bios patched with product code 0x85 for PAL games
  • - Force video mode in PS1 games adding "NTSC" or "PAL" in the file name of the BIN/CUE
  • - PS2 FAN Speed now works with PS2 Classic games
  • - Updated PS3MAPI_CORE_VERSION to 0x0124 (OsirizX additions for Dynarec)
  • - Disabling boot_plugins.txt by Evilnat
  • - Check for NULL memory allocation in make_rif.c
  • - Map path like Mamba 8.4
  • - Fixed issue in PhotoGUI. It was truncating the path by 16 bytes

V8.3 Changelog
• Added cellUsb000 symbol and data (by haxxxen and aldostools)
• Load external stage2/plugins from USB device (by haxxxen and aldostools)
• Failsafe Cobra stage2 (by bguerville/aldo)
• Restore CFW Syscalls without reboot just entering to 'Settings > System Update' on XMB (by aldo)
• Integrated Dynamic Control FAN (to control fan when webMAN is unloaded) (by aldo/Evilnat)
• Support Photo GUI integration with webMAN MOD (mount games from 'Photo' column) (by aldo/DeViL303)
• Get/Set FAN speed (by aldo)
• Enable/disable features: Photo GUI, Restore Syscalls (by aldo)
• Opcode to create CFW Syscalls (6, 7, 8, 9, 10, 11, 15, 389, 409) (by aldo)
• Opcode to set fake accountID (by Evilnat)
• Opcode to activate account (act.dat) (by Evilnat)
• Opcode to create license (RIF) (by Evilnat)
• Updated ps3mapi_load_process_modules to load custom modules and system modules (by haxxxen)
• Added ps3mapi_get_process_module_info
• Increased from 24 to 32 the max number of map paths (by aldo)
• Added sm_get_temperature patch in kernel (by Evilnat)
• Added sm_get_fan_policy patch in kernel (by Evilnat)
• Added sm_set_fan_policy patch in kernel (by Evilnat)
• Fixed Control FAN payload, avoids loading previous mode (by Evilnat)
• Disable stage2.bin while Recovery Menu is loaded (by haxxxen)
• Fixed max FAN speed after shutdown (by Evilnat)
• Improve Habib's QA flags code imported by aldostools (by Evilnat)
• Fixed black screen in CFW2OFW converted games (by Evilnat)
• Added sm_ring_buzzer with single_beep, double_beep and triple_beep (by Evilnat)
• Skip license creation (rif) if it already exists (by aldo)
• Added cellFsMkdir symbol (by Evilnat)
• Added constant FAN Speed while a PS2 ISO is launched (by Evilnat)
• Check/Disable/Enable QA Flags (by Evilnat)
• Creation of act.dat while launching a PSN game (by Evilnat)
• Convert someones's else savedata to your own savedata (by Evilnat)
• Block Log In on PSN/SEN when CFW syscalls are enabled (by DeViL303)
Contrributions by developer from v7.0+ - 8.2
[ @Joonie 's Changes ]
* Firmware spoofing is disabled due to the changes of PSN Auth since 4.60
* PLS3 patches are removed from modulespatch.c since this is one of those pre-applied patches on 4.xx CFW
* unknown E3 patches are removed to fix an issue with XMB, [Originally found by rancid-0, from his PS3ITA 4.50 COBRA]
* Dual VSH supported for REBUG REX / D-REX CFW, with the proper hash check code was developed by habib and Nzv recently.
* NPDRM Fself fix is no longer used due to improved fself patches hard coded within the firmware modules on REX/D-REX
* Built-in reactPSN feature supported

[ @habib 's changes ]
* Run payload with Kernel privileges
* Boot times speed improved
* PS2 bc and semi bc consoles wont load iso when cobra disable
* Stage0 and stage0 base are merged, (Optimization on stage0 and stage1)
* Syscall 11 is added to support full lv1 peek.
* Syscall 15 is added to allow execution of any lv2 internal function.
* Allow Syscall 11 to gain full access to syscall 6/7/9/10 to prevent modification from homebrews like multiMAN.
* PS2 Launcher is no longer needed due to new codes in storage_ext, now COBRA can behave the same way that VSH does to apply configuration of DS3 controllers.
* PS2 Launcher can still be used, which allows PS2ISO with netemu on backward compatible consoles.
* PS2 Netemu toggle is added for Backward compatible consoles, it is very useful for those units with broken EE/GS chips as well.
* PS2 Netemu can now use decrypted CONFIG, place the game config file in the same game path for ex)
dev_hdd0/PS2ISO/GOW.ISO
dev_hdd0/PS2ISO/GOW.ISO.CONFIG
* HASH calculation algorithm is changed, now it uses static hashes, so the hashes will not be changed unless modules have major changes.
* Stealth extension support to disable Syscall 15
* Allows temporary LV1 peek from syscall 8 when "disabling COBRA" is not used

[ @kokotonix changes ]
* webMAN integration on boot. Also disables external webMAN plugin located in dev_hdd0 (Disabled for REBUG 4.82.1 LITE)
* PSN Patch stealth mode, it remove custom syscall from the ps3
* Homebrew blocker added, when Syscalls are disabled by plugins or homebrews, it will prevent homebrews from being launched, and it will return as 80010006 on XMB.

[ @deank 's changes ]
* Improved map_path, to fix the issue with games like Shadow of Mordor
* Permission protection is disabled to increase game compatiblity and full DEX support.[no more issue with Target Manager or CCAPI]
* 80010017 / 8001002B Error fix is added since 4.60, this was developed to prevent issues with games when game disc is inserted in BD Drive.
* LIC.DAT check is patched to fix the issue with launching homebrew since 4.60
* Full burned optical media support for PS3 Games. (CD-R, DVD-R SL/DL, BD-R SL/DL, BD-RE)
[ @_NzV_ 's changes]
* PS3MAPI 1.2.2 support, it is similar feature comparing to CCAPI, but open sourced project and also can unload vsh plugins , attatch process on all type of EBOOT.
One of those great debugging features.
* Partial disable syscall8 and unhooks all cobra hooks (Part of PS3MAPI)
* Block update from disc
[ @aldostools 's changes ]
* Improved PSX media type support, now it supports following disc types
* 2048 // 2352 // 2336 // 2448 *
* Improved Video mode patch with proper region detection
Original COBRA payload was relying on ps1emu's detection method, now COBRA has extra pre-processing that can detect region properly and force apply correct refresh rate depending on the game's region.
(Improved PS3MAPI functions)
* Added PEEK/POKE (LV1/LV2) as PS3MAPI opcodes (syscall8)
* Added option to block access and request access to syscall8 using a key
(also as PS3MAPI opcodes)
* Added temporary disablement of Cobra syscall8 to allow dumpers peek 0x1000 to 0x9800
* BASIC_PLUGIN hash is commented.
* 80010006 Error fix when trying to install a game update with syscall disabled. Fix & Research @Joonie @Alexander @Aldo
[ @Alexander 's changes ]
* Fixed data corruption if you uninstall game/game update/homebrew with syscall disabled

[ @haxxxen 's changes ]
* Extra patch for PSP SAVE DATA is disabled by default to improve compatibility, however can be toggled by CROSS+R1 when launching PSP launcher.

[@Evilnat 's changes]
* Updated KW's code to search webMAN in flash and load it firstly if it's found in /dev_hdd0, will search in the following paths:
- /dev_flash/vsh/module/webftp_server.sprx
- /dev_flash/ps3ita/webftp_server.sprx
- /dev_flash/webman/webftp_server.sprx
- /dev_flash/dragon/web.sprx

1st Source Code Release from Team Cobra
http://psx-scene.com/forums/content/breaking-news-cobra-releases-source-code-cobra-usb-3790/

2nd Source Code Release repost (original tortuga-cove link is down (cant find it) - This source code and release was by Former lead developer of CobraUSB who was no longer affiliated with team cobra and when he learned they made it Open Source he cleaned it up and re-released the source code (now that he could) and documented it for the scene and upgraded it to v7.0 with mixing it into Rogero CFW at the time. There is some info on that
https://www.psx-place.com/threads/about-cobra-v7-xx-cfw-the-dongle-less-cobrausb.2389/

Far as features go, i do not know a complete rundown. Other then the listing above

Evilnat and Joonie github's you can see the change i got from above
 
About USB stuff, You can link this. It is mainly for OFW but rules for CFW are exactly the same.
https://www.psx-place.com/threads/faq-updating-sony-consoles-from-usb-ps3-ps4-ps5-psp-pstv.33737/

DO NOT HAVE PS3 GAME DISC IN THE DRIVE (IT WILL READ OFF DISC INSTEAD OF USB DEVICE)
Click to expand...
It is true only for QA flagged machines. CEX and DEX without QA, will use update from disc only if game demand newest fw than is installed. That's the purpose of update on disc. Why QA consoles act like that (why Sony did that) is unknown.

Firmware 4.85: PS3Xploit Original Flash Writer, (later replaced by bgtoolset but that is offline)
Click to expand...
I don't remember now but isn't it was range from 4.82 up to and include 4.84? Because 4.85 changed something in browser and HFW start to be needed (which is Frankenstein assembled from 4.84 and later). @esc0rtd3w [?]

Also on Rebug REX / Evilnat's PEX CFW's - Fake Save Data Owner Feature is an option, the other two options work on all CFW's.
Click to expand...
Worth to mention that FSDO changing ownership of save. Victim which will use it and save in game, no longer owned the save and save be recognized as long this options is turned on. So if eg. victim decide to change CFW from Rebug or change any DEX OFW/CFW to CEX, it will face a need to resign save for him. @bucanero [?]

What is CFW/ CEX / DEX / PEX / REX noBD / noBT / CFW / DB FIRMWARE ?
Click to expand...
You forgot about MFW. ;) It is just CFW but modified by MFW tool.

DB Firmware - This is a Dualboot firmware for CFW user's this is exactly like OFW, but for CFW its allows you to return to a CFW later on. this can be very useful when playing your disc games online and want tobe cautious of a ban for using a modded system.
Click to expand...
It is CFW so not exactly like OFW, just with only patches allowing user to install CFW again.

Game Screenshots: Taking Screenshot's while In-Game can be very easy when the firmware has the feature of "In-Game Screenshot Unlocked" as when your in the in-game XMB you can scroll to the PHOTO column and see the feature labeled as "Save ScreenShot". In OFW this is a feature that is seen in some games but locked in other's, in cfw's this features unlocks it for all. NOTE: it will work in some homebrew, but some homebrew does not play nicely with the in-game XMB,
Click to expand...
In some games, this hack results in random freezing after taking screenshot (eg. Ratchet & Clank: Deadlock). Also, not all games can even allow that simply becasue of they mechanics (i.e when PS Button invoking pause menu, which covering what user want to screenshooting). Some games somehow also put their watermark and horribly compress JPG (e. Dragon's Dogma / DD: Dark Arisen). So always better is using button combo from a plugin.
 
Berion said:
It is true only for QA flagged machines. CEX and DEX without QA, will use update from disc only if game demand newest fw than is installed
Click to expand...
well no, only about DEX. it is the SAFEST thing you could have, cause how can DEX accept CEX and there are no DEX discs. besides, there is no (fake) QA DEX with current firmwares, cause token has to be recalculated each time you switch. another reason why I have gone my own way and not relating on given things. anyways, it is supperior in every way in my eyes
 
Berion said:
Worth to mention that FSDO changing ownership of save. Victim which will use it and save in game, no longer owned the save and save be recognized as long this options is turned on. So if eg. victim decide to change CFW from Rebug or change any DEX OFW/CFW to CEX, it will face a need to resign save for him. @bucanero [?]
Click to expand...

Yes, the actual account-id if you use FSDO will be changed to "ffffffffffffffff". Since resigning and modding save-games is really easy with Apollo, I honestly prefer to use my own account-id and resign when needed. That way I can share saves between HEN, CFW, and even OFW without worries.
 
LuanTeles said:
Thanks @STLcardsWS, i found a nice FAQ that can be useful to grab some information FAQ - ConsoleMods Wiki
Click to expand...

There is some outdated info there be cautious (but good info as well).

I never been a huge fan of that wiki, its not terrible but could be so much better and currently its outdated in alot of pages, was from the start , One huge issue i have Where are source links? there is none on alot of pages, Not how do you "preserve" a scene like that? When info becomes outdated then the wiki is an issue . It's hard to keep everything up to date. I do not think anyone can do that we have outdated stuff here as well (reason for the 2023 version of the FAq here). It will happen, but that is why source links are so important and should be looked at priority #1 when creating or documenting info.not brushed off

But like the Cobra Overview its not quite upto date. It's not terrible but it looks like v6.0 more so then v8.4. Then you have site like Wololo using this overview on news just the other day (not sourcing it BTW ) but its not a correct overview anymore,

  • Region free BluRay
  • ISO mounting for BluRay/DVD/PS1/PS2/PS3*
  • Mounting ISOs and games over network
  • ISOs can be split and still mounted, to bypass FAT32 4GB file limit on USB
  • PS1 backup discs work just like retail discs
  • Launch any PSP ISO using the Cobra PSP Launcher (compatibility is not 100%)*
  • Launch PS2 ISOs on any console (HDD only, software emulator is not 100% compatible)
  • Never requires a real disc in drive
  • Boot Plugins (apps that run in the background on boot)
  • Dynamic firmware spoofing for mounted backups (apps don't require updates for every firmware update)
Click to expand...

https://consolemods.org/wiki/PS3:FAQ

"Dynamic Firmware Sppofing for mounted backups"
not sure that feature is worded right but i could be wrong.

"Never Requires a disc"
What was this an original CobraUSB feature from 3.55.
What does require a disc anymore past 3.41 ?


My own overview could use some work (below) as well but its better describes today's Cobra.
We have things like Kernel Plugin Support / Optical Media Support / PS2/PSX emulation improvements / PS3MAPI support and i am missing alot of highlights that could be added. .
  • PRX plugins at boot time (sprx) - (Run in background)
  • Kernel Plugin Support
  • Game ISO Support: PS1/PS2/PS3/PSP/
  • Video ISO Support DVD/BluRay
  • Blu Ray Movie region free functionality
  • Split ISO support on FAT32 drives (4GB limitation, split ISO do not need merged play like unsplitted ISO's)
  • Network Support: PS1/PS3/DVD/BluRay in ISO and Remote Installation of PKGs
  • NTFS HDD Support (prepNTFS, or multiMAN Required to scan contents)
  • PS2 ISO Support non-BC (full software emulation) Consoles
  • PSP ISO Support on all PS3's (using Cobra Launcher, not all games work)
  • PS1/PS2 Improvements
    • Improper PSX region patching
    • Cobra opcode to bypass automatic detection of video mode and force specific video mode
  • PS3MAPI support, allows you to attach process on both CEX/DEX via its own API app.
  • Run Optical media (Burned/Burnt) support (PS1/PS3 Games for all cfw Models)

Also the MAMBA page there on that seems to be out of date as well, pointing to a 4.84 installation that does not apply today, .

@aldostools would know this the best, but i believe one the only current method of injecting mamba by an app is using IRISMAN. Also he is the guy to ask about the difference between mamba and cobra. Feature wise they are on par and mamba has became the test bed for many of cobra features (since mamba is safer for testing). the two offer difference in the scene as most of you know one is injected into the firmware and applied at boot everytime (unless disabled) and mamba is not built into the firmware but executed (though doesn't mamba have the ability to autoboot now??).

The feature set is the same but also differences how they execute and operate. Mamba was originally created by Estwald (Iris Manager developer), at the time the Cobra Payload was locked down the CobraUSB.. So estwald wanted to replicate some of Cobra's features and he started to do so and that is how MAMBA was born, overtime developer's like @_NvZ_ and @aldostools have been adding features to MAMBA. @aldostools currently maintains MAMBA and @Evilnat maintains Cobra.


You goto pages like the FAQ not a bad FAQ but not a good one either.
Example:

Q. I'm interested in developing for the PS3. Where can I start?
A. While this subreddit and Wiki is great for end-users, you are unlikely to find expert developer help here. You can see past and present research at the PS3 Devwiki, and get live help on the following IRC channels: #psdevwiki, #ps3dev, #psl1ght. PSL1GHT is a community-made open source SDK used to develop homebrew.
Click to expand...

I think one of the most important places for PS3 Development was left out here, if your trying to grow a scene would you not try and maybe mention where most of the PS3 Scene developer's tend to post project / information / Idea's and give support? I am just sayin'
they do say "While this subreddit and Wiki is great for end-users, you are unlikely to find expert developer help here." but you know where you are very likely to find expert developer help @ ______________ ? hmmmm its missing.. ..


The was an older wiki from reddit turned into a website later on,
They never updated the info when making into a website (but promoted it, instead of updating it)
 
Last edited:
Berion said:
You forgot about MFW. ;) It is just CFW but modified by MFW tool.
Click to expand...

I do not consider that a CFW type, Its CFW at end of the day.
Plus most using MFW for a firmware they are going to call it CFW anyway.

With so many terms and that really not meaning nothing at end of the day. I stopped using the term a long time ago.

Berion said:
It is CFW so not exactly like OFW, just with only patches allowing user to install CFW again.
Click to expand...
Not really,
It's OFW for CFW user's if you want to get technical.

Its not CFW in the traditional sense because it acts and behaves just as OFW would, not as CFW would,
It's essentially 99.9% OFW. Allow's CFW user's to use OFW without the need to re-jailbreak is all (modified firmware yes, CFW no)

Its like just like HFW,
Its not a CFW,
its an OFW that has swapped new webkit with old one.
(that modification unlike the Dualboot firmware still allows unmodded hacked console's to install the firmware)

They are both 99.9% identical to OFW and function as OFW would expect for those minimal changes in each

if MFW terms was not used wrongly, that may of been a good term to use for those today, As these are modified firmware's but MFW took on the same meaning as CFW and now i think the term MFW is burnt.. IMHO MFW builder should of just been called CFW builder back in the day :).
 
Last edited:
I'm glad to see that the ps3 community is still so active.
Shame those impostors who possibly steal data and also those youtubers who only promote bad practices.
 
I thought the years 2013..2015... Were the best best ever days for the ps3 scene... It's still going stronger and better than ever.. it's the most active scene so far compared to ps4 and other consoles. A great appreciate and gratitude to all the developers who contribute to the scene and give from their free time.
 
STLcardsWS said:
I do not consider that a CFW type, Its CFW at end of the day.
Plus most using MFW for a firmware they are going to call it CFW anyway.
Click to expand...
Indeed, it is not CFW type, but term wildly use back in time. Worth to add it just to clarify things for some diggers. ;]

Not really,
It's OFW for CFW user's if you want to get technical.
Click to expand...
Technically, it is CFW because it is modified OFW. Example with HFW doesn't fit here because HFW is assembled from two different OFW, nothing inside is modified, while those DualBoot have patched some files. It doesn't matter that patches only touching revoke list etc. The fact it is modified, making it been a CFW.
 
@STLcardsWS Sorry for bumping but this thread is pinned and is WIP... so I have a few comments -

Regarding Movian - It should be noted that while it can add support for container formats that are not natively supported (e.g. mkv) and certain audio codecs that aren't natively supported (e.g. flac) but it does not support video codecs that are not natively supported (e.g. x265, av1) and probably never will because that would require reimplementing them from scratch.

Regarding the overheating / dynamic fan control - It should be noted that no software based solution is a replacement for properly maintaining your console. If you never clean dust from the inside and never replace the thermal paste it will YLoD on you eventually.
 
You must log in or register to reply here.

Similar threads

Back
Top