Hi
I have 2 Kindle Fire HD 7 inch. The 16GB is rooted and can run ADB commands from the latest FirstAide. The other is a new 32GB (arrived today) and I am trying to root it.
In XPs admin tools/computer management, the Android Composite ADB Interface driver is shown. In Properties/general, the rooted device is shown as working normally, whereas the unrooted device is shown as "Currently, this hardware device is not connected to the computer. (Code 45)"
Obviously, trying to use FirstAide to root the new device won't work if ADB isn't working.
As the PC installation is the same, and even the same USB data is being used, there must be something different with the new device. I can't believe that the storage size plays a part so what should I look at? ADB is turned on in the new device (more/device/ADB).
I do have a factory cable but don't know how that can be used in this instance. The new device seems to work normally, and both device and PC have been rebooted/reset to no avail.
Can anyone help or does it look like the device is faulty?
edit: the new device was v7.2.2 but updated itself soon after to 7.2.3 which is the same as the rooted 16GB device
I just used the factory cable and reset the device which went into fastboot mode but didn't respond to any fastboot commands. Switching off and replacing the factory cable with standard data cable saw it boot normally (I thought the boot mode was persistent until reset?)
Maybe try a factory reset on the new one and then turn off wifi until you root it.
Sent from my KFTT using xda premium
If you connected the 32gb kindle before enabling adb at any point you'll want to UNINSTALL its drivers from device manager on your PC and upon reconnect your PC will install the adb version of these drivers assuming adb is enabled.
Let me know how this works for you.
Sent from my KFTT using xda app-developers app
Thanks for the replies. I'm a little confused.
Eventually, I uninstalled the drivers from the PC. I found I couldn't install the drivers using the new FirstAide, I got an error message, so I used the old FirstAide and the drivers installed no problem. From there I could get to root. :laugh:
However, now I find that the old device isn't seen by ADB whilst the new one is..... it's as if the drivers are device specific.
Can anyone explain this to me? In my mind, the drivers, once installed correctly should work for all devices. At the moment, I'm faced with uninstalling/reinstalling drivers whenever I want to swap devices.
victorlugo do you literally mean that if you charge up the device without enabling ADB then you won't be able to install the drivers? As it is, enabling ADB was one of the first things I did, as it was my intention to root it immediately and transfer data from the 16GB model using Titanium.
well, I now have 5 drivers installed covering the 2 devices:
2 x Android ADB Interface
2 x Android Composite ADB Interface
1 x Tate-PVT-08
anyone have any ideas why this might happen? Each device responds to ADB ok, but they use separate drivers
Related
For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud
Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080
anyone have problems in ubuntu 10.04 can't get it :'(
I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk
I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.
[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.
If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs
I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps
Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.
Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave
I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.
I have 2 Kindle Fire 2nd generations. I'm trying to root them. So far, I have successfully rooted one, using qemu, and Bin4ry's Root as laid out here: http://forum.xda-developers.com/showthread.php?t=2075959 . In order to be successful with this, I already have the drivers installed, and the SDK for this. I have already made sure that ADB was enabled on the device, but it is not being detected when trying "adb devices" from the command line. I have also already tried to kill-server, and start-server, I've rebooted both the Kindle, and the PC. Also, my PC is running Windows Vista. My computer detects both devices as a Kindle, and I am able to transfer files to and from both devices fine. The only apparent difference between the 2 is that adb will detect one fine and not the other. When I run "adb devices" with my other Kindle connected, it detects that one just fine. If anyone can help, I'd really appreciate it!
Chr0nos77 said:
I have 2 Kindle Fire 2nd generations. I'm trying to root them. So far, I have successfully rooted one, using qemu, and Bin4ry's Root as laid out here: http://forum.xda-developers.com/showthread.php?t=2075959 . In order to be successful with this, I already have the drivers installed, and the SDK for this. I have already made sure that ADB was enabled on the device, but it is not being detected when trying "adb devices" from the command line. I have also already tried to kill-server, and start-server, I've rebooted both the Kindle, and the PC. Also, my PC is running Windows Vista. My computer detects both devices as a Kindle, and I am able to transfer files to and from both devices fine. The only apparent difference between the 2 is that adb will detect one fine and not the other. When I run "adb devices" with my other Kindle connected, it detects that one just fine. If anyone can help, I'd really appreciate it!
Click to expand...
Click to collapse
Are you using the same cable?
Try going to the computers device manager and disabling the kindle uninstalling the driver reinstalling it then reenable the kindle. then try adb devices and see if that works
I am using the same cable. I reinstalled the drivers by uninstalling, and reinstalling in device manager. It worked thank you! I'm surprised that it had to be reinstalled for an identical device, but I'm happy it worked. Sorry about the slow response, I've been busy the last couple of days. Again, I really appreciate the help!
I bricked my Fire HD 7" a while back and decided to start working on it again.
I was doing some mods before I bricked it. The device, once it boots into Kindle's OS is EXTREMEMELEY slow. All the icons are blank, and it is extremely slow to do anything on but it kinda works. The menu to reset the device doesn't work, and the keyboard and other stuff barely works if at all as well.
I believe the unit used to be rooted, but somewhere along my bad fixing process I believe it is 'locked' again.
I am currently working on making a factory cable from the droid website in where you solder a cable from 1 to 4.
Following that guide. Any tips?
Thank you very much
Edit:
I can boot the KF HD second gen into fastboot mode but no idea what to do next. I have tried almost everything. I can't instal adb or even get the drivers to work. The device shows up with Windows giving me an error message. Yes, I have Android sdk and Java installed with proper Google usb drivers and api in there modified to add Kindle Fire HD in there. And yes, I have tried to manually add drivers. It just won't work, and or show life.
This sounds like a bad qemu root... look in the /data folder for a ".prop" file and delete it if you can. I would check the device manager for a usb composite device with a hardware id vid of 1949 and uninstall it if I were you. Also try the drivers in my signature, they should work with all modes but you tend to have to uninstall the driver between going from normal os to fastboot and recovery.
Sent from my LG-P769 using xda app-developers app
stunts513 said:
This sounds like a bad qemu root... look in the /data folder for a ".prop" file and delete it if you can. I would check the device manager for a usb composite device with a hardware id vid of 1949 and uninstall it if I were you. Also try the drivers in my signature, they should work with all modes but you tend to have to uninstall the driver between going from normal os to fastboot and recovery.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Can you go into detail on what it is that you mean pleasE?
kingbowness said:
Can you go into detail on what it is that you mean pleasE?
Click to expand...
Click to collapse
ok lemme reply now that i'm on my pc so i can type better, the kindle drivers are a bit finicky, between switching between fastboot, recovery, and the normal os it tends to make you have to uninstall the device to reinstall the drivers, and if adb was enabled in the os typically it shows up as a composite device that you don't tend to notice, so if you goto the device manager, look under usb devices, and see some composite devices right click them and hit properties and goto the details tab, look for one with a hardware id with something like "USB\VID_1949" it will have other stuff after that but i don't feel the need to put it. If you find one of those then uninstall the composite device and search for new hardware or just unplug and plug the kindle back in, it should be able to install the drivers now. Otherwise just uninstall any previous kindle devices when switching between boot modes.
As for the other part i was saying, you could probably just fix this if adb is enabled in the main os, just connect to the kindle from an adb shell and cd into the /data folder and look for a ".prop" file(run the command ls if you don't know that much about linux it will list the contents of the directory you are in.), i don't remember the name, but part of the qemu root process sometimes leaves that file there and causes the symtoms you mentioned, deleting the file fixes it but i don't remeber its name offhand. so if you see a .prop file in the /data folder then run "rm whatevername.prop"
stunts513 said:
ok lemme reply now that i'm on my pc so i can type better, the kindle drivers are a bit finicky, between switching between fastboot, recovery, and the normal os it tends to make you have to uninstall the device to reinstall the drivers, and if adb was enabled in the os typically it shows up as a composite device that you don't tend to notice, so if you goto the device manager, look under usb devices, and see some composite devices right click them and hit properties and goto the details tab, look for one with a hardware id with something like "USB\VID_1949" it will have other stuff after that but i don't feel the need to put it. If you find one of those then uninstall the composite device and search for new hardware or just unplug and plug the kindle back in, it should be able to install the drivers now. Otherwise just uninstall any previous kindle devices when switching between boot modes.
As for the other part i was saying, you could probably just fix this if adb is enabled in the main os, just connect to the kindle from an adb shell and cd into the /data folder and look for a ".prop" file(run the command ls if you don't know that much about linux it will list the contents of the directory you are in.), i don't remember the name, but part of the qemu root process sometimes leaves that file there and causes the symtoms you mentioned, deleting the file fixes it but i don't remeber its name offhand. so if you see a .prop file in the /data folder then run "rm whatevername.prop"
Click to expand...
Click to collapse
Nope, nothing shows up in device manager in those areas. The Kindle shows up under portable devices. NOTHING works in uninstalling or changing it's drivers.
I can't get ADB no matter what it seems.
So what about when its in fastboot mode? If it goes into fastboot, uninstall the portable device and try searching for new hardware, if it cant find a driver then point it to mine. If you can get fastboot working you can just use kindle fire first aid to restore the device.
stunts513 said:
So what about when its in fastboot mode? If it goes into fastboot, uninstall the portable device and try searching for new hardware, if it cant find a driver then point it to mine. If you can get fastboot working you can just use kindle fire first aid to restore the device.
Click to expand...
Click to collapse
Drivers don't work in fastboot. I keep getting This Device cannot start code 10.I got the drivers to work in normal mode now and have ADB installed, but I can't find the ADB devices even with kill-server and adb devices.
Thank you everyone for your help, I got the issue fixed.
I used FFFirstAide.
That didn't work for me for a while because my fastboot cable had a disconnected data lined.
I am so frustrated right now I don't even know what to do. Here is where I am and I welcome any ideas. I have read and tried every suggestion I can think of.
I have a Win 8 laptop I want to connect the Nexus to so that I can sideload 5.1. Currently the phone is still factory stock.
With debug turned off, my computer sees the nexus and I can transfer files. It sees it as an MTP device
With USB DEbug checked, my computer no longer sees it at all.
I have the latest android sdk installed.
When I go into platform tools and run adb devices- it is blank, nothing in either state (debug on or off).
Also it is not recognized in "Fastboot devices" when in fastboot mode, so the computer is not seeing it.
I have used USBDEview to delete drivers, then reinstalled using the latest Google USB drivers. no Help.
I have tried using motorola device manager to install proper drivers, no help.
Tried using Koush universal drivers and it did not help.
Thank you for any ideas you may have.
Try using "Nexus Root Toolkit" to set up the drivers for you. It has a driver setup tool.
aawshads said:
I am so frustrated right now I don't even know what to do. Here is where I am and I welcome any ideas. I have read and tried every suggestion I can think of.
I have a Win 8 laptop I want to connect the Nexus to so that I can sideload 5.1. Currently the phone is still factory stock.
With debug turned off, my computer sees the nexus and I can transfer files. It sees it as an MTP device
With USB DEbug checked, my computer no longer sees it at all.
I have the latest android sdk installed.
When I go into platform tools and run adb devices- it is blank, nothing in either state (debug on or off).
Also it is not recognized in "Fastboot devices" when in fastboot mode, so the computer is not seeing it.
I have used USBDEview to delete drivers, then reinstalled using the latest Google USB drivers. no Help.
I have tried using motorola device manager to install proper drivers, no help.
Tried using Koush universal drivers and it did not help.
Thank you for any ideas you may have.
Click to expand...
Click to collapse
I just went through that a couple hours ago. I ended up having to go in the device manager, and manually point it to look for the drivers in the platform-tools folder of windows sdk. Once I did that, the little yellow triangle went away, and all was well, adb and fastboot worked as normal. Hopefully that works for you too.
Hi. I've been trying for hours to get Helium backup to work with my R1 and it won't work. My G4 works fine with the same USB port and cable. When my G4 is plugged in, if I type adb devices, it shows up. The BLU phone does not show up. I've tried uninstalling and installing Helium in my computer and in the phone. I did a hard reset on the phone. I downloaded and installed the drivers Helium recommends and nothing. I simply can't make the R1 work. I've noticed a few people having the same problem in other forums but I haven't found a fix for it.
Anyone can give me some ideas? Thanks.
Did you enable usb debugging. Not calling you an android dummy but we have all forgot to enable usb debugging one time or uhnutha.
Yeah, I enabled it.
Another day trying to get adb to see my phone and nothing. I installed mtk drivers, etc and I'm still getting a blank when typing "adb devices"...
Are you using the cable from Blu? I noticed that my other devices work fine with any cable, but the R1 only seems to respond with the Blu provided USB cable.
Yeah, I started using the BLU cable just in case and it didn't make a difference.
Sent from my VS986 using Tapatalk
My phone recognizes ADB perfectly in TWRP but I cannot get adb to work with the system up.
Not a cable or adb drivers.
king200 said:
My phone recognizes ADB perfectly in TWRP but I cannot get adb to work with the system up.
Not a cable or adb drivers.
Click to expand...
Click to collapse
Don't be so sure it's not driver, because while in recovery and while in system the phone reports different mode to PC, so could be using different driver
Try going into device manager in Windows and updating the driver. Select choose from available drivers, and if there's one that's different than what is currently loaded, try that one.
Sent from my BLU R1 HD using Tapatalk
Vendor ID issue, you need to update the adb_usb.ini to include it.
I got adb to see my R1 under Windows. When you plug it in, change from MTP mode to PTP mode and unplug it, then plug back in. It works in PTP mode but not MTP mode for some odd reason.
Synir said:
Vendor ID issue, you need to update the adb_usb.ini to include it.
Click to expand...
Click to collapse
What is the proper vendor entry. What is your entries. Currently I have:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x12D1
king200 said:
What is the proper vendor entry. What is your entries. Currently I have:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x12D1
Click to expand...
Click to collapse
did it work?
Has anyone solved this issue yet?
i cant seem to figure out how to get adb to work with this phone. need help im on 6.6 and no step by step instructions on how to either roll back or just install a new rom.
pookeye said:
i cant seem to figure out how to get adb to work with this phone. need help im on 6.6 and no step by step instructions on how to either roll back or just install a new rom.
Click to expand...
Click to collapse
ADB just "works" for so many users, It leaves the dumb question . Did you enable developer options and turn adb debugging?
Also what abd are you using?
Easiest thing to do would be reinstall adb + fastboot with 15 second install.
link to that is in the unlock tool thread. Which will also answer your question what is needed to install new / other rom.
(tool unlocks bootloader, flash twrp, can install superSU,)