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

Search This thread

rdnetto

Senior Member
Jul 3, 2011
317
96
yeah, it is a change in the way the ramdisk is handled, it is specific to jhintas initrd for some reason
OK, so how do I get an initrd that works with your kernel? Is there some script or command I need to run?


thank you.
what is the tool to use for creating a full backup ? (is it nandroid or something else ?)
also, what shall I use for resizing the partition ?

I have :
system.img
data.img
cache.img
on my nandroid backup...

Ok, that should be fine. Run the flash kit, then restore the nandroid backup and you should be fine.

I don't know if you'll need to resize the partition file, since I'm not familiar with how nandroid works. Try it without the resizing and see if it works.
In case you do, here're the instructions:
Use resize2fs then dd to create a copy of the file without the uneeded zeros at the end.
e.g. if you've used resize2fs to reduce it to 4 GB, then 'dd if=original.bin of=smaller.bin bs=1G count=5' (while you probably only really need count=4, I prefer to go a little over in case there's some overhead).
Note that once the file has been restored to the transformer it'll only be 4GB until you use resize2fs under Ubuntu to expand it to fit all available space. This can be avoided by only shrinking it to the new size of the partition instead of the smallest possible size, but increases the amount of time it takes to restore the backup.

(This has to be done under Linux because Windows doesn't understand Linux filesystems).


i need help with the wpa supplicant, ive tried to do this and i saw a guise for transformer ubuntu, but it was the wrong format, can anyone give me a sudo command or something that will work? the connection i have is a wep

I'd suggest upgrading to WPA since WEP is extremely insecure, but here're some general instructions on wpa_supplicant and here's an example of how to do wep.
 
  • Like
Reactions: mrmrmrmr

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
OK, so how do I get an initrd that works with your kernel? Is there some script or command I need to run?




Ok, that should be fine. Run the flash kit, then restore the nandroid backup and you should be fine.

I don't know if you'll need to resize the partition file, since I'm not familiar with how nandroid works. Try it without the resizing and see if it works.
In case you do, here're the instructions:
Use resize2fs then dd to create a copy of the file without the uneeded zeros at the end.
e.g. if you've used resize2fs to reduce it to 4 GB, then 'dd if=original.bin of=smaller.bin bs=1G count=5' (while you probably only really need count=4, I prefer to go a little over in case there's some overhead).
Note that once the file has been restored to the transformer it'll only be 4GB until you use resize2fs under Ubuntu to expand it to fit all available space. This can be avoided by only shrinking it to the new size of the partition instead of the smallest possible size, but increases the amount of time it takes to restore the backup.

(This has to be done under Linux because Windows doesn't understand Linux filesystems).




I'd suggest upgrading to WPA since WEP is extremely insecure, but here're some general instructions on wpa_supplicant and here's an example of how to do wep.


can you post the bootimg that you are having issues with
 

mrmrmrmr

Senior Member
Jan 14, 2007
2,552
257
Ok, that should be fine. Run the flash kit, then restore the nandroid backup and you should be fine.

I don't know if you'll need to resize the partition file, since I'm not familiar with how nandroid works. Try it without the resizing and see if it works.
In case you do, here're the instructions:
Use resize2fs then dd to create a copy of the file without the uneeded zeros at the end.
e.g. if you've used resize2fs to reduce it to 4 GB, then 'dd if=original.bin of=smaller.bin bs=1G count=5' (while you probably only really need count=4, I prefer to go a little over in case there's some overhead).
Note that once the file has been restored to the transformer it'll only be 4GB until you use resize2fs under Ubuntu to expand it to fit all available space. This can be avoided by only shrinking it to the new size of the partition instead of the smallest possible size, but increases the amount of time it takes to restore the backup.

