[Q&A] Ubuntu on the Transformer (eMMC install)

Search This thread

scottrod

Senior Member
Aug 15, 2008
103
8
Can an Asus Transformer running Ubuntu run Microsoft Office? I am considering getting one of these for college as my Asus G73 gaming laptop only gets like 1.5 hours of battery life, so i just need something to type on and to bring to class
 

vhda

Senior Member
Jul 22, 2011
84
16
Can an Asus Transformer running Ubuntu run Microsoft Office? I am considering getting one of these for college as my Asus G73 gaming laptop only gets like 1.5 hours of battery life, so i just need something to type on and to bring to class

Anything against LibreOffice?
 

vhda

Senior Member
Jul 22, 2011
84
16
Never heard of it, im just starting to get into the tablet market, (have had a android phone for a while though) just would prefer MS office but whatever works for typing would be nice so thanks for the suggestion!

I would advise you to install Ubuntu in your home PC, maybe in VirtualBox. Play around with it to get a feel of what you're getting yourself into. Please note that the current image for Transformer is still not fully functional, but when it is it will be something very similar, if not equal, to what you are able to experience inside VirtualBox.
 

Eutherin

Senior Member
Sep 9, 2009
61
1
You probably modified the file somehow. Please make sure /etc/network/interfaces is correct. Or better yet, re-write it.

I did that. I had it working, then restarted after i installed the like 193mb of update files it was nagging me to get, and then it stopped working :[
 

vhda

Senior Member
Jul 22, 2011
84
16
Ah, that's right. LibreOffice is Java, so it doesn't need an ARM build. I stand corrected.

And here I was thinking there were some parts that were done in C or C++. Apparently arm is the only build that does not depend on libreoffice-base, which depends on libc6. How the h**l did they do that? (Google is not being my friend today)

Anyway, learning something new every day :)
 

DanielT3235

Senior Member
Dec 15, 2010
64
7
Lincoln
Windows Flash Kit?

Here it is, the updated windows flash kit

usage:

1- Make sure to have Asus Sync installed on your PC (if u don't have it, download it here)

2- Download and extract the windows-flash-kit-v3.rar inside the Asus Sync installation folder.

3- Put the boot.img bootloader.bin recovery.img system.img ubuntu.img inside the folder and run the runme.bat.

To change between OS u will need to that the kernel via CWM, please check this

To make the touchpad working follow these steps

1- Make sure u have the Asus Sync running, your TF101 is connected and turned on in log in screen (ubuntu)

2- Run runme.bat

3- Go to ADB Menu and check if your device is recognized, if it doesnt just Kill and Start the ADB again till it recognize it

4- Go Back and enter the Dualbooting System menu

5- Go to Install touchpad support and fix conflicts with wi-fi menu then run the function 1, then 2 and so on, till the 4... if u get error's on ADB just do the step 3 again and return to the function that u were...

For those who already done this steps and changed between systems and want the touchpad back on again just do the step 3 and then go to Install touchpad support and fix conflicts with wi-fi menu then run the function 2...​

Ok, ive got them all together but i cant find the recovery.img and system.img to put inside the Asus Sync installation folder. Can you please direct me to these files? Where should they be?

Kind Regards
 

cuckoopt

Senior Member
Jul 17, 2011
59
30
Braga
Ok, ive got them all together but i cant find the recovery.img and system.img to put inside the Asus Sync installation folder. Can you please direct me to these files? Where should they be?

Kind Regards

thats the flash kit only, u will need to download the ubuntu.img, from the 1st (or 2nd, i dont know...) post... then u will need to download the rom u want (nvflash versions only!) or u can backup your current rom and then flash with that... Atm u have prime, revolver and revolution hd, but i think that prime is the only one who have a working version of nvflashd for download

---------- Post added at 01:56 PM ---------- Previous post was at 01:29 PM ----------

i remembered just now... lilstevie, i've a question for u... why this is taking so long... not that i'm on a rush... but... u know... its a lot of time without any updates... are u gonna wait for ubuntu 11.10 to be released? it looks quite nice... and most importantly it comes with an improved virtual keyboard... i think that ubuntu devs also thought about the tablets market... so.. what u have in mind?
 

DanielT3235

Senior Member
Dec 15, 2010
64
7
Lincoln
thats the flash kit only, u will need to download the ubuntu.img, from the 1st (or 2nd, i dont know...) post... then u will need to download the rom u want (nvflash versions only!) or u can backup your current rom and then flash with that... Atm u have prime, revolver and revolution hd, but i think that prime is the only one who have a working version of nvflashd for downloadQUOTE]

