Berion
Developer
NONE recovery mode is implemented in the official firmware (so called: BIOS) of SCPH and KDL models (COH and DESR are separate categories and require a separate guide), because it has never been and will not be needed by the user. PS2 firmware (BOOTROM and DVDROM) lies on ROM chips, which are, as the name suggests, read-only - so it cannot be overwritten. On the other hand, in the case of software such as HDD OSD (Browser 2.00), PSBBN (PlayStation Broadband Navigator) or Linux, which are all installed on the hard disk, this can be done from the disc (original and only on supported models). The same is true for update of DVD-Video player on the memory card.
The problem arises with exploits, which usually require other exploits to install them. And since the user usually has only one, or can only use one due to the console model or lack of required hardware, the so-called recovery mode, in which the user's configuration is ignored and from which any application can be launched, is useful. Of course, the role of recovery can be played by any attack vector, e.g. another memory card with FMCB, an internal hard drive, FDVDB (Free DVD Boot), etc., but the point of recovery mode is to use the same already installed exploit - a working one, with only the broken configuration and/or resources which can be replaced or restored.
Free McBoot (FMCB)
When the application starts, it looks for files on the USB:
Only FAT32 on MBR is supported. If GPT is used, the media will not be found, if exFAT is used FMCB will freeze, and if any other file system is used, as when the partition table is GPT, the media will also not be found.
PlayStation 2 Basic BootLoader (PS2BBL)
When the application starts, it looks for files on i.e the USB:
Both FAT32 and exFAT are supported - both on MBR. In the case of GPT, the media will not be found.
The problem arises with exploits, which usually require other exploits to install them. And since the user usually has only one, or can only use one due to the console model or lack of required hardware, the so-called recovery mode, in which the user's configuration is ignored and from which any application can be launched, is useful. Of course, the role of recovery can be played by any attack vector, e.g. another memory card with FMCB, an internal hard drive, FDVDB (Free DVD Boot), etc., but the point of recovery mode is to use the same already installed exploit - a working one, with only the broken configuration and/or resources which can be replaced or restored.
Free McBoot (FMCB)
When the application starts, it looks for files on the USB:
- mass:/RESCUE.ELF
- mass:/FREEMCB.CNF
Only FAT32 on MBR is supported. If GPT is used, the media will not be found, if exFAT is used FMCB will freeze, and if any other file system is used, as when the partition table is GPT, the media will also not be found.
PlayStation 2 Basic BootLoader (PS2BBL)
When the application starts, it looks for files on i.e the USB:
- mass:/PS2BBL/CONFIG.INI
Both FAT32 and exFAT are supported - both on MBR. In the case of GPT, the media will not be found.
Last edited:
