Hardware is Nexus 10 tablet, 16GB, Android 4.2, kernel 3.4.5, build JOP40C. Manta v8, LJ12. Plan is to use as a device for playing locally-cached media.
Requires the following additional setup.
0. enable developer options, fastboot, adb
Go to system settings, and then “About.” With your finger, tap on the part of the screen that says “build.” Keep doing it until it says you are a developer.
Some background on fastboot.
Get new Android SDK from:
tar xvfz ../android-sdk_r21-linux.tgz
tools/android update sdk –no-ui
Needs adb to be version 1.0.31 or greater for adb sideload to work.
which lets one run the more useful tools
Get the fastboot binary from the android-tools package for Fedora 17. Ie:
yum install -y android-tools
Yay. Then, open up the android brain, ie power on the nexus 10 device, and then hold down the power and volume buttons simultaneously. You’ll eventually see the android menu: don’t panic. It’s all cool…
Got to the linux workstation, plug in usb from workstation to micro-usb on the nexus ten. Then, in a linux terminal, type:
and you’ll see something like:
where the serial number of the nexus 10 device is displayed. Contact! (See 4. re-image for adb kickstarting fastboot mode). Enter
fastboot oem unlock
And then use the volume key to toggle yes, hit the power key to restart, and volia! It kicks control back to the bootloader, restart, and the nexus 10 tablet is rooted.
Do this first, it wipes all data on the device.
3. cwmod recovery
Get file, install as
fastboot flash recovery ./recovery-clockwork-touch-188.8.131.52-manta.img
Output should look like:
sending 'recovery' (6068 KB)...
OKAY [ 0.734s]
OKAY [ 0.170s]
finished. total time: 0.904s
go to recovery, start sidecar install on nexus10 device then, on connected workstation
should output something that includes “sideload” as the status, then:
platform-tools/adb sideload Superuser-jb-4.2-fixed2.zip
and volia! Done. Re-booted into android, can select Superuser app and proceed as normal.
Get original system software factory images:
In addition, get the signed OTA zip files. For Android 4.4 Kit Kat, the mantaray OTA images.
Power off the Nexus 10, power on while holding down volume. When the fastboot menu appears, at this point can use the “fastboot” utility on a connected linux workstation to find device. To use adb, press the top right button until “start” changes to “recovery.” HIt the power button to select.
Next screen is an android down for the count, chest open, a red triangle warning. At this point, press power and volume up, to get another menu.
This menu you can toggle with the volume button. Toggle to “apply update from adb.” At this point, the “adb” utility on a connected linux workstation can find the device.
Then, plug device into linux workstation via USB, and type:
adb sideload 27xxx.signed-mantaray-KRT160-from-JWR66Y.xyz.zip
After completion, toggle restart and you’re done.
In ye olde times, one could also do something like this via punting into fastboot mode:
The screen on the Nexus 10 device turns to something new, the fastboot menu. One can also update via fast boot, doing something like:
fastboot flash bootloader bootloader-manta-mantamd03.img
fastboot -w update image-mantaray-jop40c.zip
the linux terminal will spew some info, and then it ends with:
Created filesystem with 11/33840 inodes and 4363/135168 blocks
sending ‘cache’ (10372 KB)…
OKAY [ 1.544s]
Whatever works. If you unpack the factory image and find scripts like “flash-all.sh”, these can usually be run from the attached linux workstation with fastboot to automate the process.
5. mounts and mounting
get terminal and busybox installed. Assuming Superuser app is installed, device is rooted and unlocked.
Get a terminal app. Launch said terminal app. Enter
To gain root. Superuser will ask to authorize, accept.
busybox mount -o rw,remount /
So now root is mounted read-write, as opposed to read-only.
Make mount directory:
mkdir -p /storage/share/autueuil
chmod 777 /storage/share
chmod 777 /storage/share/auteuil
Maybe use /storage/auteuil instead.??
Bluetooth pairing with a variety of devices seems to work without issue. Tried: Jawbone big jambox, Logitech tablet keyboard.
6. network mounts nfs/cifs working on device
Directions for cifs seem clear, but are not working for me. For NFS, this seems to work (make sure mount point directory exists on device.)
busybox mount -t nfs -o nolock 172.31.200.33:/Public /mnt/sdcard/auteuil
Awesome output to see:
/storage/emulated/legacy/auteuil 5496G 4599G 879G 524288
Only problem is although apps like terminal can then read the mount as normal and list directory contents, apps cannot.
So, there must be something wrong about the way it is mounted. I see 664 and groups of sdcard_rw on most volumes.
There also seems to be something odd about all apps not being able to touch (or even see) parts of storage that are very specific. Seems like only /storage/emulated/legacy/* mounts will work?
Try two. Install an app to enable adb over tcp/udb instead of USB. Start it, grant it superuser permissions. Works: ADB Konnect.
Open terminal on device, get root
adb connect localhost
connected to localhost:5555
List of devices attached
Then instead of:
busybox mount -t nfs -o nolock 172.31.200.33:/Public /sdcard/auteuil
adb -s localhost:5555 shell su root -c “busybox mount -t nfs -o nolock 172.31.200.33:/Public /sdcard/auteuil”
Then per media:
3. dnla client working, host is twonky 7.x on media server.
4. way to watch x264/ffmpeg movies
MX Player, MX Player A7 Hardware
n7, PlayerPro, Squeezebox, SqueezeDroid, etc.
CoolReads, Adobe Reader, Akido
By printer manufacturer’s app. Samsung and Epson both have apps for working with printers (Mobile Print, Epson iPrint). Connecting to networked CLP315 via nexus 10 connected to wifi worked perfectly for photos and pdfs. Printing gmail when two-factor encryption is turned on for gmail is not working.
micro -USB port on device is upside-down. No SD/micro-sd slot.