4.75 Custom Firmware (CFW) & Updated Homebrew Apps

a few questions if anyone has the time to get back to me or pm me..
I have also made a new 4.75cfw and have installed it on my cech2503b slim and cechl03 fat, both installed fine and I used sen and psnpatch on both to access PSN.
I have the full log from start to finish with everything that was happening during the build..
yes its a mfw but ive never had issues with Playerkp420s in the past so thought I would make one for myself :)

DONT WORRY im not looking to hand it out or anything I am going to test it out for a few days then install on more ps3s
and if all is well then atleast I can make my own future cfws to use until others come out.

I just wanted to ask what the md5= thing is that everyone goes on about????
also how long until I know if its no good? or would it have not worked straight away?


theres no need to be rude or anything im happy to keep my 4.75 to myself just wanted some info...

thanks everyone :)

PLEASE MOVE IF IN THE WRONG PLACE
 
a few questions if anyone has the time to get back to me or pm me..
I have also made a new 4.75cfw and have installed it on my cech2503b slim and cechl03 fat, both installed fine and I used sen and psnpatch on both to access PSN.
I have the full log from start to finish with everything that was happening during the build..
yes its a mfw but ive never had issues with Playerkp420s in the past so thought I would make one for myself :)

DONT WORRY im not looking to hand it out or anything I am going to test it out for a few days then install on more ps3s
and if all is well then atleast I can make my own future cfws to use until others come out.

I just wanted to ask what the md5= thing is that everyone goes on about????
also how long until I know if its no good? or would it have not worked straight away?


theres no need to be rude or anything im happy to keep my 4.75 to myself just wanted some info...

thanks everyone :)

PLEASE MOVE IF IN THE WRONG PLACE

If you don't know what the md5 is for, and how it changes, you should NOT be installing firmware, let alone making it.

md5 is a validation check, FYI. Beyond that, you need to read ALOT MORE
 
in that case il learn all that wont I. was only asking theres no need to be so blunt about it. im not sharing it with anyone and if I messed up my ps3 its down to me.
im sure many of you had to start somewhere...

so I have checked my pup file and cant verify the code on google why is that? or is it because its new?
I get this when using pup check md5 - f988261c9d3bd5987c93cffd995a7012

again im only asking, its not the end of the world :)
 
Last edited:
in that case il learn all that wont I. was only asking theres no need to be so blunt about it. im not sharing it with anyone and if I messed up my ps3 its down to me.
im sure many of you had to start somewhere...

so I have checked my pup file and cant verify the code on google why is that? or is it because its new?
I get this when using pup check md5 - f988261c9d3bd5987c93cffd995a7012

again im only asking, its not the end of the world :)
MD5 is used to check the integrity of a file o backup. For example, lets say you share your .PUP and its MD5 hash is xxxxxxxxxxxxxx02, and i want to install your .PUP on my ps3 but what if i want to make sure the downloaded file is not corrupted? I proceed to check the integrity of such file with a MD5 Checker (i use winmd5).
 
MD5 is used to check the integrity of a file o backup. For example, lets say you share your .PUP and its MD5 hash is xxxxxxxxxxxxxx02, and i want to install your .PUP on my ps3 but what if i want to make sure the downloaded file is not corrupted? I proceed to check the integrity of such file with a MD5 Checker (i use winmd5).

ahh ok I understand thanks
 
ahh ok I understand thanks

I would also mention at this point, to not install any cfw you create on another persons console. There is a lot more reading you need to do before you can ETHICALLY ask someone else's console to run, when you were not aware how to verify the validity.
The solution to ethically allow it would be to provide the complete source code in addition to your firmware, and put big warnings all over the place to ensure that users do not accidentally brick their systems.

Basically like this. One patch not applied properly can equal a green light of death. Or a yellow light of death. There are hundreds of little tiny things that are in play, that need to be tested thoroughly before release.

Here's hoping that eventually you get to be a big name like the rest for cfw development, or that everything is working perfect for you. I don't mean ill will, just also have to look out for the protection of those that don't know better than to install risky cfw/mfw builds. :)
 
