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

Search This thread
By:
Advanced…
franky1029

franky1029

Senior Member
Aug 22, 2009
104
5
How would I go about getting the kernel to get the headphone jack working?

And thank you to everyone who's gotten us this far, it's really awesome work! I hope to one day contribute myself. (Have some learning to do...)

Sent from my HTC Vision using Tapatalk
 
M

mgalyan

Senior Member
Aug 14, 2010
95
4
Ok... well...

Got my wifi boot script working.
Daily Unity updates to fix the sidebar.
Logitech cordless mouse is working perfect.
Downloading codecs from the restricted repository...

All I really want now is speakers and touchpad. I'm unfortunately not much of a coder, so I doubt I can be of any dev help, but would be glad to try.

Thanks for making this possible. We are turning tablets into beasts! :)

Edit: Having trouble getting a Flash plugin installed. Searched a few sites but all the methods lead me nowhere.
 
Last edited:
S

salamandar

Senior Member
Feb 18, 2009
298
19
At work showing off Ubuntu on my TF101, is there a way to add a 2nd wifi AP to the wpa_supplicant.conf? Something along the lines of duplicating the info with my works SSID and Key?
 
A

aligatro2010

Senior Member
May 30, 2010
361
73
lilstevie said:
flash does not exist for arm linux distributions, there are plugins which act as an intermediary service for firefox though I believe
Click to expand...
Click to collapse

It exists, but I wasn't able to make it work. This one is compiled for Armel OMAP 3430. It's actually version 9, but patched to appear as version 10. When I tried to ld <name>.so it showed me bunch of warnings maybe that's why it makes ff crash.(I placed it in the correct folder) I can get you the whole maemo rootfs for n900 if you want.

http://maemo.org/packages/package_i...u_pr1-2_armel/adobe-flashplayer/3.0.0.82+0m5/
 

Attachments

  • libflashplayer10_0_53.rar
    2.1 MB · Views: 16
Last edited:
jcarrz1

jcarrz1

Retired Recognized Developer
May 26, 2009
1,633
1,430
scienceprousa.com
your md5 is wrong for nvflash-ubuntu.tar.gz.

correct is 95eda389e64461533c51fd1e4e237a30

ubuntu.img contained inside is 43d8da14b2952c0a62302518c66707cf
 
jcarrz1

jcarrz1

Retired Recognized Developer
May 26, 2009
1,633
1,430
scienceprousa.com
the attached image might provide a little more information about the issues people are having with not executing the included bins in the linux flash kit.

look especially at the terminal output. this has been chmod +x'd and a+x'd. and same issue before and after with nautilus as well.

anyone? idk what to do either...

