Develop Bugs

The Dangers of Tool Kits and One Click Root Methods + Mini Rant

I don't create threads on xda very often and 95% of my posts are me trying to help people out, but this is something I wanted to get off my chest.
It seems like everyday in this forum there are about 5 new threads of people "stuck in a bootloop" or "stuck on Google screen." The majority of these people don't know the difference between adb and fastboot or bootloader and recovery.
I bought the G1 on launch and there weren't tool kits. We had to use telnet and command prompt to do everything manually. I knew nothing about linux or coding, but I followed instructions and learned what was happening when I entered these commands. Through owning the G1 and then moving on to the Nexus One I don't remember seeing so many threads about people "soft bricking" their device. I think the reason for this is the tool kits and other scripts that make it almost too easy to unlock and root your phone. While I respect the people who write these scripts (and I think they do serve a purpose in some situations) I think it's causing more harm than good.
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Weigh in with your thoughts, criticisms or tl;dr comments.
Thanks.
EDIT 8/9/12: Link to efrant's Android Galaxy Nexus 101 guide. All the info you need to know. http://forum.xda-developers.com/showthread.php?t=1812959
EDIT 11/14/12 My Thank you & Goodbye post.

I agree that it's lack of research that causes the problems. But don't knock the toolkits, they're designed for ease and they work perfectly with an understanding of what's going on. I can go thru adb and unlock and root because I researched the absolute **** out of it and know how to use adb but I used a toolkit. Like I said, if they don't want to research then bad on them. Gotta learn somehow be it by mistake or research. But the toolkits aren't the enemy.
Sent from my Galaxy Nexus

There's always a bigger fish. Like little man syndrome , be careful before you develop big man syndrome. " I'm taller than you "
PS even with research, " you can't fix stupid " so just let it go. A poor craftsman blames his tools. Simple as that.
Sent from my Galaxy Nexus using Tapatalk

Leaving good enough alone.
It's getting pretty comical when you see a "help me" post and before you even start reading the post you can correctly predict that the post will start something like this: "so I flashed *****'s custom ROM and now my phone's f****d".

This thread is so full of #winning. The easy way is not always the best way.

I used the manual methods for my Atrix so now after getting a good feel for Fastboot and ADB, the GNex Toolkit was really painless to use.
I understand what you're saying though. I guess some people just want easy routes to get what they want, completely scrolling past the giant red text that tells them exactly what could (and most likely will) happen.

phaze one said:
I agree that it's lack of research that causes the problems. But don't knock the toolkits, they're designed for ease and they work perfectly with an understanding of what's going on. I can go thru adb and unlock and root because I researched the absolute **** out of it and know how to use adb but I used a toolkit. Like I said, if they don't want to research then bad on them. Gotta learn somehow be it by mistake or research. But the toolkits aren't the enemy.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I'm going to second this, as long as the toolkits are well documented (showing what they did where, and why it was done) they can save people time typing the commands and looking them up if they forget them.
It's very similar to creating a GUI front end for a program. If done properly they're nothing but useful and time saving.

Im guilty of using the wugfresh kit. I could have easily done everything myself, but it contained everything I needed.
I agree with pretty much everything you said though. I see people offering money for them to root their phone over team viewer, etc. Those are the same people that warranty their phone that they, themselves messed up.

Thanks for your feedback everyone.
I just wanted to clarify I'm not ripping toolkits. They are a great way to get where you want to go quickly. If you know what you are doing by all means use it. But, to me it seems like they are just the cheat sheet to the test. Yeah, you aced the **** out of the test, but when asked to apply what you should have learned from that test in a real life situation; you are screwed.

How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.

adrynalyne said:
How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.
Click to expand...
Click to collapse
Exactly.
Wouldn't it be sweet if there was actually "profit" and the phone started spitting out money?
You're a dev. See what you can cook up.

The hardest part is just those drivers, not that I call it hard, just Windows can be a pita.
Once that part is working then using adb and fastboot comands I think is fairly straightforward and don't need the toolkit.

Im hardly experienced with Android or Linux. Ive used both for the past year or so only, and did take time to learn what abd commands there are etc. but also will use the toolkits to save time and headaches.
Anyways, its always like this. iOS hacking forums are similar.
Also, if you can get into recovery why do a nandroid? On SGS I was told by devs its not really needed as long as you dont mix up kernels. Do that, and what help is the nandroid? Cant flash it if you cant get into download mode. If you can, thats what stock images are for? I sync everything I really care about to cloud/PC.