I would also mention at this point, to not install any cfw you create on another persons console. There is a lot more reading you need to do before you can ETHICALLY ask someone else's console to run, when you were not aware how to verify the validity.
The solution to ethically allow it would be to provide the complete source code in addition to your firmware, and put big warnings all over the place to ensure that users do not accidentally brick their systems.

Basically like this. One patch not applied properly can equal a green light of death. Or a yellow light of death. There are hundreds of little tiny things that are in play, that need to be tested thoroughly before release.

Here's hoping that eventually you get to be a big name like the rest for cfw development, or that everything is working perfect for you. I don't mean ill will, just also have to look out for the protection of those that don't know better than to install risky cfw/mfw builds. :)

THANKS PSYKOSIS as I say I will not be sharing anything for a long time just trying to learn what I can and im sure il get there in the end :)
 
MD5 is unique calculated hash for files in this case for PUP file. If you build pup, and its working then you can check MD5 of this file and share. Now lets say you are sharing your MFW with community, someone downloading this and checking MD5, if calculated sum is same as you write then end-user is sure that instaling EXACTLY same pup as you. But if MD5 is different than one you provided then user know that something is wrong (bad download, edited pup, disk problem, etc), and this file shouldn't be installed because have really brick potential.

Even if you change ONE single byte of your pup file then MD5 will be totally different. Also if you build another pup with exatcly same setting like before MD5 will be different due to different time stamp of files inside, and because compresion is used, is imposible to compress files inside exactly same way in this case. This sum giving people proof that is exactly same file that you uploaded.
 
I would also mention at this point, to not install any cfw you create on another persons console. There is a lot more reading you need to do before you can ETHICALLY ask someone else's console to run, when you were not aware how to verify the validity.
The solution to ethically allow it would be to provide the complete source code in addition to your firmware, and put big warnings all over the place to ensure that users do not accidentally brick their systems.

Basically like this. One patch not applied properly can equal a green light of death. Or a yellow light of death. There are hundreds of little tiny things that are in play, that need to be tested thoroughly before release.

Here's hoping that eventually you get to be a big name like the rest for cfw development, or that everything is working perfect for you. I don't mean ill will, just also have to look out for the protection of those that don't know better than to install risky cfw/mfw builds. :)

