BleemSync has been superseded by a new project. For the latest in PlayStation Classic modifications, please use Project Eris!



After countless hours of development and cups of coffee, BleemSync by ModMyClassic is now Project Eris! Project Eris is intended to be the easiest and ultimate modding tool for the PlayStation Classic and should be the only tool you will ever need when it comes to modding the PlayStation Classic. Find it here!

The rest of this page is old information.

What is BleemSync?

BleemSync is a tool that originated by ModMyClassic’s very own DoctorDalek. Once he dumped the EMMC memory around the time of the PlayStation Classic release day, it was Hakchi’s MadMonkey who originally discovered the vulnerability of the GPG signing keys and bundled passphrase. Once it was realised that we were able to generate our own executable payloads for the console, DoctorDalek founded the BleemSync project. Since then, members of the ModMyClassic dev team with the help of external developers and with the assistance from Libretro, BleemSync has become what it is today. It’s still very much in early stages in terms of development but with a dedicated team behind it, developments and improvements are made each day.

Why BleemSync?

Create your custom PlayStation Classic experience by adding your own games, emulators, themes and mods.

Easy to use, UI application to use to allow easy game adding/syncing, modification and configuring. (Compatible with Windows, Mac and Linux)

Better FileSystem support (Ext4, exFAT, NTFS, FAT32)

OTG support (no more USB compatibility issues)

Network support (supports a limited number of Wi-Fi and Ethernet adapters)

Folder support

Drag and Drop game transfer now supported. (Drag games onto USB and it will load them up)

Multi OS support (Windows, Mac, Linux) (basically anything that has a RDNIS driver. Which is a lot.)

Reliable and steady emulation performance.

RetroArch support and Integration.

Multitude of various controller support with RetroArch.

Big community available to offer support to fellow users.

And many more awesome features!

Requirements to use BleemSync

Windows, Mac, Linux is supported. (In theory chromeOS (untested))

A low powered USB drive to install initial payload. After that any USB is supported via OTG.

If you want to use the on console BleemSync UI tool: Generic RDNIS driver (this should auto install for Windows and Linux. Mac driver can be found here) note 1 – The PSC is disguised as a Samsung Galaxy (same as Hakchi) so it should easily install when connected. note 2 – If you use Hakchi CE for the (S)NESC then you very likely have the RDNIS driver installed already. (It uses the same driver) note 3 – If in doubt regarding the Windows RDNIS driver you can grab it here A half decent web browser. (Google Chrome, Firefox, Microsoft Edge, Safari, Opera) (Internet Explorer is NOT supported!)



How to use BleemSync

The BleemSync UI app actually runs on the console itself, however we now have a new drag’n’drop method available where you can just drop your games on the usb and it will process them (read more below).

How to install from fresh (Including OTG setup):

Show More

BleemSync v1.2 – Installing from fresh Disclaimer – We are not responsible for any damage caused to your console. Please note that you are installing and using at your own risk! Download the BleemSync v1.2 zip package to your computer. Format a USB drive (USB 2.0 preferable) to FAT32 and label it SONY. The format must be FAT32 or ext4. Extract the zip package to the root of your newly formatted USB. Make sure your console is unplugged from power. Insert the USB to controller port 2 on your console and hook the console power back up. Progress updates are displayed on the screen so it is recommended to have the HDMI cord plugged in. It is recommended that while updating you do not have any other usb devices connected to your console. Note: If you have an externally powered usb hub, insert your usb drive into the hub and insert the hub into controller port 2. (Recommended for users with USB power issues) When the console’s LED is orange, power it on as normal and wait! The system will create a backup of your existing kernel, recovery, and data partitions. This may take up to 5 minutes. The LED will alternate green and red while this is happening, and the following will be displayed on screen: Screenshot After the backup has completed the initial payload will be installed to the console. When the payload has finished installing you should see this screen: Screenshot Once the console has powered off and you see an orange LED. Remove your usb stick and plug it into your computer. IMPORTANT: Create a backup of your consoles backup files copy them somewhere safe. The backup files are stored in USB:\bleemsync\backup . It is important you keep a copy of these files somewhere safe. They are unique and can only be used on the console that created them. DO NOT DELETE THESE FILES FROM THE USB DRIVE! If they do not exist then the console will re-create them on boot (and any backups made subsequent to this would be of the upgraded BleemSync kernel and not the original one). Download the custom kernel (LBOOT.EPB) and save it to USB:\bleemsync\update . Safely remove the usb from your computer and plug it back into your console. Turn on your console. The console will count down from 5 before performing the kernel upgrade. During the upgrade the console will turn off (LED completely off), turn back on (LED flashing green), and then turn off once more. When the LED has returned to orange the installation of BleemSync is now complete! Turn the console back on and it will now boot to the BleemSync Boot Menu. Next Steps Ensure you have created multiple copies of the backup files. The backup files are stored in USB:\bleemsync\backup . It is important you keep a copy of these files somewhere safe as they will be required should you need to revert your console back to stock or recover your console. They are unique and tied to the console that created them. There will be three files: USB:\bleemsync\backup\LBOOT.EPB USB:\bleemsync\backup\LBOOT_KERNEL.EPB USB:\bleemsync\backup\LRECOVERY.EPB Do not delete these files from the USB drive. If they do not exist then the console will re-create them on boot (and any backups made subsequent to this would be of the upgraded (modified) system and not the original one). Reformat your USB drive in a better format. exFAT, NTFS and ext4 are all supported. Simply copy the entire contents of your USB drive to your computer, format the drive in the format you want (remember to name the drive SONY), and then copy the contents back to your USB drive. Note however that should you want to restore your kernel (or further upgrade to any future kernel releases) then you will need to reformat you drive into FAT32 or ext4 (or use a secondary usb for the upgrade). The kernel upgrade process is not compatible with NTFS or exFAT (Optional) Use your OTG cable! Simply connect your USB drive to your OTG cable and start the console as normal. BleemSync will load in the same way that it would when you connect it to controller port 2.

