Related
Ive been to a dozen websites... everyone has a copy paste basically of the method. I've altered adb_usb.ini with the 0x1949 and altered the android_winusb in the correct places but when I attempt to update the drivers under my device manager my kindle is listed under Disk drives... not "other" etc like everyone tells me to look for.. and attempting to update the driver results in telling me I already have the best driver. I am unable to find my kindle with an adb devices even after multiple starting and killings of the server. I uninstalled the android sdk and reinstalled and redownloaded everything but still no luck. Please help. I'm far from a master but this is not my first rodeo having rooted 3 android phones.
Idk how you do it on other oses but on windows 7 it's:
Device manager, right click, update driver, let me choose, let me pick, have disk, c:\<path to win_usb.inf>
Sent from my Kindle Fire using Tapatalk
aye the problem is it believes it already has the best drivers for the job and won't accept android_winusb.inf as it's superior
Download Kindle Utility and run install-drivers.bat
Sent from my Kindle Fire using xda premium
I just discovered that and was very hopeful but it replied
This version of C:\Users\*\Desktop\Kindle Fire Utility\tools\x64\devcon.exe
is not compatible with the version of Windows you're running. Check your compute
r's system information to see whether you need a x86 (32-bit) or x64 (64-bit) ve
rsion of the program, and then contact the software publisher.
Android Debug Bridge version 1.0.25
I'm on Vista.. assumed it would have worked
edit: its possible that the x86 worked and the x64 failed.. but the fact remains my device remains un-found. If I wasn't balding I'd be tearing out my hair.
Thank you to those who have tried to help however.
i had this problem earlier but my friend fixed it! when he wakes up ill have him post the solution
now i have superuser apk on system but no root and adb said success!! wtf
Jcase fixed my su problem i wasnt pushing the su with adb
congrats, im still messing with things but running out of options on my end.
Try running the batch file from an administrator command prompt. Also delete any existing device in devmgmt.msc. I'm also on Vista, worked ok for me.
Sent from my Kindle Fire using xda premium
i attempted the driver batch as administrator... it oddly doesn't make it as far as without.. it just says the system can not find the path specified 4 or 5 times then stops. And I've attempted to delete the kindle from disk drives which is the only location it shows up but as soon as i plug it in again it re-installs.
Edit: a side note.. i have a "Android Phone" in my device manager that appears to be my kindle and is using the 0x1949 drivers... I assumed it was my actual phone but it disappears/reappears when i unplug my kindle
Thanks to everyone who helped, by the grace of god i got my device recognized ... got it rooted... then bricked it installing TWRP.. finally unbricked it... and now I'm not messing with it for the rest of the night lol
Ok so I am new hear and I was reading in THIS POST about installing TWRP using the Kindle Fire Utility. So I installed the drivers as directed and I see in my device manager "android ADB device" and in my taskbar I can eject the kindle. In File Manager I do not see the Kindle fire and the Kindle Fire Utility is not seeing my Kindle Fire. I am stuck and cannot post in the above forum because I have not made enough posts. Any help would be greatly appreciated. I would like to install Cynogen Mod to my Kindle fire to be able to access the full capabilities of this wonderful device.
Thank you
a good method to start is using kfu as you suggested but there are some tricks to get it running:
- place it to c:\ and rename it to "kfu" (it don't like spaces in pathname)
- try to install the correct drivers by running install_drivers.bat else install/update them manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
- pay attention on the driver verification level:
http://forum.xda-developers.com/showpost.php?p=22065426&postcount=846
- the drivers are in c:\kfu\drivers\kindle
- right drivers for each mode:
normal & recovery boot -> android composite adb interface
fastboot -> android adb interface
once you got rid of the drivers you have to update the run.bat of kfu to work with burritoroot3:
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
now you should be good to go ...
Thank you BB3 I will give this a try later tonight. appreciate the help
man install buritoroot and TWRP(which installs and FireFireFire) by yourself when i tried with the kindle fire utility all got were errors, but when i installed it by myself everythink went smooth. Just find separate guide for every step
1.Root
2.TWRP and FireFireFire
3.CM7
I'm having the same problem as you and it sucks I just want to root it
Hate to necro post, but I'm having the same issue and none of the posted suggestions work. I have the ADB drivers installed (the Kindle is detected as "Android Composite ADB Interface"), but I did not install the drivers using the KFU batch file; I could never get it to stop producing the unsigned error, no matter what system settings I chose for unsigned drivers. I ended up doing a manual driver install and directing the installer at the driver files that came with KFU. Now KFU refuses to "see" the Kindle connected to my system and therefore I can't do a thing with it. I am able to browse the Kindle files in Windows Explorer (should I be able to? I've seen conflicting answers to this), but KFU always reports its ADB status as "Offline". Soft disconnecting the Kindle (hitting the "Disconnect" button on the Kindle) doesn't change anything, except removes my ability to browse the Knidle files (no surprise there).
This is a fully updated (6.3) Kindle and Windows XP. I did attempt to manually do what KFU does automagically prior to finding out about KFU, but that effort produced similar results; the Kindle was never detected by the SDK tools, despite the drivers loading properly. I have also tried multiple USB ports on my system, but they all produced the same results. About the only thing I haven't tried is a different USB cable, but if the Kindle is able to be "seen" by the OS correctly, I don't think the cable is a problem.
Have you tryed rebooting your computer? http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html or http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US nat3mil gives good instruction it helps to watch the video do the step while paused then move onto the next its how I did it the first time the second time I just used the utility was easy peasy cause drivers were already installed and functional
Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.
cogadh said:
Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.
Click to expand...
Click to collapse
If you followed the instructions to the t like not plugging in your device until you have the drivers installed .then you may have something on your computer preventing adb try the 6.2.2 method
http://m.youtube.com/#/watch?desktop_uri=/watch?v=AZ88CYWv0FU&v=AZ88CYWv0FU&gl=US or just keep looking for something that works cause people miss steps all the time sometimes its persistence or trial and error that gets results I'm very surprised your not seeing anything in device manager that applies to your kindle mine installed some drivers immediately when I connected it I had to change them to root it but it did show up in the list of devices as well as appearing next to my c drive as a kindle for SD card access but I'm on windows seven anything I connect does something.
No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.
cogadh said:
No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.
Click to expand...
Click to collapse
Could be your machine but don't use the utility and when you do put twrp on if ya get there use 2.0 the older version people are having trouble with the new one http://www.techtuple.com/477/how-to-root-kindle-fire-6-3-easily/ this is done through cmd without utility. Original thread here http://forum.xda-developers.com/showthread.php?t=1568340
About all the advice I can give you all else fails use another computer windows 7 machine things are more straight forward than xp
Edit: just a side note a lot of people are bricking their devices I keep remembering the Christmas story be careful you'll shoot your eye out also some people I believe are having success opening kfu attaching thier fire while off then powering up the kindle
I read somewhere that the utility doesn't work for xp wish I could find the post I think you need to push the files the old way using command prompt and you will get it sounds like your drivers are there but utility is useless
If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Thanx soup better said than what I was trying
if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.
First time i've ever rooted a kindle and i had the same problem.
To fix this just go to device manager and uninstall the driver and then unplug and replug in your kindle then run the utility.
oh no trouble at all rooting rooted rommed and rockin here took the 6.3 ota this morning with 5 mins I was rooted with fff twrp then went back to 1 of my restore points of cm7 after a backup of 6.3 thanx tho
soupmagnet said:
If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
If all newbs do no other work but learn to use fastboot and adb it would save save a lot of grief for them and the ones helping them. jes sayin..
Thepooch said:
if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.
Click to expand...
Click to collapse
This will only work if the device is booted to a point where it will receive adb commands. Otherwise, use "fastboot devices". Sometimes if you are stuck at the bootloader it helps to shut your device down completely and restart before issuing fastboot commands.
Beyond that, it's a driver issue.
Sent from my Amazon Kindle Fire using xda premium
I had that same problem., but then I uninstalled the current drivers for my kindle altogether, and disabled them, then I ran install_drivers .bat again, then it worked.
Kindle Fire running KANG CM9
New developer, working on my own custom rom
I've used different guides, searched to death, but cannot seem to get the driver installed on this XP computer. Some of the guides seem to be for Vista or Windows 7. Is there a good video for XP, or one that relates to the driver issue?
xp is a good choice for this because you don't have to care about the uac (user access control)
maybe this one helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
I was in the same boat as you but luckly i had a netbook with windows 7 starter that worked for me. I couldn't find any help for XP either.
Sent from my Kindle Fire using xda premium
Unfortunately, that did not work for me. I'm fairly computer savvy, but this has stumped me. I will keep looking.
I was getting rather upset because I could get the USB drivers installed, but ADB still wouldn't recognize my Fire.
Is this the problem you guys are having? Or can you just not get the drivers to install at all?
It turned out that my problem was a complete, "I'm an Idiot!" deal. Especially because I'm a System Engineer and should know better than to overlook the steps I did. But, in very few of the instructions of how to load the drivers, does it tell you where the adb_usb.ini file needs to be located. I was thrown off because with the Kindle Fire Utility (ver. 0.9.3 at least), it comes located in the drivers folder. Plus, just about every time this file was mentioned, it always had a big thing about adding the 0x1949 device ID, which caused me to miss the couple times I ran across instructions that said where it needs to be located.
The adb_usb.ini needs to be, in XP, located in the ".android" folder that is located in your username's folder. For example, if I am logged into my computer as PBFred, the path would be the following...
C:\Documents and Settings\PBFred\.android
I also ran into one other problem. When you manually select the path for the driver, android_winusb.inf, (which you can place where ever you want) XP shows you a list of compatible device drivers. The correct device driver, "Android Composite ADB Interface", isn't listed unless you uncheck the box that says "show compatible devices only". If you don't uncheck that box, it just lists "Android ADB Interface", which is not the right one.
Once I did that, I was good to go. The only issue I have now with the driver is for no apparent reason, it asks for the driver to be reinstalled about half the time I plug my Fire in, even though I haven't plugged any other devices in inbetween. But since the path to the driver is still saved, it only takes 2 seconds.
I hope this helps you guys out.
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
DukeSilver79 said:
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
Click to expand...
Click to collapse
I don't quite follow where you are stuck.
Does running the command "adb devices" list your device? If so, your USB drivers are installed correctly. Which means that the version of Windows you are running pretty much doesn't matter any more.
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
'USB Debugging' enabled?
Of course. It will install drivers for the ADB device, it just won't be detected by adb.exe.
I tried the 'switch to Photo MTP' mode trick too. I am having no issues with adb to a One XL, One V, Defy, Aurora II or U8800. This is really bizarre.
Do you have java jdk installed correctly?
http://www.oracle.com/technetwork/java/javase/downloads/index.html
I wasn't aware java was relevant to adb at all (and I don't think it is) but yeah I have the JDK installed and it works fine for my app dev.
I had the same issue. Drivers installed correctly (and worked on other phones) but not the N4.
In the end i used an Ubuntu Virtual machine, attached the phone, followed a guide on XDA for getting ADB drivers in linux, and it worked straight away.
Days of trying in windows, and done in 5 minutes through linux.
Yep, I too went the virtual machine route.
Ridiculous. The only two developer devices I've owned (Nexus S and Nexus 4) and they've both been impossible to get the adb drivers going...
Passa91 said:
I wasn't aware java was relevant to adb at all (and I don't think it is) but yeah I have the JDK installed and it works fine for my app dev.
Click to expand...
Click to collapse
Yes you have to have installed the java jdk to run adb, it doesn't work without it. Java jdk is supposed to be setup first before you install the sdk so that it finds it. One issue why people can't get adb working is that the path environment variables are not set up and need to be manually entered.
Example of setting your windows path environment variables for jdk version 6 windows 32 bit on Windows Vista.
right-click on My Computer, and select Properties
under the Advanced tab, hit the Environment Variables button
in the dialog that comes up, under System Variables double-click on Path
Add ;C:\Program Files (x86)\Java\jdk1.6.0_18\bin to the Path variable (or wherever the jdk was installed)
Add ;C:\android\android-sdk-windows\platform-tools to the Path variable (or wherever you installed the sdk)
Passa91 said:
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
Click to expand...
Click to collapse
I posted a solution some time a go find it in my posts
Sent from my Nexus 4 using xda premium
davehunt83 said:
I had the same issue. Drivers installed correctly (and worked on other phones) but not the N4.
In the end i used an Ubuntu Virtual machine, attached the phone, followed a guide on XDA for getting ADB drivers in linux, and it worked straight away.
Days of trying in windows, and done in 5 minutes through linux.
Click to expand...
Click to collapse
The linux guides include editing the udev rules so that you manually enter the Nexus 4 into the list of devices in order to get adb to recognize the phone. Could be the same issue with windows. I only have the sdk installed on a Linux box and haven't used it on windows since I installed it on a Vista box a few years ago but I would imagine windows would have the same problem recognizing the phone.
Linux Install Instructions
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Passa91 said:
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
Click to expand...
Click to collapse
I used the Universal_Naked_Driver_0.72. It worked for me. I did not install Java.
http://dl.dropbox.com/u/18573149/Universal_Naked_Driver_0.72.zip
RacerXO said:
I used the Universal_Naked_Driver_0.72. It worked for me. I did not install Java.
http://dl.dropbox.com/u/18573149/Universal_Naked_Driver_0.72.zip
Click to expand...
Click to collapse
You shouldn't even be able to install the sdk properly without having java jdk installed first as the windows installer checks to see if its there.
http://developer.android.com/sdk/installing/index.html
Edit: and by installer I meant SDK Manager, what you use to download and install the android usb drivers. I suppose you can get past the java limitation by just downloading the sdk and copying the needed files into the c directory then using 3rd party drivers but java jdk is what controls the phone once its connected so I don't know how you are getting it to work.
Edit 2: I guess I was wrong in part, I installed the sdk without java jdk on a windows xp box, used the universal drivers linked to above, and it recognized my phone in adb devices and I was able to reboot it. But I can't use sdk manager as it requires java jdk to be installed.
had the same issue... you must be using a usb port on the front/side of the computer
use one of the usb ports on the back, and you should be just fine.
This happens to me too. On all windows computers I have used for ADB and all phones it will work the first few times, and then it won't work no matter what. I can usually get fastboot to work reliably but that is it.
Sent from my Nexus 4 using Tapatalk 2