Originally Posted by ps3hen
They switched the offsets inside the NAND/NOR, well thats quite stupid, so no one knows the structure of the NAND/NOR execept DH. So no one's tools expect 'their' tools can patch a NAND/NOR dump for downgrade . Why would someone do that?
|
it seems tno one can really help on demonhades at the moment
i was wondering if to restore 3.56 ma in a working state i could do one of the following:
1) usb:\Lv2diag.self <----dh self
usb:\PS3UPDAT.PUP <---- 3.56 ma same as the one that was installed prior brick (rogero no check v3.1)
usb:\Lv2diag.self <----dh self
usb:\PS3UPDAT.PUP <----rogero no check v3.1 (when this was done it bricked )
2) if 1) will not work how about doing this in advance.cfg :
########################################################
#Restore "rflash" Fichero origen "/dev_usb000/rflash.bin" <------3.56 ma Backuprflash.bin size:262,144Kb
# 0 = Disabled
# 1 = Delete and restore all sectors.
# 2 = Check sectors and only delete/write the differents sectors.(SLOW)
;1
########################################################
#Restore "/dev_flash" from "/dev_usb000/flash1.bin" <------3.56 ma Backupflash1.bin size:204,544Kb
# 0 = Disabled
# 1 = Enabled
;1
########################################################
#Restore "/dev_flash2" from "/dev_usb000/flash2.bin" <------3.56 ma Backupflash2.bin size:16.384Kb
# 0 = Disabled
# 1 = Enabled
;1
########################################################
#Restore "/dev_flash3" from "/dev_usb000/flash3.bin" <------3.56 ma Backupflash3.bin size:512kb
# 0 = Disabled
# 1 = Enabled
;1
all other options set to 0
Originally Posted by ps3hen
So no one's tools expect 'their' tools can patch a NAND/NOR dump for downgrade.
|
that is exactly what i also suspect ,so what about doing it as 1) and 2) as second option with their tools ?can everyone here give me his opinion regarding this . . . this way i should be able to go back to original state instead of the actual brick