How to update from previous BleemSync versions (0.x, 1.x etc):

Show More

BleemSync v1.2 – Updating from BleemSync from 1.1 Disclaimer – We are not responsible for any damage caused to your console. Please note that you are installing and using at your own risk! Please Note: You should ALWAYS backup your usb before attempting to upgrade. The upgrade shouldn’t affect your data however we can not guarantee that you will not lose data in the process. So please backup your usb data before attempting. Download the new BleemSync zip package to your computer. Extract the folders from the zip to your usb. Overwrite any existing files/folders. (Note: Mac users should choose merge not replace when extracting the new files to the usb) (Optional) This update resets your RetroArch settings to update the downloader url. If you wish to keep your existing settings please delete the UPDATE_RA_CONFIG file in USB:\bleemsync\flags . You may also skip the payload reinstall by deleting the rest of the files in the flags directory. Connect your usb drive to your console as you normally would and power on the console. The update is now complete. Optional Kernel Update A new kernel is available for BleemSync 1.2 that adds in support for additional network adapters and restores rumble functionality for certain controllers to install the new kernel please follow the instructions below. (Note: Kernel upgrades must be done via the front usb ports using a usb with either a FAT32 or ext4 filesystem) If your usb drive is formatted as NTFS/exFAT please stop here and see “Flashing kernel using secondary USB” otherwise continue. Download the custom kernel (LBOOT.EPB) and save it to USB:\bleemsync\update . Safely remove the usb from your computer and plug it back into your console. Turn on your console. The console will count down from 5 before performing the kernel upgrade. During the upgrade the console will turn off (LED completely off), turn back on (LED flashing green), and then turn off once more. When the LED has returned to orange the upgrade is now complete! Turn the console back on and it will now boot to the BleemSync Boot Menu. BleemSync v1.2 – Updating from BleemSync from 1.x Disclaimer – We are not responsible for any damage caused to your console. Please note that you are installing and using at your own risk! Please Note: You should ALWAYS backup your usb before attempting to upgrade. The upgrade shouldn’t affect your data however we can not guarantee that you will not lose data in the process. So please backup your usb data before attempting. Remove the old payload folder (f854cc9b-6cfc-4524-90a2-a2b35bbc3e24) from your usb. Download the new BleemSync zip package to your computer. Extract the folders from the zip to your usb. Overwrite any existing files/folders. (Note: Mac users should choose merge not replace when extracting the new files to the usb) Connect your usb drive to your console as you normally would and power on the console. It is recommended that while updating you do not have any other usb devices connected to your console. The system will create a backup of your existing kernel, recovery, and data partitions. This may take up to 5 minutes. The LED will alternate green and red while this is happening, and the following will be displayed on screen: Screenshot After the backup has completed the initial payload will be installed to the console. When the payload has finished installing you should see this screen: Screenshot Once the console has powered off and you see an orange LED. Remove your usb stick and plug it into your computer. IMPORTANT: Create a backup of your consoles backup files copy them somewhere safe. The backup files are stored in USB:\bleemsync\backup . It is important you keep a copy of these files somewhere safe. They are unique and can only be used on the console that created them. DO NOT DELETE THESE FILES FROM THE USB DRIVE! If they do not exist then the console will re-create them on boot (and any backups made subsequent to this would be of the upgraded BleemSync kernel and not the original one). If your usb drive is formatted as NTFS/exFAT please stop here and see “Flashing kernel using secondary USB” otherwise continue. Download the custom kernel (LBOOT.EPB) and save it to USB:\bleemsync\update . Safely remove the usb from your computer and plug it back into your console. Turn on your console. The console will count down from 5 before performing the kernel upgrade. During the upgrade the console will turn off (LED completely off), turn back on (LED flashing green), and then turn off once more. When the LED has returned to orange the upgrade is now complete! Turn the console back on and it will now boot to the BleemSync Boot Menu. Next Steps Ensure you have created multiple copies of the backup files. The backup files are stored in USB:\bleemsync\backup . It is important you keep a copy of these files somewhere safe as they will be required should you need to revert your console back to stock or recover your console. They are unique and tied to the console that created them. There will be three files: USB:\bleemsync\backup\LBOOT.EPB USB:\bleemsync\backup\LBOOT_KERNEL.EPB USB:\bleemsync\backup\LRECOVERY.EPB Do not delete these files from the USB drive. If they do not exist then the console will re-create them on boot (and any backups made subsequent to this would be of the upgraded (modified) system and not the original one). Reformat your USB drive in a better format. exFAT, NTFS and ext4 are all supported. Simply copy the entire contents of your USB drive to your computer, format the drive in the format you want (remember to name the drive SONY), and then copy the contents back to your USB drive. Note however that should you want to restore your kernel (or further upgrade to any future kernel releases) then you will need to reformat you drive into FAT32 or ext4 (or use a secondary usb for the upgrade). The kernel upgrade process is not compatible with NTFS or exFAT (Optional) Use your OTG cable! Simply connect your USB drive to your OTG cable and start the console as normal. BleemSync will load in the same way that it would when you connect it to controller port 2. BleemSync v1.2 – Updating from BleemSync from 0.x Disclaimer – We are not responsible for any damage caused to your console. Please note that you are installing and using at your own risk! Please Note: You should ALWAYS backup your usb before attempting to upgrade. The upgrade shouldn’t affect your data however we can not guarantee that you will not lose data in the process. So please backup your usb data before attempting. Open your USB drive using a file explorer and delete the following folders if they exist: 028c18a9-ec4b-4632-b2cf-d4e20f252e8f lolhack BleemSync NOTE: It is important to only delete these files. If you delete any other BleemSync files then the migration is less likely to be successful. Download the new BleemSync zip package to your computer. Extract the folders from the zip to your usb. Overwrite any existing files/folders. (Note: Mac users should choose merge not replace when extracting the new files to the usb) Connect your usb drive to your console as you normally would and power on the console. It is recommended that while updating you do not have any other usb devices connected to your console. The system will create a backup of your existing kernel, recovery, and data partitions. This may take up to 5 minutes. The LED will alternate green and red while this is happening, and the following will be displayed on screen: Screenshot After the backup has completed the initial payload will be installed to the console. When the payload has finished installing you should see this screen: Screenshot Once the console has powered off and you see an orange LED. Remove your usb stick and plug it into your computer. IMPORTANT: Create a backup of your consoles backup files copy them somewhere safe. The backup files are stored in USB:\bleemsync\backup . It is important you keep a copy of these files somewhere safe. They are unique and can only be used on the console that created them. DO NOT DELETE THESE FILES FROM THE USB DRIVE! If they do not exist then the console will re-create them on boot (and any backups made subsequent to this would be of the upgraded BleemSync kernel and not the original one). If your usb drive is formatted as NTFS/exFAT please stop here and see “Flashing kernel using secondary USB” otherwise continue. Download the custom kernel (LBOOT.EPB) and save it to USB:\bleemsync\update . Safely remove the usb from your computer and plug it back into your console. Turn on your console. The console will count down from 5 before performing the kernel upgrade. During the upgrade the console will turn off (LED completely off), turn back on (LED flashing green), and then turn off once more. When the LED has returned to orange the upgrade is now complete! Turn the console back on and it will now boot to the BleemSync Boot Menu. Next Steps Ensure you have created multiple copies of the backup files. The backup files are stored in USB:\bleemsync\backup . It is important you keep a copy of these files somewhere safe as they will be required should you need to revert your console back to stock or recover your console. They are unique and tied to the console that created them. There will be three files: USB:\bleemsync\backup\LBOOT.EPB USB:\bleemsync\backup\LBOOT_KERNEL.EPB USB:\bleemsync\backup\LRECOVERY.EPB Do not delete these files from the USB drive. If they do not exist then the console will re-create them on boot (and any backups made subsequent to this would be of the upgraded (modified) system and not the original one). Reformat your USB drive in a better format. exFAT, NTFS and ext4 are all supported. Simply copy the entire contents of your USB drive to your computer, format the drive in the format you want (remember to name the drive SONY), and then copy the contents back to your USB drive. Note however that should you want to restore your kernel (or further upgrade to any future kernel releases) then you will need to reformat you drive into FAT32 or ext4 (or use a secondary usb for the upgrade). The kernel upgrade process is not compatible with NTFS or exFAT (Optional) Use your OTG cable! Simply connect your USB drive to your OTG cable and start the console as normal. BleemSync will load in the same way that it would when you connect it to controller port 2.

