psplockv2 and v2.1, when set to manual input, bricks psp

I have psplockv2.1 on my 3.03oe-c (and i tried this on 3.51 m33 and the same thing happend) all the files are in the right place named correctly and the text in the file is also correct so when i set it to manual input 010 i start it up, it asks me for the code and i enter it and it sais psp unlocked and it takes like 4 seconds and starts up with the (im using the default theme) sony computer entertainment and the after the wave is done wiggling the screen fades to black and freezes.is there a fix or something for this? I used a cxmb plugin v1.2 and v1.1 seperatly (these you just put on your memory card not the flash0 or 1) and it didn't freeze the first time i entered the password and worked but if i reset my psp it would freeze again and id have to disable and enable the plugin in recovery mode for it to work again (ive used the cxmb with and without the psplock and same reaction) and also the cxmb plugin would also freeze the psp when i tried to play any games,homebrew,ect. and when i took the cxmb off my memory card my psp would go to the blue screen and then restart and blue screen again so id go back to fw1.5 then back to 3.03oe-c.
There are three options with psplock: make it so you have to type a password before it starts up 110 or 010, text output 100, and disable 001 and what your supposed to do is rename vshmain.prx to vshmain_real.prx and put in the new vshmain.prx from the downloaded psplock file.

[ace]

What exactly does that program do? And does it always do that on your psp? Sounds like The wrong top_menu was flashed or something along those lines.

@ace... its like a password protection type of program for your psp.

@scochivonricter... i know that program (or one similar) is pretty old, so do you know if its even compatible with 3.03 oe-c? Because if your editing the vshmain.prx (or any other files) then your going to need one thats compatible with your firmware otherwise it will semi brick your psp. I'll look into it for you though some time within the next day or two.

*Edit*

You followed all the instructions to a T and its still messing up you say...

Instructions:
Access flash0, and rename vshmain.prx to vshmain_real.prx

Paste the vshmain.prx included

Access flash1, add a file called lock.lock, and type in 5 digits for a passcode

Add a file called config.lock in the root of the root of flash1 (This isn't required, if its not found then it
simply defaults to 000

Access ms0, add a file called lock.lock, and again type in the same 5 digits for the un-locker


Do you have any other plugins running?

i disabled all the other plugins and followed the instructions 1by1. but i upgraded to 3.40oe-a and now it works but it would still be nice to know a way to fix that for 3.03oe-c and 3.51 m33 unless i should just wait for the next version