Open Source Pandora Battery Tool 0.52 *** SLIM & FAT BAT ***

[Highlander]

work done by by MaHan05, so i can't take credit for this, but can assure that it works.

Downgrading from 2.0 to 1.5

The following two files are necessary...

MPHDowndrader
1.50 EBOOT

2.0 U.S. EBOOT
2.0 JAP EBOOT

you'll need to upgrade to 2.0 first, if you're using 1.51 or 1.52

* Please note Norton AntiVirus and/or other virus scanners will incorrectly detect the MPH Downgrader as a virus.

This will ONLY WORK on a 2.0.

1. You need to unzip the files MPHDowngrader.zip and EBOOT_1.50.zip. Use a program such as WinRAR, 7Zip, or WinZip (check Google). Once they are unzipped, you're ready to begin.

2. Set up a USB connection with your PSP and your computer.

3. Once the connection is set up, open up My Computer and browse to the removable disk that is your PSP. You'll need to set a few things up here.

4. When you first double click to open up the PSP on your computer, you'll be in what's called the root menu. There will be a PSP folder showing if you are in the right place.

5. Copy over to your PSP the following files to THIS location in the root folder...NOT in the PSP folder or any other folder. Index.dat and h.bin should both be in your root directory.

6. Once this is done, open up the PSP folder and then open up the Photo folder. Here, you will copy overflow.tif over, keeping it in the Photo directory and not a sub directory.

7. Now, go back to the PSP directory and go into the Game directory. If there is not already, create a folder called UPDATE. It MUST be called UPDATE and nothing else.

8. Open up the new UPDATE folder and then copy EBOOT.PBP into this folder from your computer. Once all of this is done, you're ready to downgrade. So far, so good.

Double check that you followed the above instructions before continuing.

Good.


9. Now, disconnect the USB connection from the computer and plug the AC adapter into the PSP. As with all upgrades, you must have a certain percentage of battery life as well as the AC adapter plugged in, or this will not work.

10. Go to the Photo icon on your PSP and scroll through the pictures to get to overflow.tif. You do NOT have to press anything. It will start automatically. Two strings of letters/numbers will appear. This is normal and good.

11. Wait AT LEAST 30 SECONDS and then turn off your PSP by holding the power button up until it fully shuts down. Then, start your PSP again.

12. You will now go over to the Game icon and scroll down to memory stick. Select it and you should see the 1.5 update.

13. Select it and start it up. Go through it as you've done before with your 2.0 update and follow the prompts. When the update reaches 99% it will crash and show an error. THIS IS OKAY. DO NOT PANIC. Once again press the power switch up until it fully turns off.

14. Now, turn the PSP back on. You will get another error. Just press the "O" button and it will restart after rebuilding the system data. Then just set it up as you did when you first got your PSP and you have a brand new 1.5 PSP. Be responsible with it.

please note that nor I or Digital World is responsible for what you do with you PSP nor are we held responsible if you damage or corrupt your PSP.

all mods/upgrades/hacks are done at your own risk.

 

[Highlander]

Guide for personalizing your PSP with your own choice of monthly backgrounds

please note this is not my work, so i can't take credit.

This tutorial will explain how to change your background using PSPersonalize. For simplicity I've created a custom PSPersonalize package for the no-swap KXploit method.

We're not responsible if you render your PSP useless.

Note: This DOES NOT work on any firmware versions - strictly 1.50!
What you need:

PSPersonalize KXploit package
some new psp backgrounds

There are 12 months in a year, thus 12 possible backgrounds for the PSP. You MUST rename the bitmaps you download to XX.BMP (XX represents numeric two digit month)

examples:

01.BMP - January
02.BMP - February
03.BMP - March
04.BMP - April
05.BMP - May
06.BMP - June
07.BMP - July
08.BMP - August
09.BMP - September
10.BMP - October
11.BMP - November
12.BMP - December
Remember the following rules when using a custom background - the image must be:

a 24-bit Bitmap (BMP)
<= 150KB in size
<= 300x170 resolution
Got it? Good.

1: First create a USB connection between your PSP and PC.

