28w ago - Following up on the PS3 Factory 3.56 with Flasher news, French PlayStation 3 developer raymanvtwo has shared a way to install Rebug PS3 CFW 4.21.1 on any version PS3, however, it requires a PS3 Hardware Flasher, will format your HDD and may result in a permanently bricked console so be WARNED!
Below is a rough translation of the process, as follows: You will need just a flash, great care, attention and rigor.
This method will format the hard drive of your PS3, make sure to recover your important data. Also, you incur a risk of irreversible brick in case of bad handling. Neither I nor PS3-Addict can not be held responsible. If you are not able to follow this tutorial to the letter, thank you spend your way!
Firstly, ensure the validity of your dump, flow rebuilder is the best in the field. Also check that all your fichiez is a different size of 0 bytes (including bootloader_0). If there is a problem, it will help you out.
Now that you have your dump, to see if the offset 200 if you or IFI FI.I with HxD as hexadecimal editor. If you IFI, go to the next step. If you FI.I, open flow rebuilder Select "Byte reverse and extract a NOR dump file." and then made your dump "execute operation". If you get an error is that your dump is not good. Before you dump, you must make new bytes reversed under penalty brick your PS3 but it will be easily retrievable.
Now, you need winskeet and patch (here and here or mirrored here). Winskeet open, go to the tab "patch" in "input file", select your dump file and select the patch. Txt file previously downloaded the archive. Made apply and save your dump patched.
Now write your dump patched (do not forget to do it again if you had reversed bytes FI.I at the top). Now your PS3 Decomposition Systems is no longer able to work, do not worry, this is normal. Go to the recovery menu (it may be that your PS3 shuts herself at the first attempt, the second should succeed). Install CFW Rebug 4.21.1 (available via the "system update").
If after several attempts you are unable to install Rebug CFW 4.21.1, format the HDD, then reinstall the switch on the PS3. On a USB drive to FAT32, put the. Rebug 4.21.1 CFW PUP (available here and here) in x: \ PS3 \ update and rename it to PS3UPDAT.PUP. You will get a message asking to connect a controller and press the PS button, then follow the plug your USB drive, make sure there is no disc in the drive BR, then press START and SELECT at the same time for 3s and follow the instructions to install your CFW. Enjoy.
PS: This method has been tested with the Rebug CFW 4.21.1, if you use another CFW, it will be at your own risk. This method has been tested on a PS3 with the metldr "anti CFW 3.55", it should work on any console. Thank you to give me a feedback on the effectiveness of this method and possible problem. Thank you also include PS-addict and I and keep the links given in this tutorial if you publish on your sites this method.
Finally, thank you to the work of the "Three Musketeers" and the Rebug team has allowed me to patch my PS3.
From Cyberskunk: Tested on my 3K series.. DOES NOT WORK (didn't think it would)..
From Rogero: Tested here also on a 3K machine, didn't work, it bricked... metldr .2 and lv0.2 won't be easy to bypass....
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
it won't work anyway cause the 4.30 custom firmware has been resigned using old bootloader console keys, 3000x series has new keys but to bypass the flasher problem extract the coreOS from the 4.30 custom firmware and you need to byte reverse it and paste it into your nor backup at offsets 0C0010 & 7C0010 using a hex editor
its because newer consoles have a minimum firmware version of 3.60 or higher and will never support 3.55 or below sony blacklisted the private key that geohot found in newer firmwares and new consoles also have new boot loader keys so you cant flash a custom coreOS onto a 3000x or higher cause they have been signed with the old bootloader keys.
if by some miracle the new private keys can be calculated then all the new consoles would be jailbroken again but this is highly unlikely now that sony use a true random number to generate them