How to make ps3 cfw.

but that still didn't give me enough space, so I went to the resource,
There I found some files are not zlib compressed (explore plugin rco is one),
so I compressed it and ran through some features that use it and I could not see anywhere that it lagged,
If you need 3.5 MB extra in dev_flash, delete the PIC*.png from /dev_flash/vsh/resource/explore/netflix and the theme in /dev_flash/vsh/resource/theme

BTW I see your EBOOT.BIN of Overflow Boxed Tools is 2.27MB, maybe you should consider to make a lighter version.
 
Last edited:
Due to me adding so much to the dev_flash in my conversion cfws I spent some time combing for any way to make more space,
with the core_os in order to add the dex kernel you must resign the other files to make space in the pkg, so I painfully made some bat files to unpack/repack the entire syscon and module,

Ugh? why did you have to do this? Are you going to release CDEX or REX FW?
 
Ugh? why did you have to do this? Are you going to release CDEX or REX FW?

I did with 4.76, 4.78 and 4.80,
Well technically 4.76 was dex ofw 4.60 spoofed to 4.76,
When I bought my last dech console it was from someone at rock* and I had access to the dex pups,
unfortunately he has moved on to a non sony related company and I no longer have access so until I can find another person I'm not sure when the next time I will be able to do that will be :(
I was thinking about making a frankenstein cfw with 4.80 4.81 and 4.75 kernel as you can resign kernels and use them on different versions just like other files but I'm not sure about the ramifications in regards to performance and I don't think it would be very well received.
 
If you need 3.5 MB extra in dev_flash, delete the PIC*.png from /dev_flash/vsh/resource/explore/netflix and the theme in /dev_flash/vsh/resource/theme

BTW I see your EBOOT.BIN of Overflow Boxed Tools is 2.27MB, maybe you should consider to make a lighter version.

Thank you Aldo I will look at that,
also I have been looking at cutting the code in the boxed tools down to save size,
it's just once I think of a different idea the code becomes much, It started off as less than 750kb and grew and grew lol.
I was thinking of hijacking singstars download in order for the cfw to directly download the boxed tools and then I could not put it into the cfw, I'm unsure about the final plan as of now lol.
 
That's really cool and handy to know, a MB is a lot for one file - 0.5% of total space. If you are ever looking for even more space, there is 1.57MB taken up by unneeded Netflix signup pics inside resource/explore/Netflix/ (Rebug removed them without issue in 4.80). you could delete them or dummy them with 1x1 pixel images just incase. There are also lots of very similar backgrounds in the resource/explore/icon folder, some of those could be deleted and the calls redirected to the remaining ones. Probably get another MB there :)

I thought that official netflix worked on latest cfw ? but to be honest I've never tried lol
 
I did with 4.76, 4.78 and 4.80,
Well technically 4.76 was dex ofw 4.60 spoofed to 4.76,

I am not quite sure what you meant here, it's not necessary to build DEX CFW with what you mentioned unless you want to include dual kernels including retail one. I suppose you tried what I do with REX/D-REX

When I bought my last dech console it was from someone at rock* and I had access to the dex pups,
unfortunately he has moved on to a non sony related company and I no longer have access so until I can find another person I'm not sure when the next time I will be able to do that will be :(

The same problem here, our provider went M.I.A., he mentioned that his company stopped working on VITA,so as a result, VITA stuff were taken down from his source at that time, ever since then he's been M.I.A.

I was thinking about making a frankenstein cfw with 4.80 4.81 and 4.75 kernel as you can resign kernels and use them on different versions just like other files but I'm not sure about the ramifications in regards to performance and I don't think it would be very well received.

Now that you have the source of our toolbox, you can swap kernels from core_os easily,
However it's impossible to insert 3 kernels in Core_OS, as you're only allowed for roughly about 7mb per each ROS.

But it's quite pointless to have multiple kernels especially like versions you mentioned. having the same version of Retail/Debug kernels enough IMO, of course you need corresponding modules to have proper functionality along with vsh which is what current REBUG offers.

Miralatijera did similar approach, it was quite impressive, he wrote his own debugger like the one that Target Manager provides.

