Thank you! All I did was share code that had already been released. I never forced anyone to use and I made it VERY CLEAR THAT IT COULD BRICK YOUR DEVICE. If you can't or didn't read that part, it isn't my fault.the code was released under gpl and posted by the creators, so you can't then go complaining about others sharing it :/
and in the same way no one is responsible for a bricked device but the person who chooses to work on said device, the gpl is very clear
"This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
all this childish bickering is crazy and needs to stop.
*wrecked.All I see here is a bunch of mess being created by the creator of the thread, @Fredo2000 himself. First and foremost, @jcase did state that the program/what he is working on is incomplete, and you decide to actually release to the community thinking that "everyone" has the knowledge and knows what they are doing, and now resulting in people's phone bricking. And funny thing is that you are pushing the blame on the ones making the tool when you are the one who leaked it out and created this kind of havoc in the forums.
Isn't it very contradicting that you, as the creator of the thread, didn't respect the developers and thinking that "Oh since there's a link for it that I could share with everyone, why not? Cause everyone over here understand how the tool works and I don't need to ask the developers before sharing the link." and now pushing the blame back to the developers cause "problems" occurred in the process of you releasing the tool to the wrong part of the audience and resulting with people bricking their phones with no ways to save themselves until an official KDZ/TOT comes about.
It's really ridiculous that things would even become this way, and this is the first time ever in the forums where I've seen such irresponsible bullsh*t from members of XDA. You don't deserve to be here @Fredo2000 . You created havoc and have wreck the one of a lucky few chances where we could have been patient and wait for @jcase and @beaups to release a full-fledged working tool for everyone to use.
Why can't you just admit that you publicly released something that was blatantly stated not to be released by the dev? It really doesn't matter what high ground you take on the matter.Thank you! All I did was share code that had already been released. I never forced anyone to use and I made it VERY CLEAR THAT IT COULD BRICK YOUR DEVICE. If you can't or didn't read that part, it isn't my fault.
The code was released for moments and quickly redacted due to issues involved. The OP here knows that. If you want to get GPL technical, I suggest you study GPL. GPL requires that the license be placed in each source file that the license applies to. So, the files that the OP (irresponsibly posted) are not GPL licensed.the code was released under gpl and posted by the creators, so you can't then go complaining about others sharing it :/
and in the same way no one is responsible for a bricked device but the person who chooses to work on said device, the gpl is very clear
"This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
all this childish bickering is crazy and needs to stop.
Nail on the head dude.History is repeating itself.
Been watching these threads, hoping to upgrade to the G5 from the G3. And I swear I'm living in a time loop.
"Bump" gate all over again. Sad that these people just can't respect what the "Actual" Devs request. And the Devs even go out of their way to help them.
Just sad.....
Sent from my LGLS990 using XDA-Developers mobile app