Related
Hello everyone,
Can anybody explain how dual boot works.
Whether android is booted on top of windows mobile as some upper layer or does it rely on hardware as it is native OS installed. Is there any difference between native android phone and android booted from windows mobile, except missing some functionality?
Thanks
Cheers!
when you use heret to boot android winmo is shut down, then android runs as the native os, this is nessesary as without android being flashed to the devices rom there would be no way to boot it obviously. in theory if android is made stable enough on a device it would be possible to make an android rom for that device
To add some additional information:
You are probably talking about the Gen Y dual boot software.
Gen Y dualboot is nothing more than an application that runs immediately after Windows is booted. So before you get to the dualboot, Windows is actually already booted.
Then, after pressing Android, Windows Mobile launches the Haret, by which Windows Mobile shuts down and the Android Kernel loads up.
So to have it in a schematic view:
-----------------------------------------------------Stay in Windows Mobile
Kernel WM --> WM booted --> DualBoot <
-----------------------------------------------------Launch Android Kernel --> Android booted
Hello xda,
Recently We have heard about ubuntu for phones and tablet now this is the time that the first developer preview has rolled out!
Your device must be unlocked! (you can do thiscalso by installing this preview!)
Supported devices are:
- Galaxy Nexus maguro
- Nexus 4 mako
- Nexus 7grouper
- Nexus 10 Manta
What are the Fuetures at the moment?
Shell and core applications
Connection to the GSM network (on Galaxy Nexus and Nexus 4)
Phone calls and SMS (on Galaxy Nexus and Nexus 4)
Networking via Wifi
Functional camera (front and back)
Device accessible through the Android Developer Bridge tool (adb)
How to get the developer preview image?
Deploying Image to Device
To install the Ubuntu Touch Developer Preview on your device, you will need to execute the command below. Please note, this will wipe the contents of the device so ensure you have made a back-up. To install and get updates,
run the following command: phablet-flash -b The -b performs a full bootstrap on the device.
If the device is already unlocked it will carry on.*If you have already bootstrapped once and want to install a daily just do:
phablet-flash, This will deploy the latest build onto your device. Your device should reboot into the Ubuntu Unity shell.
Note: the files are saved in*Downloads/phablet-flash.
Rolling back to android?
The Ubuntu Touch Preview image is not for everyone and may not suit your current needs (yet). If you wish to roll back to an Android factory image, follow these steps:
- Recall the version that was installed before flashing.
- Download the factory image corresponding to your device's model and version (initial table has links).
- Ensure the device is connected and powered on.
- Extract the downloaded file and cd into the extracted directory.
- run*adb*reboot-bootloaderrun*./flash-all.sh*(use*sudo*if lack of permissions on the workstation don't allow you to talk to the device).
Your device should boot into Android after the process is finished.
For more info see:
https://wiki.ubuntu.com/Touch/Install?action=show&redirect=TouchInstallProcess
Left behind in the comments what you think about Ubuntu Touch
Greetings SK.
Porting Ubuntu Touch:
https://wiki.ubuntu.com/Touch/Porting
Dual booting Windows RT and RT 8.1 (almost)
I was original working on dual booting RT from internal flash and from SD card
by adding extra entries in the bcd store and a ‘copy’ of windows on the SD card
Note it actually still boots from the system partition on the internal flash but tries to boot an alternate Windows installation from \windows on the SD card
http://forum.xda-developers.com/showthread.php?t=2343101
But now moved on to dual booting Windows RT and RT 8.1 (both from internal flash)
and almost have it working
Installing the RT 8.1 Preview saves the old OS in \windows.old\windows
Or rather saves most of it, but not all
So you need to pre-save much of the original \windows elsewhere, using the recovery environment, BEFORE installing 8.1
as certain important bits seem to get stripped out of windows.old
Then use the same technique of adding entries to the bcd store to allow the system to boot from \windows.old\windows
It wont be perfect as it will pick up certain hard coded \windows stuff and also will pick up the wrong \Program Files
but should be just about usable, especially in desktop mode which is the reason for keeping the original OS
It does boot, but doesn’t pick up the Start screen properly, so need further work on that
Could do it properly if we shrank the C: volume and set up a new dedicated volume for the alternate OS
Original RT
Use recovery environment to make a copy of
\windows\system32\*
\windows\system32\config\*
\windows\system32\drivers\*
Would be easier to copy \windows /s but then get a bloated mess due to the WinSxS hardlinks
Install 8.1 Preview
copy the copied data over the top of \windows.old\windows
will be lots of access denied for files already there
but will copy the important missing files
including the registry hives, ntoskrnl.exe, winload.efi [need the old winload.efi as the new one wont accept the signature of the old ntoskrnl etc]
Suspend bitlocker (if in use)
manage-bde -protectors -disable c:
bcdedit /copy {current} /d "Windows RT 8.0 hack”
note the new guid
bcdedit /set {guid} recoveryenabled no
bcdedit /set {guid} path \windows.old\windows\system32\winload.exe
bcdedit /set {guid} systemroot \windows.old\windows
Restart (or shift restart)
Select the Windows RT 8.0 hack
The original RT OS boots but no Start screen
but is running and a dot will follow your finger
Need to modify the windows.old registry and fix up something
To be investigated
Can also test and develop this with Windows 8.1 Intel on a PC
That also doesn’t get the full Start screen on the hacked (barstardised) alternate boot back to 8.0
Also best to rename \windows.old to something else, as \windows.old gets removed after a few days
Note, this is a hack
The correct method would be to set up seperate OS partition on the internal flash drive
(but a bit small to do that)
Or to get the alternate OS to boot from SD card
Also as mentioned in the 8.1 jailbreak thread, RT 8.1 wont run RT 8.0 OS binaries or office binaries
(due to the new and more restrictive signatures needed by RT 8.1)
You can create a VHD and extract recovery WIM there to get a complete copy of OS. Earlier I've played with that with success.
One note: you can't use the recovery to restore the original "main" windows while BCD has an VHD entry - it fails with an undescriptive error.
My windows8.1 recovery file is .esd not .wim.So I must install windows8.1 first then make a windows8.0 vhd?And microsoft says windows rt cant boot from VHD.
windowsrtc said:
My windows8.1 recovery file is .esd not .wim.So I must install windows8.1 first then make a windows8.0 vhd?And microsoft says windows rt cant boot from VHD.
Click to expand...
Click to collapse
Yes, just take WIM from the recovery partition of 8.0, extract it to VHD, then upgrade to 8.1
I was playing with the windows PE - it could boot from VHD. So I assume that "big" RT would boot too, but had no mood to finish tests.
Enjoy this while you can, because I suspect that the Windows 8.1 final release will include a firmware update that locks out booting 8.0 forever on your device.
Also, disable Windows Update or change it to manual mode, on both 8.0 and 8.1!! I think Microsoft will release RT 8.1 as a free upgrade that is forced upon 8.0 by being labeled an important Windows update.
I think I am strong enough to return my surface to microsoft and get my money back if microsoft block my windows 8.0.And then I will say goodbye to any windows rt device.
Myriachan said:
.. I suspect that the Windows 8.1 final release will include a firmware update that locks out booting 8.0 forever on your device.
Click to expand...
Click to collapse
Definitely not, at least not immediately after the 8.1 official release. As this would cause lots of complains and support calls from people not being able to use the recovery USB disks in the case if the upgrade process goes wrong or if they'd like to return to backup.
mamaich said:
Definitely not, at least not immediately after the 8.1 official release. As this would cause lots of complains and support calls from people not being able to use the recovery USB disks in the case if the upgrade process goes wrong or if they'd like to return to backup.
Click to expand...
Click to collapse
Microsoft is copying Apple--that is the whole reason Windows 8 exists--and Apple is even worse than this, giving Microsoft plenty of precedent. On iPads, not only can you not downgrade after you upgrade, you can't even do a restore to your current version. If your iOS device is corrupted, you have to upgrade to the newest version.
Apple's enforcement of this mechanism is that during the reflash operation, the boot ROM generates a random challenge that needs to be answered by Apple's servers with public-key cryptography. Therefore, you can never flash a version of the OS to your device unless Apple is authorizing that version at that particular moment.
I don't think that Microsoft will add a phone-home requirement to restores like Apple does, but I think that they will lock out the old version.
Apple does not officially allow you to make a backup copy of your OS including all your data to a bootable USB. So they don't need to care about user-made backups. While MS recommends doing this before upgrade - so they'd need to support a downgrade path.
Anyway we see one improvement in Win8 development infrastructure. MS have published the whole Windows 8.1 RT WDK (a driver-maker kit), including all import libraries for usermode apps. So you can create a driver for WinRT or a normal desktop app without old hacks with manual import-library creation (of cause you'll need a working "jailbreak" or a development device). Have they done this as a mistake or intentionally - I don't know, but anyway go and grab your copy
windowsrtc said:
My windows8.1 recovery file is .esd not .wim.So I must install windows8.1 first then make a windows8.0 vhd?And microsoft says windows rt cant boot from VHD.
Click to expand...
Click to collapse
ESD file is an encrypted WIM file. The 8.1 upgrade process has trashed the recovery partition upgrading it to 8.1
Today I'll try to revert to 8.0 (fortunately I've made a recovery USB before upgrade), then try to make an 8.1 VHD to use it in parallel with 8.0.
I'll publish instructions when (or if) I'll succeed.
And yes, seems that 8.1 stopped to support booting from VHD. At least I was unable to do this from the first attempt. But I had success with VHD in 8.0, so I'll start from reverting to it.
Here is a simple method of having both 8.0 and 8.1 on the same device. You'll need a 64Gb device.
I've decided not to play with VHD any more and just added the another partition.
So here is what to do (do everything in a running Windows 8.0, not in a command line mode):
1. manage-bde -protectors -disable c:
2. Shrink your OS partition from disk manager GUI leaving about 20 Gb free space.
3. Create new partition over the free space, format it to NTFS, add a drive letter, say, F:
4. Obtain image.wim from your recovery USB or from a recovery partition and do:
Dism /apply-image /imagefile:full-path-to-your-backup-install.wim /index:1 /ApplyDir:F:\
5. Add the needed entries to boot-menu:
bcdedit /copy {current} /d "Windows RT 8.0 copy”
bcdedit /set {guid} device partition=F:
bcdedit /set {guid} osdevice partition=F:
bcdedit /timeout 5
6. Reboot
Select the second OS - you'll see that it boots, but you'll get an error. This is due to the wrong drive letter assignments. Your backup image "knows" that the first partition has drive letter C:, while now this letter should be assigned to the second one. It is easy to fix this, read this article: http://support.microsoft.com/kb/223188. Just boot to a command line environment, run regedit, select HKEY_USERS, use "load hive" menu to load "\Windows\System32\config\SYSTEM" from the second partition (when asked how to name the key - type any name you like), then rename "\DosDevices\C:" to "\DosDevices\Z:" and "\DosDevices\D:" to "\DosDevices\C:" (they are located in HKEY_USERS\your-loaded-key\MountedDevices). Unload hive, reboot - and everything would be fine.
You'll have two OSes, I'd recommend to upgrade the one located on the first partition to 8.1 and leave the newly created one as 8.0, so later, when you'd decide to stay on 8.1 you'd just would need to delete a second partition and expand the 8.1 over the remaining space.
Usual note: be careful when playing with the partitions and registry. As you can't kill the device even by deleting all the partitions (you can always boot from usb and recover them manually) - the recovery process is rather complex for the ordinary user.
mamaich said:
Here is a simple method of having both 8.0 and 8.1 on the same device. You'll need a 64Gb device.
I've decided not to play with VHD any more and just added the another partition.
...
Click to expand...
Click to collapse
Thanks! That worked perfectly, even on my 32Gb Surface RT. :laugh:
I only had to tweak the 5th step a bit; on the second and the third line I had to change "{guid}" to "{current}" if I remember correctly.
But afterwards I didn't even get the error you spoke about, the dual boot worked directly.
I also enabled the classic boot menu with "bcdedit /set {default} bootmenupolicy legacy", as the new one first boots and then lets you choose, which can be time consuming.
The problem with this legacy bootloader on the surface rt is that the touchcover doesn't work, you can select a OS with the volume buttons of the tablet, but you can't press enter.
It works with an usb keyboard, but It would be nice if the touchcover would work.
Hey mates!
I wanted to try out 8.1 final with dual boot on my 64GB surface RT. Are there any updates on this topic?
I would take the instructions from @mamaich and wanted to know if we can use the touch cover to select the OS by now?
If not, we could create 2 scripts for changing the default OS.
1) Placed on 8.0 Desktop: Switch default OS to 8.1 and reboot
2) Placed on 8.1 Desktop: Switch default OS to 8.0 and reboot
Cheers
Blade
So far so good. I got dual-boot 8.0 and 8.1.
mamaich said:
... then rename "\DosDevices\C:" to "\DosDevices\Z:" and "\DosDevices\D:" to "\DosDevices\C:"...
Click to expand...
Click to collapse
I did not have to do this step. Doesnt matter which Windows i load, it sets the active Windows Partition to C and the non active one to F or D
Here I am on my main sytem (Jailbroken RT 8)
Click to enlarge
Here I am on the newly created untouched System 8.1
Click to enlarge
And for {guid} in step 5 line 2 and 3 i inserted the ID given me in the Output of line 1...
For those who got Problems with shrinking the partition: deactivate Pagefile
How to deactivate Pagefile:
press search
type in "advanced"
press on "Settings"
click on "View advanced System Settings"
click on the tab called "Advanced"
click on "Settings" in "Performance"-section
click on "Advanced"-tab
click on "Change" in "Virtual Memory" section
untick "Automactically manage ..."
set bullet-point to "No paging file"
click on "Set"
3 times OK and then reboot
Don't Forget to set it back after resizing!!
A quick warning: you'll probably want to re-enable paging after resizing the partitions. Most RT devices only have 2GB of RAM. Even with just web browsing, email, etc. you could end up hitting that if you're a heavy browser tab like me. Gaming, really big Excel spreadsheets, running desktop apps via jailbreak (why else keep 8.0 around?) and so on are much more likely to hit that limit. When apps hit the limit, and the OS can't increase the commitable memory because there's no paging file to back data swapped out of RAM, stuff will start crashing.
Yes, ofc. I write a warning in my list (I thought it would be self-explaining). Thank you master.
btw I did it. Got dual-booting JB8.0 and RT8.1. everything works very nice. (Even though i used 2nd Partition for win8.1 with only 14,6GB, because I wanted to Keep my highly modified and customized winRT8.0)
For those who want a shortcut on the Desktop to get to advanced boot Options: download shortcut
Works in both 8.0 and 8.1, if C:\ is root path for each (see my last post)
This way you can set the timeout of your boot-menu to 0 and set the OS you are using mainly as Default. To Switch OS simply use the shortcut, OR: open Charms-bar - Settings - Power - hold SHIFT while clicking on restart
After that: [Could not take a screenshot]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, everyone.
Tomorrow I will get a surface RT with windows 8.1 already. Is it possible to make the dual boot like this too?
If it's a gen1 RT, yes (use the 8.0 recovery image to install it). If it's a gen2 ("Surface 2") then no.
Featured on XDA-Portal
Hi all !
Welcome to the tutorial of how to install Android x86 !
I've written this extensive guide, it is as detailed as possible and it is written as easy and as understandable for new user.
This guide is, however does not put guarantee of any action you've done outside the guide itself. Anything such as partitioning, OS installing or uninstalling is not guaranteed by me or by anyone at XDA. You're doing this at your own will.
Preparations :
1. Any computer / device that supports installation via flash driver / disc (or have enough space for VM)
2. Any media that is mentioned below (either flash drive, CD / DVD, or VM)
3. Android x86 ISO
4. 2 GB of free or clean partition is recommended (you can use more than 2 GB to increase internal storage)
1. Download Android x86 ISO.
You can download it here
If your device isn't listed there, download Generic ICS build here : Click ! [You need to unzip after download]
The newest KitKat build is unified and it's also generic. It supports wider range of hardware, but it does not support LAN device (yet). You can download it here
Follow the guide with your preferred installation method.
If you're using USB stick / Flash Drive :
2. Download UNetbootin
You can download it here : Click !
On Ubuntu (11.04 and higher, or its derivatives) you can type : sudo apt-get install unetbootin
On Arch (or its derivatives) type : pacman -S unetbootin
3. Run UNetbootin, select the Android x86 ISO
4. Select USB drive (make sure you don't select your HDD partition), then click OK
5. The UNetbootin will copy and install Android x86 live image & installer to your flash drive
6. Reboot your device after the process is completed
7. Boot to Boot Device Selection (in BIOS image), after you entered it, select your flash drive
8. There will be a GRUB menu generated by UNetbootin, select Install Android x86 to hard disk
9. Wait until it loads
10. Select partition to install Android x86
11. If you're unsure, don't format the partition
12. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you've installed GRUB, do not select yes.
13. Another prompt, 'make system r/w', select yes (this enables root and read write access to your system partition)
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual sdcard, input 2GB (maximum size)
15. Reboot your device
If you're using CD / DVD
2. Burn the Android x86 ISO
3. Reboot your device, go to Boot Device Selection menu, select the CD / DVD
4. You will see Android x86 GRUB menu, select Install Android x86 to hard disk
5. Wait until it loads
6. Select partition to install Android x86
7. If you're unsure, don't format the partition
8. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you've installed GRUB select no (installing it will break your GRUB configs)
9. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
10. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 2 GB (maximum)
11. Reboot your device
If you're using it as virtual machine :
2. Set up the VM (RAM set to min 512 MB), tweak the configuration to match your need
3. Make sure you've loaded the ISO file in the VM menu, load the VM
4. A GRUB menu generated by Android x86 will appear, select the last option (Installation - Install Android x86 to hard disk)
5. Wait until it loads
6. Create a new partition (Navigate to New, , set to maximum size, navigate to write, done, navigate to quit)
7. Install Android x86 to the new partition
8. Format the partition to ext4
9. Answer 'yes' to 'Install bootloader GRUB bla-bla-bla'
10. Answer 'yes' again to 'make system r/w' (enables root and read write access to your partition)
11. If you're asked for sdcard, then input 2GB (the maximum size is 2GB, if your partition is smaller input suitable size for your partition)
12. Reboot when the process is done
How to add Android x86 to GRUB Menu
For GRUB 1.97 - 1.99 / 2.00
1. To make it easy, install GRUB Customizer
Type these into terminal emulator :
Code:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
2. Open GRUB customizer, make a new GRUB entry.
3. Open 'Sources' tab, type these :
Code:
[B]set root='(hd0,4)'[/B]
search --no-floppy --fs-uuid --set=[B]root e1f9de05-8d18-48aa-8f08-f0377f663de3[/B]
linux [B]androidx86[/B]/kernel root=UUID=[B]e1f9de05-8d18-48aa-8f08-f0377f663de3[/B] quiet [B]androidboot.hardware=generic_x86[/B] SRC=[B]/androidx86[/B] acpi_sleep=s3_bios,s3_mode
initrd [B]androidx86[/B]/initrd.img
Pay attention for the bolded part, here's what to change :
1. set root='(hd0,4)' : Change the (hd0,4) to partiton Android x86 is installed.
The hd0 means sda, so if you install it to sdb, it'll be hd1 and so on.
The hd0,4 means the partition number, in my case, hd0,4 means sda4. So if you install it on sda6, it'll be hd0,6.
2. --set=root e1f9de05-8d18-48aa-8f08-f0377f663de3 : The random number here is the UUID of partition Android x86 is installed
You must change it to correct UUID, you can easily got UUID by creating new entry in GRUB Customizer then go to Options tab, then select the 'Linux' option in dropdown. You'll see partition dropdown, select your partition. Open the source tab, you'll see the UUID there.
3. androidx86/ : The root of Android x86
Change it into your Android x86 root. You can see what's your Android x86 root by navigating to Android x86 partition, and you'll see a folder name started with 'android', that's the root of your Android x86
4. androidboot.hardware : Your device, of course.
Note : If you're using Android 2.3 - 4.0.3, change it to androidboot_hardware
Here's the list of hardware :
Code:
- generic_x86 : If your hardware isn't listed, use this
- eeepc : EEEPC laptops
- asus_laptop : ASUS laptops (supported ASUS laptops only)
GRUB 2.0 tutorial is the same like GRUB 1.97-1.99.
-------------
FAQ
-------------
Q : Does this work on my device ?
A : Try it ! There's generic build which supports many device.
Q : Which release should I pick ?
A : Generic is recommended (if your device isn't listed in download list), if your device is supported (like EEEPCs for example), pick one for your device. Do take a note that newer builds uses unified image, which means it supports wide range of hardware.
Q : Will this overwrite my old OS ?
A : As long as you install it in different partition and you did the right setup, you are good to go !
Q : Why does my network / touchscreen / mouse / etc, doesn't work ?
A : Mostly this is a driver problem. Try to use newer / older release. If it doesn't work, try different build for other device (there's a chance this will fix your problem)
Q : Does Android x86 works on USB disk (as a Live Image / as an OS itself) ?
A : It does, I have tested it on Gingerbread and ICS release.
Q : Why deep sleep / suspend doesn't work on my device ?
A : This is one of the issue on Android x86. The developer might be working on a fix.
Q : It doesn't work on a VM setup !
A : Check your configuration and virtual disk, Android needs at least 2GB of free space.
Q : Why does games feel choppy when played ?
A : This is because the game uses ARM libs / libraries which is not optimized for Android x86 (which uses ARM to x86 translator by Intel). On newer build, like unofficial Lollipop release doesn't include ARM to x86 translator, so it can't execute any ARM libraries or binaries.
Q : Android 4.4.2 RC-1 hangs on bootscreen (the flashing Android logo / tty1 terminal) !
A : Check your hardware, if you're using x64 probably the x64 isn't supported yet. Also, try using older release.
Q : There's no Play Store !
A : Sometimes, nighlies build (as Custom ROMs user calls it) is uploaded, this type of build doesn't have GApps. Also, if you're using deprecated release (old release), they have Android Market instead of Playstore.
Q : Can you flash .zips in this ?
A : You can, but it's not recommended.
Q : Play Store only have small amount of app !
A : Because Play Store detects your device as Android with a x86 CPU. This kind of CPU isn't widely used by apps in Play Store (most CPU in Android phone is ARM)
wow awesome guide :good:
Desktop
Does this also work on a desktop?
Rami1997 said:
Does this also work on a desktop?
Click to expand...
Click to collapse
Bro, any computer. Be it a desktop, netbook, ultrabook, MacBook, Linux computer, etc
F4uzan said:
Hi All !
I'm going to post a tutorial, how to install Android x86 to your laptop & netbooks (works on Personal Computer too).
So, let's start !
Preparations :
1. A working laptop & netbooks
2. R/W CD / Bootable USB stick (flashdisk)
3. Android x86 ISO
4. Free partition :
- 2 GB for Froyo - ICS
- 8 GB for JellyBean 4.2 - JellyBean 4.3
- 10 GB for KitKat 4.4.2
1. Download Android x86 ISO.
You can download it here : Click !
If your device brand is listed there, download Generic ICS build here : Click ! [You need to unzip after download]
If you're using USB stick :
2. Download UNetbootin
You can download it here : Click !
On Ubuntu (11.04 and higher) you can type : sudo apt-get install unetbootin
3. Run Unetbootin, select the Android x86 ISO
4. Select USB drive (instead of Hard Disk), then click OK
5. The UNetbootin will install Android x86 live image & installer to your USB stick
6. Reboot your device after the installation is completed.
7. Boot to Boot Device Selection (in BIOS image), after you entered it, select USB2.0 / USB4.0 / USB Disk (or something similiar)
8. There will be a GRUB like menu generated by UNetbootin, select Install Android x86 to hard disk
9. Wait until it to load
10. Select partition to install Android x86
11. If you're unsure, don't format the partition
12. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you're using Ubuntu, select no
13. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
15. Reboot your device
If you're using CD R/W
2. Burn the Android x86 ISO
3. Reboot your device, go to Boot Device Selection menu, select the CD / DVD
4. You will see Android x86 GRUB menu, select Install Android x86 to hard disk
5. Wait until it to load
6. Select partition to install Android x86
7. If you're unsure, don't format the partition
8. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you're using Ubuntu, select no
9. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
10. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
11. Reboot your device
I'll add tutorial how to add Android x86 to Ubuntu's GRUB menu. Stay tuned !
There's no screenshot, because the result may vary with your device.
Click to expand...
Click to collapse
Sorry if this has already been asked/answered but would this work on a Surface Pro (1st gen) or a Dell Venue 8 pro?
Windows
raghav kapur said:
Bro, any computer. Be it a desktop, netbook, ultrabook, MacBook, Linux computer, etc
Click to expand...
Click to collapse
And this doesn't delete windows right?
dodgebizkit said:
Sorry if this has already been asked/answered but would this work on a Surface Pro (1st gen) or a Dell Venue 8 pro?
Click to expand...
Click to collapse
Yes, it will work on both. Not sure about the touchscreen and the keyboard covers though
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
Rami1997 said:
And this doesn't delete windows right?
Click to expand...
Click to collapse
If you overwrite this Android installation over the Windows, then IT WILL DELETE WINDOWS.
But, if you create separate partitions for Windows and Android, then you can dual-boot.
I suggest that you run Android in a virtual machine rather than installing this way
Cool
Sent from my Nexus 5 using Tapatalk
Sounds great, can't wait to try it on my old laptops, thanks!
If you want Ubuntu Grub entry, see here : https://groups.google.com/forum/#!topic/android-x86/GrPdnpa6XBM
Use Li's kernel from here IF YOU ARE USING 4.4 on an UEFI system (<efivar> KP): https://groups.google.com/d/msg/android-x86/GrPdnpa6XBM/dA1ChqU1vu4J
All credits goes to there owners (not to me ).
GOOD LUCK
BTW, I have Vaio S (SVS 2012) and I can get WiFi working of I boot from legacy mode BIOS from an external HD w/ the original kernel, while it doesn't work of I boot it from UEFI w/ the custom kernel (since it can't boot w/out it) and doesn't work w/ either 4.3.X or 4.2.X. Can someone help me? (using Intel Centrino Advanced N 6235)
Thanks
Interesting
Anyone try to run this as a VM using either VMWare or VirtualBox?
sent from my hsvxo out in cbciioebd
Whoop!! Featured on portal!!
Sent from my LG-E430 using XDA Premium 4 mobile app
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
Could we set more for more space to install apps?
simon_lefisch said:
Anyone try to run this as a VM using either VMWare or VirtualBox?
sent from my hsvxo out in cbciioebd
Click to expand...
Click to collapse
Yep, I did... But when I tried to boot it it shows only attachment and stock on Android logo
Could someone please answer my question please, also can you try the OS before installing it on the hdd, like test it and reboot and then install it
Awesome... wud try it n post screen shots if i can :laugh::good:
i tell you sth.. i was able to make 2gb data partition only... and trying to change data.img in other programs to make it bigger but never succeded.. maybe there is some workaround to make data partition bigger... or to use swap with usb stick or sth..
i had installed android x86 kitkat on usb 8gb drive and works perfectly some apps just had problems with mouse pointer.. (i think those designed for android 2.3) just had this problem with only 2gb data partition...
Bootmgr is missing
unetbootin creates the boot image but my windows laptop doesnt detect it
jarusss said:
Yep, I did... But when I tried to boot it it shows only attachment and stock on Android logo
Click to expand...
Click to collapse
Same thing happened to me with Virtualbox. However, I shutdown the VM, unmounted the iso, and rebooted. After that, it worked. I used the 4.4 version.
Why isn't it as easy as on the pc ? on pc you just download the OS you want , you make it bootable with a program like Rufus (in a USB drive) you plug the USB on the pc/laptop, you follow the instructions and done. on smartphones/ tablets its too complicated you have to download a custom recovery , and why every rom is not compatible with every smartphone/ tablet?
andreas_xs said:
Why isn't it as easy as on the pc ? on pc you just download the OS you want , you make it bootable with a program like Rufus (in a USB drive) you plug the USB on the pc/laptop, you follow the instructions and done. on smartphones/ tablets its too complicated you have to download a custom recovery , and why every rom is not compatible with every smartphone/ tablet?
Click to expand...
Click to collapse
Installing custom roms and custom recovery maybe complicated at first but once u get the hang of it it wouldn't be as complicated anymore
As with the Android ROM it consists not only of the operating system software ( bootloader, Linux kernel & Android Framework ) but also of a wealth of drivers & APIs, what are tailored to Android device's hardware and its interfaces. Hence it should be clear that not every available Android ROM will flawlessly run on every Android device: thousands of different brands and models of Android devices are on the market, all have different features.
Installing an incompatible ROM, in the best case, makes components of your Android device unavailable ( they are simply not working ), in the worst case, you might "softbrick" the Android device ( it won't even start up ).