Database Users

[Tutorial] Boot Linux on the Typhoon

Started to mess about with this earlier today, finally got the damn thing to work Turns out it is quite easy..
First, to get one thing straight, this will only boot the kernel, it will dump you at a shell which you have to remotely log on to via telnet over usb. There will be some (not so) fancy text appearing on your phone's screen but that is about it. Also, it only works on unlocked phones.
This is what you get:
On your computer you'll get this:
Cool, huh? Btw, this is running from a memory card, your OS will be untouched so as soon as you reboot the phone it will boot right back into WM2003/5/6.
1. What you need
* A HTC Typhoon running any rom of your choice (I did it on WM6).
* A miniSD memory card
* A Linux distro - I downloaded the Ubuntu Live CD and ran it through VMWare, no need to install anything or reboot your computer.
* miniSD image of Xanadux - this is the linux port for HTC devices. Grab the latest version here: http://rapidshare.com/files/92218185/Linux.zip.html
(these files are extracted from the miniSD image file found here: http://vivien.chappelier.free.fr/typhoon/download.html)
2. How to run linux on the Typhoon
1. Instead of installing linux properly on your phone which requires partitioning of the internal memory etc (a lot can go wrong) we'll put it on the memory card then a Windows Mobile program called HaRET will boot linux for us from WinCE. Completely non invasive in other words.
This bit is dead easy, just extract the Linux.zip file you just downloaded and copy the files to the root of your memory card (must be memory card, can't do this from the internal memory afaik). Next, go to the File Explorer on your phone and find the file HaRET.exe. Run it then press the run button (this button has focus when you execute HaRET.exe so just press the joystick when the windows appears) and you will see a message saying "Booting linux", then after a few seconds your screen will go black and some text will appear.
Voila! That's linux running on your phone!
2. Connect to the phone via telnet
If read the last line of text that appeared on screen you'll see that it says "Press enter to activate this console" but no matter what buttons you press on the phone nothing happens, some gibberish appears but that's it.
Solution: telnet to the phone from your computer.
Get Ubuntu to boot on your computer, then go to Applications->Accessories and run the Terminal. Next type in the following commands:
Code:
modprobe cdc_ether
modprobe usbnet
ifconfig usb0 up 192.168.9.1
and finally
Code:
telnet 192.168.9.10
Login with username root and you'll find yourself at a shell like the screenshot above. Everything you see from now on is coming linux from your phone!
I've noticed that Xanadux doesnt always initialise the USB port unless it is connected via USB when booting up so make sure you always have your phone connected via USB when you run HaRET.
Now I'm going to try to figure out how to get the GSM module to work...

LINUX based ROM??
Hi shandar,
I have read your post and I am interested to know if you are cooking a LINUX based ROM that will run in a WIndows Mobile device? That would be too good to be true.
Also another question is do you need to have Linux running on your desktop to make this tutorial work?

ryanchanmd said:
Hi shandar,
I have read your post and I am interested to know if you are cooking a LINUX based ROM that will run in a WIndows Mobile device? That would be too good to be true.
Also another question is do you need to have Linux running on your desktop to make this tutorial work?
Click to expand...
Click to collapse
Hey, well, I don't know enough to make a linux rom for smartphones. I'd love a working linux distro for Typhoons & Windows Mobile phones in general but it is way out of my league unfortunately.
Btw, I probably should clarify that I only wrote the tutorial, the actual linux port is made by someone else.

[GUIDE] (sort of) Dualbooting Windows 8 & Ubuntu with Super Grub2 Disk

Hi there,
I have being trying to boot into my Ubuntu 10.10 with WIndows 8 Developer Preview installed, and I have found a quick workaround (I think most of you will probably know it already, but I'll post it here anyway for those who don't )
Firstly, install the Linux distribution of your choice (I tested with Ubuntu 10.10, so I'm not sure about any other OS's!)
Next, grab a copy of Super Grub2 Disk off supergrubdisk.org (can't post links yet... too new! ;-) ) and burn it to CD/DVD/USB.
Then, reboot your PC with Super Grub2 Disk in and select your boot device from the boot menu (I pressed F12 on my Acer) and Super Grub2 Disk should load. Select "Detect Any OS" (the first option) and wait while it scans your partitions for operating systems.
It should then display something like "linux 3.0.0-12-generic", "linux 3.0.0-12-generic (single-user mode)" and "Windows Vista (bootmngr)" (I thought the Vista bootmngr was a bit strange - must be the same boot manager as in earlier versions, but with linux-crippling secureboot :-( ). Select linux 3.0.0-12-generic and you are done!
You can now safely remove the disk. For (nearly) seamless usage, burn Super Grub2 Disk to a USB drive and tweak the BIOS settings to boot off said USB drive!
Enjoy

Simpler: after doing this and booting into Ubuntu, reinstall grub via the terminal or software center, problem solved, no more CD needed. (I used this method to triple boot between Ubuntu 11.04, Win7, & Win8)
Sent from my Sensation using Tapatalk

NikolaiT said:
Simpler: after doing this and booting into Ubuntu, reinstall grub via the terminal or software center, problem solved, no more CD needed. (I used this method to triple boot between Ubuntu 11.04, Win7, & Win8)
Sent from my Sensation using Tapatalk
Click to expand...
Click to collapse
I hadn't thought of that - thanks!

[GUIDE] Dual-booting Windows 7 and Ubuntu Linux and Install Ubuntu through VirtualBox

DUAL-BOOTING WINDOWS 7 & LINUX​
The following guide is to help would-be developers install Linux. If you are unsure how to partition a hard drive or run a backup, you probably should not attempt this. You've been warned, also I am not responsible for anything bad that may happen to your computer, this is simply a guide. If you have questions or run into a stumbling block, don't hesitate to ask. Lastly this guide was written for users using Windows 7, though it should work for other Windows versions I have no personal knowledge of how to accomplish this. Lastly read the guide the whole way through, there are two different methods one appears easier than the other.
METHOD 1 (TRIED AND TRUE)​
Downloads for method 1)
Ubuntu 12.04 (LTS): This is the most current Ubuntu Linux release.
PowerISO: PowerISO is a small program that allows you to mount an .iso file as a physical drive, and allows for easy CD/DVD creation.
EasyBCD: EasyBCD is an excellent way to edit MBR so that it is easy to go from one OS to the next.
Prep-Step 1) Back up your work (This should be a no-brainer but all too many times have I seen someone in a sticky spot because they didn't have a good backup). Its not unheard of for a hard drive to become corrupted after repartitioning, but I can say that its not common either.
Prep-Step 2) Make a Windows recovery disc, if you have OEM installed Windows. If you did a clean Windows install or have the Windows disc for the operating system you are running, grab it. When installing a second OS you have to mess with the Master Boot Record (MBR), and the easiest way to repair the Windows MBR is with the recovery function on the disc.
Prep-Step 3) If you are like me and insisted on clean installs on your PC (I get not doing it every time on your phone, but I don't get in the habit of installing OS' on my PC), make sure that Windows is installed first. This step will save you a potential headache, and $50 bucks when you break your keyboard for not following Pre-Steps 1 and 2. The long and short of it is that Windows when it is installed will over-write whatever is on the hard drive its being installed on, including the Linux bootloader.
Optional Prep-Step I personally have found it easiest to partition my disc from Windows, so I am including this step.
a) [CLICK] "Start" in Windows
​
b) Type "disk management" and press [ENTER]
c) Choose the drive you wish to partition, in this case we will use the C drive, in the bottom pane, then [RIGHT-CLICK] on the main partition, [CLICK] "Shrink Volume"
d) Shrink the partition by entering how many MB you want to take from that partition, keep in mind for any of you people like myself who like to see even numbers on hard drives that 1 GB = 1024 MB, not 1000. Then [CLICK] on "Shrink" Please keep in mind that Ubuntu recommendsAT LEAST 10 GB and requires 4.4 GB If you are planning to do ROM development you should consider shrinking by around 100 GB or more if you have it.
You will now see unallocated space on your hard drive and for now thats a good thing. I typically do the actual format of the new partition during the Ubuntu install.
Prep-Step 4) Download Ubuntu and either a) burn it to a disc using an app like PowerISO, or b) put it on a USB stick. For ROM development you need to run the 64 bit version of Ubuntu.
OTHER RELEVANT INFO: While doing more in depth research I found several posts in forums about installation errors on hard drives larger than 1TB. The work around for this seems pretty easy. BEFORE PARTITIONING run a defrag, the goal is to get the new partition as close to the beginning of the disc as possible. Once again, if you have not already done so...BACKUP your data. If you have over 500 GB used on your hard drive you will most likely have issues booting Linux on a single hard drive, but you can still dual-boot when both OS' are on different hard drives.
INSTALLATION
​Step 1) Insert the Ubuntu CD you burned into the CD/DVD tray of your PC and reboot your computer.
Step 1.5) If your BIOS is not set to boot from the CD drive you will need to tell the BIOS to boot from the CD, by pressing either F2, F12, Escape, or Delete depending on your BIOS. BIOS option are different for most PC manufacturers so I will not include how to change your boot order in this guide.
Step 2) Continue the installation and follow the prompts until you are asked this question: "How do you want to partition the disk?".
Step 3) If you followed the optional step and have room for Ubuntu then select the partition that you have already formatted select "Install Ubuntu alongside Windows 7" follow the installer through the rest of the steps. If you did not do the optional step, select "Something else" which will open up the "advanced disk partitioning tool"
Step 3.5) Not Applicable if you did the optional step in the preinstallation. When the Advanced disk partitioning tool opens you will see two (2) NTFS file systems (/dev/sda1, and /dev/sda2) DO NOT RESIZE /dev/sda1 unless you know what you are doing. It is ill advised to say the least and can cause boot issues. That said select /dev/sda2 (for most users this is their Windows partition) and [CLICK] "change". This will open a pop-up so that you can select how much of the Windows partition you want to use for Linux.
Step 4) In the "Installation Type" window at the bottom you should now see an area called "free space", select it, then [CLICK] "add" to add a new partition.
Step 5) The first partition we will add is the boot partition. For the partition type the default should be logical, if it is then leave it there, if not select logical. The recommended size is 500 MB. Keep the "Use as" box at its default which should be ext4, and the mount point is /boot. [CLICK] "ok"
Step 6) In the "Installation Type" window [CLICK] on "free space" and [CLICK] "add" to add a new partition, this partition will be / (root). Once again this will be a logical partition which will be used as a ext4 file system, and the mount point is /. The root partition does not need to be HUGE, 75% of the minimum 4.4 GB should be fine (Even if you are using much more than the minimum there is not much need for a / that is more than a few GB in my own experience. [CLICK] "ok" when finished.
Step 7) In the "Installation Type" window [CLICK] on "free space" and [CLICK] "add" to add a new partition, this partition will be /home. Once again this is a logical partition, using ext4 and the mount point is /home. The size of this partition is going to vary from user to user. You are only creating one more partition for Linux after this, and that partition is relatively small (1GB per 1GB RAM installed), so do not hesitate to use the majority of the space you allocated for Linux on this partition. [CLICK] "ok" when finished
Step 8) In the "Installation Type" window [CLICK] on "free space" and [CLICK] "add" to add a new partition, this last partition is for your swap. Once again this is a logical partition, but it will not be used as a ext4 file system, in the dropbox select "swap area". For the partition size I recommend using the rest of whats available for the swap, which should be 1GB per 1GB of RAM installed, for example if you have 4GB of RAM your swap should be 4GB. Once finished [CLICK] "ok".
Step 9) Once again you should be in the Advanced Disk Partition Tool ("Installation Type" screen), there you can see the partitions you have created. Because the /boot partition is logical it should be listed as /dev/sda5 (Always check...I can not express enough that anomalies happen). In the "Device for bootloader installation:" dropbox select /dev/sda5 or whatever it was labeled (EX /dev/sda#) [CLICK] "install now"
Step 10) Follow through the rest of the installation and enter your user information. After the install is completed successfully reboot your PC, it will reboot into Windows (which is 100% expected since we did not tell the MBR to look for our Linux system.
Step 11) Download and install EasyBCD from here, it is a free download.
Step 12) Open EasyBCD and [CLICK] "Add New Entry" , then [CLICK] the Linux/BSD tab. From the "Type" dropbox select "GRUB 2". I believe the name box comes filled with the OS info by default, if not in the "name" type "Ubuntu 12.04 (LTS)" and [CLICK] "add entry" (Not "Add New Entry")
Step 13) [CLICK] on "Edit Boot Menu", select your default OS and set the time out options.
Step 14) [CLICK]"Save Settings"
At this point you should have a dual-booting computer with both Windows 7 and Linux...Congrats.
MAKE WINDOWS BOOT BY DEFAULT ON PREVIOUSLY INSTALLED DUAL BOOT SYSTEM​
Step 1) Restore the MBR from your Windows installation disc
Step 2) Download EasyBCD from here its pretty easy to use. The non commercial version is free too. This program will allow you to select the boot priority.
If you require more detailed instruction please PM me and I will add to the OP​
​

