When i "update driver software" through manager and point to ../usbd_driver
it's "unable to install your Android 1.0 device"
I'm using win7 64bit.
I looked through the inf file and did not see Galaxy Nexus.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[International / GSM] [HOW TO] Root the GSM/HSPA+ Samsung Galaxy Nexus
- Thread starter scary alien
- Start date
-
- Tags
- galaxy nexus
When i "update driver software" through manager and point to ../usbd_driver
it's "unable to install your Android 1.0 device"
I'm using win7 64bit.
I looked through the inf file and did not see Galaxy Nexus.
residualimages
Newbie
certainly odd. I'm using Win7 x64 as well...
this is the version part of my android_winusb.inf file:
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
efApple
Member
got mine installed using the driver that comes with PDANet for Android for Win7/Vista. Was able to fastboot with success
greatchief1
Newbie
Confused....
Mine is still on 4.0.1, I have NOT done anything to it yet. Does the OP still hold true, or will I loose root once it updates to 4.0.2? What steps do you recommend I take?
Thanks in Advance!!!
Mine is still on 4.0.1, I have NOT done anything to it yet. Does the OP still hold true, or will I loose root once it updates to 4.0.2? What steps do you recommend I take?
Thanks in Advance!!!
residualimages
Newbie
i updated to 4.0.2 before I rooted, or realized the update would apparently make you lose root.
so my money is on, just update to 4.0.2, then do the unlock and root.
and if you want my story: http://androidforums.com/galaxy-nex...-root-samsung-galaxy-nexus-4.html#post3655937
civicsisedan
Android Expert
Flashed CWM through rom manager, rebooted into recovery and I did make a nandroid back up.
Booted phone. Plugged in to put Google Wallet zip on phone..
Rebooted into recovery and no recovery image.. Exclamation point now...
i dont think recovery sticks, I had to reflash CWM in Rom Manager to get it to work, didnt get to flash zip I accidently hit power button forcing it to reboot thinking it was the volume buttons.. Had to go back into Rom Manager and reflash CWM AGAIN....
Can someone that has CWM flashed and working try and turn off phone and reboot into it?
Booted phone. Plugged in to put Google Wallet zip on phone..
Rebooted into recovery and no recovery image.. Exclamation point now...
i dont think recovery sticks, I had to reflash CWM in Rom Manager to get it to work, didnt get to flash zip I accidently hit power button forcing it to reboot thinking it was the volume buttons.. Had to go back into Rom Manager and reflash CWM AGAIN....
Can someone that has CWM flashed and working try and turn off phone and reboot into it?
residualimages
Newbie
hey, I just had the same experience. Reboot into recovery, red exclamation point. going to reboot and reflash and see what happens.
sgrinavi
Android Enthusiast
Hmmm.. similar problems here - (Rooting NOOB here)
In the device manager, with the phone on (and plugged-in, of course) I see
SAMSUNG Android Phone
+ SAMSUNG Android ADB Interface
When I go to the boot loader that device goes away and it looks like
Other Devices
+Android 1.0
When the phone is on (again, not in boot loader) and I run ADB Devices - it returns a long string of letters and numbers - when it is in the bootloader ADB sits there <waiting for device>
HALP
In the device manager, with the phone on (and plugged-in, of course) I see
SAMSUNG Android Phone
+ SAMSUNG Android ADB Interface
When I go to the boot loader that device goes away and it looks like
Other Devices
+Android 1.0
When the phone is on (again, not in boot loader) and I run ADB Devices - it returns a long string of letters and numbers - when it is in the bootloader ADB sits there <waiting for device>
HALP
Travillion
Well-Known Member
This happened to everyone I know of. Reboot and do it again. For me, it then said already running as root. No more problems.
civicsisedan
Android Expert
Yes I dont think CWM sticks for some reason. I keep having to reopen Rom Manager and reflashing it to be able to get into recovery.
Google Wallet broke all my apps, I had to uninstall and re install Rom Manager to get back into recovery and Nandroid Back up, I think I know how to get it working so I will try again...
Google Wallet broke all my apps, I had to uninstall and re install Rom Manager to get back into recovery and Nandroid Back up, I think I know how to get it working so I will try again...
residualimages
Newbie
when you're in the Boot Loader and you see the Android 1.0, manually update drivers to use the android_winusb.inf (usually located in C:\Program Files\Android\android-sdk\extras\google\usb_driver\) and select "android bootloader interface"
Travillion
Well-Known Member
You need to download a samsung driver (I think the OP link for Naked Samsung is the one that I used). When you are in the bootloader, open device manager and update your driver for Android 1.0 to the samsung driver. Then your computer will be able to speak to your phone when it is in the bootloader. Took me hours this morning to figure that out.
residualimages
Newbie
i believe there was a comment to 'fix permissions' after Google Wallet, so I'm going to attempt that next.
civicsisedan
Android Expert
Ok so for Google Wallet.
I flashed zip and fixed permission and booted. Apps were broken. Went back into Recovery and fixed permissions again, this took longer.. Booted back up..
Seems like everything is good. Opened google wallet, added the google prepaid card and got $10...
I flashed zip and fixed permission and booted. Apps were broken. Went back into Recovery and fixed permissions again, this took longer.. Booted back up..
Seems like everything is good. Opened google wallet, added the google prepaid card and got $10...
residualimages
Newbie
and "optimizing applications" ?? what's with that.
civicsisedan
Android Expert
Ok so today was succesful. I picked up the Galaxy Nexus and
Unlocked Bootloader
Acheived Root
Flashed CWM
Made Nandroid Backup
Flashed Google Wallet
And am about to go spend my free $10!
Im off of here for the day...
Unlocked Bootloader
Acheived Root
Flashed CWM
Made Nandroid Backup
Flashed Google Wallet
And am about to go spend my free $10!
Im off of here for the day...
sgrinavi
Android Enthusiast
Yeah me. It worked.. well, I unlocked the boot loader and ran the Paul O'Brien deal. It rebooted a couple times and now I am starting from scratch - so I guess I got the wipe part right LOL..
Now ... off to figure out the google wallet deal
Thanks for your help
Now ... off to figure out the google wallet deal
Thanks for your help
billtvshow
Newbie
Well I just had an interesting experience.
So I was one of the people who had the 4.0.2 problem where we were held up at the production build message.
I went ahead and rebooted and used my phone normally for a few hours.
So I just got to where I could work on rooting my phone again and saw the superboot method was working, so I downloaded it and ran the superboot img via fastboot and got stuck on the Google Logo for a good 15 minutes.
So then I decided to try the adb commands for the hell of it while still on the Google screen and when I put in the adb root command, it said it was already rooted. So then I tried the rest of them. None of the rest had been processed. Remount worked. Then to push su and Superuser.apk I had to copy them over from the original folder I had made for my attempt via boot.img and put them in my superboot folder. The adb commands pushed them on there and then I did the last two adb chmod commands, then waited a sec and pulled the battery and turned it back on. Permanent, working root. Awesome.
Side note, you will need to take the -win (or whatever system you have) off of the file names to use the default instructions, though you could just type out the commands with the -win on them just as well.
So I was one of the people who had the 4.0.2 problem where we were held up at the production build message.
I went ahead and rebooted and used my phone normally for a few hours.
So I just got to where I could work on rooting my phone again and saw the superboot method was working, so I downloaded it and ran the superboot img via fastboot and got stuck on the Google Logo for a good 15 minutes.
So then I decided to try the adb commands for the hell of it while still on the Google screen and when I put in the adb root command, it said it was already rooted. So then I tried the rest of them. None of the rest had been processed. Remount worked. Then to push su and Superuser.apk I had to copy them over from the original folder I had made for my attempt via boot.img and put them in my superboot folder. The adb commands pushed them on there and then I did the last two adb chmod commands, then waited a sec and pulled the battery and turned it back on. Permanent, working root. Awesome.
Side note, you will need to take the -win (or whatever system you have) off of the file names to use the default instructions, though you could just type out the commands with the -win on them just as well.
Le0_Br4zUc4
Android Enthusiast
I got bootloader unlocked and CMW flashed. Can I install superuser on my LTE nexus now?
I was having the same issue, just tried with the R3 superboot which has been linked to several times, again got stuck on the google screen but after about 5 minutes, I pulled the battery. after rebooting, su is there and I do appear to have root
Le0_Br4zUc4
Android Enthusiast
where is this R3 superboot?