El Daddy said:
Exactly.
Wouldn't it be sweet if there was actually "profit" and the phone started spitting out money?
You're a dev. See what you can cook up.
Click to expand...
Click to collapse
LOL...I wouldn't be here if I could

Toolkits for the nexus is kinda unnecessary because it is so easy to unlock, but there are devices that one the 1%(?) could unlock without a toolkit.
Sent from my HTC Desire HD using XDA App

I
adrynalyne said:
How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.
Click to expand...
Click to collapse
One-click rooting on my Fascinate:
I used z4root to root my phone before I flashed my first ROM (back then I just used ROM Manager for everything and didn't even bother looking at the ROM threads on XDA until the late DJ05/DL09 days when I got used to flashing manually in Clockwork Recovery). With z4root I didn't even need to use my PC to root, but it didn't always work when I had to go back to stock.
One-click Odin pitfalls:
My first experience with Odin was using a one-click version to flash a stock Froyo leak on my Captivate when they had just started making custom ROMs for Froyo. I had a bad experience using one-click Odin so I soon learned how to manually use Odin to do much more than simply flash a Froyo leak with one click. I soon discovered that Odin could be used to do much more than simply going back to stock - I could flash different versions of Clockwork Recovery, different Captivate and Fascinate modems, etc.
Learning adb for myself:
When I got my Gnex I used the exact method adrynalyne posted, and I found it more gratifying than any one-click root (I got my Gnex before there even was a 1-click, and I had long gotten used to adb. There's actually a lot more you can do with adb than simply rooting. If you only use it for rooting it's like going to a four-star restaurant and always ordering the hot dog from the kids menu - you're barely scratching the surface of what adb can do. I highly recommend reading up on adb and learning the different commands you can use. For example, it got me out of a bootloop more than once on my Fascinate when I was running AOSP MTD ROMs (long before jt1134 made 3-button recovery work on them).
The tl;dr:
One-click methods actually hinder you from exploring your phone's full potential, and often do more harm than good. Learning to do things manually for yourself lets you discover other possibilities you never would have found with the one-clicks.
Terminators run on Android

skynet11 said:
One-click methods actually hinder you from exploring your phone's full potential, and often do more harm than good. Learning to do things manually for yourself lets you discover other possibilities you never would have found with the one-clicks.
Click to expand...
Click to collapse
This is exactly my sentiment.

android01 said:
There's always a bigger fish. Like little man syndrome , be careful before you develop big man syndrome. " I'm taller than you "
PS even with research, " you can't fix stupid " so just let it go. A poor craftsman blames his tools. Simple as that.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You just used 5 rhetorical sayings that make very little sense, in the context of this topic. Be helpful or don't post, maybe?
OP, I couldn't agree more. Too many people post here (and other places) about being stuck in a bootloop even though they should already know how to fix it, if they knew anything about the process they had gone through. It's utterly insane that people are making heavy modifications to a device that costs $650+ without knowing *what* they're doing.
It's like someone going outside to change the oil on their car without knowing a thing about it and following the most basic instructions from some random person on the internet, then freaking out when someone tells them they poured the oil into the power steering reservoir.

No-ones forcing you to help people who have screwed up their phone so I don't see the need to be all holier than thou about it. Why should people have to understand everything that goes on when they use a one-click method? People should just make sure they read the instructions so they don't screw things up. That's the problem, not the tools they use.

As has been stated before in this thread.. you can't stop the stupid, or protect people from their own stupidity.
After far too many years helping out "stupid" users (here and on other forums), unfortunately, I find it far better to pick and choose who I want to help these days. Then, if I get frustrated, I only have myself to blame.. for even responding in the first place.

[Q] Why is it so difficult to root the GN?

I just received my GSM Nexus that came with 4.0.4 and hopped on to root. Half the methods warn against using the method with 4.0.4 or have replies reporting 4.0.4 problems. The other half require 3-4 downloads, running command windows, and 30-40 minutes of time and a factory reset. What gives? Every other android phone I've had in the last 3 years have all had ultra simple one-click programs. Plug it in. Click. Done.
What's so different about this nexus that requires this complicated stuff?

BobbyDash said:
I just received my GSM Nexus that came with 4.0.4 and hopped on to root. Half the methods warn against using the method with 4.0.4 or have replies reporting 4.0.4 problems. The other half require 3-4 downloads, running command windows, and 30-40 minutes of time. What gives? Every other android phone I've had in the last 3 years have all had ultra simple one-click programs. Plug it in. Click. Done.
What's so different about this nexus that requires this complicated stuff?
Click to expand...
Click to collapse
There's nothing complicated about it. You only think it's complicated because you are used to one-click programs -- which is the very reason I don't recommend using them: it prevents the user from learning anything, much like using a calculator before learning how to add and subtract.
Obtaining root access on a GNex is extremely simple. It consists of booting or flashing a custom recovery and using it to flash one zip file. That's it.
And the reason that a lot of one-click exploits don't work on the GNex is that it is running the latest version of Android, which has patched the security holes the the older exploits were using.
Sent from my Galaxy Nexus using Tapatalk 2

Already tried the Gnex Toolkit 6.1?
This is supposed to work with 4.04. I didn´t try it yet, i rooted mine GN with 4.02.
But it wasn´t much more than 1 click with the toolkit.

My guide will work.
Ignore all toolkits, and do it the right way.
You'll thank yourself later if you ever need to go back to stock...
Or have a bricked device.
Srsly.

What is OP talking abouit? the GN is one of the EASIEST phones to root.

Its very easy, here:
https://www.youtube.com/watch?v=FK-AyIJm_6s&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium

Troll?
Sent from my Galaxy Nexus using Tapatalk 2

zephiK said:
What is OP talking abouit? the GN is one of the EASIEST phones to root.
Click to expand...
Click to collapse
Not if all your used to is installing an app with one big button saying "click here to root". So many people don't realize that you don't need a one-click app or a toolkit to make rooting easy -- all it takes is a little bit of reading.

efrant said:
Not if all your used to is installing an app with one big button saying "click here to root". So many people don't realize that you don't need a one-click app or a toolkit to make rooting easy -- all it takes is a little bit of reading.
Click to expand...
Click to collapse
Toolkit is available. Doing the manual method is not the only way of doing it.
Not that I'm endorsing using a one click root because it is relatively easy,
get drivers.
fastboot oem unlock
fastboot flash recovery

This phone is hard to root ?
Nono...the Droid Incredible was hard to root way back. We had to rely on a race condition and precise timing to get the exploit to work. THAT was hard.

I'm very confused. Every nexus phone always had one command:
Fastboot OEM unlock
Gnex is the same as all previous nexus. What am I missing here? Just fastboot one command and you're done.

RogerPodacter said:
I'm very confused. Every nexus phone always had one command:
Fastboot OEM unlock
Gnex is the same as all previous nexus. What am I missing here? Just fastboot one command and you're done.
Click to expand...
Click to collapse
The problem here is that the OP has not done much (if any) reading on this.
Yes, I agree with you, being able to unlock your bootloader makes gaining root access easy. But what you posted: "Just fastboot one command and you're done." is not a procedure to gain root (its information like this that makes a lot of n00bs think unlocking their bootloader is the same as getting root access), and it is certainly not a way to explain it. I could be mistaken though...

I think your just use to other phones that either u Odin it or use app that would flash the phone with root on it. I remember first Android I did it was a pain took time to get timing right for first few times I thought I was missing something
Sent from my Galaxy Nexus using Tapatalk 2

Jubakuba said:
My guide will work.
Ignore all toolkits, and do it the right way.
You'll thank yourself later if you ever need to go back to stock...
Or have a bricked device.
Srsly.
Click to expand...
Click to collapse
I used Jubakuba's guide; very straight forward, no surprises. Highly recommended!

If all you are used to is one click methods, then yes, it SEEMS hard. It is actually very simple.
Fastboot OEM unlock
Fastboot reboot bootloader
Fastboot flash recovery recovery.img
Fastboot reboot recovery
Flash the su.zip from recovery
Reboot to a newly rooted phone
Done. And I even added at least one step that you don't HAVE to do.
Sent from my Galaxy Nexus using XDA

thos25 said:
If all you are used to is one click methods, then yes, it SEEMS hard. It is actually very simple.
Fastboot OEM unlock
Fastboot reboot bootloader
Fastboot flash recovery recovery.img
Fastboot reboot recovery
Flash the su.zip from recovery
Reboot to a newly rooted phone
Done. And I even added at least one step that you don't HAVE to do.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
This is on the right track.
But how about:
1) Where do I enter those commands?
2) Where do I get all the required files? Is recovery.img the same as cwm.img the same as recovery-clockwork-5.5.0.2-maguro.img?
3) How come my PC doesn't recognize my device?

