When I plug my wife's phone into my computer it doesn't recognize it as a media device. It does recognize it as an adb device though so I was able to unlock the bootloader and root it. She wants me transfer music and can't, any ideas? Also when I plug in my nexus 4 it appears as a media device.
Sent from my Nexus 4 using xda app-developers app
Bump. Can anyone help me?
Sent from my Nexus 4 using xda app-developers app
Anyone?
Sent from my Nexus 4 using xda app-developers app
mark8503 said:
Anyone?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
when you first put it in, did it download any drivers? if it didnt then go to lgs website and download them.
I got the same effing problem and haven't been able to figure out how to fix it. Every time I uninstall the phones drivers stupid windows will install it right back as adb device...
Sent from my Nexus 4 using xda premium
I have a similar problem with my wife's N4. Hers does not recognize as a MTP device nor as an ADB device. In device manager it shows it, but adb devices never lists it and it never shows up in Computer when I disable USB debugging. My N4 has no problems with either. I've uninstalled and reinstalled the drivers and can't figure it out!
Weird thing though, it detects it in fastboot mode.
I just got off the phone with Google Play Devices support and explained the issue. They are assisting in getting an exchange.
tutech said:
I have a similar problem with my wife's N4. Hers does not recognize as a MTP device nor as an ADB device. In device manager it shows it, but adb devices never lists it and it never shows up in Computer when I disable USB debugging. My N4 has no problems with either. I've uninstalled and reinstalled the drivers and can't figure it out!
Weird thing though, it detects it in fastboot mode.
Click to expand...
Click to collapse
I had this same problem, and it was the lack of drivers. Uninstall in device manager what you have, restart, then install the 4.2 Google SDK drivers. This works in Windows 8 without any extra procedures. I have the SDK installed, and directed the 'have disk' driver search to the SDK directory/extras/google. There were three adb drivers, and I installed them all. I really don't know what I'm doing, but that solved the problem.
Nexus4, Tapatalk
tutech said:
I just got off the phone with Google Play Devices support and explained the issue. They are assisting in getting an exchange.
Click to expand...
Click to collapse
Dude it's not the phone lol. It's the computer. When I plug my phone into my dad's computer it detects it fine. It happened on mine because I installed those adb drivers
Sent from my Nexus 4 using xda premium
What worked for me was uninstalling my old Motorola drivers and then using http://forum.xda-developers.com/showthread.php?t=1995688 to uninstall the SDK drivers for the Nexus 4 that I had originally installed when I got the phone. Then I installed the drivers provided with the Nexus 4 Toolkit and everything works great. MTP, ADB, Fastboot, and the phone is recognized within CWM/TWRP.
tyea said:
I had this same problem, and it was the lack of drivers. Uninstall in device manager what you have, restart, then install the 4.2 Google SDK drivers. This works in Windows 8 without any extra procedures. I have the SDK installed, and directed the 'have disk' driver search to the SDK directory/extras/google. There were three adb drivers, and I installed them all. I really don't know what I'm doing, but that solved the problem.
Nexus4, Tapatalk
Click to expand...
Click to collapse
I can uninstall the drivers just fine but when I plug in the nexus it automatically installs the adb drivers again..
Sent from my Nexus 4 using xda premium
have kind of a similar problem, but a bit different
my computer was able to detect the phone in mtp, adb and fastboot mode, installed the drivers, unlocked bootloader, and everything was fine
this morning the computer no longer able to detect the phone, but it still charges when i plug in the usb cable to the computer; cant transfer files, adb and fastboot list no devices, even device manager doesnt show the phone being plugged in
UPDATE: just tried on another computer, nothing... not even asking for drivers, and the phone doesnt even show it is connected in MTP mode like before... im screwed
I have a similar problem too..
My Nexus 4 works fine when I plug it into the computer, it shows the device just fine. But, when I plug my brother's Nexus 4 into my computer, it does not recognize it, it installed the drivers but I can't see the device in My Computer. In device manager, it shows up. With my brother's phone, I can mount it as Camera (PTP) and I can go into it, but it cannot detect it as a Media device (MTP)
Girn said:
I can uninstall the drivers just fine but when I plug in the nexus it automatically installs the adb drivers again..
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Perhaps, in device manager, select the adb driver, right click to update, direct the update to have disk....SDK Google extras location?
Nexus4, Tapatalk
Think I tried that before and windows said the drivers are already up to date
Sent from my Nexus 4 using xda premium
Girn said:
Dude it's not the phone lol. It's the computer. When I plug my phone into my dad's computer it detects it fine. It happened on mine because I installed those adb drivers
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
In my case anyway, its definitely not the computer. I have two identical, brand new Nexus 4 16GB phones. One is recognized with the appropriate drivers on my computer and the other is as well, however the second one does not show in My Computer nor get listed with ADB devices - unlike the first. The only difference between the two scenarios is the physical phone that is plugged into the computer.
Same with me, my phone works fine but when I plug my wife's in.. Nothing.
Sent from my Nexus 4 using xda app-developers app
I haven't been able to fix it by the suggested methods.. When it's on the other mode for camera pics it works fine and in device manager I get under " portable device" nexus 4 showing up.. But when I switch it to MTP all I get is android adb interface in device manager and no nexus 4
Sent from my Nexus 4 using xda premium
Bump
Sent from my Nexus 4 using xda premium
Girn said:
I haven't been able to fix it by the suggested methods.. When it's on the other mode for camera pics it works fine and in device manager I get under " portable device" nexus 4 showing up.. But when I switch it to MTP all I get is android adb interface in device manager and no nexus 4
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Same for me. I did get it to read my wife's phone though by using the nexus 4 toolkit to uninstall then reinstall the drivers. Funny thing, now it reads her phone and not mine. D'oh!
Sent from my Nexus 4 using xda app-developers app
Related
So I got my n4 last week and I've been trying to unlock and root it to no avail. I've tried using the toolkit as well as using the method indicated in another thread on xda. I keep getting errors when trying to install the drivers.
I've been able to get the adb driver installed on win 7, but not the fastboot driver (using the toolkit).
I've even tried installing the drivers using the toolkit on a VM running xp without any luck.
Could someone please help me out with this? I remember having similar issues when rouoting my captivate, but I was able to use my work laptop to install the drivers (I don't have admin rights anymore).
Sent from my Nexus 4 using xda app-developers app
A) Proofread.
B) Reboot into recovery and plug the phone into the computer. Go to device manager on your computer, look for the USB device with the yellow exclamation point, update the driver. Reboot your computer.
estallings15 said:
A) Proofread.
B) Reboot into recovery and plug the phone into the computer. Go to device manager on your computer, look for the USB device with the yellow exclamation point, update the driver. Reboot your computer.
Click to expand...
Click to collapse
A) Wow that was bad, corrected
B) No devices were displayed in device manager when I booted to recovery. By the way, when I tried to update the drivers in fastboot mode, I kept getting errors.
Perhaps an earlier driver needs uninstalled? Check this thread: http://forum.xda-developers.com/showthread.php?t=1992345
I tried that driver, that is the driver I referenced in the OP, sorry for boy linking.
Sent from my Nexus 4 using xda app-developers app
Austin Ag06 said:
I tried that driver, that is the driver I referenced in the OP, sorry for boy linking.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I was actually referring to the comments in the thread. A ton of people had issues installing. I thought you might try some of their methods.
I was trying to transfer some music file to my phone, but my Kies (Win 7 64bit and Win 7 32bit) could not detect my phone I tried to re install the drivers several time without any luck, phone still charging by PC and when ever I uninstall driver from PC and connect my phone PC start installing all the driver and install driver without any error but still my phone doesn't show up in kies or in windows and connected devise.
It would be appreciated if some one guide me to resolve this issue.
Thanks,
clean the registry when you uninstall drivers using ccleaner
polish_pat said:
clean the registry when you uninstall drivers using ccleaner
Click to expand...
Click to collapse
Still no luck, Kies still not showing my phone
I restore stock firmware by ODIN and still my phone does not show up in my PC
Any suggestions?
Bump
Sent from my SGH-I337M using xda app-developers app
nomi640 said:
Bump
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
Do you have android debugging checked?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I tried both with usb debugging and without but no results
Sent from my SGH-I337M using xda app-developers app
Bump
Sent from my SGH-I337M using xda app-developers app
Any help
Sent from my SGH-I337M using xda app-developers app
nomi640 said:
Any help
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
I've never installed Kies in my life, so I can't comment on it's functionality. nor am I stock...but before I rooted and started flashing, my Rogers S4 was stock.
I used the AT&T drivers to get it to connect in debug or MTP mode. Maybe they will help. You can find them HERE. click downloads or see all downloads and then EXE on the right for the USB Drivers...
still no luck
nomi640 said:
still no luck
Click to expand...
Click to collapse
well I know those drivers work for fact. My Rogers S4 was running VLUAMDJ software...my computer installed some drivers but it didn't work...it never showed up. just like your symptoms. I uninstalled my existing Samsung drivers (which I downloaded when I got my Note 2)...reboot...install those drivers I linked you to, connected phone...detected right away and MTP started working as expected.
so you either have issues with your system (software wise), or it's a faulty cable. I'm going to lean towards the latter first. It's not the first time I've seen that. feel free to try another cable...also if you want...plug your phone in and take a shot of dev mgr and paste it so I can review...or PM me the pic if you prefer....
I thought kies had a troubleshooting mode. Have you tried that? It is referenced I the noob rooting video.
Here is pic for my dev mngr, I tried 3 usb cable, kies troubleshooting but still not showing up, when I plug my phone kies start-up but does phone does not show up in computer or kies.
Thanks for all reply, I can't send phone to Samsung for repair either because I bought from kijiji and Samsung warranty is not transferable
xtechx said:
well I know those drivers work for fact. My Rogers S4 was running VLUAMDJ software...my computer installed some drivers but it didn't work...it never showed up. just like your symptoms. I uninstalled my existing Samsung drivers (which I downloaded when I got my Note 2)...reboot...install those drivers I linked you to, connected phone...detected right away and MTP started working as expected.
so you either have issues with your system (software wise), or it's a faulty cable. I'm going to lean towards the latter first. It's not the first time I've seen that. feel free to try another cable...also if you want...plug your phone in and take a shot of dev mgr and paste it so I can review...or PM me the pic if you prefer....
Click to expand...
Click to collapse
Any idea?
nomi640 said:
Any idea?
Click to expand...
Click to collapse
sorry forgot about the thread, my apologies. I haven't been using tapatalk as much recently, and that's where I used to check my participated threads.
I don't have those devices under ports if I have usb debugging on or off...weird. I'm on win8 x64...the only thing I didn't expand was Portable devices...I only have the two references in my dev mgr....
can you try uninstalling all the detected devices in dev mgr, and delete the driver from the system when doing so? then disconnect the phone, reboot, install those at&t drivers, then plug the phone in and test?
I want to recommend removing Kies before all of that, but not sure if you used it in the past, where it store the backed up data, etc..if you've never used it then please do uninstall Kies before what I mention above...
let me know.
Tried everything but no luck
Sent from my SGH-I337M using xda app-developers app
nomi640 said:
Tried everything but no luck
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
I've installed those drivers on 3 different windows 7 systems this week and not one has failed to recognize MTP on the device first try...I even soft bricked my device a couple days ago, odin'ed back to VLUAMDJ stock, installed drivers on a win8 system that had never had an Android device plugged into it and wasn't connected to the internet (just installed those at&t drivers from a usb drive)...guess what...worked again..
It shouldn't work so easily for soo many people then not at all for you. I'm baffled at how easily it works for me even, and I've been trying to make it not work. I"m a technician I enjoy trying to break things to see if I can duplicate an issue, and fix it....and I can't duplicate your issue.
either something to with your USB port(s), or drivers (either mobo chipset or usb), or windows installation. if you have usb that are controller by a chipset like Intel then other USB that are another chipset, try on the other "bank" so to speak...you'd have ot know how to look for that if you had it though...or try it on someone elses computer with those at&t drivers. don't connect the phone until you install the drivers.
if it's not usb port(s), drivers, or the windows installation you either have 3 bad micro USB or you have a faulty USB port on your phone. or pocket lint preventing a proper connection (although I've assumed you've looked for that already)...those are the only things left.
Still no luck
Sent from my SGH-I337M using xda app-developers app
Hey everyone, thanks in advance for the help. I just got a nexus 4 yesterday, that was already updated to 4.3 when I got it. My problem is when I go to unlock the boot loader, it won't recognize the phone. It says "list of devices attached" but doesn't give a serial number. Also, before this, it was giving a serial number, but was saying it was offline. So I uninstalled and reinstalled the drivers. Any help is most appreciated.
Sent from my Nexus 4 using xda premium
You might need updated adb/fastboot exe/dll's. Grab them from a toolkit, that's what I did.
meangreenie said:
You might need updated adb/fastboot exe/dll's. Grab them from a toolkit, that's what I did.
Click to expand...
Click to collapse
I completely upgraded the whole SDK. Still no good.
Sent from my Nexus 4 using xda premium
Try this... When you're connected to the PC , toggle USB debugging off and on.. It might ask for authorisation of ur PC in your phone.. Give yes.. Then do adb devices .. You might fight the offline thing gone
Sent from my Nexus 4 using Tapatalk 4
badhri said:
Try this... When you're connected to the PC , toggle USB debugging off and on.. It might ask for authorisation of ur PC in your phone.. Give yes.. Then do adb devices .. You might fight the offline thing gone
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I did that, got it to boot into boot loader through adb, then my fastboot drivers wouldn't install. So I uninstalled everything and started from scratch and now I can't even get the serial number to come up.
Sent from my Nexus 4 using xda premium
Enzopreme said:
I did that, got it to boot into boot loader through adb, then my fastboot drivers wouldn't install. So I uninstalled everything and started from scratch and now I can't even get the serial number to come up.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hmm.. doesn't it get shown as Android devices under device manager?
I too had a similar kind of problem with adb. I uninstalled the drivers manually and installed it again using Koush's Universal ADB (Android Debug Bridge) Driver for Windows. It has fastboot thing also. It worked for me.
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
You can also try someone else's PC or something. Install the drivers using the above link and just fastboot. Sorry, if that is of not much help. I'm new, both to this place and to this Nexus 4 device as well. All the best.
I'm not able to use fastboot at all on my nexus 4
I always get:
< waiting for device >
adb works fine, I can shell and view all the files etc. and "adb devices" lists my phone there and doesn't say offline. I've done all the normal stuff like changing USB ports (2.0 and 3.0) and I've tried different versions of ADB and the driver, clearing the RSA keys on the device. The phone is totally stock, no root and running 4.3 / JWR66Y and this has been happening before the latest OTA (JWR66Y) update (first OTA of 4.3)
Here's my bootloader info
Command line: console=ttyHSL0,115200,n8 androidboot.hardware=mako lpj=67677 uart
_console=enable lcd_maker_id=primary lge.hreset=off lge.reset=mode_reset gpt=ena
ble lge.kcal=0|0|0|x lge.rev=rev_10 androidboot.emmc=true androidboot.serialno=0
0475fbe14129674 androidboot.bootloader=MAKOZ20i androidboot.baseband=mdm bootrea
son=reboot
and I'm currently using the "Android Composite ADB Interface" Rev8 driver from the SDK on Windows 7 x64 along with the 18.0.1 version of the platform tools.
Did you download the fastboot.zip and place it in platform-tools of the android SDK?
Sent from my Nexus 4
Try the SDK package ..
Sent from my MB886 using xda app-developers app
I'm using the fastboot binary from the SDK as stated in the OP
I know this may seem obvious but covering the basics. You installed the fastboot driver? Is phone seen at all via device manager?
Sent from my Nexus 4 using xda app-developers app
marsdta said:
I know this may seem obvious but covering the basics. You installed the fastboot driver? Is phone seen at all via device manager?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do you mean the ADB driver or something else, I've tried the naked ADB driver and the SDK ADB driver, both give the same result, ADB.exe connects, I can open a shell and see the files etc., but fastboot.exe just hangs on waiting for device
When you plug in phone and its in fastboot is it recognized by device manager? Do you see an exclamation point next to it. If so you have to click and choose update driver(I used sdks version)
Sent from my Nexus 4 using xda app-developers app
marsdta said:
When you plug in phone and its in fastboot is it recognized by device manager? Do you see an exclamation point next to it. If so you have to click and choose update driver(I used sdks version)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No problem there. I don't think ADB would work if the driver weren't working would it?
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app
Delete.. Dndnt read OP properly.
marsdta said:
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes I've reinstalled the driver a few times and tried different drivers. I've tried the universal naked 0.72.the rev8 from the SDK and Koushes, all 3 work with adb and none worked with fastboot
marsdta said:
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Which driver did you use in the end? I've tried just about everything, I even grabbed another nexus 4 and I'm having the same issue with that one (which is on the earlier 4.3 OTA update btw)
Download the fastboot.zip and place it inside platform tools, even though SDK shows fastboot download fastboot again and place it inside
Sent from my Nexus 4
Cream$ickleHJ said:
Download the fastboot.zip and place it inside platform tools, even though SDK shows fastboot download fastboot again and place it inside
Sent from my Nexus 4
Click to expand...
Click to collapse
Download from where? Which files do you suspect are missing?
I used the one from the SDK. When booted up device manager shows adb composite and when in boot loader device manager shows android boot loader interface.
When you are reinstalling the drivers did you uninstall them first. That's what I usually do. Once helped someone who had the driver installed several times, so they were conflicting . I would uninstall drivers and delete any mention of them. Reboot PC. When plug in phone I ignore it trying to search and install boot loader driver. And install it manually
Sent from my Nexus 4 using xda app-developers app
Just got my phone today and for some reason cannot install the drivers in order to root my phone. I've enabled developer mode also and usb debugging is also not recognized oh the device as showing up on screen although its checked as active. Could my drivers for the nexus 5, nexus 7 our old nook he be coming into conflict with the drivers from this device somehow? I've routed several phones and this is strange and unusual behavior to me. Any help would be appreciated.
Sent from my LG-D800 using xda app-developers app
reignlight said:
Just got my phone today and for some reason cannot install the drivers in order to root my phone. I've enabled developer mode also and usb debugging is also not recognized oh the device as showing up on screen although its checked as active. Could my drivers for the nexus 5, nexus 7 our old nook he be coming into conflict with the drivers from this device somehow? I've routed several phones and this is strange and unusual behavior to me. Any help would be appreciated.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
It would help to know morea about what OS your using to root it. What have you tried so far? What cable are you using? Have you tried it on more then one machine? There is pertinent information missing that makes it hard to help. The old drivers might be causing a confict but I doubt it. However, if you think they are just uninstall them.
Switch to camera mode
Sent from my LG-D802 using Tapatalk