How to migrate from other previous tools:

Show More

BleemSync – Migrating to BleemSync from other tools

There is no easy way to say this however a lot of other “hacks” and “tools” out in the wild use a multitude of different formats or even bolted on to the side of old BleemSync versions. We can’t really accommodate for this or guarantee that other builds will bolt into BleemSync. The best thing to do in this instance would be to download your games and saves and do a fresh install (instructions above) and manually copy over your saves after you have configured your set up using the BleemSync UI

How to uninstall BleemSync:

Show More

BleemSync – How to Uninstall BleemSync These instructions specify how to remove the BleemSync payload from the internal memory of the console. We only advise you do this if you are giving away or returning the console. Keeping the BleemSync payload installed is beneficial even when switching to a different mod. You can remove BleemSync from your usb simply by reformatting the usb or deleting the files. BleemSync 1.1 or later: Create a file called UNINSTALL in USB:\bleemsync\flags\ . Note: The file is case sensitive and must not have a file extension. Plug the usb into your console and boot like normal. Wait until a message on the screen notifies you it is safe to shutdown the console. Remove the power cord from the console.

BleemSync 1.0 or earlier:

Download the uninstall image here: Uninstall Image Unzip the img file to your computer Burn the image to a USB using something like Etcher (Link can be found here: ) https://www.balena.io/etcher/ Completely unplug everything from your console and insert the usb in PORT 2 Plug in the power and press the power button (once the LED is ORANGE) This should only take a very short time and the LED should go out and back to orange when done.

