PSP 1001 PHAT (IC1003) 6.60 PRO C2 has messed up buttons ingame (on mem stick), UMD's work fine.
GoogleCodeExporter opened this issue · comments
Google Code Exporter commented
What steps will reproduce the problem?
1. Install CFW on PSP 1001
2. Boot up installed game from mem stick
3. Test out the buttons
What is the expected output? What do you see instead?
It should work, but for me the buttons do not work. It is not a hardware issue
because UMD's work fine with no control issues.
What version of the product are you using? On what operating system?
PSP 1001 PHAT (IC1003) 6.60 PRO C2
Please provide any additional information below.
I tried re installing and flashing to no avail . I also tried older software
but still, the in-game keys do not work. I can however exit the game by
selecting the home button, there, the keys are fine. But all input is jammed
in-game. In the PSP home menu I cannot access the recovery menu via the select
button, I also cannot use the "hold R while booting" trick either. I have
tested this on 2 CFW enabled games and in both I cannot use my buttons. For
diagnostic purposes I tried the "key cleaner" and "P-tester" tools (their
controls seemed to work fine "in-game") and found that all keys were
functional. And of-course I did the usual formats and removed the battery for
24 hours and also resetting all settings to default. It was suggested via
online forums that I access the recovery menu (but I can't) and disable the VSH
menu. And no, the psp was not on "hold" the whole time. I am baffled. I am
tired. Please help.
Original issue reported on code.google.com by wahidsha...@gmail.com
on 26 May 2013 at 2:21
Google Code Exporter commented
Oh and I just checked OFW and CFW browser controls, every single control is
fine. So according to "key cleaner" and my hardware tests, everything is 100
percent working. So we can rule that out.
Original comment by wahidsha...@gmail.com
on 26 May 2013 at 2:31
Google Code Exporter commented
Start from disabling all plugins or deleting the seplugins folder.
Original comment by piotrekhenry
on 28 May 2013 at 6:13
Google Code Exporter commented
Solved. Turns out it was the ISO itself.
Original comment by wahidsha...@gmail.com
on 5 Jun 2013 at 11:01
Google Code Exporter commented
"Solved. Turns out it was the ISO itself."
Original comment by devnonam...@gmail.com
on 25 Aug 2013 at 2:16
- Changed state: Invalid