Thanks cuckoopt, so i the files i was missing are from the Android Rom i want to flash along with Ubuntu, such as prime?

ive already got the Ubuntu files from post one or 2.

Many Thanks!
 

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
thats the flash kit only, u will need to download the ubuntu.img, from the 1st (or 2nd, i dont know...) post... then u will need to download the rom u want (nvflash versions only!) or u can backup your current rom and then flash with that... Atm u have prime, revolver and revolution hd, but i think that prime is the only one who have a working version of nvflashd for download

---------- Post added at 01:56 PM ---------- Previous post was at 01:29 PM ----------

i remembered just now... lilstevie, i've a question for u... why this is taking so long... not that i'm on a rush... but... u know... its a lot of time without any updates... are u gonna wait for ubuntu 11.10 to be released? it looks quite nice... and most importantly it comes with an improved virtual keyboard... i think that ubuntu devs also thought about the tablets market... so.. what u have in mind?

The delay is a combination of things, 1) setting up the buildbox, 2) Uni, 3) stability.

1 is nearly done, and should be ready any moment now,

3 is looking much better since the oneiric beta2 update,

2 is the most important thing at the moment, it is coming up to the end of the 2011 university year. I have 3 or 4 major assignment pieces due over the next 4 weeks, then exams. My career is far more important than this project.

There is also a fourth reason, but that is almost meeting its mends, I was set back a little bit by the HDD in my coding box/buildbox dying on me
 

rickatnight11

Senior Member
Dec 31, 2010
210
61
2 is the most important thing at the moment, it is coming up to the end of the 2011 university year. I have 3 or 4 major assignment pieces due over the next 4 weeks, then exams. My career is far more important than this project.

School comes first. You know we all appreciate your work, especially during what must be a very stressful time in your life. Let us know, if you need anything.
 

Shuriku

Member
Oct 4, 2011
6
0
Dual boot linux windows kit

Hello all. I'm new at this so please give me your support a bit.
I need to flash my TF101 to dual boot with Ubuntu.
I've seen the instruction for windows
I've downloaded the flash kit, prime 2.0.1 and update to 2.0.2.
Now I've got:
boot.img recovery.img system.img ubuntu.img and flasher ready but I don’t know where to get bootloader.bin from. Where should I find it?
I’m impatience to start with it already.
 

cuckoopt

Senior Member
Jul 17, 2011
59
30
Braga
Thanks cuckoopt, so i the files i was missing are from the Android Rom i want to flash along with Ubuntu, such as prime?

ive already got the Ubuntu files from post one or 2.

Many Thanks!

thats right Daniel... u need the nvflash version... u can find the prime's one on prime post... it should be easy...

Hello all. I'm new at this so please give me your support a bit.
I need to flash my TF101 to dual boot with Ubuntu.
I've seen the instruction for windows
I've downloaded the flash kit, prime 2.0.1 and update to 2.0.2.
Now I've got:
boot.img recovery.img system.img ubuntu.img and flasher ready but I don’t know where to get bootloader.bin from. Where should I find it?
I’m impatience to start with it already.

