ps3 downgrade / dual nand protections ?

[diddledoo]

Hi

is there any protectection system in the ps3 that prevents me from changing my nand with a flash chip to every firmware version i want to (or have a backup). i mean solder a nand reading chip in the ps3 read out the nand, than update to 3.42,  can i than reflash thenthe 3.41 and everythings like before updating ?

like the cpu-fuses in the x360... or any other protection

if not, we just need to make a dual nand setup, and we can switch from our "homebrew nand", to the "online nand"
(just like the cygnos chip for the 360 that is pretty useless now cause u cant really switch kernels cause of different fuse-configurations in the cpu)

also, if u dont have a second nand, it would be at least a good update-protection, to have a nand backup of your own ps3 for reflashing

[inspuration]

Once you upgrade you can never go back.

[sbmotoracer]

You mean like the infectus modchip?

http://www.infectus.biz/developer-features.php

[inspuration]

You mean like the infectus modchip?

http://www.infectus.biz/developer-features.php

The infectus does not allow downgrading the nand. Once the PS3 is updated you cannot downgrade.

[diddledoo]

where / whats the protection ?

yea i mean with the infectus chip or similiar stuff, no matter what u just need a simple usb-io chip

if i have made my very own nand backup eg 3.41, what prevents me from reflashing old backups to the nand?
what stops them from running ? how should the ps3 know ? there aint no efuses in the ps3

if i have my 3.41 backup with my key bla bla.... why should i not be able to reflash it after maybe accidently updating to 3,42

thats not really downgrading, just reflashing the nand versions that were back-uped before

in my opinion we should start with making a nice reuseable nandbackup, BEFORE sticking ANYTHING in the usbport
sony will f*** around more than ms with the jtags, in my opinion sony is s.o. who starts editing exploitable consoles secretly in the background, as we can see they think they can do whatever they want with "their" sold consoles,

thats for sure, backing up is always the first step<--

what hardware/software protection of the ps3 should prevent s.o. from reflashing his own nand images he made from the same ps3 ?
i dont know of any protection against that, and the only working protection i know against something like that is the efuse stuff which the ps3 doesnt have

with a nand and hdd backup, i dont see anything that prevents me from making a hacked console virgin again

is there data/hardware anywhere else that can be modified by sony , anywhere else then on nand and hdd ? (like in the cpu with the x360 fuses)

[Arakon]

There ARE efuses in the PS3.

[diddledoo]

thats pretty much information....

does that mean ps3 uses the efuses for the same purpose than x360, blowing a efuse every important update ?

if thats the case it would be pretty useless to make a CLEAN nand backup before using psgroove
i thought it may be wisly for future coming ps3 stuff, to have a clean nand backup
but if you really will never be able to go online again (with another nand with another firmware revision) buying a infectus would be a waste

is there any documentation about the efuse stuff ?

[ChipD]

Arakon is correct.The PS3 uses efuses similair to the efuses on the 360.Before infectus forum went down, there was a few members working on ps3 flashing utility that worked with the infectus because ps3 support was removed from the official infectus software.You can also use amoxiflash made by team twiizer member bushing.But its for linux and you will have to compile it yourself.I know somebody had ported it to windows but i dont know if that version has ps3 nand support added.

To be honest though, your better off waiting for a method of dumping the entire nand via homebrew app.I dont think it will be too much longer before were able to backup, and flash custom fw with the press of a button(ps3 controller button that is).

[mathieulh]

There ARE efuses in the PS3.

Those are only used at factory (to store the per cpu root key) and cannot be blown through software.

To prevent downgrading, hashes are written in the syscon's eeprom.