Develop Bugs

Please help me root!

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

[Q] Can't get phone to re-root, please help

Previously I had installed on my phone (I believe, but could be mistaken) a Twilight Kernel and Hurricane v1.6 Rom. Well, I had nothing but problems with the rom, and put up with them for some time, just because I didn't have time to go through and find a rom I liked and flash it. I decided to do just that yesterday.
Apparently my mind broke and I did something wrong (probably numerous things). I had first attempted to put the shiney new CWM9 with Shadow Kernel on, rather, I made the mistake of trying to just put the Shadow Kernel on after having done a full (triple) wipe on my phone. I got the boot loop for the kernel since there was no rom (duh) loaded. Okay, no problem, I'll toss a rom on the SD and boot into CW3 and flash it? Yeah, not so much. I got a short "Samsung" logo boot loop and could not get into CW3 after that.
So, I Odin'd it back to EL30, thinking I'll just start from fresh, right?
Wrong.
Next in the series of mistakes I made, I forgot that I had already downloaded and installed the Samsung drivers (don't ask, my brain was apparently on leave yesterday) and attempted to re-install them. They did not like this and would not progress and I had to End Process the install from Task Manager. I then uninstalled the drivers completely fearing that I may have corrupted them by trying to re-install and then EP'ing them.
I then re-installed them, or so I thought. Plug phone in and start again with One Click Root. Fail. The script couldn't find my device.
Hours of searching and trying different things later, script still couldn't find my device, though I now have both the phone recognizing there is a USB connection, and the computer has stopped yelling at me that there are no drivers (I believe it finally gave up and installed the Windows drivers for it). But still can't get it rooted or do anything but stock stuff.
So..
1:Samsung drivers won't install, running Windows 7-64 Ultimate; error at end of install just states: "The MMS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones v1.3.450.0."
2hone previously recognized USB Debug mode, but no longer. Will only Recognize standard USB connection, and with the connection made to PC, the script will not recognize the device.
3:adb for all intensive purposes does not appear to be loading..per the message from the script "Root was not obtained after 60 seconds. Make sure the phone is connected and that adb is working. If adb shell isn't root, reboot the phone and try the script again." I've rebooted numerous times, but I'm pretty certain that since it's not going into Debug, it's just not being recognized.
I have even tried Gingerbreak with no luck, just continuously sits on the rooting screen, but never proceeds (upwards 45 minutes I let it go).
Please please please please help me fix all the mistakes I did and get this thing working again and get the damned drivers installed proper.
(Baseband-S: D700.0.55.EL30, Kernel version 2.6.35.7, Build number: Gingerbread.EL30)
Note* I am happy with any root/kernel/rom at this point, I don't care, I just want the damned thing rooted again.

And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?

Qbking77 youtube him...
Or I could do it for you remotely via teamviewer... either way
Sent from my SPH-D700 using xda premium

AtrophiedAnnie said:
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Click to expand...
Click to collapse
If you are up and running EL30 just Google How to Root Samsung Epic on EL30 and a qbking77 youtube video will pop up and all the links are there as well for the files you need. If you are not up and running then you need to go into the Roll Up sticky thread in Development and click on How to Restore a semi-bricked Samsung Epic....all links are there for that including 64bit drivers.
Sent from my SPH-D700 using xda premium

Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )

AtrophiedAnnie said:
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
Click to expand...
Click to collapse
Sounds more like serious root rust to me. Gotta keep up...lol. Samsung tries to make it harder to root...that works for 5 minutes around here...LOL.
Sent from my SPH-D700 using xda premium

IT'S DONE!!! Again thank you both so much1

[Q] Galaxy Nexus ToolKit, firmware build selection question

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

Trying to Root - Driver install issue

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

[Q] Apparent Soft Brick... Issues with a fix

Hello, I am aware that I am a noob, but the issue I have is important to me.
When the android L developer preview came out I was thrilled, and thus proceeded to install it. I will spare you the details, but I ended up having everything on my Nexus 7 wiped except for TWRP. Now, me and my brother have attempted an adb push to get a rom on the tablet, but adb can't find the Nexus 7. Also, the Windows USB drivers refuse to be installed for the device (the process I used to do so was fully correct.) To actually post on XDA was my last resort after hours of research and attempting to revive my Nexus. Any willing advice would be great. Thanks!

doublewhamy said:
Hello, I am aware that I am a noob, but the issue I have is important to me.
When the android L developer preview came out I was thrilled, and thus proceeded to install it. I will spare you the details, but I ended up having everything on my Nexus 7 wiped except for TWRP. Now, me and my brother have attempted an adb push to get a rom on the tablet, but adb can't find the Nexus 7. Also, the Windows USB drivers refuse to be installed for the device (the process I used to do so was fully correct.) To actually post on XDA was my last resort after hours of research and attempting to revive my Nexus. Any willing advice would be great. Thanks!
Click to expand...
Click to collapse
Reboot to bootloader.
fastboot devices
If device shows up, flash stock firmware. Link in siggy.

Aerowinder said:
Reboot to bootloader.
fastboot devices
If device shows up, flash stock firmware. Link in siggy.
Click to expand...
Click to collapse
I appreciate the assistance!