PS3 Is there any v1.00 CFW or anything pre 3.00?

@DeViL303 , I'm not sure how helpful this will be, but there's a database of firmware: https://gbatemp.net/threads/ps3-firmware-collection.447574/

s7evinsins has a database too, but I tried one link, and it was down. those may be down as well, and it doesn't have a cfw lower than 3.41 or 3.55.

as for cfw 1.00, I'm thinking it may have been @haxxxen who made it. I don't know if he released it online though. I think he just did it to do it. I could be wrong on the dev, but that's what I'm thinking.
 
Well getting a video of v1.00 is the easy bit, Just downgrade and record with PVR. CFW 1.00 not so easy..

I will try make one someday.


I found the one Evil_Nat did I was wrong though. He did 3.15 CFW the last official one to have OtherOS but GeoHot did do a 3.21 adding OtherOS support back.
 
@DeViL303 , I forgot to mention. be very careful on firmware that low. there's no recovery mode.
Thanks for the warning, but we have official factory service mode on older OFW afaik, So should be ok hopefully.
I found the one Evil_Nat did I was wrong though. He did 3.15 CFW the last official one to have OtherOS but GeoHot did do a 3.21 adding OtherOS support back.

Thanks. Yeah I seen that. If no one else makes one I will have a look, Im interested in 2.80 really, As I want to look into widgets. I have hdd dump from 2010, that has files still there from 2.80 times.

Also I think a v1.02 CFW would be cool for nostalgic value (earliest PUP available). We could even make a v1.00 CFW PUP by taking xmls from DEX, as it has all the v1.00 CEX entries anyway, so we could get very close to OFW 1.00 with that.
 
yw. I wish I could be more helpful. I think @haxxxen updated mfw a while back, so he may have used it and 1.02 for testing. I believe the point was seeing if it was possible to create cfw on it, which it is. there's a part on psdevwiki that talks about adding newer keys to older firmware. that may have been what he was trying to achieve. it says that it is indeed possible. I think @sandungas mentioned doing it with mfw can screw something up. manually might be okay (not sure). there's not a whole lot of info on it aside from a couple sentences on psdevwiki.
 
If some CFW maker wants a little side project, please make some older CFWs for research purposes. We need like v1.50 Cobra CFW, 2.50 Cobra CFW. :)

@Bobby_Downgrades maybe?
This is the kind of things that needs a good plan, i think it would be good tryng to see if there are some significative groups of PS3 models with the same minimal firmware
Lets say... imagine we realize that there are a lot of PS3 fat models with minimal firmware 2.40... then that firmware version is a good candidate to create a CFW for it because lot of people could use it

Another thing that could be convenient (incase the minimal firmware doesnt makes sense) is to use the rounded versions... like 1.00 2.00 and 3.00 because this is when happened the biggest changes
Or the versions previous to them, so you can see how it was working inmediatly before the change to 2.00 or 3.00

I would be interested in some 2.80 CFW, specially for thoes older Phat users or collectors, whom want the benifits of the CFW, but want the firmware originality, specially Fan Control.

The problem might be with the PS2 Backwards Compatibility patches into the self itself, remember patches were added until 4.30,so there are some PS2 Titles that don't work properly on older firmwares, specially for the C/E models,unless you can add the latest PS2GX_Emu.self into the older CFW, which might not be compatible.

Sent from my G8141 using Tapatalk
The emulators can be taken from 4.85 i think there is no problem about it because works as independent programs, the only thing needed to do is to resign them well for the old firmware
With the PSP emulator maybe is going to be a bit messy because are lot of files
you don't understand the intentions. He is not looking for a CFW on older firmware to use it every day.

if @DeViL303 feels like it can be helpful to his research i think he is the only to speak on that aspect.

Stands to make more sense in seeing if things work on an earlier CFW then to port and then see.
I can see how it would be useful thing for developers. but he is not suggesting it be made for everyday or user use.
Its for development purposes its for research.
Well, but is true there has been lot of people along the time asking how to revert the look of XMB to an older firmware
Personally i like XMB a lot (is one of the most intuitive interfaces i ever seen) but i dont want to revert it, i like most of the improvements they did
The only things i dont like is the "spam" of the stores, the "preview" of the hakoniwa app in photo, and things like that... just because i find them excesive

Anyway... there is many people that wants the old XMB, but you are right that the best way is not installing an old firmware, maybe the XMB will look more "lighter" in an old firmware but they are going to lose features too

Ps3 1.0 dex update found here on wiki
https://www.psdevwiki.com/ps3/1.00_DEX
There is other for AVtool, this one is interesting because it have the emulators
https://www.psdevwiki.com/ps3/1.00_AV
Inside some of the emulators it can be seen a timestamp extremelly precise of the time when the firmware was compiled, by comparing them it can even seen how many time takes the official compilation enviroment to compile the emulators, lol (just a couple of minutes if i remember correctly)

