Related
Hello,
I've got a strange problem:
-remix os works good when is install on usb (the alpha & the beta )
-remix os stuck at remix os boot screen when it's installed on ssd
What can i do (because on usb it's not very fast)?
atom n270 (32 bit)
gpu intel 945
Thank you
vlgyneco said:
Hello,
I've got a strange problem:
-remix os works good when is install on usb (the alpha & the beta )
-remix os stuck at remix os boot screen when it's installed on ssd
What can i do (because on usb it's not very fast)?
atom n270 (32 bit)
gpu intel 945
Thank you
Click to expand...
Click to collapse
Here too for resident mode guest mode worked after vga=791
Matam AlHaidariya said:
Here too for resident mode guest mode worked after vga=791
Click to expand...
Click to collapse
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Bombo1 said:
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Click to expand...
Click to collapse
Trying hope it work thanks
Bombo1 said:
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Click to expand...
Click to collapse
thank you, but your url it's about virtualisation and my problem concern install in ssd
vlgyneco said:
thank you, but your url it's about virtualisation and my problem concern install in ssd
Click to expand...
Click to collapse
Use steps 4 to 6 after you boot from USB with Remix OS, you will be able to reformat and install the OS again
Bombo1 said:
Use steps 4 to 6 after you boot from USB with Remix OS, you will be able to reformat and install the OS again
Click to expand...
Click to collapse
I whil try this today and will tel you
RE: Stuck at Remix OS boot screen
After much playing around and trial and error, I've managed to fix the flashing logo problem;
A lot of the scripts for the grub entry are needlessly complex, so I'll try and outline it as simply as I can. Make sure you use the grub customizer gui app (http://ubuntuhandbook.org/index.php/2016/04/install-grub-customizer-ubuntu-16-04-lts/) because it handles the different variations on the grub system from ubuntu-based distributions.
Since you will probably be at the stage of actually getting to the Remix OS flashing logo, I'll outline the details for the entry script in grub customizer that works and is fairly easy to follow;
The insmod entries may not all be needed, but including them all doesn't do any harm;
insmod gzio
insmod part_gpt
insmod ext2
The set root command tells grub where to find your RemixOs partition or folder, you can find your partition numbers by typing sudo fdisk -l in a terminal, it will list lots of /dev/sda[x] entries. eg (/dev/sda0, /dev/sda1 and so on) /dev/sda0 is your first partition on your first hard disk, which will be hd0 for grub. If you have more than one physical hard disk you will also have /dev/sdb entries here too, those will be hd1 for grub.
If you have RemixOS installed in your first hard disk hd0, and in the 3rd partition /dev/sda3 the line in the grub entry will be;
set root=(hd0,3)
The next few lines are telling grub which files to load up for RemixOS and are fairly simple by comparison;
linux /kernel /root=/dev/ram0
You will recall that 'kernel' is one of the files you extracted from the RemixOS ISO, this command basically tells the OS to load the kernel for Remix into ram. The next line is a bit more complicated, but it's the meat of the whole RemixOS system, after this command you can tell RemixOS which options you want to enable for your system. There are too many options to list here, so we'll keep it simple.
androidboot.hardware=RemixOS_x86_64 androidboot.selinux=permissive SRC=/system.img
This is also a fairly simple line, if you have an older x86 only machine, make sure you delete the '_64' at the end of the androidboot.hardware line. The next section androidboot.selinux=permissive is required. Lastly the SRC= line is the part I missed out when I was loading it for the first time. You have to make sure you point this SRC= to the system.img that you originally extracted from the ISO. The rest of the commands after this are the specific options you can configure, I'll leave that to your research
Finally, the last line initrd /initrd.img is required and also not terribly complicated.
The entry in grub customizer therefore should look a lot like this:
insmod gzio
insmod part_gpt
insmod part_msdos
insmod ext
set root='(hd0,3)'
linux /kernel root=/dev/ram0
androidboot.hardware=RemisOS_x86_64 androidboot.selinux=permissive SRC=/system.img
initrd /initrd.img
Bearing in mind to adjust where necessary for your own system, hope this helps!!!!
PSon't forget to SAVE entry in grub customizer!!!
Matam AlHaidariya said:
Here too for resident mode guest mode worked after vga=791
Click to expand...
Click to collapse
if your still having issues this worked for me www youtube com/ watch?v=3Vl25bJeGn8 just take out the spaces and insert periods
1. Create a second ext4 partition for Remix OS using Gparted
You should delete the linux-swap and the extended partition first. After reducing the size of your Ubuntu partition sda1 you can create your Remix OS partition sda2.
Finally you'll create a new extended partition containing the linux-swap.
http://postimage.org/index.php?lang=german
2. Install Remix OS into the new partition
Use the steps described in "Installing Remix OS to Hard Drive or Virtual Machine without additional tools", but there are a few differences:
- Skip step 3, because you have a formatted ext4 partition already (in my example: sda2)
- Step 4: Select sda2 for your installation (formatting of sda2 not needed)
- Step 5: Do not install a boot loader GRUB; do not install EFI GRUB2 (you'll customize the Ubuntu boot loader)
3. After a reboot Ubuntu will start. Please install grub-customizer
sudo apt-add-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
4. Start grub-customizer and add a new entry (Ctrl + N) named e.g. "Remix OS", Type "other"
Boot sequence:
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /android-2016-07-12/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/android-2016-07-12
initrd /android-2016-07-12/initrd.img
(hd0,2) has to be changed if you use a partition other than sda2 on hd0 for Remix OS.
Example: If you are using sdb2 on hd1 the "set root" command is
set root='(hd1,12)'.
You can obtain the Android path (e.g. /android-2016-08-11/) by mounting the Remix OS partition with the Linus file manager.
Example of boot menu entry for Remix OS
http://postimage.org/index.php?lang=german
If you are working with the Remix OX 32bit version you have to use ". . . androidboot.hardware=remix_x86 . . ." in the last line (beginning with linux).
Example: With version 3.0.103 (2016080805) 32bit the line has to be:
linux /android-2016-08-08/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive SRC=/android-2016-08-08
initrd /android-2016-08-08/initrd.img
5. Make the Remix OS entry the second boot menu entry
http://postimage.org/index.php?lang=german
6. Modify the General Settings
- Default: first entry
- Show menu
- Start default after 5 seconds
http://postimage.org/index.php?lang=german
7. Save the new grub configuration
8. Check the new swap UUID and correct it in /etc/fstab
sudo blkid | grep swap
9. Reboot and select the second entry "Remix OS"
Thanks for the guide it's really useful for me since I'm already using ubuntu and had a separate partition ready for another OS.
I am having some trouble with the grub configuration.
Error: Disk <<hd0,3>> not found
alloc magic is broken at 0x6ff89b20: 6fded940
Aborted. Press any key to exit
Click to expand...
Click to collapse
Here's my disk layout:
sda1 EFI system partition
sda2 EXT4 /
sda3 EXT4 /remix
sda4 EXT4 /home
sda5 swap
Click to expand...
Click to collapse
And here's my grub entry:
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,3)'
linux /android-2016-07-12/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/android-2016-07-12
initrd /android-2016-07-12/initrd.img
Click to expand...
Click to collapse
I have changed only "insmod part_msdos" to "insmod part_gpt" since I'm using GPT/UEFI (I'm running it on an old mac mini, only boots UEFI)
Any idea what might be wrong? I already triple-checked the grub entry and stilll can't figure out what's going on. Tried also editing hd0,# on boot to no avail either.
EDIT: Would it be easier to have it as single OS? I already backed up and cleaned the HDD.
Willdrick said:
Thanks for the guide it's really useful for me since I'm already using ubuntu and had a separate partition ready for another OS.
I am having some trouble with the grub configuration.
Here's my disk layout:
And here's my grub entry:
I have changed only "insmod part_msdos" to "insmod part_gpt" since I'm using GPT/UEFI (I'm running it on an old mac mini, only boots UEFI)
Any idea what might be wrong? I already triple-checked the grub entry and stilll can't figure out what's going on. Tried also editing hd0,# on boot to no avail either.
EDIT: Would it be easier to have it as single OS? I already backed up and cleaned the HDD.
Click to expand...
Click to collapse
Are you sure it's (hd0,3)?? You may have to recheck that. Enter the command mode by pressing 'c' at Grub menu and execute 'ls' command to list partitions. I guess it must be (hd0,gpt3) or something like that. You can double check which is RemixOs partition by using 'cd' into each partition executing 'ls' to list files.
Thanks Thisu, but no dice, I even tried installing RemixOS as the main OS without any luck. I have used crappy linux installers (like way back knoppix) but damn Remix takes 1st prize. Right now I'm trying to reinstall GRUB2efi from an ubuntu live USB. No matter what kind of installation I do for Remix I get the typical "blank" GRUB screen (the one that states "....minimal bash command...." and a GRUB> prompt)
I don't know what's the matter with this installer, it's never consistent. sometimes it asks for a data file creation, sometimes doesn't, sometimes just reboots after the install, sometimes prompts what to do... Resident mode tends to work but from this particular drive and computer, is barely useable due to poor speeds. And trying to repurpose an old mac with this is far worse, the PoS won't even try booting a normal MBR scheme. it HAS to be EFI
/rant
Willdrick said:
Thanks Thisu, but no dice, I even tried installing RemixOS as the main OS without any luck. I have used crappy linux installers (like way back knoppix) but damn Remix takes 1st prize. Right now I'm trying to reinstall GRUB2efi from an ubuntu live USB. No matter what kind of installation I do for Remix I get the typical "blank" GRUB screen (the one that states "....minimal bash command...." and a GRUB> prompt)
I don't know what's the matter with this installer, it's never consistent. sometimes it asks for a data file creation, sometimes doesn't, sometimes just reboots after the install, sometimes prompts what to do... Resident mode tends to work but from this particular drive and computer, is barely useable due to poor speeds. And trying to repurpose an old mac with this is far worse, the PoS won't even try booting a normal MBR scheme. it HAS to be EFI
/rant
Click to expand...
Click to collapse
I am no GRUB specialist, and I do not use EFI. I found a working GRUB configuration for Remix OS by copying and modifying the primary GRUB configuration for Linux Mint 17.3. The tool I used is the "grub-customizer". I installed Remix OS in partition sda2, and "set root='(hd0,2)' " worked for me.
I created and formatted sda2 using GParted; so during the Remix OS installation sda2 did not have to be formatted. Because I wanted to use the Ubuntu GRUB installation, the Remix OS installer has been told not to install GRUB und EFI GRUB2.
In case if someone still looking for help, use the example below. I was successfully able to boot with configuration below.
All you have to do is to mention right gpt partition where you have installed remix os mine was gpt6.
Then by running the "blkid" command in ubuntu terminal find the UUID of the partition
Replace my UUID which is in this example with yours.
Instead of root=/dev/ram0 use root=UUID of the partition.
Hope it will help some
insmod part_gpt
insmod ext2
set root='hd1,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt6 --hint-efi=hd1,gpt6 --hint-baremetal=ahci1,gpt6 c604b8c5-95f4-4b14-b0cb-88bd45d871e9
else
search --no-floppy --fs-uuid --set=root c604b8c5-95f4-4b14-b0cb-88bd45d871e9
fi
linux /android-2016-07-26/kernel quiet root=UUID=f1f10df6-d879-42c6-af68-e7b021b5e7bd androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/android-2016-07-26
initrd /android-2016-07-26/initrd.img
noob question,
do i need to install ubuntu 1st? before i install remix?
mrkLu said:
noob question,
do i need to install ubuntu 1st? before i install remix?
Click to expand...
Click to collapse
Installing Ubuntu first is at least easier, because Ubuntu will not detect Remix OS as "installed system" and will not offer installing Ubuntu as second system, providing dual boot.
ok, i have finally install everything,followed what have been put here.
but i get an error once i choose remix os on GRUB
error '/android-2016-07-12/kernel' not found
error 'you need to loadthe kernel first'
@remixtester
Firstly, thanks for the guide. I've got it mostly figured out but I have a couple of questions for you.
The partition I have installed Remix to is sdb12, so how would I edit the grub? Is it:
Code:
set root='(hd0,12)'
or
Code:
set root='(hd1,12)'
or something completely different?
Answer:
sdb = hd1 so the code is:
Code:
set root='(hd1,12)'
Also, the "/android-2016-07-12 has to be changed if you will use a Remix OS version other than 2.0.403 (2016-07-12)" section might need a little more clarification. I understand that I need to change this because I'm using Version 3.0.104, but there's no indication in this guide on how to find the correct information for builds that differ from the one you mention using. So how do I find out what to change that line to (as per the build I downloaded)?
Answer:
Mount the partition you installed Remix to in the Linux file manager and view the folder there.
Even though I've answered my questions I'm leaving this here for anyone else having the same questions in future. It might be a good idea to add this info to your guide.
remixtester said:
1. Create a second ext4 partition for Remix OS using Gparted
You should delete the linux-swap and the extended partition first. After reducing the size of your Ubuntu partition sda1 you can create your Remix OS partition sda2.
Finally you'll create a new extended partition containing the linux-swap.
http://postimage.org/index.php?lang=german
2. Install Remix OS into the new partition
Use the steps described in "Installing Remix OS to Hard Drive or Virtual Machine without additional tools", but there are a few differences:
- Skip step 3, because you have a formatted ext4 partition already (in my example: sda2)
- Step 4: Select sda2 for your installation (formatting of sda2 not needed)
- Step 5: Do not install a boot loader GRUB; do not install EFI GRUB2 (you'll customize the Ubuntu boot loader)
3. After a reboot Ubuntu will start. Please install grub-customizer
sudo apt-add-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
4. Start grub-customizer and add a new entry (Ctrl + N) named e.g. "Remix OS", Type "other"
Boot sequence:
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /android-2016-07-12/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/android-2016-07-12
initrd /android-2016-07-12/initrd.img
(hd0,2) has to be changed if you use a partition other than sda2 for Remix OS
/android-2016-07-12 has to be changed if you will use a Remix OS version other than 2.0.403 (2016-07-12)
Example of boot menu entry for Remix OS
http://postimage.org/index.php?lang=german
If you are working with the Remix OX 32bit version you have to use ". . . androidboot.hardware=remix_x86 . . ." in the last line (beginning with linux).
Example: With version 3.0.103 (2016080805) 32bit the line has to be:
linux /android-2016-08-08/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive SRC=/android-2016-08-08
initrd=/android-2016-08-08/initrd.img
5. Make the Remix OS entry the second boot menu entry
http://postimage.org/index.php?lang=german
6. Modify the General Settings
- Default: first entry
- Show menu
- Start default after 5 seconds
http://postimage.org/index.php?lang=german
7. Save the new grub configuration
8. Check the new swap UUID and correct it in /etc/fstab
sudo blkid | grep swap
9. Reboot and select the second entry "Remix OS"
Click to expand...
Click to collapse
I did the same you instructed but when i select Remix OS in boot menu. Attached screen comes it pc restarts .
Please help.
sachinwadhwa46 said:
I did the same you instructed but when i select Remix OS in boot menu. Attached screen comes it pc restarts .
Please help.
Click to expand...
Click to collapse
Which version of Remix OS did you use? 32bit or 64bit?
What's the name of the partition where you installed Remix OS?
Did Remix OS start after you clicked OK here:
http://postimage.org/index.php?lang=german
Which boot sequence did you enter into the boot menu entry for Remix OS (Ubuntu "Grub Customizer")?
remixtester said:
Which version of Remix OS did you use? 32bit or 64bit?
What's the name of the partition where you installed Remix OS?
Did Remix OS start after you clicked OK here:
http://postimage.org/index.php?lang=german
Which boot sequence did you enter into the boot menu entry for Remix OS (Ubuntu "Grub Customizer")?
Click to expand...
Click to collapse
Actually i did a mistake. Infact its a mistake in your code for boot sequence in your guide
In eg of 32 bit , you have written initrd=/andoid..... And correct is initrd /android......
Anyways hardly matters, your guide was awesome. Thank you !!!
helpp
I followed every step on the guide, but when I try to boot Remix Os, it just says "disk /dev/ram0 doesn't exist", I don't know what to do, I've tried changing /dev/ram0 for other disks and dir,, but just says the same "disk -the disk I decide to put- doesn't exist
also, sorry for my bad english, I mostly speak spanish
Ok everything went ok boots up and runs fine. my question be if you were going to root this you would want it to be after you make the bootable usb which will then change it to system.img and make the change on the grub customizer then install it to the partition with "Tab" INSTALL=1.
error when trying to start Remix OS
After the procedure, when I tried to start the operational system an error appeared "error archive '/android-2016-07-12/kernel' not found. alloc magic is broken at 0xb798ee00: b76cfc20." . How can I find the correct name of the kernel I had installed to make some changes in the grub costumization.
Thanks.
Label RemixOS partition as RemixOS using gparted and use the script in below link either through custom grub entry or grub-customizer.
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-alongside-ubuntu-t3463014
For anyone having problems running RemixOS alongside GRUB
For anyone having problems running RemixOS alongside GRUB, you can try the guide updated for the latest version I just posted.
Use EasyBCD or If ur using for simple puposes install The OS on virtualbox or VmWare
An Easy way to dual boot with ubuntu
You can try this method. It doesn't require any hassle of partition or bootable usb. https://youtu.be/g3XTDpTw6A8
The latest Remix OS for PC OTA update (3.0.204) is ready. Thanks for your patience and for the feedback you've been sending us.
First , I'd like to give an update on the sleep issues that are still affect some of you (and us). We've been able to pinpoint the issue (through your feedback) to PCs running Skylake (6th generation) Intel chips. If you'd like to pitch in and look into the issue, please go to the Android-x86 Open Source Project OSDN repository: https://en.osdn.jp/projects/android-x86/
Also, we close to resolving the HDMI sound output issue. It's actually just going through internal testing right now, so look out for that in the next update.
And now, here are the full release notes for today's OTA update:
___________________________
Remix OS for PC version: 3.0.204
Release date: September 13, 2016
Release notes:
- Integrated Android-x86 R1, inlcuding the latest Android Security patch (September 2016)
- Improved Remix OS performance on low-end budget PCs
- Fixed multiple cases where Wi-Fi can't connect after sleep
- Improved App drawer's search
- Remix Central's apps library has been updated
___________________________
Thanks all for your continue feedback. Remix OS for PC would be nowhere without you guys, so please keep the feedback flowing!
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
how do i upgrade from 3.0.203?
Upgraded. Looks great!
How about when I boot up, I have to manually connect to Wi-Fi. It doesn't automatically connect?
how can we boot into Remix OS 3.0 update 204 using Grub2win ? Can anybody help me giving a grub.cfg for booting into UEFI 64bit System. Having Issue during installation on UEFI 64bit stuck on "Remix OS" Boot logo
For this version, 3.0 204
For this version, the start menu does not work on my pc. and wifi did not connect automatically after reboot
nothing regarding video playback?? Or even the non functional Game toolkit after 2.0.203?
Nor anything regarding the volume up/down issue on XPS18.... I have submitted the correct way for this issue. If I press it once up, it goes max volume and won't turn down until I go back to home screen and close all running apps. Same with volume-down. I press it once and it silences the sound until I go back to home screen and kill running apps. This error only happens when I try to adjust volume while in an app and not on home screen. This means I have to set pre-determined volume THEN open an app....
DO u have any update on Keymapping tool?
start menu not showing up... I have to open apps through play store!
btw. i hate those ads in start menu. Windows 10's advertising featured apps through store live tile is more elegant way of advertising than this ..
Post 3.0.203 update, RemixOS fails to boot, getting stuck at the command window with a '-' (hyphen)sign. Tried deleting user data and installed the latest 3.0.204 on a clean NTFS formatted HDD partition, still the same thing,not booting at all. Mine is Fujitsu Laptop with Core i3(2nd gen),4GB RAM, and with switchable nVidia GT620M graphics.
New update, still the same bugs. Not wasting my time anymore.
TrialUserXP said:
how do i upgrade from 3.0.203?
Click to expand...
Click to collapse
Upgraded to 204 on my ext4 HDD partition by installing over (on top of) the 203, applying INSTALL=1 to the boot menu command line of the USB-stick (http://goo.gl/j7fba7).
Successfully I think. Could anybody explain what might be wrong with this installation method, please!
- Improved Remix OS performance on low-end budget PCs
finally i get best thing i'm actually waiting for YAY
no sound
i am use sony duo 11. i installed remix os version 3.0.204 . no sound from speaker but headphone is ok. plz fix it. thank very much.
This version now refuses to boot with hardware 3D acceleration on my laptop with NVIDIA Optimus hybrid graphics (Intel HD 4000 and GeForce 740M). On previous versions (not sure about previous 3.0.2xx, but 3.0.1xx worked, as did the later versions of 2.0) I'd add "nouveau.modeset=0" to the boot parameters, but it doesn't seem to do anything on this version (nouveau kernel module still loaded). Android-x86 6.0-r1 has the same problem as well.
Bugs:
No sound
Wifi doesn't connect to saved networks on reboot
Ongoing power management issues (frozen and needs reboot if it sleeps)
Also, trying to do the OTA borked my system, and I had to hard format the USB and recreate the media and reinstall from scratch.
PC is Chromebook Pixel 2 LS in developer mode, Legacy Bios enabled.
hallergard said:
Upgraded to 204 on my ext4 HDD partition by installing over (on top of) the 203, applying INSTALL=1 to the boot menu command line of the USB-stick.
Successfully I think. Could anybody explain what might be wrong with this installation method, please!
Click to expand...
Click to collapse
Take a look what i did (BEWARE try them on a system in which there is no linux Grub installed) otherwise you will be at lose )
Step 1: Well i made a extra partition of 10gb by shrinking the c drive (Note UEFI 64 bit system) & didnt assigned any of the Drive letter and formatted with fat32 file system. let it be (hd0,gpt6).
Step 2: Installed a Tool called GRUB2win from a Developer Drummerdp (Awesome work he did). Installed a Grub2win EFI Module and in Boot entry i made a Remix Os Boot entry which is made default by this tool (GRUB2Win- here is plus point you can also this grub anytime by uninstalling).
Step 3: Took a Pendrive 16gb. Used RUFUS 2.11 tool to burn the Give REMIX OS 3.0 iso with "GPT partition table for UEFI" on the pen drive.
Step4: On completion, Restarted the laptop or computer in which you made the partition. Booted from the Pen Drive
Step5: To edit the custom command Press "E" and add "INSTALL=1" in the give command.
Step 5: NOTE : YOU SHUD REMEMBER WHICH FAT32 PARTITON YOU MADE other you could format your windows partition too . In my case it was the 6th one which was a only fat32 partition. select and format with EXt4 .
Step6: Skip both the Grubs to install.
Step7: After syncing to the disk you will get REboot and Run ANDROID X86 Select "RUN ANDROID X86" and HOLLA YOU will boot into the REMIX OS 3.0 204
The only problem i got is with the grub2win GRUB.cfg file becoz i dont knw what edit shud i make in grub entry to make it boot even in the after the restart
in the C drive where Grub2win in installed Grub2.cfg have this Commands by default :-
menuentry 'Remix' --class remix --class icon-remix {
[*] set bootfile=/RemixOS/kernel
[*] getbootpartition file $bootfile
[*] if [ $? = 0 ] ; then
[*] linux /RemixOS/kernel root=/dev/ram0 verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive DATA= SRC=RemixOS CREATE_DATA_IMG=1
[*] initrd /RemixOS/initrd.img
[*]
but i this doesnt work at boot becoz these locations arent correct according to the latest update any help to this could make it work every time
iamvishalattri said:
Take a look what i did (BEWARE try them on a system in which there is no linux Grub installed) otherwise you will be at lose )
Step 1: Well i made a extra partition of 10gb by shrinking the c drive (Note UEFI 64 bit system) & didnt assigned any of the Drive letter and formatted with fat32 file system. let it be (hd0,gpt6).
Step 2: Installed a Tool called GRUB2win from a Developer Drummerdp (Awesome work he did). Installed a Grub2win EFI Module and in Boot entry i made a Remix Os Boot entry which is made default by this tool (GRUB2Win- here is plus point you can also this grub anytime by uninstalling).
Step 3: Took a Pendrive 16gb. Used RUFUS 2.11 tool to burn the Give REMIX OS 3.0 iso with "GPT partition table for UEFI" on the pen drive.
Step4: On completion, Restarted the laptop or computer in which you made the partition. Booted from the Pen Drive
Step5: To edit the custom command Press "E" and add "INSTALL=1" in the give command.
Step 5: NOTE : YOU SHUD REMEMBER WHICH FAT32 PARTITON YOU MADE other you could format your windows partition too . In my case it was the 6th one which was a only fat32 partition. select and format with EXt4 .
Step6: Skip both the Grubs to install.
Step7: After syncing to the disk you will get REboot and Run ANDROID X86 Select "RUN ANDROID X86" and HOLLA YOU will boot into the REMIX OS 3.0 204
The only problem i got is with the grub2win GRUB.cfg file becoz i dont knw what edit shud i make in grub entry to make it boot even in the after the restart
in the C drive where Grub2win in installed Grub2.cfg have this Commands by default :-
menuentry 'Remix' --class remix --class icon-remix {
[*] set bootfile=/RemixOS/kernel
[*] getbootpartition file $bootfile
[*] if [ $? = 0 ] ; then
[*] linux /RemixOS/kernel root=/dev/ram0 verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive DATA= SRC=RemixOS CREATE_DATA_IMG=1
[*] initrd /RemixOS/initrd.img
[*]
but i this doesnt work at boot becoz these locations arent correct according to the latest update any help to this could make it work every time
Click to expand...
Click to collapse
This grub cmd kernel line works for me [64bit UEFI Install], basically replace DATA= ****** with SRC=/RemixOS
Code:
linux /RemixOS/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SERIAL=random logo.showlogo=1 SRC=/RemixOS
(opt. add REMOUNT_RW=1 if you want to mount system Read Write)
and for DEBUG=2 boot:
Code:
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SERIAL=random logo.showlogo=1 SRC=/RemixOS DEBUG=2
EDIT: make sure you have a "data" folder, like in
yourPartition: /RemixOS/data
I love love love Remix OS. I have had an issue with the past couple that seems to slightly differ than others. I am running a Yoga 3 and a Surface Pro 1. I switched from the Yoga to the SP1 because the WiFi just drops. It sits and spins at Turning WiFi on. This just randomly happens while using. Not during reboots. I am not sure what is going on. I just plug in a USB to Ethernet and roll. Just curious if this is just me?
Steps
Download Remix OS for PC from
http://www.jide.com/remixos-for-pc
Create an ext4 partition for minimum of 8 GB with label as RemixOS using Gparted from Ubuntu.
(Note : Resizing, ie. shrinking an existing partition, takes more time.
If you have fewer files in an existing partition it will be better to copy those files to another partition
and delete first partition
and create 2 new partitions. One for Remix OS and another for old Data. This will save time.
You should be careful while using Gparted so that partition in which Ubuntu and Windows have been installed is not messed up.
If there is an existing partition which you can allot entirely for Remix OS then open Gparted reformat it to ext4 and label it as RemixOS)
Right click downloaded Remix OS file and select Extract.
Again extract the resultant *.iso file.
Copy the iso extract resulting files and folders to the new ext4 partition labelled RemixOS.
Boot option
Boot option can be created in two ways - either by Making an entry in /etc/grub.d/40_custom file or by Making an entry through Grub-customizer
Making an entry in /etc/grub.d/40_custom file
Open Terminal and type below command
sudo gedit /etc/grub.d/40_custom
--> Make the file opened look like below by copying. Change the "set root=(hd0,3)" as per the RemixOS partition drive number in Gparted mine is sda3. If yours is sda4 change it as "set root=(hd0,4)"
#!/bin/sh
exec tail -n +3 $0
menuentry "Remix OS" {
set root=(hd0,3)
linux /kernel initrd=/initrd.img boot=LABEL=RemixOS disk=LABEL=RemixOS quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1
initrd /initrd.img
}
--> Save --> close.
Type below Terminal commands
sudo chmod +x /etc/grub.d/40_custom
sudo update-grub
(Remix OS does not appear in grub detection while updating grub but appears in Grub Boot Menu)
or
Making an entry through Grub-customizer
Install Grub-customizer in Ubuntu
Type below commands in terminal for installation
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
Start Grub customizer - select edit - new -
put menuentry as "REMIXOS Resident mode - All your data and apps are saved" or as "Remix OS"
Type as "other"
copy below to the boot sequence. Change the "set root=(hd0,3)" as per the RemixOS partition drive number in Gparted mine is sda3. If yours is sda4 change it as "set root=(hd0,4)"
set root=(hd0,3)
linux /kernel initrd=/initrd.img boot=LABEL=RemixOS disk=LABEL=RemixOS quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1
initrd /initrd.img
Select Save.
Note : Not writing to MBR has resulted in Ubuntu not booting and Remix OS booting when options for Ubuntu was selected in Boot menu. And Remix OS did not show up in Grub menu entry.
So select File - > click write to MBR.
After MBR write, restart ubuntu and select Remix OS.
Patience is needed here it will take some time to install. Sometime without any animation or display movement. So do not restart when it is like that. Wait few minutes it will boot up.
Activate Play Store using Play Activator app (comes pre-installed)
After much trial and error found working way of installation of RemixOS alongside Ubuntu. So sharing it here.
You can increase Internal Storage / Memory from Ubuntu by following
Open Files -> select RemixOS partition -> after it has been mounted move mouse pointer over RemixOS again but don't click -> it will show the mount path normally it will be /media/xxxxxxx/RemixOS (user name will be displayed in place of xxxxxxx -> note the path
You can copy data.img file to Ubuntu partition for restore purpose in case anything goes wrong, before attempting resizing.
open terminal and type below commands
-> cd /media/xxxxxxx/RemixOS
(the path noted)
-> sudo e2fsck -f data.img
type sudo password
-> resize2fs data.img 8G
(Note : Replace 8G as per the partition size allocated to RemixOS.
If you have allocated 40GB to RemixOS partition then you can leave 10GB for OS and
allocate balance 30GB to Internal memory. In such case command will be resize2fs data.img 30G
Important :- allow sufficient space for System use)
-> exit.
I encountered some errors while resizing it asked whether it should be fixed and I pressed two times yes for fix errors.
Remix OS boot was fine it showed increased Internal Storage.
Even OTA update works. Patience is needed when no animation or display or Blank Screen. Wait few minutes. It will restart.
(updated from 3.0.202 to 30.0.203 to 3.0.204 to 3.0.205 to 3.0.206 so far without any errors).
While updating to 3.0.206 the newly introduced update percentage screen disappeared after 65% and display showed blanked screen but update happened and rebooted after 5 minutes (may increase or decrease depending on your RAM). So don't shutdown on blank screen.
Note: Edge scroll not working, two finger scroll works, in laptop (Remix OS).
Why do I get corrupted sd , when formatting it deleted everything off hard drive. I have latest remix 64 extracted,also extracted system.img and placed it into root folder on Ubuntu ,along with kernel,initd.img,ramdisk.img, edited grub to boot, everything runs but only 1 gig of memory with the corrupted part ,
Increase Internal Storage / Memory of Remix OS through Ubuntu
miko12312 said:
Why do I get corrupted sd , when formatting it deleted everything off hard drive. I have latest remix 64 extracted,also extracted system.img and placed it into root folder on Ubuntu ,along with kernel,initd.img,ramdisk.img, edited grub to boot, everything runs but only 1 gig of memory with the corrupted part ,
Click to expand...
Click to collapse
System data is shown in android file manager as corrupted. But Remix OS runs fine.
See first post on how to increase internal storage (now added).
Am I able to make an ext4 even if Ubuntu is using the whole drive and portions,ubuntu setup has ext4 for root folder and a swap partition I tried repartitioning the drive to have space left but it wouldn't let me install Ubuntu I created 150gb for / ,500mb for boot,100gb for home ,and 2048mb for swap to install
miko12312 said:
Am I able to make an ext4 even if Ubuntu is using the whole drive and portions,ubuntu setup has ext4 for root folder and a swap partition I tried repartitioning the drive to have space left but it wouldn't let me install Ubuntu I created 150gb for / ,500mb for boot,100gb for home ,and 2048mb for swap to install
Click to expand...
Click to collapse
If you feel 150gb is more for / - Shrinking it may be done through Ubuntu Live DVD Gparted. Patience needed here shrinking may take more than one hour. There is remote chance of Ubuntu not booting up and requiring Ubuntu reinstallation.
Alternatively you can try reinstalling Ubuntu from Live DVD after deleting the existing / partition and creation of two ext4 partitions one for Ubuntu / and other for RemixOS. Leaving the 100gb home as it is.
I have a 320gb Acer c710 chrome book with seabios installed ,along with lubuntu 16.04, I'm trying to manual install lubuntu or Ubuntu since its same, I want to make Linux with 150gb as / , and the rest as earlier , so I have close to 70gb for remix or what ever , but when doing so I get an error when installing but I'm a try the live USB option see if that works on shrinking , I'm still learning Linux but understand most of it pretty easy , but really like remix for the gaming , since they switched to mm I have had it run successfully but root issues and fc, now I'm trying to run it with the official and re root after
Made the ext4 partition , but not getting boot stays in bootloop,do I need to extract the system.sfs,and use the system.img
miko12312 said:
Made the ext4 partition , but not getting boot stays in bootloop,do I need to extract the system.sfs,and use the system.img
Click to expand...
Click to collapse
Extracting iso is sufficient.
Delete the already copied files to the new ext4 RemixOS partition from Ubuntu and copy again the iso extracted files. Then boot to Remix OS.
I have everything running but still says corrupted USB , I have made a data IMG of 10gs ,everything is running but can't install anything from play store ,root seems to be working also ,wifi disconnects also
miko12312 said:
I have everything running but still says corrupted USB , I have made a data IMG of 10gs ,everything is running but can't install anything from play store ,root seems to be working also ,wifi disconnects also
Click to expand...
Click to collapse
Activate Play using Play activator.
Wifi auto on is not working. Click on wifi icon on bottom right it will connect. If still not working try switching off and on wifi.
Already activated play store but all apps even systems won't install or update ,have to use Altoids and apps downloaded ,
miko12312 said:
Already activated play store but all apps even systems won't install or update ,have to use Altoids and apps downloaded ,
Click to expand...
Click to collapse
Try restarting.
Still can't tried changing sfs to IMG,changed the initrd for r/w but still can't install apps from play store even if they are system apps
---------- Post added at 05:59 PM ---------- Previous post was at 05:58 PM ----------
It runs well , with su
support but would like to download games for x86 then to have to transfer games from online or other devices or resources
How do I get rid of the corrupted USB , I think since the system and other IMG s are read only it can't install properly
I still get corrupted as ,but adding folders Android/data ,and data to the remixos partition it fixed the play store I can now do everything I also made the system.IMG bigger and created my own data.IMG
miko12312 said:
I still get corrupted as ,but adding folders Android/data ,and data to the remixos partition it fixed the play store I can now do everything I also made the system.IMG bigger and created my own data.IMG
Click to expand...
Click to collapse
Today updated to 3.0.205 by OTA. System.IMG may not work with OTA update.
Have you tried installing / updating apps with Remix Central before creating Android/data and data folders ?
I have not used playstore so far.
The android folder is not nessacery as it uses the other portion of Ubuntu as an SD only need data folder I am updated to latest , the corrupted part is the swap space I think , its the only partition I can think of ,but most games run slow on remix and don't work yet
How can I modify the system without it reverting ,so I can modify system apps and delete and install some as system apps
Get Root Access. Install Superuser app from playstore.
Install Titanium backup for backing up of both user and system apps and apps' data.
I think Link2sd app has feature of moving user app to system app.
Hi all.
I decide to post this guide after checking and rechecking internet to find a procedure to install Remix OS (and Android x86 versions higher than 4.4.4) on a eeePC in a reproducible manner. In fact I tried many times and, as I had mixed results, I did not understand why sometimes I was successfull and sometimes not.
Today I was able to provide rationale for this behaviour and now I report my findings hoping to be useful to someone.
Requirements
Asus netbook eeePC
I tested successfully this technique on:
eeePC 1000HE with N280 CPU, 2GB of RAM and a 160 GB HDD
eeePC 1005HA with N280 CPU, 2GB of RAM and a 160 GB HDD
RemixOS 32 bit version 3.x (or Android-x86 version 5.x and higher)
https://www.fosshub.com/Remix-OS.html/Remix_OS_for_PC_Android_M_32bit_B2016101201.zip
Gparted Live
http://downloads.sourceforge.net/gparted/gparted-live-0.26.1-5-i686.iso
A program to create bootable USB stick. For example:
unetbootin
Two USB sticks
Procedure
Create a bootable USB stick containing RemixOS 3.x 32bit following one of many tutorials you can find all over the internet. The easiest way is to use RemixOS for PC Installation Tool program which is given together to RemixOS when you download it. A good alternative (which I prefer) is unetbootin.
Create a second bootable USB stick containing gparted-live. The procedure is very similiar to that used to create the RemixOS booting stick USB and here you can also use unetbootin.
Put the booting stick USB containing gparted-live into an USB port of your eeePC and boot from it following one on the tutorials explaining how to boot an eeePC from an USB stick.
Launch Gparted program and, first of all, delete every partition on the eeePC HDD.
Then, from the GParted main menu, select "Device" > "Create Partition Table".
Here you find 2 possibilities: msods and gpt.
Select "msdos", NOT "gpt"!!! This is the first and more important trick to apply!
After this, use gparted-live to format the entire eeePC HDD using ext4 filesystem.
After having applied this filesystem to all the eeePC HDD, exit from gparted-live and shutdown your PC.
Remove gparted-live USB stick from your eeePC and insert the RemixOS USB stick.
Switch on the eeePC again, booting from the USB stick containing RemixOS, this time.
When the program asks how to install RemixOS, choose "Resident mode" and immedtately after press the "Tab" key on the keyboard to modify the default parameters of the installation.
The original ones are:
/kernel initrd=/initrd.img root=/dev/ram0 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC= DATA= CREATE_DATA_IMG=1
You need to substitute them with:
/kernel initrd=/initrd.img root=/dev/ram0 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC= DATA= INSTALL=1
When the program asks a partition to install RemixOS (or Android-x86), select sda1
Please, Do NOT use the item "Create/Modify partitions" of the menu!
This is the second important trick because otherwise the Partition Table changes to GPT from msdos and nothing works anymore!
On the following screen select "Do not format" (the partition) as already formatted by gparted!
Install boot loader GRUB and skip the installation of EFI GRUB2.
Accept to install /system directory as read-write.
As the last step of the installation, select to reboot the eeePC.
While the system is rebooting, remove the USB stick so the device reboots from the internal HDD.
When the first screen appears, it is a black & white one, and reports that the GRUB used is the version 1.1.5.
Below a menu with 4 choices appears. They are:
Remix OS 2016-10-12
Remix OS 2016-10-12 (Debug Mode)
Remix OS 2016-10-12 (Debug nomodeset)
Remix OS 2016-10-12 (Debug Video=LVDS-1:d)
the first being the default one which starts automatically in few seconds.
Wait quite a little bit (about 10-20 minutes) while a white "RemixOS" logo blinks on a black background.
After this long waiting, Remix OS appears and you can configure it.
In particular as reported by maxiclo here:
http://forum.xda-developers.com/remix/remix-os/bug-currupted-usb-drive-waring-severity-t3472170
there is a a severe issue with RemixOS clean installation on native EXT4 partition using INSTALL=1 (ie the installation on a HDD without other OS).
In fact RemixOS identifies a "Corrupted USB drive" and Android propose to fix it formatting the USB.
If you execute the suggested fix, everything will be damaged and you cannot reboot your eeePC in RemixOS anymore!
So, go to Settings -> RemixOS -> Experimental features
Deselect the option "Enable disk partition mount"
The system ask for a reboot: execute it.
This is the third important trick to use.
That'all folks!