LG G5 Root Bounty! [Currently $1,420] [LINK FOR LGTOOL BY BEAUPS AND JCASE ADDED]

When will root be achieved?

  • Within 2 months

    Votes: 56 65.9%
  • Over 2 months

    Votes: 29 34.1%

  • Total voters
    85
Status
Not open for further replies.

Indicious Flow

Senior Member
May 11, 2010
525
416
0
Singapore
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.
 
Aug 11, 2010
43
24
0
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.
 
F

Fredo2000

Guest
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.
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.
 
F

Fredo2000

Guest
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.
*wrecked.
;)
 

Anarchist77

Senior Member
Sep 13, 2014
320
240
73
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.
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.

You were asked not to and you blatantly ignored this, now to the detriment of the wider and general XDA community.

Go on and flame me etc as much as you want.. but i don't think i am alone in how i feel about how this has been handled? It comes down to a simple matter of respect.

It reminds me of the same exact situation when the G3 was launched and bootloader unlocking was at the foremost of users attention/focus.
 

engine95

Recognized Contributor
Oct 14, 2008
3,912
4,801
263
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
 

beaups

Senior Recognized Developer
Nov 28, 2007
3,276
7,257
253
Dublin, OH
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.
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.

http://www.gnu.org/licenses/gpl-howto.en.html

--beaups
 

Coycaine

Senior Member
Sep 17, 2011
1,742
1,179
0
Reno, NV
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
Nail on the head dude.
 

miggs78

Member
Jul 19, 2015
12
2
0
A request to both devs: We all know the creator if this thread is a <insert your fav word> and what he did (whether he admits it or not) is just plain simple dumb. But for the love of us all here, please consider continuing on this project. Minus one person, a lot of us here are patiently waiting for a root. Honestly it would mean a lot to us if you continued. Simple request if you can...
 

matt4321

Retired Senior Moderator - When red-headed people
Dec 20, 2011
3,986
6,199
263
27
Reading, UK
This thread will remain closed, there is far too much chaos to reopen it again.

If someone wants to open another bounty thread, take current pledges from the OP and maintain that then that is fine.

However it must be on topic, any talk or links posted of the removed tool by @jcase and @beaups will result in an infraction. Consider this your warning. Me and other moderators will be watching closely.

Forum moderator,

matt4321
 
Last edited:
Status
Not open for further replies.