How to use the new BleemSync ‘Drag’n’Drop’ transfer method:

Show More

Introduction The transfer tool is a new feature in BleemSync v1.1. It can be used to automatically add games to BleemSync via the USB drive rather than connecting the console to your PC. The transfer tool will run automatically during the BleemSync boot process and will generate games with information from the included database. Currently the transfer tool only supports PSX games. Cover Setup (Optional) Covers are not included in the release by default however they can be added in 2 different ways. First you can include a cover with the game files (see process below). Otherwise you can download a collection of over 9000 game covers from here. Download either the Default Thumbnails PNG or Regional Case Thumbnails zip files (Thanks to Rocky5 for providing these covers). The cover images must be extracted from the zip archive to USB:\bleemsync\opt\psc_transfer_tools\covers. When adding games the tool will automatically pull covers from this folder if it matches the serial number of the game being added. Transfer Process After running the BleemSync v1.1 payload for the first time you should see a transfer folder on your USB (USB:\transfer). If you have not yet run the payload you can create the transfer folder manually. To transfer games all you need to do is copy a game in a supported format (see below) to the transfer folder. The tool will process the game files and any related files. Cue files (for games that require them) will be validated/corrected if supplied. If a cue file is required and is not supplied a generic cue file will be generated. Note: cue files added to the transfer folder will not be automatically deleted, please verify generated cue file is correct before deleting. Custom Covers To add a custom cover the cover image must share the same filename as the game only with the png extension. If a custom cover is not provided in the transfer folder the tool will look for a cover image matching the game’s serial number in the covers folder (USB:\bleemsync\opt\psc_transfer_tools\covers). JPEG images are also supported by the stock UI however the extension must be changed to “.png” to work with the transfer tool. Note: JPEG files cannot be displayed as thumbnails in RetroArch playlists Multi-Disc Games Multi-disc games should be handled properly so long as all discs are transferred at the same time. For multi-disc games it is best if the name format is similar to GameName (Disc 1), GameName (Disc 2) .etc although this is not required as long as the discs are sorted alphabetically. Multi-Track Games Multi-Track game support is included. For multi-track games it is best if you provide the cue file for said game. If the cue file cannot be found a cue will be generated automatically however it may not be valid for every game. The naming scheme for multi-track games is strict and MUST be followed, failure to do so will cause the game to be added incorrectly. The naming scheme is as follows: GameName.cue

GameName (Track 1).bin

GameName (Track 2).bin Note: For games with 10 tracks or more each track file must have a two digit track number. SBI Files Certain PAL games require SBI files these files must be added to the transfer folder along with the corresponding game. SBI files can either be named the same as the game’s serial or match the game’s filename. Supported Formats The following are the only game formats are supported: BIN+CUE

BIN

IMG

ISO

PBP

How to use on console BleemSync UI:

Show More

BleemSync v1.2 – How to use BleemSync UI to sync games and change config

Please Note: The BSUI will not work when running in OTG + drag’n’drop mode. It’s advised you check one of the youtuber how-to videos below for a easier visual and audio based tutorial, but once you have successfully installed BleemSync 1.1 and have your formatted USB ready… Always make sure you have no power connected when plugging in the USB. (This also includes external power for powered USB hubs!) Plug your formatted USB (with the bleemsync app and bootloader) into controller port 2 on your console. Connect your console to your pc using the power USB cable as normal. When the LED turns ORANGE, turn on the console as normal. If you already have the RDNIS driver installed you should hear/see a connection sound as the USB device is recognised and the console turns on. If not your OS should automatically install it for you.

Note 1 – If you are on MAC you will require to download the driver manually here: https://goo.gl/FQYNW5

Note 2 – If you already use Hakchi CE on your PC you should have the RDNIS driver installed

Note 3 – If unsure, plug in and power on and check your device manager. You should see something like: http://prntscr.com/mapcf6 If you have the console connected to HDMI, you want to boot to the boot menu. If HDMI is connected, the UI will only work whilst you are waiting on the Boot Menu screen.

Note 1 – The console is set to boot directly to the boot menu by default

Note 2 – If you disconnect the HDMI cable the console will always start the on console BleemSync UI Once you have given the console approximately 10 seconds from turning on, open your desired web browser (Internet Explorer is not supported!)

The following steps we are currently in the process of improving, please bare with us.

Troubleshooting 1 – If your console has not yet properly loaded the BleemSync UI you are likely to see something like:

Troubleshooting 2 – If you tried for over a minute and still have nothing then you have likely not got the RDNIS driver. Check your device manager to ensure that your driver is installed

Troubleshooting 3 – Might seem dumb but you might have not turned the console on or you don’t have the USB with BleemSync on it connected to the PSC port 2.

Troubleshooting 4 – If your RDNIS is connected and you still don’t have any luck. If you shutdown the PSC and plug your USB in to the PC, check your logs. It’s likely your USB is incompatible or is corrupt.

