[Q&A] Ubuntu on the Transformer (eMMC install)
- Thread starter lilstevie
- Start date
Hey guys, how can I completely remove OLiFE recovery and install CWM? I have CWM installed now, but flashing a new ROM with CWM doesn't do anything. I still boot into Prime 3.2.1 which I installed with OLiFE.
I am trying to use qemu-i386 on ubuntu on the transformer, but it keeps complaining of seg faults.
is qemu-i386 woring for anyone, am not sure if there is a problem ( tried even linaro's ppa )for qemu on ARM.
Sorry for my ignorance but is i-386 not x86 base and thats why it won't work on arm?
Sent from my Transformer TF101 using xda premium
qemu-i386 is to emulate a x86 target.
I am not sure if it is necessary to chroot at all, in that case will have to mirror yet another ubuntu img...
I am not sure if it is necessary to chroot at all, in that case will have to mirror yet another ubuntu img...
Why do you want to have qemu
ya to do some x86 but why? so there is no linux version what your looking for?most of the apps are available, but some exist only as binaries - and these are for x86 architecture. Most are not essential, but occasionally some prove to be necessary for one's work.Why do you want to have qemu
In my case, Dropbox and Acroread - the latter since it can read proprietary Adobe LiveCycle Rights Management.
and it is a nice waste of time trying to get something work. after all, this is the whole scope of such forums...
Can anyone please help me, ive installed Ubuntu months ago and i need get back to stock rom, clockworkmod seems to have gone completely, and really cant do anything, how to re-flash clockwork mod? Its not letting me thought Rom manager?
Please someone? A thank you is waiting you?
Please someone? A thank you is waiting you?
did you tr with Recovery Installer by gnufabio?
---------- Post added at 07:28 PM ---------- Previous post was at 07:13 PM ----------
did you try recovery installer by gnufabio?
http://xdaforums.com/showthread.php?t=1346180I haven't fine sir
Thanks
Hey shaola, long time no chat. I'm in the same boat as this gentleman. I want to reflash the ICS stock rom just to see what it's about, but cwm fails to actually do it. I tried with cwm, and it said it flashed successfully, but I booted the tf up and it went straight into Prime 3.2.1, the rom I installed with OLiFE.
Also, doesn't OLiFE need an image to flash? Not a zip file (like most roms come as)?
Do you know how to completely get rid of OLiFE recovery and replace it with CWM? I have cwm installed and I can boot into it, but the OLiFE recovery option to "skip wiping data and cold boot Linux" is still there.
Sent from my iPhone using Tapatalk
ASUS Transformer tf101 32gb + dock.
hi @ all,
yesterday i used olife to put ics 4.0.3 with ubuntu in dualboot on my transformer. everything works fine so far. then i tried to do a full backup with olife (backup -> ubuntu (for dualboot backup) -> android (as first rom) and whether i check personal data or not, as soon as i press "any" key after putting the tf in apx mode, the script starts nvflash, but gives me a warning:
nvflash configuration file error: file not found
and then it seemed to start the backup with the last line saying [Resume Mode]
this is the point where i can't see if he's doing anything and after half an hour i closed the terminal since there was no progress shown.
now my questions:
-should i just have waited longer?
-what will be shown while backing up?
-is the missing config file a problem? any way to solve it? (i read something a time ago where you had to adjust some path, but can't find the thread anymore)
cheers & thx in advance,
canedha
yesterday i used olife to put ics 4.0.3 with ubuntu in dualboot on my transformer. everything works fine so far. then i tried to do a full backup with olife (backup -> ubuntu (for dualboot backup) -> android (as first rom) and whether i check personal data or not, as soon as i press "any" key after putting the tf in apx mode, the script starts nvflash, but gives me a warning:
nvflash configuration file error: file not found
and then it seemed to start the backup with the last line saying [Resume Mode]
this is the point where i can't see if he's doing anything and after half an hour i closed the terminal since there was no progress shown.
now my questions:
-should i just have waited longer?
-what will be shown while backing up?
-is the missing config file a problem? any way to solve it? (i read something a time ago where you had to adjust some path, but can't find the thread anymore)
cheers & thx in advance,
canedha
Yes, Olife needs and image file instead of zip, you can (re)place the boot.img, system.img and recovery.img you want to in the images folder.
If it's easier four you you can also flash revolver by gnufabio downloading nvflashable rom and go to stock from there.
---------- Post added at 10:12 AM ---------- Previous post was at 10:04 AM ----------
Please use the web search engine, just typing your error i found it:
http://xdaforums.com/showthread.php?t=1191141&page=160
there and the first post of the next page
Last edited:
I already found and read that one, but it didn't give any answers to the problem?!?
The only hint is remove.cfg in this one line, but the other guy tried it and ran into even more problems...
did i missunderstand the posts or did i miss something?
The other problems of that guy are unrelated, so fix the .cfg thing
Hi thanks for your help and patience.
I changed the .cfg thing in the backup.sh, with the same result. Could not find config file :S
Then I saw that the Variable LAYOUT in the option I'm using is given the value android-linux and if I'm correct that the config files name that is searched for by the script adds up to android-linux.cfg, then i know why there is no file. there is simply no file with that name.
when i changed it to dualboot (which is the file that was used for creating the system with android 1 and ubuntu 2), since dualboot.cfg is in the folder, the script continued but ran into another problem somewhere.
when i read the terminal correct he SENT the bootloader.img? but then he couldnt find a file again...
i downloaded the olife package again to see if i had an corrupted/old one, but it exactly the same (version 1.2a i think)
is there a newer version or could somebody send me a working one?
or does somebody know how to fix it (if i did something wrong in my first try, probabely i have to make more changes than the one .cfg removal in backup.sh) ???
thx in advance,
toby
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
