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
Related
I have a Droid Charge right now and I'm planning on getting a Google Nexus as soon as I have some time to go up to the store to actually get the phone.
But the question I have is, how do I root it? The Verizon LTE version. Because... it simply comes down to this; if I can't root it, I don't want it.
With the manual way. The adb way. Or the fast boot way. I also seen this on Droid-Life yesterday and it seems like one of those quick "one click root" methods. I never tried it so I don't know. Here's the link
http://www.droid-life.com/2012/01/1...-receives-load-of-new-features/#disqus_thread
I found this...
http://forum.xda-developers.com/showthread.php?t=1400871
I'm assuming that that's what I need to root this beast?
Also... do I have to unlock the bootloader? I've never had to unlock a bootloader, the Droid Charge which I have right now didn't have a locked bootloader.
trparky said:
I found this...
http://forum.xda-developers.com/showthread.php?t=1400871
I'm assuming that that's what I need to root this beast?
Also... do I have to unlock the bootloader? I've never had to unlock a bootloader, the Droid Charge which I have right now didn't have a locked bootloader.
Click to expand...
Click to collapse
You have to unlock the bootloader by setting up ADB after installing the android SDK to your computer. There are a ton of step by step guides for this but it is super easy and requires only one command after the set up is complete "fastboot OEM unlock" then I recommend using the CF-Root method that also has the guide here on XDA. The CF-Root method is also on command and basically just adds root to your stock rom.
---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------
badassirocz said:
You have to unlock the bootloader by setting up ADB after installing the android SDK to your computer. There are a ton of step by step guides for this but it is super easy and requires only one command after the set up is complete "fastboot OEM unlock" then I recommend using the CF-Root method that also has the guide here on XDA. The CF-Root method is also on command and basically just adds root to your stock rom.
Click to expand...
Click to collapse
Here is the CF-Root link
http://forum.xda-developers.com/showthread.php?t=1396952
So you don't recommend using the method in the forum thread I mentioned?
I already have ADB installed on my computer and have used it multiple times to do shell-related stuff and to push/pull files.
I would use regular ADB command prompts. Download and install the Samsung drivers and go to town. The only thing you may experience is after you install the drives and start ADB command if it hangs on waiting for device you need to go into device manager on you computer and you should see your phone listed with a yellow question mark or exclamation point. You need to select it and manually install the drivers from there. Still a piece a cake and the must fool proof way to go.
trparky said:
So you don't recommend using the method in the forum thread I mentioned?
I already have ADB installed on my computer and have used it multiple times to do shell-related stuff and to push/pull files.
Click to expand...
Click to collapse
use the post that you found, if you have driver problems install PDAnet. It will work like a charm, just make sure you read all the way through first then start again from the beginning and do it step by step. Don't need to bother with adb anymore that the rootkit is out, its quick and easy and a great tool if your not comfortable with ADB
Edit: Also not to be a jerk, but you really should just search the development forum instead of cluttering the forums. You found the answer yourself.
I used the GNex Toolkit found on the development forum.
GSM Version: http://forum.xda-developers.com/showthread.php?t=1392310
LTE / CDMA Version: http://forum.xda-developers.com/showthread.php?t=1400871
Really simple and easy to use. It does it all for you. All you have to do is know what current build your phones running, by going into Settings->About Phone.
Load it up, select build version, hit the Unlock,Root,Recovery option.
I'd recommend you do this immediately, as unlocking the bootloader wipes your phone.
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
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
Hi,
I want to root my Galaxy Nexus (T-Mobile) but the WugFresh root toolkit wants to know if my device is "TAKJU-MAGURO" or "YAKJU-MAGURO".
My settings don't mention either one: http://db.tt/SlNoG0Yi (screen shot)
How can I find it? I'm using the latest stock ROM from Samsung.
Thanks in advance...
Go into maps, check about, and it will list your make
root your maguro the right way.. fastboot OEM unlock, fastboot flash a custom recovery, flash either the su binaries or a custom ROM in your new recovery, reboot and profit. this is a nexus device, google made it easy for us to unlock our bootloader and root our devices.
simms22 said:
root your maguro the right way.. fastboot OEM unlock, fastboot flash a custom recovery, flash either the su binaries or a custom ROM in your new recovery, reboot and profit. this is a nexus device, google made it easy for us to unlock our bootloader and root our devices.
Click to expand...
Click to collapse
How is that easier than WugFresh?
BarryF said:
Hi,
I want to root my Galaxy Nexus (T-Mobile) but the WugFresh root toolkit wants to know if my device is "TAKJU-MAGURO" or "YAKJU-MAGURO".
My settings don't mention either one: http://db.tt/SlNoG0Yi (screen shot)
How can I find it? I'm using the latest stock ROM from Samsung.
Thanks in advance...
Click to expand...
Click to collapse
There's an option on wugfresh that says yakju-takju any build, when you select your build use that instead, then wugfresh will automatically find what build your gnex is an select the right one for you, I had wugfresh toolkit 1.5.5 version which is the latest, I assume you do to.
Sent from my Galaxy Nexus using xda premium
BarryF said:
How is that easier than WugFresh?
Click to expand...
Click to collapse
you can type three words right? "fastboot OEM unlock" unlocks you bootloader. then the four words "fastboot flash recovery recoveryname.img" flashes your recovery. then in your recovery you just select your file that you want to flash, then reboot. hows that harder than Wugs? then when you mess up your device, you will be familiar how to fix it, with your recovery or fastboot.
simms22 said:
you can type three words right? "fastboot OEM unlock" unlocks you bootloader. then the four words "fastboot flash recovery recoveryname.img" flashes your recovery. then in your recovery you just select your file that you want to flash, then reboot. hows that harder than Wugs? then when you mess up your device, you will be familiar how to fix it, with your recovery or fastboot.
Click to expand...
Click to collapse
That sounds way harder to me.
Sent from my Galaxy Nexus using Tapatalk 2
It's slightly harder but really great to know how to do in case you run into issues in the future. IMO a basic knowledge of fastboot is essential.
Sent from my Galaxy Nexus using xda premium
It seems a little intimidating at first, but with a little reading and patience it's not too difficult. I used a toolkit to root my Evo 4G and ended spending around 3 hours sorting out the problems it caused. I used the method simms22 is describing to root my GNex and even going slow it only took about 45 minutes. The biggest problem I had was getting drivers installed. Take a little time to read the stickies and get familiar with the process. I literally laughed at myself when I was finished and realized how simple those commands are.
Sent from my Galaxy Nexus using xda premium
BarryF said:
That sounds way harder to me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No it's actually easier. Really, just open an adb/command prompt and just type what simms said. Really basic. BTW it will be good to learn this so u can get the CWMR Touch for free and flash it via fastboot.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
As much as I would love to learn fastboot (really), I don't have the time, and now I'm scared of using WugFresh. I guess I will root my device another time.
Thanks for all the replies!
BarryF said:
As much as I would love to learn fastboot (really), I don't have the time, and now I'm scared of using WugFresh. I guess I will root my device another time.
Thanks for all the replies!
Click to expand...
Click to collapse
Nothing wrong with waiting until you are a bit more comfortable. Keep reading here at XDA. The more of that you are willing to do, the less scary it is. Check out the threads asking questions about problems. Even if you don't have the problem, you will be getting familiar with the terminology and problem solving methods.
Sent from my Galaxy Nexus using xda premium
Pierceye said:
It seems a little intimidating at first, but with a little reading and patience it's not too difficult. I used a toolkit to root my Evo 4G and ended spending around 3 hours sorting out the problems it caused. I used the method simms22 is describing to root my GNex and even going slow it only took about 45 minutes. The biggest problem I had was getting drivers installed. Take a little time to read the stickies and get familiar with the process. I literally laughed at myself when I was finished and realized how simple those commands are.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It's definitely a little intimidating at first. For me the hardest part was getting the sdk set up properly (I'm sure the alcohol didn't help ) but now I can't imagine using a kit or a "1-click" method.
TomBall718 said:
It's definitely a little intimidating at first. For me the hardest part was getting the sdk set up properly (I'm sure the alcohol didn't help ) but now I can't imagine using a kit or a "1-click" method.
Click to expand...
Click to collapse
Lol! Yeah, liquor and technology can make things unpleasantly interesting.
Sent from my Galaxy Nexus using xda premium
The truth is, I am an Android dev and quite comfortable with adb and the sdk. However I've never flashed a ROM or know anything about bootloaders, and only have one device to experiment with, which is my development device, and I can't take the chance of bricking it. The only reason I want to root right now is because I need to run an app that requires it (Screencast Video Recorder).
I wish I had another device to experiment with!
slayr76 said:
There's an option on wugfresh that says yakju-takju any build, when you select your build use that instead, then wugfresh will automatically find what build your gnex is an select the right one for you, I had wugfresh toolkit 1.5.5 version which is the latest, I assume you do to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Agreed! Its terribly easy to install SDK from Google, Download a recovery, download the SU (superuser) and a ROM of choice and be done with it within 3 minutes. The one-click stuff is convenient but always ends up with more problems. One step out of place and you brick your phone. Furthermore, if you can't run a simple command line on your computer, should you really be rooting your phone? Just common sense man.
andrewjt19 said:
Agreed! Its terribly easy to install SDK from Google, Download a recovery, download the SU (superuser) and a ROM of choice and be done with it within 3 minutes. The one-click stuff is convenient but always ends up with more problems. One step out of place and you brick your phone. Furthermore, if you can't run a simple command line on your computer, should you really be rooting your phone? Just common sense man.
Click to expand...
Click to collapse
I'm perfectly comfortable at a command line but this "simple command" just seems easier to you because you're very experienced and you can make assumptions that I can't. For example you make "download a ROM of choice" sound so easy, but I wouldn't even know where to start to choose and then find the right ROM. (Besides, I only want to root my current ROM, not change ROMs).
I also have no doubt that "one step out of place and you brick your phone" applies as much to fastboot as it does to WugFresh. No?
Anyway, in my personal experience there is always critical information missing or major assumptions in the docs for custom mods (even the one-click WugFresh docs assumed I knew if my phone was takju or yakju. What the hell is a takju or wakju???). Incomplete docs seems to be the #1 complaint around here when modding.
I wish I knew fastboot as well as you guys, and maybe one day I will, but right now I just need a rooted phone so I can video capture my screen. And I can't risk bricking my only device.
Thanks again for the advice!
You're right about basic assumptions regarding a new user's level of knowledge. It was what made me the most nervous about rooting. If you are already familiar with adb and the command line interface you have a pretty good head start. In the stickies section, Jubakuba, efrant and mskip all have some great information and guides about rooting. Some of the information is a little outdated but worth the read. Start with efrant's Android 101. That will answer a lot of your questions. Oldblue also has a good summary of all of the different firmware versions (takju, yakju). Most of us appreciate that you aren't just diving in and making a mess. Very few us have the money to risk screwing up a several hundred dollar device for the sake of curiosity or experimentation. If you are developing you have even more reason to be cautious. So take your time. As far as bricking the phone goes, you're in luck. The GNex is intended as a developers device and is difficult (not impossible) to hard brick. You've already found your way here to XDA, now it's just a matter of reading and learning. And, I know it's difficult, but try not to let your feathers get ruffled. A thick skin seems to be a prerequisite around here.
Sent from my Galaxy Nexus using xda premium
Hello all. I am new to the N7. I look forward to trying out some of the awesome development in this forum. Before I begin I need to ask some things. I have spent ALL DAY today reading forums and researching this device b4 I begin. But to be honest, I can not spend days reading every post out there and still be a dad here. So I am trying to stream line this some. I am not a newbie in rooting / roming. Sorry if I have not seen a topic like this b4 posting. There are just so many in this forum now to go through. I will delete this one once helped if nessary. Also THANK YOU VERY MUCH in advance for any help I get here.
1. I have a Verizon note 2, Verizon PERMANENTLY locked the bootloaders on their phones so development has stoped/ slowed drastically. I know the N7 has a locked bootloader that can be unlocked. Is this still true on a stock 5.1.1 lollipop version? or Is there a step to reflash to an older rom I should do first?
2. I see the wugs toolkit out there and a nexus toolkit. Is there any reason to use one over the other? Are either of these working on my STOCK 5.1.1 rom still?
3. Can someone please run down the steps to achieve UNLOCK, ROOT, AND CUSTOM RECOVERY? I seen how wugs does all that in it's program. So if that is the way than a good link to use Please.
Once again. Thanks in advance for your help here. Please also feel free to add in here anything I need to be aware of b4 I begin making my N7 a beast of a tablet. I can not wait to try out some of the awesome roms and mods I have seen so far.
:thumbup::beer::thumbup::beer::thumbup::beer::thumbup::beer:
To root or not to root? That is the question.
1. It's unlockable
2. No need for a toolkit just use fastboot, unless you don't want to know what you're doing. It's in the platform-tools folder of the android sdk. There are many guides on xda about how to use it. Don't forget to install googles usb driver.
3. Very easy. Boot the tablet to the bootloader by holding volume down and power while turned off.
Plug into the computer and open a command prompt in whatever folder you have fastboot and type fastboot oem unlock and hit enter. Follow the steps on the tablet.
For recovery download the recovery .img you want and put it in the fastboot folder. Type fastboot flash recovery whatevername.img
To root just download the su zip from here and flash it through recovery.
You need to be careful you don't have a new Nexus 7 version which doesn't allow the mounting of any of the partitions in a custom recovery. I have one of these new Nexus 7s and no matter what I do I can't get the recovery to work, there's a thread about it.
Sent from my SM-G925F using Tapatalk
Batfink33 said:
You need to be careful you don't have a new Nexus 7 version which doesn't allow the mounting of any of the partitions in a custom recovery. I have one of these new Nexus 7s and no matter what I do I can't get the recovery to work, there's a thread about it.
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
Ok so how do I locate n answer to this issue. The serial number in the bootloader info? Or something else?
Thanks for the two answers so far!
:thumbup::thumbup::thumbup::thumbup:
To root or not to root? That is the question.
robrooter said:
Ok so how do I locate n answer to this issue. The serial number in the bootloader info? Or something else?
Thanks for the two answers so far!
[emoji106][emoji106][emoji106][emoji106]
To root or not to root? That is the question.
Click to expand...
Click to collapse
Here's the thread on the issue. I bought my N7 yesterday and I'm affected by this. I can't resolve it and am stuck on stock at the moment which is annoying as I bought it to mess about with Roms and kernels. I'm not sure how you identify which tablets are affected but it seems the later manufactured ones are.
http://forum.xda-developers.com/showthread.php?t=3064562