Oh Crap....

**Mr. Shizzy** · August 10th, 2006, 12:30

Originally Posted by NoQuarter

edit the part that says boot on holding x to a program you have in the games folder to see if it will boot on startup when you hold x.Also when it autoboots into devhook does it auto start the emulated firmware or does it give you the devhook menu?

ok , it didn't work. Ill be later. Jmann is gonna help me on IM. Thanks to all!!!

**NoQuarter** · August 10th, 2006, 12:34

.Crap, WHATEVER YOU DO DON"T put # in front of devhook autoboot that's the only way your using usb mode.definitly need to try
ex: devhook = "ms0:/PSP/GAME/IRSHELL/EBOOT.PBP";
just make sure the name of the non percent folder of IRSHELL is the same as in the path of the devhook command.
you need xflash on your memstick,the reason for this is that IR shell has usb mode.since IR shell can launch devboot.pbp I'm guessing the devhook autolauncher in config can launch any eboot.pbp.if you can make it to IRSHELL then launch xflash for the version spoofing to 1.00 so you can launch 1.50 update.
or do a 2.0 update then downgrade back to 1.5
or try to remove custom firmware with xflash
just make sure you autoboot into something that has usb capability

OK I just did some experimenting and yes I think the devhook command in config can be used to launch eboot.pbp.
The reasoning behind this: I changed my autoboot command in dark alex's firmware to point to ms0:/PSP/SYSTEM/DEVBOOT.PBP and custom firmware auto launched my 2.71 firmware!

So the devhook command and autoboot command have the same function
with the exception that the devhook command activates when the wlan switch is off.

Make sure quotes and everything is in the right place I mean perfect you only get one shot since you could lose usb ability if anything is screwed up

**Mr. Shizzy** · August 11th, 2006, 02:05

i figured out what i did wrong. I'm just not sure if it can be fixed. I made 2 mistakes....(I found these excerpts in a FAQ)

MISTAKE 1:

"To ALL 2.5/2.6 downgraders: It apears that the dumped firmware that is used for the 2.5/2.6 downgrade can cause some trouble with the installation of Custom Firmware. I recomend that any 2.5/2.6 downgraded PSP be updated to 2.0 and then back down to 1.5 with the 2.0 -> 1.5 MPH Downgrader. This give the PSP a clean 1.5 firmware for the Custom Firmware to flash too."

I broke that rule. Then there were 2 fixes offered. but niether will work b/c i flashed over the custom firmware w/o removing it first.Here was the other excerpt:

Recovery of a PSP

Flashing your PSP always comes with a certain risk, whether is be a font/gameboot/backround or even the initial custom firmware. This section is to help you recover from a bad flash or a partial-bricked PSP.

The most common error after a custom firmware flash is the "file size of vshmain_real.prx does not match", this is simply because the flasher homebrew did not work once it was flashed. There is no need to get upset, as it can be easily fixed....well most of the time.

Option #1:
Restart your PSP with the HOLD Switch Down (ON), you will be taken you to the recovery mode of the custom firmware.

Go to -> Recovery Menu
-> Remove Custom Firmware

This will remove the custom firmware. Restart your PSP, Go to Step 2 if you want to try installing it again.

DO NOT FLASH OVER CUSTOM FIRMWARE, REMOVE IT FIRST.

Option #2:
If you cannot enter Recovery Mode and it only boots to 1.5, you must use a 2.0 eboot update and place it on your memory stick @ ms0:/PSP/GAME/UPDATE/. Run the Update. Once finished you will then need to use the 2.0 -> 1.5 MPH Downgrader.

Now you can try and re-install the custom firmware.

Bricked PSP from a bad font/gameboot/backround
Another way to partially-brick your PSP is by flashing a bad font/gameboot/backround via x-flash, PSPersonalize...etc.

"First Enter Recovery Mode by HOLD Switch Down (ON) on boot. From there enter USB Mode andf copy the index.dat [Download] that came with your custom firmware to root (ms0:/). Download the 1.5 eboot update and place it on your memory stick @ ms0:/PSP/GAME/UPDATE/. Exit USB mode."

With niether one of these work arounds possible , im stuck. Anyone have any ideas????

**DPyro** · August 11th, 2006, 02:17

If you can still use Devhook, try emulating a 1.50 firmware and updating your firmware to 2.00.

EDIT: Actually, if you can still run Devhook try placing a 2.00 update eboot in the Devhook folder and see if that works.

**Mr. Shizzy** · August 11th, 2006, 02:24

Originally Posted by $n!pR

If you can still use Devhook, try emulating a 1.50 firmware and updating your firmware to 2.00.

EDIT: Actually, if you can still run Devhook try placing a 2.00 update eboot in the Devhook folder and see if that works.

In wih devhook folder? the one on the root of the memory stick? Or one of the ones in the GAME folder? Thanks in advance for the info.

**DPyro** · August 11th, 2006, 02:28

Well, the folder the custom firmware points to to autolaunch Devhook. Also, you may want to use a different memstick in case it doesnt work, so then you can still access the usb and Devhook etc.

**DPyro** · August 11th, 2006, 02:29

OR, you can set the cfg file so that X launches the update eboot.

# Set this to the application you want to start when holding X on boot (add # to remove)
autoboot = "ms0:/PSP/GAME/UPDATE/EBOOT.PBP";

**Mr. Shizzy** · August 11th, 2006, 02:33

Originally Posted by $n!pR

OR, you can set the cfg file so that X launches the update eboot.

# Set this to the application you want to start when holding X on boot (add # to remove)
autoboot = "ms0:/PSP/GAME/UPDATE/EBOOT.PBP";

The first trick you suggested may work. Unfortunatly I tried the second, and the psp seemd unable to update. (But it will launch anything else that way) Strange...