[JonahUK]

Originally Posted by hellsing9 The whole problem here that's the blues are still making money, then came the clones that make money too.

This is why I said that if somebody releases a method that can be used on official eboots (ie, from the disc so you can backup your original and play), you wouldn't need the dongle, ergo, the dongle is useless and not needed.

Surely making it redundant is what the end goal is?

If the dongle is cracked, we have access to their current library of games but they will just release newer hardware and encrypt their eboots differently and then its back to square one.

By releasing a method to do this with your own eboots is the best way forward as you can backup any game, apply the method and play.

@KDSBest already stated that people are looking at the eboots but which ones?

If its TB ones then its pointless (see above), they should be looking at how to do it on original eboots.

The games are why TB make money, take those out of the equation and TB are gone.

[defyboy]

Originally Posted by JonahUK This is why I said that if somebody releases a method that can be used on official eboots (ie, from the disc so you can backup your original and play), you wouldn't need the dongle, ergo, the dongle is useless and not needed. Surely making it redundant is what the end goal is? If the dongle is cracked, we have access to their current library of games but they will just release newer hardware and encrypt their eboots differently and then its back to square one. By releasing a method to do this with your own eboots is the best way forward as you can backup any game, apply the method and play. @KDSBest already stated that people are looking at the eboots but which ones? If its TB ones then its pointless (see above), they should be looking at how to do it on original eboots. The games are why TB make money, take those out of the equation and TB are gone.

Except that TB are not the developers problem. They are Sony's problem.

I'm sure if you explain the situation to Sony they will kindly give you an easier method to pirate their games.

[JonahUK]

Originally Posted by defyboy I'm sure if you explain the situation to Sony they will kindly give you an easier method to pirate their games.

Why do you automatically assume I'm a pirate? I updated to OFW a long time ago.

If I was a pirate, I'd be on 3.55 with a TB as that is all it provides.

[defyboy]

Originally Posted by JonahUK Why do you automatically assume I'm a pirate? I updated to OFW a long time ago. If I was a pirate, I'd be on 3.55 with a TB as that is all it provides.

I didn't assume you were a pirate. It was quite clearly a sarcastic remark.

[JonahUK]

If it was intended as sarcasm then fair enough.

[MajorDisaster]

Instead of putting money together to pay a Dev to Crack TB how about paying a Dev to make a program that will make all Eboots 3.55 compatible? Like the program DeanK made called PS3 EBOOTMod and EBOOTFix Tools.

If you didn't know, with DeanK's program all you needed to do was run the program and drag & drop the Eboot and the program would make the Eboot compatible with lower firmware.

Cracking TB would be nice and all but couldn't TB Devs just update it and change the way they make Eboots 3.55 compatible and then making Eboots they release incompatible with the Cracked TB?

I think If a EBOOTFix Tool can be made the end results would be the same, and that is to make TB die and have a way to play current games on 3.55.

[JonahUK]

Originally Posted by MajorDisaster Instead of putting money together to pay a Dev to Crack TB how about paying a Dev to make a program that will make all Eboots 3.55 compatible? Like the program DeanK made called PS3 EBOOTMod and EBOOTFix Tools.

Those worked because the keys were known.

[euss]

Originally Posted by MajorDisaster I think If a EBOOTFix Tool can be made the end results would be the same, and that is to make TB die and have a way to play current games on 3.55.

Then start coding!

1. Get the TB keys
2. Fix the self corruption in the SHT, so it will unself right.
2b. Alternatively, get the decrypted binairies dumped
3. Resign the decrypted ELF/PRX with proper tools (already exist for 3.56 and below)
4. Have fun

[MajorDisaster]

Originally Posted by JonahUK Those worked because the keys were known.

I know that, If the keys for 4.11 where public there would be no need for someone to make a new program, we could just put the keys inside DeanK program.

Originally Posted by euss Then start coding! 1. Get the TB keys 2. Fix the self corruption in the SHT, so it will unself right. 2b. Alternatively, get the decrypted binairies dumped 3. Resign the decrypted ELF/PRX with proper tools (already exist for 3.56 and below) 4. Have fun

I'm sorry were you not aware this thread was for suggestions? Obviously I'm not a coder hence, why I suggested it, whether it be a bad one or not isn't the point of this thread to post suggestion cause we hate TB?

[JonahUK]

Originally Posted by MajorDisaster I know that, If the keys for 4.11 where public there would be no need for someone to make a new program, we could just put the keys inside DeanK program.

If they were known, we wouldn't need to put them anywhere as we would have CFW/MFW.

I know what you're saying but the keys would negate the need for any program to make eboots compatible.