Help Nexus 5 yellow exclamation point in control panel.

[Codec]

How do I fix this?

 

[Brian706]

Download the Google driver: http://developer.android.com/sdk/win-usb.html

Extract to desktop (or anywhere handy) right click the yellow exclamation point in device manager, choose update driver.

Browse to the location of the extracted folder. Should install the driver then.

 

[mk_ultra19]

How do I fix this?

I had the same problem on a windows 7 64 bit machine. I had correct drivers installed, but NOTHING would allow my Nexus 5 to be " seen " by my laptop.

My Galaxy S3, Nexus 7 were fine. After much trial and error... I made a back up of everything important on my laptop to a portable hard drive, then I reformatted my laptop back to default settings, re-installed everything back from my portable hard drive and voila... my nexus 5 shows up in my device manager " without the yellow triangle " and now I can transfer files to and fro.

I am in NO way saying this is the correct solution, but it worked for me...after everything else I tried, did not.

 

[Codec]

Ok I am having the same problem again, but the google driver I downloaded is not working. Windows is saying it was unable to install the nexus 5. Is it because I am on android 4.4.3 now?

 

[akmsr]

Try the universal naked driver from XDA forum. Also make sure to connect to a USB 2 port of the computer

 

[Rxpert83]

If google driver didnt work...Try this driver here:

http://www.koushikdutta.com/post/universal-adb-driver

 

[Codec]

If google driver didnt work...Try this driver here:

Koush

tried that, didn't work

 

[Codec]

also tried the universal naked driver and no dice

 

[jhawkkw]

Sounds like it may be the MTP driver that's not loading correctly. Is the device booted and is adb enabled?

 

[Codec]

Sounds like it may be the MTP driver that's not loading correctly. Is the device booted and is adb enabled?

abd enabled? Can you explain what you mean? And yes the MTP driver is not loading.

 

[Brian706]

I had the same issue after rooting. Drivers worked fine to root, then after rooting, the fastboot drivers worked but not mtp.

Once I flashed a rom, everything was fine again.

So I would suggest doing a full wipe (minus internal storage) and then flashing a custom rom. Dirty Unicorns is a good one.

Either that or try using the factory images to return to stock.

The problem happens when you immediately flash the custom recovery after unlocking the bootloader. This should normally be fine but you can avoid this issue by booting back into the system after unlocking the bootloader and then flashing a custom recovery.

Like I said, once I flashed a rom, everything was all good again.

 

[Codec]

I had the same issue after rooting. Drivers worked fine to root, then after rooting, the fastboot drivers worked but not mtp.

Once I flashed a rom, everything was fine again.

So I would suggest doing a full wipe (minus internal storage) and then flashing a custom rom. Dirty Unicorns is a good one.

Either that or try using the factory images to return to stock.

The problem happens when you immediately flash the custom recovery after unlocking the bootloader. This should normally be fine but you can avoid this issue by booting back into the system after unlocking the bootloader and then flashing a custom recovery.

Like I said, once I flashed a rom, everything was all good again.

I used the WugFresh toolkit to root and did a wipe before and I used a google factory image.

 

[OldRick]

Buy a Mac.

 

[Brian706]

I used the WugFresh toolkit to root and did a wipe before and I used a google factory image.

Have you tried a Ubuntu Live DVD? It may eliminate any driver issues.

 

[Codec]

Have you tried a Ubuntu Live DVD? It may eliminate any driver issues.

don't know what that is

 

[Codec]

Buy a Mac.

you're not helping

 

[Brian706]

I'm not sure why I suggested that... It would make sense for a rooting issue, but you're already rooted.

Anyway, here's more information about it: https://help.ubuntu.com/community/LiveCD

It's weird that nothing will fix the issue. Have you tried doing things manually? As opposed to using a toolkit...

Factory images to return to stock then run the fastboot commands yourself... I really have no idea what the issue is but the only thing I can think of is the off chance that something with the root toolkit is causing you issues...??

 

[Codec]

i just used the manual driver instalation instruction guide in WugFresh toolkit and fixed the problem