[OFFICIAL] 3.40 OE-A and 3.03 OE-C Installation Guide, FAQ, and Support Thread

[InhumanElmo]

They are in the readme. To check them get a program like fast sum for the md5, the SHA1 is checked by the update maker, and the crc32 sum can be checked with a program found at this Link
The SHA256 I haven't been able to check.

[NeilR]

Wait. I have 3.03 OE-A, do I have to use the psp/game150 folder or do I use the normal psp/game folder. I have the thing set to 1.50 kernel.

If you're talking about upgrading, it is advised to use the GAME150 folder even though you have the GAME folder set to use 1.50 kernel..

And for the people who ignore documentation:

Spoiler for Checksums of the generated file:

CRC32: 27A38F3A
MD5: 95C84F1F20643FB29E5F7DFFF 6D04291
SHA1: E4CE6EB16F90F0F6670710854 16C10B0BEA7CC22
SHA256: 1C72C1BE3C7E03E56F127AF36 5B8AA0B6C8C7A70BFF30E2770 C222E28D1CBBFE

[InhumanElmo]

Yes I am talking about upgrading. Ill go through with it once i check the SHA256 hash.

[so_swish]

Cintro[flashless v.] & the GBpath modifider arent works ?

what 2 do

[Kwiksta]

Hey all!

Would I be able to use the DATA.DXAR I used when I upgraded to 3.03 OE-B?

Thanks!

Kwiksta

[PSPduh]

Hey all!

Would I be able to use the DATA.DXAR I used when I upgraded to 3.03 OE-B?

Thanks!

Kwiksta

No because then you would have 3.03 OE-B.
Generate the 3.03 OE-C data.dxar, all the data.dxar's aren't the same.

[nights]

Cintro[flashless v.] & the GBpath modifider arent works ?

what 2 do

Um Cintro the flashless version works for me on 3.03 OE-C.

[Adiuvo]

I thought there were some autoboot running problems?

[Synye]

Anyone else taking so long for it to extract and pack the 3.03 fireware? Running for like 10 mins so far and its not frozen.
EDIT: Finished.

[Adiuvo]

Ir's probably your memory stick that causes the problems BTW.

[TeamOverload]

This thread should come in handy shortly. I better start reading up on this now to get prepared.

[Scorned]

Well im just curious because its taking a really long time. But is the DATA.DXAR File supposed to take so much time? Its been, "Extracting and packing 3.03 firmware..." for a while now and im starting to get a little nervous...

[nights]

I haven't had any problems with the CIntro flashless autoboot version. I don't know maybe I am just special lol.

[InhumanElmo]

Do you know something we don't, because it doesn't work for me.

[miltonap]

I was wondering if I should update to 3.03 OE-B first then to OE-C. Or can I do it directly right now from OE-A2. I want to be safe so thats why Im asking

[nights]

Milton you can do it from either.

[clouducla7]

be safe and just upgrade in order. as for the data. taking forever, mine did too ( about an hour and a half for 3.02a and about two hours for 3.03oec) and all went well.

[InhumanElmo]

^Wow. Thats an extremely long time. I get mine done it like... a couple of minutes. It takes me no more than 15 minutes to upgrade a 3.03 OE firmware.

[Adiuvo]

The time does not matter. It varies greatly on all PSP's.

[gamecraver]

Tried to install but during the extraction and packing, it gave me error.

First, when I tried to install the 3.03OE C installer, it prompt me to make sure my batt is 75% , then it book to the main screen. (tried twice and same result)

I del off and re do the extraction again, 303Eboot give me error so I re copy paste that. Then suddenly 150 Eboot gave me error. Aint sure whats going on. Anyone? Now I re download the stuff and try again.


I re d/l, I run the oeupdmaker, no use.. error is what i kept seeing

[hollywood_8]

Hi first time poster here , My friend who usually helps me upgrade my psp . But now doing this update by myself

PSP is in 3.03 oe-B , it was pretty easy to do ..

I did all what it said in the instructions but mine froze up before the little pink txt showed up .

