Related
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.
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
Got an Australian Gnex running 4.04. The OTS jellybean update is months away according to Vodafone AU so ive been looking into manual solution that causes the least disruption possible. Very tough diciphering the language on here. My apologies but there doesnt seem to be a specific thread that can help.
From what i have read - I can open the Bootloader and somehow flash the factory image without rooting?
Was on the dev page at google to get the latest firmware? - ive DL'd yakju Android 4.1.1 (JRO03C)
I have already unlocked the bootloader with a toolkit for mac found here on XDA. i just dont know what to do next? The file is a .tgz which ive never heard of? dont you normally copy the whole zip file to the SD card then boot into recovery and somehow flash the new firmware? Help.
bigdave78 said:
Got an Australian Gnex running 4.04. The OTS jellybean update is months away according to Vodafone AU so ive been looking into manual solution that causes the least disruption possible. Very tough diciphering the language on here. My apologies but there doesnt seem to be a specific thread that can help.
From what i have read - I can open the Bootloader and somehow flash the factory image without rooting?
Was on the dev page at google to get the latest firmware? - ive DL'd yakju Android 4.1.1 (JRO03C)
I have already unlocked the bootloader with a toolkit for mac found here on XDA. i just dont know what to do next? The file is a .tgz which ive never heard of? dont you normally copy the whole zip file to the SD card then boot into recovery and somehow flash the new firmware? Help.
Click to expand...
Click to collapse
All the info you need is in this post: http://forum.xda-developers.com/showthread.php?t=1626895
Petrovski80 said:
All the info you need is in this post: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thanks - i had read that thread but im stuck at the directory commands. its not working on mac.
Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.
Petrovski80 said:
Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
bigdave78 said:
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.
Click to expand...
Click to collapse
Question remains - once the bootloader is unlocked - can you install the downloaded google factory image from recovery without any complex commands?
bigdave78 said:
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.
Click to expand...
Click to collapse
It is not complicated at all. If you don't know how to open a terminal window and type in commands, it has nothing to do with android or flashing. It has to do with knowing how to use your computer.
I already replied to you in the other thread: to switch directories in a terminal, you use the cd command, i.e., cd /this/is/where/my/files/are
Lack of knowledge on how to use your Mac should not be confused with anything Android... not related at all.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
It is not complicated at all. If you don't know how to open a terminal window and type in commands, it has nothing to do with android or flashing. It has to do with knowing how to use your computer.
I already replied to you in the other thread: to switch directories in a terminal, you use the cd command, i.e., cd /this/is/where/my/files/are
Lack of knowledge on how to use your Mac should not be confused with anything Android... not related at all.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I genuinely appreciate the help, but realise that 95% of computer users will never open a terminal and type a command. Ive typed your commands in terminal but its not working and i dont understand directories. If i dont ask questions ill never learn will i? I cant see your reply anywhere??
bigdave78 said:
I genuinely appreciate the help, but realise that 95% of computer users will never open a terminal and type a command. Ive typed your commands in terminal but its not working and i dont understand directories. If i dont ask questions ill never learn will i? I cant see your reply anywhere??
Click to expand...
Click to collapse
Asking questions if you don't understand is perfectly fine... and I'm willing to help. But complaining that a procedure is complicated and lengthy when it actually is not, is not cool.
As for your issue (although I've never used MacOS): if you save the files in a directory call junk, and junk is located in myname, the the command to reach junk would be something like: cd /myname/junk. Or, find a way to open a terminal in the junk directory to begin with -- I'm sure if you search any Mac help site (with something like how to open a terminal) you can easily find that out, no?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Asking questions if you don't understand is perfectly fine... and I'm willing to help. But complaining that a procedure is complicated and lengthy when it actually is not, is not cool.
As for your issue (although I've never used MacOS): if you save the files in a directory call junk, and junk is located in myname, the the command to reach junk would be something like: cd /myname/junk. Or, find a way to open a terminal in the junk directory to begin with -- I'm sure if you search any Mac help site (with something like how to open a terminal) you can easily find that out, no?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The fact ive sat here for more than 4 hours reading through threads, searching forums, reading tech sites, asking friends, unlocking the bootloader, downloading firmware, trying desperately to make 'terminal' work with your method, and leaving posting in this forum as the last resort - is testmanet to how complicated this is to a new user - especially one on a mac system. Ive used one click root methods previously when i had access to windows - unfortunately i dont anymore. I think the guides are easy to follow as a PC user, not necessarily for a mac. Ive tried to use terminal to locate the files, i cant do it. dont understand the basic principals involved to understand the mistakes im making.
bigdave78 said:
The fact ive sat here for more than 4 hours reading through threads, searching forums, reading tech sites, asking friends, unlocking the bootloader, downloading firmware, trying desperately to make 'terminal' work with your method, and leaving posting in this forum as the last resort - is testmanet to how complicated this is to a new user - especially one on a mac system. Ive used one click root methods previously when i had access to windows - unfortunately i dont anymore. I think the guides are easy to follow as a PC user, not necessarily for a mac. Ive tried to use terminal to locate the files, i cant do it. dont understand the basic principals involved to understand the mistakes im making.
Click to expand...
Click to collapse
I think you are making it more complicated that it really is. When you open a terminal, in which directory does it open? In other words, what is the prompt that you see? THAT is the directory that you should download and extract all the files to.
That's the problem you need to fix. Read some basics about macosx. Get comfortable using it. Then proceed with flashing your gnex.
This looks like a good tutorial:
http://guides.macrumors.com/Terminal
Sent from my Galaxy Nexus using Tapatalk 2
I'm now rooted with super user acces. followed techfanatic9's guide in the Mac thread and keyed in the commands in terminal. But now how do i install the factory image from Google?Yakju-jro030c? Its not a rom is it??
Do i still need to learn terminal commands???
bigdave78 said:
I'm now rooted with super user acces. followed techfanatic9's guide in the Mac thread and keyed in the commands in terminal. But now how do i install the factory image from Google?Yakju-jro030c? Its not a rom is it??
Do i still need to learn terminal commands???
Click to expand...
Click to collapse
Another issue you are having is that you are trying too many different methods, and confusing them. There was no need to root if you are flashing a new rom.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Another issue you are having is that you are trying too many different methods, and confusing them. There was no need to root if you are flashing a new rom.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, so now there is no way i can do this because im rooted? ...im a frustrated, technically struggling user that just wants to try and get jelly bean stock image - nothing more extravagant than that. ive tried to follow every instruction to the letter.....aside from having to learn terminal language for OSx, im doing my best. come on dude, not everyone has that kind of time
bigdave78 said:
Okay, so now there is no way i can do this because im rooted? ...im a frustrated, technically struggling user that just wants to try and get jelly bean stock image - nothing more extravagant than that. ive tried to follow every instruction to the letter.....aside from having to learn terminal language for OSx, im doing my best. come on dude, not everyone has that kind of time
Click to expand...
Click to collapse
You can still flash the stock jb as per my instructions. It's just that rooting made no difference - it was a wasted step.
And as I said before, you don't have to learn the commands, as I've written them out for you. You just need to find out how to save the files and open a terminal in the same folder, which doesn't seem like a difficult thing to do. Google should be able to tell you how to open a terminal in a specific folder. Or, as I mention before, save the files in the folder which you already have your terminal open.
The whole purpose of my guide was to learn -- and you are have a more difficult time than others because you have taken shortcuts (I.e. 1-click methods) in the past.
I agree, not everyone has that kind of time: I have 3 kids (with everything that comes along with that), work a high-stress, 70 hour a week job, and no IT/tech/linux/android background, but I managed.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
You can still flash the stock jb as per my instructions. It's just that rooting made no difference - it was a wasted step.
And as I said before, you don't have to learn the commands, as I've written them out for you. You just need to find out how to save the files and open a terminal in the same folder, which doesn't seem like a difficult thing to do. Google should be able to tell you how to open a terminal in a specific folder. Or, as I mention before, save the files in the folder which you already have your terminal open.
The whole purpose of my guide was to learn -- and you are have a more difficult time than others because you have taken shortcuts (I.e. 1-click methods) in the past.
I agree, not everyone has that kind of time: I have 3 kids (with everything that comes along with that), work a high-stress, 70 hour a week job, and no IT/tech/linux/android background, but I managed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I didnt find how to move the terminal command subject and i did try many different pages via google and many different ways of phrasing the query. So i just dumped all the files onto the desktop as that was where terminal seemed to be referringand it seems to be working. im waiting for the final reboot - its taking a long time. :fingers-crossed:
bigdave78 said:
I didnt find how to move the terminal command subject and i did try many different pages via google and many different ways of phrasing the query. So i just dumped all the files onto the desktop as that was where terminal seemed to be referringand it seems to be working. im waiting for the final reboot - its taking a long time. :fingers-crossed:
Click to expand...
Click to collapse
I think you got it! The first boot will take significantly longer than usually.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I think you got it! The first boot will take significantly longer than usually.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Still waiting. should it take 15 minutes plus??
40 minutes. Stuck on the black screen with google and the lock at the bottom?
take it this is bad news.
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