I need help, my PS3 keeps going onto its favourite black screen and saying the following: 'No applicable update data was found. Connect storage media that contains update data of version. 4.11 or later, and then press the START and SELECT buttons. At the same time.' When I press START and SELECT like it says, it checks for a while and comes back to this.
The error 'The Sources files could not be found files' in DISM tool, is commonly caused because of the following reasons: Reason 1. DISM tool cannot find online (in Windows Update or WSUS) the files needed to perform the repair, when using this command: 'DISM /Online /Cleanup-Image /RestoreHealth' Reason 2. You have specified a wrong Windows Image (install.wim) file as the repair source, when using this command: 'DISM /Online /Cleanup-Image /RestoreHealth /Source ' Reason 3. The install.wim or the install.esd file, that you 're using as a repair source, contains multiple install.wim files. (DISM /Online /Cleanup-Image /RestoreHealth /Source) Related articles:. In this troubleshooting guide you will find several methods to resolve the following DISM errors: 'The Source Files Could not be Found', '0x800f081f', '0x800f0906', '0x800f0907'. How to FIX: DISM /RestoreHealth Could not Find Source Files to Repair Windows 10 or Windows 8/8.1.
Clean and Analyze the WinSXS folder. The Windows Component Store folder, aka WinSXS (C: Windows winsxs), contains all the files needed during servicing operations in Windows, such as the installation of updates, hotfixes, etc. Additionally, the WinSXS folder, contains all the files needed for a Windows installation or repair. In time, the size of WinSXS folder becomes large or corrupted, because of updates and new features that are added to the installation, so it needs cleaning before running the DISM tool. To do that: 1. Right click at Start menu and select Command Prompt (Admin).
Type the following commands in order:. DISM /Online /Cleanup-Image /StartComponentCleanup. SFC /SCANNOW.
DISM /Online /Cleanup-Image /AnalyzeComponentStore. SFC /SCANNOW 3. Restart your computer. After the restart, open command prompt (as admin) again and run DISM. DISM /Online /Cleanup-Image /RestoreHealth Method 2. Specify an alternative Repair Source in DISM by using the /Source switch. By default DISM looks online to find the required files to repair the Windows Image.
But in most cases, this doesn't work, so you need to specify a local source for the known good files by using the /Source switch. Requirements: To accomplish this task you need the install.wim file (X: sources.install.wim), from a Windows installation media (USB, DVD or ISO), that has the same Windows version, edition and language with the installed version. If you don't own a Windows installation media (USB, DVD or ISO), then you can obtain one, by using these options:. Option A. Download Windows by using the, or. Option B. Download Windows in a ISO file by using the tool, by following the instructions on this article: Important Notes.
If you have used the Media creation tool (option A), to download Windows 10, then you may need to extract the according to your Windows version install.wim file, from the install.esd file (X: sources install.esd), by using these instructions: 2. If you have used the Windows ISO Downloader tool (option B), to download Windows 10/8 ISO, then you may need to extract a Windows Image (according to the installed Windows version) from the install.wim file (X: sources install.esd) file, by using these instructions: To specify an alternative Repair Source in DISM. Attach the Windows installation media on your system.
Right click at Start menu and select Command Prompt (Admin). Type the following command and press Enter:. DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM: X: sources install.wim:1 /LimitAccess.
Note: Replace the ' X' drive letter according to your case. For example, if the Windows installation media is at drive 'D', then the command will be:. DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM: D: sources install.wim:1 /LimitAccess 6.
Be patient until DISM repairs the Windows image component store. When the operation is completed, you should be informed that the 'operation is completed successfully'.
Note: If the DISM tool fails again with 'Error 0x800f081f: The Sources files could not be found', then read this before proceeding to the rest methods. The problem has – probably – occurred because the install.wim file, contains multiple install.wim files. Finally, to complete the repairs run the sfc /scannow command:.
SFC /SCANNOW 9. When the SFC scan is completed successfully, you 're done! Specify an alternative Repair Source by using Policies or Registry. Attach the Windows installation media on your system. Copy the install.wim file from the Windows installation media (e.g. (X: sources.install.wim) to the C: drive (root folder).
According to your Windows version (Pro or Home), follow the instructions below to specify the C: install.wim file, as the default source to repair the Windows Image. Windows 10 Pro & Windows 8/8.1 Pro – Specify DISM /Source in Local Group Policy Editor: 1. Press Windows + R keys on your keyboard to load the Run dialog box. Type gpedit.msc and press Enter to open the Local Group Policy Editor. In Group Policy Editor navigate (from the left side) to. Computer Configuration Administrative Templates System 4. At the right pane open the ' Specify settings for optional component installation and component repair' setting.
Apply the following settings: 1. Check Enabled 2. At ' Alternate source file path' type: wim:C: install.wim:1 3. Check Never attempt to download payload from Windows Update 6. Click OK and close Policy Editor.
Restart your computer. After the restart, run the 'DISM /Online /Cleanup-Image /RestoreHealth' command again. When the repair is completed, then undo the changes in Policies. Windows 10 Home & Windows 8/8.1 Home – Specify DISM /Source in Windows Registry: 1.
Press “ Windows” + “ R” keys to load the Run dialog box. Type regedit and press Enter to open the Windows Registry Editor. At the left pane, navigate to this key:. HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion Policies 4. Right click at Policies key and select New Key 5. Give at the new key the name: Servicing 6.
Highlight the Serving key. Right click at the right pane and choose New Expandable String Value 8. Give at the new value the name: LocalSourcePath. Double click at 'LocalSourcePath' and at the value data box, type: wim:C: install.wim:1 10. Right click again at the right pane, and choose New DWORD (32-bit) Value. Give at the new value the name: UseWindowsUpdate 13. Double click at 'UseWindowsUpdate' and at the value data box, type: 2 14.
Click OK. 2 = Do Not use Windows Update 15. Close registry editor and restart your computer. After the restart, run the 'DISM /Online /Cleanup-Image /RestoreHealth' command again. When the repair is completed, then undo the changes in Windows Registry. Fix DISM Source Files Cannot be Found Error with Windows Repair Upgrade.
The other method to fix DISM errors is to perform a repair upgrade of Windows 10. Repair/Upgrade Windows 10 by using the Media Creation Tool. Download and run the media creation tool according to your OS Version. Accept the License Terms. Choose the option Upgrade this PC now and press Next. Wait until Windows is upgraded. Use DISM and SFC tools to complete repairs.
– After Windows upgrade: 1. Right click at Start menu and select Command Prompt (Admin). At the command prompt window give the following command in order to complete the repairs:. DISM /Online /Cleanup-Image /StartComponentCleanup. Dism /Online /Cleanup-Image /RestoreHealth.
sfc /scannow Method 5. Fix DISM errors by examine the CBS.LOG file. (UPDATED on 17/5/2017) After it's execution, DISM creates a log file named 'CMS.log' at 'C: Windows Log CBS' directory (e.g.
C: Windows Log CBS CBS.log), that captures any issues found, when DISM command tool is executed. So, the last method to fix DISM's 'Source Files Cannot be Found' error, is to examine the CBS.LOG file, in order to find out and remove the installed package(s) that causes the problem.
Examine DISM's log file (CBS.LOG). Navigate to C: Windows Log CBS directory and open the CBS file. Using the Find tool (View Find), search for 'Checking System Update Readiness'.
Now look under the 'Checking System Update Readiness' line, to find out the corrupted package(s). e.g As you can see at the below screenshot, the corrupted package is named: ' Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0' 4. Once, you find out, the name of the corrupted package, then continue to the next step. Remove the corrupted package's registry entry. Simultaneously press the Windows + R keys to open the RUN command box. Type regedit and press Enter to open the Windows Registry Editor.
IMPORTANT:Before you continue to modify the registry, first take a backup. To perform a registry backup: a. From the main menu, go to File & select Export. Specify a destination location (e.g. Your Desktop), give a filename (e.g.
“ RegistryBackup”) and press Save. From the left pane navigate and select this key:. HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion Component Based Servicing 5. With the Component Based Servicing key highlighted, go to Edit Find (from the menu) and search for the corrupted package name in the registry. To do that, just copy and paste in the search box, the name of the corrupted package from the CBS.LOG. ' Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0') 6.
At this occasion, the name of the corrupted package was found at the following two (2) registry locations/keys:. HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion Component Based Servicing PackageIndex Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd640.0.0.0. HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion Component Based Servicing Packages Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0 7. Now, for safety reasons, backup all the registry key(s) you found, by right-clicking on each of them (on the left pane) and choose Export. Note:Save the registry keys on your desktop, in order to easy import them backup if something goes wrong.
(Double click at the exported key(s) and Merge). Then, assign full control permissions, to the all key(s) you found, to Administrators. To do that: 1. Right click on each key and select Permissions.
Highlight Administrators, place a check mark on Full Control checkbox and click OK. Finally, delete all the registry key(s) you found. (Right click on each key and Delete) 10. Close Registry Editor. Move the corrupted packages to other location on disk. Navigate to C: Windows Servicing Packages folder. Now find and move to your desktop, all the packages that their name begins with the name of the damaged package in the CBS.LOG.
At this occasion I found (and moved to my desktop) the following four (4) files, that their name begins with the name of the corrupted package: Microsoft-Windows-TestRoot-and-FlightSigning-Package. Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0. Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0.mum.
Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package31bf3856ad364e35amd6410.0.15063.0. Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package31bf3856ad364e35amd6410.0.15063.0.mum, 3. Restart you computer. Run the 'DISM /Online /Cleanup-Image /RestoreHealth' command again. If DISM is completed without errors, then proceed and delete permanently the exported registry key(s) and the moved packages from your desktop.
Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others. I'm troubleshooting an issue with my GPU mining rig running the trial version of Windows 10. Suddenly, multiple different mining applications didn't recognize any of my AMD graphics cards, but they were shown in Device Manager.
I noticed that I was getting the notification 'Application has been blocked from accessing graphics hardware', which brought me here. DISM couldn't find the source files (error 0x800f081f) and also wouldn't recognize the install.wim file from the freshly downloaded ISO. Ultimately, Method 4 worked and a repair was successful. Thank you very much for taking the time to create such a thorough guide!.
Margit Dec 05, 2018 @ 16:25:35. Even though the descriptions of the different methods are very clear, I wasn't able to solve the problem yet. I feel like I'm going in circles from one method to another now without making any progress. So If anyone could give me any hints based on the log file below I would be very grateful. Checking System Update Readiness.
2018-11-04 14:33:51, Info CBS 2018-11-04 14:33:51, Info CBS (p) CSI Manifest Corrupt (n) amd64b6eb56d3a1ffc6dbde7f8d8eb688a28631bf3856ad364e3510.0.17134.165none90c9a1eb6668c11c 2018-11-04 14:33:51, Info CBS Repair failed: Missing replacement manifest. 2018-11-04 14:33:51, Info CBS (p) CSI Manifest Corrupt (n) amd64f4ebfb19ca40545b5b70cb6de1d79fb031bf3856ad364e3510.0.17134.165none5a9f0441ba4fe9a6 2018-11-04 14:33:51, Info CBS Repair failed: Missing replacement manifest.
2018-11-04 14:33:51, Info CBS 2018-11-04 14:33:51, Info CBS Summary: 2018-11-04 14:33:51, Info CBS Operation: Detect and Repair 2018-11-04 14:33:51, Info CBS Operation result: 0x800f0907 2018-11-04 14:33:51, Info CBS Last Successful Step: Entire operation completes. 2018-11-04 14:33:51, Info CBS Total Detected Corruption: 2 2018-11-04 14:33:51, Info CBS CBS Manifest Corruption: 0 2018-11-04 14:33:51, Info CBS CBS Metadata Corruption: 0 2018-11-04 14:33:51, Info CBS CSI Manifest Corruption: 2 2018-11-04 14:33:51, Info CBS CSI Metadata Corruption: 0 2018-11-04 14:33:51, Info CBS CSI Payload Corruption: 0 2018-11-04 14:33:51, Info CBS Total Repaired Corruption: 0. I'm using windows Home version. Rodrigo Sep 21, 2018 @ 10:14:29. Hi I cant find those files in regedit, I cant repair it please help. Checking System Update Readiness. (p) CSI Manifest Corrupt amd640e9075b73b1af304ca71bb474bade76e31bf3856ad364e3510.0.16299.371none402e1fbfb487c610 Repair failed: Missing replacement manifest.
(p) CSI Manifest Corrupt amd64302f1d1561cd10a9c6c95131bf3856ad364e3510.0.16299.371none45635903fb6c44b9 Repair failed: Missing replacement manifest. Summary: Operation: Detect and Repair Operation result: 0x800f081f Last Successful Step: Entire operation completes. Total Detected Corruption: 2 CBS Manifest Corruption: 0 CBS Metadata Corruption: 0 CSI Manifest Corruption: 2 CSI Metadata Corruption: 0 CSI Payload Corruption: 0 Total Repaired Corruption: 0 CBS Manifest Repaired: 0 CSI Manifest Repaired: 0 CSI Payload Repaired: 0 CSI Store Metadata refreshed: True Total Operation Time: 1390 seconds. lakonst May 15, 2018 @ 14:03:33. Thanks, I tried all the steps. But it is still same CMD C: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:c: install.wim:1 /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.431 89.1% Error: 0x800f081f The source files could not be found. Use the 'Source' option to specify the location of the files that are required to restore the feature.
For more information on specifying a source location, see. Checking System Update Readiness. (p) CSI Manifest Corrupt amd640e9075b73b1af304ca71bb474bade76e31bf3856ad364e3510.0.16299.371none402e1fbfb487c610 Repair failed: Missing replacement manifest. (p) CSI Manifest Corrupt amd64302f1d1561cd10a9c6c95131bf3856ad364e3510.0.16299.371none45635903fb6c44b9 Repair failed: Missing replacement manifest. lakonst May 15, 2018 @ 16:35:37. My Windows 10 Home 64-bit system suddenly started acting weird. I ran an sfc /scannow and noted 4 corruptions: fdeploy.dll, fde.dll, gptext.dll, and gpedit.dll.
Followed your Method 1 and seem to have resolved the problem but am curious about the last sfc /scannow CBS.log – it showed 'source file in store is also corrupted' for all four corruptions, but then showed 'All files and registry keys listed in this transaction have been successfully repaired' Never even got to the DISM /Online /Cleanup-Image /RestoreHealth step. Is that even possible? Could sfc/scannow have cleaned things up without the RestoreHealth, given the stated corruptions? Or is this just one of the Microsoft mysteries?. lakonst Sep 08, 2017 @ 13:11:20. With minor differences, I tried the solution at posted by DAC324 and it worked perfectly: DISM /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 100.0% The restore operation completed successfully. The operation completed successfully.
Sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. Before I get into the details of what I did, I have a suggestion for this webpage: I would add a 'last resort' Method 5 that describes running DISM /Online /Cleanup-Image /ScanHealth and then examining the bottom of the C: Windows Logs CBS CBS.log file to see exactly what the problem(s) is(are). Then search the Internet for possible solutions.
In this case, it appears that someone at Microsoft left a 'testroot' in the packages of the production version of Windows 10 when it shouldn't have been there. Here is what I did: 1.
I found two instances of 'testroot' packages in the registry at HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion Component Based Servicing PackageIndex of my Windows 10 Home 64-bit version 1703 build 15063.296. They were: Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0 Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package31bf3856ad364e35amd6410.0.15063.0 2. I exported each of these two registry entries to my desktop for safe keeping, just in case I needed them later. Then I changed the permissions on the two registry entries giving myself full control. Then I deleted both registry entries.
Then I searched my C: drive (using the Everything program) for 'testroot' files. There were 4, all located in the C: Windows Servicing Packages folder: Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0.mum Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0.cat Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package31bf3856ad364e35amd6410.0.15063.0.mum Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package31bf3856ad364e35amd6410.0.15063.0.cat 6. I MOVED all 4 to my Desktop for safe keeping, just in case I needed them later. The I rebooted. The reboot went perfectly and, as you saw above, 'DISM /Online /Cleanup-Image /ScanHealth' and 'SFC /Scannow' both work perfectly. Stu. lakonst May 12, 2017 @ 12:20:27.
Continuing from my mistakenly placed comments at the bottom of: I followed your instructions which were: Windows 10 has many bugs. Anyway try the following: 1. In a elevated command prompt give the following commands in order: DISM /Online /Cleanup-Image /StartComponentCleanup SFC /SCANNOW DISM /Online /Cleanup-Image /AnalyzeComponentStore SFC /SCANNOW 2. After SFC Restart your computer. After Restart, open command prompt (as admin) again and try again DISM /Online /Cleanup-Image /RestoreHealth Step 1: DISM /Online /Cleanup-Image /StartComponentCleanup completed successfully with no comments about fixing anything. SFC /SCANNOW just said 'Verification 100% complete. Windows Resource Protection did not find any integrity violations.'
DISM /Online /Cleanup-Image /AnalyzeComponentStore said: Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store: 4.11 GB Actual Size of Component Store: 4.01 GB Shared with Windows: 3.41 GB Backups and Disabled Features: 451.65 MB Cache and Temporary Data: 145.43 MB Date of Last Cleanup: 2017-05-10 08:03:33 Number of Reclaimable Packages: 0 Component Store Cleanup Recommended: No The operation completed successfully. SFC /SCANNOW just said 'Verification 100% complete.
Windows Resource Protection did not find any integrity violations.' Step 2: The computer restarted normally.
Step 3: DISM /Online /Cleanup-Image /RestoreHealth result was: 98.2% Error: 0x800f081f The source files could not be found. Use the 'Source' option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see. The DISM log file can be found at C: WINDOWS Logs DISM dism.log What could it possibly be?. lakonst May 11, 2017 @ 09:48:44. Yes, I've tried all 4 methods and get the same problem.
What makes me think I do NOT have to reinstall Windows 10 is that when I run DISM /Online /Cleanup-Image /CheckHealth I get Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 The component store is repairable. The operation completed successfully. It says 'The component store is repairable' which means to me that there must be a way to repair it short of doing a complete reinstall from scratch. When I run DISM /Online /Cleanup-Image /ScanHealth the C: Windows Logs CBS CBS.log says 2017-05-11 08:07:01, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked. 2017-05-11 08:07:01, Info CBS Repr: CSI Store check completes 2017-05-11 08:07:01, Info CBS Ensure WCP corruption flag is clear 2017-05-11 08:07:01, Info CBS All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear 2017-05-11 08:07:01, Info CBS Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). HRESULT = 0x80070002 – ERRORFILENOTFOUND 2017-05-11 08:07:01, Info CBS Checking System Update Readiness. (p) CBS MUM Corrupt Microsoft-Windows-TestRoot-and-FlightSigning-Package31bf3856ad364e35amd6410.0.15063.0 Summary: Operation: Detect only Operation result: 0x0 Last Successful Step: CSI store detection completes.
Total Detected Corruption: 1 CBS Manifest Corruption: 1 CBS Metadata Corruption: 0 CSI Manifest Corruption: 0 CSI Metadata Corruption: 0 CSI Payload Corruption: 0 Total Repaired Corruption: 0 CBS Manifest Repaired: 0 CSI Manifest Repaired: 0 CSI Payload Repaired: 0 CSI Store Metadata refreshed: True I believe I found the solution here: Look for the posting by DAC324. What do you think? Should I try it?
Stu. lakonst May 11, 2017 @ 15:25:09.
The Great PS3Xploit V3.0 HAN AIO Guide Or How I combed the forums for all the correct information DISCLAIMER I am not responsible for your mistakes. This guide was put together through my own expiriences and any problems that may arise with your expiriences are not my problem. Anything is possible when making your console do things it wasn't made to do and if you brick your console because you missed a step, deviated from the instructions or just went gung-ho on your console then that's your fault. By following my guide you accept the risks involved with modifying system software. There has been one case of a bricked console. This was a 3k model ps3 where the owner had removed the WiFi chip because of a fault. Although this has been an isolated incident, you have to remember we are modifying the software on our consoles.
PIRACY DISCLAIMER I do not condone piracy. I love a free game more than most but I will not steal it. All of my examples and methods below were tested using games that I personally own. DO NOT DISCUSS PIRACY IN THIS THREAD OR THIS FORUM!
DO NOT ASK ME FOR DOWNLOAD LINKS! DO NOT ASK ME HOW TO MAKE A RAP FILE! Credits Huge thank you to the PS3Xploit team for their work: W, esc0rtd3w, bguerville and Habib.
Hello to all and welcome to my All In One guide for PS3Xploit V3.0 HAN. This guide was created out of information gathered from these forums in an attempt to consolidate and streamline the process for the noobs. A little background: I'm a simple guy with a thirst for analytics and problem solving. I've pretty much hacked every console imaginable with the PS3 being one that escaped my grasp (My PS3s have always been late models, no flasher for me). I've been following PS3Xploits progress since December 2017 and when the news dropped that 3k and 4k models had been exploited, I was incredibly excited to start work on modifying my PS3 Now, as you can imagine, finding information just after the release was impossible.
So it's taken a long time for information and guides to be released and a noob would find it hard (or even be bothered) to search the forums for their answers. That's where this guide comes in!. IF THIS IS THE FIRST TIME YOU HAVE FOLLOWED THIS GUIDE. Please read this guide front to back, side to side and top to bottom before you even turn your PS3 on. There is a huge amount of information contained herein and if its your first time reading about PS3Xploit, HAN, PKGs, RAPs and RIFs then it might seem a bit daunting to start with.
My guide was designed with the noob in mind but it's still not for the faint hearted. We will be using alot of tools on our PC to get most of this working. FOLLOW EACH AND EVERY STEP IN THE ORDER THEY COME IN. DON'T MISS A STEP THERE MAYBE SOMETHING IMPORTANT MISSED. Basic Windows understanding is prefered but not entirely needed. Introduction - Why you should have 2 accounts For reasons of keeping you Main Account clean and reduce your risk of a ban (THERE IS NO WAY TO STAY 100% SAFE), you MUST create a second user and PSN account for use with some HAN exploit tools.
So, when you boot your PS3 and scroll all the way to the left in XMB, you will have TWO user accounts. One user will be your MAIN account with your main PSN login, on this account you can: Enable HAN Install signed PKGs (CONTENT ONLY. NO RIF PKGs) Run all your backup content Run all your legitimate content GO ONLINE The other will be your SECONDARY account with your secondary PSN login, on this account you can: Enable HAN Install/Update HAN Dump act.dat and idps.hex Copy act.dat and idps.hex Install signed PKGs (BOTH CONTENT AND RIF PKGs) Now, make sure you read that correctly, take a deep breath and lets jump straight into Part 1. Create Throw-Away Account and Activate PS3 As previously mentioned, it is recommended to create a throw-away Playstation Network account and new user for the exploit. Create a new User for your PS3. Login to your throw-away PSN account on your new user account. Navigate the XMB to 'Playstation Network/Account Management/Activate' and activate your console.
Logout of secondary PSN account. Reboot/Shutdown. FROM NOW ON, ANY HAN ACTIVITY MUST BE EXECUTED FROM YOUR SECONDARY USER ACCOUNT. You can still use your main user account to do anything non HAN related. READ DISCLAIMER then MOVE ONTO SECTION B.
Install HAN And now for the MAGIC! .
Boot console. CHECK YOU ARE ON YOUR SECONDARY USER Account. Open Browser.
Navigate to. Navigate menu at top of webpage and select 'HAN Installer'. Once webpage has loaded, scroll down and select 'Initialise HAN Installer'. Wait for 'HAN Installer initialised successfully' in green letters. If it fails to initialise then close browser and restart Section C. Click 'Launch HAN Installation'. HAN Installer will do its thing and then reboot.
HAN is now installed on your PS3. MOVE ONTO SECTION D. .
Download 'hansupportfiles.zip'. Extract the contents of the zip file to the root of your USB drive.
Insert USB drive into right most USB slot. Boot console. CHECK YOU ARE ON YOUR SECONDARY ACCOUNT. Navigate to. Navigate menu at top of webpage and select 'HAN Installer'.
Once webpage has loaded, scroll down and select 'Initialise HAN Installer'. Wait for 'HAN Installer initialised successfully' in green letters. If it fails to initialise then close browser and restart Section G. Click 'Launch HAN Installation'. HAN Installer will do its thing and then reboot. HAN is now updated on your PS3.
Part 2 - Dump ACT.DAT and IDPS.HEX In this part we will be dumping our act.dat and idps.hex files needed to resign our PKGs. WHEN DUMPING LICENCE, MAKE SURE YOUR LOGGED INTO YOUR SECONDARY USER ACCOUNT. Make sure your have a USB disk inserted into the rightmost usb port on PS3. Boot console.
Navigate to Navigate the menu and select 'ACT/IDPS Dumper'. Select 'Initialise ACT/IDPS Dumper and wait for the green letters. If failed, repeat. If successful, select 'DUMP ACT.DAT and IDPS' Your Licence has now been dumped to USB.
Boot Console. ENABLE HAN. Navigate to Package Manager/Install Package Files/Standard. Install HAN Toolbox. Reboot Console.
For the Demo Downloader feature to work correctly, a couple more steps are needed:. Boot Console. ENABLE HAN. Navigate the XMB to HAN Toolbox/Toolbox Settings/Setup Update Demo List. Select 'Step 1', and tap X and select YES.
Let download and installation finish. Navigate the XMB to. Toolbox/Toolbox Settings/Setup Update Demo List. Select 'Step 2'. Slect the drop down menu 'Select Source RCO File'. Scroll down the list and select 'explorepluginfull.rco'. Select the dropdown menu 'Root Path'.
Select '/dev/game/HANTOOLBX/USRDIR/files/'. Select 'Initialize Flash RCO Replacer'. What for the green letters '.initialized successfully'. Select 'Copy RCO File To Flash'. Allow console to fully reboot. So, now that HAN toolbox is installed we can do a lot of extra stuff. HAN Toolbox can now be used in place of the web browser.
There are shortcuts to all the tools that HAN brings. Enabler, Copier, Dumper. As well as Soft Reboot, Hard Reboot and Shutdown. The Demo Downloader is a handy feature for. Yes, you guessed it. Downloading demos.
This bypasses the need to access the PSN Store. You can install all your content over a network from your PC.
HAN Toolbox has some extra features when used with PKG Linker (More info in Part 6). A File Explorer which can be used to browse the complete file system. Don't delete something that you don't understand. You could brick.
Tools to Install I like to create a working folder on the root of one of my hard drives named 'WORK' so it is easier to navigate the tools during the conversion process. Some tools will give errors if filenames contain spaces. So if you try to create a game from: 'C:/WORK/Playstation 1/PSX Game 1.ISO' It will fail because A. There is a space in 'Playstation 1' and B. There are a few spaces in 'PSX Game 1.ISO' The correct file path would be: 'C:/WORK/Playstation1/PSXGame1.ISO'.
Extract PKG Resigner to WORK folder. Copy your ACT.DAT and IDPS.HEX to ' WORK PS3xploit-resigner-master rifgen-master' folder.
Extract PSX Classics Tools to WORK folder. Create new folder 'TrueAncestor' in WORK and unzip TrueAncestorRepacker into this folder. PS3Tools.exe may trigger your antivirus.
If this happens, make an exception in your antivirus software or disable your antivirus while using the tools. Install PS3Tools to your WORK folder. You may have some trouble opening 'PS3ToolsMenu.exe'. A message may appear saying 'MSVBVM50.DLL' was not found. If you get this message, download and install to fix this error. Thus concludes tool setup!
And know for the good stuff. Prerequisites For PSX conversion you will need a few images for the 'look and feel' of your game within the XMB menu. There are 3 images in total but i only use 2. ICON0.PNG - This is the icon of the game when highlighted in XMB PIC1.PNG - This is the background image when highlighted in XMB PIC0.PNG - This is the information box located in the bottom right of the screen when highlighted in XMB You can download a set of blank templates from. Edit as you wish.
I usually use Photoshop or GIMP2 to import the game cover art onto the ICON0 template and export. I then search google images for a relevant image for the background, usually of ingame play. Any PNG can be used but filename must match the ones above and ICON must be 320x176 and background image 1920x1080. Converting PSX ISO I will be using GTA 2 as an example to run you through the conversion process. Rip/acquire your PSX to ISO. Navigate to ' WORK psxclassics PSX2PSP 1.4' and select 'Clasic mode'. Click 'Options' and move 'Compression' Slider to 0.
Save and close. Reopen 'Clasic Mode'. Select your ISO file. For multi disk games, click the dropdown menu to add more disks. Name your files and directory's so they contain NO spaces. Fill in the 'Output PBP Folder' box (for ease, i set this to ' WORK psxclassics').
Check 'Game Title' is correct ( Grand Theft Auto 2). Write down the games 'GameID' ( SLES01404).
Click 'Convert'. Navigate to ' WORK psxclassics' and find the newly created folder of your game ( Grand Theft Auto 2).
Copy/Move the 'EBOOT.PBP' from this folder into ' WORK psxclassics' folder. Drag 'EBOOT.PBP' onto 'makepsoneclassicmetadata.exe' to make a ISO.BIN.DAT file. Copy this and past it into notepad: ' makenpdata -e ISO.BIN.DAT ISO.BIN.EDAT 1 1 1 0 16 3 00 UP9000- TITLEID000000001 5'. Edit this command so it contains your 'GameID' where 'TITLEID' is.
So in my GTA 2 example: ' makenpdata -e ISO.BIN.DAT ISO.BIN.EDAT 1 1 1 0 16 3 00 UP9000- SLES01401 5'. Hold shift and right click an empty part of the 'psxclassics' folder and select 'Open command window here'. If you don't have 'Open command window here', follow guide to add it to windows. Copy and Paste your edited command into the command window and hit Enter. Installing Onto PS3 .
Boot PS3. ENABLE HAN!.
Navigate XMB to 'Game/Package Manager/Install Package Files/Standard'. Select your PKG and it will start the process of copying the PKG. Please be patient, the 'Please Wait' screen will take some time.
KEEP WAITING!! I know you think it hasn't worked but it is working. Once the 'Please Wait' has gone, navigate the XMB to 'Game/Package Manager/Playstation Network Content'. Here you will find the install for your PKG. Wait for install process to finish. PS2 ISO Conversion UPDATE: has updated his Ps2classicgui application to now include configuration files. This will increase compatibility with certain ps2 titles.
You can find his updated tool. It includes a large amount of config files for many games. Very busy lately so I will update the following section as soon as I can. In the mean time I think it's pretty easy to do.. Rip/Acquire PS2 to ISO.
Open 'PS3ToolsMenu.exe' located in ' WORK ps3tools ' folder. Select 'Conversion Tools'. Select 'PS2Classics GUI'.
Click the folder icon and select your ISO. Click 'Encrypt'.
If you get an error its more than likely you didn't read the part where i said DON'T USE SPACES in filenames and folders. Read Part 2, prerequisites and tool installation. Once encrypted you will be asked to save an 'ISO.BIN.ENC.BIN.ENC' file, save anywhere. Locate this file and rename it to 'ISO.BIN.ENC'.
Go back to 'PS2Classics GUI' window and click the 'Make PKG' tab. Right click on ICON, Background and Game title to change any of these to your liking. Click 'Make PKG'. It will open the location you saved your 'ISO.BIN.ENC', select it. Let the tool work some magic. Once complete, your game PKG will be in the same folder as your 'ISO.BIN.ENC'.
Copy this PKG to ' WORK PS3xploit-resigner-master rifgen-master' folder. Drag PKG onto 'ps3xploitrifgenedatresign.exe'. Copy resulting signed PKG to USB root. MOVE ONTO SECTION B. PSP ISO Conversion .
Rip/Acquire your PSP to ISO. Open 'PS3ToolsMenu.exe' located in ' WORK ps3tools ' folder. Select 'Conversion Tools'.
Select 'PSP2PS3 GUI'. Click the '.' Button next to file dialogue box and select your ISO (Remember NO spaces in filenames and folders).
The tool will automatically use the ICON, PIC1 and Game title from within the ISO. Click 'Options'. Make sure that 'PSP Remaster' is selected. Click Convert. Let PSP2PS3 GUI do its thing. When prompted, click 'Make PKG'. Let PSP2PS£ do more of its thing.
When complete, the tool will open a folder containing the result. Copy/Move the pkg into ' WORK PS3xploit-resigner-master rifgen-master' folder. Drag PKG onto 'ps3xploitrifgenedatresign.exe'. Copy resulting PKG to USB root.
MOVE ONTO SECTION B. Installing onto PS3 . Boot PS3.
ENABLE HAN!. Navigate XMB to 'Game/Package Manager/Install Package Files/Standard'. Select your PKG and it will start the process of copying the PKG. Please be patient, the 'Please Wait' screen will take some time. KEEP WAITING!! I know you think it hasn't worked but it is working.
Once the 'Please Wait' has gone, navigate the XMB to 'Game/Package Manager/Playstation Network Content'. Here you will find the install for your PKG. Wait for install process to finish. Thus concludes the simplest part of the guide.
Now, here's the thing with PSP. I've yet to find a game that actually works. Compatibility isnt very good.
So far I've tested Gitarooman Lives, GTA: Liberty City Stories and MGS: Portable Ops+ The first 2 boot to black screen and MGS boots to menu. I can navigate menu but get a black screen when starting the game Report back if you have gotten any games to work. UPDATE: is a small compatibility list. Tested more games and report you findings to the thread Moving onto an equally similar section. PSP Minis ISO Conversion . Rip/Acquire your PSP Mini to ISO. Open 'PS3ToolsMenu.exe' located in ' WORK ps3tools ' folder.
Select 'Conversion Tools'. Select 'PSP2PS3 GUI'. Click the '.' Button next to file dialogue box and select your ISO (Remember NO spaces in filenames and folders). The tool will automatically use the ICON, PIC1 and Game title from within the ISO. Click 'Options'. Make sure that 'PSP Mini' is selected.
Click Convert. You will be prompted to sign the eboot. SELECT NO. Let PSP2PS3 GUI do its thing. When prompted, click 'Make PKG'. Let PSP2PS3 do more of its thing. When complete, the tool will open a folder containing the result.
Copy/Move the pkg into ' WORK PS3xploit-resigner-master rifgen-master' folder. Drag PKG onto 'ps3xploitrifgenedatresign.exe'.
Copy resulting PKG to USB root. MOVE ONTO SECTION B. Boot PS3.
ENABLE HAN!. Navigate XMB to 'Game/Package Manager/Install Package Files/Standard'. Select your PKG and it will start the process of copying the PKG. Please be patient, the 'Please Wait' screen will take some time. KEEP WAITING!! I know you think it hasn't worked but it is working.
Once the 'Please Wait' has gone, navigate the XMB to 'Game/Package Manager/Playstation Network Content'. Here you will find the install for your PKG.
Wait for install process to finish. Thus concludes another simple conversion process. So far I have only managed to boot one game but that's only because it was the only game i had ripped from my PSP before it died. So I assume others will work.
Prerequisites Check your bluray game compatibility there may be an exclusive method to make. Your game work. You will need a couple of tools for this one. CFW2OFW Helper - A handy tool that will take you game data, download the relevant update and create 2 folders for the next tool.
Download - Make Backup PKG - This tool will take these 2 folders and create a game PKG and an Update PKG. Download Following the norms of my guide, create folders if needed in our WORK folder for these tools and and extract them. Downloading Update and Converting to PKG .
Copy/Move the contents of your ISO to ' WORK CFW2OFW Helper' folder. Run 'CFW2OFW Helper.exe'.
CFW2OFW Helper will start to download the relevant update for your game. It will create a folder with your Games title.
Inside this folder are another 2 folders. These may be different if your game region is different to my example. Copy/Move these 2 folders into ' WORK make-backup-pkg' folder. Run 'do.bat'.
Leave the command window to do its thing. When complete, you will have 3 PKGs that start with '000000-NPUB.' (filenames may vary). Copy these 3 PKGs to ' WORK PS3xploit-resigner-master rifgen-master' folder. Sign each one by dragging each one onto 'ps3xploitrifgenedatresign.exe'. Copy the resulting signed PKGs to USB root.
MOVE ONTO SECTION C. DLC There are 2 types of DLC, one will just need resigning. The other will need its RAP/RIF counterpart.
Acquire your DLC, it must match the same region as your main game PKG we installed earlier. (NO PIRACY DISCUSSION). If your DLC needs a RAP, aquire RAP. Copy your DLC pkg into ' WORK PS3xploit-resigner-master rifgen-master' folder. If RAP required, Copy/Move PKG into ' WORK PS3xploit-resigner-master rifgen-master'.
Drag your pkg onto 'ps3xploitrifgenedatresign.exe'. If rap required, start 'resignall.bat.bat' to obtain Rif PKG. Copy resulting signed pkg(s) onto USB. REPEAT SECTION C. Part 5.B - PSN Games This part of the guide will outline games that originated from PSN Store. This includes BluRay titles that have been re-released onto PSN Store!! Great news if an update isnt available for your BluRay disk game!!
Now, this part of the guide is going to be vague as I do not want to run the risk of getting banned or this invaluable piece of text to be removed. . Acquire your Game PKG. (DO NOT DISCUSS PIRACY). Acquire your Game RAP. (DO NOT DISCUSS PIRACY).
Please note that game PKG and RAP are matching pair. Copy/Move PKG into ' WORK PS3xploit-resigner-master rifgen-master'.
Copy/Move RAP into ' WORK PS3xploit-resigner-master rifgen-master raps'. Run 'resignall.bat'. Drag Game PKG onto 'ps3xploitrifgenedatresign.exe'. Copy/Move your signed Game PKG and RIF000 PKG to USB root.
Boot PS3. MAKE SURE YOU ARE ON YOUR SECONDARY USER ACCOUNT.
Enable HAN. Install Game PKG and RIF000 PKG And that concludes this part about PSN Titles. Install c00 Unlock PKG .
Boot PS3. MAKE SURE YOUR ARE USING YOUR SECONDARY USER/ACCOUNT. ENABLE HAN!. Navigate Package Manager and install c00 PKG. Login to PSN. Start PSN Store.
Search for your game. Download the Demo Version. Install the game just like any other PSN content game. Once installed, exit PSN Store. Logout of PSN Account.
You have now completed enabling and downloading c00 games. As an added bonus, here is a full list of titles that c00 Unlock PKG will allow you to download and play. Part 6 - Using a Network to Transfer PKGs larger than 4GB A problem with the FAT32 file system is its 4GB file size limitation. Not a problem with most PS1, PSP and a few PS2 games. But a vast majority of PS3 titles are much larger than 4GB. That's where PKG Linker comes in handy. A quick FYI, I use a VPN.
And when I set about trying to make this work, it would fail to connect EVERY. I was pulling my hair out over what it could be. I stumbled upon a configuration file and realised that the PKG Linker and server were trying to connect to my VPN 'ethernet adapter'. I disabled my VPN and restarted from the beginning and it worked great!!
So, if your like me and you use a VPN, disable it for the rest of the transfer process. Creating Package List PKG and Starting the Server .
Start 'PKG Linker.exe'. Click 'Yes' to export package list. Click 'OK'. Click 'Yes' to using built in server.
Click 'OK'. Now follow the Apache install process leaving all settings default.
Leave 'Run server now?' Box unchecked. Click 'Yes' to signing PKG. Let command do its thing and hit Enter twice to exit. Click 'OK'. Server will now start in a Command Window (Leave this open while you transfer PKGs).
Click 'OK' in server confirmation window (Separate window from command window). Navigate to ' WORK PKGLinker ' folder and copy 'PackageList.pkg' to root of USB. Insert USB into rightmost USB. MOVE ONTO SECTION B.
Transferring PKGs Later On . Copy your new PKGs into the ' WORK PKGLinker ' folder. Start 'PKG Linker.exe' to start server. On PS3, navigate to 'Game/HAN Toolbox/Install Packages form Webserver'. Select 'Resfresh Package List'. Your PS3 will download the new package list and install automatically.
Navigate HAN Toolbox and select 'Soft Reboot'. Your new PKG files will now show in the webserver menu. IF YOUR GET ERROR CODE 80710092, MOVE ONTO TROUBLESHOOTING. If your receive error 80710092 then you are having connection issues. This could be one of many variables.
This is not HAN related. This is your network/router/wifi/pc settings. Please read this post. Windows firewall. Other firewall or AntiVirus.
Cable problem. Port blocked on server. Port conflict on server. Missing dll on system.
Packagelist not updated by usb since server settings changed. Port changed in pkg linker but not changed in server settings. Port changed in server settings and not changed in pkg linker.
PS3 not rebooted since new package list loaded on Important things to try after reading trouble shooting tab in first post of pkg linker thread. Disable firewalls, inc windows firewall, defender etc. Make sure the pkg linker app says your PC IP, it may have picked up wrong IP and need to be typed in manually. See if you can access server via ps3 web browser. update package list via usb everytime you change settings until it works (always reboot ps3 to see changes on XMB).
Try change ports (in app and server). Try run other servers (xampp, miniweb, hfs, node.js). Read the entire pkg linker thread and try other peoples solutions. Google how to set up a web server and try learn about it.
Part 7 - Homebrew Applications and Emulators UNDER CONSTRUCTION In this section we will cover Homebrew applications and emulators. Unfortunately, Ps3Xploit HAN DOES NOT natively support homebrew. But there is a silver lining. When the Ps3Xploit v3 preview/demo was shown a few weeks back, users and showcased the homebrew emulator SNES Station successfully running as a Ps2 Classics backup. The basic idea is that you take your homebrew and roms and repack them into an ISO image then continue as if it was a Ps2 ISO used for converting into a PS2 Classic. Build Your Own Here I will discuss making your own Ps2 Classic containing your chosen homebrew.
Download the prebuilt uLaunchELF ISO image from and unzip to our WORK folder. Download CDGenPS2 from and unpack into its own folder in our WORK folder. Mount 'Emulator V1.ISO' with your favourite ISO software and extract its contents to a folder. Open CDGenPSP. Drag the contents you extracted from 'Emulator v1.iso' into the big white space in CDGenPs2.
Drag any PS2 homebrew you want to test into the 'EMULATORS' folder (it already contains a working Sega and SNES emulator). Drag any ROMs you want to try into the ROMS folder. Click 'File' and select 'Save CD'. Save the 'imagen.bin' image to our WORK folder. Open 'PS3ToolsMenu.exe' located in ' WORK ps3tools ' folder. Select 'Conversion Tools'. Select 'PS2Classics GUI'.
Click the folder icon and select your 'imagen.bin'. Click 'Encrypt'.
If you are asked to add LIMG, select YES. Once encrypted you will be asked to save an 'ISO.BIN.ENC.BIN.ENC' file, save anywhere. Locate this file and rename it to 'ISO.BIN.ENC'. Go back to 'PS2Classics GUI' window and click the 'Make PKG' tab. Right click on ICON, Background and Game title to change any of these to your liking. Click 'Make PKG'.
It will open the location you saved your 'ISO.BIN.ENC', select it. Let the tool work some magic. Once complete, your game PKG will be in the same folder as your 'ISO.BIN.ENC'. Copy this PKG to ' WORK PS3xploit-resigner-master rifgen-master' folder. Drag PKG onto 'ps3xploitrifgenedatresign.exe'. Copy resulting signed PKG to USB root. Boot Ps3, enable HAN, install PKG, boot game.
Once loaded, navigate uLaunchELF to 'cdfs:/EMULATORS/' to find your homebrew. Select your desired Homebrews '.elf' file. Do lots of testing, report back what homebrew is working for you.
SNES Station Here we will unpack the SNES Station ISO, add ROMs and repack the ISO using CDGenPs2.. Download the prebuilt ISO from. Download CDGenPS2 from and unpack into its own folder in our WORK folder. Extract the ISO into our WORK folder. Mount the ISO with your favourite ISO software. Extract the contents of the ISO into a folder in our WORK folder.
Open CDGenPSP. Drag the contents you extracted from your ISO into the big white space in CDGenPs2.
Drag any ROMs you want to try into the ROMS folder. Click 'File' and select 'Save CD'. Save the 'imagen.bin' image to our WORK folder. Open 'PS3ToolsMenu.exe' located in ' WORK ps3tools ' folder. Select 'Conversion Tools'.
Select 'PS2Classics GUI'. Click the folder icon and select your 'imagen.bin'.
Click 'Encrypt'. If you are asked to add LIMG, select YES. Once encrypted you will be asked to save an 'ISO.BIN.ENC.BIN.ENC' file, save anywhere. Locate this file and rename it to 'ISO.BIN.ENC'.
Go back to 'PS2Classics GUI' window and click the 'Make PKG' tab. Right click on ICON, Background and Game title to change any of these to your liking. Click 'Make PKG'. It will open the location you saved your 'ISO.BIN.ENC', select it.
Let the tool work some magic. Once complete, your game PKG will be in the same folder as your 'ISO.BIN.ENC'. Copy this PKG to ' WORK PS3xploit-resigner-master rifgen-master' folder. Drag PKG onto 'ps3xploitrifgenedatresign.exe'. Copy resulting signed PKG to USB root.
Boot Ps3, enable HAN, install PKG, boot game. Navigate the 'CDROM/Roms' directory to find your list of games. If you get messed up graphics, turn 'Interlace' off in SNES Station options. PGEN Pgen is a Sega Mega Drive/Genesis emulator. This zip file was made my user.
Download the Pgen pack from and extract to our WORK folder. Download CDGenPS2 from and unpack into its own folder in our WORK folder. Navigate to ' WORK PGEN ROMs' and place all your ROMs in their repective folders. Open CDGenPS2. Drag the entire contents of 'PGEN' folder into the big empty white space in CDGenPs2. Click 'File' and select 'Create CD'. Save the 'imagen.bin' image to our WORK folder.
Open 'PS3ToolsMenu.exe' located in ' WORK ps3tools ' folder. Select 'Conversion Tools'. Select 'PS2Classics GUI'.
Click the folder icon and select your 'imagen.bin'. Click 'Encrypt'. If you are asked to add LIMG, select YES. Once encrypted you will be asked to save an 'ISO.BIN.ENC.BIN.ENC' file, save anywhere.
Locate this file and rename it to 'ISO.BIN.ENC'. Go back to 'PS2Classics GUI' window and click the 'Make PKG' tab.
Right click on ICON, Background and Game title to change any of these to your liking. Click 'Make PKG'. It will open the location you saved your 'ISO.BIN.ENC', select it.
Let the tool work some magic. Once complete, your game PKG will be in the same folder as your 'ISO.BIN.ENC'.
Copy this PKG to ' WORK PS3xploit-resigner-master rifgen-master' folder. Drag PKG onto 'ps3xploitrifgenedatresign.exe'. Copy resulting signed PKG to USB root. Boot Ps3, enable HAN, install PKG, boot homebrew. MultiEmu ISO User has finished up a nice little taster of whats to come with a MultiEmu pack. This pack can be loaded with ROMs easily and using CDGenPS2, repacked into an ISO image ready for PS2 Classics Gui. The MultiEmu pack contains 2 sega emulators (PGen and PiciDrive), a SNES emulator, a Wondwerswan emulator (Wonderstation) and a DosBox emulator.
There's still some kinks to work out so heard on over to his thread to take a more detailed look. Download the MultiEmu pack from and extract to our WORK folder. Download CDGenPS2 from and unpack into its own folder in our WORK folder. Navigate to ' WORK MultiEmuV1 ROMs' and place all your ROMs in their repective folders. Open CDGenPS2.
Drag the entire contents of 'MutliEmuV1' folder into the big empty white space in CDGenPs2. Click 'File' and select 'Create CD'. Save the 'imagen.bin' image to our WORK folder. Open 'PS3ToolsMenu.exe' located in ' WORK ps3tools ' folder. Select 'Conversion Tools'.
Select 'PS2Classics GUI'. Click the folder icon and select your 'imagen.bin'. Click 'Encrypt'.
If you are asked to add LIMG, select YES. Once encrypted you will be asked to save an 'ISO.BIN.ENC.BIN.ENC' file, save anywhere. Locate this file and rename it to 'ISO.BIN.ENC'. Go back to 'PS2Classics GUI' window and click the 'Make PKG' tab. Right click on ICON, Background and Game title to change any of these to your liking. Click 'Make PKG'.
It will open the location you saved your 'ISO.BIN.ENC', select it. Let the tool work some magic. Once complete, your game PKG will be in the same folder as your 'ISO.BIN.ENC'. Copy this PKG to ' WORK PS3xploit-resigner-master rifgen-master' folder. Drag PKG onto 'ps3xploitrifgenedatresign.exe'. Copy resulting signed PKG to USB root.
Boot Ps3, enable HAN, install PKG, boot game. Once loaded, navigate uLaunchELF to 'cdfs:/EMULATORS/' to find 5 emulators to use. Part 8 - PS3 Game Mods Unfortunately, as I've started work recently and have alot of studio time coming up with my band, I really don't have the time to explain this one. Also, I have a PC if I want to mod games, Buuuuuuuuut, A very talented user by the name of has put together a nice guide to help everyone out.
You can go check the thread out Part 9 - XMB mods So, using various HAN tools, we can change quite a bit when it comes to customisation. These XMB mods have the potential to soft brick your console. This means you will need to reinstall OFW through recovery to revive your console. This will allow you to change the boot logo and sound of your PS3. There are some Ps3Xploit logos and sounds available from.
If you would like to create your own logo/sound then head on over to for a nice tutorial on how to make them. Choose which logo/sound you would like. Extract/Move the 3 files you need: 'coldboot.raf', 'coldbootmulti.ac3' and 'colbootstereo.ac3' onto the root of your USB drive. Insert USB drive into rightmost USB slot on PS3. Navigate the XMB to 'HAN Toolbox/File Injector'. Select 'Inject Coldboots', a browser window will open. Select 'Initialize Cold Boot Installer'.
Wait for green text to confirm succesful. Select 'Launch Cold Boot Installation'. Wait for PS3 to fully reboot. Here we are going to change the waves of the XMB, this can be in the form of different colours, multiple colours and various visual changes to the shape of the waves.
You can download a really nice wave that comes with the official release from. Any valid 'lines.qrc' should work. Extract 'lines.qrc' from the release onto the root of your USB drive. Navigate the XMB to 'HAN Toolbox/File Injector'. Select 'Inject Lines.qrc', a browser window will open. Select 'Initialize XMB Wave Installer'. Wait for the green text to confirm successful.
Select 'Launch XMB Waves Installer'. Wait for PS3 to fully reboot.
Here we will change the font style on our Ps3. Any TTF font is compatible but do consider that if the font size is too large or too small, it may become unreadable. You can change all 3 system fonts. Normal, Rounded and Pop. Please also consider that if the Original font is changed, it will replace the system font used for things like notifications and the epilepsy warning when you boot your console.
Download your desired font. (Must be a TTF font).
For Original, rename your font to 'SCE-PS3-RD-R-LATIN2.TTF'. For Rounded, rename your font to 'SCE-PS3-SR-R-LATIN2.TTF'. For Pop, rename your font to 'SCE-PS3-VR-R-LATIN2.TTF'. Copy/Move your renamed fonts to the root of your USB drive. Boot console.
Navigate the XMB to 'HAN Toolbox/File Injector'. Select 'Inject TTF Font', it will open a browser. Select the drop down box 'Slect Source Font File'. Select your desired font we renamed earlier. Select 'Initialise Font Flash Replacement'.
Wait for the green confirmation. Select 'Copy Font To Flash'. Wait for PS3 to fully reboot. Part X - Install PKGs to USB Hard Drive?!???!! - Maybe Yes, Maybe No. Keep checking back for updates. You spotted this section that says you might be able to play your backups from a USB Hard Drive.
Here's the low down. I've been speaking to some people, who tell me that there's a possibility of this happening. Here's the key word though, ' possibility'. I'm not saying that it's available. I'm not saying that it's being worked on.
I'm not saying that it even exists. I'm saying that there may be a possibility later on. DO NOT ASK ME ABOUT USB HDD SUPPORT. THIS WILL BE ADDED AS SOON AS I KNOW THE DETAILS!! Conclusion/Outro Wowee. What a journey its been. I hope you have found my guide useful in some way and I hope your console exploitation adventures are successful and enjoyable.
This guide was written solely by myself with a few pointers from various members from this forum. I have taken the time out of my own busy life to put this all together and is available to everyone FREE of charge You may copy and spread this guide far and wide as long as you give credit and link back to the original thread here at PSX Place. Peace /tab/tabs.