This is just a rough version and the process for end users will be a lot simpler.
Step 1: Go to libusb and download and install the lib USB driver.
Step 2: Paste this link into your browser and download Updater: HERE
Step 3: Unzip the file and run the program updater.exe
Step 4: Plug in your PSJailBreak USB unit and click the My Serial Number Button on the top left of the window.
Once this is done you will have to email us back your serial number from the same email account we sent you our email.
We will then generate the files for each individual serial number and email you back the file to update your USB unit.
Please remember that for end users, the lib USB driver will already be built in to the updater program and users updating files will automatically be generated after clicking the My Serial Number Button, so the process will be very simple.
Please get back to us asap with your individual serial numbers.
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!
You are probably right Tommasi. They probably purposely worded it so it seemed like they meant 3.50 FW support but what they will release will be 3.50 Game support.
I reckon its possible the psjailbreak guys might have had the original hack ready and in testing for a while but waited for PSmove's release , as it might have been a dealbreaker for some who considered getting it, if it meant no psn AND no move support it would not be as appealing.
Anyway I think people don't realise how long we could have been waiting for a PS3 hack like this, It might have never happened as security will only get tighter over the next years. I hope that the guys who put the time into this hack made nice money early on of pirating kids who preordered, the kind of kids who wouldnt have been bothered/able to flash hexs and ftp an stuff, for them it was worth the price of 2 or 3 games! imagine how long it took to develop and test payload and BM until it got to a level ready for retail release at the same time not letting it leak before they were ready!
Wonderkik: That was a common misconception when rumours of jailbreak first came out, but it is since proved to be a proper hack.
It just uses the power and eject start sequence to initiate, also it uses the sony jig ID during exploit but this is not anywhere near a real sony jig, This works pretty much like an old school psp buffer overflow exploit, put simply it confuses ps3 into writing to an area of memory it not meant to allowing an xml to be patched along with a few hyperviser patches to stop ps3 panicing.
Anyway aside from that I really think these guys haven't got half the credit they deserve, I find it extremely hard to believe that that some random new hacker/team popped up with this as a first piece of work on the scene. I see it being much more likely that either:
It's a sony leak, an employee who knows ps3 inside out and has tried to cash in (Why not, I probably would in that position!)
It's an already well known dev or group possibly from psp or 360 scene, but they are staying quiet due to inevitable backlash for not releasing it for free and legal problems (I'm thinking BIG well known name if this is the case, I have no problem with them charging really, their time and they can charge for it whenever the want)
It was something to do with geohot as he dumped the hardware and might have seen this bug in code somehow. he seemed to be making headway on ps3 very quickly and even said he could make a 3.21 that would retain otherOS, not really a guy to talk crap either, then he just stoppped. maybe he sold his discovery to a thirdparty (so Jailbreak name is maybe not just a coincidence!)
Possibly There was just a lot of money and people thrown at the problem by a big company, enough paid devs working on a console for months would probably find a hole!
To me it seems impossible for this to be developed slowly from scratch by a unknown dev or devs as the amount of trial and error involved to get the hack to this stage would be ridiculus especially when the dev would have no way of knowing if each step was successful unless all steps succeeded.
I would be very suprised is this story turns out to be true about 3.42 - 3.50, jailbreak team are good but I doubt they are that good! I still hope its true though, maybe original jailbreak devs did discover more exploits and they only released this one!
The rumored 3.42 / 3.50 "support" might be also just support for PLAYING games requiring FW higher than 3.41 or some kind of patching 3.41 firmware PRIOR it's update to allow it still to be JB-en hence however is already on 3.42 or 3.50 might be still out of game anyway ...