efrant said:
This is on the right track.
But how about:
1) Where do I enter those commands?
2) Where do I get all the required files? Is recovery.img the same as cwm.img the same as recovery-clockwork-5.5.0.2-maguro.img?
3) How come my PC doesn't recognize my device?
Click to expand...
Click to collapse
1.) A command prompt
2.) Download the SDK - it has everything you need (drivers, fastboot, adb). The image is any image you download, put whatever it is named there.
3.) Because you don't have the drivers set up properly. Download the SDK. If it doesn't auto-detect select it manually from the usb drivers folder in the SDK. If it doesn't detect select manually from a list and pick android bootloader interface.

This has to be one of the easiest devices to root, took less then 5 minutes.
using fastboot it is also the easiest one to return to stock. I had to return mine to google due to a defect and it took less then ten minutes to do.
The OP just needs to read rather than looking to be spoon fed.
In each development section there are instructions in a sticky post.

Because everyone who wrote a procedure assumes people are not noobs so they skip steps.
I am a noob with my phone and it took me hours of reading various procedures and piecing them together to get my phone rooted

Not tell if this is trolling or real
Sent from my Galaxy Nexus using Tapatalk 2

Jelly bean root

I have this big problem where I flashed jelly bean and lost root and cwm, boot loader is still unlocked, but I can't access recovery I get this android sign with a clap open and an exclamation mark on it and it doesn't go to recovery so how do I root ? Sry if this is already posted but I can't find anything help full
Thanks I advance
Sent from my Asus Transformer Pad Infinity