METHOD 2 (USING THE WINDOWS INSTALLER)​
I want to start by stating that I personally have never used this method, but it seems like its pretty easy (perhaps easier than Method 1). Credit for this part of the guide goes to Ubuntu.com.
Prep-Step) Download the Windows Installer from HERE. I suggest using Internet Explorer for this since IE gives you the option to just run the installer, rather than downloading it, only to delete the installer off your hard disk later.
Step 1) Run the installer if you have not already
Step 2) When prompted, enter the username you would like to use and the password for that account. Then [CLICK] "Install"
Step 3) Wait...The download is about 500MB so it may take a while to download and install but apparently you can still use your computer while this install is taking place. Once prompted [CLICK]"Finish" to restart.
Since I have not used this method I can not tell you at this point if it is necessary to repartition your hard disk when using this method. I will format my other PC and try it out later today or tomorrow and update this post as necessary.​
INSTALLING UBUNTU THROUGH VirtualBox
​
Please read through the entire guide BEFORE attempting to do the tasks detailed in this guide. For this portion of the guide I used Ubuntu 11.10-Desktop, which is no longer a current release. The steps should be pretty close to the same, but after Step 7, things may get a little out of order.
Step 1) Open VirtualBox and [CLICK] "New" to add new virtual machine
Step 2) In the name field You are going to name your virtual machine, generally I use the distro name (EX "Ubuntu 12.04 (LTS)"), if you name like this the next box will automatically change to Linux, and the version will say "Ubuntu" [CLICK] "next".
Step 3) Select how much RAM you want to use for your virtual machine, generally I will use 2 GB, if I am going to use a virtual machine (This is where a dual boot has its biggest advantages. Your hardware is only running one OS, when virtualized your hardware is essentially running two.). [CLICK] "next".
Step 4) Now you are going to create your virtual hard drive, keep in mind if you are running a virtual machine to develop (I don't recommend this), you are going to want to dedicate more than a few GB for Linux (100GB+). [CLICK] "create". I use the VDI disk image type so I made sure that was the one selected, and [CLICK] "next", now at this next screen you can choose if you want your virtual hard disk to be dynamic (Only as large as it needs to be), or a fixed size. I chose dynamic, but again this may not be effective for development purposes. I have no personal knowledge of this so I can not answer that question. Finally [CLICK] "create"
Step 5) In the VirtualBox main screen [RIGHT-CLICK] your Linux virtual machine and select start.
Step 6) You will be prompted for which drive the installer for whichever distro you are using, at this point you want to go to the box to the right of the drop menu and select the .iso for the distro you want to use. Now [CLICK] "start"
At this point you should have a virtual machine running and ready to install Ubuntu.
Step 7) You are going to select your language and [CLICK] "Install Ubuntu". [CLICK] "continue" on the next screen.
Step 8) At this point you will be asked how you want to install Ubuntu, whether you want to erase the entire disk and install Ubuntu or if you want to do something else. You can do either one, without risking damage to your PC on a virtual machine, which is part of why we had to create the virtual disk. For this guide I am going to choose to Erase the disk and Install Ubuntu make your selection then [CLICK] "continue", then [CLICK] "install now".
Step 9) Choose your timezone then [CLICK] "Continue"
Step 10) Select your keyboard layout then [CLICK] "continue"
Step 11) Enter the user information you wish to use then [CLICK] "continue"
Allow the virtual machine some time to install the OS and once installation is completed it will prompt you to reboot [CLICK] "restart now". Congrats you should now have a working virtual Linux desktop!

