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

Search This thread

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
I just found a thread that stated the problem with nvflash in b70 is fixed and that lilstevy was part of that project also the b80 is presumed to have the same system so also unlockable does this mean I will be fine with a new eee pad?

Really want this device but want my warrenty and want it brand-new not second hand so if this is true and viable I'd rather have new :)

Sent from my GT540RR using XDA App

the solution is far from ready for the B7/8 devices, we still have a lot of work to do as ASUS/nVidia inadvertently broke something with nvflash
 

trialsrider1

Account currently disabled
Nov 10, 2010
664
279
GB
Danzano, the hd rom came out yesterday so it's still in testing. Prime is the one that's been around for a littlel while and what lots of people run. The hd one does look good though. I will be testing it as soon as I can download it.

Sent from my Transformer TF101 using xda premium
 

Danzano

Senior Member
May 21, 2011
3,075
463
Auckland
Awesome news guys

So hopefully if I buy the device should be able to do what I want to soon right?

Also news on the HD sounds good :)

Sent from my GT540RR using XDA App
 

cosine83

Senior Member
Apr 2, 2010
587
51
Las Vegas, NV
www.grathwohl.me
Not to rain on anyone's parade but if you're looking at the TF101 as a cheap netbook, there's cheaper netbooks you can load Ubuntu on much easier with much better support than spending the money on a TF101. That said, I'm really looking forward to working with Ubuntu or another ARM build of Linux on the TF101 (Slackware, anyone?).
 

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
I am putting together a build for release later a kind of "Technical Preview" if you will of oneiric. This build is not dual-boot, features acceleration to some extent, and u-boot.
 

Danzano

Senior Member
May 21, 2011
3,075
463
Auckland
Alot of netbooks are not android native they are usually dual boot with vinilla and crap battery life tf is better on battery and initial os

Lil stevy you don't plan to abandon the project anytime soon do you?

If so we have support and a great xda community screw netbooks with there OEM support xda has created better roms in spare time without the big budgets

So lilstevy if I buy this device and its unfortunately a post b70 how many weeks/months away is the nvflash unlock?

Sent from my GT540RR using XDA App
 
Last edited:

vhda

Senior Member
Jul 22, 2011
84
16
I am putting together a build for release later a kind of "Technical Preview" if you will of oneiric. This build is not dual-boot, features acceleration to some extent, and u-boot.

Will you also post source code and scripts?
I'm curious on what changes were required to get Ubuntu working.
 

Danzano

Senior Member
May 21, 2011
3,075
463
Auckland
Also is over clocking still available with dual boot and will the set CPU system scalling still work with Ubuntu or not?

Sorry for so many questions

Sent from my GT540RR using XDA App
 

residentorca

Senior Member
Jan 24, 2011
276
76
Seattle
Moto G Play
How big will the backup be?

Sent from my Transformer TF101 using xda premium

I'm assuming that the backup for dual-boot systems will require 16GB for the 16GB TF model. If you dumped the contents of the windows-flash-kit into the Asus Sync program folder as recommended, you should have at least 16GB free on that drive as that's where the backup will go.

I don't have enough free space on my Win7 primary SSD drive where Asus Sync is installed so will therefore try putting the contents of the windows-flash-kit into the platform-tools folder under android-sdk-windows, which is on a larger secondary HDD, and run the backup script from there.
 

cuckoopt

Senior Member
Jul 17, 2011
59
30
Braga
I'm assuming that the backup for dual-boot systems will require 16GB for the 16GB TF model. If you dumped the contents of the windows-flash-kit into the Asus Sync program folder as recommended, you should have at least 16GB free on that drive as that's where the backup will go.

I don't have enough free space on my Win7 primary SSD drive where Asus Sync is installed so will therefore try putting the contents of the windows-flash-kit into the platform-tools folder under android-sdk-windows, which is on a larger secondary HDD, and run the backup script from there.

That will depend on what kind of backup u do... the rom files are ~0,5GB, the ubuntu files ~4GB and media it will depend on what u have on your android...
 
  • Like
Reactions: residentorca

fonix232

Senior Member
Jun 20, 2009
1,222
735
London
Samsung Galaxy Tab S6
I am putting together a build for release later a kind of "Technical Preview" if you will of oneiric. This build is not dual-boot, features acceleration to some extent, and u-boot.

