Android 9.0 installation in PC - installer does not boot. - Android Q&A, Help & Troubleshooting

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

Related

How to Install Remix OS to HDD using Grub2 for Windows [Noob Friendly Tutorial]

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.

Onda obook10 factory reset bootloop - Request for system dump

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

Can't change resolution or ota update (vmware)

1. there's no option in the settings for updating
2. i can't change the resolutions
i'm not sure how to edit the grub config, i know you can temporarily change it on boot, but even adding UVESA to it, it didnt do anything for me (maybe i did it wrong)
i also tried this http://forum.xda-developers.com/showpost.php?p=67845695&postcount=13
i managed to change the resolution, but the 'physical size' is still 800x600
so right now, no matter what i change it to, it scales it down into 800x600 window
any help would be appreciated
-edit-
well, i took the dumb way approach and just downloaded the .104 iso and did another install
still trying to figure out the resolution situation
does rooting the os cause ota to be disabled? superuser is preinstalled, so i'm confused if this is the case
Using VirtualBox I was able to change the physical size by adding this to the boot options (example):
. . . video=-16 UVESA_MODE=1200x900 INSTALL=1 DEBUG=
(see link).
I do not know whether this works for VMWare, too. Perhaps you can try or use VirtualBox in place of VMWare.
The update is a separate app
I assume that you installed Remix OS in VMWare using the "INSTALL=1" boot option. An OTA update is not possible; it works for pendrive installations only. The update of an "INSTALL=1" installation is described here .
In order to perform the update you need to start a Linux operating system using a pendrive (e.g. PartedMagic), in order to rename the basic directory from the old value (e.g. /android-2016-08-03/) to the value of the current version (e.g. /android-2016-08-11/) and in order to delete all directories within the basic directory other than /data.
After this step you can perform a normal installation (INSTALL=1), but you must not format your partition sda2 because you want to keep your data.
yes, the only way to install it was through install=1
anyways, that's not my problem anymore, the screen resolution is
i need to somehow access the grub file to add vga=xxx, it seems to be the only way i can change resolution
its easy to find the grub install, i can change it to 342 to get near 1200x800 but its terrible still, would be best if someone wrote openvmware-tools udpate for android

Remix OS installs perfectly, but fails to load after subsequent restarts. Help!

Hey,
New to Remix OS and running into some issues.
Dual booting at the moment, Windows 7. Installed Remix successfully and booted up the first time with no issues. Everything looked to be working. I then restarted the system and selected Remix from the bootloader and it starts the boot process and then my monitor goes into standby mode and never comes out.
Went back into Windows and wiped out the installation using the Remix installer. Reinstalled again, and again no issues on first boot, all looks good. Restart again and same thing....
Has anyone run into this before?
System is an older Dell optiplex 320.
Update:
Initially I was running off the add on gfx card, Nvidia 7300 GT. While this displayed perfectly, it has the boot issue on restart. I then switched to the onboard gfx, which is an ATI Radeon Xpress 200. This takes care of the boot issue, but the image has a lot of colour distortion. Its usable, but not pleasant to use. Useless for pics and videos. I played around with the resolution (during boot, VGA=ASK) and there's no difference.
Ideas?
Reviving this old thread. I hate there being the same question everywhere with no resolution. I was able to resolve this issue, so I am posting the fix here.
This issue is because the built in formatter on the installer will format the partition table in GPT format and make it not be seen as a bootable device in many BIOS's, so GRUB never gets loaded and thus you get the blinking cursor as there is basically nothing to boot according to the BIOS.
The fix is to use a partition editor, any will likely work, but I used Hirens Boot CD and use Gparted (aka Parted Magic). On the drive you intend to install it to, wipe it and create a partition table that is MSDOS/MBR (under 'devices' in Gparted). This will create a standard MBR partition table. Create a new partition in EXT4 format, size it how you want or use the full drive, your choice. Reboot and load up the install media for RemixOS. Install it as normal again, but when the install options come up, select the drive where you created your EXT4 partition, and make sure NOT to format it. Let the install finish, and get into RemixOS again and try a reboot. It should now properly load up GRUB on boot and will boot normally now on subsequent reboots.

Touch enabled grub bootloader?

