Related
I've gotten a new nexus 7 in the mail today and the first thing that I tried to do was unlock the bootloader and root the device to flash custom kernel and ROM. but i ran into a problem in the first step. Im having no luck with the drivers at all. i have searched and tried everything. I have tried this 1.5.2 toolkit and watched the video. In the section that i have to go to device manager and manually install the drivers, i didnt get anything. i downloaded the driver from asus themselves and it worked (pictured below) but when i try to use adb commands, nothing happens. I also installed the 64 bit drivers and it gives me the same thing as the picture and when i run the toolkit, it doesnt find adb. Can anyone help out please? and yes, i have enabled usb debugging, just in case you wonder.
What OS are you using?
When you plug the Nexus in the USB port does anything happen?
Have you rebooted the workstation?
4.1.1 jellybean. I've rebooted several times. When I plug it into the computer, my computer makes the regular "New device" sound and then it searches for the nexus driver but cannot find it. The tablet shows debugging connected.
Sent from my Gameboy Color
You have a workstation with JellyBean on it? I'm guessing it is a Win box perhaps right? Have you rebooted it?
I just unlocked and rooted today. I downloaded and installed the drivers from the PDAnet website. Everything worked fine. Hope this Info helps you get you unlocked and rooted
Sent from my Rooted Nexus 7 using xda premium
krelvinaz said:
You have a workstation with JellyBean on it? I'm guessing it is a Win box perhaps right? Have you rebooted it?
Click to expand...
Click to collapse
Sorry no, I misunderstood. I don't have a workstation. I have a laptop running Windows 7 and the tablet is running jelly bean.
Sent from my Gameboy Color
speedygonzo said:
I just unlocked and rooted today. I downloaded and installed the drivers from the PDAnet website. Everything worked fine. Hope this Info helps you get you unlocked and rooted
Sent from my Rooted Nexus 7 using xda premium
Click to expand...
Click to collapse
You went to pda net website and downloaded a .exe file and ran it right? I guess I'll have to do it from another computer maybe. I just don't have one though. I'll keep trying
Sent from my Gameboy Color
See my driver advice in http://forum.xda-developers.com/showthread.php?t=1794203
osmosizzz said:
You went to pda net website and downloaded a .exe file and ran it right? I guess I'll have to do it from another computer maybe. I just don't have one though. I'll keep trying
Sent from my Gameboy Color
Click to expand...
Click to collapse
Yeah, just download the driver package you need for your laptop and install them. The .exe is more like a setup/installation wizard for the drivers.
Sent from my Nexus 7 using xda premium
Napalm2 said:
See my driver advice in http://forum.xda-developers.com/showthread.php?t=1794203
Click to expand...
Click to collapse
Still nothing. I keep getting the android composite ADB interface driver no matter where i install the driver from and i've uninstalled and deleted the driver various times.
speedygonzo said:
Yeah, just download the driver package you need for your laptop and install them. The .exe is more like a setup/installation wizard for the drivers.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
still the same android comosite ADB interface
I was finally able to unlock the bootloader in Linux. But ran into another annoying problem
Sent from my Gameboy Color
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
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
Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Duplicate post. Please erase.
nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.
Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app
I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.
Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.
Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!