(This has to be done under Linux because Windows doesn't understand Linux filesystems).

Please excuse me if I'm sounding too novice.
I didn't understand how this works; how will I know which partition file to resize (if it needs to be resized) ?
How can I understand if nandroid needs resizing before I restore ?

Also, I have a few questions before doing that operation and taking the risk of losing my Android ROM:
1. how shall I update Android rom once I have dual boot ? (How to gointo recovery)
2. is there a windows toolkit to use under Windows ? (I only have Linux setup under my VMware environment, would that work with the Linux toolkit ?)
3. Once I have Ubuntu running, shall I be able to upgrade to latest Ubuntu (11.10) ?

Thank you sir...
 

rdnetto

Senior Member
Jul 3, 2011
317
96
if that is a boot.img it is amazing it even goes that far, the bootimg is fubard
Odd, I just used abootimg with the same commands as in the flashkit. We are talking about the file inside zip, right? I ran it on the netbook, but it shouldn't make that much difference...
I've been using the latest copy of abootimg from the git, so I don't think it's that..


Please excuse me if I'm sounding too novice.
I didn't understand how this works; how will I know which partition file to resize (if it needs to be resized) ?
How can I understand if nandroid needs resizing before I restore ?

Also, I have a few questions before doing that operation and taking the risk of losing my Android ROM:
1. how shall I update Android rom once I have dual boot ? (How to gointo recovery)
2. is there a windows toolkit to use under Windows ? (I only have Linux setup under my VMware environment, would that work with the Linux toolkit ?)
3. Once I have Ubuntu running, shall I be able to upgrade to latest Ubuntu (11.10) ?

Thank you sir...
0. If none of the files are >5GB, just skip the resizing step. If they are, the biggest is the one to resize.
1. Recovery/CWM works the same as always. It's actually used as an (interim) boot manager.
2. There's a Windows flashkit, and you can use the copy of nvflash included to do backups, etc. if you convert the .sh files into .bat ones. (This is only possible for simple scripts like the backup.)
I'd suggest trying to make it work with the Linux one though (either through the virtual machine or with a live CD) since I had no end of problems getting the drivers for nvflash to work under Windows.
3. You can, though I haven't tried it. To be perfectly honest, you're probably better off just installing 11.10 now. To do so, create an image with rootstock and use it as the root filesystem. After that run the driver injection script, get wifi working, then run 'apt-get install ubuntu-desktop'. (alter as required if you prefer a different desktop environment). Keep in mind you'll need to do all that in the terminal, since until you install it there won't be a GUI.
Alternatively you could use the official rootfs for Tegra 2 systems. That would be a lot easier, but AFAIK no-one's tested it with the transformer yet. Since there are some differences between the systems, I don't know how that would turn out.

For reference, here's the command to create a new root filesystem:
Code:
sudo rootstock -f TF101 -l user -p mypassword --seed build-essential,openssh-server,nano,aptitude --imagesize 8G --components main,restricted,multiverse,universe --notarball -m http://ports.ubuntu.com/ubuntu-ports -d oneiric
 
  • Like
Reactions: mrmrmrmr

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
Odd, I just used abootimg with the same commands as in the flashkit. We are talking about the file inside zip, right? I ran it on the netbook, but it shouldn't make that much difference...
I've been using the latest copy of abootimg from the git, so I don't think it's that..

yeah that was a mybad, was using the wrong tool, however I can confirm that your initrd is buggered
Code:
lilstevie@lilstevie-VirtualBox:~/android_linux$ file initrd.img.gz 
initrd.img.gz: gzip compressed data, from Unix, last modified: Tue Jul 26 14:04:33 2011
lilstevie@lilstevie-VirtualBox:~/android_linux$ gunzip initrd.img.gz 

gzip: initrd.img.gz: unexpected end of file
 

rdnetto

Senior Member
Jul 3, 2011
317
96
Code:
lilstevie@lilstevie-VirtualBox:~/android_linux$ gunzip initrd.img.gz 

gzip: initrd.img.gz: unexpected end of file
Ah, so that's how you test it. My original copy of the initrd had gotten corrupted (not sure how), which explains why none of my attempts were working. Redownloading the flashkit fixed it. Thanks for that.
 

mrmrmrmr

Senior Member
Jan 14, 2007
2,552
257
Odd, I just used abootimg with the same commands as in the flashkit. We are talking about the file inside zip, right? I ran it on the netbook, but it shouldn't make that much difference...
I've been using the latest copy of abootimg from the git, so I don't think it's that..



0. If none of the files are >5GB, just skip the resizing step. If they are, the biggest is the one to resize.
1. Recovery/CWM works the same as always. It's actually used as an (interim) boot manager.
2. There's a Windows flashkit, and you can use the copy of nvflash included to do backups, etc. if you convert the .sh files into .bat ones. (This is only possible for simple scripts like the backup.)
I'd suggest trying to make it work with the Linux one though (either through the virtual machine or with a live CD) since I had no end of problems getting the drivers for nvflash to work under Windows.
3. You can, though I haven't tried it. To be perfectly honest, you're probably better off just installing 11.10 now. To do so, create an image with rootstock and use it as the root filesystem. After that run the driver injection script, get wifi working, then run 'apt-get install ubuntu-desktop'. (alter as required if you prefer a different desktop environment). Keep in mind you'll need to do all that in the terminal, since until you install it there won't be a GUI.
Alternatively you could use the official rootfs for Tegra 2 systems. That would be a lot easier, but AFAIK no-one's tested it with the transformer yet. Since there are some differences between the systems, I don't know how that would turn out.

For reference, here's the command to create a new root filesystem:
Code:
sudo rootstock -f TF101 -l user -p mypassword --seed build-essential,openssh-server,nano,aptitude --imagesize 8G --components main,restricted,multiverse,universe --notarball -m http://ports.ubuntu.com/ubuntu-ports -d oneiric

what is "driver injection script" and where can I find it ?
also where can I find rootstock ?

edit: Ok; I got rootstock. But I still don't know what driver injection script is...

problem with rootstock:

root@ubuntu:~/tf/rootfs# sudo rootstock -f TF101 -l user -p mypassword --seed build-essential,openssh-server,nano,aptitude --imagesize 8G --components main,restricted,multiverse,universe --notarball -m http://ports.ubuntu.com/ubuntu-ports -d oneiric
I: Running on a i686 machine
Your debootstrap installation does not seem to have support for the oneiric distribution
root@ubuntu:~/tf/rootfs#
 
Last edited:

rdnetto

Senior Member
Jul 3, 2011
317
96
what is "driver injection script" and where can I find it ?
also where can I find rootstock ?

edit: Ok; I got rootstock. But I still don't know what driver injection script is...

problem with rootstock:

root@ubuntu:~/tf/rootfs# sudo rootstock -f TF101 -l user -p mypassword --seed build-essential,openssh-server,nano,aptitude --imagesize 8G --components main,restricted,multiverse,universe --notarball -m http://ports.ubuntu.com/ubuntu-ports -d oneiric
I: Running on a i686 machine
Your debootstrap installation does not seem to have support for the oneiric distribution
root@ubuntu:~/tf/rootfs#

Driver injection script is in the flashkit.

Are you running rootstock on a 11.10 installation?
 

rdnetto

Senior Member
Jul 3, 2011
317
96
Regarding kernel patches, I noticed that there are a lot of error messages during bootup regarding the Apparmor 2.4 compatibility patches with the kernel from linux_kernel_TF101. This seems to fix the problem, but I'll leave it to someone who knows what they're doing to commit it to the repo.

Also, a note to anyone who uses the patched kernel: you need to disable the network manager (it's in init.d) to connect with wpa_supplicant).


Honestly, I haven't done it myself - that's just what I'd try. I can't imagine that running a live cd image would take too much effort though.
 

mrmrmrmr

Senior Member
Jan 14, 2007
2,552
257
ok; I've downloaded a vmware image for 11.10 and it's working now.
installed rootstock and creating rootfs with the command you've suggested.

I assume the output of this will be an ubuntu.img file to be used with the toolkit and I won't need to use the ubuntu.img given in the first/second post of this thread ?

about the driver injection script, which file is that ?
inject-firmware.sh ?

when shall I run it ? in APX mode juyst after the flashing of Ubuntu ?

edit:
this is an 8GB image , will it fit ?
-rw-r--r-- 1 root root 8589934592 2011-10-23 15:54 qemu-armel-201110231514.img

wtf ?
Code:
sending file: ./images/system.img
/ 536870912/536870912 bytes sent
./images/system.img sent successfully
./images/ubuntu.img is too large for partition
command failure: create failed 
root@ubuntu:~/tf/toolkit#
 
Last edited:

mrmrmrmr

Senior Member
Jan 14, 2007
2,552
257
After sending the system.img , the script hangs on sending ubuntu.img :

Code:
root@ubuntu:~/tf/toolkit# ./flash-linux-android4.sh 
reading config file ./ubuntu/bootcfg/bootimg.cfg
reading kernel from ./ubuntu/zImage
reading ramdisk from ./ubuntu/initrd.img
Writing Boot Image linux.img
Nvflash started
rcm version 0X20001
System Information:
   chip name: t20
   chip id: 0x20 major: 1 minor: 4
   chip sku: 0x8
   chip uid: 0x037c7043424162d7
   macrovision: disabled
   hdcp: enabled
   sbk burned: true
   dk burned: true
   boot device: emmc
   operating mode: 4
   device config strap: 0
   device config fuse: 0
   sdram config strap: 0

sending file: ./images/transformer.bct
- 4080/4080 bytes sent
./images/transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: ./images/bootloader.bin
| 976013/976013 bytes sent
./images/bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: UBT
creating partition: SOS
creating partition: LNX
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 UBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 17 GPT please wait.. done!
done!
sending file: ./images/bootloader.bin
| 976013/976013 bytes sent
./images/bootloader.bin sent successfully
sending file: ./images/system.img
/ 536870912/536870912 bytes sent
./images/system.img sent successfully
sending file: ./images/ubuntu4.img

What is wrong with my setup ?
 

Danzano

Senior Member
May 21, 2011
3,075
463
Auckland
sending file: ./images/ubuntu4.img
[/code]

What is wrong with my setup ?[/QUOTE]

I cant see anything wrong you sure you where not just being impatient i have a quad core laptop and it still took a good 20mins to complete the transfer it is a big file and nvflash communication isnt the quickest

Sent from my tf101 using xda premium 1.59Ghz
 

mrmrmrmr

Senior Member
Jan 14, 2007
2,552
257
ok; I might be a little impatient, but the counter for sending bytes did not even show up.
in the previous step system.img is being sent and the counter goes through from 0 to 500M.
When sending of the ubuntu.img began, the counter did not start.

And I'm not using the standart rootfs; it's a self created rootfs with rootstock. So I thought there might be something wrong.
Any ideas ?
When should I expect to see the counter ?
 

rdnetto

Senior Member
Jul 3, 2011
317
96
ok; I've downloaded a vmware image for 11.10 and it's working now.
installed rootstock and creating rootfs with the command you've suggested.

I assume the output of this will be an ubuntu.img file to be used with the toolkit and I won't need to use the ubuntu.img given in the first/second post of this thread ?

about the driver injection script, which file is that ?
inject-firmware.sh ?
when shall I run it ? in APX mode juyst after the flashing of Ubuntu ?

Yes, yes, and after Ubuntu has been booted.

edit:
this is an 8GB image , will it fit ?
-rw-r--r-- 1 root root 8589934592 2011-10-23 15:54 qemu-armel-201110231514.img

wtf ?
Code:
sending file: ./images/system.img
/ 536870912/536870912 bytes sent
./images/system.img sent successfully
./images/ubuntu.img is too large for partition
command failure: create failed 
root@ubuntu:~/tf/toolkit#

You'll need to modify your .cfg file to increase the size of the Ubuntu partition. You can either use the one I posted a while ago (if you have a 32 GB drive) or read lilstevie's post on how to edit the file (it's not as simple as you'd think).

It'll take a bit less than an hour to copy, but you should see some feedback indicating that it is.
 

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