If your problem is with U-Boot to get it to dual-boot, I think I can help with it. But we will need button drivers for that (atleast GPIO-calls of it to be included in the u-boot boardconfig), and some more stuff. I think it would be pretty to go with a touchscreen enabled u-boot, and use a UI on boot to select which OS you want (currently, Android, Ubuntu, maybe MeeGo). That gives me an idea, u-boot is capable of making a basic linux setup as recovery/system management, and we could even manage to create our own partition layout on the device itself before loading the images (ofc this will need a totally unlocked partition layout, your blobsbegone should do it I think). U-Boot is capable of a lot of things ;)
 

rdnetto

Senior Member
Jul 3, 2011
317
96
Really want this device but want my warrenty and want it brand-new not second hand so if this is true and viable I'd rather have new

Using nvflash is pretty much guaranteed to void the terms of the warranty. (I haven't actually read it but I doubt it would allow it.) If need to make a claim I suggest using nvflash to restore it to the stock firmware before sending it in.

I'm not sure what NZ law is like, but many countries have statutes which prevent manufacturers from refusing to honour warranties for unrelated modifications. e.g. Asus could refuse claims relating to software, but if the screen breaks or whatever then they should still honour it.
 

Danzano

Senior Member
May 21, 2011
3,075
463
Auckland
Ok so this procedure does not touch the kernel?

So I could use clemsyn/blade's 13 with prime and Ubuntu?

Also I won't be returning it for software faults it would only be hardware say a screen defect etc and flash to stock before handing in :)

Sent from my GT540RR using XDA App
 

cuckoopt

Senior Member
Jul 17, 2011
59
30
Braga
Ok so this procedure does not touch the kernel?

So I could use clemsyn/blade's 13 with prime and Ubuntu?

Also I won't be returning it for software faults it would only be hardware say a screen defect etc and flash to stock before handing in :)

Sent from my GT540RR using XDA App

u can run prime with clemsyn/blade's 13, but not ubuntu
 

Danzano

Senior Member
May 21, 2011
3,075
463
Auckland
Ok I just found the tf I'm looking for I think

Model number TF-1b1800a

Is this pre b70?
This is the model I want right?

Also is there anyway we could find away to have the o/c kernel with dual boot or is it impossible?

Update just confirmed its a B60 gonna put it on hold at store buy next week or so :)

Sent from my GT540RR using XDA App
 
Last edited:

nextract

Member
Sep 25, 2008
21
0
Flash

I downloaded the libflashplayer.so file, im just wondering if anybody has had any success getting flash to work on Ubuntu, everything else works, so flash is just the missing component at the moment...

Any advice would be greatly appreciated. I also tried the opensource alternatives literally no joy with those at all.

Thanks!
 

cuckoopt

Senior Member
Jul 17, 2011
59
30
Braga
I downloaded the libflashplayer.so file, im just wondering if anybody has had any success getting flash to work on Ubuntu, everything else works, so flash is just the missing component at the moment...

Any advice would be greatly appreciated. I also tried the opensource alternatives literally no joy with those at all.

Thanks!

My personal advice is just for u to wait... a few more days (i hope so) and an update will be released... so... just wait... i think that this new update will come with a bunch of new comparabilities and accelerations...
 

nextract

Member
Sep 25, 2008
21
0
My personal advice is just for u to wait... a few more days (i hope so) and an update will be released... so... just wait... i think that this new update will come with a bunch of new comparabilities and accelerations...

ok great, will do and btw i have a B70 and i have no problems with nvflash im not sure what all this stuff about nvflash being broken on B70's is I have two and i have flashed them both without an issue....

Sent from my Transformer TF101 using XDA Premium App
 

rdnetto

Senior Member
Jul 3, 2011
317
96
Ok so this procedure does not touch the kernel?
As I understand it, all the methods so far swap out the kernel when changing the bootloader. Ubuntu doesn't work with a regular Android kernel.

Also is there anyway we could find away to have the o/c kernel with dual boot or is it impossible?

Dual boot has already been achieved, though it's kinda clunky compared to the uboot solution that's being worked on.

OC can be done under Android, since there are Android kernels for that. The Ubuntu kernel doesn't support it right now, and AFAIK no-one is working on it - wifi, hardware acceleration, etc. are more important

Model number TF-1b1800a

Is this pre b70?
This is the model I want right?
You need to look at the serial number. It will begin with B70 or whatever the revision is. The serial number is printed on a sticker near the propriety connector.
 

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