HOWTO: Update stock emulator in PSClassic

Discussion in 'Other Consoles & Oldies' started by subcon959, Feb 17, 2019.

  1. subcon959
    OP

    subcon959 teh retro

    Member
    13
    Dec 24, 2008
    ** WARNING - WRITING INTERNAL STORAGE ALWAYS CARRIES SOME RISK **
    ** ONLY DO THIS IF YOU ARE WILLING TO TAKE FULL RESPONSIBILITY **

    ** THIS IS NOT A BEGINNERS GUIDE, IT ASSUMES A MEDIUM LEVEL OF PROFICIENCY **

    You will need,

    Bleemsync 1.0: https://github.com/pathartl/BleemSync/releases (+compatible USB stick)
    FTP client: https://filezilla-project.org/download.php?type=client
    Telnet client: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
    A microUSB data cable to power the PSC from your PC USB port.

    Follow the instructions on the Bleemsync site to get through the initial install. We only need this to get telnet and FTP server, so once the installation is successful you can stop following the instructions. We are only concerned with running the PSC stock, so won't actually be using Bleemsync or a USB stick after initial install. However, do grab the updated emulator binary from the Bleemsync 1.0 archive. You will find it at "\bleemsync\etc\bleemsync\SUP\binaries" and the file is simply named "pcsx".

    Remove the USB stick and start the PSC. Everything should be working exactly as stock. Leave it sitting at the menu.

    Provided your microUSB cable supports data, and not just power, you can now access the FTP server running on the PSC through this same USB connection that is powering the console.

    Now fire up the FTP client on your PC. Use the following settings to make a connection:

    HOST: 169.254.215.100
    USERNAME: root
    PORT: 21

    NOTE - no password is required.

    If successful, you should see a directory listing of the internal storage of the PSC. If it doesn't work, then you either didn't get Bleemsync installed properly or you have some other PC issues that are beyond the scope of this guide. You can use this opportunity to make a backup of your PSC files.

    The folder we are interested in is "/usr/sony/bin/" so browse to it and look for the file named "pcsx". It should be around 1MB in size (compared to the updated one from Bleemsync 1.0 which is about 1.5MB). Download a copy of the file and keep it somewhere safe as a backup.

    Now, we can't simply upload/overwrite this file as the partition is set as read-only by default. Go ahead and try and you will just get an error. We need to make it read/write and we do this with telnet.

    Start up your favourite telnet client (putty in this example) and connect to the same host as above, 169.254.215.100, using port 23. The login name is again "root" and no password is needed. You should get a nice welcome screen and command prompt. There are various things you can do here as it is basically a small linux environment, but we are only interested in one command:
    Code:
    mount -o remount rw /
    Press enter and it will appear as if nothing has happened but as long as there was no error then it worked. Be careful from this point as there is nothing stopping you erasing any system file and bricking the device.

    Upload/overwrite the "pcsx" file with the one from Bleemsync 1.0. It should go through without any error this time. Disconnect from FTP. Type "exit" in putty to disconnect the telnet session. Restart the PSC.

    NOTE - You will now have access to the in-game options menu by pressing "SELECT+TRIANGLE". It's important to note that, unlike with previous hacks using a USB stick, now any changes you make will actually be written permanently if you choose either of the SAVE CFG options.
     
    Last edited by subcon959, Feb 17, 2019
    tito83, ksm59, neblyn and 9 others like this.
  2. BL4Z3D247

    BL4Z3D247 GBAtemp Stoner

    Member
    7
    Oct 22, 2008
    United States
    I'm so high, I don't even know!
    Can't believe I missed this!

    Thanks for this, I was going to try and do this myself but now I don't have to.
     
  3. cronus07

    cronus07 Newbie

    Newcomer
    1
    Mar 15, 2009
    United States
    I did this and now my system will not boot any games. I restored the original PCSX and still will not boot any of the internal games.

    EDIT: this is fixed, please see my response/solution further down if you run into the same issue of PCSX not booting.
     
    Last edited by cronus07, Mar 27, 2019
  4. fixingmytoys

    fixingmytoys GBAtemp Advanced Fan

    Member
    5
    Jan 4, 2018
    Australia
    might have a look at this
     
  5. cronus07

    cronus07 Newbie

    Newcomer
    1
    Mar 15, 2009
    United States
    I essentially soft-bricked a PSC doing this. no amount of restoring the original PCSX would allow games to be booted from the stock main menu. It will flash (like it's trying to load PCSX) and then go back to the main menu. It seems like replacing the PCSX sets off some type of security flag (encryption?). There is a "PCSX-kill" file in the same directory, not sure if it has anything to do with it. I am going to have to keep poking at it to see what this did to the console but for now the stock UI is dead because of this. Games will still load via autobleem/bleemsync
     
  6. subcon959
    OP

    subcon959 teh retro

    Member
    13
    Dec 24, 2008
    Not sure how you managed to do that as Ive done this on 7 consoles now without any issues.
     
  7. cronus07

    cronus07 Newbie

    Newcomer
    1
    Mar 15, 2009
    United States
    I'm open to suggestions!
    I connected through Putty and Filezilla fine. did a backup of the PCSX file and everything looked good. The only slight difference is I grabbed the PCSX file from an fresh copy of Bleemsync 1.0 (I then tried bleemsync 1.0.1 with same effect) and overwrote the PCSX. disconnected from ftp and exited putty. powered down PSC, unplugged and rebooted. Games wouldn't load. ok fine, tried to restore the copy I have of PCSX and same deal. No matter what I do, it simply won't boot games from the stock carousal anymore. it'll flash for a second and go back to carousal. Ideas?
     
  8. subcon959
    OP

    subcon959 teh retro

    Member
    13
    Dec 24, 2008
    I really have no idea how you managed it, but there is probably a simple explanation of why it's behaving that way.

    For reference, this is what my folder looks like (maybe look at the "Attrib" column to see if your file permissions are screwed up)

    [​IMG]
     
  9. fixingmytoys

    fixingmytoys GBAtemp Advanced Fan

    Member
    5
    Jan 4, 2018
    Australia
    hi, just quick question or two , i am all ready using Bleemsync , so i still able to do this ?? and it is fine to grab updated emulator binary from the Bleemsync 1.0.1 archive. mind you i can just tell it in bleamsync to use it
     
    Last edited by fixingmytoys, Mar 26, 2019
  10. subcon959
    OP

    subcon959 teh retro

    Member
    13
    Dec 24, 2008
    It doesn't really make sense to do this if you're using BS or whatever as the USB method is going to over-mount this file anyway.
     
    BL4Z3D247 likes this.
  11. BL4Z3D247

    BL4Z3D247 GBAtemp Stoner

    Member
    7
    Oct 22, 2008
    United States
    I'm so high, I don't even know!
    Not to mention they'd be already using the updated stock emulator.

    People, this is if you just want to update the stock emulator and load games without using hacks(BleemSync, AutoBleem, ect.) or a USB drive for playing games. This is if you want to keep it stock but build the game lineup to your linking and use the latest PCSX build.
     
  12. cronus07

    cronus07 Newbie

    Newcomer
    1
    Mar 15, 2009
    United States
    thanks, I'll take a look as soon as I have access to my PSC again later today and give an update.

    FWIW: this was part of the error log so chances are it has to do with permissions:

    Can't open preference file [/data/AppData/sony/ui/user.pre] for loading
    saveMemcardBackup()
    memcard is broken
    saveMemcardBackup()
    memcard is broken execv() : Permission denied execv( [/usr/sony/bin/pcsx] [-lang] [3] [-region] [1] [-enter]
    Could not invoke pcsx : exit status = 1 ​
     
  13. cronus07

    cronus07 Newbie

    Newcomer
    1
    Mar 15, 2009
    United States
    ok, follow-up. It was the permissions which I thought I had updated the first time in filezilla but filezilla was not updating the permissions:

    Command: SITE CHMOD 755 pcsx
    Response: 500 Unknown command
    I ended up editing the permissions in Putty with the following:


    root@bleemsync:~# cd /usr/sony/bin/
    root@bleemsync:/usr/sony/bin# ls -alh

    total 4.2M
    drwxr-xr-x 3 root root 1.0K Sep 1 15:00 .
    drwxr-xr-x 5 root root 1.0K Sep 9 2018 ..
    -rwxr-xr-x 1 root root 16K Sep 9 2018 auto_dimmer
    -rwxr-xr-x 1 root root 1.3K Sep 9 2018 checkcurrentlog.sh
    -rwxr-xr-x 1 root root 452 Sep 9 2018 killp
    -rw-r--r-- 1 root root 1.6M Sep 1 15:00 pcsx
    drwxr-xr-x 2 root root 1.0K Sep 1 15:03 plugins
    -rwxr-xr-x 1 root root 454 Sep 9 2018 recovery.sh
    -rwxr-xr-x 1 root root 156 Sep 9 2018 recovery2.sh
    -rwxr-xr-x 1 root root 67 Sep 9 2018 showCopyright.sh
    -rwxr-xr-x 1 root root 1.7M Sep 9 2018 showLogo
    -rwxr-xr-x 1 root root 3.2K Sep 9 2018 showVersion.sh
    -rwxr-xr-x 1 root root 3.9K Sep 9 2018 sonyapp
    -rwxr-xr-x 1 root root 3.1K Sep 9 2018 sonyapp-copy
    -rwxr-xr-x 1 root root 2.4K Sep 9 2018 sonyapp-copylink
    -rwxr-xr-x 1 root root 927K Sep 9 2018 ui_menu​
    root@bleemsync:/usr/sony/bin# chmod 755 pcsx

    This fixed the problem for me. I'll add this info just in case anyone else runs into the same problem. Just for full clarity I did this using a windows 10 PC.

    thanks for the help, PCSX is playing well now.
     
    ManitoCC likes this.
  14. thekarter104

    thekarter104 GBAtemp Advanced Maniac

    Member
    8
    Mar 28, 2013
    United States
    Is it possible to run an updated emulator on the USB with Autobleem nowadays?
    So you don,t have to touch the internal storage so there is no brick risk that way.
     
  15. ManitoCC

    ManitoCC Member

    Newcomer
    3
    Jan 7, 2017
    Thanks, had the same issue, and this worked for me.
     
  16. fallingrat

    fallingrat Advanced Member

    Newcomer
    4
    Jun 24, 2018
    Spain
    I'm having the same issues that @cronus07 explained above. However, my permissions seem to be alright: -rwxr-xr-x for pcsx. I changed the permissions via telnet on Mac OS.

    I tried to go back to the stock emulator but games aren't running. Any ideas? Thank you

    Edit: Error.log looks like this:

    saveMemcardBackup() memcard is broken
    pcsx terminate error.
    pcsx terminate error.
    pcsx terminate error.
    pcsx terminate error.
    saveMemcardBackup() memcard is broken
    saveMemcardBackup() memcard is broken

    Edit:
    Nevermind. It was because I was using a Mac. I did the same with windows and worked perfectly. I think the Mac was messing the file somehow

    [​IMG]
     
    Last edited by fallingrat, Jun 15, 2019
  17. focusonme

    focusonme GBAtemp Regular

    Member
    4
    Jun 30, 2016
    United States
    Which Version did Sony use? So Sony did no optimizations to PCSX? They just use the software without any special PS Classic optimisations that we will miss after the update?
     
  18. ksm59

    ksm59 Newbie

    Newcomer
    1
    Jul 13, 2019
    France
    Hi everyone, i change my "pcsx" files like @subcon959 said (thanks for you tuto). But, select+triangle dosen't work when i play a game. How can i solve that? Thanks for your help.
     
    Last edited by ksm59, Jul 13, 2019
  19. tito83

    tito83 Member

    Newcomer
    4
    Aug 4, 2011
    Cote d'Ivoire
    Maybe you skip the "mount -o remount rw /" section of the tutorial. Btw it's only 1 file.
     
  20. sideskroll

    sideskroll GBAtemp Advanced Fan

    Member
    3
    Aug 25, 2010
    Peru
    Here
    Nice work my friend. We all appreciate your findings. Let me ask you a couple of questions, do we need to restore the permissions to the partition after replacing the file? If so, how? Also, do you know the differences between the revisions? (The " original" and the one from bleemsync) how about the one from autobleem? (I THINK since the last beta theyre using another "optimized" version?) Or is it the same as bleemsync?
    Finally, is it worth it? I mean, can you notice an improvement?
    Thanks again and I hope you get to read and reply to this post.

    Edit: also, would you happen to know the location of the bios files? I'd like to try and replace them with my own (to test different versions etc)
     
    Last edited by sideskroll, Jul 19, 2019
Loading...