GNex Drivers Not Staying Installed in Bootloader/Fastboot Mode - This Device Cannot Start (Code 10)

[androidluvr2]

So I lost root when I installed the 4.2.2 OTA. I have always had driver issues with all 3 of my Windows machines when connecting my Galaxy Nexus to machines running XP, Vista and 7, have installed and reinstalled every driver known to man and have tried different USB ports and different cables to no avail.

I have USB debugging enabled on my GNex and have allowed USB debugging for my Windows 7 computer based on its RSA fingerprint. When I plug my GNex into my Win7 computer and go to Device Manager, these are the drivers that are installed:

The drivers are current - the Samsung Android ADB Interface and Samsung Mobile USB Composite Device driver are dated 1/23/2013 and the Samsung Galaxy Nexus driver is dated 5/11/2012. I also am using the most recent versions of adb and fastboot from the SDK.

When I type "adb reboot bootloader" from a command prompt, it puts my phone in fastboot mode but when it does, the Galaxy Nexus driver uninstalls as does the Samsung Mobile USB Composite Device driver. The Samsung Android ADB Interface remains installed:

Same thing is true when I plug my GNex into my computer while the GNex is in fastboot mode.

When I type "adb devices" from a command prompt while my GNex is in fastboot mode, it does not find my GNex. When I type "fastboot boot boot.superboot.img" from a command prompt while my phone is in fastboot mode, my phone goes to the Google screen with an unlock symbol at the bottom, the CMD screen reads as in the image below and my computer recognizes a device on the GNexs' USB port but installs a driver named Samsung Mobile MTP Device that has the same date (5/11/2012) as the Galaxy Nexus driver but has a yellow exclamation point on it and when I right click it and go to Properties, the device status says "This device cannot start. (Code 10)."

My phone then will stay hung on the Google screen until I disconnect it from my computer and do a battery pull to restart it. Once restarted, root checker says I don't have root.

Does anyone have any insight into what is going on with the drivers or why I can't reroot my device? I have literally installed and reinstalled every version of the Samsung ADB and Galaxy Nexus drivers I can find as well as every other USB related driver on my computer. I don't think this is a driver problem so much as it is a Windows problem.

 

[Paul627g]

I would highly recommend using Wugs Toolkit if your having driver issues. It does a great job of overcoming this problem for you. Yes this is one area where those " 1 clicks " come in handy...

[h=3][Automated] Wug's Nexus Root Toolkit v1.6.2 (Updated 12/29/12)[/h]

 

[androidluvr2]

I would highly recommend using Wugs Toolkit if your having driver issues. It does a great job of overcoming this problem for you. Yes this is one area where those " 1 clicks " come yn handy...

Thanks. How is Wug able to overcome the driver issue, though? If the toolkit can do it, I should be able to do it. It's just a matter of figuring out why it is happening, no?

 

[Paul627g]

The drivers for some reason are a huge peta with the GNex.... I could do it blindly any day of the week with my NS4G and any version of Windows but for some reason the GNex and the Windows drivers just don't gel right...

Use the toolkit, it will save you a huge mess of headaches... Thats basically all I use it for myself, the rest I do all manually via fastboot or adb.

 

[androidluvr2]

The drivers for some reason are a huge peta with the GNex.... I could do it blindly any day of the week with my NS4G and any version of Windows but for some reason the GNex and the Windows drivers just don't gel right...

So do you think that Samsung wrote bad drivers?

 

[Paul627g]

I honestly don't know what the issue is.. But I've gone down the same path as you my friend with the device manager, doing everything humanly possible to get things to work and somehow, somewhere, something is always not 100% with the drivers doing manual install or letting Windows seek out and installing them..

I finally gave in and let the toolkit do the drivers for me and within a minute or two its done and I never have a problem since then.... FWIW.... Done it on Windows XP, Vista 64 and Win 7 - 64 bit and it works like a charm.

 

[androidluvr2]

I finally gave in and let the toolkit do the drivers for me and within a minute or two its done and I never have a problem since then.... FWIW.... Done it on Windows XP, Vista 64 and Win 7 - 64 bit and it works like a charm.

OK, so are you saying use the toolkit to install the drivers and then doing everything else manually? Or use the toolkit to reroot?

 

[Paul627g]

If your going to use the Tool Kit to do the drivers you might as well click the button and let it do the root for you too... Again I'm not a 1 click person but if your already there might as well let it perform the task for you.. Then from there on out do things manually as you please. I fully understand the gratification you get from performing things manually over anything automated but man those damn drivers will drive anyone insane...

 

[androidluvr2]

but man those damn drivers will drive anyone insane...

I am going to use it because like you, fiddling with these drivers has sucked the life out of me, lol! and so I am giving up. But I noticed that on the first page, they mention universal drivers written by 1wayjonny. So that must be how the toolkit overcomes the driver issue - by not using the flawed Samsung drivers and instead using the universal drivers, yes?

 

[Paul627g]

Could very well be... Honestly I didn't even read the fine print about the drivers in the tool kit.. I just knew it was the golden ticket to my headaches so I downloaded it, installed it and let it setup the drivers for me...

Now I just keep it installed on standby just in case there is ever a connection issue.

 

[androidluvr2]

Update - got root back by using the toolkit. The toolkit was fine with the Samsung drivers while booted but the instructions had me manually install a driver in bootloader mode - Google Galaxy Nexus Bootloader Interface (dated 12/6/2010) - that I have not seen before. So I guess I had not installed/uninstalled/reinstalled every GNex driver known to man! Not sure why the GNex bootloader interface doesn't get more press since it seems to be a key for the GNex.