PS3 How to boot psn iso off exfat usb - without installing game to internal hdd ?

H

harmjabo2

Member
@aldostools
I'm trying to boot psn coverted iso in webman mod, but when I load it bounces me back to xmb. When I install the game to to internal, and then run the iso it works. How can I get the iso to boot without internal hdd installation first ?
 
It depends the game. Some games come in physical disc, but require to install the game data to hdd to work.

If the game has updates, the game data also is stored in hdd.

The short answer is you cannot play from exFAT alone if the game requires to install to HDD.

If you have an external USB formatted in FAT32, you can enable external gameDATA using SELECT+SQUARE to redirect /dev_hdd0/game to /dev_usb000/GAMEI. But it only works if the game doesn't install files larger than 4GB.
 
@aldostools
Can I copy the game folder into /dev_usb000/GAMEI, or do I have to install the pkg into this partiton ?
Do I need place exdata folder on fat32 drive as well ?

*Update
I installed the pkgs, and the game shows up in xmb.
When I try to boot it, it brings me back to xmb.
Is there any fix for this ?
 
Last edited:
harmjabo2 said:
@aldostools
Can I copy the game folder into /dev_usb000/GAMEI, or do I have to install the pkg into this partiton ?
Do I need place exdata folder on fat32 drive as well ?

*Update
I installed the pkgs, and the game shows up in xmb.
When I try to boot it, it brings me back to xmb.
Is there any fix for this ?
Click to expand...

The files in GAMEI can be copied. It doesn't require to be installed.
The exdata folder can be in hdd0 or usb0 or usb1 (fat32).

If the game has files larger than 4GB, the game will be broken due FAT32 does not accept files >4GB.
If the game has updates, the pkg files must be installed in the correct order.
If the files were modified, verify if they were signed properly.
 
harmjabo2 said:
@aldostools
Is there a fix, if game installed to GAMEI drive keeps going back to xmb - after i load it ?
Click to expand...

No, unless you first identify the cause why it goes back.
Above I mentioned 3 common reasons. There could be others that I may have missed.
Sometimes enabling Cobra debug and using socat to check the activity log helps to find what's wrong.

harmjabo2 said:
can the exdata folder go into the root of usb or is there a specific folder structure ?
Click to expand...

Create exdata folder in the root of /dev_hdd0, /dev_usb000 or /dev_usb001.
Put the rap files inside that folder. That's all.
 
harmjabo2 said:
@aldostools
Sorry for sounding like such a noob, but
How do I use cobra debug and socat ?
BTW I'm evilnat 4.89 cfw
Click to expand...
You must swap the stage2.bin file in/dev_flash with a debug build and reboot.
Then you can use socat on Linux or socat-windows on Windows to listen to UDP broadcasts on port 18194 using this command:
Code: 
socat -u udp-recv:18194 stdout

Iirc in his CFWs, Nat added a XMB entry to CFW Tools to swap release/debug builds so you shouldn't need to get the file and swap manually
As to socat-windows it can be found on GitHub at https://github.com/StudioEtrange/socat-windows
 
bguerville said:
You must swap the stage2.bin file in/dev_flash with a debug build and reboot.
Then you can use socat on Linux or socat-windows on Windows to listen to UDP broadcasts on port 18194 using this command:
Code: 
socat -u udp-recv:18194 stdout

Iirc in his CFWs, Nat added a XMB entry to CFW Tools to swap release/debug builds so you shouldn't need to get the file and swap manually
As to socat-windows it can be found on GitHub at https://github.com/StudioEtrange/socat-windows
Click to expand...

BTW I prefer to use the command line below, because it logs the output to a file and the screen.
Sometimes the PS3 produces a big amount of data that is difficult to read or get lost in the buffer.
Logging to a file allows to analyze the outcome and find errors more easily.
Code: 
socat -lu stdout udp-recv:18194,reuseaddr |tee stdout.txt
 
aldostools said:
BTW I prefer to use the command line below, because it logs the output to a file and the screen.
Sometimes the PS3 produces a big amount of data that is difficult to read or get lost in the buffer.
Logging to a file allows to analyze the outcome and find errors more easily.
Code: 
socat -lu stdout udp-recv:18194,reuseaddr |tee stdout.txt
Click to expand...
Yes sure.
One can also use something like this to log to file.
Code: 
socat -u UDP-RECV:18194 CREATE:cobra_dbg.log

I never tried but it might be possible to use netcat as well.
 
harmjabo2 said:
@bguerville
Where does log file save ?
Click to expand...
What log file?
There's no log file created on the PS3 in this process.
There can be a log file created by socat on your PC but ONLY if you use a command to log to file, in which case the log file will be created in the socat folder by default, otherwise the logs are only displayed in the terminal window.
 
Yes, I mean the log file is in the socat win folder. When I open it it's empty
I arttached the cmd prompt

BitR79V
 
Last edited:
harmjabo2 said:
Yes, I mean the log file is in the socat win folder. When I open it it's empty
Click to expand...
If the Debug stage2 has been swapped AND you rebooted the PS3, Cobra logs are automatically broadcast to UDP port 18194 on your LAN.

If your PC is connected to the same LAN, same subnet, socat will receive the UDP broadcast.

Just use the first command I posted to begin with, logs should display in the terminal/command prompt, if you don't see anything, something is wrong, otherwise close socat and restart it with one of the log to file command.
 
You must log in or register to reply here.

Similar threads

Back
Top