Talk:ADB Over USB (Nook Classic)
From nookDevs
Contents |
Toggle
So I keep getting an error after deamon starts. error: closed any idea how to fix this? --Jetgosch10 22:29, 12 August 2010 (PST)
-
-
It's not an actual issue, you can use adb shell, adb install, etc without issue --Poutine
- Okay thanks --Jetgosch10
-
It's not an actual issue, you can use adb shell, adb install, etc without issue --Poutine
Nice! I'm assuming we can write an app that can toggle this, like Android phones do, right? Anyway, kudos to JesusFreke! --Zyrjello 22:33, 28 February 2010 (PST)
I'm getting the following Error:
insmod: init_module '/lib/modules/g_android_adb.ko' failed (Exec format error) when I try running the insmod line in step 4.
I am using softroot 1.3. Thanks --Bartlantz 20:07, 7 May 2010 (PDT)
-- The same issue (also using softroot 1.3) --User:Ired 10:14, 25 May 2010 (PST)
-- The same issue (also using softroot 1.3) --Jonny 21:29, 14 June 2010 (PDT)
-- I also have the issue (Softroot 1.4) --JennaKitty 09:22, 1 July 2010 (PDT)
Why we need this ADB over USB?
Just wonder in what circumstances where we need this function whilst we need wifi to start with anyway?
-- At my school our wifi only allows traffic over certain ports and not the ones I need for adb. --Jonny 21:29, 14 June 2010 (PDT) -- Also plugs a big security hole of having adb via wifi on by default
Wouldn't the Nook Color SDK do all of this for you?--Emoney007 10:31, 16 January 2011 (PST)
setprop
Hello JesusFreke,
Once i do
setprop persist.adb.tcp.port 5555
to turn it on, what do i do to turn wifi back off? --Spec 19:10, 4 August 2010 (PDT)
problems getting adb over usb going
Having some problems with adb over usb. 2.4.1 softroot. I'm getting the "unable to connect to
"adb connect 192.168.0.102:5555" command is only for WI-FI. For USB, just giving adb commands. You are already connected. --Hari 11:06, 26 August 2010 (PDT)
More problems getting adb over usb going
Using latest version listed on site, everything seems to go well and all I have to do is hit Windows key + R, adb shell, and the command line opens right up with the #. However, it doesn't recognize a single command, I've tried everything. When I do adb --anything, it just says "adb: adb not found"
- First of all lets move all disussion to Talk page. Second as indicated on the instruction above once you do adb shell and get no error, that means you are successfully done. # means you are in the nook. So what exactly is the problem? And please sign your posts --Spec 17:39, 1 September 2010 (PDT)
"# means you are in the nook. So what exactly is the problem?" The problem is that I'm there. Now no command does anything, nothing is recognized and the screen is useless to me. --RandomInternetGuyYou'llNeverSpeakTo 17:50, 1 September 2010 (PDT)
- How about command ls - does that work? What are you trying to accomplish? What command are you looking for? --Spec 18:18, 1 September 2010 (PDT)
I just want to install an app but I can't seem to do it. The commands work after restarting the nook several times and connecting the usb cord. But when I do "install nookMarket.apk" it just pops up a prompt from busybox that seems to try to explain how to do it correctly, but is awful in getting me to understand it. Thank you for the help, I'm sorry about this, I'm just frustrated, --InternetGuy 18:22, 1 September 2010 (PDT)
Now we're getting somewhere. instead of typing 'adb shell', put your apk in the root of your c:\ drive. Now do windows + R and type cmd. Then assuming the name of the apk is c:\nookMarket.apk , type 'adb install c:\nookMarket.apk'. Full list of adb commands is available when you type 'adb --help' --Spec 18:27, 1 September 2010 (PDT)
- By the way if I'm not mistaken nookMarket is part of softroot so you shouldn't have to install it. Once you have nookMarket pretty much all apps can be installed via nookMarket. --Spec 18:28, 1 September 2010 (PDT)
Either way it worked, thanks, your method is much easier than what's listed. --InternetGuy
Trouble in Linux
Running Ubuntu 10.10, I created this file: /etc/udev/rules.d/51-android.rules with the included text in step one. Then I type "/etc/init.d/udev reload" into the terminal, and get the following response:
Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service udev reload
Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the reload(8) utility, e.g. reload udev reload: Operation not permitted
I can't connect to ADB over USB, since the terminal rejects "adb" as "command not found" --leo9 02:00, 8 December 2010 (EST)
@leo9 -- I've updated the page for instructions for Ubuntu 10.10. The terminal did actually tell you what to do when the reload failed (reload udev), but you do have to make sure you do it as root. Also, you'll need to cd to the folder where the adb is located, then use ./adb. --Linals 18:29, 16 March 2011 (PDT)
Deleted complaint, figured out what was wrong.... --AnjeTheNerd 19:29, 4 April 2011 (PDT)
ADB via USB for Nook Touch?
Will this method work for the nook 2e(simple touch)? I assume this device will need a different driver then then the one provided here... Crazy Jake 09:04, 18 July 2011 (PDT)