Troubleshooting 5 – If all else fails, check the how-to videos to make sure you are doing it correct and then send us your logs in the Discord support channel and we will look at it for you. (PLEASE exhaust all other options first) Go and visit http://bleemsyncui.com/ failing that you can try http://169.254.215.100:5000/ Troubleshooting 1 – If your console has not yet properly loaded the BleemSync UI you are likely to see something like: http://prntscr.com/maph2k If this is the case then just wait 5-10 seconds and try again.Troubleshooting 2 – If you tried for over a minute and still have nothing then you have likely not got the RDNIS driver. Check your device manager to ensure that your driver is installedTroubleshooting 3 – Might seem dumb but you might have not turned the console on or you don’t have the USB with BleemSync on it connected to the PSC port 2.Troubleshooting 4 – If your RDNIS is connected and you still don’t have any luck. If you shutdown the PSC and plug your USB in to the PC, check your logs. It’s likely your USB is incompatible or is corrupt.Troubleshooting 5 – If all else fails, check the how-to videos to make sure you are doing it correct and then send us your logs in the Discord support channel and we will look at it for you. (PLEASE exhaust all other options first) On Successful load it will take a few seconds and you should now see the BleemSync UI http://prntscr.com/mapphg You are good to go! Check out one of the YouTube how-to videos below for a more in depth how-to use and add games as it’s too detailed for this guide.

How to set your Wireless Network Information:

Show More

There are multiple ways to configure BleemSync to connect to your wireless network. The easiest method is via usb detailed below. You can also configure the network by connecting to the console via telnet/ssh and running the command wifi-wpa-setup or manually configuring the wpa_supplicant.conf file in USB:\bleemsync

etwork\etc\wpa_supplicant Create a new file called ssid.cfg in USB:\bleemsync\etc\bleemsync\CFG . Open this file with a text editor. Add your SSID Name on the first line of the file. Add your password to the next line. Save the file and safely remove the usb from your PC. Plug the usb into your PS Classic and boot up as normal. Ensure you have set enable_networking to TRUE in the Settings Menu Example ssid.cfg : MYNETWORKNAME MYNETWORKPASSWORD

How to use BleemSync Folders:

Show More

Folder support has been added to BleemSync in version 1.2. Folders are currently created and managed using the on-console Folder Manager app. This app is added as a launcher and requires the ui_app_launchers variable to be set to TRUE in the Settings Menu to be accessible. The Folder Manager is accessible through the carousel. Folders can only be created and swapped using the Folder Manager app. Future versions will allow folders to be added to the carousel as well as support adding launchers to particular folders. The procedure below explains how to create and use a folder. Select Folder Menu from carousel. Press R1 to create a new folder. Configure your folder name, icon and games. Press Save to create your new folder. On the Folder Select screen press X to enter your new folder To exit out a folder enter the Folder Menu and either enter a new folder or press O to exit without selecting a folder.

Flashing kernel using secondary USB:

Show More

Flashing a kernel to the system requires either a FAT32 or ext4 file system. If your usb is formatted as NTFS or exFAT you will need to either use a secondary USB to flash the system. Alternatively you can completely backup all the files from your original USB to your computer and reformat it to FAT32 or ext4 to complete this process, once the process is complete the usb can be reformatted back to the original file system, and you can restore all the files. Format a USB drive (USB 2.0 preferable) to FAT32 and label it SONY. The format must be FAT32 or ext4. Extract the BleemSync v1.2 zip package to the root of your newly formatted USB. Copy your backup files from your original USB (or backup) to your new USB. Make sure they are placed in USB:\bleemsync\backup you will need to create this folder if it does not exist. Download the custom kernel (LBOOT.EPB) here, and save it to USB:\bleemsync\update . Safely remove the USB from your computer and plug it back into your console. It is recommended that while updating you do not have any other USB devices connected to your console. Turn on your console. The console will count down from 5 before performing the kernel upgrade. During the upgrade the console will turn off (LED completely off), turn back on (LED flashing green), and then turn off once more. When the LED has returned to orange the kernel upgrade is now complete! You can now remove the USB. You can now return to using your original USB.

Where to Download

BleemSync 1.2.0

BleemSync 1.2.0 Custom Kernel

Addon Packs

BleemSync 1.1.0 RetroArch Only Addon (Unzip on to USB after install to boot directly to latest RA and DB files etc pre installed)

BleemSync 1.1.0 RetroArch Cheat Pack

BleemSync 1.1.0 RetroArch Overlay Pack

Latest Feature List

BleemSync v1.2 Release Notes:

Show More

BleemSync v1.2 Release Notes Added Network support

Added Folder support with on-console Folder app

Added on-console Game Manager app

Updated RetroArch to 1.7.8

Fixed issues with transfer tool and pbp files

Improved transfer tool serial identification

Fixed issue with RetroArch playlist generator

Fixed stock emulator multi-disc launching issue

Added new settings variables to web UI

Added new settings variables to settings menu

Modified settings menu to dynamically load modifiable variables from file



BleemSync v1.1 Release Notes:

Show More

BleemSync v1.1 Release Notes Added OTG support

Added on usb Drag’n’Drop transfer tool

Added kernel backup/restore

Updated xpad.ko for increased controller support

Added launcher to stock carosel

Added thumbnails to internal RA playlist

SSH support added

Added status text to boot sequence

Added 3rd party controller support to Stock UI

Fixed issue with extra discs displaying on pcsx “Disc Change” screen

Reduced Theme Mounting load times

Added tool to generate RA playlists for external (usb) games

Added settings menu

Added texture filter toggle to stock pcsx emulator

Updated RetroArch to 1.7.7

Fixed RetroArch black screen bug