RESERVED FOR DUAL BOOT ON 2 HARD DISKs GUIDE

ItzCrooK2UxD said:
RESERVED FOR DUAL BOOT ON 2 HARD DISKs GUIDE
Click to expand...
Click to collapse
Bro, can u show a guide to install inside virtual box cos i try to install it. Always fail at i686 kernel problem. Tks
Sent from my LG-P990

orbital_71 said:
Bro, can u show a guide to install inside virtual box cos i try to install it. Always fail at i686 kernel problem. Tks
Sent from my LG-P990
Click to expand...
Click to collapse
I can add in a virtual machine guide too. You're using Virtual Box, and not VMWare Player? If you are getting kernel failures I would try redownloading Ubuntu.
Also which settings are you using for your virtual machine?

ItzCrooK2UxD said:
I can add in a virtual machine guide too. You're using Virtual Box, and not VMWare Player? If you are getting kernel failures I would try redownloading Ubuntu.
Also which settings are you using for your virtual machine?
Click to expand...
Click to collapse
i am using virtualbox V4.2, i am able to dual boot but when i try to install inside virtualbox no success. I had try i386 and amd64 uninstall ubuntu and try install inside ubuntu but still fail. Using the storage setting to mount the disc. Tks

orbital_71 said:
i am using virtualbox V4.2, i am able to dual boot but when i try to install inside virtualbox no success. I had try i386 and amd64 uninstall ubuntu and try install inside ubuntu but still fail. Using the storage setting to mount the disc. Tks
Click to expand...
Click to collapse
Also a few things I forgot to ask...What kind of computer are you using, please be detailed and include things like Processor speed (chip number if you know it), RAM, and which OS you are using, and which version of Ubuntu (or other Linux distro) you are attempting to run in VM. I am going to try to replicate your error, so I can walk you through it.
Also you state that you had no success, please elaborate. Did the virtual machine not boot? Did it boot, but you could not get logged in? The more details the better...Thanks

