[Q&A] Ubuntu on the Transformer (eMMC install)
- Thread starter lilstevie
- Start date
thanks =)
the command is "cat /dev/zero > /dev/mmcblk0p3" but I have this message :
"cat: write error: No space left on device"
do you know what to do?
EDIT : despite the error message, it's running on android so thanks thanks thanks =D
but i have a last question
how to "reactivate" the APX mode, because my device is no longer recognized by windows or linux...
the command is "cat /dev/zero > /dev/mmcblk0p3" but I have this message :
"cat: write error: No space left on device"
do you know what to do?
EDIT : despite the error message, it's running on android so thanks thanks thanks =D
but i have a last question
how to "reactivate" the APX mode, because my device is no longer recognized by windows or linux...
Last edited:
thanks =)
the command is "cat /dev/zero > /dev/mmcblk0p3" but I have this message :
"cat: write error: No space left on device"
do you know what to do?
EDIT : despite the error message, it's running on android so thanks thanks thanks =D
but i have a last question
how to "reactivate" the APX mode, because my device is no longer recognized by windows or linux...
This error messages is expected, so all is just fine.
As for the APX...
Well as far as I know there is no way to deactivate it... You just have to shut down the tablet and reboot, holding volume up.
Sent from my Transformer TF101 using XDA
If you're having issues under Windows, try doing so under Linux. You don't need to install the drivers for it, so it's a bit easier.
If it's off, that's what you'd expect. Run 'while true; do sleep 1; sudo lsusb; done' under Linux, then plug in the TF and hold down POWER + VOL_UP. You should see Nvidia something or other appear. If you see Asus something or other, then it's detecting it but it's not in APX mode.
Just enable universe, multiverse, etc. and you're good. We don't have any specifically for the TF.
it's doesn't work, nothing happens in the loop :/
but the fact is, when my transformer is on, and plugged, nothing happen to! (i can't have access to the flash drive!)
That's why i think maybe the cable is broken, or the interface where i connect the cable damaged...
but the fact is, when my transformer is on, and plugged, nothing happen to! (i can't have access to the flash drive!)
That's why i think maybe the cable is broken, or the interface where i connect the cable damaged...
-official Adobe binary plugin for Firefox (less efficient, but seems to handle audio better)
-gnash
-lightspark (experimental)
Last 2 are in the repos (look at the browser-plugin packages), first can be found if you search the thread.
Wireless & Bluetooth
[SOLVED]
installed default dual-boot olife prime android, ubuntu 11.10 following wiki 2 days ago. works like a charm. absolutely beautiful!
except: since then trying to get wireless working in ubuntu. tried lots of variations. two different routers. open security, wep, wpa, ...; have ubuntu automatically scan (fine) and connect (breaks down), manually tried workaroung via wpa_supplicant. seems like nothings working at all.
running a laptop with freshly installed ubuntu 11.10 in parallel. automatic wireless-connections no problem. running out of ideas by now. last one: reinstall everything from scratch. might it be - if all others seem to install and have wireless out of the box - that the drivers/firmware weren't properly transferred?
thanks a lot in advance for ideas
ps: bluetooth doesn't work either. injecting firmware didn't seem to work. later it might have worked as the initial and shutdown protocol of ubuntu showed something about bluetooth. patchram /lib/firmware/... didn't work.
---
checked another wireless-network at a friends place. two different routers. worked perfectly. after a wee bit more fiddling: problem is related to a certain router (a vodafone easybox). this one as leading router/dhcp-server and nothing's working anymore.
working with transformer&ubuntu is just great. thanks a lot all.
[SOLVED]
installed default dual-boot olife prime android, ubuntu 11.10 following wiki 2 days ago. works like a charm. absolutely beautiful!
except: since then trying to get wireless working in ubuntu. tried lots of variations. two different routers. open security, wep, wpa, ...; have ubuntu automatically scan (fine) and connect (breaks down), manually tried workaroung via wpa_supplicant. seems like nothings working at all.
running a laptop with freshly installed ubuntu 11.10 in parallel. automatic wireless-connections no problem. running out of ideas by now. last one: reinstall everything from scratch. might it be - if all others seem to install and have wireless out of the box - that the drivers/firmware weren't properly transferred?
thanks a lot in advance for ideas
ps: bluetooth doesn't work either. injecting firmware didn't seem to work. later it might have worked as the initial and shutdown protocol of ubuntu showed something about bluetooth. patchram /lib/firmware/... didn't work.
---
checked another wireless-network at a friends place. two different routers. worked perfectly. after a wee bit more fiddling: problem is related to a certain router (a vodafone easybox). this one as leading router/dhcp-server and nothing's working anymore.
working with transformer&ubuntu is just great. thanks a lot all.
Last edited:
I have a sbk2 Transformer (B80*) that I've rooted. I understand I can't dual boot with Ubuntu since nvflash isn't supported, but is it possible to completely replace Android with an Ubuntu ROM? For example, by using CWM.
It is, and I will be happy to walk anyone through the steps (totally manual) if that is what they want, it does come with the disclaimer of only being recommended to advanced users, as it does involve a lot of screwing around. Come visit irc://irc.freenode.net/#asus-transformer and find me if you are interested.
I wouldn't say I'm an advanced user, but I'm not a noob either. Is it possible to 'undo' it and go back to stock ICS? I don't have anything to base "a lot of screwing around" on, so I don't know what level of risk that means. I understand all of this has some risk, but since nvflash isn't supported, I want to be somewhat sure I'm not going brick it. Is it possible to post a "cliff's notes" version (or a link) of the process so I can decide if I feel comfortable?
Regardless, thanks for the offer of help.
So I have been following this for quite sometime now and I have gotten stuck somewhere. My config as of last night was prime as default and Ubuntu 11.10 in recovery. I had heard that the TF is now supported in CyanogenMod for CM9. So I went ahead and downloaded Rom Manager and installed Clockwork. I got into CWM and installed CM9. I kinda like it but has all kinds of annoyances that make me mot want to play with it at all. I did back up Prime install but when I try to restore back to prime it just hangs on boot logo. I'm able to to get into CWM again and restore back to CM9 but not back to Prime. Could it be a kernel issue or am I over working on such a small issue. Also I have seen somewhere to install Linux kernel back in Olife thru updating kernel but I was looking for a mobile way of doing this without being strapped to my computer. Something with installing thru zipps to get Linux kernel back after CWM gets installed. I hate to redo my whole tab again with a lot of tweaks on it, on the ubuntu side.
*UPDATE*
I tried to install my stock back up and loads up fine and was able to updated to ICS. I think its a kernel issue. I may have to wait to get home and play around with updating kernels to boot up correctly.
*UPDATE*
I tried to install my stock back up and loads up fine and was able to updated to ICS. I think its a kernel issue. I may have to wait to get home and play around with updating kernels to boot up correctly.
i would appreciate also if there was a link to show how to get ubuntu on a sbkv2, even if without dual boot. However, I would have a few questions, namely:
1)is it reversible, even with a nandroid backup & restore? I could then use android for hoe, and ubuntu for when I am away
2) how far is the unlocked bootloader from asus going to take?
I had this idea of hijacking the android ssystem early on in the init.rc to boot a full linux instead of zygote, but am not sure if this is at all possible. I do not know if at this early stage in booting if it is possible to allow a user to choose, like a grub system.
thanks
stephen
Hello guys, Could anyone reupload this file to another sercvice please? Megaupload is down now
Question, is the files you looking for are the ones to flash on the tab to change/modify how the tab boots into? I was looking for something like this but couldnt find anything on this.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
66This 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.25Changelog
------------------------------------------------------------------
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 Release8Multiboot 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 : 40c9f82c30e0fd8230c712e23f2e35977Downloads:
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"6Simple 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
