Official PSP 3.03 OE-C And Compatibility thread! - Page 5 - PS3 NEWS

**PSPSwampy** · 01-27-2007

Quote:

Originally Posted by getfunky

Thanks for the guide PSPSwampy!

No worries mate, thanks for the thanks, but please use the

button to show your appreciation rather than post a 'thank-you' message.

Thanks

P.s. Thanks to everyone who's given me a

for my tutorials etc so far

**thpek** · 01-27-2007

Well, mine is bricked and it's a non TA-082. It's just my luck and I have already read up many entries to revert back but it ain't working. Nonetheless, thanks for all the help. Lesson learnt but painfully

**naturesbane** · 01-28-2007

thpek: Did you brick the PSP installing the USB mod? or was it bricked doing something else?

What model PSP?

**naturesbane** · 01-28-2007

re: PSPSwampy's guide to installing a USB plugin on 3.03 OE-C

Works great thanks!

Note to others: remember to go into save games and return to memory stick after changing modes.

**Frameskip** · 01-28-2007

Quote:

Originally Posted by delirumhappy

Does GTA:VCS iso work NO-UMD?

Is there a way to get it to run w/o no-UMD? I can't get it to load at all...

**juan2320** · 01-28-2007

Did you try to turn off no-UMD and put a UMD in your psp drive?
or you can try to enable the Plain Modules in the recovery menu.

**badmofo** · 01-28-2007

So I have an excellent reason for recovering your unit back to original 1.50 firmware - clearing the flash0 and flash1 from any tweaking and updating you might have done previously with devhook or button swapping, gameboot files, etc.

Here is my scenerio: I have an original Japanese 1.50 PSP, never updated or downgraded. I messed with the flash though doing the button swap hack, flashing devhook files, flashing gameboots, and possibly other things I don't know about. Anyway, was ready to update to custom firmware 3.03 oe-c, so I uninstalled the flash files from the devhook using devhook and went to it. I followed all the directions and everything went smoothly, I ended with a 3.03 oe-c unit. I thought I was good.

But then I tried setting up a wireless infrastructure internet connection. Kept giving me some kind of internal error when I tried to save my settings. Ad hoc seemed to work fine, but not infrastructure, I couldn't save the settings.

So I tried a couple more times just re-making and re-flashing the custom firmware, still no luck. So I guessed something was messed up with the flash, and aside from having a program to clean the flash (both 0 and 1), I decided to clean install with original firmware 1.50 and then re-upgrade to 3.03 oe-c.

After the recovery to 1.50 my wireless connection worked again. And after my upgrade to 3.03 oe-c in continued to work, wahoo!!!!

So I guess it is a good idea to somehow clean the flash before upgrading. Not sure if there's another method, but this way worked for me!!!! :grin:

Hope this is helpful, take it easy. :tupbig2

**jrombart** · 01-28-2007

Quote:

Originally Posted by PSPSwampy

It doesn't matter where you upgrade from - this is a full installation package.
(As long as it's v1.5, or one of Dark_Alex's previous releases

)

My understanding on this is that you MUST use the files provided in this release (along with the 1.50 / 3.03 eboot's) to create a new DXAR on EVERY PSP this is because
1. The DXAR created is (presumably) specific to this custom firmware (ie you can't use a DXAR you created with the last version).
2. The DXAR has some kind of encoding in it that relate to YOUR PSP and ONLY YOURS, so anyone elses won't work for you.
3. If you're going to attempt it, best doing it the correct way, other wise you risk a BRICK

PSPSwampy.

Although I agree with most everything you say, I must disagree with the requirement that one must create the DXAR file for every PSP. I doubt the 3.03 OE-C DXAR file is specific to each PSP because the DXAR file for 3.03 OE-C has an exact file signature that you can check from Dark Alex's readme.

Once you have saved this file cleanly into your hard disk after creating it for the first time using the Update Maker for OE-C, you can use this DXAR file on multiple PSP's without recreating it. As Dark Alex said, you can skip this step in the future, but you have to do it again probably if a new custom firmware by Dark Alex will require a new different DXAR.

I think when one actually flashes the DXAR into the PSP unit, that's the only time it starts to flash something uniquely related to that particular unit.

**bp499** · 01-28-2007

Just upgrded to OE-C following PSPSwampy's excellent guide!

Thanks a million to Dark_Alex for such a nice piece of coding!

**PSPSwampy** · 01-28-2007

Quote:

Originally Posted by jrombart

Although I agree with most everything you say, I must disagree with the requirement that one must create the DXAR file for every PSP. I doubt the 3.03 OE-C DXAR file is specific to each PSP because the DXAR file for 3.03 OE-C has an exact file signature that you can check from Dark Alex's readme.

Once you have saved this file cleanly into your hard disk after creating it for the first time using the Update Maker for OE-C, you can use this DXAR file on multiple PSP's without recreating it. As Dark Alex said, you can skip this step in the future, but you have to do it again probably if a new custom firmware by Dark Alex will require a new different DXAR.

I think when one actually flashes the DXAR into the PSP unit, that's the only time it starts to flash something uniquely related to that particular unit.

Good point about the checksum!