yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Citizen_Snips:
$20 says lazol posts a "help I used a toolkit & now idk what to do" thread in q+a when he bootloops lmao. Sorry dude, but your reasoning as to why they are good is just plain stupid. If you don't have time or intrest to learn what you're doing to your phone then you should not be doing it at all. I wonder if your doctor did the same thing? "Well hmmm. I never actually paid attention in med school or read any books or learned anything, but let's go ahead and do this heart transplant. I'm sure everything will go okay." Maybe it does at first but when you flat line and he has no idea what to do. . . Get my point? This IS NOT a random android phone forum just to help you root and show off your phone. It is a developer website made BY and FOR developers. People who want specifically to "mess" with their phones on internal root levels. People who want to help other people learn how to develop.

If you don't have the time or interest to learn what you're doing to your phone on a level where even 1 wrong line of code COULD permanently disable your device then you don't deserve to have an account on XDA. Who cares if a toolkit made your life easier? This website is not designed around making lives easier. It is about developing for the great and wonderful android and mobile phone community. Toolkits do not teach you how to develop at all. If you have no interest in development then head on over to Rootz or somewhere else.

Kinda like learning stick. Sure you could buy an automatic transmission vehicle and have the car shift for you & you not learn stick. But what happens when your buddy takes you to a party in east bumble**** and his car is stick and he gets plastered and can't drive home anymore? Its 1:30am and you have class at 6am and your house is over an hour away? Uh oh! Bet you wish you learned the real way to do it instead of taking the quick & lazy way out.

No offense to all of these people advocating toolkits, but how freaking lazy are you?? ADB takes literally minutes to learn. I went from no knowledge to bootloader unlocked/rooted/ROM flashed in under 20 minutes. You really don't even have a half hour to read up on it?? Bull. No free time on the weekend? A quick 15 minutes after you put the kids on the bus before you leave for work? For 10 minutes while you are on the toilet? To say you have literally no spare time in your life whatsoever is complete and total crap. Sit on your computer while watching the game and read up some stuff during commercials. Seriously to say your life consumes too much time to read an article on the internet is rubbish. In the time it took you to read this entire reply you could have already learned how to unlock the bootloader and root using ADB! Seriously.

I still say link anyone having a problem to a direct pm of the toolkit dev. He helped the person mess up their phone let him help fix it. If he keeps getting what floods the QA section in his inbox daily, I'm sure he would be more than happy to unpin his toolkit. The link is in his SIG. Those who wish to find it will and the rest will never have a soft brick or boot loop because of it...
[Samsung Galaxy Nexus] Beamer9408:
It's just stupid because all the people that post questions mention using a toolkit for root/unlock then don't know how to fix it. We get a million questions on how to fix the same problems over and over yet somehow they are all different a bootloop is a bootloop no matter how it happened you can use the same method to fix this bootloop no matter how it happened. Learn to use the tool available.
[Samsung Galaxy Nexus] El Daddy:
If you spent as much time as me and many others on here trying to help people with their problems, you might feel a bit differently.

Its very difficult to troubleshoot users issues when they have no idea what happened to their phone. Sometimes we can figure it out. Then, when we give them steps to fix the problem, they have no idea what we're talking about.

People who are versed in adb and fastboot can follow directions and get their device up and running again.

I've said it before and I'll say it again, I don't hate toolkits, I created this thread to enlighten people of the dangers of taking the easy way out. Its not knowing about the schematics of the motherboard. Its just knowing how to debug your devices using the tools Google provided.

Now. Back to football. Go Vikings! :)
[Samsung Galaxy Nexus] @rbiter:
May interest somebody in a breathing tube and bottle of oxygen? Or an apple device? I like how a few people answered interviewers waiting in queue for the iPhone 5 that apple devices are so smart it's like they do the thinking for you. Now if y'all excuse while I use my diaphragm and lungs to breathe on my own.

...
[Samsung Galaxy Nexus] segv11:
Google self-driving cars will serve an important purpose too. People will be able too use a car without leaning how to drive.

But I hope that those who root and ROM such cars did at least learn a bit about driving first...