ray3andrei said:
I have this big problem where I flashed jelly bean and lost root and cwm, boot loader is still unlocked, but I can't access recovery I get this android sign with a clap open and an exclamation mark on it and it doesn't go to recovery so how do I root ? Sry if this is already posted but I can't find anything help full
Thanks I advance
Sent from my Asus Transformer Pad Infinity
Click to expand...
Click to collapse
Try rerooting or flashing the stock image using this
http://forum.xda-developers.com/showthread.php?t=1454314

This one works also, out of experience.
http://forum.xda-developers.com/showthread.php?t=1392310

jprocha101 said:
Try rerooting or flashing the stock image using this
http://forum.xda-developers.com/showthread.php?t=1454314
Click to expand...
Click to collapse
Rerooting doesn't work I may flash 4.0.4 stock back and then install cwm and stock 4.1 and imediatly super su... but will this wipe any of my files ?
Many thanks
Sent from my Jelly Beaned GNexus

ray3andrei said:
Rerooting doesn't work I may flash 4.0.4 stock back and then install cwm and stock 4.1 and imediatly super su... but will this wipe any of my files ?
Many thanks
Sent from my Jelly Beaned GNexus
Click to expand...
Click to collapse
Just flash the file that is located in post #2 in the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

ray3andrei said:
I have this big problem where I flashed jelly bean and lost root and cwm, boot loader is still unlocked, but I can't access recovery I get this android sign with a clap open and an exclamation mark on it and it doesn't go to recovery so how do I root ? Sry if this is already posted but I can't find anything help full
Thanks I advance
Sent from my Asus Transformer Pad Infinity
Click to expand...
Click to collapse
jprocha101 said:
Try rerooting or flashing the stock image using this
http://forum.xda-developers.com/showthread.php?t=1454314
Click to expand...
Click to collapse
Mikedick said:
This one works also, out of experience.
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
why are you suggesting using a toolkit to a user that doesn't know what's happening manually, let alone what a toolkit does.
It will be that much harder to track down any issues that may arise.