ItzCrooK2UxD said:
Also a few things I forgot to ask...What kind of computer are you using, please be detailed and include things like Processor speed (chip number if you know it), RAM, and which OS you are using, and which version of Ubuntu (or other Linux distro) you are attempting to run in VM. I am going to try to replicate your error, so I can walk you through it.
Also you state that you had no success, please elaborate. Did the virtual machine not boot? Did it boot, but you could not get logged in? The more details the better...Thanks
Click to expand...
Click to collapse
Mine system 2nd gen i5 2 gb ram window 7 home premium. since i already duat boot ubuntu 12.04 amd64 bit and how actually to install inside virtualbox? I f i follow the instruction from askubuntu i will get stuck at the boot image of ubuntu saying the kernel i686 kind of stuff error. Was vmware player are better to use it for? tks

orbital_71 said:
Mine system 2nd gen i5 2 gb ram window 7 home premium. since i already duat boot ubuntu 12.04 amd64 bit and how actually to install inside virtualbox? I f i follow the instruction from askubuntu i will get stuck at the boot image of ubuntu saying the kernel i686 kind of stuff error. Was vmware player are better to use it for? tks
Click to expand...
Click to collapse
I have always used VMWare Player myself. Once I get home I will install VirtualBox and do a write up and walk you through it. Aside from RAM we have similar setups. Give me a few hours and I'll try to walk you through it.

