READ EVERY SINGLE LINE CAREFULLY AND DO EXACTLY AS I HAVE WRITTEN IT DOWN. FOLLOW IT TO THE LETTER AND YOU WILL HAVE REMIX OS ON YOUR SYSTEM IN NO TIME.
THINGS REQUIRED:
1) Grub2 for Windows (Open Source/Free)
Link: http://sourceforge.net/projects/grub2win/files/
2) Remix OS for PC (Courtesy of Jide)
Link: http://www.jide.com/en/remixos-for-pc
3) BIOS with legacy boot option. NO LEGACY = NO FUN. Simple as that. Can't help you there.
Note: If you have an Acer laptop, there is a very high chance that you have it. My laptop is a 2014 version, it still has legacy boot option, so chill.
Click to expand...
Click to collapse
4) 8Gb or more USB Pendrive or Memory Card in a Card Reader.
STEPS FOR INSTALLATION:
STEP 1 : CREATING HARD DISK PARTITION
a) Create a Hard Disk Drive (HDD) partition. For this, right click "My PC"/"My Computer" > Manage
b) Go to the "Disk Management" section.
c) Let the window initialize. Once it does that, right click one of your drives which has a large amount of free space.
d) Select "Shrink Partition".
e) Select the amount you want for android. Example, 1000 value means 1 GB, so 30000 means 30 GB. Enter this value or any value you want. Select Next.
f) In this window, select "Fat32" option. Click Next.
g) Keep clicking next, next until the window closes.
h) Congrats! You are now the proud owner of a new partition.
STEP 2 : MAKING BOOTABLE REMIX OS USB DRIVE
a) Make the bootable "Remix OS" flash drive using the tool provided in the official zip file.
b) Once done, reboot.
STEP 3 : PREPARING THE BIOS
a) Just as the computer begins to start, keep pressing F12.
b) In the BIOS menu, go to "Boot" tab and select "Legacy" option. Disable "Secure Boot".
c) Change the "Boot Order" by making the flash drive being above HDD.
d) Press F10 to save and reboot.
STEP 4 : FIRST TIME INSTALL
a) In the menu that follows, go to "Resident Mode" and press "Tab".
b) At the end of the line that apprears, write "INSTALL=1" without the double quotes.
d) Choose "FAT32" when it asks you to which format method is to be used.
e) Follow the instructions and when it asks you to install "Grub Bootloader" and "EFI Grub Bootloader" select "Skip"
f) Let it install.
g) Follow the instructions on the screen.
STEP 5 : GETTING THE INSTALLATION FOLDER NAME
1) Reboot.
2) Go to the drive in which you installed your remix os.
3) Since we formatted it to a Fat32 format, windows will be able to open it. Good. Go ahead and open it.
4) There will be a folder created, named something like "android...." with a date or reversed date. Cool. Copy the folder name. We will need it.
5) Go to your Grub2 installation and write these lines in the "conf" file:
Code:
Android
menuentry 'Remix OS' {
set root='(hd0,6)'
linux /android-2015-12-31/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC=/android-2015-12-31
initrd /android-2015-12-31/initrd.img
}
Note:
a)My sda number was 6. Meaning, primary hardisk, partition number 6.
b)The folder that my remix installation created was named "android-2015-12-31". So, I copied it and pasted it in the code above. Just replace your folder name here. Make sure to type the correct sda number.
c) If your harddisk does not have sda number, but something like "msdos", then replace sda with "set root=(msdos,partition number)". That shoud do it.
4) Save and reboot.
STEP 7 : INSTALLING REMIX OS WITH MAX STORAGE
Now, since we need maximum space for remix, we will install remix again, but this time with "ext4" format.
Wondering why we installed it first using Fat32 format? Well, good question. The reason is that we needed to find the folder name. Without it, we cannot boot remix os. So, we formatted it to fat32 which windows can read, so that we can open the drive and get the folder name. Simple as that.
Click to expand...
Click to collapse
1) Repeat Step 3 , except that when it asks you to which format to use, select "Ext4" for maximum storage.
2) Continue with the setup.
3) Reboot.
STEP 7 : BOOTING REMIX OS
1) When it asks to choose OS, select "Grub2 for Windows".
2) Select Remix OS.
3) Enjoy Remix OS.
FAQ:
Q1) I have no legacy option. How to get it?
Click to expand...
Click to collapse
A) If you dont have a legacy option, then you are screwed. Can't help you there.
Q2) Are you an idiot? Why did you give a nonworking method when you know we have no legacy boot option?
Click to expand...
Click to collapse
A) Legacy boot option provides the most easiest way to install any android os, be it Phoenix OS, Remix or even x86 Android Project ROMs. So, if you don't have it, you can always use the EFI based ROMs.
Q3) I messed up my device because of you. Now what should I do?
Click to expand...
Click to collapse
A) First of all, this is the easiest method with no chances of errors. If you messed even this up, why are you even here?
Q4) I like your work. Do you want a cupcake?
Click to expand...
Click to collapse
A) Aww! No, than.....wait! Is it a strawberry cupcake?
Q5) I would like to donate. Where is your paypal?
Click to expand...
Click to collapse
A) I have done nothing. All the work was done by the superb guys and gals at http://www.android-x86.org/ . So, donate to them to keep them alive. Also, JIDE team forked their project and made their OS. So, support them too.
How do I know the sda?
Hi I don't have an option to press Tab on the Resident/Guest mode page, it doesn't do anything. I don't know if it's a difference between the Legacy and EFI versions of Remix OS (I'm using the EFI version, by the way). I was able to press 'e' to "edit selected item", but adding INSTALL=1 just caused an install error. Secure boot is off.
geop0p3 said:
How do I know the sda?
Click to expand...
Click to collapse
During the installation, it will show you a list of hard drives. There, it will also show you the hard drive number, like sda1,sda2 etc. Choose any one greater than 6. Anything less will harm your windows installation or your EFI partition.
F1Fanatic27 said:
Hi I don't have an option to press Tab on the Resident/Guest mode page, it doesn't do anything. I don't know if it's a difference between the Legacy and EFI versions of Remix OS (I'm using the EFI version, by the way). I was able to press 'e' to "edit selected item", but adding INSTALL=1 just caused an install error. Secure boot is off.
Click to expand...
Click to collapse
Use the cursor keys to select resident mode, press TAB on the keyboard and write "INSTALL=1" at the end of the line that appears on the screen. Simple.
this methode work great, thank
+ 1
I also did it this way, only added a "DEBUG=" at last position of the line.
But, normally you don't need it.
Hi, I have a dual booted machine (windows 8.1 and kali 2.0) and i'm wondering, is there any way i can triple boot with remix and if so, how do i go about it??
I've already a EXT4 partition, where reside Linux atm... I should convert in FAT32? Or I can use it in EXT4?
If I format that partition I lost my Grub, so when Android ask for install grub I should say yes?
TheBasterd said:
Use the cursor keys to select resident mode, press TAB on the keyboard and write "INSTALL=1" at the end of the line that appears on the screen. Simple.
Click to expand...
Click to collapse
Well, the EFI one doesn't have the TAB button functionality.. it uses the 'e' button to edit the command line
akkufix said:
+ 1
I also did it this way, only added a "DEBUG=" at last position of the line.
But, normally you don't need it.
Click to expand...
Click to collapse
Adding "DEBUG=1" means that you want a log of what is happening behind the scene. Only useful if the remix installation is not booting up.
nate121 said:
Hi, I have a dual booted machine (windows 8.1 and kali 2.0) and i'm wondering, is there any way i can triple boot with remix and if so, how do i go about it??
Click to expand...
Click to collapse
I am quadruple booting it, if that even makes any sense. I have a partition of ubuntu, one for windows, one for android lollipop android x86 rom and one for remix. So, yes, you can safely triple boot it. Use the method I told above, or if you dont have legacy boot, I cant help you there.
kretex said:
this methode work great, thank
Click to expand...
Click to collapse
Anytime.
Just mention your system, so that if I create a list of working systems with this method, it can help a lot of people and narrow down the possible systems.
zenida said:
I've already a EXT4 partition, where reside Linux atm... I should convert in FAT32? Or I can use it in EXT4?
If I format that partition I lost my Grub, so when Android ask for install grub I should say yes?
Click to expand...
Click to collapse
Here are the things to keep in mind:
1) If you are using linux as your primary os, this method wont work for you, or atleast I dont know about it.
2) If you have a partition for linux, leave it as is and make a seperate partition.
3) ext4 is supported, but dont format it before hand. Let the USB installer format it. Use a fat32 format in the beginning so that you can differenciate between the different partition of your system. Then, in the install screen, choose that fat32 partition and choose ext4 format for it. It will automatically format it to ext4. No further headache required.
priyank.g said:
Well, the EFI one doesn't have the TAB button functionality.. it uses the 'e' button to edit the command line
Click to expand...
Click to collapse
Cool! Thanks for the info. In mine, it flashes "Hit [tab] for options". So, thats why I said tab. :good:
TheBasterd said:
Adding "DEBUG=1" means that you want a log of what is happening behind the scene. Only useful if the remix installation is not booting up.
Click to expand...
Click to collapse
No boot without a log.
Btw.
For those, who are using Linux as primary OS and also have already installed Grub...
I haven't tested it - but it should work.
You can try to install Remix with this method here, but don't let Remix install it's Grub.
After this is done, boot into Linux and run a "sudo update-grub" in terminal.
This should find Remix and put it in boot-options as new OS next to the others.
akkufix said:
No boot without a log.
Btw.
For those, who are using Linux as primary OS and also have already installed Grub...
I haven't tested it - but it should work.
You can try to install Remix with this method here, but don't let Remix install it's Grub.
After this is done, boot into Linux and run a "sudo update-grub" in terminal.
This should find Remix and put it in boot-options as new OS next to the others.
Click to expand...
Click to collapse
Yeah but I want to overwrite Linux because I'll format later. So Remix grub doesn't recognize windows?
Inviato dal mio Nexus 4 utilizzando Tapatalk
zenida said:
Yeah but I want to overwrite Linux because I'll format later. So Remix grub doesn't recognize windows?
Inviato dal mio Nexus 4 utilizzando Tapatalk
Click to expand...
Click to collapse
I thought you want to keep Linux too.
Sure it will find Windows.
In this case, you can use the installer from Remx and let it install it's Grub.
It will be the best to format Linux-partition before you start to install Remix, because then Grub only have Remix and Windows as boot-options and you will not need to edit or re-run Grub again.
Also, you could use the Linux-partition and install Remix in it.
But, if you will use ext4 format as Remix-partition, you can't do changes in Grub within Windows, like boot order. You then will need terminal app in Remix to do this.
If something will go wrong (i.e. no boot), re-run Remix-installer and re-install Grub.
akkufix said:
I thought you want to keep Linux too.
Sure it will find Windows.
In this case, you can use the installer from Remx and let it install it's Grub.
It will be the best to format Linux-partition before you start to install Remix, because then Grub only have Remix and Windows as boot-options and you will not need to edit or re-run Grub again.
Also, you could use the Linux-partition and install Remix in it.
But, if you will use ext4 format as Remix-partition, you can't do changes in Grub within Windows, like boot order. You then will need terminal app in Remix to do this.
If something will go wrong (i.e. no boot), re-run Remix-installer and re-install Grub.
Click to expand...
Click to collapse
I'm trying to install Remix on a VM but it seems to stuck... with that parameter I can workaround in the installation setup, but after partitioning, formatting and installation, at bootstrap grub doesn't start and it can't find any OS... now I try with gparted live to prepare my VHD and I'll retry
zenida said:
I'm trying to install Remix on a VM but it seems to stuck... with that parameter I can workaround in the installation setup, but after partitioning, formatting and installation, at bootstrap grub doesn't start and it can't find any OS... now I try with gparted live to prepare my VHD and I'll retry
Click to expand...
Click to collapse
Did you made you virtual harddisk bootable?
Set parameter "boot" in the installer's partition tool for your vhd.
Related
I recently ordered an Onda obook10 dual booting tablet (Android 5.1 +Win10) from GearBest, and received it a week (and a half) ago. It is the V5 version (9th and 10th digits of S/N). Booted into Android at first, swiped around a little, and then left it alone for when I was free. Day before, I booted into Windows, and seeing that an account was already set up, hit the factory reset option (Options: remove all personal files, normal wipe (not thorough)). It rebooted, said it was resetting, then got stuck at 5% for a half hour. I then did a hard reboot, and it starting resetting again. I repeated this a few times, with different waiting periods, but it always got stuck at 5%. I wanted to see what was going on, so I opened the OS selector menu and tried to boot into Android, but that put the device into a bootloop, and it's stayed that way since. I downloaded the recovery WinPE from their website, and tried running it; all went well until the last step (installing the install.wim file), which succeeded, but when the batch file tried to set the boot options/flags, it threw an error about not being able to access D:, and failed. Tried making the recovery USB and installing multiple times, but it failed every time. I then tried Gandalf's WinPE image, which booted, and tried using imagex to install the .wim file to C: manually, as detailed here. This failed too.
I'm at my wits' end, honestly. I have no idea what else to try. There's another WinPE file available for download, but it's dated only a couple of weeks after the one I already have, so I'm hesitant to download it if there's any other option (I have very low bandwidth, it would take me at least two days). Also, it's hosted on Baidu, and the download times out after about an hour, and cannot resume. If anyone could give me any ideas, or point me towards a guide I haven't found yet (I've read all the relevant ones I could find on the Onda forums, but please post them anyway if you think they would be helpful), that would be great.
What would be perfect is if someone could upload, or point me toward a system dump/partition clone of at least the Windows partition and boot partition; I have the tools needed to flash those.
Thanks in advance.
EDIT: I managed to fix this a while ago, and have put the procedure somewhere in this thread, but since people keep popping up every now and then asking for it, I'm going to put this here so it's easier to find. Copied from later in the thread, here, and modified to be more general:
This uses slightly modified commands from the Onda firmware install script, and will result in a COMPLETE WIPE and reinstall of Windows - all the files on the Windows partition will be lost. This SHOULD work for anyone whose Android is working but Windows isn't, but I can't guarantee that. I can't even guarantee that this will work (though I am pretty sure it will) - I have not tested it completely. If you can, you should make a backup of anything files on the internal storage, just in case. As always, read the whole procedure before starting.
NOTE: If your Android isn't working, you need to install that first - get the Android file from the Onda Baidu page (look for the one for OBOOK 10 (not SE), with the appropriate V1, V2, V3, V5, or V7 code - you can find your code by checking the serial no. on the back of your device, the 9th and 10th characters), and follow the instructions in the document included in the zip - they are pretty straightforward, but you'll have to use Google Translate, as they're in Chinese. This MUST be done before the Windows procedure, because the Android installer wipes the entire disk.
If you want, you can make the procedure easier for yourself and save all the commands below to a text file, put it in the root folder of the USB before booting, and open it in Notepad by using:
Code:
notepad D:\textfile.txt
Or whatever name you give it. That way, you can copy paste them all easily.
Boot into the Windows installer, and when the command window appears, press Ctrl-C. After a few seconds, it will ask you if you want to terminate batch job, type 'y' and press enter. You now have a command prompt to work with.
You have to delete your Windows partitions first. The below partition numbers should be correct, but you should make sure first by running "list partition" and checking if it corresponds with the last 3 partitions, which should be your Windows partitions - their sizes are usually 128 MB, 35 GB, and around 800-1024 MB, and their types are Reserved, Primary, and Recovery (DO NOT delete the Primary partition at the beginning of the disk). DO NOT delete the Unknown partitions - those are Android's.
Code:
diskpart
sel disk 0
sel partition 14
delete partition
sel partition 13
delete partition
sel partition 12
delete partition
Your Windows partitions are now completely gone, so you'll have to recreate them first.
Change directory to the images folder.
Code:
cd D:\images
Get filesizes of .wim files to create partitions accordingly:
Code:
for %I in (Install.wim) do set INSTALL_SIZE=%~zI
set /a INSTALL_SIZE_MB=%INSTALL_SIZE:~0,-6%
for %I in (Winre.wim) do set RE_SIZE=%~zI
set /a RE_SIZE_MB=%RE_SIZE:~0,-6%
if %RE_SIZE_MB% LSS 430 (set /a RE_SIZE_MB=480
) else (
if %RE_SIZE_MB% GEQ 430 (
if %RE_SIZE_MB% LSS 680 (
set /a RE_SIZE_MB=%RE_SIZE_MB%+320
) else (
set /a RE_SIZE_MB=%RE_SIZE_MB%+1024
)
) )
Make sure to preserve all the spaces and brackets in the above code.
Enter diskpart, run the following:
Code:
sel disk 0
create partition msr size=128
create partition primary
shrink minimum=%RE_SIZE_MB%
format quick fs=ntfs label="Windows"
assign letter="W"
create partition primary
format quick fs=ntfs label="Recovery"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
You should now have 14 partitions when you do "list partition".
Exit diskpart.
Now for the actual installation:
Code:
md w:\recycler
md R:\recovery\windowsre
DISM /Apply-Image /ImageFile:"D:\images\Install.wim" /ApplyDir:w: /Index:1 /Compact /ScratchDir:w:\recycler
xcopy D:\images\Winre.wim r:\recovery\windowsre /y
Create boot entry:
Code:
bcdboot w:\WINDOWS
If that doesn't work, then:
w:\WINDOWS\SYSTEM32\BCDBOOT w:\WINDOWS
Set recovery environment:
Code:
w:\windows\system32\reagentc.exe /SetREImage /Path R:\recovery\windowsre /target w:\windows
And that's it! You should have both OSes operational now.
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
EDIT: I've put the guide in the first post.
Flashing Help
SirVer said:
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
Click to expand...
Click to collapse
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
[email protected] said:
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
Click to expand...
Click to collapse
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Widows swith icon
SirVer said:
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
[email protected] said:
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
Click to expand...
Click to collapse
Is the partition still there, or is that just free space you're seeing? For me, the partition was gone, with unallocated space in its place. If the partition is still there, then your job is relatively simple.
1. Make a WinPE recovery drive from another Windows machine, or just use a custom one (like Gandalf's WinPE, Google it).
2. Boot into it from the BIOS menu.
3. Load a command prompt.
4. Type "diskpart" (no quotes). Wait until you get a prompt like: DISKPART>
5. Enter the following commands:
a. select disk 0
b. list partition
c. select partition xx (where xx is the number of the Windows partition. If it's not labelled, it'll be the one about 36 gigs in size.
d. assign letter=c
e. exit
6. Now just run "bcdboot C:\Windows"
7. Reboot, and you should see Windows in your BIOS menu once more, and the button should pop up on Android as well.
If the Windows partition is not there, and it's just free space, things become more complicated. You'll need to get your hands on the Windows installer image. There is an older version on the Onda website (December 2015) that should do the job - or rather, there's a link to their Baidu account. You can find the more recent version in their account as well. The issue is that Baidu doesn't allow you to download files that large without installing their crapware. I got around it by registering an account and some URL-fu, but it's a PITA, especially if you have a slow connection. There's a Yandex mirror somewhere, but I'm not at home, so I don't have the link right now. I'll post it when I get back. EDIT: Here it is.
After you get the files, DON'T install it; it might wipe your Android install (did for me). There's an issue in their install script that made the command that hides the Android partitions from getting deleted not work. What I did was terminate the automatic install, and selectively apply the relevant portions of the script manually. You could probably do the same, but it could take you a while; took me two days and a bunch of background reading. If you're used to messing with Windows installs though, it'd probably be a cakewalk for you. I'd prepare some instructions for you, or even try and write a script myself using that one as a base, but I have exams right now, and I wouldn't have time for at least a week. If you haven't figured it out by then, just ask, and I'll do it.
Sent from my LG-D855 using Tapatalk
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Frezza said:
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Click to expand...
Click to collapse
You can enter the BIOS menu by connecting a keyboard and holding down ESC while booting up.
Sent from my LG-D855 using Tapatalk
Help
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
[email protected] said:
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
Click to expand...
Click to collapse
I don't remember exactly what it's called, but I think it was the second menu entry - Boot <Something>. In that menu, you should see your USB drive USB EFI device or something like that listed - it might also show the manufacturer name (it showed my USB as a Sandisk). If you don't see it, you may have made a mistake when making the bootable USB - try it again while reading the instructions on Gandalf's site carefully. If you used Rufus to make the bootable, maybe try Unetbootin this time - it worked fine for me.
P.S. In case you meant boot into the file - you can't. You have to write it to a USB drive first. Instructions are on the same site you downloaded it from.
Sent from my LG-D855 using Tapatalk
Can I install Windows 7 by Gandalf on this Tablet?
Frezza said:
Can I install Windows 7 by Gandalf on this Tablet?
Click to expand...
Click to collapse
Install? Maybe, but you wouldn't have any of the necessary drivers, so touch and WiFi and stuff wouldn't work. However, you can download the drivers and try installing them, which might work, though it probably won't since they're made for Windows 10.
Sent from my LG-D855 using Tapatalk
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Frezza said:
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Click to expand...
Click to collapse
Depending on certain things, you may be able to just run the installer without doing anything extra. Are you able to boot into Android? Open a CMD window, and run the following commands:
1. diskpart
2. sel disk 0
3. list partition
Post the output of these here. A screenshot will also be OK.
Sent from my LG-D855 using Tapatalk
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
betsesv said:
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
Click to expand...
Click to collapse
When you extract that, you'll get a bunch of files and a DOC in Chinese explaining the procedure to make the recovery disk. Once you've made that, a WARNING before you boot into it: it will automatically open a CMD and start a delay counter, after which it will start the install automatically. Since this might break the Android side, you'll have to cancel it with Control-C in that delay period, which will give you a normal CMD to work with. You can use this to run the commands from my last post. If you want to be extra safe, also download a different WinPE recovery file (like Gandalf - actually you should download this anyway, it has some useful tools you might need later on), and boot into that instead. Depending on the output of those commands, you may be able to just run the automatic installer without worries.
Sent from my LG-D855 using Tapatalk
obook20 crashed
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
alexander137 said:
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
Click to expand...
Click to collapse
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
SirVer said:
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
alexander137 said:
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
Click to expand...
Click to collapse
Just press it down for a long time, at least 10 seconds, that'll do it. For some reason it takes a really long time to force shutdown. If that doesn't work, then there might be an issue with your hardware. Also try typing the "exit" command - it should put you into the BIOS menu directly.
Sent from my LG-D855 using Tapatalk
Until now I was testing Remix on a flash drive, most of the stuff is running great, so I think it's time to try it on the HD.
So here's the question, it's possible to install RemixOS on HD without create partition?
I want Remix to be installed in a regular folder in my HD, with an option to select it in the OS selector when PC starts, and I want it to use data.img instead of something else... Basically just like Phoenix OS.
Is this possible?
Thx..
Cheers...
Regnas said:
Until now I was testing Remix on a flash drive, most of the stuff is running great, so I think it's time to try it on the HD.
So here's the question, it's possible to install RemixOS on HD without create partition?
I want Remix to be installed in a regular folder in my HD, with an option to select it in the OS selector when PC starts, and I want it to use data.img instead of something else... Basically just like Phoenix OS.
Is this possible?
Thx..
Cheers...
Click to expand...
Click to collapse
dude, all you need to do is to look on jide's web
For Hard Disk Installation:
NOTE: Currently, installation tool only supports Windows 7, Windows 8 or Windows 10, with a minimum capacity of 8GB. Users of other operating systems, please install on USB flash drive.
1. Download the Remix OS for PC package, which contains the Remix OS for PC ROM & Installation Tool.
2. Open the Remix OS Installation Tool and follow the instructions to install Remix OS for PC on your hard disk.
3. Reboot your PC.
NOTE for UEFI boot: press special key (F12 for Dell, F9 for HP, F12 for Lenovo, Option Key for MAC) while booting to enter boot menu and ensure that Secure Boot is disabled.
4. Select Remix OS in Windows Boot Menu.
find more on http://www.jide.com/remixos-for-pc#downloadNow
Dude...just try and will know the answers [emoji4]
bombaglad said:
dude, all you need to do is to look on jide's web
For Hard Disk Installation:
NOTE: Currently, installation tool only supports Windows 7, Windows 8 or Windows 10, with a minimum capacity of 8GB. Users of other operating systems, please install on USB flash drive.
1. Download the Remix OS for PC package, which contains the Remix OS for PC ROM & Installation Tool.
2. Open the Remix OS Installation Tool and follow the instructions to install Remix OS for PC on your hard disk.
3. Reboot your PC.
NOTE for UEFI boot: press special key (F12 for Dell, F9 for HP, F12 for Lenovo, Option Key for MAC) while booting to enter boot menu and ensure that Secure Boot is disabled.
4. Select Remix OS in Windows Boot Menu.
find more on http://www.jide.com/remixos-for-pc#downloadNow
Click to expand...
Click to collapse
Thanks, I already saw this...
But in this guide it's not clear what the installation tool will do, if it will create partitions, if it will format something etc... Take the USB installation as an example, I never thought it would create 3 partitions on it...
That's why I'm asking this... Besides, I saw many people unable to boot into Windows after some sort of HD installation of Remix.
Have you tried this method of installation?
If yes, how is the structure of the directory, what files are in there, is it using data.img?
Cheers...
kretex said:
Dude...just try and will know the answers [emoji4]
Click to expand...
Click to collapse
I'm triple boot Win 10, win7 and Phoenix OS, so I'm a little afraid of mess things up.. It would be a nightmare.......
Regnas said:
Thanks, I already saw this...
But in this guide it's not clear what the installation tool will do, if it will create partitions, if it will format something etc... Take the USB installation as an example, I never thought it would create 3 partitions on it...
That's why I'm asking this... Besides, I saw many people unable to boot into Windows after some sort of HD installation of Remix.
Have you tried this method of installation?
If yes, how is the structure of the directory, what files are in there, is it using data.img?
Cheers...
Click to expand...
Click to collapse
The hard drive installation will create a folder called "RemixOS" and add a boot entry for it in the Windows boot loader. In that folder is the kernel, initrd.img, system.img, menu.lst and some other files. An 8 GB data.img will be created on first boot. Those who have problems with booting are typically using a third-party method to install it.
putr4s said:
The hard drive installation will create a folder called "RemixOS" and add a boot entry for it in the Windows boot loader. In that folder is the kernel, initrd.img, system.img, menu.lst and some other files. An 8 GB data.img will be created on first boot. Those who have problems with booting are typically using a third-party method to install it.
Click to expand...
Click to collapse
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Regnas said:
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Click to expand...
Click to collapse
It appears that for the issue mentioned in the link you posted the solution is to simply disable Secure Boot. I don't have much experience with UEFI myself, but on a BIOS system the installer worked perfectly, it didn't break either Windows or Linux Mint.
Sent from my Galaxy Tab 2 3G using Tapatalk
Regnas said:
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Click to expand...
Click to collapse
it also happened to me, i had to use lenovo's one click recovery...
now i installed remix on my d drive and it's fine, last time it went wrong, just because i tried to root it.. so just don't try to root and you'll be fine
this is what the folder looks like:
putr4s said:
It appears that for the issue mentioned in the link you posted the solution is to simply disable Secure Boot. I don't have much experience with UEFI myself, but on a BIOS system the installer worked perfectly, it didn't break either Windows or Linux Mint.
Sent from my Galaxy Tab 2 3G using Tapatalk
Click to expand...
Click to collapse
Thanks for the support.
Fortunately (I hope) I'm on BIOS as well, cause I heard somewhere that disabling secure boot prevents Windows to boot. I don't know if it's a Windows requirement on UEFI machines...
Now it's time to build courage to install it....
Cheers..
bombaglad said:
it also happened to me, i had to use lenovo's one click recovery...
now i installed remix on my d drive and it's fine, last time it went wrong, just because i tried to root it.. so just don't try to root and you'll be fine
this is what the folder looks like:
Click to expand...
Click to collapse
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Regnas said:
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Click to expand...
Click to collapse
I expanded the data.img using this tutorial (http://forum.ppcgeeks.com/android-tp2/138623-how-get-bigger-data-img.html). Don't mind the fact that it was originally made for Windows Mobile devices running Android on SD card, the concept is the same (add zeros to the end of data.img, then expand the partition table in the data.img to cover the extra space).
putr4s said:
I expanded the data.img using this tutorial (http://forum.ppcgeeks.com/android-tp2/138623-how-get-bigger-data-img.html). Don't mind the fact that it was originally made for Windows Mobile devices running Android on SD card, the concept is the same (add zeros to the end of data.img, then expand the partition table in the data.img to cover the extra space).
Click to expand...
Click to collapse
Interesting method...
Thanks for sharing..
Regnas said:
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Click to expand...
Click to collapse
no need to expand at all, you can choose between 8, 16 and 32GB
bombaglad said:
no need to expand at all, you can choose between 8, 16 and 32GB
Click to expand...
Click to collapse
Thank you Sir.
Hmm, interesting...
Where I can choose this, in the installation tool?
And does it take too long to boot? I'm asking this because I expanded the data.img of Phoenix OS, and since then it takes a lot more time to boot.
Cheers..
Regnas said:
Thank you Sir.
Hmm, interesting...
Where I can choose this, in the installation tool?
And does it take too long to boot? I'm asking this because I expanded the data.img of Phoenix OS, and since then it takes a lot more time to boot.
Cheers..
Click to expand...
Click to collapse
nope, as long as your data.img is much smaller than your actual harddisk, you will have no problems with speed.
yes, the instalation tool asks you what size you want to use, either 8, 16 or 32 GB can be chosen
bombaglad said:
nope, as long as your data.img is much smaller than your actual harddisk, you will have no problems with speed.
yes, the instalation tool asks you what size you want to use, either 8, 16 or 32 GB can be chosen
Click to expand...
Click to collapse
Thank you Sir.
Cheers.
So.....the problem solved [emoji16]
kretex said:
So.....the problem solved [emoji16]
Click to expand...
Click to collapse
We're getting there........
Finally I installed it on my Hard Drive... Everything seems to be working fine...
Thank you guys for all the info, help, support and whatnot...
Cheers..
Why another tutorial?
As I searched the net and XDA for a guide to actually install Remix OS and found nothing that worked for me I decided to share with you guys how I managed to install it in Resident Mode. Writing this from XDA Labs on my PC now... For me I found out that the Remix OS installer is totally useless - with some copying from Remix OS folder to root folder of the created partition and manually adding UEFI entry I managed it to boot in Guest Mode but Resident Mode was still not working (bootloop). This started to make me mad as I tried so many tutorials already...
So I tried Phoenix OS and it seemed at first that this one was much better - no need for adding UEFI boot entry or experiencing Windows boot entry problems and such as it installs GRUB and boots the OS just fine. First entry in GRUB is Windows, second one Phoenix OS. Well, started it and it booted up... finally! Used it, wanted to install an app and ran into a random reboot. After a while I recognized that these random reboots happened quite often and the system was unusable for me. So my idea was just to replace Phoenix OS files with Remix OS files as the booting part was already working... and guess... it worked! You can't choose Guest Mode though, but I think you won't need that at all on your PC.
Best one on this: you won't need to open your BIOS start-menu and can boot up normally, just choose your system in GRUB bootloader which appears automatically without the need to do anything before. I find it quite annoying to hit BIOS button to start Remix OS, don't you too? So if you are able to install but don't like that behaviour this tutorial is also for you!
So here it is...
On which machines does this work?
Should be working on all PCs / Laptops running Windows 10 with GPT and UEFI BIOS. Probably also works on machines with MBR instead of GPT partition table and legacy Bios, quite sure this works also on older Windows versions (7/8/8.1). Just let me know if it works for you or doesn't.
How to install
(1)
- Create an NTFS partition on which you want to install it (right, no FAT32 crap!). It should be at least 32 GB.
If you don't know how just search XDA or Google. There are several Remix OS installing tutorials on YouTube which show how to do that in Windows.
(2)
- Download Phoenix OS 1.0.9 RC
- Download Remix OS or Remix OS Hacked Edition if you like to have root and some tweaks for it.
I used Hacked Edition.
(3)
- Use Phoenix OS installer and install it on your created partition (make sure you got the correct drive letter! I'm not responsible if you don't and lose your data...), don't reboot.
- Open the created partition in Explorer.
Create a folder named RemixOS, move all files from PhoenixOS to RemixOS.
(Obviously Phoenix is based on Remix and expects it's data to be in RemixOS folder. Funny bug. ;D)
- Reboot. Choose Remix OS.
Enjoy the nice, buggy OS. For some this may be just everthing they need. If you're happy and experience no reboots or other bugs you should be just fine and don't have to follow the next steps.
(4)
- Reboot to Windows.
- Unzip Remix OS archive - should be 2 files: Remix OS image and installer. You could safely delete the installer as you won't need it.
Use 7zip or Winrar (or whatever) to extract the Remix OS image file into a folder.
- Move the contents of that extracted folder into the RemixOS folder on your created partition. Overwrite everything. You could also extract the image file directly into RemixOS folder.
(5)
- Reboot. Choose Remix OS.
- Done.
You now should be running a working Remix OS in Resident Mode. Works fine here.
Be nice and hit thanks if I could help you.
Zwulf said:
Why another tutorial?
....
(3)
- Use Phoenix OS installer and install it on your created partition (make sure you got the correct drive letter! I'm not responsible if you don't and lose your data...), don't reboot.
.....
Click to expand...
Click to collapse
Hi.
Does that mean that the installation of Phoenix OS erase all the data in that partition?
Regards.
jocaferlo said:
Hi.
Does that mean that the installation of Phoenix OS erase all the data in that partition?
Regards.
Click to expand...
Click to collapse
I'm not sure about that, only used it on a freshly formatted partition. Mentioned this just to make sure not to be blamed if it should do so.
There's a few things off with these instructions:
1. PhoenixOS does not use a RemixOS folder
2. PhoenixOS's grub.cfg won't boot any RemixOS version especially x64 - as PhoenixOS is 32bit only.
stock phoenixos grub.cfg
Code:
menuentry 'Phoenix OS' --class android-x86 {
search --set=root --file /efi/PhoenixOS/kernel
linux /efi/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
initrd /efi/PhoenixOS/initrd.img
}
Something else is going on here. Perhaps the phoenixOS's grub.efi is being used; but it's using the RemixOS grub.cfg. But I think it's just the RemixOS .efi/.cfg and something just switched the default bootloader to grub2 from WBM
HypoTurtle said:
There's a few things off with these instructions:
1. PhoenixOS does not use a RemixOS folder
2. PhoenixOS's grub.cfg won't boot any RemixOS version especially x64 - as PhoenixOS is 32bit only.
stock phoenixos grub.cfg
Something else is going on here. Perhaps the phoenixOS's grub.efi is being used; but it's using the RemixOS grub.cfg. But I think it's just the RemixOS .efi/.cfg and something just switched the default bootloader to grub2 from WBM
Click to expand...
Click to collapse
Maybe, my deeper technical know-how about that is very limited, but I know that it works for me - reproducible. This is just for those like me who tried literally every guide on the net and still none worked. This one probably will. Myself, I find that kind of strange, too and I'm not able to explain why, but it does work. It's just a try and error thing, but for me it works - as already mentioned: reproducible. Got an i7 2nd gen and a X79 Gigabyte Mainboard.
Zwulf said:
Maybe, my deeper technical know-how about that is very limited, but I know that it works for me - reproducible. This is just for those like me who tried literally every guide on the net and still none worked. This one probably will. Myself, I find that kind of strange, too and I'm not able to explain why, but it does work. It's just a try and error thing, but for me it works - as already mentioned: reproducible. Got an i7 2nd gen and a X79 Gigabyte Mainboard.
Click to expand...
Click to collapse
I'm not saying it doesn't work; but what appears to be happening is that the first 'failed' RemixOS installation added things [to efi/esp partition]. And the PhoenixOS install added or replaced something that made the first install work correctly - it could be either the PhOS grub.efi [although that's 32bit] or as simple as it changing your default bootloader.
Download EasyUEFI if you can and see what's in the first partition - I'm just personally curious as to what is going on here.
I'm also using a non-Jide released grub [like Ubuntu users would be - but with a different setup]
HypoTurtle said:
I'm not saying it doesn't work; but what appears to be happening is that the first 'failed' RemixOS installation added things [to efi/esp partition]. And the PhoenixOS install added or replaced something that made the first install work correctly - it could be either the PhOS grub.efi [although that's 32bit] or as simple as it changing your default bootloader.
Download EasyUEFI if you can and see what's in the first partition - I'm just personally curious as to what is going on here.
I'm also using a non-Jide released grub [like Ubuntu users would be - but with a different setup]
Click to expand...
Click to collapse
Sounds very possible... Got EasyUEFI installed but I'm at work atm. Will tell/show you what's in there later this evening when I'm home. The strangest thing I didn't get: original RemixOS booted fine after copying RemixOS folder content to root - but only guest mode worked, not resident. But I mentioned that already in OP. The whole thing would have been a lot easier if I didn't ditch my Arch Linux for RemixOS (for GRUB's sake... ;D), but there were less things to learn...
These instructions didn't work for me, except for the fact that I didn't create a partition. Phoenix would come up as a boot choice but would boot loop.
Sent from my Nexus 6P using Tapatalk
Hi all. I'm looking for a bit of help restoring my boot menu. Win 10 decided to update and now my Asus VivoVM42 only boots directly into Windows. No longer do I have the option to select Remix. In my bios, "other os" is enabled.
My remix partition is still there (R:\) along with all its data, I just need some help getting the (grub?) boot menu to show up again.
Excuse my ignorance, I only know enough to get into trouble. I can follow directions well.
Thanks in advance.
How were you booting to Remix before (do you know which bootloader)? If you have a UEFI BIOS, you could use EasyUEFI (or similar) to set up a boot entry. Once done you would then need to set up your BIOS boot order, or hit the hot key that shows the boot options, just the same as if you wanted to boot from USB.
If you were using Grub or Lilo or similar then you need to re-install that, but will likely need to set up the entries.
I use the UEFI option myself... If you want more specific instructions then let me know.
---------- Post added at 11:22 PM ---------- Previous post was at 11:12 PM ----------
instructions
From within Windows
Download and install EasyUEFI
Launch EasyUEFI as admin
Click on "Manage EFI Boot option"
Click on "create an new entry" button, it is the second from the top, in the middle
Select type "other"
Description "remix"
Select the parition on which Remix OS is installed
Then in the file path section, browse to "\efi\boot\bootx64.efi"
Now when you reboot you should be able to hit the relevant key for your device which brings up the boot menu. Select Remix and boot.
I used the remix installation tool included in the zip file from jides site and installed remix on a partition. So the boot loader is whatever is included with that?
I can navigate from within Windows to:
R:>remix os>efi>boot
And I do see the bootx64.efi file there
I'll give your instructions a try in a bit to add remix to the boot options
Thanks for the help so far
pistacios said:
I used the remix installation tool included in the zip file from jides site and installed remix on a partition. So the boot loader is whatever is included with that?
I can navigate from within Windows to:
R:>remix os>efi>boot
And I do see the bootx64.efi file there
I'll give your instructions a try in a bit to add remix to the boot options
Thanks for the help so far
Click to expand...
Click to collapse
That file is always present *in case* the host system needs it. My instructions will only work if your system has a UEFI style BIOS. If you post the make/model/version I can have a look. Otherwise you will need to reinstall Grub, which is also not too difficult.
Here's some pics of the bios and what happens when I select Remix in the boot options.
I just noticed I was in the wrong directory
R:>efi>boot (folder is empty)
So it looks like whatever was there was wiped out.
Solved-
Rather than attempting to fix the loader, I downloaded the newest version of remix, ran the install tool on the same partition and kept user data. All is the same as I left it.
Back in business.
Thanks again for trying to help, much appreciated.
danmiddle2 said:
How were you booting to Remix before (do you know which bootloader)? If you have a UEFI BIOS, you could use EasyUEFI (or similar) to set up a boot entry. Once done you would then need to set up your BIOS boot order, or hit the hot key that shows the boot options, just the same as if you wanted to boot from USB.
If you were using Grub or Lilo or similar then you need to re-install that, but will likely need to set up the entries.
I use the UEFI option myself... If you want more specific instructions then let me know.
---------- Post added at 11:22 PM ---------- Previous post was at 11:12 PM ----------
instructions
From within Windows
Download and install EasyUEFI
Launch EasyUEFI as admin
Click on "Manage EFI Boot option"
Click on "create an new entry" button, it is the second from the top, in the middle
Select type "other"
Description "remix"
Select the parition on which Remix OS is installed
Then in the file path section, browse to "\efi\boot\bootx64.efi"
Now when you reboot you should be able to hit the relevant key for your device which brings up the boot menu. Select Remix and boot.
Click to expand...
Click to collapse
Which version of EasyUEFI you are using as i think latest version don't support editing / adding boot menu entry now.
I wanted to keep windows Loader as the main and want to chainload grub entry in that triend multiple options but no success.
Could you please help me with that. I am using windows 10 x64 (UEFI) and my laptop model is Sony SVE15127CN
aaquib786 said:
Which version of EasyUEFI you are using as i think latest version don't support editing / adding boot menu entry now.
I wanted to keep windows Loader as the main and want to chainload grub entry in that triend multiple options but no success.
Could you please help me with that. I am using windows 10 x64 (UEFI) and my laptop model is Sony SVE15127CN
Click to expand...
Click to collapse
The latest version (2.7) definintely still works. It can be downloaded here http://www.easyuefi.com/downloads/EasyUEFI_Free.exe you will need to run it as Administrator. The website offers other similar tools, but that is the one you need.
If you set Remix up as a UEFI boot option, using the method I mentioned then you don't need Grub.
The only drawback is that you seem to *need* to use the FAT32 filesystem, which has a filesize limit of 4GB, limiting the data.img file size, which acts as the filesystem in Remix. If you format the drive in NTFS, then you can't set up a UEFI bootloader from it. I am trying to find a workaround for this now as my Remix installation is "full".
I want to dual boot android on my pc. I downloaded the ISO, installed ISO via Rufus. When I boot this flash drive, the live image works fine but when I click on installing it, it just gives me a blank screen. Any suggestions?
xxXPANDER said:
I want to dual boot android on my pc. I downloaded the ISO, installed ISO via Rufus. When I boot this flash drive, the live image works fine but when I click on installing it, it just gives me a blank screen. Any suggestions?
Click to expand...
Click to collapse
GRUB bootloader installed?
Complete guide here.
jwoegerbauer said:
GRUB bootloader installed?
I saw the link. Followed the steps. Stuck after step 5 in the link and cant proceed to step 6. I dont think grub is the issue here?
Click to expand...
Click to collapse
I'm having the same/similar problem (no choice to install is presented)
Context: I use a USB stick with refind to find and boot an android-x86_64-9.0-r2.iso that I have already imaged onto /dev/sda8 (imaged using the linux dd command).
When I use refind and select to boot /dev/sda8, android-x86 boots to the console shell prompt, and then seconds later starts a live run GUI screen. The boot process never stops to present me with a choice of install versus live run, as it should do. And that is my problem.
I'm looking for a workaround. I can switch between console and live GUI using Ctrl-Alt-F1/F7, so I can do command line stuff as root . Anything I can do to kill the live GUI and start the disk installer mode from the console? Name of installer program? Name of GUI is not Xorg or X or anything usual, it seems .
PS: If I knew which distro is underlying android-x86_64-9.0-r2.iso , maybe I could look up some keyboard salute to select installer mode during the boot?
one workaround found
@xxXPANDER, the following may be of interest to you, and @jwoegerbauer, too:
I managed to get the installer going by booting the iso from refind with one trick applied. Details: From refind gui boot, select the iso partition, and then use the hit-key-F2-twice method to edit the refind command line and append the phrase INSTALL=1 and then hit ENTER to boot.
At that point the installer mode came up, rather than the android live GUI mode, and I selected to install according to my plan, onto the empty partition /dev/sda9 with ext4.
I had a surprise that the installer put the data section of the installation on sda6:/android-9.0-r2/data/ (about 180MB), but the rest of the installation on /dev/sda9. Not sure how the installer figured out that I had tried before to do an alien-rpm-based install onto an existing ub18 on sda6. The image I booted was on sda8, and the destination I set was sda9. But still /data ended up on sda6:/android-9.0-r2/data/ . Weird.
Upshot: you need to shoehorn INSTALL=1 into the boot recipe, one way or another. I think the whole problem we're having should be considered a bug, though. It is almost as if the iso checks whether it is being booted from grub2 or not, and if not, jumps straight into live mode. This certainly caused me at least two full days worth of trouble so far, and I see no documentation of this strange behavior. At the very minimum there ought to be some documented keyboard salute that prevents this behavior during a standalone (non-grub2) boot. Maybe someone will disagree, but AT LEAST there should be prominent documentation, say on page https://www.android-x86.org/installhowto.html