• Steam recently changed the default privacy settings for all users. This may impact tracking. Ensure your profile has the correct settings by following the guide on our forums.

compile homebrew for the 5.03 tiff?

H

HacKmaN

#include
could anyone help me, what I should do, if I want to compile cpp files for the tiff exploit?
I'm using minpspw as compiler and eclipse as IDE.
 
It is. But only Matiaz have that. I thought if there is Sparta SDK, there is also 5.03 TIFF Exploit SDK available to public.

And Davee, how did you made ChickHEN without SDK?
 
U3-Robot said:
It is. But only Matiaz have that. I thought if there is Sparta SDK, there is also 5.03 TIFF Exploit SDK available to public.

And Davee, how did you made ChickHEN without SDK?
Click to expand...

I used the power of lolhax.
 
Davee's sarcasm abilities just went up one level

xD
 
If you really have to ask about coding for the TIFF, I'm not sure if you should even bother with it... Besides, what's wrong with HEN? Coding regular stuff a) gives you way more capabilities (kernel mode without special trickery and custom imports), b) is much easier and faster and c) has debug capabilities. Not to mention it works across firmwares.

U3-Robot said:
It is. But only Matiaz have that.
Click to expand...
Bzzzzt. There's a little thing called "2.0 TIFF Hello World" which was released with sources here. Anyone with reading and programming skills can adapt that to his TIFF binary loader. There was no such thing as "TIFF SDK", there was never going to be, because the TIFF was way too unstable and Davee was making the HEN.
 
I don't say HEN is bad, I only tried to make files which are no EBOOTs, I started coding only some time before and I'm trying much things like that in the last time;)
I won't do something like becus and xenogears did, they only made cfw enabler for piracy, and they are pirates themself, because they stole the work of m33, GEN and Davee.
Sorry for my bad English. lol
 
If you really need to ask those questions you should stay far, FAR away from coding for exploits.

Don't get me wrong, I don't want to be mean, but letting code run in an "exploited environment" is not as easy as just running an executable.
There is quite some restrictions and many, many other problems you have to deal with in that situation, you WILL get crashs you can't explain (due to missing experience), likely caused by stack oddities or other threads interfering with your code or your code with them.
Can you handle that, or even find those things as cause for the malfunction?
(If "yes", then go ahead, if no.... well.... ;))

You will not get happy with this, trust me.

// EDIT
One more thing that came into mind while re-reading the above:
You also can't just call functions like you are used to do, as you have no imports that get resolved upon your codes execution.
You have to manually find/know the funtion pointers and make them into function calls before you can use them.
Also there is only a limited list of functions you could call at all, only the ones already imported by the environment you exploited....

Well....
 
You must log in or register to reply here.
Back
Top