2: Extract PSPersonalize_v1a-kxploit.zip to your memory stick under \PSP\GAME - this will create two directories, so you'll end up with:

PSP\GAME\PSPersonalize%
PSP\GAME\PSPersonalize

3: Rename your BMP's respectively

4: Copy the BMP's to the root directory of your memory stick. If Windows recognizes your PSP as drive letter i: then copy the bitmap(s) to i:\. The final result should resemble this directory structure:

5: Browse to the Game menu on your PSP

6: Select PSPersonalize - disregard any "Corrupted Data" - it's nothing

7: Boot PSPersonalize

8: It will automatically detect the BMP's in the root directory. Press "O" to confirm the background change or press "X" to cancel

9: You'll end up at a "finished..." screen. Press "Home" and return to the PSP menu

10: You should see your background, depending which month you selected. If you don't try rebooting the PSP

 

[Highlander]

PSP ISO Compressor

Filename: PSP_ISO_Compressor_1.1.zip
Size: 355KB


Description:
v1.1 A user-friendly front-end for converting ISOs to .DAX or .CSO compressed format. v1.1 includes:

* Added support to convert .dax<->.cso automatically.
* Code cleaned up and reordered.
* Fixed bug where trying to convert an iso image with an extension in capital letters, e.g. GTA.ISO or gta.ISO; the program would not automatically change the extension to the new format, e.g. .dax, meaning that you were trying to overwrite the original ISO with the compressed one causing the program to crash and a 4KB .iso file to be created.

Written by danny_kay1710

 

[Highlander]

Easy 2.71 Downgrader

Filename: Downgrader2.71FULL.exe
Size: 15.63MB


Description:
Easily downgrade your 2.71 PSP with no questions asked! Connect your PSP via USB, turn up your speakers, and run this Windows executable. That's it, that's all!
Released by Xtrusion.

Easy Downgrader 2.71

 

[madnlooney]

have you tried psp umd dumper 0.2? it dumps the umd till your ms is full, you copy the part dumped file to PC then continue dumping. with all parts you click the .exe and it puts then together as an iso. ive attached it if you havnt got it.

 

[DEE747]

Play movies on your PSP

1st u will need a convertor to do this there are lots about WINAVI PSP VIDEO 9
XILISOFT and my favorite IMTOOtoDVD

once youv`e chosen your convertor next step is to convert the movie most convertor`s do same thing ie; DVD into drive and then click on convert to MP4 you can normally select the drive destination you want to send it to so if you USB your PSP to the PC and select the external drive location (ie DRIVE G/MP_ROOT/100MNV01) the film will convert and be put into the folder in ur psp

some convertors will name the files for you but incase they don`t u need to rename them or the psp won`t recognise the files and when you go the film folder they will not be shown or you will get an icon saying CORRUPT DATA

If you go into MP_ROOT/100MNV01 and rename the files as follows :-

M4VOOOO1 for the main film and the thm should be named the same as the main film this links them together it will then show u an icon of the film in the memory stick when u access it.
To name the 2nd film you would name it M4VOOOO2 on so on

 

[DEE747]

Easy step by step guide for converting psx games to PSP

I cannot take any credit for this as the program created by ZiNgA BuRgA is so simple your child could use this, I have uploaded the program in the downloads section so just go and download from there , and do as follows :-

1. Once downloaded put winrar file in new folder and extract all files.

2. Click on icon of control POPSTATION GUI.

3. Click on the Browse but and select the ISO,CUE,IMG or BIN file.

4. Then select the destination folder you want to send your converted file to .

5. If your ISO game is PAL just tick the tab fix screen height (PAL games the screen is pushed down abit at top) if your not sure tick tab anyway.

6. There is a CUSTOMIZE the EBOOT section at the bottom where you can change the icon thumbnails should you chose to default settings are in next tab PREVIEW EBOOT.

7. When you have finished customizing your EBOOT icons just click GO!!!!

8. When conversion is done connect PSP via USB cable and select drive PSP is located and it will automatically send direct to PSP in the correct folders.

9. START UP PSP GO TO MEMORY CARD AND ENJOY !!!

N/B
There is a compression level on this program too

 

[DEE747]

tutorial on using vcdromx