Messing with kernels can be safely done with lv2_loader integrated inside REBUG TOOLBOX, which is my favorite method when it comes to porting payloads for various projects including COBRA 7.X
 
I thought that official netflix worked on latest cfw ? but to be honest I've never tried lol
It does, its just that the sign up images are not needed, people can sign up on their PC, for the sake of 1.56MB flash they can anyway ;) Also Ive never actually seen where those images show on the XMB, maybe its only in different regions.
 
I am not quite sure what you meant here, it's not necessary to build DEX CFW with what you mentioned unless you want to include dual kernels including retail one. I suppose you tried what I do with REX/D-REX



The same problem here, our provider went M.I.A., he mentioned that his company stopped working on VITA,so as a result, VITA stuff were taken down from his source at that time, ever since then he's been M.I.A.



Now that you have the source of our toolbox, you can swap kernels from core_os easily,
However it's impossible to insert 3 kernels in Core_OS, as you're only allowed for roughly about 7mb per each ROS.

But it's quite pointless to have multiple kernels especially like versions you mentioned. having the same version of Retail/Debug kernels enough IMO, of course you need corresponding modules to have proper functionality along with vsh which is what current REBUG offers.

Miralatijera did similar approach, it was quite impressive, he wrote his own debugger like the one that Target Manager provides.

Messing with kernels can be safely done with lv2_loader integrated inside REBUG TOOLBOX, which is my favorite method when it comes to porting payloads for various projects including COBRA 7.X

I don't think I was clear, the 4.76 dex cfw I made from 4.60 dex ofw spoofed to 4.76 for psn access,
the 4.78 and 4.80 cfws were like your drex/rex with an edited version of the rebug toolbox to accomadate for the cfws I made in regards to paths, file names and what files are renamed/swapped (I did message evilsperm numerous places to ask for permission to use and add into my cfw but had no reply, I decided that as he released it open source he meant for it to be used, I hope that's ok, I didn't want to move the dex conversion method into my own boxed tools as it's not my method so just updated and edited the rebug toolbox leaving the name but adding thanks for the source),

I did not mean to add 3 kernels although such a thing would be quite epic,
I only meant to use files from 4.75 4.80 and 4.81 to make a cfw, using kernels from 4.75 and vsh with files from 4.80 inside a 4.81 pup (possibly using some of the 4.80 module files may help with the 4.81 files and 4.75 kernels, just speculation tho)
using different kernels with different version vsh is unpredictable but sometimes works ok dependant on version,

Yes I agree that the rebug toolbox lv2_kernel swap is a blessing, when first using cobra I quickly found that if you port it wrong you hard brick (many times I have e3'd my way back to safety) but now I install all cobra files into a cfw with standard non cobra kernel and load from toolbox (no heartache),
I also like testing the combination of module files (those different in cex and dex releases) I find that with different versions a different combination works well, for example on 4.80 all different modules are better if dex but with 4.78 I found that the cex explore plugin works better, not sure if you found that and it may have just been my imagination lol.
 
It does, its just that the sign up images are not needed, people can sign up on their PC, for the sake of 1.56MB flash they can anyway ;) Also Ive never actually seen where those images show on the XMB, maybe its only in different regions.

Oh ok, yes I think different regions, a friend of mine uses american netflix on his ps3 and he says that it's much better than ours
 
Oh ok, yes I think different regions, a friend of mine uses american netflix on his ps3 and he says that it's much better than ours
I had US and EU running on my system at one point, at the time I really didn't see a difference except for version numbers.
 
I would like to see more like it anyway, us beginners gotta start somewhere. I can already use mfw builder, this is more interesting though. :)



You use puad though don't you? I ask because I saw it say "[PUAD]" after the version string in one of your recent releases.
I do use puad but not for tar balls files because it's buggy on there
I do use puad on upl and core os because it's fast
 
I do use puad but not for tar balls files because it's buggy on there
I do use puad on upl and core os because it's fast


Yes I also find it's very quick when just unpacking core os and upl, handy when turning a cfw into nobd.

