Barnes and Noble has likely introduced a new hardware revision which bricks your unit if you install their official 1.0.0 Firmware (A step needed to root). As of right now, Nooks with serial #s starting with 1003 (running firmware 1.4.1) cannot be rooted, and should NOT be attempted. See New_Hardware_Revision for more details

ADB Over USB

From nookDevs

(Difference between revisions)
Jump to: navigation, search
(Linux)
(Linux)
Line 28: Line 28:
-
3. Restart/start ADB daemon in USB mode (AS ROOT)
+
3. Restart/start ADB daemon in USB mode
-
   sudo adb kill-server
+
   adb kill-server
-
   sudo adb start-server
+
   adb start-server

Revision as of 20:01, 26 July 2010

Contents

ADB

ADB, or Android Debug Bridge is a versatile tool lets you manage the state of an emulator instance or Android-powered device.


As of NookDevs Softroot/ROM 2.4.1 (B&N:1.4.0), ADB on the nook is done over USB only by default.

This functionality was introduced thanks to JesusFreke. The source diff and relevant files can be found here.

You may need to do some extra steps in order for your ADB over USB to work.


Windows

Use the driver here: http://www.multiupload.com/AX9GWFJG95


Linux

1. put this in your /etc/udev/rules.d/51-android.rules

SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"


2. Restart/reload udev

 /etc/init.d/udev reload


3. Restart/start ADB daemon in USB mode

 adb kill-server
 adb start-server


4. You can then connect as a normal user by

 adb shell
 adb lolcat

Mac OSX

Unknown


README from initial distribution

This is a kernel module for the nook 1.4 firmware. It has support for both mass
storage devices as well as adb over usb.

Installation:
1. Overwrite the existing /lib/modules/g_file_storage.ko (on the nook) with the
version from this archive.

2. Overwrite the existing /sbin/adbd (on the nook) with the version from this
archive

3. Reboot nook

---
adb connect <your_nooks_ip>:5555
adb push g_file_storage.ko /lib/modules/g_file_storage.ko
adb push adbd /sbin/adbd
adb shell reboot
---


Once it has booted back up you can plug in the nook as per normal, and can
connect with adb, and see both exported drives.

You can eject the drives on your computer and the nook will leave the
"USB Drive Mode" and go back to the home screen. After that, you will still
be able to connect to adb as long as it remains plugged in.

The sources for this module are in drivers/usb/gadget/g_file_storage_adb.c, in
the kernel source at http://github.com/JesusFreke/nook-linux-kernel

When building the module from source, the module will actually be named
g_file_storage_adb.ko. You should rename it to g_file_storage.ko for use on the
nook. Alternatively, you could change the name of the module that gets loaded
in init.rc.

adbd was compiled from the source in the cupcake-release branch in aosp, with
a small change to make it wait for up to 5 seconds for the usb device to become
available (see adb.c.diff)

By default, you won't be able to use adb over wifi, using this module/adbd. But
if you set the persist.adb.tcp.port system property

    setprop persist.adb.tcp.port 5555

it will cause adbd to listen on the specified port so you can use adb over both
usb and wifi. Note that adb over wifi is insecure and not recommended. Anyone
on the same local network could potentially connect to your nook.

Personal tools
Google AdSense