Try these:

-Upgrade to SE-B". This is much better and testing to see if SE is any good with the first version is not very clever.

- Ensure all your homebrew is in the "GAME150" folder under "PSP" on the memory stick. This means that all the applications in that directory are loaded under the v1.50 firmware kernel. The "GAME" folder on SE-A indicates to the firmware that all executables should be loaded with the v2.71 kernel, which is not what you want.
(If you upgrade to SE-B" then you have the option of switching the "GAME" folder to the v1.50 kernel and the v2.71 kernel to a folder called "GAME271").


- If the files display as corrupted, you have two choices; (The latter is better):
|
|- 1. Download "PBP Unpacker" (Google it). Find a homebrew |that show is |Incorrupt, and choose to extract the files from that |EBOOT.PBP using
|PBP unpacker. Take the PARAM.SFO file and place it in a safe place. Now,
|use PBP unpacker to extract the files from the corrupted EBOOT into a |different folder.
|(If it's a Non-Kxploit'ed EBOOT, or single-folder homebrew, then just use the |PBP from that directory. If it's Kxploit'ed, then unpack the files from the |EBOOT in the folder ending or beginning with the % symbol).
|Open the PARAM.SFO file from the working EBOOT with PBP unpacker and |edit the program title to your liking. Save it to file.
|Replace the PARAM.SFO from the directory of the non-working EBOOT's files |with that of the file we just edited. Press "NEW" in PBP Unpacker and using |the options assemble the file using all the files in the EBOOT's directory. |(Using what there is, so if there's no images or .PSAR file don't worry.) Press |"Save", and save it to the homebrew directory.
|It should now work!
|
|
|-- 2. This method is much, much easier. Download the file [HERE].
Then, open the EBOOT using the program (Requires Java), and type in the appropriate name for the application. If the file is K-xploit'ed (Two folders, one with a % symbol), open the EBOOT in the folder with the %. Then, press "Fix EBOOT". Done!

Both methods work great, but the second one is easier.

Post back if you're still having trouble.

__________________

jeeez there is soooo many problems with the 2.71 se firmwares... JUST DOWNGRADE BACK TO 1.5!

__________________

Ha! I would like to see some valid evidence to support that. In what way(s) are there disadvantages to SE? What are the problems?

__________________

ummm homebrew probably can't run for him because he in se-a it automatically sets the kernel 1.50 folder to game150 and he's probably running it from game u should just update to se-b3 and then set the kernel 1.50 folder to game not game150 and wtf are u talking about se has many problems name one its just ppl don't spend the time and actually try to read stuff before hand and the "add-ons" for 1.50 are VERY n00b friendly thats y its easier for ppl to get things done the first time on a 1.50

__________________

it sound like his homebrew is in the game folder i had the same problem when i swapped my 1.5 and my 2.71se-b memsticks

and as for so many problems with 2.71SE Bullsh*t i've had no problems with it so far it loads a lot faster than devhooking 2.71 the xmb is quicker (in flash memory) and there's an advanced recovery menu to fix semibricks and allow autorunning eboots, umd/no-umd mode.
most se problems are user related all that hasn't worked for me is what was stated the iso emulation programs and with 2.71se-b you dont need them any way.
just cuz it didn't work for you don't try to bring its reputation down.

__________________