The above video goes away if you are a member and logged in, so log in now!
Just a quick reply from Math on his twitter,
"@x3MAXcom There is no such thing as a "ps3 master key". Stop saying utter crap kthx. There are even several keys when it comes to signature."
Originally Posted by Jon Salat
my initial idea would be to modify the PSgrade code so that at the end insdead of loading the LV2DIAG.self it would for instance load XXXX.what ever on the micro SD slot inside the X3MAX (kind of like the E3 downgrade works loading the lv2diag.self from internal memory) that file being the payload and re exploiting the system on current firmware (as the payload acts as a USB hub being plugged in and out repetitively)
something along the lines of that method would give our payloads boot priority again
but your saying that is what the original PSJB did?
PSJB didnt act like a USB hub like the rest of our payloads?
I'm not here to fight
Originally Posted by safin
It's just sickening to see many other people gettin' there hopes up for probably nothing. Stores are giving refunds until Dec 22 2010, so it would be pretty sour if X3Max takes beyond Dec 23th to release anything other than a TXT/JPG/VID (which should get them enough time to sell this old dongle in a new SKU) and it either is proven fake or reversed for any flashable dongle/AVR/PIC out in the world.
Loading of LV2DIAG.self is softwired in the PS3 bootproces. The LV2DIAG.self we now use, is the Sony signed file that was leaked >805 days ago (from a Japanese Slim JIG?). Afaik if you need to load 'XXXX.SELF' instead of 'LV2DIAG.self' you need CFW and/or access to SYSCON flash and still need to sign your own compiled SELF properly.
Originally Posted by korn16ftl
Appldr NPDRM 1.00-3.31 (rev 0x01):00 040AB475 09BED04B D96521AD 1B365B86 BF620A98 / 3.40-3.42 (rev 0x04):00 B61A91DF 4AB6A9F1 42C326BA 9592B526 5DA88856 / 3.50-3.55 (rev 0x07):00 9EF86907 782A318D 4CC3617E BACE2480 E73A46F6
It's a little bit more complicated than that.
Originally Posted by wartutor
This is a wait-n-see issue.
If they do have something to offer, they will release it and it will be cloned.
If not, then there is nothing to talk about.
What is the generic software you loaded on your E3?
Originally Posted by kneehighspy
Doesn't it just work that way with their "Dual Load" Firmware and you drop a k.hex or h.hex file in the "E3_4M_STICK" side?
That 3.15 hex you are linking in you sig doesn't work. (800010009 factory)
Originally Posted by ieder-zijn-meis
An admin bot post... interesting, and that's the only exciting part.
No video, no nothing...
"do our best to prevent, or at least delay that from happening.", in other words, they may never release it even if they are not BS!
And if they are not BS, may be PS3YES will be releasing it 1st
It did act as a USB hub. I thought you were suggesting exploiting the PS3 when it checks the USB for LV2DIAG.self on bootup in product mode.
While I'm not agreeing with them, your logic is wrong. They said when it's ready, as in when they feel they have enough security so it isn't cloned within 24 hours.
Originally Posted by bouma
All news posts are processed through an admin bot now. This is to prevent issues with moving member submitted news to the front page. We had several instances of people editing their posts after they were moved to the front page to include links to shops, etc. The original news submission for this story came from InsideX3, not any staff here.
Originally Posted by totalv
I'm curious as what they consider the "Master Key". They have a little bit of flexibility because of how loose the term is being thrown around. It sounds good. I wouldn't be to terribly surprised if they have something up there sleeves, but not a 3.5x jailbreak in the same sense we have now. If they somehow were able to decrypt the bootloader via direct or indirect methods maybe, but if that was discovered there wouldn't be need for a dongle. Or isolated/decrytped metldr. I guess you could consider those master keys. I would bet my house against either or both of those situations though.