ItzCrooK2UxD said:
I have always used VMWare Player myself. Once I get home I will install VirtualBox and do a write up and walk you through it. Aside from RAM we have similar setups. Give me a few hours and I'll try to walk you through it.
Click to expand...
Click to collapse
But if vmware is a good virtual machine to use then i just follow u with it. i can just uninstall virtualbox no problem for me.

orbital_71 said:
But if vmware is a good virtual machine to use then i just follow u with it. i can just uninstall virtualbox no problem for me.
Click to expand...
Click to collapse
OK...I got home and booted into Windows for the first time in a few weeks to do this. I am going to do an install, just to see if I get any errors come up. Not saying its something you did or didn't do, maybe a bad download. I got my VirtualBox from HERE
Updating the OP here in a few minutes...

ItzCrooK2UxD said:
OK...I got home and booted into Windows for the first time in a few weeks to do this. I am going to do an install, just to see if I get any errors come up. Not saying its something you did or didn't do, maybe a bad download. I got my VirtualBox from HERE
Updating the OP here in a few minutes...
Click to expand...
Click to collapse
i install this version VirtualBox-4.2.0-80737-Win.exe

orbital_71 said:
i install this version VirtualBox-4.2.0-80737-Win.exe
Click to expand...
Click to collapse
When you open VirtualBox does it show your Linux install on the left side? Also are you getting to a terminal prompt when it tells you this? If it does give you a terminal prompt try typing
sudo dpkg-reconfigure virtualbox-dkms [ENTER]
sudo dpkg-reconfigure virtualbox[ENTER]
Click to expand...
Click to collapse

ItzCrooK2UxD said:
When you open VirtualBox does it show your Linux install on the left side?
Click to expand...
Click to collapse
No terminal prompt when i install it, i never install on mine startup bar but on mine desktop screen there are. Anyway tonight when i reach home i uninstall mine virtualbox and try install the amd64 version and see how to see whether is the version problem not.
Sent from my LG-P990

Bro, one thing i don't understand since i already dual boot window and ubuntu. When i try to install ubuntu inside virtualbox why must i install ubuntu again inside virtualbox with the iso. and repeat the installation for ubuntu again. Wasn't there suppose a walk through with it? Tks
Sent from my LG-P990

orbital_71 said:
Bro, one thing i don't understand since i already dual boot window and ubuntu. When i try to install ubuntu inside virtualbox why must i install ubuntu again inside virtualbox with the iso. and repeat the installation for ubuntu again. Wasn't there suppose a walk through with it? Tks
Sent from my LG-P990
Click to expand...
Click to collapse
You need to reinstall Ubuntu on to the Virtual disk you are creating, because the virtual machine is not looking at your entire disk. It only sees what you tell it to see on the virtual disk.
Also I edited my second post to include a walk through of a VirtualBox install

Bro, in step 8 installation of ubuntu inside virtualbox, if i choose erase. What will be erase of this selection? Tkd
Sent from my LG-P990