Added glui menu to RetroArch

Added compressed core support to RetroArch

Bundled pcsx RetroArch core now supports chd files

BleemSync v1.0.1 Release Notes:

Show More

BleemSync v1.0.1 Release Notes

Payload Changes Fixed broken RA font on copy over from console

Migrate now migrates over cores and bios files correctly

Added Credits and License information

Added Uppercase support for alternative format games

Fixed network RA buildbot issues.

Fixed JAPAN console RA stock game list in RA GUI

Fixed JAPAN stock EMMC games to prevent crashing when loading BS1.0 on JP console

Optimised on console SQLITE3 code

Fixed the chance of RA overwritting good fixed configs with crap ones.

Fixed Old RA folder not moving to remove/ after migration

If no retroarch core options config exists then create. (Stops overwriting existing global core configs)

Changed config logic so if no cfgs used for BS or RA then create them on load with defaults

ADDED UPDATE_CONFIG, UPDATE_RA_CONFIG and UPDATE_BOOT to supported flags (use to force update cfg with defaults)

Added Xpad driver support. Loads more controller support added, including Xbox 1, Xbox 360 and steam controller support. Mostly complete list available here: list

Added SDL mapping support for the boot menu, (List of mapped controllers)

Added physical console button support for the boot menu

(`reset` toggles options. `open` selects that option)

(`reset` toggles options. `open` selects that option) Changed memory configuration to prevent crashes from occurring when memory limit is nearing. We now over commit memory so a lot of issues should now be prevented.

Overcommit the DRAM

Created extra fast swap ram totalling to 512mb more memory split across 4 cores into 128mb banks to increase compatibility, stability and slight performance (in some small cases)

Added new bleemsync build of RetroArch 1.7.6

UPX’d RetroArch 1.7.6

Optimised Monochrome XMB theme assets for Ozone

Compressed all RA bundled assets

Added brand new Ozone theme as default (won’t override existing set ups)

Added compressed Ozone theme assets

Prepped some code for OverClocking and network support within RA

Optimised GDB and SQLite3

Improved initial RA directory structure

Optimised RA as a whole down from 18.2mb to 8.23mb (approx 50% reduction whilst include many more features)

Optimised whole payload and reduced size UI Changes Fix database entry generation when .cue file extension is not all lowercase.

Fixed issue where cue files were being created for pbp files. No longer necessary with intercept updates.

Fixed issue with cue files with capital filenames being added to the system improperly

Added full rebuild regional.db button to BleemSync UI

BleemSync v1.0 Release Notes:

Show More

BleemSync v1.0 Release Notes

General Updates Added brand new UI to allow easy syncing and modding for your PlayStation Classic!

USB payload completely redone from scratch, much better design meaning more stability, faster boot times and more flexibility.

Added support to the stock console UI for the additional PS1 formats “m3u” “pbp” “img” “mdf” “toc” “cbn”

Completely new and improved bootloader. Contains more sense checking and script vetting to ensure no broken boots. (No more lolhack)

Auto deployment/install and update facility added.

Added permanent safe USB lockout disable, telnet and ftp support. (These services will install on initial install so you don’t need a USB to load these services)

Added NTFS and exFAT drive support. (Once initial install in complete)

Because of the USB lockout disable, you can now run psc from TVs and PC USB ports.

Improved LED support, green = idle/OK, orange = BS function running, flashing red = attention needed, see on screen. (You can now see exactly when something is running)

Added function libraries so you can add your own scripts in to the boot sequence if you wish for extra tinkering

Added boot profiler (Every function in the boot sequence will get timed and recorded so you can identify slow down issues within boot)

Integration of RetroArch by default (will be optional in later builds)

Added full verbose logging, any issues should now be logged easily within the logs directory of the USB to help easily identify common issues

Initial install sets up basis for backup/restore and OTG support (coming in 1.1)

Game folders are much less complicated and require less mounting per game.

Included patch pack for stock 20 games to run at full speed if launched via RetroArch PCSX from either stock UI or playlist.

Added auto migration tools to run on first boot after install. General Updates UI Features TBA Boot Updates Added the ability to fully customise your boot routine. You can select what functions/routines and extra debugging routines are run during boot time.

Added customisable boot options, including quick load, Heath check disable and custom splash screen support. (Static only supported for 1.0)

Added kickass BleemSync splash screen on load (Can be disabled or customised)

Added new build of BootMenu as default, now with BleemSync theme images and the ability to change the boot menu background theme too. (Just like the splashscreen)

Added boot menu music toggle

Bundled custom original (90s ps1 demo style) boot menu music

Added the facility so you can boot directly to the bootmenu, RetroArch or the stock UI. (Configurable from USB or UI)

Removed the long boot times, especially for large collections! Stock UI Updates Added ability to load in original 20 games on EMMC into the stock UI including your customs.

Added auto alphabetical’ising’ so you can sort automatically by alphabetical order. (You can also set your own order from the UI)

Added ability to easily load in custom UI themes, you can load as many themes on to the usb and select from the config.

Added ability to randomise themes on boot * Included completely original custom theme for bleemsync. (Configurable)

Themes now no longer need all theme files to work. Just requires the files you wish to replace. (Includes sounds)

Added the ability to launch all pcsx games from the stock UI with RetroArch PCSX (recommended!)