live usb btw, and ignore my noobishness in remembering to use sudo :{

edit, ignore the attachment its squished. BAD XDA



Uploaded with ImageShack.us
 

Attachments

  • Screenshot.jpg
    Screenshot.jpg
    39.7 KB · Views: 156
Last edited:
jcarrz1

jcarrz1

Retired Recognized Developer
May 26, 2009
1,633
1,430
scienceprousa.com
I fixed that problem by remounting my external drive where I was working with simpler permissions. just
Code: 
mount -t ntfs-3g /dev/blah4 /media/blah5
and it worked.

now, i get from the script "usb device not found"...?
 
lilstevie

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
jcarrz1 said:
your md5 is wrong for nvflash-ubuntu.tar.gz.

correct is 95eda389e64461533c51fd1e4e237a30

ubuntu.img contained inside is 43d8da14b2952c0a62302518c66707cf
Click to expand...
Click to collapse

yeah I forgot to update the md5sum here when I did the last update to the rootfs, thanks for being the only person in 5 days to actually check the md5 of your download.
 
lilstevie

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
jcarrz1 said:
I fixed that problem by remounting my external drive where I was working with simpler permissions. just
Code: 
mount -t ntfs-3g /dev/blah4 /media/blah5
and it worked.

now, i get from the script "usb device not found"...?
Click to expand...
Click to collapse

run lsusb, do you see nvidia corp on the list of attached devices?
 
franky1029

franky1029

Senior Member
Aug 22, 2009
104
5
Is there a way that we might be able to create a new 'recovery' that will give us access to Linux/Android/CWM? Or would we have to do something like incorperate the boot options into CWM?

I'm just thinking of ways that we would still be able to update our Android systems.

Since we have access to to Android partitions in Ubuntu, we could create scripts or programs through there, right?

Sent from my Transformer TF101 using Tapatalk
 
lilstevie

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
franky1029 said:
Is there a way that we might be able to create a new 'recovery' that will give us access to Linux/Android/CWM? Or would we have to do something like incorperate the boot options into CWM?

I'm just thinking of ways that we would still be able to update our Android systems.

Since we have access to to Android partitions in Ubuntu, we could create scripts or programs through there, right?

Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse

you will still be able to update, updates using blobs will still flash all the correct locations and everything, you will just need to reflash the LNX and SOS partitions back to android bootimgs before applying the update
 
E

Eutherin

Senior Member
Sep 9, 2009
61
1
I want to install this, but the whole, "gets rid of recovery mode" makes me really nervous, if my device were to somehow become bricked, how would I fix it without recovery, or am I just SoL with a $600+ paperweight?
 
blk_jack

blk_jack

XDA Labs & Feed Dev/RD
Jun 7, 2010
3,307
11,443
Toronto
The same way you flashed on recovery in the first place - nvflash

Sent from my HTC Vision using XDA Premium App
 
P

pim

Senior Member
Mar 22, 2006
125
1
Thionville
Can't make the wifi work !

Sorry guys but I can't make my wifi work and I become really crazy ! I've been trying for hours.
What I've done so far is copying the drivers from the android partition to the ubuntu partition. The wlan0 is shown when I type ifconfig.
Then I've creted the file : /etc/wpa_supplicant/wpa_supplicant.conf
with this conf :
Code: 
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
network={
    ssid="NETGEAR"
    psk="mydummypass"
    scan_ssid=1
    proto=WPA
    key_mgmt=WPA-PSK
}
After this I did what is in post #118 :
Code: 
auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
added in my /etc/network/interfaces
Then I've rebooted my system and I still can't connect . My Wifi network is encrypted in WPA without mac filtering.

ifconfig :
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:31 errors:0 dropped:0 overruns:0 frame:0
TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2618 (2.6 KB) TX bytes:2618 (2.6 KB)

wlan0 Link encap:Ethernet HWaddr 44:a7:cf:9d:ae:19
inet6 addr: fe80::46a7:cfff:fe9d:ae19/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:58 (58.0 B) TX bytes:11820 (11.8 KB)

wlan0:avahi Link encap:Ethernet HWaddr 44:a7:cf:9d:ae:19
inet addr:169.254.8.82 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

Any help is welcomed :)

Another question : is it possible to install linux mint instead of ubuntu (ubuntu based os)
thanks
 
jcarrz1

jcarrz1

Retired Recognized Developer
May 26, 2009
1,633
1,430
scienceprousa.com
I'm done with Ubuntu, so the script I want to use is the 2nd to last one or the last one? What is blobsbegone and does it work with clockwork flash able roms that are in blobs (at least I think they are, like prime non-nvflash and revolver)

Or do I just want the last one that's factory reset essentially? And after the script that's appropriate, how do I get cwm back on again? Thanks
 
I

icow

Senior Member
Mar 11, 2010
90
0
when will we have a windows flash it as i have o idea how to use linux so im leaving it well alone
 
You must log in or register to reply here.

Similar threads

EpiphanyMachine
[HowTo] Native Ubuntu - Post Install Questions Here not in [DEV]
Replies
92
Views
67K
E
eLar19
I
[Q] How To Install WhatsApp On A Wifi Only Asus Transformer?
Replies
27
Views
67K
O
osabor
B
[Solved] MTP for WinXP - A service installation section in this INF is invalid
Replies
40
Views
202K
I
istvan_06
M
[Q] Bricked Transformer
Replies
548
Views
70K
E
enriquekit
E
[Q] Asus transformer won't turn on :(
Replies
38
Views
64K
G
Grantf44

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 66
    lilstevie
    lilstevie
    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.
    View
    25
    lilstevie
    lilstevie
    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
    View
    8
    Jhinta
    Jhinta
    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
    View
    7
    lilstevie
    lilstevie
    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"
    View
    6
    R
    rdnetto
    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
    View

New posts