129w ago - Here's a small app called n4ru Flash Loader, a successor to
JaicraB's Loader, I made in a few minutes. It's completely untested as I have no access to a PS3 until Monday and thus may not work at all, so feedback would be appreciated.
Download:
n4ru Flash Loader SRC /
n4ru Flash Loader PKG File
It uses the
SynaPS3 library, even though it only uses 1 function from the library. No harm in self-advertisement for my (baby-stage) library?
Jaicrab's Loader was made when we still had to use peek/poke to remount directories. We now have syscall8 (hermes) and syscall35 (PL3) for remounting directories. This makes things much easier.
This loader is universal and works with both Hermes and PL3. Create a folder called "cfw" on the root of your device and place the "dev_flash" folder inside it. Then create another folder called "cfw" INSIDE your "dev_flash" folder.
It supports CFW on your harddrive, so once you have a "finalized" build of your CFW, just throw it on hdd0 and run the app on start!
Along with mounting your dev_flash, this app will also dismount your cfw the next time you run it.*
It checks for the "cfw" folder on the following devices (in this order, meaning bottom devices take priority):
hdd0
ms
usb00x (1 through 7)
Source is of course included, and so is a compiled .pkg
*If any part of the app is broken it's probably this.
20 Comments - Go to Forum Thread »
Forgive me if this is wrong - i've not done any work on PS3 or linux coding and don't know much about the syscalls etc but...
The problem was that if you use PL3 to redirect /dev_flash to /1234_456 you also get /dev_flash2 and /dev_flash3 redirected to /1234_456.
It is possible that the payload I was using had issues (I reverted to hermes4b) but one flavor of the PL3 implementation didn't work as expected.
I mean it WORKED by replacing the table and /dev_flash with the new path, but one has to take care for other flashes because they share the SAME names (up to the 2/3).