I can't see the Nook using adb anymore. I can see my phone so the connection is fine. Seems to have happened after installing the B&N SDK. Anyone else have this issue??
macndroid said:
I can't see the Nook using adb anymore. I can see my phone so the connection is fine. Seems to have happened after installing the B&N SDK. Anyone else have this issue??
Click to expand...
Click to collapse
I had this issue.. not sure what broke... double check the 'adb_usb.ini' file in your 'c:\users\user\.android' folder and make sure it still has '0x2080', mine was changed somehow. not sure if this is what fixed my adb connection but it's working again now.
During installation, it changed the "'adb_usb.ini" file...just go back into it and add "0x2080" back. It should work again.
Bingo. That did it - just edited and added 0x2080 on a new line.
The technically correct answer...
...is after installing the nook SDK, you then run the following command, per the instructions:
android update adb
Related
hi all.
The title of the thread says it all.
My ddms only shows com.cooliris.media as a running application.
Has anyone similar problems? Or even a solution for it?
cheerio n3utrino
PS: Running Ubuntu Linux. ADB and everything else is working. But those darn threads won't show.
I had this problem for some time. I solved it but I'm not exactly sure how. Try updating adb and ddms to the most recent sdk. Also, an existing adb session such as from eclipse seems to cause it on occasion.
I had this problem before but after updating to the latest ERE27 N1 ROM everything are showed in DDMS as normal. May be you should give it a try.
n3utrino said:
PS: Running Ubuntu Linux. ADB and everything else is working. But those darn threads won't show.
Click to expand...
Click to collapse
I'm assuming you've tried rebooting your computer, but if not...try `adb kill-server', and if that doesn't work, try rebooting. Sucks but sometimes it's the only way (even in Linux).
[SOLVED]
Rooting my phone did the trick.
Now all threads are showing.
Thanks for the suggestions.
hi all.
I'm still in this trouble.
How did you solve this? > n3utrino
BR.
Addition
To solve the problem one must
Declare your application as "debuggable" in your Android Manifest.
In Eclipse, you can do this from the Application tab when viewing the Manifest (on the right side, set Debuggable to true). Otherwise, in the AndroidManifest.xml file, add android:debuggable="true" to the <application> element.
Click to expand...
Click to collapse
if you dont want to root your phone.
Ok. I got my nc rooted, and used ROM Manager to install NF internally. Now I want to put gApps on it. So far everything is working wonderfully.
I download the Easy Driver Pack (http://forum.xda-developers.com/archive/index.php/t-910008.html) and follow the instructions. My NC isnt recognized. I went through all the troubleshooting tips there that I could find and my NC still isnt recognized.
Next I download http://legacyschool.us.to/nookdev/nook-usb-installer.rar and follow those instructions thinking that I might be able to fix said problem above. Still a failure. Now I've reached the point that I'm becoming slightly frustrated. Before I rooted my NC was recognized. Before I used ROM Manager to install NF my NC was recognized, and now I cant figure out wtf I'm doing wrong. Can someone help me out please?
UPDATE:
I got ADB to recognize my nook and it says that it's one of the adb devices plugged into my computer. When I go to enter the command prompts to install google apps, the cmd window freezes up after I input the first line (and I'm hoping I read the directions correctly and have my cmd window pointed in the right direction, at the sdk tools folder with the correct google application system file inside it)
So I'm not sure where to go after this because I'm not seeing anywhere that I could go back and fix an error. Maybe someone else will.
Subject largely says it all. ADB is running fine through terminal, but when I run the adb devices command, no results are returned. Trying to run the install script to get the market up and running.
Any help? And the old cliches ring true here "I've searched, and failed" for quite some time. The only similar result I've seen on here just wound up "working" for someone.
Cheers.
ADB wasn't recongnizing my Nook Color either so I downloaded the adbWireless app from the marketplace. Hope this helps!
ChickenGod said:
ADB wasn't recongnizing my Nook Color either so I downloaded the adbWireless app from the marketplace. Hope this helps!
Click to expand...
Click to collapse
Unfortunately until i have an adb connection, i cannot install the market, which is a shame considering i really enjoy the HC preview.
When had the same problem w nook color running CM7, somebody told me to put 0x2080 in .android/adb_usb.ini. it worked first time I tried. Next day, it did not. After I checked off Stay Awake (under Application,Development), it works since.
Well why dont you use the terminal that -should- be on the HCv4... you can use busybox to push and do other things...
What are you trying to do?
arrjaytea said:
Subject largely says it all. ADB is running fine through terminal, but when I run the adb devices command, no results are returned. Trying to run the install script to get the market up and running.
Any help? And the old cliches ring true here "I've searched, and failed" for quite some time. The only similar result I've seen on here just wound up "working" for someone.
Cheers.
Click to expand...
Click to collapse
Just use Auto-nooter and you'll get the market
ChickenGod said:
Well why dont you use the terminal that -should- be on the HCv4... you can use busybox to push and do other things...
What are you trying to do?
Click to expand...
Click to collapse
pdanders said:
Just use Auto-nooter and you'll get the market
Click to expand...
Click to collapse
I appreciate the attempts to help, guys - but I did think I made it somewhat clear in the OP that I was trying to load the market via the widely circulated ADB script. I don't know if busybox is an option - and Auto-nooter is definitely not.
Regardless, thanks again - and I did just decide to go with the flashable HcV4 as it included the market and gapps bundle. Now if only we can get that new fangled gmail up and running... though I know that's wishful thinking at the moment.
I had this exact same problem. No matter what I tried, I couldn't get ADB to work on my MacBook with HC v4. So I booted into Windows using parallel and that worked, so I have been using windows thus far to ADB into the Nook
A couple of days ago I flashed Eclipse v2.0, wanting to change my phone up a bit I had been on shift3r for a few weeks. Anyways, just now I was trying to copy some modules into my /system/lib/modules to overclock my device and was having issues copying within my phone. So I tried to use an adb shell to do so, but I keep getting the output of the device being offline, this is what I'm getting:
-NV57H:~$ adb devices
List of devices attached
0A3BAF200C014015 offline
And I have done a search, where some people were having trouble using certain cords, mainly with Samsung devices, and switched cords with success. This does not apply in this situation as I have used adb many times with the cord I'm using, and also I did try to switch cords anyways. Also the only other thing I saw was a situation involving driver installation and re-installation creating problems. As I am on Lubuntu, and not Windows, this does not apply to the situation because I have neither installed or re-installed drivers. My adb is setup properly because I have been using this computer for a couple weeks now and it was working previously. Any ideas on anything that could have happened? or maybe I should switch ROMs?
additionally: on my file manager, in the address bar for my device when it is plugged up, it is seeming odd to me, this is now what the address is showing for my device's sdcard:
gphoto2://[usb:002,007]/
I think I might have messed something up on my Bionic. If you read the first post I was saying how I tried adb on the same computer I've been using, AFTER flashing Liberty. Well I've gotten rid of Liberty and went back to SHIFT3R to try to fix the problem, and my problem is still looming. I have tried on Lubuntu and Windows, and my girlfriend's Incredible 2 works on both of the OS's with the same cables I'm using as well. I remember the other day when I was flashing Liberty, I had to mount my USB while in recovery to move the file onto my SDCARD because it had vanished once I tried looking for it to flash it. I remember when I tried to eject my phone from my computer (lubuntu), it said that it was busy and could not unmount the phone, after the file transfer screen went away as well. And then I waited a few minutes and tried again, it said the same thing, but I unplugged the cable anyways and unmounted USB in recovery. The file flashed fine so I know it was not still transferring the zip file. If anyone knows what I may have done or what I may be able to do to fix this let me know. I just wanted to update the thread with my most recent trials and errors in fixing it. Thanks to anyone who can guide me. I have never had issues with adb before.
O man i really hope someone can help us with this issue.
I have the same problem..
I am trying to use the path saver, and it keeps telling me device offline.
RSD lite won't even recognize it.
HELP!!!
Me too
I had the same problem... I wanted to upgrade the radio on my Bionic to the .901 load... I could not get adb to see my device.
Using Windows 7 64 bit (Ultimate).
RSD Lite would not recognize device either.
Decided "Screw it", I'll just go back to my nandroid backup... which didn't work either.... soooo... here I am.... stuck.
Off to google I went... I don't know which of these fixed it, but it is working now... here is what I did.
Found a thread that stated "run your commands from the 'C:\platform-tools' directory... so I took all of the files from the "Bionic Path Saver 1" and copied and pasted them into this directory.
Secondly, instead of just double clicking the upgrade batch file (runmebbb.bat) like I was before, I opened a DOS command shell -IN ADMINISTRATOR MODE- and ran the batch file from there.
It immediately kicked off and I was off and running.
For those of you that don't know what I am talking about, I was upgrading... using instructions from this thread:
http://forum.xda-developers.com/showthread.php?t=1433783
I hope this helps... it bugged the crap out of me... but the feeling of relief certainly makes up for it.
Well the thing is it doesn't work on windows or Linux with my bionic. I've tried various Android devices that I own and all of them work on both of my operating systems except for my bionic
Sent from my DROID BIONIC using Tapatalk
Same issu
I just installed Eclipse 2.2 on my Bionic and now i am getting the same issue. Has anyone found an answer or a fix for this? Also, does the .902 patch have anything to do with it? Any help is greatly appreciated.
Once i had this problem the only way i fixed this was by using RSDLite to flash a FXZ. Changing ROMs didnt work, nothing worked but that. It wont affect RSD reading the phone in AP Fastboot mode. Just make sure you install moto drivers and have the newest version of RSD Lite. That worked for me, now I have my adb back
Sent from my Transformer TF101 using xda premium
Are you using Safestrap recovery? If so I think that may be the issue.
Try downloading "ADB Over Wifi" from the market.
Then "adb connect iport"
The widget should show you ip/port when you activate it.
Bionic 2.2 Eclipse adb device offline
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
s.wyckoff1 said:
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
Click to expand...
Click to collapse
First of all, it automatically adds 5555 into your address so instead use
Adb connect 10.0.2.2 or whatever your ip is. And as far as not showing your device with a USB cord, try various other cables. I have over ten cables and maybe two work with my bionic. I urge you to use as many as possible before my next recommendation. This problem screwed with me for a couple months and finally i booted into fastboot mode and FXZd my phone. I booted my phone up after that and adb worked perfect. I don't know what causes this.
Sent from my DROID BIONIC using xda premium
Eventually I discovered why adb wasn't working. Apparently there was no adb daemon running. I came across this in a different thread awhile back. Once I copied it to my phone's /sbin/ directory (there was a link to the file in this post http://forum.xda-developers.com/showthread.php?t=974824) and ran adbd from a terminal I could use logcat. However it was removed everytime the phone cycles power so only a temporary fix. I was considering trying another rom instead of eclipse 2.2. It was also buggy in that when I tried to do an adb install it broke terminated the daemon.
If you're using linux I always do "sudo adb start-server"
Sent from my DROID BIONIC using Tapatalk 2
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.