Related
This guide was written to provide more specific information for installation instructions than the OP below.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
OP for Tubutnu by x3maniac
1. Download the newest “tubuntu v0.x.x” without Prime (system.img) or Ubuntu.img as it is written in the OP.
a. This download contains the application, boot.img file, and basic kernels available at the time of this guide needed for installation. There will be updates for kernels specific to an Ubuntu image as the developer is able to work on them. Check for new downloads and posts.
b. The download also contains drivers and installation for APX mode located using the “Other” tab in the application.
c. This download does NOT contain the Linux operating system nor the Android ROM.2. Extract all the files in “tubuntu v0.x.x” to a Tubuntu folder wherever you wish. 7-Zip is the zip program of choice but any others should work fine.
3. Download Prime ROM [stock hc w/ root](system.img)
a. This download is the system.img that contains a root enabled Android ROM.4. Extract the system.img file from this download.
a. Copy this file to the \images directory. The images directory is a sub folder of the TF-101 Ubuntu Installer application that you extracted in step 2.5. Download the Ubuntu image of your choice.
a. Currently there are 2 Lubuntu downloads. Read the bullets and determine which one you want.6. Extract the image file of this download and place it in the \images directory. Rename this file to ubuntu.img.
7. Open the TF-101 Ubuntu Installer application.
8. Connect your usb cable to the TF-101 and the computer.
a. Shut down the tablet.9. Enter APX mode by holding the volume up button first, then hold the power button until you hear the usb sound from the computer.
a. Your screen will be black and the TF-101 Ubuntu Installer application will light up green and say APX Detected if you correctly entered APX mode.10. Change the dropdown to SBK 1 located directly below the green APX Detected text.
11. Click on the Flash tab.
a. Select Android/Ubuntu and then hit Flash.
b. Android is the primary boot option here.12. You will see an install log in the right of the application. Mine takes about 15 minutes or so but you will know you are finished when you see the Android ROM load as well as the red text APX NOT Detected (in case your screen is off when you come back).
13. Proceed with setting up Android. DO NOT reboot or power off before the initial Android set up is complete.
14. Once completed and you wish to enter Lubuntu, power off the TF-101 and hold down volume down first and then power. You will see your screen say hit volume up in 5 seconds for recovery. Hit volume up within 5 seconds and it should boot your Linux graphical desktop environment.
Instructions for installing new kernels for SBK1.
1. In your Tubuntu installation directories, locate transformer.bct and bootloader.bin.
a. Copy these 2 files to the \bins directory of the Tubuntu installation application.2. Download the updated kernel from the OP.
a. Extract the .img file into the \bins directory of the installation application. You do not need to rename it because the command you enter in step 3 part b indicates the name of the kernel file.3. Open a command prompt to the directory of \bins for the Tubuntu installer application.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 6 whatever_the_kernel_filename_is.img
c. The filename is the name of the kernel you extracted and copied into the \bins directory. This name can really be anything so long as the command you enter reflects that filename.4. After the copy completes you will be back at the command prompt.
a. Type this command and hit enter: nvflash -r --go5. Your tablet will reboot after the nvflash mode is exited and depending on your configuration it will boot to Android. Boot to Linux now.
6. Download the supplemental kernel file to the root of your filesystem That is the / directory.
a. Open terminal and type this and press enter: sudo wget http://novaspirit.com/tubuntu/kernel_sup.tar.gz /
b. Then type this command and press enter: sudo tar zxvf /kernel_sup.tar.gz
c. This supplemental is installing modules and drivers to the appropriate locations.
d. Reboot.7. Please understand names of files especially the kernels and updates will change periodically. The commands and methods of extracting have not changed at this point so substitute the appropriate filename and you should be good to go.
For SBK1 devices, the installation of a custom Android ROM using recovery is very similar to updating the kernel instructions in the post above.
Instructions for installing custom ROM's for SBK1 with Lubuntu installed.
1. In your Tubuntu installation directories, locate transformer.bct and bootloader.bin.
a. Copy these 2 files to the \bins directory of the Tubuntu installation application.3. Copy the file cwrrecovery.img to the \bins folder.
a. You should be able to substitute a newer recovery file than what comes with the Tubuntu installation application.2. Download the zip file of the custom Android ROM you wish to install.
a. Copy it to either your Internal SD card or External SD card. Depending on the recovery version you flash you may not be able to use your Internal SD card.3. Open a command prompt to the directory of \bins for the Tubuntu installer application.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 5 cwrrecovery(orwhateverfilenameyourrecoveryis).img
c. The filename cwrrecovery.img is the name of the recovery that comes with the installer application. Please substitute appropriately if you are going to flash a different recovery application. You can also use TWRP just use the appropriate .img file name.4. After the copy completes you will be back at the command prompt.
a. Type this command and hit enter: nvflash -r --go5. Your tablet will reboot after the nvflash mode is exited and depending on your configuration it will boot to Android.
a. Now you want to boot to the Android recovery. Do that by powering off the tablet and booting like normal into recovery mode. This should be volume down and power. Hit volume up when prompted to do so. Flash your ROM according to the ROM owner's instructions. I recommend to complete your ROM's installation set up before proceeding to step 6.6. You must now flash your Tubuntu Linux kernel back or you will not be able to boot into Linux. Follow the instructions again from the \bins directory using the command prompt and putting your tablet back into APX mode which is volume up and the power button until the Tubutnu installation application shows green for APX Detected.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 5 whatever_the_kernel_filename_is.img
c. Type this command and hit enter: nvflash -r --go7. You should now be back into your Android ROM again. From here simply power off and boot into recovery using volume down and power. Then hit volume up when it says to on the screen. If Linux boots without issue then you have successfully reinstalled your kernel.
I did exactly what's in the post. With Tubuntu 0.4.7, Prime ROM, Lubuntu V1.1-rc1 (12.10) and the *updated kernel 12/10/2012* (without supplements)
But after Android initial boot, I reboot but it doesn't finish booting Android. It stops here:
http://i50.tinypic.com/2zswdw3.jpg
Anything I can do to fix this? Android does boot properly, but Lubuntu doesn't
If anyone knows how to fix this with only Ubuntu (and without Android) then that is fine too..
TomTcom said:
This guide was written to provide more specific information for newcomers.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
Click to expand...
Click to collapse
sainthout said:
I did exactly what's in the post. With Tubuntu 0.4.7, Prime ROM, Lubuntu V1.1-rc1 (12.10) and the *updated kernel 12/10/2012* (without supplements)
But after Android initial boot, I reboot but it doesn't finish booting Android. It stops here:
http://i50.tinypic.com/2zswdw3.jpg
Anything I can do to fix this? Android does boot properly, but Lubuntu doesn't
If anyone knows how to fix this with only Ubuntu (and without Android) then that is fine too..
Click to expand...
Click to collapse
0.4.7 fixes the issue with sbk1 and you don't have to do it with these instructions anymore.
However I did try the newer kernel and got stuck at the same spot you did using my instructions just before the 0.4.7 was uploaded. Go to the original thread and post the issue there.
Thanks for the quick reply! Will post the issues
Outdated Thread But Valid Information
This thread is now outdated. X3Maniac has updated his Tubuntu installation application (0.4.7) to fix the issues with installing kernels and recoveries for SBK1 devices.
The information in this thread is still valid for behind the scenes and you can still use the wheelie and nvflash as standalone items if you wish to do something with your device outside the scope of the main thread.
Thanks for all the thanks from users!
Found a bug with 0.4.7. It's possible the tab may not reboot into Prime automatically with this version. When the dev has time it will get updated. If it doesn't reboot and the Tubuntu application says everything is done, manually hold power and let it reboot to Prime to finish installation.
question..
TomTcom said:
This guide was written to provide more specific information for newcomers.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
1. Download the newest “tubuntu v0.x.x” without Prime (system.img) or Ubuntu.img as it is written in the OP.
a. This download contains the application, boot.img file, and basic kernels available at the time of this guide needed for installation. There will be updates for kernels specific to an Ubuntu image as the developer is able to work on them. Check for new downloads and posts.
b. The download also contains drivers and installation for APX mode located using the “Other” tab in the application.
c. This download does NOT contain the Linux operating system nor the Android ROM.2. Extract all the files in “tubuntu v0.x.x” to a Tubuntu folder wherever you wish. 7-Zip is the zip program of choice but any others should work fine.
3. Download Prime ROM [stock hc w/ root](system.img)
a. This download is the system.img that contains a root enabled Android ROM.4. Extract the system.img file from this download.
a. Copy this file to the \images directory. The images directory is a sub folder of the TF-101 Ubuntu Installer application that you extracted in step 2.5. Download the Ubuntu image of your choice.
a. Currently there are 2 Lubuntu downloads. Read the bullets and determine which one you want.6. Extract the image file of this download and place it in the \images directory. Rename this file to ubuntu.img.
7. Open the TF-101 Ubuntu Installer application.
8. Connect your usb cable to the TF-101 and the computer.
a. Shut down the tablet.9. Enter APX mode by holding the volume up button first, then hold the power button until you hear the usb sound from the computer.
a. Your screen will be black and the TF-101 Ubuntu Installer application will light up green and say APX Detected if you correctly entered APX mode.10. Change the dropdown to SBK 1 located directly below the green APX Detected text.
11. Click on the Flash tab.
a. Select Android/Ubuntu and then hit Flash.
b. Android is the primary boot option here.12. You will see an install log in the right of the application. Mine takes about 15 minutes or so but you will know you are finished when you see the Android ROM load as well as the red text APX NOT Detected (in case your screen is off when you come back).
13. Proceed with setting up Android. DO NOT reboot or power off before the initial Android set up is complete.
14. Once completed and you wish to enter Lubuntu, power off the TF-101 and hold down volume down first and then power. You will see your screen say hit volume up in 5 seconds for recovery. Hit volume up within 5 seconds and it should boot your Linux graphical desktop environment.
Click to expand...
Click to collapse
i just succeeded dual booting into ubunto.the prime rom just booted...can i install eos jb rom and still dual boot to ubuntu? thanks in advanced
Yes you can. You will need an updated recovery .img file that supports jb. You temporarily flash the new recovery boot into it then install the new rom. See my post on installing updated android roms. Its the third one I think.
oh sorry for the silly question,,i got it now thanks a lot.. nice job
Hi there,
First off, thanks for the tutorial and hard work!
I've been able to successfully install Lubuntu v1.2 and Lubuntu V1.1-rc1 but I've run into issues with both that I'm hoping you can help me with.
When I installed v1.2, my wireless adapter didn't work and I wasn't able to copy any files (kept saying I was out of space, probably a mounting issue).
When I installed v1.1-rc1, things seemed to work well (wireless worked) but when I tried to upgrade the kernel to 3.1 following the instructions, my mouse pad stopped working and so did my wireless adapter again. I saw that there is a way to fix the mouse pad but it seemed to require an internet connection. Any idea what I did wrong or how to fix the wireless on either v1.2 or on v1.1-rc1 with the 3.1 kernel?
Thanks!
You're welcome.
To solve the space issue, open terminal and execute this command: sudo resize2fs /dev/mmcblk0p8
The wireless adapter isn't working because the 3.1 kernel is not stable. Do Not Use It.
Get this from the OP:
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
Then get the supplement from the OP:
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/
TomTcom said:
You're welcome.
To solve the space issue, open terminal and execute this command: sudo resize2fs /dev/mmcblk0p8
The wireless adapter isn't working because the 3.1 kernel is not stable. Do Not Use It.
Get this from the OP:
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
Then get the supplement from the OP:
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/
Click to expand...
Click to collapse
Awesome, works like a charm. Thanks again!
Not sure if I'm the only one experiencing this, but every now and again whenever i click anywhere it thinks I'm trying to move a file (shows the little file icon when I move the mouse). Is this a known bug or just something in my settings I need to change?
Thanks!
---------- Post added at 12:40 PM ---------- Previous post was at 12:19 PM ----------
I also just found that my sound stopped working. It was working before when I used the instructions from the original post (using alsamixer) but I guess somewhere along the way of me messing around I broke it. Here is the error output when I try to play an mp3 in mplayer:
Code:
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 128.0 kbit/4.54% (ratio: 16000->352800)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==========================================================================
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
MPlayer interrupted by signal 6 in module: ao2_init
I've tried searching for a solution but still no luck. I've also tried other players and they don't work either. Any help would be greatly appreciated.
Thanks!
Treizy said:
Not sure if I'm the only one experiencing this, but every now and again whenever i click anywhere it thinks I'm trying to move a file (shows the little file icon when I move the mouse). Is this a known bug or just something in my settings I need to change?
Thanks!
---------- Post added at 12:40 PM ---------- Previous post was at 12:19 PM ----------
I also just found that my sound stopped working. It was working before when I used the instructions from the original post (using alsamixer) but I guess somewhere along the way of me messing around I broke it. Here is the error output when I try to play an mp3 in mplayer:
Code:
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 128.0 kbit/4.54% (ratio: 16000->352800)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==========================================================================
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
MPlayer interrupted by signal 6 in module: ao2_init
I've tried searching for a solution but still no luck. I've also tried other players and they don't work either. Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
See KingZaks post for sound settings. It's in the op and his signature.
The clicking shouldn't do that every time. Did you extract the supplemental zip and are you using the 1.2-1.6ghz kernels?
Hmm, I'm thinking of installing fresh to see if things get fixed. Is there a way to do that without touching the Android partition? I don't want to have to reflash EOS and what not. Do I just not include the Prime img in the images folder?
Thanks!
A Terribly Confused Noob!
Hello:
I am terribly confused and I hope that someone can help me to understand a few things! I am sorry if I don't understand all the links but they seem to go round and round. Right no I have no less that 25 tabs open trying to figure out the first step.
So, to my first question (probably the first of many): This guide was written to help "newcomers", of which I am definitely one. But, right under that statement comes the statement "The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do." Does that mean I'm actually supposed to start at Post #2? But Post #2 assumes I already have "Tubuntu installation directories", which I don't have so I can't locate the two files.
I am attempting to be a user of Ubuntu on my Transformer, not a developer - I take my hat off to all of you that have put your Transformers in harm's way developing the techniques and software that I want to use, but the instructions are terribly confusing for someone not familiar with all of the terms!
Any help would be most appreciated and I thank you in advance.
Sparky
TheArtfulDodger said:
Hello:
I am terribly confused and I hope that someone can help me to understand a few things! I am sorry if I don't understand all the links but they seem to go round and round. Right no I have no less that 25 tabs open trying to figure out the first step.
So, to my first question (probably the first of many): This guide was written to help "newcomers", of which I am definitely one. But, right under that statement comes the statement "The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do." Does that mean I'm actually supposed to start at Post #2? But Post #2 assumes I already have "Tubuntu installation directories", which I don't have so I can't locate the two files.
I am attempting to be a user of Ubuntu on my Transformer, not a developer - I take my hat off to all of you that have put your Transformers in harm's way developing the techniques and software that I want to use, but the instructions are terribly confusing for someone not familiar with all of the terms!
Any help would be most appreciated and I thank you in advance.
Sparky
Click to expand...
Click to collapse
Hey Sparky, there's no more active development on this just so you are aware. That means you can make your own images for newer Linux builds if you wish but things such as hardware acceleration and kernels will not be updated.
In step 1 of my guide you are going to the OP link by the dev who made the Windows based Tubuntu application.
Go to where you see these links:
tubuntu v0.4.7 [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.7 (jan, 3 2013)
tubuntu v0.4.6beta [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.6b (dec, 10 2012)
tubuntu v0.4.2beta [78mb] without Prime(system.img) or ubuntu.img
download v0.4.2b (dec, 7 2012)
tubuntu v0.3alpha [57mb] without Prime(system.img) or ubuntu.img
download v0.3a
Prime ROM[stock hc w/ root](system.img)
download
Download tubuntu v0.4.2beta (78mb).
Download tubuntu v0.4.7 (1mb).
Extract the files to whatever location on your Windows machine.
The 1mb file is a replacement of tubuntu.exe file. So just copy/paste and overwrite that file on your Windows machine.
Do you know how to put your tablet in APX mode? If not, you open tubuntu.exe (you might need .net 4.0 Microsoft framework to run the tubuntu.exe). With the tablet off and usb connected to your windows machine, hold volume up and power. The application tubuntu.exe should have a green indicator that it's connected. Change the dropdown to sbk1.
From there you can choose how you want to flash, such as android as the default boot and linux as the secondary boot.
Ignore.
Guide to making a Raring Ubuntu-core image on a Linux PC/laptop (NOT a virtual machine (VM)) for the purpose of installing it on your TF101.
All credit goes to the time and consideration x3maniac took to assist me with doing this!
OP for Tubutnu by x3maniac
This guide allows you to create a CORE Ubuntu image on your Linux box and then install it using the Tubuntu application for Windows. ***Please note, a CORE image does not contain a GUI. The gnome-core guide in the next link will walk you through the steps of installing the gnome-core GUI after you have made your fresh Raring Ubuntu-Core image.***
http://forum.xda-developers.com/showthread.php?p=37803357
***Why do I want to do this when the OP by x3maniac already has a Raring image for download? This guide is helping you make your own UPDATED image. There are daily builds of Raring and the image in the OP by x3maniac is over 2 months old as of this last update to this post.***
Please note that I am using a stock Ubuntu 12.10 laptop. I believe any variant of Ubuntu on a laptop or PC should work with this guide just fine.
Download the files first and then open Terminal to input our commands.
Download: http://cdimage.ubuntu.com/ubuntu-core/daily/current/raring-core-armhf.tar.gz
(You may optionally choose any date time from the Ubuntu-core folders. Ensure you are using the armhf tar.gz file.
Download (Recommended): https://www.dropbox.com/s/dqn9aa94oeju9kf/modules.tar.gz
Alternate Download: http://goo.im/dev/x3maniac/mod_firm_ext.zip
Alternate Download: http://www.novaspirit.com/downloads/mod_firm_ext.zip
After the downloads are complete, open Terminal and let’s get the image built!
A side note, I did not know that using ~ represented the user folder so if you do great, if not it will help you understand that /home/thomas can be represented using ~. So any subfolders of /home/thomas are included using the ~. I will specify my full paths and you can substitute the directories you wish to use. (Linux is still new to me too, I know enough to be dangerous!)
1. mkdir /home/thomas/images/ubuntu-raring
2. cd /home/thomas/images/ubuntu-raring
3. sudo apt-get install qemu
4. sudo apt-get install qemu-user-static
5. Now type this command: qemu-img create raring.img 200M
a.The Ubuntu Raring core image is approximately 186MB. So you understand at 186MB you only have 14MB available of extra stuff you can put into the image. You can resize up later but never down. You may specify any MB size you wish to use for the image. Experiment later, for now just make it 200M.
6. fdisk raring.img (you will see an error about invalid flag, this is ok, step 7 below is w for write, do proceed to step 7)
7. Type w to quit
8. Determine the file system you want (I used ext4)
a. Now type: mkfs.ext4 raring.img (according to config file of Tubuntu app, the partition is set up as ext3, you can use that as well)
b. A warning that your image is not a block special device (when choosing ext4) hit Y to proceed.
c. From /Ubuntu-raring directory type: mkdir mount
9. Now type: sudo mount –o loop ./raring.img ./mount
10. Now type: cd mount
10a. Now type: ls (you are only listing the mount directory to verify you have the lost+found directory) Go up one directory to /home/thomas/images/ubuntu-raring
11. Now type: cp /home/thomas/Downloads/raring-core-armhf.tar.gz /home/thomas/images/ubuntu-raring
12. Now type: sudo tar xvvf raring-core-armhf.tar.gz –C ./mount (you should not be in the mount directory)
13. Now type: sudo tar xvvf modules.tar.gz -C ./mount (you should not be in the mount directory)
14. sudo cp /usr/bin/qemu-arm-static /home/thomas/images/ubuntu-raring/mount/usr/bin (enter)
15. Now type: sudo chroot mount (if successful you will see /#)
16. Now type: passwd and make a password and confirm it.
17. Now type: exit
18. Now type: sudo umount ./mount
19. You should now be in the /home/thomas/images/ubuntu-raring/ directory. From here use the ls command and see your raring.img file.
20. You will need to copy this file your Windows box and use the Tubuntu installation application OR wheelie and nvflash commands. (Wheelie and nvflash commands are for more advanced users).
21. Click on this link for the next guide: http://forum.xda-developers.com/showthread.php?p=37803357
Hi, I have no problems creating the image and mounting it. But when chrooted:
apt-get update
0% [Working]qemu: Unsupported syscall: 374
Err http://ports.ubuntu.com raring Release.gpg
Something wicked happened resolving 'ports.ubuntu.com:80' (-11 - System error)...
I am on Ubuntu 12.10 64-bit. What could it be? qemu & qemu-user-static installed, qemu-arm-static copied...
Thank you and sorry for my CZ-english
onmail said:
Hi, I have no problems creating the image and mounting it. But when chrooted:
apt-get update
0% [Working]qemu: Unsupported syscall: 374
Err http://ports.ubuntu.com raring Release.gpg
Something wicked happened resolving 'ports.ubuntu.com:80' (-11 - System error)...
I am on Ubuntu 12.10 64-bit. What could it be? qemu & qemu-user-static installed, qemu-arm-static copied...
Thank you and sorry for my CZ-english
Click to expand...
Click to collapse
I need to update my guide. After the image is created on your Linux box you then install it on your tablet using tubuntu application. From the tab is where you run apt get commands. Sorry about that.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
I need to update my guide. After the image is created on your Linux box you then install it on your tablet using tubuntu application. From the tab is where you run apt get commands. Sorry about that.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Oh, I see, but I think I will not be able to install apt-utils wpasupplicant if the wlan0 adapter is not working (I mean when wpasupplicant is not installed in the image).
onmail said:
Oh, I see, but I think I will not be able to install apt-utils wpasupplicant if the wlan0 adapter is not working (I mean when wpasupplicant is not installed in the image).
Click to expand...
Click to collapse
Yes you will because the core image has everything you need except the supplicant. You can make your own supplicant or copy from your working dual booted prime image of android. Let me try and update the guide later tonight.
Sent from my SGH-T999 using Tapatalk 2
onmail said:
Oh, I see, but I think I will not be able to install apt-utils wpasupplicant if the wlan0 adapter is not working (I mean when wpasupplicant is not installed in the image).
Click to expand...
Click to collapse
Ok, made several changes to my guide. Here's a couple things to note in case you missed them.
1. This guide helps you make an image of Raring Ubuntu-Core. This means there is no GUI and an additional post I have linked to for installing Gnome-Core (your actual desktop environment) for Raring.
2. After the Raring.img is made, you need to start on the Raring Gnome-Core guide and follow those instructions. That installation takes about 2 hours to download and answer questions because it is such a core install.
3. About the wifi, you will be using x3maniac's Tubuntu Windows installation application and starting from fresh with Prime Android and your new Raring image and if you follow the second guide it will walk you through setting up your wifi (do make sure you boot into Prime Android and set up your wifi first before booting to Raring.
4. Please familiarize yourself with the OP I have linked to for the x3maniac Tubuntu application.
It's not as hard as it may seem. After you do it a few times it's rather quick. Installing gnome-core by yourself is kind of slow and a bit tedious but the purpose of doing this was to have complete control of your image.
Later on if you are brave you can also build your own kernel as well and make changes. See my guide in my xda signature.
Hope this helps, thanks for using my guide. Hit the thanks button a couple of times and I'll make sure you get up and running.
TomTcom said:
Ok, made several changes to my guide. Here's a couple things to note in case you missed them.
1. This guide helps you make an image of Raring Ubuntu-Core. This means there is no GUI and an additional post I have linked to for installing Gnome-Core (your actual desktop environment) for Raring.
2. After the Raring.img is made, you need to start on the Raring Gnome-Core guide and follow those instructions. That installation takes about 2 hours to download and answer questions because it is such a core install.
3. About the wifi, you will be using x3maniac's Tubuntu Windows installation application and starting from fresh with Prime Android and your new Raring image and if you follow the second guide it will walk you through setting up your wifi (do make sure you boot into Prime Android and set up your wifi first before booting to Raring.
4. Please familiarize yourself with the OP I have linked to for the x3maniac Tubuntu application.
It's not as hard as it may seem. After you do it a few times it's rather quick. Installing gnome-core by yourself is kind of slow and a bit tedious but the purpose of doing this was to have complete control of your image.
Later on if you are brave you can also build your own kernel as well and make changes. See my guide in my xda signature.
Hope this helps, thanks for using my guide. Hit the thanks button a couple of times and I'll make sure you get up and running.
Click to expand...
Click to collapse
OK, thanks a lot, I will try. I have been playing with Tubuntu for some weeks and now I just started playing with building the image (and thinking about kernel...). Just now I am on Lubuntu (with xfce4 which I prefer) with 2.6 kernel and I am trying on my son's TF101 Raring with Gnome and 3.1 kernel. I am just thinking about the possibility when one system is "fine tuned" if it would be possible to copy it from one TF to the other one (I mean just the Linux partition).
onmail said:
Hi, I have no problems creating the image and mounting it. But when chrooted:
apt-get update
0% [Working]qemu: Unsupported syscall: 374
Err http://ports.ubuntu.com raring Release.gpg
Something wicked happened resolving 'ports.ubuntu.com:80' (-11 - System error)...
I am on Ubuntu 12.10 64-bit. What could it be? qemu & qemu-user-static installed, qemu-arm-static copied...
Thank you and sorry for my CZ-english
Click to expand...
Click to collapse
Replying to my own post because I must say - sorry, I am ehm an idiot... Because the only problem was - I have not edited the /etc/resolv.conf in the mount/etc directory. So now I can easily apt-get anything in the chroot! So it seems I can easily "prepare" an image with everything inside
onmail said:
Replying to my own post because I must say - sorry, I am ehm an idiot... Because the only problem was - I have not edited the /etc/resolv.conf in the mount/etc directory. So now I can easily apt-get anything in the chroot! So it seems I can easily "prepare" an image with everything inside
Click to expand...
Click to collapse
Did it work? I couldn't not without finding a way to inject VI into the image for editing the file. You can mess with permissions but it ultimately doesn't work from the Linux box.
If you are able to do it without the tab, post the instructions and I'll add it to my OP and give you the credit.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Did it work? I couldn't not without finding a way to inject VI into the image for editing the file. You can mess with permissions but it ultimately doesn't work from the Linux box.
If you are able to do it without the tab, post the instructions and I'll add it to my OP and give you the credit.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
It works I am just in the middle of installing xubuntu-desktop... I have made a quick & dirty bash script which will help to set hostname for the new TF101, root password, make a new user with password and add him to sudo group, automatically enable all the deb repos (universe etc.), set cpu freqs in rc.local and install some usefull utils (sudo cpufrequtils bash-completion wpasupplicant nano mc net-tools). And there is a second script you can run on the first run on TF101 which will resize the linux partition to its limit, copy the wpa_supplicant.conf from the android partition and starts wlan0 I will send this to you asap but will test this first. Hope my English is understandable
onmail said:
It works I am just in the middle of installing xubuntu-desktop... I have made a quick & dirty bash script which will help to set hostname for the new TF101, root password, make a new user with password and add him to sudo group, automatically enable all the deb repos (universe etc.), set cpu freqs in rc.local and install some usefull utils (sudo cpufrequtils bash-completion wpasupplicant nano mc net-tools). And there is a second script you can run on the first run on TF101 which will resize the linux partition to its limit, copy the wpa_supplicant.conf from the android partition and starts wlan0 I will send this to you asap but will test this first. Hope my English is understandable
Click to expand...
Click to collapse
Xubuntu on raring is working without any problems. Now I would like to get the nvidia accelerated drivers working. I have tried 2 or 3 3.1 kernels but still without success. Googling for some help on compiling 3.1 kernel.
onmail said:
Xubuntu on raring is working without any problems. Now I would like to get the nvidia accelerated drivers working. I have tried 2 or 3 3.1 kernels but still without success. Googling for some help on compiling 3.1 kernel.
Click to expand...
Click to collapse
Awesome! If you go to the op for x3maniac, you can view his github that has 3.1 kernel source. Take a look and see of it helps.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Awesome! If you go to the op for x3maniac, you can view his github that has 3.1 kernel source. Take a look and see of it helps.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
By the way, I have instructions for compiling the 2.6.36 kernel in my xda signature if that helps you.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
By the way, I have instructions for compiling the 2.6.36 kernel in my xda signature if that helps you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I know, I have already checked that. The 2.6 kernel is ok but I would really like to see the nvidia drivers working...
Had an issue mounting raring.img in step 9, had to run sudo fsck.ext4 "path to file" afterwards it mounted smoothly, dont know why tho.
JoinTheRealms said:
Had an issue mounting raring.img in step 9, had to run sudo fsck.ext4 "path to file" afterwards it mounted smoothly, dont know why tho.
Click to expand...
Click to collapse
Hmmm...did step 8a work ok?
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Hmmm...did step 8a work ok?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Afaik it did, gave me the mentioned prompt, and finished without error. Might have something to do with me running a x64 vm ? as i wasnt able to chroot either. Im trying to get this running on my tf300t, but its alot different to installing it on the trusty tf101
Cheers for the guide tho, help me understand the whole process :good:
JoinTheRealms said:
Afaik it did, gave me the mentioned prompt, and finished without error. Might have something to do with me running a x64 vm ? as i wasnt able to chroot either. Im trying to get this running on my tf300t, but its alot different to installing it on the trusty tf101
Cheers for the guide tho, help me understand the whole process :good:
Click to expand...
Click to collapse
I believe our dev x3 mentioned there were differences on a VM so it probably has to do with that.
Glad the guide is helpful. Welcome!
Sent from my SGH-T999 using Tapatalk 2
Nice guide ! I just crated a 13.04 raring img. ( Used VM Kubuntu 12.04 )
Need some updates but nice
And there is a problem with actual release, wpa supplicant is not pre installed and now I'm in the begining of your second guide and cant set up wifi.
I had to download package with chroot, then install with my tab same for nano
Anyway, it's just FYI I dont really need help
Kingzak34 said:
Nice guide ! I just crated a 13.04 raring img. ( Used VM Kubuntu 12.04 )
Need some updates but nice
And there is a problem with actual release, wpa supplicant is not pre installed and now I'm in the begining of your second guide and cant set up wifi.
I had to download package with chroot, then install with my tab, and now it doesnt find iwlan0
Anyway, it's just FYI I dont really need help
Click to expand...
Click to collapse
This guide wasn't designed to use wifi, only to correctly package it for flashing 13.04 directly to the tab. The next guide adds the gui and requires your Android to be set up to copy over the wpa_supplicant file before executing those commands.
Onmail was able to script more changes to the image from "chroot" but I didn't go that far, he was able to get the supplicant and other abilities such as adding to the package better than I did.
Hello,
I'm gonna describe here a method that can bypass the "loop device not found" bug with Android 4.3 and LinuxOnAndroid (also called Complete Linux Installer).
With that method, you will be able to run Ubuntu 12.04. It will not harm your device, since it's only an application and a "mount loop".
This is not from me, I found some loose informations on LoA's forum and just tried it out. Then I wrote this guide when I finally got it working. Credits are at the end of the post.
Informations :
- Any Kernel should work (I use ElementalX 1.4)
- Any ROM should work (I use ParanoidAndroid 3.99)
- Any 4.3 device should work (this has been seen working on Nexus 4 and Nexus 7 flo).
- This trick should work for any GNU/Linux armel distribution, but you'll have to change some things, like "startlxde" command and others. I can't help you for that.
What do I need ?
- Root access(SuperSu is recommended)
- BusyBox
- a root file explorer (ES File Explorer is recommended)
- Android 4.3 or CustomROM based on 4.3
- A computer running GNU/Linux (Ubuntu is recommended, but this should work with any debian-based distro. LiveUSB should work)
- Internet access (Around 450Mb download is needed, so 3G or 4G is not recommended)
- ... some free time.
What should I do ?
Step 1 : Install apk on your device
Download and install those 3 applications :
- Complete Linux Installer
- Terminal Emulator
- Android-VNC-viewer
Step 2 : Prepare the .img ubuntu disk on your computer
- Start Ubuntu on your computer.
- Download the LinuxOnAndroid "ubuntu.img" from Sourceforge (you'll need the 'small' version : 396Mo)
- Create a new folder (anywhere you want, ext4 partition is recommended, so /home/user is good) and call it "loa" (for LinuxOnAndroid)
Code:
[I]Example : [/I]
mkdir /home/yourname/loa
- Extract the ubuntu1204-v4-small.zip in that folder
- Open a terminal and navigate to the directory where the ubuntu.img was extracted :
Code:
cd /home/yourname/loa
- Enter the following commands :
Code:
#Create the needed directories
mkdir ubuntunew ubuntuold
#Create a new empty .img
dd if=/dev/zero of=ubuntunew.img bs=1M count=0 seek=4096
#Format your new .img into ext4 (original is ext2 and bugs with Android 4.3)
mkfs.ext4 -F ubuntunew.img
#Mount the .img into the directories
sudo mount -o loop ubuntu.img ubuntuold
sudo mount -o loop ubuntunew.img ubuntunew
#Copy the content of downloaded ext2.img into created ext4.img (may process during some time)
sudo cp -r ubuntuold/* ubuntunew
#Unmount mounted .img
sudo umount ubuntuold
sudo umount ubuntunew
Step 3 : prepare your device for the new ubuntunew.img
- Copy the ubuntunew.img (4Go) from your computer to your device
- Place the ubuntunew.img in SDCARD/ubuntu/ubuntunew.img (you'll need to create the directory)
Step 4 : prepare Complete-Linux-Installer for the new ubuntunew.img
- Open "ES File explorer", turn on the "root explorer" option
- Navigate to /data/data/com.zpwebsites.linuxonandroid/files
- Edit bootscript.sh with a text editor :
1) In "Set up loop device and mount image" :
The line :
$bbox mount -t ext2 /dev/block/loop255 $mnt
becomes
$bbox mount -t ext4 /dev/block/loop255 $mnt
2) In "Mount all required partitions" :
add the line :
$bbox mount -o bind /sys/fs/selinux $mnt/selinux
3) In "Unmount all user defined mounts if any" :
add the line :
$bbox umount $mnt/selinux
- Save changes in bootscript.sh
Step 5 : Use Complete-Linux-Installer to boot ubuntunew.img
- Open "Complete-Linux-Installer
- Go to "Launch" > "Settings" > "Add"
Name : Droidbuntu
Image : /storage/emulated/0/ubuntu/ubuntunew.img
- Choose "Droidbuntu" from the list and "Start Linux"
- Proceed with the installation (terminal starts and ask you a few things) :
Code:
Example values I used on my N7 flo :
- resolution : 1920x1200 (I disabled navbar and statusbar, if you did not, you'll have to try acceptable values)
- run vnc : [B]yes[/B] (important! it will allow you to start the GUI)
- run ssh : no
- password : whatever you want
- You should now be in linux shell (you can tell by the [email protected]:/# in the terminal emulator)
- Enter the command :
Code:
#It will allow you to start the GUI by adding startlxde to the xstartup script
echo startlxde | tee /home/ubuntu/.vnc/xstartup
- Leave the terminal alone (don't close it) and open "androidVNC"
Values to use :
Code:
Nickname : Droidbuntu
Password : ubuntu
Adress : localhost
Port : 5900
Username : root
24-bit color (4 bpp)
Check the local mouse checkbox
- Clic on "Connect"
You are now in Ubuntu 12.04 LXDE. :highfive:
You may want to change "entrymode" in settings, and use "Touchpad", it's better in my opinion.
What's next ?
To start Ubuntu later, just open Complete-Linux-Installer and click "Start linux", then once you're in [email protected], open VNC and "connect". Yes, it's that simple.
The command lines need to be entered in terminal emulator, not in lxterm nor any terminal in Ubuntu.
Credits :
LinuxOnAndroid Team
Canonical and partners
Following LinuxOnAndroid forum users : clb, Isei, RobbH
NOTE : My english surely isn't perfect. If I made any errors, or if you don't understand a step, please tell me.
I can upload an ext4 ubuntu.img (described in step 2), but only if it really is necessary. The image is 4.0 Gigabyte and it will take me a long time to upload this... (My upload internet speed is 40Ko/s so it will take 30 hours to upload, and I'll be glad not to^^)
Awesome guide thank you.
Sent from my HTC Desire HD
Could some one post the image prefered-large one because i do not have ubuntu and it seems complicated for a 'noob like me
bogii4 said:
Could some one post the image prefered-large one because i do not have ubuntu and it seems complicated for a 'noob like me
Click to expand...
Click to collapse
This will not work "as it" with the large image, because you are adding the command startlxde to Ubuntu, which will start LXDE, not Unity.
Do not forget that small image uses LXDE, when large image uses Unity. I don't know which command you should use to start Unity in the xstartup script for VNC.
But, if you want some programs that are inclueded in large-image, you can always use "apt-get install nameofthepackageyouwant" in the terminal-emulator while using Ubuntu. This command will download and install the program. But if you want Unity, I can't help you, maybe some else know...
And, by the way. You don't have Ubuntu on your PC but you want to use it on Android ? That's odd^^
can you verify this works on Flo? it's not clear that you have this on your Nexus
reading the working devices list on linuxonandroid.org, it says "It does not work when going to the mount step since there is a bug in 4.3. It should run perfectly after that is fixed."
have a link or two where someone has successfully installed this on their Nexus 7 (Flo)? or do you have screenshots of it on yours?
Midnight_Rider said:
can you verify this works on Flo? it's not clear that you have this on your Nexus
reading the working devices list on linuxonandroid.org, it says "It does not work when going to the mount step since there is a bug in 4.3. It should run perfectly after that is fixed."
have a link or two where someone has successfully installed this on their Nexus 7 (Flo)? or do you have screenshots of it on yours?
Click to expand...
Click to collapse
It works on flo, I posted here in "Neuxs 7 (2013) > Nexus 7 (2013) General" and the title of this thread is "on N7 2013".
I also explained in the introduction that this is a way to bypass the bug with 'mount loop'.
I also said in the "informations" box that it works with 'flo'
I also gave the credits to users from LinuxOnAndroid forum, who made this possible. There you'll find some testimony of people who were able to run it. You can also check RobbH's post on LinuxOnAndroid thread, here, on XDA.
Sorry, but I think that it's pretty clear haha
Sent from my Nexus 7 using xda app-developers app
sure, ok, seems odd though that you edited your OP after you tell me the info i was looking for was already in the OP
whatever, thanks anyway
Midnight_Rider said:
sure, ok, seems odd though that you edited your OP after you tell me the info i was looking for was already in the OP
whatever, thanks anyway
Click to expand...
Click to collapse
I added this to OP :
Code:
Example :
mkdir /home/yourname/loa
I'm trying to help you and others here, I'm not here to be insulted and called a liar. Thank you.
anyway (workaround) we can boot the 'large image as in Unity the full desktop experience? or do we have to wait for an actual fix ?
Just thought I would pop in and say hi.
Thanks to @Vaykadji and everyone else in LoA land that helped get everything running on 4.3 we are finally sorting the bugs.
A beta version of the app featuring the edits needed in the boot script has been pushed to our beta test group and new ext4 images are being cooked as we speak.
Should not be much longer now and LinuxonAndroid will fully support 4.3
bogii4 said:
anyway (workaround) we can boot the 'large image as in Unity the full desktop experience? or do we have to wait for an actual fix ?
Click to expand...
Click to collapse
as I said : the part in the guide where you add "startlxde" to the xstartup script is only for LXDE (so: small image of Ubuntu only). But if you find the same command for Unity, you will maybe be able to boot with Unity.
Note: Unity and LXDE are both "desktop environment", but different ones. Google it if you don't understand, I can't explain this with my poor English :/
I used this method,but in ubuntu 12.04,it's only X cursor and gray desktop.
in ubuntu 13.04,solved this problem. so we best use ubuntu 13.04.
now I have a problem:in ubuntu,I installed openjdk and run java application .if java application not close and run background.then I press power button to close screen,battery drain very quickly.I saw "android os " always awake.one hour maybe drain 5% battery.
if close the java application battery drain normal.and "android os " no longe awake.
this problem only found in nexus 7 (flo), I have run java application in other android device(like nexus 7 2012,htc evo 4g lte,htc incredible) all of them didn't appear this problem.
some people can test this problem?
and how can I resolved it?
sdwshlsdx said:
I used this method,but in ubuntu 12.04,it's only X cursor and gray desktop.
in ubuntu 13.04,solved this problem. so we best use ubuntu 13.04.
now I have a problem:in ubuntu,I installed openjdk and run java application .if java application not close and run background.then I press power button to close screen,battery drain very quickly.I saw "android os " always awake.one hour maybe drain 5% battery.
if close the java application battery drain normal.and "android os " no longe awake.
this problem only found in nexus 7 (flo), I have run java application in other android device(like nexus 7 2012,htc evo 4g lte,htc incredible) all of them didn't appear this problem.
some people can test this problem?
and how can I resolved it?
Click to expand...
Click to collapse
The X cursor and gray desktop appears when you don't add "startlxde" to you xstartup script. I'll try with 13.04 if I have the time, I couldn't tell right know.
Works well on Ubuntu 13.04 small image (but in 13.04, you don't have to do the "echo startlxde | tee /blablabla" command)
a little off topic but.. i was able to boot Windows XP using Bosch it took 10-15mins to fully boot but it is not usable i expected more mouse seems smooth but clicking - the start menu, open something takes forever :/ worth it?
Vaykadji said:
I added this to OP :
Code:
Example :
mkdir /home/yourname/loa
I'm trying to help you and others here, I'm not here to be insulted and called a liar. Thank you.
Click to expand...
Click to collapse
you're right, did not mean to insinuate anything or insult you, that was not my intent. please accept my apologies
Thank you ! We're good.
Now, since this guide will soon no longer be usefull (with LoA being updated), I'm willing to do some researchs on how to improve Linux ARM experience. Because I noticed that they were plenty of cool things that were not ported (or not officially though).
Some repo's are broken for example. Official repo's (I was planning to install LightSpark, a flash-player fork, but no can do). Maybe this will be more usefull for LinuxOnAndroid user's.
And Touch should be released soon for Nexus products (not including flo, but hopefully it'll come quick).
So, with this, it's not touch screen?
Sent from my Nexus 7 using Tapatalk 4
I manage to run Mac OsX Snow Leopard on zenfone 2 (thanks to ycavan and his windows 10 guide). I create a guide to help people to test it, so lets begin:
https://www.youtube.com/watch?v=COV_l-f7FO0
Edit: This guide works for install windows too. Please see post # 7: https://forum.xda-developers.com/showpost.php?p=72426017&postcount=7
You must have a kernel with KVM function enabled. I personally use this rom
which include KVM kernel: https://forum.xda-developers.com/zenfone2/development/rom-rbr-v1-0-t3550544
Download OsX Snow Leopard Iatkos S3V2 iso image (torrent search iATKOS_S3_V2.zip)
Download and Install VirtualBox 4.3.40 (newer version doesnt work) on PC
Open it and create a Virtual Machine (VM) as following:
Name: Snow Leopard
Type: Mac OS X
Version: Mac Os X (64 bit).
Ram: in the top green right
Create a Virtual Hard Drive named SnowLeopard (vdi format, 10 gb or up recommended, fixed size)
Click on Configure:
On System untick disquette and untick enable efi
On Display....video memory full to the right
On Storage click on the cd image and select your iatkos.iso previously unzziped
Click ok and start VM (green arrow)
When a chameleon image appears press F8 and type: -x busratio=29 (if busratio does not work and get kernel panic, you must google your PC processor´s bus ratio and change this number with yours)
Installation now begin:
Select your language
click on Utilities and disk utility. click on your disk, click on erase and select Mac OSX extended(journaled) and click erase. Then close disk utility and continue with installation. Click on continue, right arrow, then click in your disk and select Customize:
On bootloader untick AsereBLN and tick chameleon v2 rc4
On bootloader option tick Graphics Enabler
On drivers, in main hardware tick on SATA/IDE, and tick network
Click OK and click on Install. At this point the OSX installation will begin.
Reboot the virtual machine and your OSX should start.(if you get a kernel panic for VodooHDA kext, you have to delete the kext with this guide: http://www.osxlatitude.com/remove-kext-from-single-user-mode/ it is located in system/library/extensions).
When you started the VM, go to safari and search for "Multibeast Snow Leopard Edition", and download it. Open it and tick EasyBeast Install, and above tick ShowallFiles on OSx86 software. Click install. Reboot your machine. Go to applications, open showallfiles and click Show. Go to finder, SnowLeopard disk, /Extra folder and in extensions folder delete ElliotForceLegacyRTC.kext
Open safari, go to https://github.com/kholia/OSX-KVM/blob/master/kexts/QemuUSBTablet-1.2.pkg and download QemuUSBTablet-1.2.pkg and install this package. Power off Virtual Machine.
In your pc go to C:\Users\(your user name)\VirtualBox VMs\SnowLeopard and copy SnowLeopard.vdi to your internal storage on phone (you must have at least 11 gb of free space).
On your phone:
Go to Play Store and install Linux Deploy. Open it and click on down arrow. Change this options: distribution (ubuntu), Suite (xenial), username (android), password (advr), enable init, enable mounts and in mount points add /sdcard , enable ssh, dont enable GUI. Back and in the three dots click on install. It can take over 20 minutes to complete. Click on start.
Download, unzip and copy my script attached in your internal storage (not microsd).
Download aSpice Free from Play Store. Open it and in connect type 127.0.0.1:5901. Dont click connect, only minimize app
Download Termius from Play Store. Open it and click bottom right to start a new session. Type localhost:5900 and click connect. User: android pass: advr
Once connected type the following:
sudo su
apt-get update
apt-get install qemu-kvm (type y if prompted)
cp /sdcard/osx.sh /
chmod a+x /osx.sh
/osx.sh
If you get "QEMU 2.5.0 monitor" you are right, if not, search for errors.
Open aSpice free and click connect. VOILA! You should see your osx Snow Leopard starting!
thanks to @ycavan and his guide: https://forum.xda-developers.com/zenfone2/general/zf2-running-windows-7-using-kvm-t3153299
Thank you very much.
Can I use your guide for installing windows, or not?
bahaa87 said:
Thank you very much.
Can I use your guide for installing windows, or not?
Click to expand...
Click to collapse
Yes, the concept is the same. I recommend you use this guide made by Ycavan: https://forum.xda-developers.com/zenfone2/general/zf2-running-windows-7-using-kvm-t3153299 to run Windows, i personally use it, but for ease to manage I create the images (windows, osx) in virtualbox first and copy them to my phone and ejecute in vdi format on qemu-kvm.
this is awsome!!! i'll be trying it tonight! any luck with the newer operating systems?
bonznumber1 said:
this is awsome!!! i'll be trying it tonight! any luck with the newer operating systems?
Click to expand...
Click to collapse
Newer OS should work, I installed SL because i have this iso file on hand, but i dont think there are any problem installing Yosemite, EC, Sierra, considering obviously it will consume more resources
alvavaca said:
Yes, the concept is the same. I recommend you use this guide made by Ycavan: https://forum.xda-developers.com/zenfone2/general/zf2-running-windows-7-using-kvm-t3153299 to run Windows, i personally use it, but for ease to manage I create the images (windows, osx) in virtualbox first and copy them to my phone and ejecute in vdi format on qemu-kvm.
Click to expand...
Click to collapse
I tried Ycavan guide but I don't understand all steps. And I don't find any video explain it. So I want to try another guide to install windows in my phone, because I need it very much.
bahaa87 said:
I tried Ycavan guide but I don't understand all steps. And I don't find any video explain it. So I want to try another guide to install windows in my phone, because I need it very much.
Click to expand...
Click to collapse
My guide works for installing Windows too. Instead of installing mac osX in virtualbox you must install windows (with any iso installer image) and create a disk (vdi) called windows (no matter which version is, 7, 8, 10) and use this script instead of the other. The other steps are the same, only continue from "On the phone" part. Obviously you must copy the script attached on this post instead the other and to start windows you must run this on termius (type one by one and press enter):
sudo su
apt-get update
apt-get install qemu-kvm (it take a while) type "y"
cp /sdcard/windows.sh /
chmod a+x /windows.sh
/windows.sh
My guide differs from Ycavan in that he installs the system on the phone and I create the image on the pc with virtualbox and then transfer it to the phone, but the concept is the same. I give you my scripts ready to use, Ycavan explains how to create the scripts (is hard to understand if you dont know the elementary concepts). Good luck.
alvavaca said:
My guide works for installing Windows too. Instead of installing mac osX in virtualbox you must install windows (with any iso installer image) and create a disk (vdi) called windows (no matter which version is, 7, 8, 10) and use this script instead of the other. The other steps are the same, only continue from "On the phone" part. Obviously you must copy the script attached on this post instead the other and to start windows you must run this on termius (type one by one and press enter):
sudo su
apt-get update
apt-get install qemu-kvm (it take a while) type "y"
cp /sdcard/windows.sh /
chmod a+x /windows.sh
/windows.sh
My guide differs from Ycavan in that he installs the system on the phone and I create the image on the pc with virtualbox and then transfer it to the phone, but the concept is the same. I give you my scripts ready to use, Ycavan explains how to create the scripts (is hard to understand if you dont know the elementary concepts). Good luck.
Click to expand...
Click to collapse
Thank you very much.
I'll try it tomorrow.
apt-get is a debian tool...not found on android...how did u manage to use it?
Apt-get is used in linux deploy...not in android system
Hello I've Created installer script for PhoenixOS with help of grub installer script taken from remixos deb package file.
I am not responsible for anything that may happen to your PC/Laptop/Tab as a result of installing and using this script. you do so at your own risk and take the responsibility upon yourself.
Click to expand...
Click to collapse
Note: Backup your custom.cfg file if you are dual booting with other os if not then proceed further.
custom.cfg should be in /boot/grub/custom.cfg if EFI install then /boot/efi/EFI/yourdistroname/custom.cfg
p7zip-full should be installed its need for extracting ISO file.
Script should be placed where desired files or ISO is present.
--> This is tested and working fine in kde neon lts on MBR and GPT disks & EFI is not tested as I don't have that installation so it should work.
--> Other then Debian based distros IDK if my script works on them or not, so please test it yourself and inform.
--> If your home folder is defined on other disk or partition please add insmod part_gpt insmod ext2 OR insmod part_msdos insmod ext2 according to disk partition table to grub entry in custom.cfg
Click to expand...
Click to collapse
Features
Path defined root and home only.
Method defined FILES and ISO & EXE only.
Has Uninstall options.
Data folder is created in os folder
Click to expand...
Click to collapse
Make script executable
Code:
chmod +x PhoenixOS-Installer-Linux
Then Run
Code:
./PhoenixOS-Installer-Linux
reserved
reserved post
Not enough information. Please elaborate on the installation procedure itself. On Ubuntu of course it should install to sda2. I chose the path /dev/sda2/ then used .iso for the install method, and then upon trying to do the install using option 2 it simply keeps bringing me back to the menu where choices 1-4 are present.
I actually got PhoenixOS to install using the USB method, however I cannot find a working boot sequence for GRUB bootloader. I'm kind of at a loss for finding a way to easily switch between Ubuntu and PhoenixOS.
Deucalion29710 said:
Not enough information. Please elaborate on the installation procedure itself. On Ubuntu of course it should install sda2. I chose the path /dev/sda2/ then used .iso for the install method, and then upon trying to do the install using option 2 it simply keeps bringing me back to the menu where choices 1-4 are present.
I actually got PhoenixOS to install using the USB method, however, I cannot find a working boot sequence for GRUB bootloader. I'm kind of at a loss for finding a way to easily switch between Ubuntu and PhoenixOS.[/QUOTES]
I got this done by making different partitions. Sounds like a no-brainer, but it works. My main OS is MacOSX, then I made different partitions of FAT32s using Disk Utility, I created them all in different sizes (to prevent confusion). After that, I just install the other OS one by one (Phoenix will always be the last). And, I made some extra partitions during Linux installation (just in case) and deleted them after.
As for the Phoenix post, Thank you
Click to expand...
Click to collapse
It does not work...
I have placed the script and the iso file in the same home directory, chdir in that place but the script does nothing ... It asks for sudo and the it does not create any directorys.
To complicated to debug for me....
EDIT:
I have managed to install it in home / iso mode
I had to edit the generated schipt for modifying GRUB. It was copiing the whole script and not stopping at EOF ?!
It works great
Setup;
1 - Download Phonix OS ISO image on Phonix OS web site
2 - Create a folder with any name
3 - Copy the Iso file to this folder and extract the PhoenixOS-Installer-Linux.zip file to this folder
4 - Open the terminal and go to the folder you created
5 - Now run "chmod +x PhoenixOS-Installer-Linux" and "./PhoenixOS-Installer-Linux" command
6 - The script will run
7 - Select "Select Path & Method"
8 - Type "home" for path and press enter
9 - Type "iso" for method and press enter
10 - Select "Install Rom" and follow the steps
11 - Run the "sudo update-grub" command using the terminal when the process is finished
12 - Restart the computer and select Phoenix Os
I'm sorry for my bad english
bycoder said:
Setup;
1 - Download Phonix OS ISO image on Phonix OS web site
2 - Create a folder with any name
3 - Copy the Iso file to this folder and extract the PhoenixOS-Installer-Linux.zip file to this folder
4 - Open the terminal and go to the folder you created
5 - Now run "chmod +x PhoenixOS-Installer-Linux" and "./PhoenixOS-Installer-Linux" command
6 - The script will run
7 - Select "Select Path & Method"
8 - Type "home" for path and press enter
9 - Type "iso" for method and press enter
10 - Select "Install Rom" and follow the steps
11 - Run the "sudo update-grub" command using the terminal when the process is finished
12 - Restart the computer and select Phoenix Os
I'm sorry for my bad english
Click to expand...
Click to collapse
it works but when i try to boot it stucks at command shell. any idea ?