Expert advice on swapping PSP200x mobo

[idog]

Hi,

For a customer who had dropped his PSP 200x (datecode 7C), screen broken, case cracked, umd reader bent and who had bought another PSP 200x (datecode 8C, ofw 6.00) I have performed a mainboard swap at his request.

That way he could have a vulnerable board in a working PSP again

Anyway, the transplant (7C board into the working psp) went smoothly, but now the odd behavior :

- no sound when turned on. When I put the PSP in standby and on again, XMB does work with sound. When I start a game, no sound anymore.
- UMD reader doesn't work.

I have verified the cable connections and checked for continuity, all checked out.

What am I missing here ? A one on one swap of the mobo is not all there is to it ? Do I need the swap more components over, and if so, which ? (the umd reader of the fallen psp is broken beyond repair )

I have read some posts about voltage issues, but I'm placing an older board (supposedly more power than needed) into a psp with newer components (requiring less current ? ), so a lack of power shouldn't be the case (although the umd reader seems to be dead completely (not enough power ??).

Any advice is greatly appreciated !

Thanks

[MaxMouseDLL]

Try using DC8 to completely kill the NAND and then rebuild the IDStorage keys and install 5.00M33-6, that may fix your UMD issue, as for your weird sound issue, I'm not sure if that'll help, but it's possible, give it a try.

MAKE A BACKUP FIRST!

[idog]

Thanks.

It seems the sound issue is due to the daughterboard (wlan) is also needed.

As for the idstorage stuff, there's probably an easy tut somewhere on how to backup the nand and clearing it. Will look for it and report back

Am I correct in understanding that rebuilding the idstorage keys involves querying the component id's (memstick reader, umd reader) ? If so, isn't it strange that the memstick reader works without problems ?

[MaxMouseDLL]

Thanks.

It seems the sound issue is due to the daughterboard (wlan) is also needed.

As for the idstorage stuff, there's probably an easy tut somewhere on how to backup the nand and clearing it. Will look for it and report back

Am I correct in understanding that rebuilding the idstorage keys involves querying the component id's (memstick reader, umd reader) ? If so, isn't it strange that the memstick reader works without problems ?

Just use DC8, it'll do backups and IDS rebuilds... the memory stick reader should always work and require no authentication, it's Sony's method of repair too

[idog]

Just use DC8, it'll do backups and IDS rebuilds... the memory stick reader should always work and require no authentication, it's Sony's method of repair too

Ok, not much luck so far.

Replaced the wlan component, still the same problem (sound only when recovering from standby).

Nand backup done (1 bad block : 3860 if I recall correctly).
Format lflash done
5.00M33-6 reflashed.
Restarted the PSP and the blue screen (press O to restore default settings in multiple languages) came up. Pressed O and the screen faded away (just like the screen went bad) and after a few seconds the PSP turned off.
Turned it on again and the blue screen was there again. This goes on and on

Restored the NAND and we're back to square one.

I'm open to suggestions...

[MaxMouseDLL]

I'm still convinced the key to the UMD is the IDS, the IDS will also need to be adjusted for the WLAN board, and it's possible you'll have some screen brightness issues... I can't shed any light on the sound issue though sorry...

Keep trying with IDS stuff, especially DC8 and regenerating it, you have a NAND backup now, so it doesn't really matter what you do, you can always revert.

[idog]

Ok, not much luck so far.

Replaced the wlan component, still the same problem (sound only when recovering from standby).

Nand backup done (1 bad block : 3860 if I recall correctly).
Format lflash done
5.00M33-6 reflashed.
Restarted the PSP and the blue screen (press O to restore default settings in multiple languages) came up. Pressed O and the screen faded away (just like the screen went bad) and after a few seconds the PSP turned off.
Turned it on again and the blue screen was there again. This goes on and on

Restored the NAND and we're back to square one.

I'm open to suggestions...

Just found something out. I can't start the 5.50 GEN-D3 application when I have no sound (just wanted to try to see what a reflash of 5.50GEN-D would do.. ). When I do the standby trick I can start it, but if I don't I just get a black screen (fade like above) and the PSP turns off after a few seconds.

Maybe the fall hurt more than I first anticipated ? So far I have replaced mobo, wlan and power board, all to no avail....

edit : putting it in standby is a fix for (almost) anything. I can even play games on the memstick this way. Just put it in standby and back on in XMB, I can start the game. I then have no sound in the game, standby and back on and I can play with sound. It is not ideal (by far) and this doesn't bring UMD back to life ( I have regenerated the IDStorage numerous times now, not helping..), but it might be acceptable to the customer (for whom I doing this as a favour )

[MaxMouseDLL]

Very weird, Sorry I can't be of more help, i think the "Just keep messing around with it" option is probably best... if you get anywhere come back and explain.

[idog]

Very weird, Sorry I can't be of more help, i think the "Just keep messing around with it" option is probably best... if you get anywhere come back and explain.

No problem, thank you very much for your help ! I've learnt a thing or two thanks to your replies so no need to apologize

Should I one day learn the exact reason and solution for this particular problem, you can expect me to report