make: Entering directory `/home/wouldubeinta/src/psgroove-hermes'
gcc -Wall -O3 raw2payload.c -o raw2payload
ppu-gcc -c port1_config_descriptor.S -o port1_config_descriptor.o
port1_config_descriptor.S: Assembler messages:
port1_config_descriptor.S:934: Error: Unrecognized opcode: `quad_mem2(syscall_versiontest_index)'
port1_config_descriptor.S:943: Error: Unrecognized opcode: `load_label2(%r4,'
port1_config_descriptor.S:946: Error: syntax error; found `(' but expected `,'
port1_config_descriptor.S:946: Error: junk at end of line: `(0x7c01c)'
port1_config_descriptor.S:955: Error: Unrecognized opcode: `quad_mem2(syscall_process_sdkversion)'
port1_config_descriptor.S:968: Error: syntax error; found `(' but expected `,'
port1_config_descriptor.S:968: Error: junk at end of line: `(orig_syscall_25)'
make: *** [port1_config_descriptor.o] Error 1
make: Leaving directory `/home/wouldubeinta/src/psgroove-hermes'
make: *** [all] Error 2
I don't think the opcodes are defined in the port1_config_descriptor.
this is what I got atm
1. By banning (no need for that in my opinion bc psn is not a paid service; so they wont have to protect paying customars like on XBL)
2. By forcing them to upgrade to 3.xx
with the ammount of effort sony is putting into trying ot stop the JB with court cases its silly to think they wont ban us. all they will care about is that we have the JB and kill us.
thanks to cyber skunk i just upgraded to 3.50 :p
is there a hermes v4b + psn + 3.5 spoof out now?
i had the source of it but it don't have port1_config_descriptor.h ,, it just have the .S files :( and i need the .h file to compiile it with atmega16a ,
here is the source that i have :
RapidShare AG, Cham, Switzerland
if any1 please can make port1_config_descriptor.h or compile the hex for me to work with atmega16a i will be very thankfull
but will i be forced to reinstall all of the game data , and could i revert back to hermes v4b
Has anyone here been actually able to use the PSN payload on FW3.15?
I tried it but my PS3 just hangs when the Teensy is serving the exploit.
Maybe the 0x27364C address for the patch function on 3.15 is wrong?