[offtopic] Awwwhhggggg you had to say 'Green light of death' and reminded me of a Cech-2001A console tossed around in my room. Turns on, green light, immediately yellow and then red light (red light blimps until i press the power on button) :(((((((((((((((((((((((((((

edit: hey, psykosis, do you recommend that book? (that one in your signature)
 
[offtopic] Awwwhhggggg you had to say 'Green light of death' and reminded me of a Cech-2001A console tossed around in my room. Turns on, green light, immediately yellow and then red light (red light blimps until i press the power on button) :(((((((((((((((((((((((((((

edit: hey, psykosis, do you recommend that book? (that one in your signature)

I wrote it, I'd always recommend it. (I'm saying this as a person, and not a recommendation by the site or moderators).

Most people that pick it up,don't put it down. Lol.
 
MD5 is unique calculated hash for files in this case for PUP file. If you build pup, and its working then you can check MD5 of this file and share. Now lets say you are sharing your MFW with community, someone downloading this and checking MD5, if calculated sum is same as you write then end-user is sure that instaling EXACTLY same pup as you. But if MD5 is different than one you provided then user know that something is wrong (bad download, edited pup, disk problem, etc), and this file shouldn't be installed because have really brick potential.

Even if you change ONE single byte of your pup file then MD5 will be totally different. Also if you build another pup with exatcly same setting like before MD5 will be different due to different time stamp of files inside, and because compresion is used, is imposible to compress files inside exactly same way in this case. This sum giving people proof that is exactly same file that you uploaded.

Thank you, I couldn't have explained it better.
Of course I don't know enough of it to feel ready to play lol.
 
Custom firmware Ferrox 4.75 v1.0 CEX Developer Alexander

im back online with gta 5....happy as a pig sh*t

Eccolo qui..! Dopo giorni di assidue richieste siamo pronti ha rilasciare la versione 1.0 del Custom firmware 4.75 del Developer Alexander. Abbiamo testato a fondo questa versione del CFW Ferrox e possiamo confermare il corretto funzionamento su diversi modelli di console non chè un metodo alternativo per avviare le copie di backup, visto che ad oggi non vi è ancora nessun gestore che supporti il firmware 4.75.
Translation

Here it is ..! After days of assiduous requests we have ready to release version 1.0 of the Custom Firmware 4.75 Developer Alexander . We have thoroughly tested this version of the CFW Ferrox and we can confirm the proper functioning of different models of the console as well as physical a way to boot your backups , as to date there is still no manager that supports firmware 4.75

please can someone test [PS3-Release] Custom firmware Ferrox 4.75 v1.0 CEX. | maxmodding.it



Features

- Built-based OFW 4.75
- Disabled the CoreOS and control ECDSA
- LV1: patched to remove the protection LV2
- LV1: patched CoreOS Hash Check (prevents brick from the console downgradate not dehashed)
- LV1: Peek & Poke
- LV2: Peek & Poke
- Compatibility PS2 Games
- Compatibility PSP Remastered
- Compatibility PSP Minis
- Key 4.75 (start games with keys 4.70 EBOOT / sprx)
- PSN / SEN Enabled.
- RSOD Screen Bypass for consoles suffering from RSOD
- BT Remote PS3 patch
- PS3 BluRay DISC patch
- Compatibility with the latest version of REACTPSN
- App_home / PS3_GAME *
- Install Package Files *
- Ability to Downgrade from OFW 3:55 with QA activated.
- Upgradable from any CFW's
- Support XMB InGame ScreenShot Feature
- Support Remote Play Feature
- Stability as nell'OFW 4.75
- Ability to downgrade from any custom firmware with QA activated.

After installation

- Restore File System (to recovery)
- Rebuild Database (to recovery)
So, you will have a clean installation and you'll be fine.
(Thanks to franci97 & SonyForever)

Tests carried out

CECH 2004A - Tested and Working. (Thanks Mizio)
CECH 2004b - Tested and Working. (Thanks Mizio)
CECHG04 - Tested and Working. (Thanks SNK)
CECHL-01A - Tested and Working.
CECH-2501 - Tested and Working. (Thanks REIZA72)
CECH 2504A - Tested and Working.
CECHC-04 - Tested and Working.
CECHL04 - Tested and Working


FROM [PS3-Release] Custom firmware Ferrox 4.75 v1.0 CEX. | maxmodding.it

MD5: 6ADE146697DB3089A71510480C66D42D
 
Last edited:
hey everyone i want to know something about ccapi
first i press x on psnpatch to disable cfw and spoof id to my friends id wich is in the usb and go online after that do i have to use ccapi to spoof it to 0000000000000 and can i change it to 00000000 after disableing the cfw???? if i have to use ccapi for safe reasons i spoof after sing in or after i start or join a server in bf hardline for example
sry for bad english :3
 
I have a Ps3 slim running ofw 4.70 can i install a cfw 4.75 when one comes out or would i have had to do so back when my ps3 was on ofw 3.55?
 
Hey guys im a noob when it comes to CFW, but i downloaded the CFW 4.75 and when i went to do a system update i got an error
"The data s corrupted: (8002F957)
 
HI guys, any news of Nor Patcher 4.75?

Thanks in advance.

Regards,

ZerO

Use 4.70 or earlier version which you prefer...the most important is pre-check dump before patching..min. 3-4 times!!



Hey guys im a noob when it comes to CFW, but i downloaded the CFW 4.75 and when i went to do a system update i got an error
"The data s corrupted: (8002F957)

Probably you are on OFW of Sony...you need modify your ps3 firstly...
 
Last edited:
Back
Top