as i said earlier, u find the ubuntu.img on the 1st or 2nd post, all the other files must come with the nvflash version of the rom u want... there are 2 ways to get that, just look around for prime or revolver or revolution hd nvflash version, the CWM versions wont work... the other way u can simply backup your current rom and flash ubuntu with that (note that backup wont have the bootloader.bin)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 66
    This thread is for help and support related to ubuntu on the eeepad transformer, all questions not related to development should be asked here, please be friendly and do not flame each other or I will request the thread be closed.

    Download links are in the third post.

    There is a wiki entry here that has a bit more detailed explanation. Please note though that as it is a wiki information
    quoted in there may or may not be entirely accurite.

    you will need to download an nvflashable rom, like prime.



    Please read the README before attempting this. The readme is below as well as in the kit, YOU WILL LOSE DATA.

    Download links are in the second post.


    OLiFE for the ASUS transformer
    ------------------------------------------------------------------

    (c) 2011 Steven Barker <lilstevie@lilstevie.geek.nz>

    This package should have only been linked to from xda-developers
    or rootzwiki if you got the links to this package from anywhere
    but those sites please send an email to the above email
    address with the subject: "unauthorised posts"

    DISCLAIMER
    ------------------------------------------------------------------

    Steven Barker (lilstevie) nor anybody will take any responsibility
    for any damage, data loss, fire, death of a loved one, or loss of
    data resulting from using this mod for your device. Using this mod
    may void your warranty.

    NVFLASH
    ------------------------------------------------------------------

    nvflash is the intellectual property of nvidia, and remains the
    property of nvidia. Any questions or queries regarding the usage
    and licence of nvflash should be directed to nvidia.

    abootimg
    ------------------------------------------------------------------

    abootimg is by Gilles Grandou <gilles@grandou.net> and is
    unmodified. The source is available from online at
    http://gitorious.org/ac100/abootimg

    usage
    ------------------------------------------------------------------

    Usage has changed since the release of the last kit, please read
    these instructions carefully, as the install method is a little
    more complex, (but easier once you use it).

    If you downloaded OLiFE.tar.gz you will need to inject the android
    rom and ubuntu image. You can use any nvflashable rom with this.
    I recommend that you use prime as that is the configuration that
    I have tested myself, and the ROM that I support for use with this
    device. You can download the ubuntu image from
    http://lilstevie.geek.nz/ports/ubuntu.img.gz.

    If you downloaded OLiFE-Prime-Edition.tar.gz you will not need to
    download the ubuntu image or an nvflash rom as they are seeded into
    the image.

    Install instructions:

    1) Download the specific flavour of OLiFE that you want to use, and
    extract it with "tar xvf <filename>".

    2) If needed inject android rom and ubuntu image.

    3) From the directory that OLiFE was extracted in run the main script
    with the command ./OLiFE.sh.

    4) Read the text that comes up and answer the question it asks.

    5) Follow the menu to the option you want (below is a breakdown of
    what each menu item is) and follow the instructions prompted. (also below
    is instructions on how to get into the modes requested).

    Menu items:

    1) Backup Menu:

    1) Full Backup (stock)
    - Full backup (stock) takes a full backup of a stock
    android system. This gives you an option to also back
    up your user data(this will take a while).
    2) Full Backup (ubuntu)
    - Full backup (ubuntu) takes a full backup of a system
    that dualboots android and ubuntu, this backs up your
    system, and the ubuntu image. This gives you an option
    to also back up your user data(this will take a while).
    3) User data only
    - This backs up the user data partition on your device.
    (This option takes a while)
    4) Android ROM
    - This option backs up the android system only. This
    option generates all the files (minus bootloader, and BCT)
    required to flash a rom via nvflash.
    5) Ubuntu Install
    - This option backs up the ubuntu install on your device.
    2) Flash Device:

    1) Dualboot:
    - This option will install ubuntu to your device in a
    dualbooting configuration with android. During the
    installation process it asks you which OS you would like
    to boot by default.
    2) uboot (linux only):
    - This option will install ubuntu with u-boot and the
    ChromeOS kernel that supports acceleration. This option
    is currently unavailable, but should be available soon.
    3) asus boot (linux only):
    - This option will install ubuntu with the asus bootloader
    with this configuration you will use all the eMMC for ubuntu
    and there will be no android system installed on your device.
    4) stock:
    - This option will partition the device in a stock way and
    install the android system that is in ./images. Use this
    option if you no longer want ubuntu on your device.
    3) Update Device:

    1) Android Kernel:
    - This option will update the android kernel on your device
    with the boot.img from ./images/. This allows you to install
    your own kernel on the device for android rather than the one
    that comes with your chosen rom.
    2) Ubuntu/Linux Kernel:
    - This will update the ubuntu kernel on your device to the version
    included in this flashkit. This option is for updating just the
    kernel with nvflash rather than using the blob method. This method
    is also good for if you flash a bad ubuntu kernel to the device.
    3) Android ROM:
    - This option will update the android rom on the device with the
    one from ./images/. This is good for if the ROM you use is updated
    or you would like to change ROMs and there is an nvflash image for it.
    This option does not destroy your data.
    4) Ubuntu Rootfs:
    - This will update your ubuntu image on the device. This is destructive
    to data stored in the ubuntu image.
    5) Advanced (Unsupported):
    - Any option in this menu is not supported and should be considered
    unstable. There may be bugs in these options and they are not maintained
    at this point in time.

    1) Flash ChromeOS Kernel (Primary Boot):
    - This option will flash the ChromeOS kernel to the primary boot
    partition. This option may not currently work in it's current
    configuration.
    2) Flash ChromeOS Kernel (Secondary Boot):
    - This option will flash the ChromeOS kernel to the secondary boot
    partition. This option may not currently work in it's current
    configuration.
    3) Update Uboot Partition:
    - This option will update the u-boot boot partition that u-boot
    reads the kernel and boot script from. This option does work if
    you have installed u-boot by compiling it from source and installed
    it yourself.
    4) Flash ClockworkRecoveryMod:
    - This option allows you to temperarily flash CWR to the device so
    you can update the installed rom. It backs up the current kernel in
    the recovery kernel position and then flashes CWR. When you have finished
    using CWR you then push any key and put the device back in APX mode and
    it will restore the kernel that was in that position. (This only works if
    android is your primary boot option at this time).

    4) Inject Firmware:

    1) Bluetooth firmware (default install):
    - This option will inject the Bluetooth firmware from the
    android ROM located at ./images/ in to the ubuntu of your
    currently running system.
    2) Bluetooth firmware (CrOS Kernel):
    - This option will inject the Bluetooth firmware from the
    android ROM located at ./images/ in to the ubuntu of your
    currently running system and flashes the proper u-boot kernel
    if you no longer need adb support.

    5) Onscreen Keyboard:
    - This runs OnBoard so that you can run through oem-config properly
    you only need to use this option if you do not have a keyboard dock
    and on the first boot.

    1) Standard Kernel:
    - This will invoke oem-config on the standard kernel installed
    on the device.
    2) ChromeOS Kernel:
    - This will invoke oem-config on the u-boot kernel that is
    installed on the device and flashes the proper u-boot kernel
    if you no longer need adb support.

    Device Modes:

    APX Mode:
    -This mode is used by nvflash to write files to the eMMC device.
    To boot in this mode you press Power and Vol-Up.

    Recovery Mode:
    - This mode is where CWR or Asus recovery normally lives, but is
    replaced by the secondary OS in the dualboot configuration.
    To boot in this mode you press Power and Vol-Down, then Vol-Up when prompted.

    Normal Boot:
    -This mode is where android normally lives.
    To boot in this mode you press the Power button until the screen turns on.
    25
    Changelog
    ------------------------------------------------------------------

    1.2a - Release name: Odyssey

    * New name for kit: OLiFE
    * New menu system
    * Updated README
    * Better handling of platform detection
    * Bluetooth support in ubuntu.img
    * Preliminary support for ChromeOS kernel
    * Preliminary support for uboot
    * Fixed touchpad
    * Fixed network manager
    * Updated to ubuntu oneiric
    * More options for flashing and updating
    * OTB Wireless support (No more injecting)
    * Smaller ubuntu.img for faster upload to device
    * Auto resizing of rootfs on first boot
    * Larger partition size (6GB) for ubuntu
    * Refactored to more easily between devices
    * Maybe something else I have missed

    1.1 - Release name: Daedalus

    * Firmware injector for BT and wifi firmwares


    1.0 and silent updates - Release name: Prometheus

    * Support for x86_64 linux distributions
    * Updated README for release on xda-developers
    * Fixes to install scripts
    * Initial Release
    8
    Multiboot by cmw.zips

    This will restore cwm on recovery partition.
    And multiboot by flashing Ubuntu.zip or Android.zip

    Create flash-recovery.sh in flashkit dir !!

    The code below wil not work unless you provide some info on witch flash mode you used !!!!!
    Like me i have selected flash-linux-android.sh,
    View it and find witch --config file it use as you can see below.

    --->--configfile ./flash/android-linux.cfg <---

    Code:
    #!/bin/sh
    nflash --bct ./images/transformer.bct --setbct --configfile ./flash/android-linux.cfg --bl ./images/bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
    nflash -r --download 5 ./images/recovery.img

    To Make this code above work replaced nflash with ./nvflash -> then sudo sh flash-recovery.sh

    Android <-- Prime 1.7 kernel !! you can select any kernel you want !!
    MD5 : 97cf64f6d5698276bde1d8657ec80cef

    Ubuntu
    MD5 : 40c9f82c30e0fd8230c712e23f2e3597
    7
    Downloads:

    RootFS md5sum(1a9fa8a698e4a96245a3c08511841eb4)
    OLiFE md5sum(c30263fd8271a23bb211fd9fdd69fa45)
    OLiFE Prime Edition md5sum(767779ccfa200e5e00b2f1e33a3d73a9)

    Sources:
    http://gitweb.lilstevie.geek.nz
    To clone the repos "git clone git://lilstevie.geek.nz/$(name of repo).git"
    6
    Simple Version

    Here's a simple nvflash package I put together to make things easy. It uses Jhinta's CWM files (incl.) and Prime 1.7. Just add ubuntu.img (from the OP) and run download-ubuntu.sh. (You'll still need to run the firmware injection script for drivers though.)

    http://www.multiupload.com/6GZSLRBP8S

    MD5: 843f964141ac96423c2fcdfc26092050