Sent from my 4.1.2 toro Bugless Beast.
[Samsung Galaxy Nexus] JediNinjafication:
Self driving cars should only be for the physically challenged.... Or dumb texting teenagers! And all things malfunction...what then? Technological advances will be thedownfall of civilization

*Step Away From The Toolkit and NoROM Gets Hurt*

---------- Post added at 04:02 PM ---------- Previous post was at 03:20 PM ----------

Go packers!

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] Citizen_Snips:
Am I the only Pats fan here?

P.S. toolkits r bad
[Samsung Galaxy Nexus] lazol:
You've lost $20.

Let me explain my case:

1) I'm a lucky Gnex owner

2) After a while I thought I might want to get rid of the navigation bar, to take full advantage of the screen dimension.

3) I googled, and I ended up in this forum

4) I found out I needed a rooted phone to be able to modify the file build.prop

5) I don't have any idea about rooting and stuff so I decided to forget about it, because even if you don't believe it, it's totally possible not having the time to learn about rooting

6) I finded out there's a toolkit for easily rooting the phone

7) I readed the condition to use the toolkit ("I do not assume any responsability...." and stuff)

8) I decided i wanted to take the risk (is not like you said the same as a doctor with a patient, that's only my phone man...)

9) I rooted my phone, and modify the buil.prop

10) I got to my goal, thanks to the toolkit and to the guy who created it (exactly for this kind of scenario) and gently shared it for free

11) I didn't use root privileges for any other mods.

I remember last year, when I was lying down on the street whit my right leg destroyed under my motorcycle, waiting for the ambulance, I kept repeating to myself: "you knew bikes are dangerous, don't cry and complain like a kid now...". Same thing I would have done if I bricked my phone.

This is not only "a developer website made BY and FOR developers" it's also a site that anyone can reach googling "eliminate navigation bar Gnex", as I did.

Now that I have an account I partecipate at polls, read news, sometimes even suggest something about the phone.

Did I do something wrong?

Why should I leave the forum?

Did I brake any rule?

As I said in my first post in this thread, I'm not interested in penetrate the crucial secrets of the rooting, and rest assured that is not because I can't get there, but because i have no time for this.

I swear that when you have a family with kids, a full time job and you're preparing the final exam at the Royal Conservatory of Music, and assuming that you need to sleep at least 4 hours, you don't have time to properly root your phone.

So, again, thanks to the toolkit maker. I've lost waaay to much time aready...;)
[Samsung Galaxy Nexus] adrynalyne:
You could have learned everything you should know about adb and rooting in the time you spent posting about your support of toolkits.

Time not so well spent.
[Samsung Galaxy Nexus] Marisa:
I don't personally have an issue with the toolkit itself, I take issue with the mentality of the people that use them and refuse to learn what it does. They tend to be very selfish, always wanting more and getting upset when people don't want to help them. They also tend to be very ungrateful, the types that complain the loudest about minor problems (like say... toggle icons or when the dev will add X feature that's available in some other ROM.)
[Samsung Galaxy Nexus] adrynalyne:
+100.
[Samsung Galaxy Nexus] lazol:
You could have graduated at the conservatory in the time you spent posting 8000 times :)
[Samsung Galaxy Nexus] adrynalyne:
Probably, considering I've been here since 2008.

I know how to multitask though. Imagine that.
[Samsung Galaxy Nexus] Beamer9408:
Me too that's what the button in the right is.
[Samsung Galaxy Nexus] heccubusxda:
Hmmm, on 3 devices I've rooted, installed custom recoveries , superuser, flashed probably dozens of roms, kernels, patches, updates, etc ,etc...with nary a brick or a bootloop.

Maybe, I'm just lucky or maybe I'm just really careful, take my time, do my homework and don't try and bite off more than I think I can chew.

But because I haven't found it necessary to type even a line of arcane adb or fastboot commands, I'm lazy and ignorant and have no business doing anything to my phones or even posting in an xda forum?

Really?
[Samsung Galaxy Nexus] adrynalyne:
Nobody is saying don't use them. They are saying that if you must use a toolkit and break it, stop crying to us because you couldn't be bothered to learn the right way.