@DeViL303 It would have been with the nobd when I edited the upl and lv1,
I have moved to a new windows 10 environment and must have re installed puad without editing options,
normally I don't use puad only with nobd as I have not yet added upl unpack repack to my own personal program,
I will send you a copy and maybe upload for anyone who wants to try it.
I'm making a few changes and adding some extra options but I'll let you know when it's done.
Only problem with it is that I use tar.exe which I believe is what makes puad repack with smaller size pkgs inside the pup but I don't think that has an effect on the actual fw after installation.
I have noticed it copies to the hdd a bit slow but that may be due to patches in lv1 (not sure).
 
It does, its just that the sign up images are not needed, people can sign up on their PC, for the sake of 1.56MB flash they can anyway ;) Also Ive never actually seen where those images show on the XMB, maybe its only in different regions.
Trying to complete the info for the record... the images for netflix are...
Inside: dev_flash\vsh\resource\explore\netflix

ICON0.png
PIC0.png
PIC0_02.png
PIC0_03.png
PIC0_07.png
PIC1.png
PIC2.png
PIC2_02.png
PIC2_03.png
PIC2_07.png

Are the http://www.psdevwiki.com/ps3/Content_Information_Files for a standard "HDD game"
Like the ones used by an standard .PKG is just sony took the weird decission of including them in the firmware

There are 2 groups of images that are displayed "optionally" (based on the language settings of the XMB)
- PIC0.png, PIC0_02.png, PIC0_03.png, and PIC0_07.png
- PIC2.png, PIC2_02.png, PIC2_03.png, and PIC2_07.png

-------------------------
Lets use as example the first group for PIC0 (the other group works in the same way), PIC0.png, PIC0_02.png, PIC0_03.png, and PIC0_07.png
The images with a "0x" suffix are for languages (02=spanish, 03=french, and 07=portuguese) and only are displayed by XMB if the XMB is configured to that languages
Incase the image for the user language doesn't exists (as example for korean) what the XMB does is to load the "fallback image" from that group that is PIC0.png and uses english as default language (because there is no PIC0_09.PNG for korean)

This is the theory, so i think is 100% safe to delete the PIC0_02.png, PIC0_03.png, and PIC0_07.png (only keep PIC0.png) and PIC2_02.png, PIC2_03.png, and PIC2_07.png (only keep PIC2.png)

In resume, if you want to behave like the original (but "only in english") you only need 4 files in the folder:
ICON0.png
PIC0.png
PIC1.png
PIC2.png

-------------------------
A more drastic approach for the ripping is to delete all the images and keep only ICON0.PNG because this is the only image that is mandatory for a "HDD game" content (as stated in the SDK)

-------------------------
I never tested this myself though, and never installed netflix so not sure when are supposed to appear on screen, but i think that both methods i explained (remove only the language specific images... or... remove everything except the icon) should work

Edit:
Handy link with some firmware images ---> http://www.psdevwiki.com/ps3/User_talk:Eussbot
 
Last edited:
Is there anyway I can build a CFW with fan control? I just want it a constant set speed. No ability to do anything but install Movian once. . Then I plan to edit XML to completely remove package installation. This system is the one in my kids room so it does not access PSN but I also don't want her to have access to anything else. I basically want an original firmware capable of running movian that will stay cool temp wise.
 
Is there anyway I can build a CFW with fan control? I just want it a constant set speed. No ability to do anything but install Movian once. . Then I plan to edit XML to completely remove package installation. This system is the one in my kids room so it does not access PSN but I also don't want her to have access to anything else. I basically want an original firmware capable of running movian that will stay cool temp wise.
You can but really it's not for an average joe
You need to make payload in lv2 to do that
In cobra, that's a more reality
 
A more drastic approach for the ripping is to delete all the images and keep only ICON0.PNG because this is the only image that is mandatory for a "HDD game" content (as stated in the SDK)

-------------------------
I never tested this myself though, and never installed netflix so not sure when are supposed to appear on screen, but i think that both methods i explained (remove only the language specific images... or... remove everything except the icon) should work

Yes, this is what I did for last REX release. I worked on this very carefully for 4.80 REX, tested every possible combination :) and came up with the more drastic approach which I find it the most efficient because netflix requires updates regardless so it doesn't really affect the feature itself but the appearance that has translated scripts in the background images :)
 
Back
Top