Also, by comparing that timestamps with retail 1.01 it can seen they was working at full speed that first days when the PS3 was released in japan for first time, i was talking about this with @Roxanne and we was impressed of how fast they was... there is a difference of few days in between some of that first firmwares, also, the first PS3 model shipped with 1.00 firmware was only available in shops for one week only !, remember that days ? the japaneses was buying PS3's like candies sleeping at night at the door of the shop, lol
This is why s almost imposible to find a PS3 with firmware 1.00 installed (and never updated), because it needs to be one of that PS3 models sold in japan in the first week, and should be kept "boxed" until today, the probabilities for that to happen are near zero :P
@DeViL303 , I forgot to mention. be very careful on firmware that low. there's no recovery mode.
Thats super important, lol, good you mentioned it, not sure what could happen with the hdd and databases manteinance, i guess was made automatically, and i guess it had some kind of warning texts too incase of problems
 
Thats super important, lol, good you mentioned it, not sure what could happen with the hdd and databases manteinance, i guess was made automatically, and i guess it had some kind of warning texts too incase of problems
I wonder how far back does the FSM dongle work , because its even better than recovery really? I have a few of those dongles still. e3 dongle, PS3YES etc. It would be cool if those lv2_diag.self files work on v1.02+
 
I wonder how far back does the FSM dongle work , because its even better than recovery really? I have a few of those dongles still. e3 dongle, PS3YES etc. It would be cool if those lv2_diag.self files work on v1.02+
Not sure if what im going to say is right, but i always thought the original USB jailbreak dongle was exploiting a feature that is official, is a clone of the official "usb-jig" they uses in repair services or at factory. This should work in all firmwares since 1.00
With the .self that are loaded next from USB i dont really know, maybe is just a matter of resigning them with older keys
 
might be able to tell how those are signed with scetool gui. it will tell you a lot of information about any encrypted file, though the lv2diag may be a rare case (not sure).
 
This is the kind of things that needs a good plan, i think it would be good tryng to see if there are some significative groups of PS3 models with the same minimal firmware
Lets say... imagine we realize that there are a lot of PS3 fat models with minimal firmware 2.40... then that firmware version is a good candidate to create a CFW for it because lot of people could use it

Another thing that could be convenient (incase the minimal firmware doesnt makes sense) is to use the rounded versions... like 1.00 2.00 and 3.00 because this is when happened the biggest changes
Or the versions previous to them, so you can see how it was working inmediatly before the change to 2.00 or 3.00


The emulators can be taken from 4.85 i think there is no problem about it because works as independent programs, the only thing needed to do is to resign them well for the old firmware
With the PSP emulator maybe is going to be a bit messy because are lot of files

Well, but is true there has been lot of people along the time asking how to revert the look of XMB to an older firmware
Personally i like XMB a lot (is one of the most intuitive interfaces i ever seen) but i dont want to revert it, i like most of the improvements they did
The only things i dont like is the "spam" of the stores, the "preview" of the hakoniwa app in photo, and things like that... just because i find them excesive

Anyway... there is many people that wants the old XMB, but you are right that the best way is not installing an old firmware, maybe the XMB will look more "lighter" in an old firmware but they are going to lose features too


There is other for AVtool, this one is interesting because it have the emulators
https://www.psdevwiki.com/ps3/1.00_AV
Inside some of the emulators it can be seen a timestamp extremelly precise of the time when the firmware was compiled, by comparing them it can even seen how many time takes the official compilation enviroment to compile the emulators, lol (just a couple of minutes if i remember correctly)

Also, by comparing that timestamps with retail 1.01 it can seen they was working at full speed that first days when the PS3 was released in japan for first time, i was talking about this with @Roxanne and we was impressed of how fast they was... there is a difference of few days in between some of that first firmwares, also, the first PS3 model shipped with 1.00 firmware was only available in shops for one week only !, remember that days ? the japaneses was buying PS3's like candies sleeping at night at the door of the shop, lol
This is why s almost imposible to find a PS3 with firmware 1.00 installed (and never updated), because it needs to be one of that PS3 models sold in japan in the first week, and should be kept "boxed" until today, the probabilities for that to happen are near zero :P

Thats super important, lol, good you mentioned it, not sure what could happen with the hdd and databases manteinance, i guess was made automatically, and i guess it had some kind of warning texts too incase of problems

For the Full Discussion, check --> https://www.psdevwiki.com/ps3/Talk:1.00_CEX