bk201doesntexist said:
why are you suggesting using a toolkit to a user that doesn't know what's happening manually, let alone what a toolkit does.
It will be that much harder to track down any issues that may arise.
Click to expand...
Click to collapse
LOL, I think that's the whole point of the ToolKit.. So the user doesn't have to go through the manual stuff. Kind of hard to mess up on the V7 toolkit. The Dev made it pretty much dummy proof. As long as the drivers(Android 1.0) are installed on your computer you're pretty much good 2 go

Screwhead24 said:
LOL, I think that's the whole point of the ToolKit.. So the user doesn't have to go through the manual stuff.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909
Screwhead24 said:
Kind of hard to mess up on the V7 toolkit. The Dev made it pretty much dummy proof. As long as the drivers(Android 1.0) are installed on your computer you're pretty much good 2 go
Click to expand...
Click to collapse
I beg to differ. Take a look at some of the linked posts in the link I posted above, and you may feel differently.

efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
I beg to differ. Take a look at some of the linked posts in the link I posted above, and you may feel differently.
Click to expand...
Click to collapse
Yeah I'm aware of that thread but 90% of that entire thread are just back and forth post of their experience with other toolkits with other phones and how people should learn how to do it manually and yada yada LOL.. I read that entire thread before I used V7 toolkit to root mines and have to say I don't see what the big fuss is about when someone wants to do it the easy way. It's very simple and very hard to mess up.. All you do is press 1,2,3 ect.

Screwhead24 said:
Yeah I'm aware of that thread but 90% of that entire thread are just back and forth post of their experience with other toolkits with other phones and how people should learn how to do it manually and yada yada LOL.. I read that entire thread before I used V7 toolkit to root mines and have to say I don't see what the big fuss is about when someone wants to do it the easy way. It's very simple and very hard to mess up.. All you do is press 1,2,3 ect.
Click to expand...
Click to collapse
It's not about other toolkits, and it's certainly not about other phones -- it's a GNex thread...
It's fine to use a toolkit when you understand how it's doing things, but if you don't, AND something screws up, you'll be right back here with a new thread saying something like: "I used a toolkit to do abc and now it won't xyz", and asking for help. (Did you click on any of the example links in that thread?) Thing is, it is much more difficult to troubleshoot when a toolkit is used, compared to typing in the commands yourself.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
It's not about other toolkits, and it's certainly not about other phones -- it's a GNex thread...
It's fine to use a toolkit when you understand how it's doing things, but if you don't, AND something screws up, you'll be right back here with a new thread saying something like: "I used a toolkit to do abc and now it won't xyz", and asking for help. (Did you click on any of the example links in that thread?) Thing is, it is much more difficult to troubleshoot when a toolkit is used, compared to typing in the commands yourself.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yeah efrant you said it, I don't have your way with words man.
Sent from my i9250

efrant said:
It's not about other toolkits, and it's certainly not about other phones -- it's a GNex thread...
It's fine to use a toolkit when you understand how it's doing things, but if you don't, AND something screws up, you'll be right back here with a new thread saying something like: "I used a toolkit to do abc and now it won't xyz", and asking for help. (Did you click on any of the example links in that thread?) Thing is, it is much more difficult to troubleshoot when a toolkit is used, compared to typing in the commands yourself.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
At the end of last year, knowing that I will get a Nexus One and encourage by a relative, I decided to mod my G1.
It was a painful experience, for the XDA devs and Forum members, because I was totaly new and inexperienced.
I would like to pay tribute mostly to Frankdrey for his constant and kind help.
I was embarrassed and ashamed by my misunderstanding and mistakes. He never gave up on me.
I am for ever grateful to him. Should I say I hate him for giving me the virus of toying my phones.
He was not alone in his help. Demkator brought his much needed contribution too.
I am very thankful to him. And, of course, I took advantage of the outstanding job done by Ezterry.
Without them I would not have succeeded in rooting my G1.
Without them I would have not learn how to unlock, root, select the right radio, a Rom, a Kernel. Without the knowledge I acquired from them I would not have tried to mod my Nexus One after getting my GSM GalaxyNexus.
Maybe I would have had two bricks.
If at the time I had found a Toolkit chances are that, during my strugle to understand and implement the different steps to use Adb and Fastboot and to install a Rom, I would have embrace it.
That is why I fully agree with you, Efrant: we learn and the more we learn the more we increase our capabilities.
As far as my Galaxy Nexus is concerned I am waiting for the OTA to use and play with it.
Then I will unlock it (thanks, Efrant for the tutorial) and put a Rom and apps.
Needless to say I hope that we will be able to install a "unified search" as it is now with ICS 4.04.

