Hey everyone,
Is there an ADB Wireless for the Droid 2 as well? I tried the good ol adbwireless but it doesn't seem to work as it returns port 0.0.0.0:55 and it never recognizes that the wifi is already on. Tried downloading an older version and still unsuccessful.
Are there any functional ones? And also, I tried running the adb connect ip: code on cmd and it came back as adb is not recognized as an internal, etc...
Edit: Or is even anyone having troubles with the app at all or is it just me?
Im running 1.4.1 on my droid 2 and it works just fine.... dunno what the problem is... you have tried uninstalling and reinstalling right? If it comes down to it pm me with your email or dropbox or whatever and ill pull a copy of mine for ya to try
Weird cause I downloaded mine from the market and it seems as it should be the one just fine, don't get why I am not getting a network IP like normally would.
Related
It's probably just because I HAVENT USED IT IN AGES...but I have the USB driver package installed in my sdk and I guess I forget where to go from there. It works fine on my XP...I believe I'm missing the Nexus one drivers that usually install automatically but they aren't...am I?
Please and thank you for the help. I hate change :]
couldnt get adb to work on my win7 either, for some reason qtadb works perfectly, so if that suits your needs i would just use that.
Hm Ok it just keeps saying connect your phone. Could it be because I'm missing the nexus one drivers? Because they wouldn't install when I plugged my N1 in.
Ok I've researched this to death and tried in on both Windows 7 and osx 10.6.6 to attach using adb and install a couple of .apk's and the same thing happens on both platforms - NOTHING :-(.
You would think this would be pretty basic, but I am missing something somewhere.
Summary:
1. Am running the stock rooted b&n rom.
2. Can access both the internal and SD cards on the nook on both windoze and
osx. Eliminates cables, drivers etc...
3. Debug is selected in the nookstools settings
On both OSX and Win 7 installed the latest version of the Android SDK - both installs provided me with the platform-tools directory from which I will initiate all adb commands. So far so good...
on mac: ./adb devices returns:
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
$
As you can see I never get any device information returned, does not matter if Im on Windows or mac - same response.
Just for grins I downloaded the wireless app and tried to connect adb that way...no luck...
I could go into everything that i have tried over the last 24 hours...but that would also be pointless.
Bottom line...assuming this is something simpleI am just missing. Assuming since the symptoms are the same on both platforms that the issue lies on the nook but for the life of me I cannot find it.
Assuming if I cannot figure this out I will slowly go insane..my next step is to flash either froyo or honeycomb rom and see if this helps with the problems. Of course I MUST have the market available to me or I will not b able to load any .apk's.
Hpe Im in the right place. Any guidance is GREATLY appreciated.
Love this little Nook....BG
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
YMMV, but it solved that issue fo me.
Who Swami - It Worked
Swami,
I fall to my knees and bask in your knowledge: It WORKED!
I knew it was something simple, there is not a post on the entire Internet in any forum I have ever found (and I may have searched them all!) that mentions superuser needs to be running for adb to be able to communicate with the device. I wonder if this is a nook issue only. Will test on my wife's Epic this evening and post the results tonight.
My sanity now restored I bid you all a hearty SEE-Ya!
-BG
Omg I actually helped someone!
Glad it worked for ya I'm sure you felt the same relief I did when I finally stumbled across that fix.. I was pulling my hair out for hours LOL
Thanks Once More
As was I such a simple fix you would think I would have thought about permissions on the client side , such is life and tech thats why we all hang together.
Must say I was going to purchase the iPad 2 when it came out (NEVER buy 1st gen Apple) but now I'm not so sure...LOVING my Nook.
themirthfulswami said:
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
Click to expand...
Click to collapse
I'm not sure if this is related but I *think* that what made it work for me was to freshly enable the Debugging USB mode immediately before connecting the USB cable. Maybe that also triggered the Superuser app??? It's always the small things in life that make us smile
my problem is a little different.... I have sd cards with honeycomb (no market) and froyo (market and other apps). I can see the NC in adb with both, but honeycomb shows the device offline... and adb cannot talk to it. froyo show the device online and I can use adb. Both honeycomb and froyo show up in windows too.
I can't find anything that talks about getting the NC to show online to adb.
Same Problem
I have the same problem of trying to get my nook recognized. The only thing I can see different between my setup and the instructions on NookDevs was that they said I should see Android ADB Composite Interface on my Device Manager. Mine reads Android ADB Interface.
Tried the Superuser and the USB Debugging with no luck. Just really trying to get this set up so in case I need to factory reset. Because the 8x method manually is way too hard.
Have you guys read though this thread?
http://forum.xda-developers.com/showthread.php?t=910008&highlight=ADB
it worked for me like a charm.
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
I had intermittent ADB success with my Mac. After installing the ADB Wireless app there have been no problems.
Seaweedbrain said:
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
Click to expand...
Click to collapse
nvm
i connected my nook to the back of the cpu.
for some reason, it seemed to work fine.
it read the device as online.
got the g-apps
Hi all,
I have a Macbook Pro currently setup for Android Development. Eclipse works just fine, the SDK seems to be installed correctly, and I can load up the AVD emulator just fine for testing applications.
However, when I try to plug in my EVO into my laptop, I cannot get the EVO to be recognized by ADB. I've made sure the phone is setup for USB Debugging, placing it in Disk Mode/Charge Only, tried a few ADB commands in terminal (./adb kill-server, ./adb start-server, ./adb usb) but nothing works - it just doesn't see my EVO.
I'm currently running Myn's WarmTwoPointTwo on my EVO with netarchy's kernel. On the Mac, it's the newest version of Snow Leopard with Eclipse Classic 3.6.2 with all the newest updates to the SDK.
Thanks for your help.
I had this exact thing happen to me, but on a Windows box. I had rooted a ton of EVO's, pushed files via ADB, etc. One day it stopped working. Nothing had changed, I hadn't even rebooted, the laptop had just gone to sleep. Did all the normal troubleshooting, etc.
I ended up starting an install of PDANet, which re-installed ADB, and it's worked fine since. Not sure if that's an option for Macs. The last Mac I used was one of those ones that looked like a colored TV
I've done a fresh reinstall of Eclipse, the SDK, and tried your PDANet install as well and it doesn't work with my EVO or with any other Android phone I plug into my computer.
I had the same problem earlier today too. I ended up just using adb wireless to connect my evo to adb so that's a fix you can try using too.
Sent from my GTablet using Tapatalk
Whenever I use ADB, I boot the phone into recovery, then run ADB shell from there. It's the only way I've ever been able to run it. Might be worth trying.
I have a T-Mobile G1 that I had not used for a while. I decided to upgrade it to 2.2 and have been successful (Amon_RA v1.7, Cryogen 6). However, I had to do the upgrade using the SD card and WiFi because the USB is not working. I have tried to connect on both my old XP computer that used to work with the G1 and a couple of other computers using XP and Win7 with the same results.
I get USB Device Not Recognized. When I look at the Device Instance Id on the properties screen it shows USB\VID_0000&PID_0000\5&64DAA3C&0&1 and most other entries are unknown.
My Droid X works fine so I am fairly certain this must be a problem on the G1. I don't know how the G1 manages the USB connection so any help is appreciated.
I´m having the same problem but with my Vega tablet.
When I go to properties I get te VID_0000 and pID_0000 therefore y can´t install the drivers. I´ve looked everywhere but didn´t find any solution
Try another cable? Or try and see if this one works with another phone.
Same here with my htc magic, was working fine then just stopped. I've almost given up trying to get it to connect via usb, so it'd be great to see someone give a solution
Sometimes that happens to me, I try to reboot the computer as well as the phone. What really fixed it was having another rom installed.
Got a connection briefly today, then after a fresh install of laszlo's fantastic rom its gone again! Weird!
Sent from my HTC Magic using XDA App
hmmmm... try getting the 'mountusb' apk installed and see if that works...
ldrifta said:
hmmmm... try getting the 'mountusb' apk installed and see if that works...
Click to expand...
Click to collapse
thanks, please excuse my ignorance but where might I find a safe version of 'mountusb'?
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
CrimsonSentinel13 said:
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
Click to expand...
Click to collapse
BurritoRoot causes the normal adbD to behave as an unsecure one, but if your not seeing the kindle under adb devices then you have PC side problems likely.
I figured it might be PC side. I've tried everything I could after updating the Android SDK. Updating everything with what's needed for the Fire to be seen hasn't worked. I'm a bit at a dead end for ideas... I tried even using the USB3 controller on my mobo but no luck either.
Edit: Fixed!
I uninstalled the Kindle Fire from the Device Manager & got it reinstalled. It now works perfectly with ADB. I'm in the process of rooting it as I type this.
I have the same problem.
However, I have 2 fires, one running CM7 and the other 6.2.1.
The PC recognizes the one running CM7 but not 6.2.1.
So, I don't think it is the PC.
No matter what I do, adb and fastboot, device not found.
Can not access the one with 6.2.1.
Does not show up in device manager.
I have read and try various things from xda, Rootzwili and Liliputing.
follow this video thats wht helped me get past that part ur on
http://www.youtube.com/watch?v=KapnjR89ICA&feature=player_embedded
u have to make sure u update the drive for ur kindle with the driver from sdk
this is also helpful tooo
http://forum.xda-developers.com/showthread.php?t=1409120
What worked for me was following this guide up to step 3. Then, with the device manager it launches, i deleted ALL my adb/android devices and then I let windows re-install the driver when I plugged the kindle (you may need to choose the driver manually), then I could finally access fastboot/adb via cmd..
Solved problem, Thank You.
I have many drivers on my PC, Motorola, Samsung, HTC and Android.
I noticed on one boot the Kindle was listed as Samsung Android Phone.
I uninstalled the Samsung drivers.
Connected the Kindle. All is fine.
Connected my Samsung SGS II, it found the drivers.
Crimson, thanks for sharing your fix of uninstalling then reinstalling. Worked for me.
hi, i would like to apologize in advance, i am new to adb so i'm not sure if i'm even doing it right, but i have successfully rooted and installed cm7, after much googling. i did it a while ago and used the clockwork mod method. i would like to replace it with twrp but the only way i have found to do it is by using adb or the kindle fire utility, which if i understand correctly uses adb. the only problem with that is that i can't get adb to recognize it. i'm assuming it's because i don't have the proper drivers for the "cm7 kindle" because i install them for the stock kindle. please help me. i have no idea how to fix this. thanks
edit: ok guys i'm really sorry, i'm an idiot, i forgot that i had turned off usb debugging. turned it back on, worked perfectly. again sorry.