Added support for savestates and save files when launching games via RA PCSX

Added physical console button support to emulate stock PCSX emulator RetroArch Updates Improved the RetroArch deployment method for the PSC

Automatically loads in on console PS1 bios to RetroArch on first boot so no requirement to source ps1 bios

Improved playlist support to make it easier to use

Included all core info files by default

Fixed mappings for PS3 and PS4 controllers

Include completely custom and exclusive PSC RA theme. (A homage to the PS4 20th anniversary PS1 theme)

Also included updated monochrome theme (just switch from custom theme to monochrome if you wish)

Added overlay support with scanlines available by default

Added stock ps1 games in playlist so you can load stock games directly from RA playlist

Cut out dead weight and reduced file size of RetroArch

Improved screenshot saving for retroarch when saving screenshots for save files

Redone initial config and optimised the settings for psc

Set proper notification background and fonts

Misc bug fixes and improvements Misc Updates Added devtools like GDB, readelf, ldd and nano etc. Also made accommodations so you can easily mount your own binaries/libraries to the console. (SAFELY)

Plus a ton more small things and other features I forgot to mention 🙂

ModMyClassic Youtuber Videos

Click below for a embeded list of youtuber’s how to videos:

BleemSync v1.2 videos:

Show More

BleemSync v1.1 videos (Update, Fresh Install, new transfer tools tutorials):

Show More

BleemSync v1.0 videos:

Show More

Credits (WIP)

DoctorDalek (PatHartl) – Developer and project founder

Swingflip – Developer

CompCom – Developer

Cyanic – Developer

Andshrew – Developer

BBsan – Developer

Wraith – Developer

Rocky5 – Developer

HoneyLab – Developer

Defkorns – Developer

DanTheMan827 – Developer (Provided code for debug and RDNIS)

Advokaten – Developer (Added the stock game playlist for RetroArch)

Rubixcube6 – Graphic Artist (Logo, Boot Menu Theme, RetroArch icons, splash screens)

JustAndy – Graphic Artist (Stock UI theme)

Forsh – Sound Artist (Boot Menu loop)

Milenko – License and wiki moderator

Special Thanks to:



MadMonkey – Originally found the GPG signing key + passphrase flaw.

ModMyClassic Supporters – All their help and support. Especially helping with debugging and testing.

FAQ

Q. Does 1.1 improve USB compatibility?

A. YES – As of 1.1 we now provide OTG support which now means there is NO compatibility issues with USBs when running from an OTG adapter.

Q. Does this software modify my PS Classic?

A. Yes – This does mean that you have to install a very small payload to your console (2mb and 11 files). However this is completely safe and unless you hooked the PSC to the pc and tried to telnet to it, you wouldn’t know the difference. If you have no USB devices attached with the payload installed, it will boot like stock. The purpose of the payload is to enable FTP,TELNET,RDNIS, exFAT and NTFS drive support. You can still run older versions of BleemSync WITH the payload installed.

Q. What does backup do?

A. Backup will create upgrade packages, containing your partitions. As those upgrade packages will need signatures to get installed, the signatures are created as well and attached to the debug packages. To ensure, one does not accidentally try to restore a backup created from another console, the signature key is again encrypted with a unique key for each console. The backups are created under

/media/bleemsync/backup

There are three kinds of backups:

LBOOT.EPB: Backup of the main partition (ROOTFS1), user data partition, kernel partition and trusted zone

Backup of the main partition (ROOTFS1), user data partition, kernel partition and trusted zone LRECOVERY.EPB: Backup of the recovery partition (ROOTFS2), recovery kernel and recovery trusted zone

Backup of the recovery partition (ROOTFS2), recovery kernel and recovery trusted zone LBOOT_KERNEL.EPB: Backup of only the main kernel and the trusted zone

Q. How do I backup?

During boot Bleemsync Bootloader will check, if Backups are already present. If not, all backups are created. You can also force creation of a new backup with the following flags:

/media/bleemsync/flags/BACKUP_MAIN

/media/bleemsync/flags/BACKUP_RECOVERY

/media/bleemsync/flags/BACKUP_KERNEL

After backup: STORE YOUR BACKUPS SAVELY! YOUR USB DRIVE IS NOT A SAFE PLACE! SAVE IT TO YOUR PC, DROPBOX, NEXTCLOUD – WHATEVER!!!

Q. What does restore do?

A. Restore will restore one of your backups. It uses the built in updater by SONY to do so.

Q. How do I restore?

A. Restore is triggered through the restore flags:

/media/bleemsync/flags/RESTORE_MAIN

/media/bleemsync/flags/RESTORE_RECOVERY

/media/bleemsync/flags/RESTORE_KERNEL

Please note: Restore will apply the complete backup as it is. This means your PSC will be set to the same state as when the backup was created. All your settings, customizations and savegames that are on userdata WILL BE LOST.

Q. HELP!!! My PSC does not boot after restore!

A. Overall this should not happen, as there is a verification before a backup gets flashed. However, there still may be some reasons why this may happen:

Backup got corrupted

Power loss during restore

Brown Out of USB drive

If such a case happens but you kept your backup save at another location there is no need to panic!

The PSC uses FASTBOOT as a last resort if any backup flashing went wrong. Fastboot needs the raw partition image in order to restore. Therefore you need to do the following steps:

Extract your EPBs (LBOOT, LRECOVERY) with a ZIP tool of your choice. It will extract the following files: boot.img (for LBOOT and LRECOVERY) tz.img (for LBOOT and LRECOVERY) rootfs.ext4 (for LBOOT and LRECOVERY) userdata.ext4 (for LBOOT)

Open your PSC and connect the two big points above the “LM-11” text with a paperclip

Connect the PSC to the USB of your PC

Use fastboot to flash the partitions

In Linux/Mac one can use the following shell script if fastboot is in your path:

#!/bin/sh mkdir BOOT RECOVERY unzip LBOOT.EPB -d BOOT unzip LRECOVERY.EPB -d RECOVERY fastboot flash BOOTIMG1 BOOT/boot.img fastboot flash TEE1 BOOT/tz.img fastboot flash ROOTFS1 BOOT/rootfs.ext4 fastboot flash USRDATA BOOT/userdata.ext4 fastboot flash BOOTIMG2 RECOVERY/boot.img fastboot flash TEE2 RECOVERY/tz.img fastboot flash ROOTFS2 RECOVERY/rootfs.ext4 dd bs=1 if=/dev/zero of=misc.img count=16 fastboot flash MISC misc.img fastboot reboot rm -rf BOOT RECOVERY misc.img

PSCRecover.ps1

mkdir "BOOT","RECOVERY" Rename-Item LBOOT.EPB LBOOT.EPB.zip Expand-Archive LBOOT.EPB.zip -DestinationPath "BOOT" Rename-Item LRECOVERY.EPB LRECOVERY.EPB.zip Expand-Archive LRECOVERY.EPB.zip -DestinationPath "RECOVERY" .\fastboot.exe flash BOOTIMG1 BOOT\boot.img .\fastboot.exe flash TEE1 BOOT\tz.img .\fastboot.exe flash ROOTFS1 BOOT\rootfs.ext4 .\fastboot.exe flash USRDATA BOOT\userdata.ext4 .\fastboot.exe flash BOOTIMG2 RECOVERY\boot.img .\fastboot.exe flash TEE2 RECOVERY\tz.img .\fastboot.exe flash ROOTFS2 RECOVERY\rootfs.ext4 .\fastboot.exe flash MISC misc.img .\fastboot.exe reboot Get-ChildItem "BOOT","RECOVERY" -Recurse | Remove-Item -Recurse "BOOT","RECOVERY" Rename-Item LBOOT.EPB.zip LBOOT.EPB Rename-Item LRECOVERY.EPB.zip LRECOVERY.EPB

Q. I don’t like the new splash, boot menu or stock UI. Can I change?

A. Yes you can change this in the bleemsync Configuration in BleemSync UI. You can also swap out all the splashscreen images, themes etc

Q. I don’t like the new RetroArch theme.

A. Are you mad? Anyway, you can change it to monochrome in the RetroArch display settings

Q. Can I run different console games via the Stock UI with RetroArch in 1.1?

A. No – this is planned for future release. You can set an option to launch PS1 games via RA PCSX via the stock UI

Q. Can I use PBP with the stock PCSX emulator and not just the RA PCSX?

A. Yes – As shown here

Q. Why am I getting a “Not all binary files were selected, or they are misnamed.” error?

A. The filename in the cue file must match the spelling and case of the bin file exactly. filename.BIN must be spelled exactly that way in the cue.

Q. I connected my PSC to my computer and it turns on, but I don’t even hear the “device connected” sound, and nothing new shows up in Device Manager.

A. You might be using a power-only USB cable. Try a different cable.

Q. I changed the boot routine so it no longer boots to the boot menu. How can I now access the BleemSync UI?

A. Connect the PSC to the PC without the HDMI plugged in and it will boot to the bleemsync UI

Q. Can I drag games in like I did before and it work?

A. YES – Please refer to the new drag’n’drop method documented above

Q. Can I change the art work?

A. Yes, drag and drop the image of your choice in the cover square.

Q. Power button is not working in RA.

A. It wasn’t working properly, so that functionality has been pulled out for now.

Q. Dual Shock is not working.

A. It does in RA, it doesn’t in Bleemsync

Q: How do I add multidisc games to BleemSync?

A: For games in bin/cue: Make sure all of the files are in the same folder. Select all of the bin and cue files. The amount of discs you have must match the original game or it will confuse the scraper. Ex: Lunar Silver Star Story Complete has 2 game discs and a 3rd documentary disc. You must still have the 3rd disc for the scraper to recognize it.

For games in pbp format: simply select the game.

Q. How do I add a multiple discs game in PBP?

A. Just make a PBP per each disc. Then, add them all at once from Bleemsync web browser UI

Q. Connecting a USB to the front port leaves me with only one free port. Can I connect a USB HUB so I can play multiplayer games?

A. Yes

Q. Where can I get the RNDIS driver for windows or mac. It won’t detect?

A. Windows: RNDIS DRIVER Mac: RNDIS DRIVER

Q. Where are the license and legal stuff?

A. Here: https://modmyclassic.com/license-agreements/ (If you think something is missing please let us know and we can add it in)

Q. What are the SSH login details?

A. HOST: 169.254.215.100 USERNAME: root PASSWORD: Not Required PORT: 22

Q. What are the FTP login details?

A. HOST: 169.254.215.100 USERNAME: root PASSWORD: Not Required PORT: 21