Toolkit question

I've been using the GNex toolkit since I got my nexus and never had one issue. Even flashed stock 4.1.1 on it. My question is, why is everyone so against the toolkit? Why is it so dangerous? Please don't bash me because I came from an Atrix 2 and have only been using the nexus for a couple weeks but I'm just curious. Thanks.
Sent from my Galaxy Nexus using xda premium

http://forum.xda-developers.com/showthread.php?t=1469909
basically, the toolkits sometimes fail.. and fail hard. like at one point, the toolkit wanted to flash a verizon firmware on to a GSM phone (which can brick the phone). or something goes wrong, and the user has no idea how to fix it so the thread begins with "i used such and such toolkit, but i have no idea why my phone wont boot. HALP!"

I would like to say that the Toolkit actually is a shell of the adb command and fastboot command. That's all.

Using a toolkit means clicking a few buttons and not thinking about what you're doing.
%90 percent of all "OMG BRICKED" posts begin with "I used _______ toolkit to unlock and root. I've been on ____________ for ________ weeks and flashed ____________ and now it won't boot!"
This in itself speaks leaps-and-bounds about the user.
Using a toolkit to unlock and root should have no impact on future usage.
If you used toolkitA and she used toolkitB the information is not relevant.
This leads me to believe they think the toolkit is doing some mystical process (it isn't) specific to that "method" or "program."
Then, say, I want them to ADB push something to their phone.
Or ADB pull their SDCard to save it.
They have no idea what I'm talking about...and I (and others) are stuck trying to teach them how to set up ADB and get the drivers correctly installed with a broken device.
If you have ADB set up...and know it's working...it's 100x easier to fix things when they go wrong.
But if you're "bricked" and then tell us "adb devices" isn't showing anything and all commands list "no device found" we don't know if it's because ADB/drivers are set up incorrectly or if your phone is truly hosed to the point of being unrecognized...again, leading to more guesstimation in the debugging process.
Also, the toolkit will say "done" and not spit out any errors that help to debug if something goes wrong.
All-in-all...
Any user who chooses the toolkit over a few simple commands is going to end up with more problems...due to lack of knowledge.
Doing things manually is not only easy; but a learning process.
I'd recommend you look at my guide.
You don't need to unlock/root again or anything...
But get ADB/Fastboot set up and push a file to your phone to see how it all works.

Right packaged all in one folder with basic commands. But wouldnt the main cause of toolkit errors be user error? Because all the commands are set for each option example: if I choose to unlock the boot loader on GSM Maguro 4.1.1 then it'll 100% always unlock my boot loader correct? But if I, by mistake, choose the Toro etc and it messes me up then I could in theory blame the toolkit because I didn't pay attention therefore I would've suspected the toolkit as the culprit. So I'm saying, errors with the toolkit are all basically user errors right?
Sent from my Galaxy Nexus using xda premium

DarkJatrix said:
Right packaged all in one folder with basic commands. But wouldnt the main cause of toolkit errors be user error? Because all the commands are set for each option example: if I choose to unlock the boot loader on GSM Maguro 4.1.1 then it'll 100% always unlock my boot loader correct? But if I, by mistake, choose the Toro etc and it messes me up then I could in theory blame the toolkit because I didn't pay attention therefore I would've suspected the toolkit as the culprit. So I'm saying, errors with the toolkit are all basically user errors right?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
no. its not all user error. this is an example: http://forum.xda-developers.com/showthread.php?t=1803743

Jubakuba said:
Using a toolkit means clicking a few buttons and not thinking about what you're doing.
%90 percent of all "OMG BRICKED" posts begin with "I used _______ toolkit to unlock and root. I've been on ____________ for ________ weeks and flashed ____________ and now it won't boot!"
This in itself speaks leaps-and-bounds about the user.
Using a toolkit to unlock and root should have no impact on future usage.
If you used toolkitA and she used toolkitB the information is not relevant.
This leads me to believe they think the toolkit is doing some mystical process (it isn't) specific to that "method" or "program."
Then, say, I want them to ADB push something to their phone.
Or ADB pull their SDCard to save it.
They have no idea what I'm talking about...and I (and others) are stuck trying to teach them how to set up ADB and get the drivers correctly installed with a broken device.
If you have ADB set up...and know it's working...it's 100x easier to fix things when they go wrong.
But if you're "bricked" and then tell us "adb devices" isn't showing anything and all commands list "no device found" we don't know if it's because ADB/drivers are set up incorrectly or if your phone is truly hosed to the point of being unrecognized...again, leading to more guesstimation in the debugging process.
Also, the toolkit will say "done" and not spit out any errors that help to debug if something goes wrong.
All-in-all...
Any user who chooses the toolkit over a few simple commands is going to end up with more problems...due to lack of knowledge.
Doing things manually is not only easy; but a learning process.
I'd recommend you look at my guide.
You don't need to unlock/root again or anything...
But get ADB/Fastboot set up and push a file to your phone to see how it all works.
Click to expand...
Click to collapse
I'm very familiar with ADB I had an HTC amaze and a couple days after the release I had to learn adb really quick in unlocking the boot loader and flashing custom Roms. I just like convenience of having everything in one folder and one program. I do trust ADB but my issue has always been putting files in right folders and pushing and pulling files etc. Lol. But I appreciate the info you guys. I'll think twice before using toolkits again.
Sent from my Galaxy Nexus using xda premium

Zepius said:
no. its not all user error. this is an example: http://forum.xda-developers.com/showthread.php?t=1803743
Click to expand...
Click to collapse
Lest* better to use adb, I've used jubakuba's guide and worked flawless.
I don't hate toolkits but they seem to cause more problems rather then solve. Anyone who I see needs to root I direct them to jubakuba's thread.
Sent from my Galaxy Nexus using Tapatalk 2

withbloodskies said:
Lest* better to use adb, I've used jubakuba's guide and worked flawless.
I don't hate toolkits but they seem to cause more problems rather then solve. Anyone who I see needs to root I direct them to jubakuba's thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's what I'm saying. I am plenty smart enough to read before I flash, therefore I wouldn't of flashed that and I wouldn't of had an issue but if someone else would've flashed it then it would've technically been their fault for not paying attention. I understand that the toolkit had the mistake but if I pay close attention than I'll notice the mistakes and avoid them. Does that sou d pretty knowledgeable?
Sent from my Galaxy Nexus using xda premium

[Q] How to root my Galaxy Nexus but still get OTA updates from Google?

Excuse my complete noobishness, but can someone help me root my Galaxy Nexus but still get OTA updates from Google? I found multiple sources from here and a video from QBKing77 but nothing answer my question completely. I would be really grateful if someone with experience could help me by give me step by step instructions.
Thank you.

Rooting your phone does not disable OTA updates.

Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
Sent from my Galaxy Nexus using Tapatalk 2

eqjunkie829 said:
Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...

ZlateWay said:
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...
Click to expand...
Click to collapse
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
Sent from my Galaxy Nexus using Tapatalk 2

The_other_ray said:
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That is what I'm looking for! Can you explain to me step by step how did you did that? It would be great if you help me.

Use the guide in my sig or stickied at the top of this forum.
Only change would be fastboot boot recovery cwm.img rather than flash.

Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
Sent from my Galaxy Nexus using Tapatalk 2

suprakarma said:
Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks

ZlateWay said:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
Click to expand...
Click to collapse
Don't use the toolkit?
Sent from my Galaxy Nexus

Why not?
The toolkit is SUPER easy.
Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.
I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.
A lot of the custom roms aren't to my taste so I am happy to keep the stock experience
Will post again the steps when I am on my home PC.

anotherxdauser said:
Why not?
The toolkit is SUPER easy.
Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.
I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.
A lot of the custom roms aren't to my taste so I am happy to keep the stock experience
Will post again the steps when I am on my home PC.
Click to expand...
Click to collapse
simply because the toolkit is an excuse not to learn the FUNDAMENTALS of owning a nexus device.
what happens when something goes wrong? do you know what the toolkit is doing behind the scenes? most of the toolkit users DONT. there are more than enough 'HALP!1!1 I BriKt mah PhoneZ!1!!oneone' to prove this is the case....
if you understand what its actually doing, you understand how useless it truly is...

Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.
Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.
Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.
Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.
Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.
Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.
Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.
Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.
Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?

anotherxdauser said:
Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.
Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.
Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.
Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.
Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.
Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.
Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.
Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.
Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?
Click to expand...
Click to collapse
And yet another person who fails at grasping why XDA exists....
Sent from my Galaxy Nexus

Actually, I do. I understand why XDA exists but I also understand the multi-uses it really has.
Not everyone who comes here has a desire to mess with their phones all the time...
If you're not a fan of the toolkit, why not flame the developer?
Here's a short guide on what the OP wanted to do.
1) Make sure phone is up to date. Make a note of your software version - probably 4.1.2 or 4.2 and build number (mine is JZO54K)
2) Turn on USB Debugging (Settings > Developer Options > USB Debugging)
3) Shut down the phone
4) Start in Bootloader (power button + vol up + vol down)
5) Run the Galaxy Nexus toolkit
This is where we use the toolkit. Read the info and select your build number. The windows will guide you through what options you have. If you want to root only, choose that option. Go through the menus and type YES to begin.
6) Phone will restart
7) After ~160 seconds, ToolKit will restart to Bootloader
8) Phone will restart
9) Toolkit will finish rooting by pushing the files to the phone.
10) Phone will restart back to Bootloader
11) Finish - Confirm in ToolKit
See pictures for further info.