orbital_71 said:
Bro, in step 8 installation of ubuntu inside virtualbox, if i choose erase. What will be erase of this selection? Tkd
Sent from my LG-P990
Click to expand...
Click to collapse
It will format your virtual hard disk. Sounds risky but its not. Basically with a virtual machine the emulator (VirtualBox, in this case) uses a section of your hard disk and creates your virtual machine. The virtual machine has most of the capabilities as the host machine (your physical PC that you boot up), but is limited to the resources that you want to allow it to use (EX. How much RAM do you want to dedicate to your virtual machine, how much disk space will you allow it to have. So erasing it basically means it is going to clear that space within that virtual machine. It has no effect on other Windows or Linux OS' you may be using within the emulator...does that make sense? Bottom line, yes its safe to erase and in your particular case I would encourage it.

ItzCrooK2UxD said:
It will format your virtual hard disk. Sounds risky but its not. Basically with a virtual machine the emulator (VirtualBox, in this case) uses a section of your hard disk and creates your virtual machine. The virtual machine has most of the capabilities as the host machine (your physical PC that you boot up), but is limited to the resources that you want to allow it to use (EX. How much RAM do you want to dedicate to your virtual machine, how much disk space will you allow it to have. So erasing it basically means it is going to clear that space within that virtual machine. It has no effect on other Windows or Linux OS' you may be using within the emulator...does that make sense? Bottom line, yes its safe to erase and in your particular case I would encourage it.
Click to expand...
Click to collapse
Ok and i should go with ur recommendation for 100gb space if i am gonna compile rom in step 4 right? Thanks u so much Bro.
Sent from my LG-P990

orbital_71 said:
Ok and i should go with ur recommendation for 100gb space if i am gonna compile rom in step 4 right? Thanks u so much Bro.
Sent from my LG-P990
Click to expand...
Click to collapse
If you are going to be doing ROM development and compiling I would really lean more towards a dual boot than a virtual machine. Compiling is CPU intensive and on a virtual machine you aren't just running one operating system with the resources your computer has, but now you're talking about running two OS' and putting a heavy CPU load on one of them.
To answer your question, 100GB should be enough, but I do not know how development will go in a virtual machine...I have no experience in this. Perhaps someone who has developed on a virtual machine can chime in.

[Q] Trying to install android x86 on Lenovo Yoga 2 Pro

Hi.
Sorry for my bad english!
First i tried android-x86-4.4-RC2 iso + followed the tutorial from here: https://groups.google.com/forum/#!msg/android-x86/D85Jq02cLrE/RhTWtOjH3H0J
(and downloaded the kitkat_install_package.zip in link above...)
none of these worked.
Then i tried android-x86-4.4-r2.img (.img; which is the efi version not the iso version because im using gpt and uefi and dual booting win8.1 and ubuntu 14.10 with grub...)
i booted live android and unlike the other 2 images i used before, live acctually worked! so i did the instruction in this toturial:
https://groups.google.com/forum/#!topic/android-x86/GrPdnpa6XBM
i installed android on another usb with ext3 format and copied the files from that usb to a 16gb ext2 gpt partition on my hard drive (yoga 2 pro's ssd) , (also tried ext3)
First i added these grub entries:
Code:
menuentry "Android KitKat" {
set root=(hd0,8)
linux /android-4.4-r2/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/android-4.4-r2 DATA= video=-16
initrd /android-4.4-r2/initrd.img
}
It didn't worked; when i selected android entry from grub same stuff that appear on live appeared :
. . . . . . (some code) . . .
A N D R O I D [email protected]:/
then instead of that android logo that shines appear (splash screen) , it gives me a black screen! (monitor's light won't turn off, its just black...)
i tried a lot of grub entries (im not sure if this is what their name is)
including the codes in this toturial:
http://forum.xda-developers.com/showthread.php?t=2703270
Code:
set root='(hd0,4)'
search --no-floppy --fs-uuid --set=root e1f9de05-8d18-48aa-8f08-f0377f663de3
linux androidx86/kernel root=UUID=e1f9de05-8d18-48aa-8f08-f0377f663de3 quiet androidboot.hardware=generic_x86 SRC=/androidx86 acpi_sleep=s3_bios,s3_mode
initrd androidx86/initrd.img
i tried the codes from my working live android usb (from android usb, android live entry selected, i pressed e in grub and write down it's codes) :
Code:
search --file --no-floppy --set=root /system.sfs
linuxefi /kernel root=/dev/ram0 androidboot.hardware=android_x86 sdhci.debug_quirks=0x8000 quiet DATA=
initrdefi /initrd.img
i even mixed all of these codes that i mentioned and IT DIDN'T WORKED!
tried booting the android that i installed on my usb (not android live, the one i installed with my other usb as i mentioned) same thing happens!
I really want android on my yoga2p because working with it's 13inch touchscreen and its speedy cpu and ssd was really awesome i really enjoyed it!
i need your help guys, i would really appreciate it
thanks in advance.

Hi.
Solved my problem with yoga 2 pro :
groups.google.com/forum/#!msg/android-x86/UWwxam-IVqk/KaCatJUAhOcJ

Help- Stuck on boot in terminal

I have installed phonix os via exe file then click reboot.
On 1st boot it was showing be only black screen and nothing coming up. So I forcefully restrat it. Then it showing be me this screen.
How can I solve it?

rabin69x said:
I have installed phonix os via exe file then click reboot.
On 1st boot it was showing be only black screen and nothing coming up. So I forcefully restrat it. Then it showing be me this screen.
How can I solve it?
Click to expand...
Click to collapse
Cursor might be active ,type
Code:
logcat
And check output

I have the same problem, after that screen the backlight of the lcd blinks 2 times and then my laptop restarts. I tried different settings in grub.cfg and it shows some signs of life only if I put the parameter nomodeset, I see phoenix os logo and then the hdd turns off, if i put video=-16 video=LVDS-1:d I listen the hdd working but the screen is completely off. I think that my gpu is not supported. I don't know compile the drivers. I have too much troubles with amd hd8180. Any solution?
update: I tried the x32 version and there are many problems on boot:
service media.audio_flinger died
accept_ra_rt_table no such file or directory
libgapi has text relocation
the icing on the cake is signal 11 segmentation fault refferred to surfaceflinger

Hi, I was have a same problem when i install phoenix 2.5.3 to my alcatel plus 12 2 in 1 notebook ( n3350/4gb ram/32 internal storage + 32Gb ext / 11.6 " FHD / win 10 home ) after finish install the i boot, i will be black screen with cursor in the left corner event i restart again still same, nothing else happening, i allready try to install in internal, external & flash disk the result still the same. Can any one help me ? before this i install in my lenovo notebook G40-30 AMD A8 work fine.
linuxandroid said:
I have the same problem, after that screen the backlight of the lcd blinks 2 times and then my laptop restarts. I tried different settings in grub.cfg and it shows some signs of life only if I put the parameter nomodeset, I see phoenix os logo and then the hdd turns off, if i put video=-16 video=LVDS-1:d I listen the hdd working but the screen is completely off. I think that my gpu is not supported. I don't know compile the drivers. I have too much troubles with amd hd8180. Any solution?
update: I tried the x32 version and there are many problems on boot:
service media.audio_flinger died
accept_ra_rt_table no such file or directory
libgapi has text relocation
the icing on the cake is signal 11 segmentation fault refferred to surfaceflinger
Click to expand...
Click to collapse

Stuck also on boot: cannot detect the phoenix
Hello, I am trying to install phoenix as a dual boot on an HP X2. I have downloaded the latest version from the website (64bit version) and it installs normally on the hard drive. At reboot, I went to the BIOS and disabled the secure boot (it is UEFI boot by the way). I then restarted and I get the dual boot option. I select phoenix and I get the "Detecting Phoenix OS prompt, only that I got dots that populate the entire screen (I even let it run overnight with no luck).
I then tried to install phoenix onto a SDHC 16GB thumb drive. Install went fine but at boot, the BIOS does not have the option to boot on SD card, only on USB. So, I placed the SDHC card onto a USB adapter and it boots onto the SDHC via USB but I have the same issue: I got dots that populate the entire screen.
Any idea of what I could do to be able to install it? I want it on my drive.
Thanks.
PC is: HP 10-p018wm (walmart edition of HP pavilion X2).
x5-Z8350, 4GB RAM, 64GB eMMC

Hi I am also stucked at A N D R O I D x86_64:/ #
anyone can help?

Did anyone find a solution for this yet please help i tried everything :crying:
Edit : i'm using the latest version of phoenix os

I am also experiencing boot issues with Phoenix OS. I've also tried RemixOS and Bliss. All show the same issue. I'm using a Lenovo Yoga 920.
Trying to think outside of Android, specifically, I started looking at compatibility with Linux in general and the Yoga device. It looks like (and I could be wrong here...pretty new to Android_x86) the kernel needs to be up to v. 4.15. (https://forums.lenovo.com/t5/forums...Special_Interest_Linux/thread-id/10264/page/2)
If anyone has any ideas, I'm open to testing.

I got mine to boot by editing the grub file, adding nomodeset and editing vga to vga=ask then picking the 1024x768 32 bit option. Anything else and it won't pass the terminal.
Intel i5-4210u
Intel HD / Nvidia 840m
Legacy BIOS

staffwand said:
I got mine to boot by editing the grub file, adding nomodeset and editing vga to vga=ask then picking the 1024x768 32 bit option. Anything else and it won't pass the terminal.
Intel i5-4210u
Intel HD / Nvidia 840m
Legacy BIOS
Click to expand...
Click to collapse
So, is that located in "C:\Program Files\phoenixstart\config"? In that folder, I see grub.cfg and grub-64.cfg. Since I'm on a 64 bit OS, I assume it's the grub-64.cfg that I need to modify.
Finally, I just want to make sure I have the parameters set properly. Can you please verify the line I am changing is from this:
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
to this:
linux /EFI/PhoenixOS/kernel quiet nomodeset root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=ask
I am also unsure if I can set my BIOS to legacy. I'll have to double check.

hotwired34 said:
So, is that located in "C:\Program Files\phoenixstart\config"? In that folder, I see grub.cfg and grub-64.cfg. Since I'm on a 64 bit OS, I assume it's the grub-64.cfg that I need to modify.
Finally, I just want to make sure I have the parameters set properly. Can you please verify the line I am changing is from this:
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
to this:
linux /EFI/PhoenixOS/kernel quiet nomodeset root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=ask
I am also unsure if I can set my BIOS to legacy. I'll have to double check.
Click to expand...
Click to collapse
so ? did it work ?

Jinreu said:
so ? did it work ?
Click to expand...
Click to collapse
It doesn't look like modifying the file(s) in "C:\Program Files\phoenixstart\config" had any impact. To test which file was being read, I changed the timeouts on both from the default timeout of 5 seconds to 10 and 15. When I rebooted, the countdown was still 5, so there is another file somewhere else that's being read.
There was an option to change the parameters from GRUB. I went into that and modified it to have the nomodeset and vga=ask, however, that didn't do it for me.
Going to try going into the BIOS to see if I can get it changed to legacy. I'll let you know how it goes.

hotwired34 said:
It doesn't look like modifying the file(s) in "C:\Program Files\phoenixstart\config" had any impact. To test which file was being read, I changed the timeouts on both from the default timeout of 5 seconds to 10 and 15. When I rebooted, the countdown was still 5, so there is another file somewhere else that's being read.
There was an option to change the parameters from GRUB. I went into that and modified it to have the nomodeset and vga=ask, however, that didn't do it for me.
Going to try going into the BIOS to see if I can get it changed to legacy. I'll let you know how it goes.
Click to expand...
Click to collapse
it didn't work for me either, even when i change to legacy i tried typing 'logcat' the logs are going too fast i can't read anything

i see something like this in the logs
Code:
I ServiceManager: service 'media.audio_flinger' died
I ServiceManager: service 'media.player' died
I ServiceManager: service 'media.resource_manager' died

hotwired34 said:
It doesn't look like modifying the file(s) in "C:\Program Files\phoenixstart\config" had any impact. To test which file was being read, I changed the timeouts on both from the default timeout of 5 seconds to 10 and 15. When I rebooted, the countdown was still 5, so there is another file somewhere else that's being read.
There was an option to change the parameters from GRUB. I went into that and modified it to have the nomodeset and vga=ask, however, that didn't do it for me.
Going to try going into the BIOS to see if I can get it changed to legacy. I'll let you know how it goes.
Click to expand...
Click to collapse
It'd be in the hidden ESP partition. I'd test with just adding nomodeset by editing the entry before it boots [e on grub menu]

hotwired34 said:
So, is that located in "C:\Program Files\phoenixstart\config"? In that folder, I see grub.cfg and grub-64.cfg. Since I'm on a 64 bit OS, I assume it's the grub-64.cfg that I need to modify.
Finally, I just want to make sure I have the parameters set properly. Can you please verify the line I am changing is from this:
linux /EFI/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
to this:
linux /EFI/PhoenixOS/kernel quiet nomodeset root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=ask
I am also unsure if I can set my BIOS to legacy. I'll have to double check.
Click to expand...
Click to collapse
Yeah, looks good. Did it boot for you?
---------- Post added at 07:05 AM ---------- Previous post was at 06:06 AM ----------
I actually used Remix OS' grub to set the boot options. Edited one of the boot options to:
find --set-root /PhoenixOS/kernel
kernel /PhoenixOS/kernel root=/dev/ram0 androidboot.hardware=android_x86 REMOUNT_RW=1 SRC=/PhoenixOS quiet nomodeset vga=ask
initrd /PhoenixOS/initrd.img
boot

staffwand said:
Yeah, looks good. Did it boot for you?
---------- Post added at 07:05 AM ---------- Previous post was at 06:06 AM ----------
I actually used Remix OS' grub to set the boot options. Edited one of the boot options to:
find --set-root /PhoenixOS/kernel
kernel /PhoenixOS/kernel root=/dev/ram0 androidboot.hardware=android_x86 REMOUNT_RW=1 SRC=/PhoenixOS quiet nomodeset vga=ask
initrd /PhoenixOS/initrd.img
boot
Click to expand...
Click to collapse
It didn't boot. However, looking at your grub entry...it looks completely different. Here's my whole grub entry for PhoenixOS:
menuentry "Phoenix OS" {
search --set=root --file /EFI/PhoenixOS/kernel
linux /EFI/PhoenixOS/kernel quiet nomodeset root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=ask
initrd /EFI/PhoenixOS/initrd.img
}
Would you mind posting your whole grub entry for PhoenixOS?

I too am getting almost a similar problem. I installed the latest version 2.6.0 via the exe installer. It shows the line:
Detecting android x86... Found at dev/sda5
And the pc automatically restarts?... Any way to get it fixeD?

man , how can i fix this problem ? stuck at A N D R O I D x86_64:#

anyone please share solution for this? i am also facing same problem