NOTE: For people who have downloaded version 2.00, 2.01, 2.02, is necessary to use version 2.10 for optimum performance.
CustomFirmware Enabler 2.10 to 5.03 ChickHen by Xenogears and Becus25.
What is?
A program that activates the functions of the M33 custom firmware using ChickHen.
What do I need?
- A PSP Slim (Slim only works with, regardless of the plate you have)
- Firmware version 5.03.
- ChickHen R2 (minimum Beware patched versions!).
2.10 Changes:
- Fixed a problem when you change settings for the plugins.
- Fixed internal problems.
- Fixed a problem that caused a crasheo accessing plugins and have no plugin.
- Improved detection of release.
2.02 Changes:
- Fixed a bug in the installation of the Pops (The PRX MD5 is different in each PSP, which is why the test works, but not in the other consoles)
2.01 Changes:
- Fixed a bug not detect either a previous installation (caused that could not be installed above the new version)
2.00 Changes:
- System pops native activation.
- System configuration Custom Firmware.
- Verification MD5 of files that are installed in flash, if you have not installed either, re-install.
- Nice interface.
- Safety flasheos unnecessary.
- Protection from ChickHen load the Custom Firmware.
(It is necessary that this ChickHen in a folder called "ChickHEN inside Photo or Pictures.)
- Changed version of the system (now shows 5.03 M33)
Installation:
- Copy the folder to your psp CFWEnabler in X: / PSP / GAME /
To be asaÃ*: X: / PSP / GAME / CFWEnabler / EBOOT.PBP
IMPORTANT: Do not change the folder name CFWEnabler!
How to use:
Starts ChickHen from the picture section. Then start the homebrew called "CFWLoader 2.00.
Follow the instructions that tells you the program.
FAQ:
- Can load isos? - Yes, yes, you can.
- Do you like my PSP Slim is ****ing plate? - Yes, it does not matter.
- Does my PSP3000? - No, it does not work.
- Are you going to get a version for PSP3000? - It is not known.
- Sure you do not know? - Yeah, sure.
- Really? - Yes
- Really good for? - ¬ ¬
- Can you break my console? - This version has several checks to verify that everything is installed, it is 99.99% safe
- When you turn off the console I have to repeat the procedure? - Yes, you have to repeat it, but after the first time, no longer flashea anything.
- And you can not prevent either procedure? - Could be avoided if we could do an IPL compatible.
- Is expected to be in the future rectify the current problems? - It is possible, but is not guaranteed anything.
- Does the M33 SDK? - Yes, it works.
- Are the plugins? - Yes, they work.
Common Errors:
- When you start the program automatically goes to the menu --
Was unable to assign the flash, make sure you have a PSP Slim (2000), and if you go, make sure your version is correct ChickHen.
- I do not run the isos --
Make sure that your configuration is correct.
- I created a folder called SVCPlayer Why? --
You have a plugin that creates nothing to do with CFWEnabler.
- Other errors is important to check the plugins that are loaded can cause problems.
Activate Pops:
To enable compatibility with Native Pops, it is necessary to remove some modules of the firmware 5.00 official.
- Required --
- A PSP that enables homebrew loading (or PSP 2000 with Hen CFWEnabler voucher)
- The 5.00 update from Sony. (
http://rapidshare.com/files/154173870/500.PBP)
- PsarDumper with support for 5.00. (
http://rapidshare.com/files/165390935/p ... 00_too.zip)
1.-The PsarDumper copy of our report.
2.-copy the firmware 5.00 to the root of the PSP under the name "EBOOT.PBP"
3.-execute the PsarDumper.
4.-click on "X" and waited.
5.-When finished, enter usb from pc and have a root folder called F0.
6.-looking pops.prx files in the folder and popsman.prx kd (in F0)
7.-The Copy To Folder Pops within CFWEnabler (X: / PSP / GAME / CFWEnabler / Pops)
8.-Run the CFWEnabler.
9.-click on the option "Enable Support Pops."
10.-We followed the instructions.
11 .- Done, and you can delete the files from the Memory Stick Pops, both the EBOOT.PBP and the F0 folder as the files in the folder CFWEnabler / Pops.
Warning: Using the Firmware M33 can be accessed freely by the USB Flash0 care because you can cause a brick, you are advised not to change anything to the internal memory.
Acknowledgments:
- A Dark_AleX for the M33 modules.
- Especially him, who knows who he is, and that is part of the credit for helping him.
Un Saludo.