If you don't have time to learn a little, you really shouldn't be messing with your device until you do have time.
[Samsung Galaxy Nexus] jordanishere:
Efrants rooting exploit forced me to use adb for the first time. It was a good learning experience.

Recently I was unhappy with the updated version of the recovery I use, and had to use fast boot to revert to an older version. It was a piece of cake thanks to the learning experience mentioned above because I already had adb and fast boot up and running on my Mac.

Thanks for hating 1clicks!!
[Samsung Galaxy Nexus] Beamer9408:
*cough* toolkits are the best *cough*

I don't need to learn sh*t!
[Samsung Galaxy Nexus] JediNinjafication:
Especially since takes less time to learn a little than it takes to sift thru the junk to find out what's wrong....or take the easy way again and just Odin it

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] Mach3.2:
The point is if you use toolkits, don't make a thread in the Q&A section. Well if you get off your lazy ass and learn ADB an fastboot, you don't need to make 1 anyway. If you still can't understand a single f*ck, don't mess with anything, you probably won't need to make a thread in the Q&A section too. Bottom line: Don't make a thread in the Q&A asking simple problems which can be solved by learning ADB and fastboot

Beamed from my Grouper.
[Samsung Galaxy Nexus] ezeuba:
So it's OK to flood you with PMs if only I used ADB and still bricked my phone? Jeez guys!!! What beef?...
[Samsung Galaxy Nexus] johno86:
As someone who recently started using custom roms and kernels - I appreciate all the work that has been done for automating things.

I took the time and spent the hours reading through threads to better understand what exactly it was I was doing so I have a much greater appreciation for the developers and their work.

Having said that - there will always be those who just want things spoon fed to them on a silver platter. There's also those who want to learn but can't grasp the concept of what's going on so it's really no fault of their own but their lack of insight in the field of engineering and computer science.

I encourage everyone, that's new to rooting and utilizing tools for their phones, to read stickies and threads created by those who are on a vastly different level of understanding so they, too, can enjoy customizing their phones without causing headaches for themselves and others.

One can only hope however.
[Samsung Galaxy Nexus] efrant:
If someone did not use a toolkit, I always provide support if they are have issues or a boot loop.

I think most people in this forum would say that I am helpful and responsive. I have no issue spending time helping someone who wants to learn what went wrong and how to fix it. <-- This is one of the reasons I am here: I like helping those who want to learn.

However, if someone doesn't care about the learning, and just wants his/her phone fixed, or set up a certain way, I just ignore the posts, and hope others do the same. This is not a help desk or support forum.

If i read "toolkit" anywhere in the thread, I just point them to one of the many stickies, and nothing else.

The stuff here is not rocket science, and it doesn't take a lot of time to learn - if you read a few of the stickies in General and Q & A, you would know a lot. (And in case anyone is wondering, I don't work in IT or have a background in IT - I have a degree in business and work in finance. Everything I know about Android I learned from XDA and android.com.)
[Samsung Galaxy Nexus] JediNinjafication:
Mmmmmmm....I dunno bout that. I recently tried helping a guy who trashed his meid. I can usually help someone with all the dialer codes and the repair as long as they have the box and can input the info along the way. Unfortunately, his was so bad couldn't even get the spc to open any editing. All i could do was walk him thru fastboot to relock bootloader. It was obvious he didn't use adb because didn't even know the commands and was surprised at how quickly adb worked. I'm glad i had the opportunity to show him another way and can only hope he continues to use it. How can we advocate adb yet ignore those who are in obvious need of enlightenment? I think it's the best chance to say "see! See! If only you had studied you would know this! Did you learn your lesson?" While it sucks helping those quick fix people, sending a corner cutter right back to what caused the issue doesn't help either. I have found the ones who have had that "omg i jacked my phone....someone please....what do i do now" are more than willing to go with adb. Oh and just to ensure...my last step in helping is usually fastboot oem lock if they used a toolkit...along with a link to the Android developer site

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] Mach3.2:
Damn, fastboot oem lock..:eek:

Imagine the look on their face when they want to flash something:D
[Samsung Galaxy Nexus] fooman123:
the bootlocker app for gnex is handy, as all does is flip the right bit, and allows to flipping back and forth without the mandatory user data wipe..
[Samsung Galaxy Nexus] Mach3.2:
That i know, i'm the beta tester of it. But how is it going to work if that guy is completely stock, unrooted and locked, bye bye angry bird saves:p
[Samsung Galaxy Nexus] JediNinjafication:
Well guess if learned adb they would ask why I'm locking correct? Hell...they think they're bricked anyway. Harsh...all life lessons are harsh. Learn from mistakes or..."brick"

I did a restore not long ago. My phone suddenly had mind of its own. upon restore my root and recovery were gone. Still had unlocked bootloader. Fastboot wouldn't see phone. Samsung didn't have driver link. the Samsung drivers i had weren't working. I have no idea why. I posted so many times. 90 percent of responses told me to toolkit. I would rather sell my phone. After a week...i literally cried and threw my phone...(thank you otterbox defender).. Ended up loooking at hardware id in devices and googling it. got one result. Was someone who had same issue and had to write the gnex into the Google usb driver .inf file. I copied and pasted his info into my .inf file. Rebooted. Was cake after that. Man, i was grasping at straws in some of my posts...asking some dumb stuff. Sorry to anyone who tried to help...i was tripping and got sick of the...install your drivers responses as i knew were there...anyway...would i have known to copy to my sdk if used toolkit? No. Im far from knowing anything about developing but I'm glad I've always used adb.

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] Mach3.2:
That's a valid point..:eek:
[Samsung Galaxy Nexus] JediNinjafication:
Another one I'm good for is this:http://en.lmgtfy.com/?q=lmgtfy just watch the whole thing...people don't realize the wealth of knowledge that Google has! I love this app. some people get mad and i usually save this one for the really difficult people

App can be found here...http://en.lmgtfy.com/?q=let+me+Android+that+for+you basically you can put anything you want in the search and it will link to the above...if you put lmgtfy you get first link. If you use "dont feed the monkey" it will link to lmgtfy and then give results for don't feed the monkey...

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] efrant:
LOL! Yes, I remember that. ;) You kept insisting that you had the drivers installed, no matter how many times I had told you that you needed to uninstall those drivers from the SDK (which even Google says they were not meant for the GNex -- see here: http://developer.android.com/tools/extras/oem-usb.html), and install 1wayjonny's repack. You had to edit the .inf file because you were using drivers that were not supposed to be used for the GNex... :p
[Samsung Galaxy Nexus] Mach3.2:
I'm aware of it, i usually reserve it to the top 10% of the tough nuts.

You still remember this one:D

---------- Post added at 10:46 PM ---------- Previous post was at 10:43 PM ----------

By the way, how do i go about installing 1wayjonny's driver? I'm pretty savvy with computers, just that i'm in the lazy mood today, don't want to Google:rolleyes:
[Samsung Galaxy Nexus] JediNinjafication:
No!!! The gnex was not listed in that inf file at all! Nada! I uninstalled SDK..uninstalled drivers..reinstalled both.... had someone dropbox me complete different sets of both! Man...the hell I went thru! Towards the end when someone said driver If could have reached thru screen I would have!

I think is Cuz computer took crap at same time so had to go from 7 to xp Cuz all sorts of garbage going on all at once. Dude...I was so tripping. I had always used Samsung drivers from their site..no idea what going on. Once put the gnex into inf it was gravy

I still get stressed out thinking bout it. All these files from windows were in my gnex like that stickmount thing I've never used..found out something to do with how xp reads mtp ...I don't know...don't care...issue past..hope never happens again! I have since updated to a laptop..that freaking works.

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] efrant:
I know. The GNex was NOT AT ALL included. Which is why I was directing you to 1wayjonny's repack -- which DID include the GNex. No editing of .inf files needed.
[Samsung Galaxy Nexus] JediNinjafication:
Sheepishly apologizes..all I saw was some other driver thing thinking someone yet again directing to toolkit... humbly bows to the master

