MechaPwn by MechaResearch

PS2 MechaPwn by MechaResearch 2.00

It's because you didn't restore the nvram before running mechapawn 3.0 You said that you changed the model name to DTL that means you are using buggy mechapawn 2.0, so you should restore the nvram and reinstall 3.0 version
 
ciao ragazzi, ho uno scph 90004 con fremcboot e mechapwn 3.0 rc4. Ho aggiornato mechapwn senza prima ripristinare nvm.bin. Purtroppo vorrei ripristinare il nvm.bin originale ma non riesco più a trovarlo. Sapete se c'è qualche soluzione? o qualcuno che pubblicherebbe il proprio

hi guys, I have a scph 90004 with fremcboot and mechapwn 3.0 rc4. I updated mechapwn without first restoring nvm.bin. Unfortunately I would like to restore the original nvm.bin but I can no longer find it. Do you know if there is any solution? or someone who would publish their own
 
Last edited by a moderator:
ciao ragazzi, ho uno scph 90004 con fremcboot e mechapwn 3.0 rc4. Ho aggiornato mechapwn senza prima ripristinare nvm.bin. Purtroppo vorrei ripristinare il nvm.bin originale ma non riesco più a trovarlo. Sapete se c'è qualche soluzione? o qualcuno che pubblicherebbe il proprio

hi guys, I have a scph 90004 with fremcboot and mechapwn 3.0 rc4. I updated mechapwn without first restoring nvm.bin. Unfortunately I would like to restore the original nvm.bin but I can no longer find it. Do you know if there is any solution? or someone who would publish their own

This is from my PS2 SCPH-90004 PAl. Hope that helps.
https://file.io/joiK9szVD2vP
 
This is from my PS2 SCPH-90004 PAl. Hope that helps.
https://file.io/joiK9szVD2vP
I loaded the lokker backup and the ps2 works, the serial number changed when I check via mechapwn but the ps2 logo once recognized the disc became clear and readable again :D.
The problem remains that sometimes it struggles to read the original discs but by opening and closing the drawer it reads them without problems... I don't understand whyIs the backup you gave me original.
your backup was untouched by mechapwn?
 
Hi, MechaPWN 3.0 RC4 is still forcing NTSC video mode on PAL Deckard systems (tested on my SCPH-79003, no version of MechaPWN was installed on it prior to this) when selecting 'Europe' from the Patch Menu.

The OSDYS runs at 60hz, PAL PS1 games run at 60hz and are cropped off at the bottom, PAL PS2 games will show a corrupt Playstation 2 logo upon startup.

I believe this was expected in RC3 and earlier, but reportedly changed in RC4:
  • Fixed PAL/NTSC video mode change, now it is changing only on Deckard according to the selected region
 
Hi, MechaPWN 3.0 RC4 is still forcing NTSC video mode on PAL Deckard systems (tested on my SCPH-79003, no version of MechaPWN was installed on it prior to this) when selecting 'Europe' from the Patch Menu.

The OSDYS runs at 60hz, PAL PS1 games run at 60hz and are cropped off at the bottom, PAL PS2 games will show a corrupt Playstation 2 logo upon startup.

I believe this was expected in RC3 and earlier, but reportedly changed in RC4:
  • Fixed PAL/NTSC video mode change, now it is changing only on Deckard according to the selected region
use latest dev build instead.
 
I restored the NVRAM backup using RC4, then proceeded to install the dev build - MechaPwn-02e7cd1a.
After that, with the Europe region selected it still behaves the same way as RC4, OSDYS and PAL PS1 content is at 60hz etc.
this is strange. Are you 100% sure that you dont have the modchip?
 
this is strange. Are you 100% sure that you dont have the modchip?
100% sure, I did a full teardown of this console when I bought it in order to clean it, no modchip was found inside. The waranty sticker was untouched as well, so it shouldn't have been opened before.
Without MechaPWN installed, it runs at the expected 50hz, doesn't play import games either (tested with NTSC-J PS1 games)
 