Pirateghost said:
And yet another person who fails at grasping why XDA exists....
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
the toolkit also exists on xda..

k786 said:
the toolkit also exists on xda..
Click to expand...
Click to collapse
So does the person that thought I was saying the toolkit did something malicious... I never said any such thing.
Toolkits are pointless. It takes longer to learn the toolkit than it does the three commands needed to unlock and root a nexus. That's my ****ing point, yet this guy is going on about how easy the toolkit is to use. If it's so ****ing easy, why did you have to provide screenshots and instructions?
XDA-spoonfeeders.com
I miss XDA
Sent from my Galaxy Nexus
**edit**
i cannot believe that someone would actually think its NOT beneficial to understand the process, and rely solely on a toolkit...its amazing to think that there are people so wrapped up in their own little minds, that they refuse to take the time to learn to do things the right way and understand what they are doing to their device.
what happens when joe user, who only knows the toolkit, flashes a mod on his phone that was NOT intended for his phone/build/rom version, and he bootloops? he jumps on xda and posts a thread. HALP I JACKED MAH PHONE!!! how do i fix it with the toolkit?
please, for the love of tech, LEARN what it is you are doing. do us all a favor and help spread the KNOWLEDGE and stop with the damn toolkit. this website is designed for you to learn, not follow a damn prompt/menu to get instant gratification.

