As others stated, those consoles won't update. 3.56 included new encryption/signatures that we can't create ourselves. We can decrypt and verify a signature, because we know the public keys, but we can't create a PUP that a console already flashed with 3.56 will accept.
Originally Posted by Zumb4l4
Those consoles may be patchable using a NAND or NOR flasher... it may be possible, given the Waninkoko Brick solution, which flashes lv2kernel.self over a corrupted version, but there simply is no way, technically, to use the 3.56 firmware's recovery mode or system update to flash a custom firmware because we cannot sign/encrypt the files it will be looking at.
I agree, somewhat, there is no reason for a 3.56 CFW, but it would be nice to at least see a proof-of-concept; a version with the loaders patched to 3.55 keysets, revocation lists rolled back, and the new firmware protection removed. This will be a challenging task, and I'm not sure who would be up to it, but it won't come from somebody who's never done anything significant in the scene.
Working hard on UberCFW, incorporating NTFS, sub-free NetFlix and Blockbuster, PSN cheat system with built-in swearbot and MAC-spoofing, Adding MKV, RAM and BIK movie support, and Xbox360 emu*.
*not really. Get a life, newbs...
My YouTube channel: http://www.youtube.com/user/BenJeremy