[I decided to write this guide as many people have encountered problems with UMDGen.
One such problem was that the ISO size increased considerably when UMDGen was used.

So here are the instructions step-by-step on how to modify an ISO using VCDROMx:
1. Download VCDROMx English version from here: http://www.psp-hacks.com/file/183
2. Extract the file and open VcdRomX.exe
3. Click Cancel when a dialog box comes up.
4. Go to File-->Convert File.
5. Under the heading "Source", select the type as .ISO
6. Click on the picture of a folder next to the name box and browse to an select the ISO
you want to modify/fix
7. Under the heading "Target", select the Type as FCD or VCD
8. Click the folder next to name and then type in a name for the FCD and press OK
9. It will now convert. It will now convert. When it finishes press Close
(even if it says "99%")
10. Now go to File-->Fix VCDROM and then click on open VCDROM.
11.Browse to and select the FCD or VCD file that you created before and select it
and press OK.
12.From here its pretty self-explanatory from the menu you can extract,
replace and dummy files

Step-by-Step Creating an ISO:
1. Open up VCDROMx and click New.
2. Click on the folder button and browse to the place you would like to create the ISO
and type in a name for it and clickOK
3. Choose a volume label, any will do
4. Leave the VCDROM type as normal and pressOK
5. Now drag and drop the files you want to make an ISO out of (e.g PSP_GAME and UMD_DATA.BIN files)
6. Do any modifications that you want to do and click Save
7. Now use the File-->Convert File function to convert the FCD file you made
into an ISO (check above for more info)

not my work i borrowed it ok

 

[DEE747]

making ISO`s smaller without compressing

i know some games lag a bit if u compress them so thought a few of you mite like this (i cannot take any credit for this work )


Making your ISOs smaller without compression
Written by Eternalis
Monday, 11 December 2006
A few people on Afterdawn have been asking how to reduce the size of their ISO. So I wrote instructions on how to reduce the size of your ISOs without compression (for some games compression will slow down the game e.g GTA). You can always compress your ISO after following these steps if you want to reduce the size even more.

Instructions

1. Download UMDGen 4.00 from here:
http://www.umdgen.com/UMDGen_v4.00.rar

2. Now open up your ISO in UMDGen and browse to PSP_GAME\USR_DIR\ and find any AT3 files (music files) that you don't need. For each one, highlight the file and right-click then click on dummy. Note: The music files will be in a subfolder inside USRDIR, the name of the folder differs between games.

3. Now, find any PMF files (movies) you don't want and for each one, highlight the file and right-click then click on dummy.

4. Now browse to PSP_GAME\SYSDIR\ and delete the UPDATE folder.

5. Also delete the BOOT.BIN file.

6. Now go into PSP_GAME\USR_DIR\ and look for any files that have a name of a language other than english. These files are normally found in a folder called "locale" (which may be located in a subfolder). When you find them delete them. Note: By doing this you will remove any other languages from the game and you can only play the game in english.

7. Now save your ISO and it will be smaller. If you want to compress it to CSO, once you have followed the steps above, press CTRL+C.

Good Luck!

Also note: some games like Killzone do not have the music/videos stored in PMF/AT3 files so you cant use this method to make them smaller.

 

[bro]

psp guide and info

===========Homebrew Info=============
With all of this talk of homebrew, and hacking, and whatever else, you probably can't help but wonder WHAT homebrew is. Homebrew is, in a technical sense, 'unsigned code'. What this means is that all Sony provided games, from downloaded demos to UMD games, are digitally signed. When the PSP tries to run any game, it looks for this digital signature, and if it can't find it, or it's wrong, the PSP won't run it. Homebrew is run by exploiting 'holes' in the firmware that bypasses this signature check, and allows the game to be run. Sony has encrypted, or hidden, this signature from all of us. Every time we try to mess with their file, this signature gets smudged, so it can't be read anymore. This prevents us from just taking an official Sony file and replacing it with our own code, or just looking for the Sony signature

Homebrew itself is anything that is created by a user. This ranges from a SNES emulator to any of the truly original games, such as Callisto, out there. Much of it is actually very fun, and can really add to your PSP experience. Various methods have been designed to play homebrew games. This ranges from the 'kxploit' trick in firmware 1.5, to the eloader in versions 2.0 and up.

===========ISO Info=================
I will keep this section short, as I do not condone piracy. However, I would be stupid not to admit that it is what the PSP is primarly used for. An ISO is a 'image' of a game that you put onto your PSP's memory stick. Usually these are downloaded, and they are always illegal. They are also usually quite large, at least 500 MB. They can be compressed to the CSO format, which may save you 100MB or so of space.

To play these games, the most common way to do so is either Device Hook (A.K.A Devhook), which is a homebrew program, or custom firmware, which will be described later.

============Downgrader Info=============
Downgraders are homebrew applications that rewrite the PSP's flash memory to change it to a lower version. The PSP's Flash Memory holds all of the PSP's vital information, such as how it is supposed to run. Without this information, the PSP cannot run. The only way to change this is through downgraders. It is always slightly dangerous to do this, as if something goes wrong, you will have a very expensive brick. It is also extremely difficult to make a downgrader. First a User Mode exploit needs to be found, which allows us to run homebrew on that firmware version, and then a kernel mode exploit must be found, which allows us to access the PSP's flash memory to change it. Just because you hear of a firmware being 'decrypted' does not mean that it can be downgraded. Whenever possible, it is highly recommended to downgrade your PSP to version 1.5, where you can then go to Custom firmware

Downgrading is very safe. The warnings you see about bricking your PSP is there just to allow the developers to cover their bases, so that if something does go wrong, they aren't responsible. Every time you change anything on the PSP's flash memory, from a font, to a full downgrade, you have a very small chance to brick. 99% of all downgrades are successful. The other 1% is usually because the person doing the downgrade cannot follow instructions. So always read the readme file before running the downgrader, and you'll be fine. Downgrading is ALWAYS recommended over HEN or the like.

==========Firmware Info===========
The firmware is the files that the PSP uses to run, which is located on the PSP's internal flash memory. This is everything the PSP does, from how it plays a game, to the sound it makes when it starts. It controls every aspect of the PSP, including whether or not we can play homebrew. Firmware versions 1.0 and 1.5 are fully capable of running homebrew applications. 2.0 and up, however, require the eloader, and HEN (Homebrew Enabler) to run homebrew. Often times, these firmwares can be downgraded to a lower version, such as 1.5, which can play all homebrew at full speed, without the need for any extra loaders.

1.0-1.5 -> Full homebrew capability. No restrictions. Used to install custom firmware
2.0-3.50 -> Limited homebrew capability. Can all be downgraded to 1.5
1.5 POC, 1.5 CFW, 1.53, 2.71 SE, 3.03 OE, 3.10 OE, 3.30 OE, 3.40 OE, 3.50 OE, M33 -> Custom Firmwares. Full homebrew capabilities with no restrictions.
1.0-3.50 (Special Note) -> Using Pandora's Battery, ALL firmwares can be downgraded. However, to run it requires you have a PSP already capable of running homebrew games.

==========Custom Firmware===========
Custom firmware is also a new development. These require firmware 1.5 to install, as to do so involves writing to the PSP's flash memory, and 1.5 is the safest firmware to do so from. Not to be confused with official Sony firmwares, custom firmwares allow us to have some of the best features that Sony would never allow. Custom Firmware allows you to have recovery mode, so the PSP can be brought back in the event that it is ever bricked.
There are several notable PSP custom firmwares out right now.
HarleyG's Custom Firmware- This is a basic custom firmware, based on the proof of concept. It features a recovery mode, and the ability to dual boot between Devhook, and 1.5, among other features.
Dark_aleX's 2.71 SE- An earlier form of the OE firmwares, this custom firmware was based off of the 2.71 firmware. It is not widely used any more, instead being favored for the OE series of firmwares.
Dark_aleX's OE series - This is the most popular custom firmware, not to be confused with regular 3.xx firmwares. Unlike the official Sony version, this allows all homebrew to be played as if it were a 1.5 PSP, allows ISO files to be played without a loader, and also has recovery mode, among other features.
Eiffel65's 1.53- This is a custom firmware very similar in functions to HarleyG's custom firmware, but has a number of improvements. It has all of the features of HarleyG's Custom Firmware, as well as a few new features, such as the ability to load a custom XMB. It is still in its early releases, and will most likely be improved.
M33 Firmwares- Developed by Team M33, this firmware improves upon the OE series of firmwares that were left behind when Dark_AleX left the PSP hacking scene.

Information on putting any of these onto your PSP can be found in the tutorial section of this website. Just like a downgrader, these write to flash memory, so there is always a slight risk.

==============Pandora Application=================
This is a application, released by a team of VERY skilled PSP hackers, that allows us to un-brick any PSP without sending it to Sony. It uses the same process that Sony uses at its repair centers, allowing it to un-brick any PSP sent to them. The catch is, here, a minimal version of 1.5 is installed, as opposed to the latest firmwares that Sony would install. This application can also be used to downgrade ANY past, present, or future offical Sony firmware. More information on where to find this application, and how to use it, can be found in the Tutorial section of this site.
A few notes, however-
1. The "Pandora Battery" required to un-brick a PSP CAN NOT be used normally in that state. When transforming the battery into a Pandora Battery, you have the option to create a backup of the battery's flash data. This is ESSENTIAL if you intend to use it again as a normal battery. See the tutorial section for more info.
2. There is a simillar process used on the memory card. A simple Re-Format using the PSP's "Format Memory Stick" will return it to it's normal state.
3. The version of 1.5 running from the Pandora's Battery MINIMAL. Many things will NOT work. Pandora's Battery does come with a flasher that allows you to re-flash 1.5 to your PSP.

Special Note-> Pandora's Battery can unbrick or downgrade ANY PSP. The exception to this rule is any PSP that was bricked (Bricked. It can still downgrade TA-082/86 PSP's) by corrupted ID Storage Keys. PSP's bricked in this manner CAN NOT be unbricked, as Pandora's Battery has no way to fix them. (I.E- Attempting to downgrade a TA-082/86 PSP without the special downgrader)
===============================

That about sums up your information on the PSP, and why we try to hack it. Hopefully you've learned a bit, and can save yourself a few questions. If not, you are welcome to PM me, or ask in the help section of this website. Hopefully a mod here will sticky this either here in General, or move it to the Tutorials section. Either way, I hope this provides help to many PSPers out there, and helps you on your way to PSP hacking!

 

[bro]

glossary of terms

========Glossary of Terms==============
Bootsound-
The sound that plays when a PSP is coldbooted.
BOOSTER-
The developer responsible for DevHook.
Brick-
A system critical file has been corrupted on the Flash Memory, rendering the PSP unable to start. Depending on how critical the corrupted file, it may be possible to recover the PSP using any Custom Firmwares' recovery mode. Also, ANY brick (Full, or Partial) can be recovered using Pandora.
Bricker-
A slang term used to refer to any homebrew game/app that either accidentally, or purposefully, permanently damages the critical parts of the PSP's Flash, rendering it a brick.
BSoD-
This comes up when something on the Flash 1 has been corrupted. Pressing O will reset it with no permanent damage. This also commonly shows up after a downgrade. A.K.A- Blue Screen Of Death
Coldboot-
A "hard start" of the PSP
Custom Firmware-
Special firmware version created by PSP hackers to allow for additional features
Crack-
Meaning we've found a potential weakness in the PSP's firmware, which may lead to homebrew.
CSO-
"Compressed ISO", a way to make an ISO file smaller on your memory stick
Customization-
'Modifying' your PSP by flashing new fonts, icons, backgrounds, or sounds to the PSP's flash memory, usually through the use of XFlash
Dark_aleX-
Possibly one of the most well known PSP hackers, known for his work on many downgraders, and the SE/OE series of Custom Firmware.
DAX-
A shortened form of the famed PSP hacker, Dark_aleX. It is also a form of PSP ISO Compression
Decrypt-
The encryption keeping us from looking at Sony's code has been broken. This allows us to analyze the PSP's code, and look for a weakness.
Dedaleus-
The most actively developed Nintendo 64 emulator for PSP.
Devhook-
A homebrew application that allows the PSP to emulate, or imitate, another firmware version without actually upgrading, Created by BOOSTER. This is the most common loader in use. A.K.A- Device Hook
Disc0-
This is how the UMD drive is identified to the PSP
Downgrade-
The act of rewriting the PSP's flash memory with a lower firmware version to allow for Homebrew. Requires a Kernel Mode exploit
Downgrader-
Rewrites the PSP's flash memory to a lower version. Can potentially brick your PSP
Dump-
Usually includes Flash0, and occasionally Flash1. These files are copied from the PSP's flash memory, usually for use with DevHook.
Eboot-
A file that the PSP can run.
Eloader-
A.K.A Eboot Loader, A application that allows homebrew to be run on PSP firmwares 2.0 and higher
Emulator-
This fools the PSP into thinking it's something it's not, such as a SNES
Exploit-
A weakness has been found in the Firmware, which allows us to play unsigned code, A.K.A Homebrew
Fastloader-
An older form of a PSP ISO loader. Devhook is more common now.
Firmware-
The 'operating system' of the PSP
Firmware 1.5-
The most hacked firmware, next to custom firmware, that allows us to do anything
Flashing-
The act of copying a file to the Flash Memory to change the operation of your PSP.
Flash-
The internal memory of the PSP, which contains all information on how the PSP is supposed to run. Cannot be easily altered.
Flash 0-
This contains the PSP's system information
Flash 1-
This contains the PSP's information on the user, such as wifi setup, and usernames
Flash 2/3-
Rumored areas of the PSP's flash memory. Not much is known about their use.
Flash Memory-
This is the internal memory of the PSP, which contains all of its system information. A.K.A - Flash
Full Brick-
This happens when a critical part of the Flash Memory is damaged. A signal of a full brick is the inability to access recovery mode on Custom Firmware. These can be recovered using Pandora's Battery.
Gameboot-
This is the movie that is played when any game, or UMD is run
Hack-
Anything to make the PSP do something it isn't meant to
HEN-
Homebrew Enabler. This tricks the PSP into thinking it really is allowed to run homebrew code on higher firmware versions.
Homebrew-
"Unsigned Code" used to play games that Sony doesn't normally allow
ID Storage Keys-
A set of information stored on the PSP that defines the general rules for how it works, from how to handle the charger, to what firmware versions are allowed to run. (In the case of the TA-082/86 PSP's) This is above a firmware in the way that PSP uses it.
ISO-
PSP game 'image' that is usually illegally downloaded
Kernel Mode-
A way to run homebrew, and allows access to Flash memory. This allows for downgraders, or for homebrew to be run at max speed.
LCS-
Refers to Grand Theft Auto : Liberty City Stories. Commonly used to downgrade or run homebrew.
Loader-
Assists in the playing of PSP ISO's
Lumines-
A UMD Game containing a flaw allowing for PSP Downgrades in some recent (3.30 +) firmwares.
"Magic" (Or Pandora) battery-
This refers to any battery pack that has been modified using the Pandora program to allow it to un-brick a PSP. While in this state, the battery CAN NOT be used normally, but it can be restored to its original state using a backup of the battery's flash. Read the tutorial section for more information.
"Magic" (Or Pandora) Memory Stick-
This refers to any Memory Stick that contains the files used by the Pandora program to un-brick a PSP.
Modchip-
A second Flash Memory that can be soldiered to a PSP's motherboard, making the PSP 'unbrickable'. However, this requires advanced skills to install. A.K.A- Undiluted Platinum
MP4-
The only movie format that the PSP can play. In order to play, it must be specially converted for the PSP using computer software.
MS Root-
The Root of your memory stick, or the first folder you see when you open it on your PC.
Noobz team-
A team of PSP hackers that have contributed the eLoader, xLoader, and help with many PSP downgrades
OE-
"Open Edition". The common term for Dark_aleX's most recent Custom Firmware. Currently at 3.10 OE-A
Official Firmware-
Not to be confused with custom firmware, this is the firmware released by Sony to block homebrew games
Pandora-
A application that will turn your PSP's components, including its memory stick and battery, into special "Magic" items. This is the same process Sony uses to un-brick PSP's you send them.
Patched (Grand Theft Auto)-
Commonly used to refer to a version of the Liberty City Stories UMD game that has had the flaw to run homebrew removed. Impossible to tell on the box, but contains a 2.50 or 2.60 update on the UMD. Most common version of Liberty City Stories on store shelves.
Recovery Mode-
This allows you to bring your PSP back to life, if you happen to partially brick it.
RSoD-
More severe than a BSoD, this may mean something serious is corrupted. Usually, resetting the PSP will cure this, however. May also show up after a downgrade, in which case a reset will get rid of it. A.K.A- Red Screen Of Death
SE-
"Special Edition", used as in 2.71 SE, which is a custom firmware created by Dark_aleX
Semi Brick-
This is a brick that was not caused by corrupting critical files. The PSP can be recovered using Custom Firmwares' Recovery Mode, or Pandora's Battery. If recovery mode can be accessed, it is a semi-brick, not a full brick. A.K.A- Half Brick
Signature-
The way that Sony tries to restrict homebrew. The PSP will look for this every time any code is run. Hacks allow us to bypass this.
SNES_9x-
The most common SNES emulator for the PSP
Sony-
The company that designed and developed the PSP
Sony Official Firmware-
Any firmware released by Sony. These are most commonly released to combat the hacks that the PSP hacking scene has discovered. Upgrading to any Sony Official Firmware will make your PSP unable to play any homebrew games.
TA 079-
One of the "good" motherboards, which can be downgraded without any extra steps
TA 081-
Another "Good" motherboards, can also be downgraded without any extra steps.
TA 082-
"Bad" PSP motherboard. Requires a different downgrader to downgrade. Can be identified by "IC1003" marking on the upper right of the PSP UMD tray. Picture Here
TA 086-
Another "Bad" PSP motherboard. Requires the same downgrader as a TA-082 board. Can be identified in the same manner as TA 082.
UMD-
Universal Media Disk. This is what the PSP plays its legitimate games from.
Unpatched (Grand Theft Auto)-
Refers to the version of Liberty City Stories that contains a flaw allowing us to run homebrew and downgraders. Impossible to tell by the box, but has a 2.00 update on the UMD. Not easy to find anymore.
Unsigned Code-
A.K.A Homebrew. Code that is run on a PSP without the officially Sony signature.
Upgrade-
Usually referred to upgrading the PSP's firmware using an official Sony update, which is highly discouraged. May also refer to installing custom firmware.
User Mode-
This is a way that homebrew can be run, but cannot access anything on the flash memory, so it runs slower than kernel Mode
XFlash-
Allows for customization of the PSP by flashing new items to the flash memory, such as fonts, or pictures. Has a very small risk of bricking.
xLoader-
An experimental version of the eLoader, created for firmware 2.80
XMB-
Cross-Media-Bar, The PSP's 'main menu'. This is where you can choose a UMD game, view pictures, listen to music, or watch movies. all credit to Iceman

 

[bro]

for people without use of custom psp to downgrade

can be used on a fat psp or a slim psp with a datel tool battery
http://dl.qj.net/TOTALNewbi-easyInstaller-PSP-Tools-Utilities-(on-PC)/pg/12/fid/14749/catid/193

 

[Hejira]

Open Source Pandora Battery Tool 0.52 <- for SE/OE/M33/Des.Cem homebrew enabled kernels
-------------------------------------

I have used this myself on my SLIM PSP 3.71 M33-2 & 3.80 M33-5 to create Pandora and use with Des.Cem 4 and return to normal my SLIM PSP Battery.

I have Documented basically what I did here:
https://www.digitalworldz.co.uk/index.php?threads/160749/

*** IMPORTANT NOTE: Quote From Authour @cory1492! ***

Every release by me since 0.3 or so (see first post of this thread) has been tested as working on my slim battery.

As to new hardware that may or may not be out there I cannot comment directly, though apparently there are new batteries that can't be converted (yet to see proof that these supposed new batteries are actually not fakes from bad fleabay sellers or similar unscrupulous resellers) and a new revision of PSP slim that is not (currently? No idea what they'd have changed to do that) able to write batteries using the known commands.

I for one refuse to jump on the bandwagon again (though, in all things it's better to be prepared, safe rather than sorry) - it was believed at the outset of the slim that trying to convert a slim battery would result in a corrupt/bricked battery when in fact that only seems to have happened when someone tried to convert a slim battery in a old/fat PSP.

Quote From Me @Hejira
*** ALWAYS READ THE README *** (That means you to bro - LOL)

Allows the same options as the original Pandora tool:

Service mode: **This is the Option I used after I had run BACKUP EEPROM**
writes a serial 0xFFFFFFFF to the battery eeprom
(inserting the battery will power on and wait for a proper MS)

Auto boot mode:
writes a serial 0x00000000 to the battery eeprom
(inserting the battery will power on and boot the firmware)

Dummy normal:
writes a serial 0x12345678 to the battery eeprom
(the battery will work normally)

Backup eeprom: **THIS IS WHAT I DID FIRST**
reads the battery eeprom to a file "eeprom.bin" in the root of a MS

Restore eeprom
if a file "eeprom.bin" is present, it will attempt to write it to the batteries eeprom

additional option: **This is the option I used to return my SLIM BAT to normal**
Flash only serial from ms0:/eeprom.bin (0x########)
######## is the serial from the dump will flash only the serial number found in the dump. Best option instead of restoring the entire dump. With the first byte of a dump being [0], and the serial being 0x12345678 (for hex editing)
[14] = 0x34
[15] = 0x12
[18] = 0x78
[19] = 0x56

***This May not work with all batteries.***

Installation:
-------------
Use whatever method you'd normally use to run homebrew under 3.xx or 2.xx OE/SE/M33 kernels on your PSP.

example:
-put the folder "ospbt_xx" (with eboot and prx) into /PSP/GAME371
-run it from the PSP MS menu.

example2:
-put the contents of the elf folder (.elf and .prx) into the ms0:/elf
-run with jas0nuk's elf menu

known issues:
-------------
-when writing a full battery eeprom.bin file to a battery, errors may occur. Redumps may show differences from the dump being written.
-when no eeprom.bin file is present on the MS, the option to write the file to a battery will intentionally be grayed out.
-only relevant options are listed and available with any given battery.
-after the intial confirmation, there are NO OTHERS!

No warranties expressed or implied. GPL is included with the source, source modifications should be published with rebuilds.

credits:
---------
- Chilly Willy for releasing source to his apps (3.xx examples), and for the key waiting routines used in this app
- nem for sharing the battery syscon prototypes on ps2dev (BIG thanks!)
- Everyone involved with Prometheus for creating and releasing the Pandora project (including but not limited to Noobz)
- M33 for enabling homebrew on the kernel I tested this on
- Dark_Alex for proving CFW was possible, then going 1000 steps further
- Everyone behind the forums and toolchains at PS2dev.org <- without them this stuff just... wouldn't be.
- SilverSpring for your never ending patience with me, for the reversed NVM routines, and the true NVM NID name.

**** - whomever it was who scared everyone into not testing the battery creators with slim batteries. You were wrong. It works fine if you only write the serial.***

- my father for always encouraging me to go on, rest in peace.
- anyone else I may have forgotten.......

version history:
-----------------
0.52- fixed misc. syscon error handling (previously only handled battery not present error)
0.5 - updated to work with all current custom firmwares (at this point 3.80m33 is the most recent), elf also tested under des.cem V3
0.4 - by reqest (Mandingo@maxconsole) when eeprom file is present it will now display the serial from the dump on the option line
0.3 - tested as working on a slim battery
- added option to restore only the serial from a dump instead of the full dump
- added an elf folder for use with jas0nuk's elf menu (put both the elf and prx into ms:/elf/ folder)
0.2 - updated to support 3.71 syscon NIDs, should work under every SE/OE/M33 version to date.
0.1 - initial release, confirmed working in 3.52m33 and 3.60m33(slim) with PSP-1000 type batteries

If anyone feels I have abused the privelidges of their source releases, let me know and I will try to rectify it.

cory1492

Program including source View attachment 37538