If only knew the hell was having! Once downgraded couldn't connect to my WiFi on puter Cuz stupid windows! I had corporate edition...roomie has home...plus had another win 7 home...I went from 7 pro...stupid windows home vs pro/ corporate network crap...I could have committed murder and pled insanity... probably got off too

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] efrant:
;) All it was was the driver striped of any wrappers and other crap, so that it wouldn't install anything except for the driver itself. 1wayjonny did a good job of adding a lot of devices to it as well.
[Samsung Galaxy Nexus] JediNinjafication:
I feel like an after school special and am waiting for the now you know rainbow! Lol.

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] JediNinjafication:
if you speak it ...they will come! fastboot format...yay me!!!
[Samsung Galaxy Nexus] missinnes:
I understand peoples use of toolkits I really do, they feel like there is some security with a one click solution

but as someone who has used a toolkit in the past I have to say I have never been as proud of myself as the day I unlocked my gnex and flashed yakju in order to get JB before the Canadian release

I fumbled, I triple check everything before typing in a single command, I had two screens running with instructions to verify against before I dare push that enter button but I did it, and it was glorious

it brought on a even bigger appreciation for what developers do on a day to day basis and how much time people put into info threads on this site and android as a whole
[Samsung Galaxy Nexus] segv11:
The thread where we figured out what bit to flip was lots of fun. Too bad that I couldn't figure out the equivalent on the Nexus 7. I'd love to try the Nexus S, as well as any future Samsung Nexus devices like the rumored Nexus 10.

Sent from my 4.1.2 toro Bugless Beast.
[Samsung Galaxy Nexus] Zombeezy:
Well, not being a developer, but being at least tech savvy, almost all new forums I dive into will take me weeks and weeks to really get a pretty good grip on things, whether it was repairing my first PC in the 80's, building my own PCs, getting into RC cars, kite-flying, AV systems, genealogy, whatever...

Pretty much every forum (or way back the bulletin boards) has the FAQs, Beginners Here section, Experts Only, etc., and I think that XDA does a good job of letting people find their way around, get in a bit deep and so on to learn. The problem is more the "need an instant happy pill" mentality of many, be it their first root, hack or jailbreak, or to "get them working again" after they get in over their heads. Just gently point their way out of the Developers section to the General section, or even out of XDA if necessary to another site that best suits them.

I am reminded of spending hours with people fixing their PCs, or reinstalling the OS with words of advice, and the same problem seems to come up again in short order. Or hours researching and giving advice on what TV to buy and why, and they grab a local BB special.

Embrace and enjoy loving tech and being in a society where we have lots of it to play with at decent prices. But, what comes with that is the understanding of .... "The Bell Curve". Wayyyyy too many average people, and wayyy too many dummies in this world have the same access to the same tech. I just shake my head and grin to myself as I find that another JB ROM doesn't work as well as I like, and I have to wipe and reinstall another. Got to love it ...
[Samsung Galaxy Nexus] z_extend_99:
Hi guys. I'm new here in XDA although I had been an Android user for more than a year now.

Are the use of toolkits really being frowned upon? Are the risks of messing up with your device higher with the use of toolkits?

Manual procedures with ADB commands and use of toolkits both have proper steps and sequence to follow.
[Samsung Galaxy Nexus] Marisa:
It's not so much that you're more likely to mess something up as it is that if you use the toolkit you're more likely to waste the time of someone helping you (having you install the various programs you would have already) and with basic knowledge gained from doing it the manual way you're less likely to be completely lost and dependant on someone else to fix it for you.

The case is particularly bad when the steps are as easy as they are on the Nexus. Using the toolkit on this phone is practically admitting to being a lazy selfish idiot that doesn't even pretend to want to learn.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Mach3.2:
Toolkits are static, problems are dynamic, toolkits can't adapt to different problem and you can't make the problem adapt to the toolkit, better to learn the proper way and solve the problem and feel great than wait god knows how long to ask people to fix it for you on Q&A section and make people frustrated.

Beamed from my Grouper.