> Copied the oeupmaker and oepmaker% to the game150 folder .
> pasted the 150.PBP and the 303.PBP in the oeupmaker folder . ran the thing , and what I got was was a 0Kb DATA.DXAR file

> Pasted the 303oeflasher and 303flasher% in the game 150 folder
> Now I moved (cut) the DATA.DXAR file to the 303oeflasher folder then ran it .
PSP screen loads up but crashed before any pink text showed ..

It was scary , it's a good thing my PSP is still working after that ..


EDIT :
I don't know what I did wrong but it could be that :
1 . no UMD inserted , I did removed my UMD before running the 3.03 oec update . but in my recovery program my , no UMD is disabled .
2. Or I got a 0kb DATA.DXAR file .. how many kb's it supposed to have anyway ?



What did I do wrong ? pls help ..

[gamecraver]

Hi first time poster here , My friend who usually helps me upgrade my psp . But now doing this update by myself

PSP is in 3.03 oe-B , it was pretty easy to do ..

I did all what it said in the instructions but mine froze up before the little pink txt showed up .

> Copied the oeupmaker and oepmaker% to the game150 folder .
> pasted the 150.PBP and the 303.PBP in the oeupmaker folder . ran the thing , and what I got was was a 0Kb DATA.DXAR file

> pasted the 303oeflasher and 303flasher% in the game 150 folder

> Now I moved (cut) the DATA.DXAR file to the 303oeflasher folder then ran it .
PSP screen loads up but crashed before any pink text showed ..

It was scary , it's a good thing my PSP is still working after that ..

What did I do wrong ? pls help ..

Maybe you can try to reload it and run it over again. Mine got a error, dun understand why.

[InhumanElmo]

Your DATA.DXAR file is supposed to be 17.5 megs. Can you reach the xmb or the recovery menu?

[TheXxBestxX]

also make sure the checksum is same with the provided in the readme.

[sphinx13]

It doesn't work for me. I have done this before, so I know what I am doing, but when I tried to run the oeupdatemaker i get 8002014c error, so I just used the data.dxar from my 303oe original flash, and when I try to run it, I get the same error.

[InhumanElmo]

NEVER USE YOUR OLD DXAR!!! It doesn't make sense to. Yes the hashes need to be correct. Just a question. Would anyone be interested in an all in one OE-C checksum checker? I have one, but I don't want to release it because I used external programs.

[sphinx13]

Why not? Isn't it just 150 and 303 combined into one file? Someone told me the data.dxar you use for 3.03oe-a will work with 3.03oe-c.

[NeilR]

Why not? Isn't it just 150 and 303 combined into one file? Someone told me the data.dxar you use for 3.03oe-a will work with 3.03oe-c.

Someone is trying to convince you to brick your PSP. The oeupdatemaker packs the content from 1.50 and 3.03 in different ways with each OE firmware revision. An old dxar is completely incompatible and the flasher program expects it to be one made with the matching updatemaker.

[sphinx13]

Well do you know what my problem is? It gives me 8002014C error, and I can't figure out what it means.

[Henkibojj]

Hi!

I don't often roam these forums, but once I do, I dump a lot of questions. This is no exception. It might seem offtopic, but it kinda is related to OE-B... I hope.

I was trying to install this XMB rebooter-prx. Firstly, I checked if it worked by running it through recovery mode. It worked, but it restarted the PSP over and over :) No panic though, just hold R to disable it.

Then, I read that you should use uFlash to flash the prx and replace the original one (which I backuped with FA). So, I installed uFlash and screwed up because wasn't any readme in it Now I've accidently deleted three icons: Online Instruction Manuals, Remote Play and Certificate Utility (whatever that one is, does it have something to do with the PS3?), and of course nothing has happened when I select "Reset" the icons in uFlash. I might have changed other things as well...

Questions: How do I get the icons back? If I accidently changed something else, how do I reset it? Do I have to reinstall OE-B from 1.5, or with a recovery-EBOOT?

I should have used the "with-installer" one instead, if I saw it from the beginning. I found the prx via pspupdates, and not dl.qj.net. Now that I've found the installer, that's not gonna be any problem. I'd love some help for how to undo my stupid mistake. :)