Hey Guys,
New to the forum here and quite a noob on Android Systems. The GNex is my 1st smart phone and I've had it for 6 months now.
Wanting to root, unlock, and flash the new JB rom onto my phone and is using the ToolKit for the process.
-----------------------------------------------------------------------------------------------------------------------------------------
The original problem is now immaterial, what is bothering me now is installing drivers.....I cannot seem to find a way to properly install the proper drivers for my galaxy nexus. All my laptop would do is install the stock drivers upon connecting the phone to the laptop.
It doesn't matter what drivers im trying to install the condition is the same. I've so far tried out two ways, 1st is following the step by step instruction from efrant, 2nd is installing using the Galaxy Nexus ToolKit v7.0.
For a android noob like me I really have no idea what is going on here @@"
oh and what role does "USB debugging" play in installing drivers? when should it be ticked and when should it not???
----------------------------------------------------------------- below is my original question posted --------------------------------------
However during the 1st step where I need to select my firmware build, I realised the IMM76k build is listed under CDMA where my GNex has this build but is a GSM model.
How should I proceed?? Choose a similar build under GSM or choose the correct build but under CDMA instead??
thanks guys
I would root,unlock, and flash recovery via adb so incase something doesn't work you'll know what happened. Also if you want to use the toolkit just select the correct version under gsm and install the drivers. It should work
I personally would not use a toolkit, as you learn nothing by going that route.
If you want to do it yourself, look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I personally would not use a toolkit, as you learn nothing by going that route.
If you want to do it yourself, look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
actually I was going to do it your way by following through all the steps you have listed out. Like you have said somewhere its like learning math 1st before using a calculator.
However I found myself stuck at the very first part.....installing drivers....
Before yesterday I have not tried to install any driver myself. I guess the only driver that was ever installed to my PC is the one that automatically runs when you plug your phone into a computer for the first time.
When I was following your steps, I first went into device manager --> galaxy nexus --> details --> uninstall driver
and then I have no idea how to install the drivers that I have DL from following your steps. I remember in the instructions you said to plug in my GNex and I should be able to direct the PC to install whatever driver I want, but instead the PC just automatically installed the original drivers again...
So today I decided to give the toolkit a go. As you have seen the 1st problem I ran into was the mixed up variants.....(what does "build code" stand for anyways??)
And the second problem im having now is, again.....it wouldn't install the universal driver. Or at least it does not seem to have installed....
Well, now that I've got your attention D) I would like to follow your steps again if I can get pass the driver issue....I like the JB rom you have uploaded better anyways~~ fan of original stuff from Google!
thanks!!!
Just to mention, my purpose of doing all this is to get to JB faster, and maybe learn more about my device on the way.
My GNex is a GSM model, yakjuzs, build code is IMM76k (this is the odd part) if these information would help solving my problem.
I normally prefer stock google released ROMs.
@CloakedUltraling, installing the drivers is the only tricky part. You need to get to the point where you see something like "Android 1.0" in your device manager with a yellow exclamation point.
To get to that point, right click on anything you see related to Samsung or Android in device manager and click uninstall. Then go to View in the menu at the top and select show hidden devices, and uninstall anything related to Samsung or Android. Then reboot your PC, and once booted, plug your device (while it is booted into the bootloader) to your PC.
Now, you should see something like "Android 1.0". Right-click on that and select update driver, then follow the menu to manually install it, and navigate to the directory where you unzipped 1wayjonny's driver. This needs to be done TWICE: once when your device is booted into the bootloader, and once when it is booted normally.
i was doing some reading since I've missed out the backup step....lol
and I realised that having ADB installed seems to be a pre-requisite for pretty much everything...and which I have not done.
Is this the case for removing/installing drivers as well? ie, do I need ADB installed before doing all this??
OHHHH and Android SDK as well....this looks REALLY important but I have not had any knowledge of this either. Guess I should start from the Android SDK first??
CloakedUltraling said:
i was doing some reading since I've missed out the backup step....lol
and I realised that having ADB installed seems to be a pre-requisite for pretty much everything...and which I have not done.
Is this the case for removing/installing drivers as well? ie, do I need ADB installed before doing all this??
OHHHH and Android SDK as well....this looks REALLY important but I have not had any knowledge of this either. Guess I should start from the Android SDK first??
Click to expand...
Click to collapse
SDK is not required for you (unless you are developing... )
Drivers need to be installed before you can use adb and fastboot - one for each.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Please help me root this device. I have only ever done my Gs2 a few times with flashing etc, so am basically a complete noob.
I have tried for the last couple of hours and am wanting to go mad. I have followed all the lines about unlocking the device and the fastbook oem unlock, But all it ever tells me is waiting for device. Im guessing im missing drivers, but I have dont the samsung drivers a couple of times, and unzipped and followed the instructions.
Any easier to follow guides or info out there that can help me?
When I plug the phone in to unlock it, i dont get the usual ding from windows, i just get a little thre dings like it doesnt know what it is.
please help. Thanks....
Ps, sorry if I am being stupid or cluttering the forum. cheers..
No help out there at all???
If any one can I will be so grateful, Or if anyone is near to welwyn garden / st albans maybe youd fancy rooting 2 of these nexus' for me and il give you a drink?
Thanks..
Look in the development forum:
http://forum.xda-developers.com/showthread.php?t=1352413
Install the android version of pdanet on your PC... it will uninstall but will leave the drivers you need.
kravevr6 said:
No help out there at all???
If any one can I will be so grateful, Or if anyone is near to welwyn garden / st albans maybe youd fancy rooting 2 of these nexus' for me and il give you a drink?
Thanks..
Click to expand...
Click to collapse
Haven't rooted mine yet, I'll be doing it at the weekend. Had loads of issues with the drivers when I rooted my Nexus S. In the end I installed PDA net on my PC - the drivers installed with that worked fine (you don't actually use PDA net thereafter) Not sure if this works with the GN but you will not do any harm trying it.
Sent from my Galaxy Nexus using XDA App
jaketurbo said:
Look in the development forum:
http://forum.xda-developers.com/showthread.php?t=1352413
Install the android version of pdanet on your PC... it will uninstall but will leave the drivers you need.
Click to expand...
Click to collapse
Beat me to it
Sent from my Galaxy Nexus using XDA App
Cheers guys, Im so new to this, its so frustrating. Its got to be a driver issue. My comp reconises the phone when its on, but when its in bootloader mode, windows is giving me three dull bells when connecting the device....
will have a look at the other thread, Have already read that one I think, and looked so foreign to me!!! lol
I cant pst in the other thread, but have downloaded and installed pda net for android, and when it gets to installing the drivers from the phone, it does it all, ie galaxy nexus , the other driver that i cant remember and the galaxy driver is not installing. Even gone two miles down the road and got a different laptop. no matter what I download or ty and install it just dnt do it.
can some one either make a real simple idiots guide for me the idot, or locally please let me pay you a small fee to root these two phones. Im almost in tears after 5.5 hours of constant crap and pathetiness.
Wishing right now i had not bthered with these phones. At least my s2 and flashing was simple.
It says "waiting for device" because for some crazy reason when you are in fastboot mode Windows (which is what I'm using) uses a different USB driver than when you are in "normal" usb connect mode.
What you need do to sort it out is to go to Device Manager and change the driver to use the Samsung instead of whatever crazy one Windows has decided to use. Then you can carry on with doing the bootloader unlocking.
kravevr6 said:
I cant pst in the other thread, but have downloaded and installed pda net for android, and when it gets to installing the drivers from the phone, it does it all, ie galaxy nexus , the other driver that i cant remember and the galaxy driver is not installing. Even gone two miles down the road and got a different laptop. no matter what I download or ty and install it just dnt do it.
can some one either make a real simple idiots guide for me the idot, or locally please let me pay you a small fee to root these two phones. Im almost in tears after 5.5 hours of constant crap and pathetiness.
Wishing right now i had not bthered with these phones. At least my s2 and flashing was simple.
Click to expand...
Click to collapse
Ok so what have you done so far?
You have the pdanet drivers installed on your pc?
You need to boot into fastboot mode to install the driver you need to root your phone.
*THIS* guide will explain what adb and fastboot are exactly.
*THIS* guide will show you how to set up adb and fastboot.
When unlocking the bootloader you will need the file fastboot.exe which you can put in the root of your c drive for easy access. The atteached file needs to be renamed from .zip to .exe as you cant attach .exe files in xda.
If you have any more questions then just ask .
Mark.
ok..... having gone through similar a few minutes ago.
The drivers kept saying that they had failed to install. kept trying over and over.
then i twigged:
1) made sure debugging mode was on
2) Rebooted the unit into bootloader mode - suddenly the adb driver installed successfully doh !
wonder if this is the same issue you are having ... the adb drivers only install successfully once the nexus is connected via usb and in bootloader mode
of course you may know all that already but it had me stumped for a while
Thank you guys, some good info and detailed posts, which is what I was hoping for! I'm in bed now, but will give this a blast and report back tomorrow!
Really appreciated!
Thanks .......
Sent from my Galaxy Nexus using Tapatalk
Big thanks to everyone. Woke up with a clearer head and proceeded to try again. Done as wilbur said and installed drivers in recovery mode. And perfect.......
after so many problems all was sorted. Then used superboot, and all was ok. 2 galaxy nexus's rooted. think the lesson learnt is to walk away instead of furiously trying things.
Cheers for all the input. What a easy methd ONCE all the drivers are there!!
Cheers people
Glad you got it sorted
Hey
So I tried to root my SGN using Chainfires' thread, my phone got unlocked but I couldn't boot it so I got stuck with a black screen with the Google logo and an unlocked lock-logo. Now I have unrooted it and reset it back to stock using droid-life.coms' "How to", but when I try to boot now I only get the balck screen with Google-logo, and no lock-logo.
Do anyone know how I can fix this? Thanks for the help!
When I try to unroot, re-lock and set to factory state I get an error, probably because my driver isn't working, the 'SAMSUNG Mobile MTP Device'..
I tried the PDANet drivers, Samsungs' drivers and yeah.. I also downloaded the "Naked drivers" wich I found on another thread on XDA.
I really need help
How far into rooting it did you get? A link to the instructions you followed, and a detailed account of what happened and what you saw will help someone else help you.
as far as drivers go, if you installed a bunch drivers from different sources, uninstall them all, reboot, install the drivers from Samsung. Also remember that when you plug your phone in and the drivers start to autoinstall, that process can take awhile and you have to be sure it completed before trying to continue. It should show a status you can open in the system tray
Galaxy Nexus Bugless Beast 4.0.3 cdma
Also, be sure to scour all the sticky posts in these galaxy nexus forums, and also all the replies in the thread you were following. Chances are someone has explained an 'all else has failed blow it away' recovery step by step. Follow it closely!
Galaxy Nexus Bugless Beast 4.0.3 cdma
eovi said:
When I try to unroot, re-lock and set to factory state I get an error, probably because my driver isn't working, the 'SAMSUNG Mobile MTP Device'..
I tried the PDANet drivers, Samsungs' drivers and yeah.. I also downloaded the "Naked drivers" wich I found on another thread on XDA.
I really need help
Click to expand...
Click to collapse
Have you tried downloading the Google USB Driver package from Android SDK? Its under Extras. If my memory serves me right, our phones actually require two drivers (one for adb and fastboot modes, and one for normal operation). Also, when you are restoring your phone are you sure its the right version? Like you're not installing an LTE ROM on a GSM device?
Sent from my Galaxy Nexus using xda premium
@cancerouspete
I got the rooting all done until the phone was going to boot, then I got stuck at the black screen with the Google-logo. Unfortunately I can't post links, but I used Chainfires' ODIN method.
I can try to uninstall the drivers and only try Samsung drivers.
@nbeebe24
Yes, I downloaded the Android SDK drivers before I started the rooting. I am not 100% sure that it is the right version. I got the GSM, do you have a nice guide or 'How To' for restoring GSM?
Thanks for the help so far!
Let's take it form the beginning. First I followed the steps in Chainfires' thread about CF-Root for SGN (Galaxy Nexus). I used the ODIN-way to flash my phone. I followed the instructions to the letter and when I tried to boot the phone I only got a black screen with a white Google-logo in the middle and an unlocked lock-logo. Nothing else happens than this. My phone is GSM-version and is bought in Norway. One of the issues is that I'm not 100% sure of what build-number my phone is.. anyone know how I can find this out?
When I tried to fix this problem myself I tried to unroot, lock and reset the phone, and then unlock/root again with another version, the same happend (with the black screen and google logo + lock-logo). It doesn't work to unroot, lock and reset, if I do this I only get a balck screen with google-logo, but no lock-logo
I really hope someone can help me with this problem! All help and tips is appreciated!
Fixed!
I've finally fixed this problem. Can tell you how I fixed it if someone else need help.
I uninstalled the PDANet drivers, Samsung drivers and uninstalled the SDK-drivers. Then I reinnstalled the SDK driver and followed this to restore the phone to stock:
http://forum.xda-developers.com/showthread.php?t=1366806
So I guess the problem was that I used the wrong version or for another build when I CF-Rooted. I have ITL41D build.
Thanks for the help and I hope this can help other with the same issue!
Love my GNex, it's a beast! Upgraded from a SGS, this was a beast when it first came out but the electronic power are growing fast! Go Samsung and Google! Love ICS
Greetings fellow GNex owners and enthusiasts!
I've been trying to root my Galaxy Nexus unsuccessfully for the past week.
Here's what I've done so far:
1. I Unlocked the bootloader as per Droid-Life's instructions using an old method with the cmd prompt. (The complete How-To guide on their website) I installed the SDK on a windows 7 64-bit machine and went ahead with the process. This worked fine.
(*Note: My Gnex is stuck on 4.0.2 and it won't pull an update. I've tried the method of clearing the data from the framework app and resetting the clock to 1969 multiple times without success. probably 10-15 times.)
2. Since that I've tried uninstalling/reinstalling drivers, rebooting, and then rebooting some more. I've tried every available "noob-proof" method out there and i can't get it to work.
Tried Galaxy Nexus Tooklit v5.6
With and without the included drivers. tons of reboots and re-tries. root always fails.
Wugfresh's Toolkit 1.3
with and without the included drivers. tons of reboots and re-tries. root always fails.
Manually pushing CWM Recovery and SU to the phone with cmd promt via other tutorials floating around the internet, etc. Pushing CWM Recovery fails. Can't even get the temporary flash going to install SU
NOTHING works.
Is it because I unlocked the bootloader manually using an older method first?? I'm pretty sure I've been following the various instructions with each method accurately.
Can someone shed some light on me? I don't necessarily want to mess with kernels and custom ROMs. I just want to be able to wirelessly tether like I could with my OG and D2.
Thanks in advance,
Thanassi
Check my sig and try my method?
Haha.
But I'm guessing driver error.
The simplest method for getting drivers is to download and install pdanet on your PC. Then simply try again.
http://junefabrics.com/android/
I've had to root my phone 3 times and each time took 3 tries before it took. As mentioned before also make sure your drivers are good. And su files.
bow chicka wow wow.
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
shohratshankar said:
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
familyguy59 said:
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
Click to expand...
Click to collapse
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
shohratshankar said:
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
Click to expand...
Click to collapse
Yes. You don't need the SDK, as a matter of fact
The Rundll32 part, is a fact, when installing the drivers...
It has the following effect:
You have installed ADB drivers (no Rundll32). You are flashing away, and all of a sudden. BANG! Everything stoppen. Phone's bricked... Why? Windows thought it is being smart, and installed new drivers, whilst you were working. However, with the RunDll32 command, you can tell Windows, that YOU want to install the drivers manually, and check manually. Of course, you can turn this off, if you want. No prob. but I personally recommend leaving it off
It's saved many phones' lives ^^
so you are having trouble with the adb or fastboot drivers? is so i had this problem too and sometimes even have to reinstall those drivers after flashing a rom.
i had to manually install the drivers using device manager, just select the android device and go to update driver. Choose "Browse my computer for driver software" then pick "Let me pick from a list of device drivers on my computer" then choose Google in that list.
Error
familyguy59 said:
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
Click to expand...
Click to collapse
I get an error message with this application whenever I attempt to do something.
tried that
shohratshankar said:
I'm a noob too.
I followed the following method:
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
thanassi44 said:
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
GSM only??
efrant said:
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
Click to expand...
Click to collapse
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
thanassi44 said:
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
Click to expand...
Click to collapse
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
FINALLY! Have Root.
efrant said:
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for all your responses and suggestions. I finally got something to work. After some more driver swapping and rebooting, now on an XP machine, I got wugfresh's toolkit 1.3 to flash cwm recovery and I was able to install su. The program then ran an automated script to allow permanent flashing of cwm recovery. Got my titanium backup and from manager back, as well as wireless tether. Thank you all for your attention and patience!
Had such a hard time with this phone that I was beginning to have buyers remorse. Now its been set free.
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Sorry, but I've tested this program, over and over. I use it, myself. I never habe any problems...
But, I'm in the making, of a Youtube video. I'll post it, in my thread Then maybe you can see, what you did wrong
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Hang on... Did you install the scnd. file, within the ISO? If not, there's your problem...
I have the "nosearchbar" mod that disables the Google search bar that takes up the top portion of the screen.
I would like the original launcher so I can upgrade to 4.0.4. because I'm having problems.
I have looked for the stock launcher and I cannot find it.
Does someone have a download link?
Viralmind said:
I have the "nosearchbar" mod that disables the Google search bar that takes up the top portion of the screen.
I would like the original launcher so I can upgrade to 4.0.4. because I'm having problems.
I have looked for the stock launcher and I cannot find it.
Does someone have a download link?
Click to expand...
Click to collapse
For which build? mysid? yakju? ??
efrant said:
For which build? mysid? yakju? ??
Click to expand...
Click to collapse
mysid is for LTE, right? I believe it's that one.
stock 4.0.2 galaxy nexus lte.
edit: sorry. i should say stock rom, but obviously rooted + unlocked.
Viralmind said:
mysid is for LTE, right? I believe it's that one.
stock 4.0.2 galaxy nexus lte.
edit: sorry. i should say stock rom, but obviously rooted + unlocked.
Click to expand...
Click to collapse
I thought I had the mysid ICL53F images on my computer, so I was going to pull it for you, but I guess they are at work.
This is what you need to do:
1) Download the mysid ICL53F image from here;
2) Extract the system.img from within;
3) Convert it to an .ext4.img by using this;
4) If you are using Windows, use this to mount the .ext4.img and extract the file, which is /system/app/launcher2.apk[/QUOTE]
Thanks. I didn't know which program to extract the system.img with.
Now I have the Launcher2.apk so I can make a zip and flash it hoping it will make my rom stock again so I can upgrade.
Well it did not work. I replaced the modded launcher from the nosearchbar zip file with the stock launcher from the system.img, and it flashed, but nothing changed.
Guess I'm going to do a hard reset.
Viralmind said:
Well it did not work. I replaced the modded launcher from the nosearchbar zip file with the stock launcher from the system.img, and it flashed, but nothing changed.
Guess I'm going to do a hard reset.
Click to expand...
Click to collapse
A hard reset will not do anything. It just wipes your data, it doesn't touch /system.
If that was the file you modified, replacing it (and rebooting of course) with the stock file should fix it.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
A hard reset will not do anything. It just wipes your data, it doesn't touch /system.
If that was the file you modified, replacing it (and rebooting of course) with the stock file should fix it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I tried that. Nothing happened.
Viralmind said:
I tried that. Nothing happened.
Click to expand...
Click to collapse
Back up all your data off your device and do this.
efrant said:
Back up all your data off your device and do this.
Click to expand...
Click to collapse
yeah, i saw that link on your profile and was looking at it a couple days ago.
i was hoping i didnt have to go that far, but, oh well.
Okay, so I finally got around to working on this.
I got to "A. Install the drivers" and the drivers will not install.
I have uninstalled the drivers/device from device manager.
I set it so that drivers will not automatically install and rebooted.
Then I told the computer where to look for the drivers and they wont install.
I have tried all sub folders and nothing will work.
It just says "Windows cannot find driver software for your device."
Windows 7 64 bit.
Viralmind said:
Okay, so I finally got around to working on this.
I got to "A. Install the drivers" and the drivers will not install.
I have uninstalled the drivers/device from device manager.
I set it so that drivers will not automatically install and rebooted.
Then I told the computer where to look for the drivers and they wont install.
I have tried all sub folders and nothing will work.
It just says "Windows cannot find driver software for your device."
Windows 7 64 bit.
Click to expand...
Click to collapse
What happens when you have your phone booted into fastboot mode and plug it into your computer? What do you see in device manager? If you see something (related to Android or Samsung) with a yellow exclamation mark beside it, right click on it and select "update driver". Then chose manual, and browse to the folder where you downloaded (AND extracted) 1wayjonny's drivers.
efrant said:
What happens when you have your phone booted into fastboot mode and plug it into your computer? What do you see in device manager? If you see something (related to Android or Samsung) with a yellow exclamation mark beside it, right click on it and select "update driver". Then chose manual, and browse to the folder where you downloaded (AND extracted) 1wayjonny's drivers.
Click to expand...
Click to collapse
okay in fastboot mode - device manager has "android 1.0"
when i right-click install, it says "the installation is forbidden by system policy."
im guessing its referring to me changing rights so windows cant automatically install drivers, but if i change that, as soon as i plug in the usb to phone the drivers are installed instantly.
EDIT: ok, i got the drivers installed and now device manager says "samsung galaxy nexus bootloader interface"
Viralmind said:
okay in fastboot mode - device manager has "android 1.0"
when i right-click install, it says "the installation is forbidden by system policy."
im guessing its referring to me changing rights so windows cant automatically install drivers, but if i change that, as soon as i plug in the usb to phone the drivers are installed instantly.
EDIT: ok, i got the drivers installed and now device manager says "samsung galaxy nexus bootloader interface"
Click to expand...
Click to collapse
Undo the chgs you made, and try it like that. You may not see the ! but it may still install.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Undo the chgs you made, and try it like that. You may not see the ! but it may still install.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I did undo the changes.
thats why i have galaxy nexus bootloader showing in device manager instead of android 1.0
do i have to install the drivers again with phone in normal mode?
EDIT: i got it back to stock. its all done.
thanks for your help.
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT