[sardine]

Originally Posted by DEFAULTDNB 3.55 is the only console we have all the right keys for which can be made into CFW. When the 3.60 keys came out they were only for signing appldr not for allowing apps to install on 3.60 or anything like that. (Anyone correct me if I am wrong). Those keys couldnt be used to make a new CFW. END OF. TB uses a method of resigning eboots for 3.55. Probably by dumping them unencrypted from ram using the tools out the other day. This way you will never need to update to higher CFW. TB have no desires to open up higher machines to CFW, they just wanted to sell dongles to make money on DRM'd eboots. E3 on the other hand said they might be able to make a higher CFW, which would help a lot of people out. Just dont hold your breath.

Thanks for your knowledge DefaultDNB Goodnight

[sardine]

TB uses a method of resigning eboots for 3.55. Probably by dumping them unencrypted from ram using the tools out the other day. This way you will never need to update to higher CFW. TB have no desires to open up higher machines to CFW, they just wanted to sell dongles to make money on DRM'd eboots.

Hi DefaultDNB are you saying that TB disc if they want they can make it play on higher fw console but they don't want because of their dongle? I,m a bit mix up

[DEFAULTDNB]

Originally Posted by sardine Hi DefaultDNB are you saying that TB disc if they want they can make it play on higher fw console but they don't want because of their dongle? I,m a bit mix up

No. I have no idea what they have up their sleeves. But I do know they will hold back the scene with DRM.

AFAIK 3.55 was the last FW with a known dongle ID list. Beyond 3.55+ TB would have no way to enforce a dongle, so that is my guess why they stuck to 3.55.

Depending on their methods and their available hardware, they most likely dont know the newer keys in order to even start a new CFW.

Dumping eboots from ram means they dont need to know/have keys to resign them.

[sardine]

Originally Posted by DEFAULTDNB No. I have no idea what they have up their sleeves. But I do know they will hold back the scene with DRM. AFAIK 3.55 was the last FW with a known dongle ID list. Beyond 3.55+ TB would have no way to enforce a dongle, so that is my guess why they stuck to 3.55. Depending on their methods and their available hardware, they most likely dont know the newer keys in order to even start a new CFW. Dumping eboots from ram means they dont need to know/have keys to resign them.

So you mean that anyone who have the tools can do like TB but actually TB did not get the key to unlock the firmware right?

[DEFAULTDNB]

Originally Posted by sardine So you mean that anyone who have the tools can do like TB but actually TB did not get the key to unlock the firmware right?

Right. Their trick allow them to mod eboots, nothing more.