Just as the title says, I'm curious if there exists a touch (or hardkey, i.e. volume up/down and windoes key) enabled bootloader.
Currently i have to press arrow keys and enter to select either windows or android.
Is there such a thing? It would be amazing. Id rather not have to stop at the keyboard to boot to an os from grub.
Thanks in advance!
Well .. I had suffered from this problem for longtime and finally I solved by an app called android-x86 installer it's the only way to boot from your Windows tablet without keyboard at last what I ended up with .. so yo have to download an old version I recommend the ALPHA version and install it with android-x86 installer 2.4 UEFI version after finished installing you have to download the latest version of remix OS and extract with 7zip or winrar then replace all file with the same name in folder androidOS that the direction of ALFA you already installed now You can boot with two ways either from settings/update / recovery and then press restart now at advanced startup then after reboot choose "use a device " and last thing chose android OS wait 9 seconds in grub2 an finally the remixOS will boot or by simply choose android OS from boot menu by volume Up/down
Boot solution for XPS 12 9250
Will thank you for this post when my 'Thanks!' get replenished on XDA. I'm still only using windows 10 on this tablet PC.
It is not clear to me is this is dual boot Android/Windows, my understanding is that this particular usage of the Linux grub bootloader only boots to Remix OS which is android. Grub, as you know does have dual boot capabilities, but maybe not yet on the XPS 12 9250.
Sorry, but the instructions are not step-by-step details for me, and I seem to be not smart enough to follow them. Could you point me to a 1..., 2..., 3.... please?
Please update or PM me whenever you feel you have found a better boot solution for our 9250's. I will be most grateful.
namitutonka said:
Will thank you for this post when my 'Thanks!' get replenished on XDA. I'm still only using windows 10 on this tablet PC.
It is not clear to me is this is dual boot Android/Windows, my understanding is that this particular usage of the Linux grub bootloader only boots to Remix OS which is android. Grub, as you know does have dual boot capabilities, but maybe not yet on the XPS 12 9250.
Sorry, but the instructions are not step-by-step details for me, and I seem to be not smart enough to follow them. Could you point me to a 1..., 2..., 3.... please?
Please update or PM me whenever you feel you have found a better boot solution for our 9250's. I will be most grateful.
Click to expand...
Click to collapse
Grub can chainload the entry just fine. And when using the official tool it auto-adds an entry if it detects Windows is installed, which it will be as it's a windows tool [unless running via wine] it'll add an entry for it.
Without the tool you can do it manually. Personally I have a second easy to access efi partition that I use, if you want to do the same download a partition manager like minitool and confirm that you have 16MB of unallocated space between your efi and C: drive and I'll dig up a post/walk you through the rest tomorrow
HypoTurtle said:
Grub can chainload the entry just fine. And when using the official tool it auto-adds an entry if it detects Windows is installed, which it will be as it's a windows tool [unless running via wine] it'll add an entry for it.
Without the tool you can do it manually. Personally I have a second easy to access efi partition that I use, if you want to do the same download a partition manager like minitool and confirm that you have 16MB of unallocated space between your efi and C: drive and I'll dig up a post/walk you through the rest tomorrow
Click to expand...
Click to collapse
Very excited to pursue this, but this week is filled with close family coming here to stay for our only holiday celebration. Will post back here when I get that unallocated space, after creating a backup of the current system. May use Gparted, but will check out minitool as well.
Walk through, dual boot Remix OS + Win10 on XPS 12 9250
@HypoTurtle
Waiting on a second USB-C to USB cable so I can boot a Macrium Reflect flash drive and backup a restorable PC image to an external Hard drive. After I'm sure I can restore this image I'll try to install Remix OS.
This youtube link is straightforward and simple to follow for the dual boot installation process. I've seen many reporting hardware/software issues on the many XDA forum threads branching off of "Remix OS for PC". So obviously one size does not fit all. Compiling and replacing different Linux kernels, editing grub.cfg, initrd.img, system.img, data.img.... The very worse thing on xda forums are ignorant end-user whiners like me who want instant gratification with their perfectly working phone or tablet. This vast forum has so many xda-developers, steeped in code, gaining and sharing trial and error knowledge. So many thousands of threads where xda-developers are taken for granted to lay solutions into end-user's laps. So many of us end-users are oblivious to this baby sitting. I will try the time consuming and painstaking learning curve. The least knowledgeable member on xda-forums should try to learn and not be spoon fed. It is essential, whatever our capacity, to all become developers interested in expanding the usefulness of our devices over and above the limited and constrained manufacturer's parameters.

Categories

Resources