Sponsored Links

Sponsored Links

n4ru Flash Loader for PS3 - Successor to JaicraB's Loader Arrives


Sponsored Links
193w 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.





Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!

Comments 20 Comments - Go to Forum Thread »

• Please Register at PS3News.com or Login to make comments on Site News articles. Thanks!

cfwprophet's Avatar
#20 - cfwprophet - 193w ago
Ha ,so it should be /dev_flash/ otherwise it will give you some nasty bugs and you have to write a code to map arround.

Also i want to say that i for my self have learned will writing and developing PS3 ACID Tool for PC, that i have released, that its better to not combine to many apps. I've got some nasty bugs then more apps and code i have written and included.

Google teached me to split up the apps and embend them into the main app so that one .bat and .exe was called after another. And magically most bugs disappeared without the need to code around.

n4ru's Avatar
#19 - n4ru - 193w ago
You said you didn't test it and now you say you did. I actually didn't because I don't need to (I have a working solution with configurable paths, etc).

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).
I never said I tested this app, I said I tested mounting dev_flash from usb003.

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...

Isn't this simply a case of the string that is being matched?

If the syscall used to replace the path isn't specific enough then "/dev_flash" could match with "/dev_flash", "/dev_flash2" and "/dev_flash3" (Proof of this would be if you replaced "/dev_flash" with "/test" and found that flash 2 ended up being "/test2")

So surely the all round solution would be to replace the path "/dev_flash/" as it is more specific and would only match with "/dev_flash/" - it won't match with "/dev_flash2/" ?

Maybe i just missed the point entirely - but being a windows programmer i wouldn't be at all suprised!
(I'm assuming the syscall usage is kinda like a string Replacement) ?

p.s. That is of course assuming /" isn't some kind of escape character!
You're absolutely right. As I was reading dean's last post I recalled a conversation I had with KaKaRoToKS and he told me the following:
and no, it doesn't support wildcards, but you could map /dev/path/ICO to replace all ICO* files..

PSPSwampy's Avatar
#18 - PSPSwampy - 193w ago
You said you didn't test it and now you say you did. I actually didn't because I don't need to (I have a working solution with configurable paths, etc).

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).
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...

Isn't this simply a case of the string that is being matched?

If the syscall used to replace the path isn't specific enough then "/dev_flash" could match with "/dev_flash", "/dev_flash2" and "/dev_flash3" (Proof of this would be if you replaced "/dev_flash" with "/test" and found that flash 2 ended up being "/test2")

So surely the all round solution would be to replace the path "/dev_flash/" as it is more specific and would only match with "/dev_flash/" - it won't match with "/dev_flash2/" ?

Maybe i just missed the point entirely - but being a windows programmer i wouldn't be at all suprised!
(I'm assuming the syscall usage is kinda like a string Replacement) ?

p.s. That is of course assuming /" isn't some kind of escape character!

cfwprophet's Avatar
#17 - cfwprophet - 193w ago
Hmmm... nice one... but i can smell something that maybe in near - near future we will not need this CFW/USB/Firm loaders any more.

Could be a hacked installable .pup.

deank's Avatar
#16 - deank - 193w ago
It IS very simple. There's no reason that at least the mounting part shouldn't work.

I'm not sure why it's not working for you, but I know that with at least syscall35 there is no problem in mapping dev_flash, I've tested simply mounting usb003\cfw\dev_flash to dev_flash and it worked perfectly. Are you referring to using syscall8 to mount dev_Flash?

You said you didn't test it and now you say you did. I actually didn't because I don't need to (I have a working solution with configurable paths, etc).

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).

Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links







Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News