ZlateWay said:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
Click to expand...
Click to collapse
Don't use a toolkit. Learn commands yourself and you won't have to worry about what a toolkit is or isn't installing.
Sent from my Galaxy Nexus using xda premium

root toolkits are fine, if you already know what you are doing. the problem with root toolkits arises when a person that has no idea what they are doing uses them and messes something up, which happens often, just read all the threads that users start asking for help, that include the words "i used a root toolkit". you dont see any these thread with the words i used fastboot or adb. usually what happens is something simple gets messed up, then the situation becomes worse because the user didnt know/learn the basics, and messed something up after. this is the problem with root toolkits, they go around you having to learn the basics. then we get all these threads about "help, i bricked my device". just taking the little time needed to learn the basics prevent this from happening.
this is a nexus device, its meant to be able to root the device easily. this is the basic procedure.. fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries or custom rom in your custom recovery, reboot. that is it. it takes me 3 minutes to do this. add on a little reading beforehand, and maybe itll take you 30 minutes. much better than getting lost after using the root toolkit, or even messing up your device messing with stuff that you shouldnt. and, occasionally, the root toolkit itself can mess things up.
btw, op, you can always install an official "ota" manually, without receiving it ota, and without having root too. also, if you flash a rooted stock rom(unmodified, only root), youll still receive otas

You can unlock and root without install a custom recovery. IF you don't install any custom recovery and leave the stock one you'll continue to receive the ota updates.
Bye
Sent from my Galaxy Nexus using xda app-developers app