Database Develop

SDK problems

So. I have a desktop and laptop.
The only difference between the two is that one (my laptop) is running a 64 bit OS. (win7)
I was able to install the sdk and drivers on my desktop, but not my laptop.
I use my laptop a lot more often and it would be nice to be able use it for my phone.
Any ideas?

It works, just check the guides. Where exactly are you stuck or how is it not working?

Well, it installed the drivers just fine.
But I use it (mainly) for adb and such,
which doesn't appear to be working,
and also, ddms for screenshots isn't opening.

For DDMS I used the following Java:
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=java_ee_sdk-6u1-wjdk-oth-JPR%40CDS-CDS_SMI
As for ADB, does your phone show as Android Composite ADB Device under Android Phone in the device manager?

Downloading that java now, thanks. Im pretty sure I already have it installed, but you can never be to sure. I will check the adb as soon as I find my cord. It probably DOES work, I think I've gotten it to work before, I just don't use it as often as ddms ( for some reason, my ROM doesn't let shootme and drocap to work, so I need a screenshot program )

[Q] Nook, ADB problems

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.

Need help getting market and google apps on nookie

Been at it for 2h now and i just can't seem to make it work, ive installed the latest nookie froyo on the internal memory of my nook and i just can't seem to get the market on it, i tried with a guide from http://forum.androidcentral.com/bar...ion-install-nookie-froyo-internal-memory.html
But everytime i try the adb commands i get a device not found error and i can't seem to fix this problem, i have tried to install the nook usb drivers but i still get the same error, is there any easier or other way of getting it?
Thanks
Kris

Anybody?? A tablet with no market and no youtube makes it kind of useless....

Gunner86 said:
Anybody?? A tablet with no market and no youtube makes it kind of useless....
Click to expand...
Click to collapse
Yo. nookdevs dot com ADB_Over_USB
This is my second post of eight minimum. Won't let me paste a hyperlink.
Also, scan the developement section and look for some of the market zip files for Froyo.
Once you get on the market, download ADB wireless. I find it better than ADB over USB.
NookDevs also has very good tips for Froyo and where to download what.

For some reason when you simply install JUST the install.exe it doesn't work (well it didn't for me atleast) I had to also run the DPInst64.exe since I am on Windows 7 64-Bit OS. After runing the DPInst64.exe and letting it install I was able to use ADB over USB.
If you are running a 32-Bit OS DO NOT run the DPInst64.exe - Use the DPInst.exe instead.

I had MAJOR issue getting ADB to work.
All my info came from this thread:
http://forum.xda-developers.com/showthread.php?t=910008
You really need to read and re-read this and make sure you follow the exact instructions and it will work.
The problem that caused me some issues was the USB Debugging check mark was not on. But that was a problem with Auto-Nooter 3.0, you are using Froyo.
I can confirm that once the ADB drivers are installed with Auto-Nooter, they will automatically be okay when you are in Froyo (which I am now). I did not have to redo anything.
I spent several hours uninstalling/reinstalling devices and usb ports, etc in Windows Device Manager. Both on Vista 32 bit and Windows 7 64 bit. They all work fine now simply by following that thread.

[Q] ADB Issue - device offline

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

Simple explanation to fix ADB unauthorized device in 'M'

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.