The above video goes away if you are a member and logged in, so log in now!
Anyone have the correct Hex for a Teensy 2.0 ATMEGA32U4 16 Mhz 32K?
Also could anyone direct me to a link to compile my own payloads? So I don't have to contiously ask plus I can contribute if anyone needs payloads compiled.
Were you quoting me or medi01?
Originally Posted by xPreatorianx
Originally Posted by JonahUK
Lol. OK. With you saying "other guy" in your repsonse to tsb, I thought you meant me....
Originally Posted by xPreatorianx
Silly Question, but has anyone had any luck with blitz the league 2? It has no sound. The only one I have come across that does this.
I know, that most people that played this hates it, but it is my guilty pleasure. so if anyone has a fix or a solution. That would be super.
Hi guys could someone please post a hex file for Atmega32U4 8MHZ please
would love to give MOH a go
thanks in advance
To those who continue talking about how KaKaRoTo is wrong, "starting the drama" and so on... Let's try to... munch it and spit it in your mouth, in case you understand it.
Please, try to read the following:
That's what Herme's doing. And it's great. Problem is, it doesn't help collaboration a lot. It means others who'd like to help out, although they may be totally able to do so, have to "decrypt" the way he writes his code. Yeah, the code "is open", but it's like what I posted - only a LOT more complicated and obscure. Now, KaKaRoTo PROPOSED that people join the PL3 project, notice that, PROJECT, were MANY PEOPLE can work TOGETHER for a common cause. And, to make the collaboration easier, it would be better if each and every one wrote "clean code". You know, something like this:
Idiot user is totally unable to understand what KaKaRoTo and Hermes are doing.
Better, isn't it?
Apart from that, try to understand what PL3 on github is: it's NOT "KaKaRoTo's payload". If you go to the projects page, you'll see each and every change to it, attributed to the one who did it. OK, KaKaRoTo "started" it, but so what? Do you know who started Gnome? Who started GIMP? No. You know that "they're great open source projects, created by many people". And if you want to find "who did what", you can. So, why the bashing of PL3 as a project?
Now, the bashing of PL3 from a USERS point of view may seem right ("Herme's payloads worked for me, PL3 doesn't"), but that's because the software that runs under the payload is the other part of the same equation: when KaKaRoTo implemented the new way of "mounting" the blu-Ray drive to a folder, only Gaia manager supported it. Did that mean that PL3 sucked, 'cause it did something differently (or, more specifically, "the correct way")? Ofcourse not, and the creators of the BMs should support it.
And why should they support "KaKaRoTo's way of doing it" you may ask. Well, KaKaRoTo already explained: when patches and changes are implemented in the payload, they're accessible as global "functions" to the programs that can use them. Think of them like, say, the way DirectX works on Windows. DirectX itself has different code so as to run on Win32 and Win64. Programs that need DirectX, though, can work on both, the same way. That's what KaKaRoTo is saying: "leave the infrastructure part to us". Let the Payload do what it does, just like DirectX does what it does. "You write the programs that use it". 'Cause now we may have only one or two patches, that are easily implemented in a BM, but what if in 2-3 months we have 100? Why re-implement them in each and every BM, when they could exist in a "common" payload that all BMs would be able to use?
Apart from that, as KaKaRoTo explicitly stated, having the patches in the BM breaks compatibility with older Firmware versions. If there's a way for both the exploit and almost every piece of software to work on all Firmware versions, why restrict it to only a specific one? Say, if somebody actually -does- find "a hole" in 3.42 or 3.50, wouldn't it be better to have "firmware agnostic software", that could easily work on them too? Would you prefer having to wait, after a hole is found, for all homebrew creators to "re-create" their programs for the new Firmware versions?
Now, do you -still- disagree with "KaKaRoTo's way of doing things"?
Has anyone compiled this for ti-84 yet?
not taking anyones sides on this whole gossip but...if hermes chooses to write his code in a way he feels comfortable and it works..then who the hell is anyone to say he needs to change the way he does things? i will be damned if i code a certain way and someone tells me that i have to change the way i write my code just so they can understand...whats important is two things in his method..
Originally Posted by ducklord
1. he understands what he does
2. it works...