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.
HI,
I've had success installing my other android devices on my windows 7 x64 computer, have even used my (ADB) Nook Colour on a windows 7 32Bit laptop fine.
Problem: Android Composite ADB Driver wont install/ isn't found, Device is Auto Nootered on 1.1 using rooted stock firmware.
Tried:
I have the .android folder in my user profile dir with the device ID in it
Followed various wikis and guides (that worked for the 32Bit version)
Watched the driver load/unload in device manager as I tick 'Development Mode (enable ADB)'
Tried various driver packs from here and googles latest offering, still only matches up with Android ADB Driver not the Composite (wont even show me the composite one)
Wireless ADB works and is disabled, worried about installing CWM using wireless for some reason USB feels safer to me
Thinks I noticed:
Hardware ID is listed as USB\VID_2080&PID_0002 which matchs up with %SingleAdbInterface% in the ini file for the driver, composite aka %CompositeAdbInterface% has &MI_01 on the end. Not sure if that means its not getting the right hardware ID from the device when ADB/ Development mode is enabled of if having the wrong driver loaded on it shows up the wrong Hardware ID.
Things I havent tried, enabling ADB on the Nook using sqlite3 method, but if it works on another coputer didn't think it would be a good idea.
Plan:
Install CWM, flash CM7 or similar to device.
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
ouldsmobile said:
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
Click to expand...
Click to collapse
Same here!
This one is weird...
I'm on win7x64 and I *have* got adb to work at times. When I was first rooting my new NC (1.1.0), I fiddled with it and I had it running over usb fine. But now, when I plug in the usb and I either get that the device is unrecognized or it goes into usb sync mode. Haven't quite figured that out...
But, ultimately, I just use adb wireless for any adb stuff, although it's "not recommended". It's worked perfect for me all along.
Check this link
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
loupnook said:
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
Click to expand...
Click to collapse
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
UR Welcome and USB Automount?
NewZJ said:
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
Click to expand...
Click to collapse
Glad to help. What do you mean USB Auto Mount? I kind of thought that should happen?
My goal for getting adb working was to get su, which i got here http://forum.xda-developers.com/showthread.php?t=953110 with a bit of trouble but seems to work, so that i could drag items from my pc onto HC. I'm using http://forum.xda-developers.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i only see my BN media directory from my pc now (yay) but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.
I've installed DropBox but it keeps asking for an SD card, which isn't a big issue, just i haven't found the time to go buy one. Is there a way to use db without an SD card?
unfortunately no, db requires external storage. if you opened the apk to recode its default directory maybe but im not sure its possible
usb auto mount I can disable in nook tools but its a persistant system that defaults every reboot, I dont like to see it popup while using the nook when I plug it in just one of many peeves
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
GateheaD said:
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
Click to expand...
Click to collapse
I thought that as well and flashed back to the EC 1.0.1, sideloaded 1.1 update and repartitioned, used cw to add HC back and all that, and still had the same issue. Came down to the ini file not having a NookColor section.
Did you check the link http://forum.xda-developers.com/showthread.php?t=987409
I'm no stranger to drivers, I could force it to use the driver by changing the ini files but it still wouldn't appear in ADB Devices.
Flashed Nooky FroYo and now the device driver states the hardware ID has the missing '&MI_01' which means the composite driver works out of the box.
I used IOMonsters Easy USB installer and it seems to have installed the drivers for Windows 7 64Bit Fine
After running the install .exe I also had to execute the Inst64.exe
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.
QUESTION: Can someone please explain in simple form how to fix the ADB unauthorized issue that has been present since the update to M? The option for removing any current rsa keys is gone from the developer settings. And when you plug your phone in to a new computer it used to pop up a notification that would let you accept the rsa key. None of this is working any more. I cant believe that it is not a bigger issue and I have spent a few hours over a few days looking for a solution so if I have missed it, I am sorry. I have read a few things that say that google has just removed the ability to use adb and one post even explaining that, what looked to me to be a prop file variable, needed to be changed from 0 to 1, or vise versa, but didnt explain where the variable was. I dont see anything that I am confident with in the build.prop. Thanks. Please explain so that anyone will be able to overcome this issue, or point to a link.
Are you talking about the option to "Revoke USB debugging authorisations" under Developer options? It's there, at least on my N6 running stock 6.0.1 MMB29V... And I just tried to ADB to my device and the popup for the authorisation came up on the phone, just as it should.
I think you have some other problem going on.
Are you running the latest adb/fastboot tools on your PC?
Article showing removal of ADB
stevemw said:
Are you running the latest adb/fastboot tools on your PC?
Click to expand...
Click to collapse
Yes I am, I always use the one directly from the 'platform-tools' directory in the SDK. Another thing is I have read multiple articles that actually state that Google has removed the adb functionality in marshmallow... I don't get it. I even went from stock G.E. to CM an its exact same problem. Not to mention now I am dealing bwith the fact that the nethunter kernel isn't compatible with the CM build for Nexus... What!? Anyone can enlighten me on that subject I would love to know that as well... LoL. Here is link to one of the ADB articles though.
Tekto-kodi.com/kodi-news/marshmallow-android-6-removes-adb/
I looked at your link and the links provided in that article. The only thing I can read from those is that the ability to run ADB from your phone, i.e. from the terminal emulator (not your PC) has been removed. Are you trying to run ADB from your phone or your PC (I was under the impression that you're using your PC, but I have to ask)?
As I stated before, ADB from my PC to my N6 works just fine with Marshmallow (6.0.1 MMB29V).
You say that you use ADB directly from "platform-tools", but you don't say if you've updated the tools from the SDK-manager.
I have had a very eventful few hours and I'll do my best to explain. Earlier this morning I was rooted, twrp installed and running FreedomOS. I had this bright idea of flashing a file I had downloaded from the OP3T website. It was a firmware file (either the first option, the option before OB5). Everything was running smoothly until I got home and tried using fastboot at which point it just sticks on waiting for device. All normal options are checked (adb files installed, debugging selected, the works), but now I can not use fastboot what so ever. I did at one point sideload an OTA using adb sideload (filename.zip). I have tried just about every adb option I can think of to include: 15 second ADB and minimal adb and fastboot. I even deleted the OP3T drivers from my computer, reinstalled those drivers. I followed an article through technobuzz: http://www.technobuzz.net/download-oneplus-3-usb-drivers/
http://www.technobuzz.net/setup-adb-fastboot-drivers-for-nexus-oneplus-samsung-or-any-android/
I have been using adb and fastboot with no issues up til Open Beta 5 and now my PC and another PC is giving me crap and it's iritating the %%%k out of me.
adb reboot recovery works, adb devices work - showing that the device is connected. I checked the device manager and only found the portable devices. It's like my computer somehow magically deleted the adb driver and will not allow me to install an adb driver. I have no logs to check out....15 second adb was suppose to place a log file on the desktop, but it doesnt....it wont install
Here's what Im on:
OB5 (7.1.1) with stock recovery. I can not use fastboot commands. Here are some pics
http://imgur.com/a/y7iFE
http://imgur.com/a/SVVMg You should see something that says, "Android Device or ADB", but nothing - just MTP
http://imgur.com/a/62msw
I'm using windows 10, device signature is off
Essentially I just want to be able to fastboot flash TWRP and gain root.
Has anyone else experienced any kind of issues with OB5 and adb/fastboot
Btw I had the entire Android SDK installed on another computer and that did not work either....Any assistance would be greatly appreciated. I'm talking about you @redpoint73, lol
Oh boy, I've been summoned! I have to say, I'm not anywhere near knowledgeable yet with the 3T as I was with my past devices. But I'll try.
I assume you are properly trying fastboot commands while in fastboot mode (not in OS or recovery)? I assume so, since you already said it worked fine before the update. But it never hurts to ask the obvious, as a lot of folks forget that adb and fastboot work a bit differently (fastboot only in fastboot mode, adb only in OS or recovery - debugging only needed for adb, not fastboot).
Do you have the OP3T drivers installed? These are the files that Windows always opens whenever I connect the phone (while booted into phone OS), select File Transfer, and it gives the option to open the folder. Although I don't think you even need the drivers for fastboot to work. I unlocked the bootloader and flashed TWRP before I ever installed the OnePlus drivers. The generic fastboot drivers worked fine. But it's worth a try, to install the OP drivers.
I don't even know where to begin or how to reply to what you just said @redpoint73. I haven't attempted to use adb/fastboot commands since yesterday, so i have no idea as to rather it will work or not. If you have teamviewer, I can give your access to a backdoor to show you as it's easier to show then explain. Have you ever noticed when you download a zip from here: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
it never saves the file as Open Beta 3, 4, or etc. It saves the file as this long-named file.zip rather than being something easy to understand. Im able to understand it now, but a few moments ago I wasnt. I "have" downloaded the OP3T drivers on multiple occasions with no success to to fastboot only adb. My computer recognizes the device though. When I go into device manager checking things out. I will have an option that says, "portable devices". when you select that option you'll go across through some contextual menus where you wind up seeing MTP. You should see MTP if you successfully installed the OP3T devices, but at the same time you should be able to see an option that says something along the lines of ADB or Android Debug Bridge, vice versa. My computer does not say that and I have no idea where to go from here. I have no logs or anything helping me out, so it's like finding a needle in the haystack. I do know that I have all of the prereq's such as debugging selected from developers options within the phone, device signature turned off through Windows, adb/fastboot installed, OP3T drivers installed - you know the works you usually need in order to get everything working right. What I might end up doing is just reformatting my entire laptop, installing a fresh copy of windows, fresh copy of adb/fastboot and going from there. My bootloader is unlocked and has been since I've owned the device. As of right now I'm on OB5 with stock recovery. Yesterday I tried three times to sideload one of the downloads from this site: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
. However, my phone would end up saying, "installation failed" when Im in sideload mode. I'm thinking that might have something to do with a botched download from the OP3T server.
Looks like you found your solution here: https://forum.xda-developers.com/showpost.php?p=72046709&postcount=20
Fastboot/adb is usually as simple as reinstalling drivers, etc. as opposed to reformat the PC as you were considering. Reinstalling adb/fastboot was a good idea also, as I don't think I would have thought of that (although it makes perfect sense). So good job working it out!