I'm from Spain and I have a PAL console, and if it runs at 60 Hz, I don't have a chip, I had to go back to a minor compilation, but the minor ones don't run NTSC games, what fixes it on the PAL rc4 is to enter GSM and change to PAL and the pal games run as they should, my idea was to install the latest version with ntsc compatibility and run the 4 ntsc games that I have with gsm in ntsc mode and that fixes the screen issue, I hope they fix it, I have seen a compilation from two weeks ago, I guess it won't go well, right? Sorry for the translation.
 
I have the same issue with my SCPH-77003 (Europe) which si Deckard obviously...
I will try to explain it best as I can, I tried both RC4 and newest Developer build and they act the same.
After using RETAIL-DEX (doesn't matter which region I select), it behaves like this:

-it starts to use American version of FreeMCboot instead of European (I can tell by deleting "history" file)
-If I left OSDSYS video mode to AUTO, it outputs 480i
-all PS1 games runs in 240p 60Hz - even PAL ones, which will basically break them, some portion of image is not rendered and the run too fast
-PAL PS2 games run correctly at 576i 50Hz, PlayStation 2 logo on original discs is crippled however
-When running PS2 games trough OPL with "Show PlayStation 2 logo" enabled, logo shows when booting NTSC titles and doesn't show when booting PAL games (without MechaPWN, it's exactly the opposite)

Like I said, it always does this when using RETAIL-DEX option, doesn't matter which one I select, even when I use Europe or Russia option, it's still being switched to NTSC region.
Not a biggie though, all my PSX backup discs are NTSC versions, and PS2 games are not really affected by this issue, but there still seems to be and issue with regions on DECKARD consoles.
 
@Vapno92
There are 2 ways on Deckard:
- use any PAL region. In that case all burned PAL PS1/PS2 games will run smoothly, all NTSC titles will not boot. I mean NTSC will not boot completely, regardless if they are burned/original.
- use NTSC-U region. In that case all burned NTSC PS1/PS2 games will run smoothly, all PAL games will have issues with video mode, PS2Logo, etc.

So it was decided to forcefully switch after mechapawning into second way. The reason is easy - it will allow to boot any region disks in that case.

All those problems with video modes - everything can be solved by using 3rd party launchers. It will not be as easy as just put-n-run, but it will solve most of that problems. For example using DKWDRV, it is designed for PS1 titles, but also can be used with PS2 titles in a limited way.
 
i really couldn't find ps1vmodeneg ver.1.01 on any website
could anyone be kind and please help i only can find the v1.10

i really messed up and installed force unlock using the latest mechapwn
and i lost my nvmr backup file...
is there a way to Uninstall force unlock help :(
 
Last edited by a moderator:
Does the content of NVM file change by some user actions? I found 2 backups of my NVM, which are different by 2 bytes in the config 1 (OSD (User data)) area (specifically on addresses 2C0 and 2CF). Is this normal or is has been changed by MechaPwn?

EDIT: Sorry, I was blind, I found it :facepalm: It seems, that it was changed by user settings, most likely enabling/disabling SPDIF or RGB/YPbPr settings or something like that.
 
Last edited:
Hi there.
Is MechaPWN compatible with FHDB installed in another ps2 unit? Or it gonna break it? I have installed FHDB 1.966 on internal ssd drive on my NTSC/U PS2 and now i own a Japanese 55000GT, and i want to know if anything can break patching it with CEX option in MechaPAW. I wish to play NTSC/U original discs and use OPL autoboot to play internal SSD games.
Thanks!
 
Last edited:
Hi there.
Is MechaPWN compatible with FHDB installed in another ps2 unit? Or it gonna break it? I have installed FHDB 1.996 on internal ssd drive on my NTSC/U PS2 and now i own a Japanese 55000GT, and i want to know if anything can break patching it with CEX option in MechaPAW. I wish to play NTSC/U original discs and use OPL autoboot to play internal SSD games.
Thanks!
You should be fine. If anything goes wrong you can always revert back to original firmware.
 
Last edited:

Similar threads

Back
Top