Here is a chat log with KaKaRoTo
[07:28:39] <KaKaRoTo> heri, docpaul showtime would work fine
[07:28:58] <sandungas> kakaroTo, this means new tcl patches for mfw and some changes to manage 3.73 ?
[07:29:17] <KaKaRoTo> ddoo, and no I didn’t fix the npdrm algo, that’s what I’m missing (hence the “kind of”) but I’m not
working on that, that’s someone else’s job
[07:30:05] <middleman> gonna debut it at ccc kakaroto or before?
[07:30:06] <KaKaRoTo> ddoo, and even if npdrm signing worked.. how do you install your pkg on an OFW 3.73 ?
[07:30:22] <heri> so KaKaRoTo, once the NPDRM algo is fixed, a release will come?
[07:31:14] <KaKaRoTo> heri, another missing bit, but once that’s fixed, yes
[07:31:23] <KaKaRoTo> but I’ll probably be off country for the next 2 weeks
[07:31:30] <KaKaRoTo> so all work will have to be paused
[07:31:52] <heri> oh, fair enough. we can all wait 2 weeks hey :P we have waited months anyways
[07:32:06] <KaKaRoTo> ddoo, that might work.. you could also just install your pkg on 3.55 then upgrade…
[07:32:20] <KaKaRoTo> ddoo, upgrading doesn’t delete any of your packages
[07:32:37] <KaKaRoTo> ddoo, issue is, you’re lost if you didn’t do it before upgrading
[07:32:53] <ddoo> but they fail because the npdrm algo is spoted by the checks in 3.56+
[07:33:13] <KaKaRoTo> heri, also note, I “announced” it because I was excited to see it work as expected
[07:33:22] <KaKaRoTo> doesn’t mean it’s ready for release
[07:33:31] <KaKaRoTo> ddoo, exactly
[07:33:36] <heri> yeh thats what we were saying just before you came
[07:33:43] <KaKaRoTo> so you need : 1 – npdrm algo fixed, 2 – a way to install stuff
[07:33:53] <heri> you only announce when you are confident it works
[07:33:58] <KaKaRoTo> 1 has been done by someone else (don’t know if he’ll share it), and 2.. well, I just did it
[07:34:37] <KaKaRoTo> heri, well, I was testing on 3.60 and it worked, but yes, I did upgrade to 3.73 to test that it still
works just to make sure I don’t tweet any false hopes
[07:34:46] <middleman> but you cant run what you installed until 1 is fixed correct?
[07:34:59] <KaKaRoTo> middleman, exactly
[07:36:17] <middleman> interesting
[07:36:19] <docpaul> nice, thx KaKaRoTo
[07:36:40] * KaKaRoTo needs to hide now if he wants to get any work done
[07:36:42] <KaKaRoTo> ttyl
[07:28:58] <sandungas> kakaroTo, this means new tcl patches for mfw and some changes to manage 3.73 ?
[07:29:17] <KaKaRoTo> ddoo, and no I didn’t fix the npdrm algo, that’s what I’m missing (hence the “kind of”) but I’m not
working on that, that’s someone else’s job
[07:30:05] <middleman> gonna debut it at ccc kakaroto or before?
[07:30:06] <KaKaRoTo> ddoo, and even if npdrm signing worked.. how do you install your pkg on an OFW 3.73 ?
[07:30:22] <heri> so KaKaRoTo, once the NPDRM algo is fixed, a release will come?
[07:31:14] <KaKaRoTo> heri, another missing bit, but once that’s fixed, yes
[07:31:23] <KaKaRoTo> but I’ll probably be off country for the next 2 weeks
[07:31:30] <KaKaRoTo> so all work will have to be paused
[07:31:52] <heri> oh, fair enough. we can all wait 2 weeks hey :P we have waited months anyways
[07:32:06] <KaKaRoTo> ddoo, that might work.. you could also just install your pkg on 3.55 then upgrade…
[07:32:20] <KaKaRoTo> ddoo, upgrading doesn’t delete any of your packages
[07:32:37] <KaKaRoTo> ddoo, issue is, you’re lost if you didn’t do it before upgrading
[07:32:53] <ddoo> but they fail because the npdrm algo is spoted by the checks in 3.56+
[07:33:13] <KaKaRoTo> heri, also note, I “announced” it because I was excited to see it work as expected
[07:33:22] <KaKaRoTo> doesn’t mean it’s ready for release
[07:33:31] <KaKaRoTo> ddoo, exactly
[07:33:36] <heri> yeh thats what we were saying just before you came
[07:33:43] <KaKaRoTo> so you need : 1 – npdrm algo fixed, 2 – a way to install stuff
[07:33:53] <heri> you only announce when you are confident it works
[07:33:58] <KaKaRoTo> 1 has been done by someone else (don’t know if he’ll share it), and 2.. well, I just did it
[07:34:37] <KaKaRoTo> heri, well, I was testing on 3.60 and it worked, but yes, I did upgrade to 3.73 to test that it still
works just to make sure I don’t tweet any false hopes
[07:34:46] <middleman> but you cant run what you installed until 1 is fixed correct?
[07:34:59] <KaKaRoTo> middleman, exactly
[07:36:17] <middleman> interesting
[07:36:19] <docpaul> nice, thx KaKaRoTo
[07:36:40] * KaKaRoTo needs to hide now if he wants to get any work done
[07:36:42] <KaKaRoTo> ttyl
It seems that a lot of misunderstanding has been going on about the jailbreak announcement made by KaKaRoTo, with that being said he has updated his blog with what seems to be information about his jailbreak and explanation as to what is to be expected by it. Here it is straight from his blog.
Spoiler
Hi all,
I’ve been flooded with questions on twitter and I’ve read many posts on news sites and I’ve seen some stuff being said on IRC and I thought I needed to clarify a few things…
First of all, I didn’t expect to see my tweet front paged on all ps3 hacking news sites.. although I should have expected it.. but anyways, the “jailbreak” is not ready to be used, at all. I only tweeted that because I was excited having it working and I wanted to share my excitement with everyone. But this is a bit equivalent to the day I released that create_cfw.sh script that created the very first CFW/MFW but it still took a couple of months before a real, easy, multiplatform and fully fledged solution was released : PS3MFW.
We are currently at the same state, I have the proof of concept, it works, but a solution that anyone can use where they just click a button and their PS3 gets jailbroken is still far from ready.
I’ve seen people say (and even write it in their front page news) that I’ll release it in two weeks after I come back from vacation. That is not true and I never said that. What I said was that for the next 2 weeks, the project is on hold until I get back.. but when I get back, then I will continue working on it, and it will then take some more time before it’s ready and released.
Some asked if it’s based on what gitbrew was doing/suggesting or if I used someone else’s exploit or work. No, this solution is my own idea and 100% my own implementation. However, the actual solution for the full jailbreak involves some components on which I will not work, and I expect/hope that someone else will provide the solution for that.
Some speculated it might be what I spoke about back in March which I later said I wasn’t pursuing by lack of motivation.. and yes, you are right. The same hack I had in March is still valid today, I told a few people about it (rms, Mathieulh, an0nym0us, and a couple more), but no one was interested in pursuing it further and actually exploiting that flaw (mainly because it requires a huge amount of work to get a proof of concept working). 10 days ago (I started on the 11th), I got bored and decided to start poking at it again, and yesterday (a lot faster than I thought it would take), I got my first pkg installed on 3.73 firmware.
On twitter, I said “do not update if you are on 3.55″, I said that in response to someone who said he would update. Because of that, people speculated that you need to be on 3.55 first, and then install something before doing the upgrade. No, that’s not it, that would be useless. The purpose of my solution is to jailbreak a ps3 that is already on 3.73 firmware and which had never been jailbroken before. I told people not to update because, first of all, it’s not yet ready, and second of all, the 3.55 firmware gives you a lot more possibilities than what can be achieved on 3.73.
So what is this jailbreak? I won’t say because I don’t want Sony to block it in a firmware update (and yes, they potentially could) before it’s even released (and yes, I will release it when it’s ready). But I will explain this to you : in order to run your homebrew apps, you need two things. First, to be able to install them on the ps3, and second to be able to run it once installed. I did only one of these two things.
Some may say it’s not a real jailbreak, but the way I see it, there are three ‘jails’ on the ps3, I broke the first one which prevents you from installing anything, so now you can install your .pkg, great, but it won’t run, that’s the second jail. The third jail is being able to modify the firmware (peek&poke).
The second jail (running apps) is something that can be done, but it’s not my area of expertise (npdrm algo), so I will not be working on that. I am waiting for someone else to achieve it (some have succeeded but do not wish to release it, at least not for now) then I will release.
The third jail (modifying the firmware) is not possible with my method, this means that you will not have a “CFW”, you will run your homebrew applications and games on an official firmware. This also means that without peek&poke support, none of the backup managers will work. So, again, my solution is piracy-free, and as always, I do not plan on working on a way to enable piracy (or even legal backups).
Overall, the purpose will be to allow people who are on 3.73 firmware to enjoy the homebrew games that were released, to play a bit with Eskiss, and to use Showtime for playing their movies. This should be more than enough for everyone.
Finally, I will conclude by replying to another question I received : Do you accept donations? The answer is yes. I do accept donations but I do not seek them out. I will include a donate button to the bottom of this post, so if anyone wishes to donate, they can do so, however, I want to make it clear that whether or not you donate does not and will not affect in any way, the release, or the progress of the work I’m doing. If you donate, you would do it as a sign of appreciation of my efforts, and not in exchange of any favors or anything crazy like that.
That’s about it I think… If you have any more questions, please refrain from asking them, I get enough as it is already.. I also said everything I needed to say and I don’t want to give any more information than that (for now).
KaKaRoTo
I’ve been flooded with questions on twitter and I’ve read many posts on news sites and I’ve seen some stuff being said on IRC and I thought I needed to clarify a few things…
First of all, I didn’t expect to see my tweet front paged on all ps3 hacking news sites.. although I should have expected it.. but anyways, the “jailbreak” is not ready to be used, at all. I only tweeted that because I was excited having it working and I wanted to share my excitement with everyone. But this is a bit equivalent to the day I released that create_cfw.sh script that created the very first CFW/MFW but it still took a couple of months before a real, easy, multiplatform and fully fledged solution was released : PS3MFW.
We are currently at the same state, I have the proof of concept, it works, but a solution that anyone can use where they just click a button and their PS3 gets jailbroken is still far from ready.
I’ve seen people say (and even write it in their front page news) that I’ll release it in two weeks after I come back from vacation. That is not true and I never said that. What I said was that for the next 2 weeks, the project is on hold until I get back.. but when I get back, then I will continue working on it, and it will then take some more time before it’s ready and released.
Some asked if it’s based on what gitbrew was doing/suggesting or if I used someone else’s exploit or work. No, this solution is my own idea and 100% my own implementation. However, the actual solution for the full jailbreak involves some components on which I will not work, and I expect/hope that someone else will provide the solution for that.
Some speculated it might be what I spoke about back in March which I later said I wasn’t pursuing by lack of motivation.. and yes, you are right. The same hack I had in March is still valid today, I told a few people about it (rms, Mathieulh, an0nym0us, and a couple more), but no one was interested in pursuing it further and actually exploiting that flaw (mainly because it requires a huge amount of work to get a proof of concept working). 10 days ago (I started on the 11th), I got bored and decided to start poking at it again, and yesterday (a lot faster than I thought it would take), I got my first pkg installed on 3.73 firmware.
On twitter, I said “do not update if you are on 3.55″, I said that in response to someone who said he would update. Because of that, people speculated that you need to be on 3.55 first, and then install something before doing the upgrade. No, that’s not it, that would be useless. The purpose of my solution is to jailbreak a ps3 that is already on 3.73 firmware and which had never been jailbroken before. I told people not to update because, first of all, it’s not yet ready, and second of all, the 3.55 firmware gives you a lot more possibilities than what can be achieved on 3.73.
So what is this jailbreak? I won’t say because I don’t want Sony to block it in a firmware update (and yes, they potentially could) before it’s even released (and yes, I will release it when it’s ready). But I will explain this to you : in order to run your homebrew apps, you need two things. First, to be able to install them on the ps3, and second to be able to run it once installed. I did only one of these two things.
Some may say it’s not a real jailbreak, but the way I see it, there are three ‘jails’ on the ps3, I broke the first one which prevents you from installing anything, so now you can install your .pkg, great, but it won’t run, that’s the second jail. The third jail is being able to modify the firmware (peek&poke).
The second jail (running apps) is something that can be done, but it’s not my area of expertise (npdrm algo), so I will not be working on that. I am waiting for someone else to achieve it (some have succeeded but do not wish to release it, at least not for now) then I will release.
The third jail (modifying the firmware) is not possible with my method, this means that you will not have a “CFW”, you will run your homebrew applications and games on an official firmware. This also means that without peek&poke support, none of the backup managers will work. So, again, my solution is piracy-free, and as always, I do not plan on working on a way to enable piracy (or even legal backups).
Overall, the purpose will be to allow people who are on 3.73 firmware to enjoy the homebrew games that were released, to play a bit with Eskiss, and to use Showtime for playing their movies. This should be more than enough for everyone.
Finally, I will conclude by replying to another question I received : Do you accept donations? The answer is yes. I do accept donations but I do not seek them out. I will include a donate button to the bottom of this post, so if anyone wishes to donate, they can do so, however, I want to make it clear that whether or not you donate does not and will not affect in any way, the release, or the progress of the work I’m doing. If you donate, you would do it as a sign of appreciation of my efforts, and not in exchange of any favors or anything crazy like that.
That’s about it I think… If you have any more questions, please refrain from asking them, I get enough as it is already.. I also said everything I needed to say and I don’t want to give any more information than that (for now).
KaKaRoTo
[UPDATE 2]
Here is a simple FAQ of a Q/A written out by eussNL posted on the dev wiki.
Spoiler
Q&A
Q: Will I need special hardware?
A: No.
Q: Will homebrew work?
A: With NPDRM fixed, yes. Showtime would certainly be possible.
Q: Will recent games play correct
A: Yes, its 3.7x, sure it plays all 1.00 - 3.7x games.
Q: Does it have Peek& Poke?
A: No.
Q: Do Backup manangers work?
A: No, see previous answer.
Q: Does it gets us keys
A: No.
Q: Does it gets us "CFW"/MFW?
A: No.
Q: Will it allow downgrade?
A: No.
Q: So why are all the newssites hyping this that it does?
A: Because they don't read wiki's/blog's xD Besides, every minor news gets 'prolly CFW soon!' tagged by the bad ones.
Q: Is there a release date?
A: No, besides KaKaRoTo not able to work on it for 2 weeks, it also relies on (other people?) fixing NPDRM.
Q: Will I need special hardware?
A: No.
Q: Will homebrew work?
A: With NPDRM fixed, yes. Showtime would certainly be possible.
Q: Will recent games play correct
A: Yes, its 3.7x, sure it plays all 1.00 - 3.7x games.
Q: Does it have Peek& Poke?
A: No.
Q: Do Backup manangers work?
A: No, see previous answer.
Q: Does it gets us keys
A: No.
Q: Does it gets us "CFW"/MFW?
A: No.
Q: Will it allow downgrade?
A: No.
Q: So why are all the newssites hyping this that it does?
A: Because they don't read wiki's/blog's xD Besides, every minor news gets 'prolly CFW soon!' tagged by the bad ones.
Q: Is there a release date?
A: No, besides KaKaRoTo not able to work on it for 2 weeks, it also relies on (other people?) fixing NPDRM.
This is only for those that are on 3.73, those that aren't please remain on 3.55
Source
Via KaKaRoToKS twitter
PS3HAX
Via KaKaRoTo's blog
KaKaRoTo's FAQ about the new jailbreak
[PSX-Scene: Brought to you by The T-Team! News to a T!]
Daily Digest
Recent Threads
Recent Comments
vBulletin Message