View Full Version : Faults and Failures, Installing Ubuntu on Tablet/Phone

February 21st, 2013, 09:07 PM
Currently getting error on my Nexus 7 freshly flashed with latest 4.2.2 image;

Starting new HTTP connection (1): cdimage.ubuntu.com
Download directory set to /home/Downloads/phablet-flash/95
Device detected as /sbin/sh: getprop: not found
Unsupported device, autodetect fails device
Do I need to install BusyBox in Android to get 'getprop' command?

I'm about to check net for the file and I maybe able to adb push the it. I'm also going to try booting the device for first time to see if it builds files in the process then try to flash Ubuntu's files in.

February 21st, 2013, 09:39 PM
How did you "freshly flash" it?


February 21st, 2013, 10:01 PM
How did you "freshly flash" it?


Well I had Plasma Active on it. I downloaded proper image from Google and unzipped the archive where the images were. I used fastboot to flash the partitions and all is working fine with Android 4.2.2.

February 21st, 2013, 11:24 PM
I'm now manually installing using Ubuntu, and having android tools preinstalled. My device is already OEM cracked and has ClockWorkModRecovery installed. Google to get this stage if you're unfamiliar.

Get the following files from;



Boot nexus into fastboot mode, which is from device off stage. That means holding power button and volume button at same time till you see the repair mode, not the recovery. Make sure usb in plugged in.

Now open a terminal where your files downloaded to and do the following;

Type "fastboot flash boot ./quantal-preinstalled-boot-armel+grouper.img"

The image should flash the boot partition. Once done use the controls (vol +/-) to select recovery mode and then press the power button to choose. You should boot into recovery mode.

Now select 'install zip using sideloader' option. Now you can send the files;

Type "adb sideload ./quantal-preinstalled-phablet-armhf.zip"

Wait for device to work on the zip then do sideload for;

Type "adb sideload ./quantal-preinstalled-armel+grouper.zip"

Now if you reboot you should have the goods. Enjoy!

Known problems:

Sometimes devices are blocked on Ubuntu from detecting on the USB. You'll need to add a rule line to the exceptions;


add lines if not there;

# fastboot protocol on the grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="default"

# mtp protocol on the grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0600", OWNER="default"

# adb protocol on the grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="default"

# adb protocol on the grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0600", OWNER="default"

You can 'lsusb' to get the vendor id and product id, if your device isn't supported in the list!

February 21st, 2013, 11:52 PM
I'm now manually installing using Ubuntu

Why would you do that?

The "Touch Developer Preview Tools" did the job quiet well for me
after figuring out that you don't need to boot the device in recovery mode but just plain an simply running android.
Took me an hour until i found out why adb could not work that way :P.

Tomorrow i want to figure out how to get a working dualboot system.
Here you have some information about it (http://forum.xda-developers.com/showthread.php?t=2011403) but i couldn't get it working yet with the tablet version.
Though the Desktop version of Ubuntu ran fine aside Android.


July 5th, 2013, 02:38 AM
I rooted my brand new nexus 4, to install the ubunto phone and then a followed these steps https://wiki.ubuntu.com/Touch/Install and in step 4, after the Ęphablet-flash -bĘ, it started to get ubuntu phone, and then this massage appeared

Error while executing adb push /home/gustavo/Downloads/phablet-flash/ubuntu-touch/20130704.2/saucy-preinstalled-touch-armhf.zip /sdcard/autodeploy.zipMake sure the device is connected and viewable by running 'adb devices'
Ensure you have a root device, one which running 'adb root' does not return an error

and then the phone don┤t start any more, get stuck in these screen
and get stuck in these screen.

July 7th, 2013, 05:28 PM
That dropbox album appears empty.
Anyway when one of my flashes failed I sideloaded android to fix my device.
Don't remember the exact steps, I just googled sideloading.