Related
All -
I am not sure where to go. I am new to a Verizon GNex running stock ICS v4.0.4 and using a mac laptop, and looking to possibly get into rooting. It appears CM9 is popular specially since they appear to have added several of the SIII's new features.
I have read several posts on several sites talking about rooting the GNex. There seems soooooo many different ways to root i'm going crazy. Since I am new to rooting, I am not sure what is the best/easiest way to get started to ensure I don't loose anything.
Any help on the right way to go, any forum posts to start with, etc....would be very much appreciated!!
Thanks!
use this method: http://forum.xda-developers.com/showthread.php?t=1529058
dont use a toolkit either. you'll be better off with the knowledge of what you are doing and people will be more apt to help you if things go wrong.
Zepius said:
use this method: http://forum.xda-developers.com/showthread.php?t=1529058
dont use a toolkit either. you'll be better off with the knowledge of what you are doing and people will be more apt to help you if things go wrong.
Click to expand...
Click to collapse
+1
Thanks
Thank you both for replying, but....I am working on a MacBook and the link you provided appears only to be for a Windows Machine. I luv the walk-thru what exists in the forum - I just need it for a Mac..
Thanks again!
Should be the same deal... just with terminal.
Here is a zip with ad and fast boot needed for Mac. It may also have the recovery and su.zip but ignore those use what the windows tutorial says.
http://db.tt/RDgw4XlM
Sent From My Sprint Galaxy Nexus via XDA Premium
p.cooper said:
Thank you both for replying, but....I am working on a MacBook and the link you provided appears only to be for a Windows Machine. I luv the walk-thru what exists in the forum - I just need it for a Mac..
Thanks again!
Click to expand...
Click to collapse
its basically the same steps just use terminal
ok, thank you. I will look a the zip provided and go from there. Thank you all!
p.cooper said:
Thank you both for replying, but....I am working on a MacBook and the link you provided appears only to be for a Windows Machine. I luv the walk-thru what exists in the forum - I just need it for a Mac..
Thanks again!
Click to expand...
Click to collapse
Exact same method, but use Terminal instead of Command Prompt, and put a "./" in front of every command. For example:
Code:
./adb devices
I have this big problem where I flashed jelly bean and lost root and cwm, boot loader is still unlocked, but I can't access recovery I get this android sign with a clap open and an exclamation mark on it and it doesn't go to recovery so how do I root ? Sry if this is already posted but I can't find anything help full
Thanks I advance
Sent from my Asus Transformer Pad Infinity
ray3andrei said:
I have this big problem where I flashed jelly bean and lost root and cwm, boot loader is still unlocked, but I can't access recovery I get this android sign with a clap open and an exclamation mark on it and it doesn't go to recovery so how do I root ? Sry if this is already posted but I can't find anything help full
Thanks I advance
Sent from my Asus Transformer Pad Infinity
Click to expand...
Click to collapse
Try rerooting or flashing the stock image using this
http://forum.xda-developers.com/showthread.php?t=1454314
This one works also, out of experience.
http://forum.xda-developers.com/showthread.php?t=1392310
jprocha101 said:
Try rerooting or flashing the stock image using this
http://forum.xda-developers.com/showthread.php?t=1454314
Click to expand...
Click to collapse
Rerooting doesn't work I may flash 4.0.4 stock back and then install cwm and stock 4.1 and imediatly super su... but will this wipe any of my files ?
Many thanks
Sent from my Jelly Beaned GNexus
ray3andrei said:
Rerooting doesn't work I may flash 4.0.4 stock back and then install cwm and stock 4.1 and imediatly super su... but will this wipe any of my files ?
Many thanks
Sent from my Jelly Beaned GNexus
Click to expand...
Click to collapse
Just flash the file that is located in post #2 in the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
ray3andrei said:
I have this big problem where I flashed jelly bean and lost root and cwm, boot loader is still unlocked, but I can't access recovery I get this android sign with a clap open and an exclamation mark on it and it doesn't go to recovery so how do I root ? Sry if this is already posted but I can't find anything help full
Thanks I advance
Sent from my Asus Transformer Pad Infinity
Click to expand...
Click to collapse
jprocha101 said:
Try rerooting or flashing the stock image using this
http://forum.xda-developers.com/showthread.php?t=1454314
Click to expand...
Click to collapse
Mikedick said:
This one works also, out of experience.
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
why are you suggesting using a toolkit to a user that doesn't know what's happening manually, let alone what a toolkit does.
It will be that much harder to track down any issues that may arise.
bk201doesntexist said:
why are you suggesting using a toolkit to a user that doesn't know what's happening manually, let alone what a toolkit does.
It will be that much harder to track down any issues that may arise.
Click to expand...
Click to collapse
LOL, I think that's the whole point of the ToolKit.. So the user doesn't have to go through the manual stuff. Kind of hard to mess up on the V7 toolkit. The Dev made it pretty much dummy proof. As long as the drivers(Android 1.0) are installed on your computer you're pretty much good 2 go
Screwhead24 said:
LOL, I think that's the whole point of the ToolKit.. So the user doesn't have to go through the manual stuff.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909
Screwhead24 said:
Kind of hard to mess up on the V7 toolkit. The Dev made it pretty much dummy proof. As long as the drivers(Android 1.0) are installed on your computer you're pretty much good 2 go
Click to expand...
Click to collapse
I beg to differ. Take a look at some of the linked posts in the link I posted above, and you may feel differently.
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
I beg to differ. Take a look at some of the linked posts in the link I posted above, and you may feel differently.
Click to expand...
Click to collapse
Yeah I'm aware of that thread but 90% of that entire thread are just back and forth post of their experience with other toolkits with other phones and how people should learn how to do it manually and yada yada LOL.. I read that entire thread before I used V7 toolkit to root mines and have to say I don't see what the big fuss is about when someone wants to do it the easy way. It's very simple and very hard to mess up.. All you do is press 1,2,3 ect.
Screwhead24 said:
Yeah I'm aware of that thread but 90% of that entire thread are just back and forth post of their experience with other toolkits with other phones and how people should learn how to do it manually and yada yada LOL.. I read that entire thread before I used V7 toolkit to root mines and have to say I don't see what the big fuss is about when someone wants to do it the easy way. It's very simple and very hard to mess up.. All you do is press 1,2,3 ect.
Click to expand...
Click to collapse
It's not about other toolkits, and it's certainly not about other phones -- it's a GNex thread...
It's fine to use a toolkit when you understand how it's doing things, but if you don't, AND something screws up, you'll be right back here with a new thread saying something like: "I used a toolkit to do abc and now it won't xyz", and asking for help. (Did you click on any of the example links in that thread?) Thing is, it is much more difficult to troubleshoot when a toolkit is used, compared to typing in the commands yourself.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
It's not about other toolkits, and it's certainly not about other phones -- it's a GNex thread...
It's fine to use a toolkit when you understand how it's doing things, but if you don't, AND something screws up, you'll be right back here with a new thread saying something like: "I used a toolkit to do abc and now it won't xyz", and asking for help. (Did you click on any of the example links in that thread?) Thing is, it is much more difficult to troubleshoot when a toolkit is used, compared to typing in the commands yourself.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yeah efrant you said it, I don't have your way with words man.
Sent from my i9250
efrant said:
It's not about other toolkits, and it's certainly not about other phones -- it's a GNex thread...
It's fine to use a toolkit when you understand how it's doing things, but if you don't, AND something screws up, you'll be right back here with a new thread saying something like: "I used a toolkit to do abc and now it won't xyz", and asking for help. (Did you click on any of the example links in that thread?) Thing is, it is much more difficult to troubleshoot when a toolkit is used, compared to typing in the commands yourself.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
At the end of last year, knowing that I will get a Nexus One and encourage by a relative, I decided to mod my G1.
It was a painful experience, for the XDA devs and Forum members, because I was totaly new and inexperienced.
I would like to pay tribute mostly to Frankdrey for his constant and kind help.
I was embarrassed and ashamed by my misunderstanding and mistakes. He never gave up on me.
I am for ever grateful to him. Should I say I hate him for giving me the virus of toying my phones.
He was not alone in his help. Demkator brought his much needed contribution too.
I am very thankful to him. And, of course, I took advantage of the outstanding job done by Ezterry.
Without them I would not have succeeded in rooting my G1.
Without them I would have not learn how to unlock, root, select the right radio, a Rom, a Kernel. Without the knowledge I acquired from them I would not have tried to mod my Nexus One after getting my GSM GalaxyNexus.
Maybe I would have had two bricks.
If at the time I had found a Toolkit chances are that, during my strugle to understand and implement the different steps to use Adb and Fastboot and to install a Rom, I would have embrace it.
That is why I fully agree with you, Efrant: we learn and the more we learn the more we increase our capabilities.
As far as my Galaxy Nexus is concerned I am waiting for the OTA to use and play with it.
Then I will unlock it (thanks, Efrant for the tutorial) and put a Rom and apps.
Needless to say I hope that we will be able to install a "unified search" as it is now with ICS 4.04.
This is my second android device (skyrocket being the first) but that one was easy. All i had to do was "oneclick" which was run a bat file and your rooted. then to get CWM i could use rom manager and i could nandroid/flash/restore/etc
this sgs3 is a little confusing - starting with all the forums. However i hope im in the right forum =)
So out of box SGS3 AT&T - what is the best/easiest way to ROOT and install CWM on it?
for root, i see http://forum.xda-developers.com/showthread.php?t=1739426 but it seems many people have problems with that?
waiters said:
This is my second android device (skyrocket being the first) but that one was easy. All i had to do was "oneclick" which was run a bat file and your rooted. then to get CWM i could use rom manager and i could nandroid/flash/restore/etc
this sgs3 is a little confusing - starting with all the forums. However i hope im in the right forum =)
So out of box SGS3 AT&T - what is the best/easiest way to ROOT and install CWM on it?
for root, i see http://forum.xda-developers.com/showthread.php?t=1739426 but it seems many people have problems with that?
Click to expand...
Click to collapse
I'm brand new to this part of the forum but, I've already seen videos and several threats made to help you with this. You might want to spend some time looking around a little more.
ChumleyEX said:
I'm brand new to this part of the forum but, I've already seen videos and several threats made to help you with this. You might want to spend some time looking around a little more.
Click to expand...
Click to collapse
i finally ended up rooting..
it was a little confusing because the forum said "use odin , download here" and there were 5 versions .. wasn't sure which one to use =) then in the 50 pages, like 20% of the people had problems..
in the end, i used 3.0.7 and the newest AT&T image from here...i had problems at first but that was resolved by using a USB port in the back of my computer instead of the front.
i am now rooted =)
waiters said:
i finally ended up rooting..
it was a little confusing because the forum said "use odin , download here" and there were 5 versions .. wasn't sure which one to use =) then in the 50 pages, like 20% of the people had problems..
in the end, i used 3.0.7 and the newest AT&T image from here...i had problems at first but that was resolved by using a USB port in the back of my computer instead of the front.
i am now rooted =)
Click to expand...
Click to collapse
awesome, because that is the step I'm at.. My work computer won't install the samsung drivers and I'm going to do this at home.
ChumleyEX said:
awesome, because that is the step I'm at.. My work computer won't install the samsung drivers and I'm going to do this at home.
Click to expand...
Click to collapse
My work is the same way. I got an Elago micro-sd card reader to do this. After you have cwm, twrp, etc, you can just download roms, take your micro card out of the device, copy your downloaded rom to the card and re-install.
There is multiple versions. But it should not be difficult to know that of you an AT&T GS3, you don't use the international version or Verizon version.
I do agree that it can be complicated compared to other devices though. But Samsung is a lot better than some companies in this regard. Also, the Nexus devices are something to keep in mind.
Sent from my iPad using Tapatalk HD
Samsung phones are ABSOLUTELY the easiest phones to hack. HTC is the ***** with supercid ****. All I did was use Odin flash a rooted stock image and then went into the market and downloaded GOO MANGAGER and in goo hit settings and hit flash recovery. Tooooooo easy. :thumbup:
Sent from my SGH-I747 using xda app-developers app
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.
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