Really looking forward to this on 3.41.
Actually downloading the files. As soon they are downloaded i wil mod them and put it online. Maybe today.
http://www.ps3news.com/forums/ps3-ha...ve-114271.html Maybe you could take the code from this that mounts dev_hdd0 to dev_usb001 and also modify it to mount dev_flash to dev_usb002.
You could release your own firm loader,with source, also be cool if there was a reboot/reload feature so we could swap a firmware file (using ftp or filemanager) and reboot to see the changes instantly .
The reason I say use 2 USB devices is for extra speed when accessing both at once , of course devices could be mounted to seperate folders on 1 USB stick, dev_flash2 could be mounted on same stick as dev_flash just so that we would not need to modify our actual xregistry.
Last edited by DeViL303; 10-21-2010 at 12:32 PM
here's something from hermes v4 syscall8.h that might be what's needed:
Code:/* NOTES about path_open_entry: compare_addr can be a string full path for files or not. The size of the string can be len+1 replacea_ddr can replace a file, files or directories. The size of the string must be replace_string + hook_open string remnant+1 (recommended 0x800 to work with directories) // example 1: replacing a file compare_addr: "/app_home/PS3_GAME/USRDIR/EBOOT.BIN" replace_addr: "/dev_usb000/PS3_GAME/USRDIR/EBOOT.BIN" compare_len= strlen(compare_addr); replace_len= strlen(replace_addr); // example 2: replacing files by a unique file compare_addr: "/app_home/PS3_GAME/ICON" replace_addr: "/dev_usb000/PS3_GAME/ICON0.PNG" compare_len= strlen(compare_addr); replace_len= strlen(replace_addr)+1; // example 3: replacing directories compare_addr: "/app_home/PS3_GAME" replace_addr: "/dev_usb000/PS3_GAME" compare_len= strlen(compare_addr); replace_len= strlen(replace_addr);
Can you explain in more detail what we need to do to the registry? Just change the flags on the debug options? Which debug options do we need to change, and to what values do we need to change those flags?
CFWprophet: Just got around to testing this and I cant get firmloader 0.3 to run on my 3.15 console at all,just get returned to xmb but dev_flash is not running from usb, its all still the same as before reboot, and no activity light on usb stick, has anyone else got it running on 3.15 with a PIC device?
it may be because im using wrong payload for my PSgroopic device, I lent my minimus to someone so cant us ethis for now. what features are needed in payload for firmloader to work, peek and poke only?
P.S really lookin forward to your 3.41 release , might try a few of your hacks on 3.41 myself while im waiting!
I'm using a PIC device at the moment on this PS3 and as there is no hermes payloads for 3.15 im stuck using KaKaRaToS 3.15 payload for my PIC that has no peek and poke, (can not find anyone uploading his 3.15 dev payloads for PICS?) so im stuck like yourself.
It's a shame but without support for firmloader0.3 this hackpack is not going to run, has anyone got this running on 3.15 as there has not been much feedback considering the fact that if this works it enables debug options which would be massive news?!
Please release 3.41 version soon, Thanks CFWprophet
Last edited by DeViL303; 10-22-2010 at 09:58 PM Reason: Automerged Doublepost
I don't have a 3.15 system, but as I understand it, you do need peek+poke support to run USB Firm Loader. Given the way peek+poke works, I'd say you more than likely would need a USB Firm Loader specific to 3.15 systems in order to patch the right offsets.