UMDs wont run (3.03 OE-A')

My mate just phoned me and said that for some weird reason his UMDs wont run on his PSP anymore. I recently updated his PSP to 3.03 OE-A' and everything was fine, UMDs and PS1 games worked a charm. Now UMDs dont work.
NO-UMD Mode is currently disabled, so that cant be the problem.
Any help would be great.
btw, the UMDs he's trying to run are Virtua Tennis and Fired Up,
Also, if we cant resolve the problem, is it possible to re-flash 3.03 OE-A without downgrading again?

Edit - Would it maybe be something to do with overclocking? I set his PSP 266 while playing a backup of Medal of Honor.

Maybe his UMD drive has gone

it cant be the problem because Devhook still runs his UMDs perfect. Dont know what to do here. What about recovery mode?

EDIT - Im just gonna try recovery mode when the charge is up to 75%. Anyone who has any information beforehand would be much appreciated.

It is either the overclocking or if that dosn't work reflash 3.02 OE-A straight from the XMB, no need for recovery to run it, and no need to downgrade, cause I recently reflashed mine to get back the network update, cause I accendentaly permenentaly removed it.

How do I reflash it ?

BTW, I just upgraded it to 3.03 OE-B' to see if it would make a difference. It didnt. Do I just take the normal steps in installing 3.03 OE-A again?

BTW your Sig made us laugh :D

im abit screwed here on what to do, i dont want to reflash it straight away because its my friends psp and i dont wanna f*ck it up. at the minute he is on 3.03 oe-b, he has no recovery folder in game, umds wont work work from xmb but they do work in devhook. whats my best option ?

Try 3.02 OE-A or B.

Quote:

---

Originally Posted by mnuhaily22

cause I recently reflashed mine to get back the network update, cause I accendentaly permenentaly removed it.

---

How did your survive this horrific event of not having network update?

Quote:

---

Originally Posted by scottyboynow

Try 3.02 OE-A or B.

---

and can i simply flash 3.02 OE-A from 3.03 OE-B ?

im still on 3.02 oe because i got a newer version and that exact problem happened.