57w ago - It was just a week ago since the previous PlayStation 3 System Software update arrived, but today Tempest_Fire of Sony PlayStation Support has announced that PS3 System Software Update v4.31 is incoming tonight with details below!
To quote: Hi everyone, I'm posting this message to inform you that there will be a minor firmware update (v.4.31) released on the evening of Monday, October 29th.
There will not be PlayStation Network maintenance during this time; online play and access to apps will not be affected during the release of this update.
This is not a mandatory update. However, we suggest you keep your systems updated with the latest firmware, as these updates further improve overall system stability and help provide you with the best online entertainment experience possible.
To update to v.4.31, select Settings from your Xross Media Bar (XMB) > System Update > Update via Internet and then follow the on-screen instructions.
More information about PlayStation system updates can be found here: http://us.playstation.com/support/systemupdates/
Digital Platforms Community Manager
Sony Computer Entertainment America
From their Twitter: "If you've had issues with Monster Hunter Portable 3rd HD, download the optional PS3 software update (v.4.31)"
From afiser on the PS3 Keys posted above: This is as simple as putting the bootldr keys (what you all call the lv0 keys released last week) in the scetool data/keys file and running scetool.exe -d lv0 lv0.elf
From zadow28: Found some interesting, when debugging lv1.elf from 4.31:
seg000:0000000000001850 ld r8, qword_532688 # "QA_FLAG_QA_MODE_ENABLE settle\n"
seg000:0000000000001854 clrrdi r0, r10, 16
seg000:0000000000001858 std r11, 0x40(r3)
seg000:000000000000185C or r0, r0, r9
seg000:0000000000001860 std r8, 0x10(r3)
seg000:0000000000001864 std r0, 0x18(r3)
seg000:0000000000001868 std r10, 0x48(r3)
seg000:000000000000186C # End of function sub_1840
seg000:0000000000001870 # =============== S U B R O U T I N E =======================================
seg000:0000000000001870 sub_1870: # CODE XREF: sub_1BD0-FCp
seg000:0000000000001870 ld r8, 0x18(r3)
seg000:0000000000001874 rlwinm r0, r8, 0,16,16
seg000:0000000000001878 cmpdi cr7, r0, 0
seg000:000000000000187C beq- cr7, loc_18D0
seg000:0000000000001880 lbz r0, 0x728(r3)
seg000:0000000000001884 cmpwi cr7, r0, 0
seg000:0000000000001888 bne- cr7, loc_18C4
seg000:000000000000188C loc_188C: # CODE XREF: sub_1870+5Cj
seg000:000000000000188C ld r11, qword_532688 # "QA_FLAG_QA_MODE_ENABLE settle\n"
seg000:0000000000001890 li r0, -1
seg000:0000000000001894 ld r10, 0x10(r3)
seg000:0000000000001898 clrrdi r9, r8, 16
Only shows when debugging.. well thats where i'm at so far regards.
Dumps/Debug off core_os/Devflash files. 4.++
Have done some experimenting. Found out that you can actuelly run the self/sprx (ppc)
From core_os, and Devflash.. from "official" debugger,and dump them. You have to set up an fake Param.sfo, so the debugger thinks its an executable.. but the result is quite amazing. You really get an better overview, since you can see al the files it communicates with.
I use Ida pro 64 PPC proccesser to analyze, the dump. Then use Kakarotos scrips analyze_sprx.idc. Set new TOC, when the script tell you and reanalyze.
The dump is 4mb packed but 250 mb unpacked. I'll give an more deeper, TUT when i have the time. Works on all files so far i tested PPC ones, so all expect the spu files. Tested vsh.self/mcore.self/psp_emu.self plus many more.
Well here is the dump, for BDVD.SELF: http://rghost.net/41639087
Off course you can debug all the files, and the embedded spu before dumping.
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!
That's not how It works buddy, you need a flasher to downgrade back to 3.55 before installing 3.55+ CFW. I thought being on the scene for years would be enough for you to understand that.
I've already answer that a few times, so did a lot of people. 3.55+ OFWs have better checks that stops you from installing CFWs. Can we bypass that? Probably not.
For example, 3.55 OFW have MD5 = A, 3.55 Rogero CFW have MD5 = B and 3.55 Kmeaw CFW have MD5 = C, all of them have different MD5, thus the installer can see the difference between the FWs. That was just an example though, people already managed to break MD5 security, so they are going with a better hash algorithm. In short, we don't have the right keys.
The reason for me to believe we won't bypass that security is because even some not so recent algorithms, like, SHA-2, that has been published in 2001, still haven't been hacked yet and there are probably more people trying to hack It than the PS3.
XBINX Cyro: Already seen some people confirming it works, but unless this gets new features people may want to stick to Rogero as he seems to be the most trusted dev working on CFWs right now.
hello all, I managed to get my E3 installed! I have managed to get proper backup of a phat chech-h and downgraded to rogero as followed in the tutorials.
I have a few pictures i can post.. it was very easy.. sony i guess is releasing a new update 4.31? I"m quite unfamiliar with what CFW i should be on now i have a flasher.. I will be taking requests (serious) for firmware testing here in the future if anyone has suggestions.. any try ermac 4.30 yet?