Related
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
Hey guys.
Just a heads up, the Xoom can run ADB natively. Full ADB. Haven't tested it over USB Host, but it works with ADBwireless.
Doesn't seem to be documented anywhere, but it does work. Try ADB devices from a terminal on your xoom.
Meaning that the Xoom can run ADB, just like your computer. Pull APKs, ringtones, media, whatever over wifi.
EDIT: These commands should make it work without the apk.
To trigger adb wifi on your phone/non-Xoom:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
To stop adb wifi and return to USB listening:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
To connect:
Code:
adb connect [IPAddress]:[port]
For example, adb connect 192.168.1.4:5555
Or from USB on your comp:
Code:
adb tcpip 5555
adb connect 192.168.0.101:5555
To get back to USB mode:
Code:
adb usb
thats awesome thanks!
good to know thanks
you could also use adbwireless from the market to do the same thing
it's a lot easier, I think.
Yes, but some of us don't feel like paying...or just prefer command line. :]
smaskell said:
you could also use adbwireless from the market to do the same thing
it's a lot easier, I think.
Click to expand...
Click to collapse
What is included in the sdk on the xoom? I know that you can build apps from the command line on windows and linux. I think that this function would really be what I need to buy a tablet (again). Or you might be able to borrow things from the linux sdk.
Someone should take these commands and put them together into one easy to use app and launch it on the market. Many would benefit from one click type methods to natively run adb commands from the Xoom. If someone would be willing to do that of course. I'm just sayin'.
yep, weve been using the functionality for a while now!
you should also look into moto utils, which come preinstalled on the xoom and can do all sorts of funky stuff!
diablo2224 said:
Someone should take these commands and put them together into one easy to use app and launch it on the market. Many would benefit from one click type methods to natively run adb commands from the Xoom. If someone would be willing to do that of course. I'm just sayin'.
Click to expand...
Click to collapse
search "adb wireless"，you can get this awesome free app, it has a widget built-in.
and born at a bit long ago.
ftgg99 said:
yep, weve been using the functionality for a while now!
you should also look into moto utils, which come preinstalled on the xoom and can do all sorts of funky stuff!
Click to expand...
Click to collapse
So I checked out the field utils...
Apparently the Xoom has a WCDMA component? That's HSPA+ if I'm right...further supported in the iFixIt teardown.
Turned off the GSM functionality (on by default), hoping it'll save battery...not that I can complain. Battery life on this thing kicks ass.
Here's my question: Does it have an IMEI? As in can I put an AT&T SIM in there and it'll work? I'll try testing it out later. Might be time to pull out the ole' faraday cage...
schould get the commands into scripts, executable from a homescreen/the app drawer
@oshigeru YES it has an IMEI. If the AT&T Sim is on CDMA, you should have no problem to use it on the xoom, cuz i can see no restriction/branding/something on it
RinTinTigger said:
schould get the commands into scripts, executable from a homescreen/the app drawer
@oshigeru YES it has an IMEI. If the AT&T Sim is on CDMA, you should have no problem to use it on the xoom, cuz i can see no restriction/branding/something on it
Click to expand...
Click to collapse
Gscript should be able to do it.
AT&T on cdma? Lolwut?
It has an MEID that looks one hell of a lot like an imei, but I can't see an imei anywhere in the tablet. I don't know if the sim slot is active or not. (3g version.)
Sent from my Xoom using Tapatalk
I know this is an older thread but I need some direction in how to get adb in xoom to recognize my NS4G device when plugged in via usbOTG. Is it possible?
Daniel Smith1953
Jewremy said:
Hey guys.
Just a heads up, the Xoom can run ADB natively. Full ADB. Haven't tested it over USB Host, but it works with ADBwireless.
Doesn't seem to be documented anywhere, but it does work. Try ADB devices from a terminal on your xoom.
Meaning that the Xoom can run ADB, just like your computer. Pull APKs, ringtones, media, whatever over wifi.
EDIT: These commands should make it work without the apk.
To trigger adb wifi on your phone/non-Xoom:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
To stop adb wifi and return to USB listening:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
To connect:
Code:
adb connect [IPAddress]:[port]
For example, adb connect 192.168.1.4:5555
Or from USB on your comp:
Code:
adb tcpip 5555
adb connect 192.168.0.101:5555
To get back to USB mode:
Code:
adb usb
Click to expand...
Click to collapse
thanks for the info but, I can't get adb on my pc! says it doesn't exist! No idea of where to go for that. Any suggestions?
Dan [email protected]
Thank you for these commands.
Hi: I'm a long time lurker here on xda-dev, but I'm a first time rooter and this is my first time posting here.
I appreciate any help that I can get, and I will try to be as descriptive as possible so that I don't waste anyone's time. You should know that I am running OS X 10.6.7 (which is 64 bit if that makes a difference). I know that it's possible to root from OS X because I've been in contact with a fellow xda'er about his success with it and my subsequent problems. You will notice from the screenshots that I have a bootcamp partition because I plan on installing Windows 7 at some later time. I think that this may be a driver issue, but really dunno why I would have this driver problem if the person who I know has had success with OS X 10.6.7 didn't have any problems. Not sure if this matters, but I am using this sdcard: http://amzn.com/B003WGJYCY
Things that I've done that you might ask me if I've done:
-Debugging is on (I've toggled it a few times too)
-temprooted with Visionary
-Extracted the Shift file to the root of my sd card
-Checked the md5 of the file in Shift using Terminal emulator (it matches what the guide says it should be)
-Reinstalled the SDK
-Reinstalled Visionary
-Re-Extracted the 'Shift' file to my sdcard.
I am trying to root my shift following this guide : http://forum.xda-developers.com/showthread.php?t=932153
I have installed Android SDK and for have installed the packages that you can see in this screen shot: http://oi55.tinypic.com/2dvimb6.jpg
I then temprooted using Visionary: After a few failed temproots, I did get a successful temproot, which I am verified by gaining SU with the app Terminal Emulator.
I open up command prompt and do the commands that you can see in this screenshot and as you can see after ./adb shell I get "error: device not found" : http://oi51.tinypic.com/2ztcymt.jpg
As you can see, I can open adb, but the adb shell command returns an error that no device is found. I've also done this: http://oi51.tinypic.com/264t6o5.jpg
So, what do you think?
i forgot to mention that my phone is in charge only mode when I execute ./adb shell
is it connected to a 2.0 USB port?
Also have you tried restarting your phone and mac?
I also saw on another forum that Superuser had to be uninstalled then try temp rooting again.
Also are you keeping an eye on your phone while trying to gain su access? You have to click yes when it asks if you wanna give permission.
You could always try rooting via terminal on the phone. That's what I did, no PC involved.
^ Shift Faced
Thanks for your responses.
I assume these are USB 2.0 ports on my 2010 MacBook Pro. I've uninstalled superuser a couple of times, but when I use terminal emulator to check if I'm temprooted, it shows back up in my apps list.
I have never had the option of giving adb superuser permissions, but yes I have kept my eye on the phone to make sure that the phone wasn't requesting this.
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?
dubs.law said:
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?
Click to expand...
Click to collapse
That's what I did. Had been waiting for perm root so long and was so excited I couldn't stand to wait until I got home and just put the commands into terminal on the phone. Just make sure that you input all commands EXACTLY. It was recommended by others to do it from desktop so you can be sure and copy and paste the commands so as to cutdown on errors but I'm not sure why... I can copy and paste from the phone It's just kinda a pita.
^ Shift Faced
Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?
dubs.law said:
Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?
Click to expand...
Click to collapse
Nope.
^ Shift Faced
So, there is no adb commands, you just flash the "eng spl" , correct?
I rooted without a computer. Thanks!
dubs.law said:
I rooted without a computer. Thanks!
Click to expand...
Click to collapse
Awesome! I was coming on to tell you I don't really remember all the details as it was a long time ago and that I couldn't help any
Exciting doing it from the phone, right? The fear of bricking is fun
^ Shift Faced
I was to B&N today, read few books in store (on nook)
Came home, tried to connect:
adb unable to connect...
run dropbear - unable to ssh
rebooted nook via terminal
adb unable to connect...
Scratched head…
rebooted nook again via terminal
adb unable to connect...
Did basic adb troubleshooting:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb unable to connect...
stop adbd
adbd &
adb unable to connect...
netstat
showed listening (with adbd running)
127.0.0.1:5037
0.0.0.0:5555
rebooted nook via terminal
rebooted PC…
adb unable to connect...
put noogie SD, reboot, check uRamdisk – same size & timestamp
removed noogie, off/on - connected right away!
I’m puzzled…
I saw few times, after 2-3 days of reading adb is unable to connect, but reboot fixed it always.
What was different this time?
“Cold reboot”?
I spend like 30min and feel like an idiot right now…
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Adapt0r said:
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Click to expand...
Click to collapse
I did it as well before every adb connect, thought it not worth to mention.
Naturally, "rebooting PC" should reboot adb server too, right?
But it didn't help either...
If you see this issue again, just try toggling ADB Wireless On/Off and it should reset anything on the devices side. Also I've noticed that sometimes and completely random from what I can tell "USB Debugging" will get unchecked, which will mess with ADB access via USB.
Disabling/Enabling ADBwireless sometimes may help.
Maybe a stupid question: Do you have a firewall running on your pc?
digiflash said:
Disabling/Enabling ADBwireless sometimes may help.
Click to expand...
Click to collapse
won't it be the same as below or it does more?
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
digiflash said:
Maybe a stupid question: Do you have a firewall running on your pc?
Click to expand...
Click to collapse
Always
I did check it too. It was nothing worth to mention.
abd attempted to connect - got nothing back (timeout)
on NST adbd was listening, I was able to access gmail.
I can ssh neither, and dropbear was listening too.
Looks, in fact, like firewall on NST was blocking all incoming connection.
That's why I wrote "Scratched head…" - which means I checked pretty much everything.
Could somebody explain, what is the major difference for NST between:
reboot (hot reboot) & shutdown/start (cold reboot)
Or more precisely for the latter:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
ApokrifX said:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
Click to expand...
Click to collapse
Cannot connect today at all. Cold reboot doesn’t help anymore...
Did some more tests (including ADBwireless):
I cannot ping [nook IP] from my computer
I can ping [nook IP] from router.
From PC
>telnet [nook IP] 5555
Connecting To [nook IP]...Could not open connection to the host, on port 5555: Connect failed
From router:
telnet [nook IP] 5555
Connection didn’t timeout (i.e. it does connect!)
Again, looks like something on Nook blocking connections from all IP, except from default gateway (i.e. router)
Question: Does rooting process unblock connections from other IPs?
About Disabling/Enabling ADBwireless:
Before running ADBwireless
netstat
127.0.0.1:5037
0.0.0.0:5555
netstat -tapn doesn’t work
stop adbd
both above disappear from netstat
start adbd
both show up
run ADBwireless
get message: ADBwireless is off
pushed button, message changed to: adb connect [nook IP]:5555
(adb connct didn’t work)
Switch to terminal,
netstat
127.0.0.1:5037
I.e. no more: 0.0.0.0:5555
Subsequent "stop adbd"/"start adbd" changes nothing:
netstat
127.0.0.1:5037
I was wondering what ADBwireless supposed to do then?
Could somebody check from his nook what netstat shows, please?
Nook can connect to internet (gmail, market) + netstat shows all outgoing connections…
What else can I try?
I guess, I can switch to adb usb…
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Adapt0r said:
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Click to expand...
Click to collapse
One box is XP with Outpost firewall (abd set to full trust).
Another win7 (FW policy – allow outgoing connections + few exceptions).
I’m Win developer/admin and Linux(CentOs) admin.
I’m complete noob when it comes to Linux non-shell related programming.
Router runs DD-WRT.
As of now I switched to uRamdisk_1_1_rooted_usb.
When I run dropbear, I see it listening on 22, but cannot ssh still.
That’s all I guess…
Could you do one test for me please?
If your NST runs uRamdisk_1_1_rooted_wifi:
Could you ping you NST from you box
If not - could you do same from your router/AP?
1. I don't have uRamdisk_1_1_rooted_wifi on my NT and can't test it.
2. adbWireless works on my Win 7 and Mac the same way. Both comps have firewalls running and both are on the same network. I can connect and ping NT.
Just for clarification I will describe how it works on my setup:
- I start adbWireless on NT,
- it asks for root permission if it for the first time and I grant it
- then shows fat button on the screen and says adbWireless is off
- I push the button
- it says adbWireless is on, from your computer run
adb connect 192.168.15.112:5555
At this point I can ping IP address and run adb shell.
I've rooted NT for purposes of software testing and customization. I did it twice with older and newer Nooter and did not find any noticeable differences.
Let me know if you want some other tests or info.
Adapt0r said:
I can connect and ping NT.
…
At this point I can ping IP address and run adb shell.
Click to expand...
Click to collapse
To clarify (trying to get a setup as simple as possible):
We connected NST to our home wireless network and it gets IP.
We didn’t touch adbWireless yet!
Now do two tests, please:
1. From NST we ping gateway or "another device on same network", (providing it let us).
2. From "another device on same network", ping NST.
What do you get?
I thought, adbWireless just configure adbd for IP connection (as opposite for USB one) and starts it - nothing else.
If #1 works, but not #2,
and #2 starts working after you “hit adbWireless button”, than adbWireless does more then I wrote above…
Sorry, I didn't have time to do your test at home. I'll try today.
I think you are correct, adbWireless does configuration of connection by executing something like this:
Turning On:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Turning Off wifi and start listening on usb
setprop service.adb.tcp.port -1
stop adbd
start adbd
Cheers!
Edit:
Ping NST_ip_address from PC works fine.
Since I don't have terminal installed I could not test reverse pinging.
Ouch…
Just figured out:
1: I press “big red button” in adbWireless.
2: I push back button
And it pushed adbWireless into background.
If it’s the same as turning it (adbWireless) off,
it’s possible, that adbWireless reset adbd service to use USB.
Thus there is nothing listening on 5555 when I run netstat in terminal on NST.
Who’s with me?
Should be east to test:
press “big red button” in adbWireless.
I push back button
try to connect
ApokrifX said:
Ouch…
Click to expand...
Click to collapse
Updated router firmware - I can ping nook and ADB over wireless works too.
Not sure thought, if it was wireless channel problem.
I've read somewhere, some NST firmwares doesn't work on high channels or certain combined modes - like works on A+B, but not A+G
Apparently, NST firmware 1.1.2 was targeted to solve some of these issues.
PROBLEM SOLVED.
I didn't have the proper folder for the adb.exe.
-----
I have a similar problem: I recently rooted my nook simple touch with touchnooter 2.1.31, and all seems well but I can't connect to the adb wireless. IP is 192.168.0.6:5555 according to adb; I can ping from my Win XP computer if I use 192.168.0.6, but not if I add the 5555, but I just can't connect to the ereader. Wireless connections seem fine otherwise. I've tried shutting off and one the wireless adb.
I'm a complete beginner in this. On the reader, the screen has this:
"from your computer run: adb connect 192.168.0.6:5555"
This suggests that I can't simply use a firefox browser to connect? I tried using the windows cmd box, but windows indicates it doesn't know what 'adb' is. Then I found a website about adbwireless: http://theunlockr.com/2011/04/12/how-to-connect-to-your-android-device-through-adb-wirelessly/
and installed Adroid SDK Tools as indicated. When I use the cmd window, go to the proper sdk tools subfolder, and type 'adb connect 192.168.0.6:5555', windows still insists it doesn't recognize 'adb'
Please help!
try adb.exe
Meter 13,
Thanks for the reply. I added a pre-script to my op. I had created a bat file to move to the proper folder but had realized that the adb.exe had been moved to the platform-tools subfolder from its old location in the tools folder. Once I realized this, all worked well - connected to my nook, and used adb to install an apk file.
Bob
Just a note:
Ping isn't the usual TCP/UDP stuff, so there are no (port) numbers on the end.
ping 192.168.1.27
ADB uses TCP and a port number but it usually defaults to 5555
adb connect 192.168.1.27
adb connect 192.168.1.27:5555
You can also telnet to check if you can connect to the nook via TCP and port 5555
telnet 192.168.1.27 5555
(Note: If this works it will tell you that you are connected, but you can't do anything because ADB is a binary protocol.)
I had the same problem, turns out the correct drivers weren't installed. Ive downloaded HTC sync from HTC.com. I installed it and removed HTC sync afterwards. The drivers should stay there. Now reconnect your phone and try "adb devices" Before ADB wouldn't recognize my device but now it does. Tried to "adb backup -all" again, and it worked instantly.
Maybe this solves the problem?
You could try going back to a stock /boot partition.
I run my nstg rooted with the addition of about 8 files (su, xbin, busybox in system, adb wireless in /data plus a launcher) when I first root.
with the nstg, at least, I don't actually need the modified kernels - adb connects from my computers to the nstg, I simply don't have a root shell when I first connect.
This is fixed by doing an
su
once I'm in
Might be worth trying a restore of just partion 1 from your backup?
I can't find instructions on how to side load apps from OS X to my Nook Simple Touch. I rooted it using these instructions. I also installed NTGAppsAttack but it took me a while before I could log into Google and get it working. Now that it's working it doesn't seem to do much since I can't search the Google Market (probably because I can't side load apps).
First, I'm trying to install the Kindle App that I got from here. I downloaded the Android tools, but when I try to run ADB, it seems that the device isn't connected:
$ ./adb install ~/Downloads/Kindle_3.3.1.1.apk
error: device not found
- waiting for device -
I thought maybe I could load the .apk file in the Finder. There isn't enough room for me to load it onto the NookManager partition (only 8 MB free) so I put it in the My Files/Documents folder of the NOOK partition. However I can't seem to find that location using the ReLaunch app. It won't let me out of the sdcard directory.
I also tried launching ADB Konnect on the device and it tells me "Root Access Denied!"
Is it possible to install apps via SSH? I can't figure out how to get SSH running.
I'd appreciate any help. Thanks.
No idea about Macs, but for USB you will have to modify ~/.android/adb_usb.ini
Nook is not a "known" Android.
Code:
0x2080
If your root uses ADB over WiFi that would work too.