| 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.
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.
