By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Random Canadian on 25 April 2010
Edit Thread
slowmo said:
Random Canadian said:

Custom FW with out a way to deploy it is useless, its about the same as downloading a PS3 exclusive and burning it to a BDR with no way to load the disc.

 

"Just to highlight the bolded that this is another potential bonus of better understanding the FW, it could potentially open up the possibility of fixing some of the more obscure faults like the red error screen which could be nand related too. If you can dump the nand and fix corrupted parts of it there is some potential to be able to fix these faults without having to pay the first party premium."

 

There is still no practical way to write to the nand and with out something like pandoras battery to put the system into service mode and make it flash the nand with a new FW.

 You can take your system with the red error screen, dump the nand, find the fault(Big fat maybe), Fix the fault (bigger fatter maybe) and reflash ONLY if you have geo-hacked your PS3 through shocking the system bus (lol) seems easier to update the system which would flash the nand and fix the problem, If it were indeed a corrupted file in the nand.

 

I feel like im talking in circles.

There is already a method of deployment found is my understanding, I don't know what you're on about there.  I know there is no way to write to the nand, you brought that subject up, NOT ME.  It was a hypothetical situation of how CFW can benefit people, thats all.

The NAND or ROM or whatever you want to call it is where the firmware is stored , if you are admitting that there is no (practical) way to write to it then you are also admitting that there is no method for deploying custom or modified firmware. 

 

What the hell does Pandora's battery have to do with the PS3?  I highly doubt we will ever get into the service mode for flashing the nand, everything in that regard will be a hardware hack to write and dump.  Even then it might not be useful to do that given the firmware is split between nand, HDD and the locked SPE.

 

Assuming that PS3 FW is anything similar to PSP, then it would stand to reason that only lesser used modules are stored on the HDD for the FW to use and save on space in the NAND and or system ram footprint.

 

SPE is used to un/encrypt and execute functions in the XMB and probably only stores the keys to decrypt the firmware and not any actual part of the firmware itself.

Installing CFW on PSP in the early days was a lot more difficult and resulted in a lot of bricks, with the discovery of the battery being able to put the unit into service mode and being able to have direct access to the nand through usb ment anyone could now easily mod their systems.  This took YEARS on an already fully hacked system.  There will not be an Everyman usable deployment method for accessing the nand on the ps3 for a long, long time.  Making any not so imminent release of a now pointless (no deployment) solution to your problem, a laughable notion.

 

Oh and I wanted to add that Xbox(1) = best EMU box ever.

softmodding xbox's was fun back in the day.