As [U]@sandungas[/U] already noted, finding such a launch model from launch day is extremely difficult and even if you will find one, there is no guarantee if you can even dump the firmware (had this discussion already with zecoxao and CelesteBlue on Twitter) or if you can, if it will be even 1.00 since as you can see in our discussion, it is still today unclear what kind of Firmware the launch model on launch day actually had. The chance is pretty high that there isn't any PS3 outside with a 1.00 pre-installed. This would explain why the Launch Games in Japan had already the Firmware 1.02 included inside the Disc (so there was no update needed for buyers on launch day) together that the earliest "More System Information" Button Combo is triggered on both 1.10 and 1.02 at earliest. And yes, already 1 Month after Launch (December 2006), every PS3 in Japan got released with Firmware 1.10 pre-installed.

So it's better not to hope for a 1.00 CFW, believe me it will give you only headaches. :)


PS: Only [U]@sandungas[/U] was impressed about those results, I knew it already before we discussed that :P
 
that is true. the firmware I'm thinking of is probably the earliest firmware you could get onto your computer.
 
@DeViL303, I think Roxanne is correct, an old cfw pre 1.50 will be headache to make.
That being said anything after that (up to 3.55) will be pretty easy, remember most patches will not need to be applied so could be quite clean cfw.
Send me a list of which versions you wanted and I will try to do them when I have some time free.
 
@DeViL303, I think Roxanne is correct, an old cfw pre 1.50 will be headache to make.
That being said anything after that (up to 3.55) will be pretty easy, remember most patches will not need to be applied so could be quite clean cfw.
Send me a list of which versions you wanted and I will try to do them when I have some time free.
Wow thanks, that would be great if it works out someday.

As for version, I'm thinking 2.70 or 2.80 would be most useful to me for researching widgets, also lots of people on slims have a minver of 2.70, So it will suit slims and phat, and it still has widgets.

Would there be any chance of getting even just a basic cobra with debug output and background FTP just on 2.70 or 2.80?

Then if its not too much work and you had time , It would be nice for archiving to have earliest possible like 1.02, then 1.50, 2.00, 2.50, 3.00 or something to have a good sample of features.
 
Last edited:
@Roxanne what really impressed me is we need to consider is a huge company that uses very strict procedures and quality control, and it needs to follow a hierarchy, and the human factor, all this "should" cause delays
I mean... is not like in homebrew scene where someone publishes something and in 24 hours everybody knows about it and are free to install it

I guess when the sony software team compiles a firmware they needs to send an advise to get the approval of other person higher in the hierarchy, then that person sends an advise to the factories where are produced the PS3's also to the other factories that are pressing the bluray games, then the directory of the factories sees the advise with the note "use this as soon as posible" and they could take his time (each facory could have a different delay)
Also, maybe is needed to update the online servers where they stores the info about his production, etc...

Probably there are many links in the chain, but some of the first PS3 firmwares have a difference in the builddate of only 6 days, thats a bit awesome considering all this, they was working at the speed of light a chinese
 
Would there be any chance of getting even just a basic cobra with debug output and background FTP just on 2.70 or 2.80?

I think it would be much easier to port IRISMAN and Mamba 2.x (since it doesn't have PS2 & PSP emulation) to 2.70 or 2.80.
Mamba 3.x has the same level of difficulty as Cobra.

Or maybe dev_blind enabler and OpenPS3FTP / BlackBox FTP could be enough for your tests...

Unfortunately I'm too busy lately to help you...
 
@Roxanne what really impressed me is we need to consider is a huge company that uses very strict procedures and quality control, and it needs to follow a hierarchy, and the human factor, all this "should" cause delays
I mean... is not like in homebrew scene where someone publishes something and in 24 hours everybody knows about it and are free to install it

I guess when the sony software team compiles a firmware they needs to send an advise to get the approval of other person higher in the hierarchy, then that person sends an advise to the factories where are produced the PS3's also to the other factories that are pressing the bluray games, then the directory of the factories sees the advise with the note "use this as soon as posible" and they could take his time (each facory could have a different delay)
Also, maybe is needed to update the online servers where they stores the info about his production, etc...

Probably there are many links in the chain, but some of the first PS3 firmwares have a difference in the builddate of only 6 days, thats a bit awesome considering all this, they was working at the speed of light a chinese

Yes, that sounds realistic. Such mentioned work from Sony is also the reason why mostly every Direct Hyperlink to the newest .PUP-Update-File shares an older Date compared to the actual Release Date.

Example from the newest PS4 Update-File Version 6.72 (Release Date: 16th July 2019): http://djp01.ps4.update.playstation.net/update/ps4/image/2019_0709/sys_f3a31f64d894dc06040498cd7383bec2/PS4UPDATE.PUP
 
Back
Top