install Remix OS to harddisk (like android-x86) - Remix OS for PC

Hi all
I run android-x86-5.1 (on EeePC 1000H).
android-x86 offered
'Install Android-x86 to harddisk'
menu when booting from SD.
'android-x86' and 'Remix OS' ISO filesystem content look exactly same (see below)
so: Can the Remix OS ISO please be adjusted to also offer install to harddisk?
I read there are tools to install on HD from Ubuntu or Windows, but I am on android-x86 already...
Code:
ISO content
efi
efi/boot
efi/boot/grub.cfg
efi/boot/TRANS.TBL
efi/TRANS.TBL
initrd.img
install.img
isolinux
isolinux/android-x86.png
isolinux/boot.cat
isolinux/isolinux.bin
isolinux/isolinux.cfg
isolinux/TRANS.TBL
isolinux/vesamenu.c32
kernel
ramdisk.img
system.sfs
TRANS.TBL

The installer is there already, you need to manually tell it to install @ boot time with a kernel command edit i.e. INSTALL=1 DEBUG=

ecksdeeay said:
The installer is there already, you need to manually tell it to install @ boot time with a kernel command edit i.e. INSTALL=1 DEBUG=
Click to expand...
Click to collapse
ok I will try...

Dior DNA said:
ok I will try...
Click to expand...
Click to collapse
How can I install in hard disk?

I went a different way than using the existing installer, probably because I didn't know it existed. I have it set up as a boot option in grub, which wasn't that hard to do:
1.Boot into RemixOS, Resident mode like you would by using a flashdrive
2.Boot back into prefered OS ( Linux will save you some time, as you can't really update grub.cfg from Windows)
3. Create a FAT32 partition , 8GB or more. You can use a label for it, if you want.
4.Add the boot entries to /etc/grub.d/40_custom . This is what mine looks like, for example :
Code:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "REMIXOS Resident mode - All your data and apps are saved" {
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 DPI=120 UVESA_MODE=1366x768
initrd /initrd.img
}
menuentry "REMIXOS Guest mode - NO data and apps are saved" {
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= DATA_IN_MEM=1
initrd /initrd.img
}
Obviously, you will need to change out the partitions for your own, and for the DPI and UVESA variables, you can just delete them, as they are set for my screen (1366x768 15.6"), and might look really distorted for you. Of course, you can try tinker with those yourself.

It is quiet simple, but I don't know why is author of Remix OS "hided" installer.
-Prepare one partition on your PC HDD for install Remix OS
-Plug your USB with burned Remix OS in your turned off pc
-Turn on PC
-When GRUB menu loaded (Resident mode, etc...), hit TAB button on your keybord and type:
INSTALL=1
at the and of existing code, than hit the ENTER
-Installer will started, same as Android x86, select your prepared partition for install, and that's it.

stiw47 said:
It is quiet simple, but I don't know why is author of Remix OS "hided" installer.
-Prepare one partition on your PC HDD for install Remix OS
-Plug your USB with burned Remix OS in your turned off pc
-Turn on PC
-When GRUB menu loaded (Resident mode, etc...), hit TAB button on your keybord and type:
INSTALL=1
at the and of existing code, than hit the ENTER
-Installer will started, same as Android x86, select your prepared partition for install, and that's it.
Click to expand...
Click to collapse
Format ext4 o fat32? Boot no work

centrored said:
Format ext4 o fat32? Boot no work
Click to expand...
Click to collapse
Is it work from usb?

stiw47 said:
Is it work from usb?
Click to expand...
Click to collapse
Yes. Work from usb

centrored said:
Yes. Work from usb
Click to expand...
Click to collapse
Sorry, I don't know.

stiw47 said:
Sorry, I don't know.
Click to expand...
Click to collapse
Do not install grub

centrored said:
Do not install grub
Click to expand...
Click to collapse
No, I never install grub of android x86 or grub of remix or any "similar grub" cause they recognize only Winblows and don't recognize GNU/Linux, and I have 5-6 Linux distros installed on hdd. From other side, Linux grub don't recognize android x86 or remix os. Cause that, after I install android or remix, I boot to my main Linux distro and add entry for android or for remix in /etc/grub.d/40_custom.

Dior DNA said:
Hi all
I run android-x86-5.1 (on EeePC 1000H).
android-x86 offered
'Install Android-x86 to harddisk'
menu when booting from SD.
'android-x86' and 'Remix OS' ISO filesystem content look exactly same (see below)
so: Can the Remix OS ISO please be adjusted to also offer install to harddisk?
I read there are tools to install on HD from Ubuntu or Windows, but I am on android-x86 already...
Click to expand...
Click to collapse
Is this the code you are looking for?
https://groups.google.com/forum/#!topic/remix-os-for-pc/WZPbzWspTPU

are this build support for amd64 especially AMD E2 ?

Hi!
I have a similar problem too...
Remix OS doen not work on my eeepc 900. I have installed it on the 16 GB SSD modifying
root=/dev/ram0 with root=/dev/sdb1 (my SSD)
and adding INSTALL=1
When the eeepc starts I see grub 1.5, I choose Remis OS but it is not starting. Then I see the same errors you can watch in this picture: http://uploads.tapatalk-cdn.com/20160201/9574b4a6113671b412096942e994a50a.jpg if I choose to start with DEBUG=1.
Someone can help me?
Sorry for my English.

Just a FYI, in case anyone has missed the recent news, the update coming on March 1 will provide installation on Windows for dual boot and storage.
http://www.androidcentral.com/remix-os-beta-launch-coming-march-1-more-features-android-pc

Hi!
Same problem with Remix OS Beta 32bit... Very sad!
The system stops with [email protected]_x86:/ # and blink blink blink
HeLp! =)

Exact same thing here. I switched from the official remix to the hacked version and nothing is different.

hi
please help me
don't install remix for pc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

At the choose partition screen I can't click on a partition or
hit the OK button

Related

[WIP] Remix OS for PC W/ Xposed Project ROC - V3.0.207 [Pre-rooted] [Busybox] [GAPPS]

I present to you
Project ROC - Remix OS Custom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
Features:
1. XposedFramework V86 X86
2.Pre-rooted with SuperSU 2.76
3.Busybox
4.CM File Manager (root access to files)
5.Deodexed
6.Debloat
7.Adaway
8.GAPPS
Changelog for Project ROC
V3.0.207
Updated to version 3.0.207
Updated GAPPS
Updated SuperSU
V3.0.206
Xposed Framework V86 X86
SuperSU 2.76
Busybox
CM File Manager
Deodex
Adaway
Changelog for Remix OS 3.0.207 by Jide
Remix OS version: 3.0.207
Release date: November 25, 2016
Remix OS Build Number - 64-bit: B2016112101
Remix OS Build Number - 32-bit: B2016112201
Release notes:
1. Added Verbose mode to save log files for easier debugging.
Guidelines: https://github.com/JideTechnology/Remix-OS-For-PC/wiki
2. Updated Linux kernel to 4.4.30
3. Added "Never sleep option" to be seen in languages other than English
4. Fixed a bug there was an issue remembering the last selected system in your boot menu
__________________________________________________ _____________
If you experience any bugs or issues, report it through our Verbose mode!
Changelog for Remix OS 3.0.206 by Jide
Release date: October 11, 2016
Release notes:
- Houdini update resolved issues with apps like Snapchat and Candy Crush
- Fixed most dual GPU issues
- Fixed keyboard input issues when key-mapping is activated
- Fixed conflicts between mouse and keyboard input when key-mapping is activated
- Added Wi-Fi drivers for Realtek wireless cards - rtl8723bs, rtl8723bu, rtl8812au
- Updated Gaming Toolkit to v.1.2.1
- Improved boot menu
- Added touchscreen drivers from Next Window (touchscreen manufacturer)
- Ads have been removed from the 'My apps' section of your app drawer
Click to expand...
Click to collapse
Install Instructions:
LEGACY
1. Extract Project ROC
2. Run Remix OS Installation Tool
3. Select Project ROC with the corresponding version number for the ISO
4. Select desired install location: Hard Disk or USB
5. Select target drive and partition
6. Press OK and allow the installer to finish
7. Close the installer and navigate to the installer location (Since I installed to my C: partition, it was located at C:\RemixOS\)
8. Open menu.lst with your favourite text editor (I used Notepad++)
9. Add this: REMOUNT_RW=1 after SRC=RemixOS/
Make sure the red code is added like this:
Example:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/[B][COLOR="Red"] REMOUNT_RW=1 [/COLOR][/B]DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
10. Save and reboot to Project ROC
11. All versions from .205 will have the Xposed Framework files included, but must be manually installed to be able to use. If you want to install and use Xposed Framework then follow these steps!
Boot Remix OS with Debugging
To do this add the flag: "DEBUG=1" just like earlier with the "REMOUNT_RW=1" flag! (You can remove it once you have installed Xposed!)
When it asks you to type exit do not type exit, instead follow this: 1. "su" (allow su permission 2. "cd /system/xposed" 3. "sh flash-script.sh" 4. "exit" 5. "exit"
e.g.
>su
>cd /system/xposed
>sh flash-script.sh
>exit
>exit
12. Update all apps via Google Play Store
UEFI
Thanks to @Vioner for letting me use his instructions!
Now you need to make the change persistent:
For Remix OS installed on hard drive:
LEGACY BOOT:Apply adequate changes to grub.cfg or menu.lst file in your Remix OS installation folder. Editing both files won't hurt
UEFI BOOT: Apply adequate changes to EFI:/boot/grub/grub.cfg file in your ESP (EFI System Partition) - example path Z:/boot/grub/grub.cfg
Instruction on how to access grub.cfg file on Windows
BEWARE, ACCIDENTALLY REMOVING OR MODIFYING SOME FILES FROM ESP PARTITION WILL RENDER SYSTEMS NOT BOOTABLE - WILL REQUIRE RECOVERY TOOLS.
To access ESP, you need to:
start cmd.exe as administrator
Kill Explorer -> Mount the ESP -> Start the Explorer as admin using below commands:
Code:
taskkill /f /im explorer.exe
mountvol Z: /s
explorer.exe
If you fail to mount the system partition then it's probably already mounted. Start notepad as administrator then browse My computer and you should find a SYSTEM drive - that's ESP.
Edit & save the EFI:/boot/grub/grub.cfg file
Reboot and test if the changes worked(if you reboot into Windows, the ESP should be inaccessible again - it automatically unmounts upon restart)
For Remix OS installed on a USB stick:
You will need to access USB partition labeled REMIXOSSYS.
Filesystem of this partition is not supported by Windows, so without any 3rd party apps you won't be able to modify the needed files.
You will need to either use a Linux distribution or edit from Remix OS on other device. Be dexterous
LEGACY BOOT:Apply adequate changes to REMIXOSSYS:/SYSLINUX.CFG
UEFI BOOT: Apply adequate changes to REMIXOSSYS:/boot/grub/grub.cfg
Add a post with your results after using the guide and hit Thanks it it worked for you List your device brand and model & GPUs models + Remix OS version
Downloads:
Google Drive
32-bit: V3.0.207
V3.0.207 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUX1RkaWhGTXFxQlU
V3.0.207 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUZm04R2o2U3lIR00
64-bit: V3.0.207
V3.0.207 (XPOSED NOT INCLUDED, IT CAUSED BOOT PROBLEMS https://drive.google.com/open?id=0B-mpriMWe2WUUWtVVW5hLXdYUkk
V3.0.207 GAPPS (XPOSED NOT INCLUDED, IT CAUSED BOOT PROBLEMS) https://drive.google.com/open?id=0B-mpriMWe2WUaFVUS0JBVGZGN3M
32-bit: V3.0.206
V3.0.206 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11)https://drive.google.com/open?id=0B-mpriMWe2WUclVMWUZnZ1dIY0E
V3.0.206 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUNk5ZWDUxTU9ralE
64-bit: V3.0.206
V3.0.206 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUUTl1ZDlRN3BZLWs
V3.0.206 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUR2JiVmZKelRKdU0
Credits:
Jide for providing us with an awesome OS
@rovo89 for Xposed Framework
@Chainfire for SuperSU
@Stericson for Busybox
@mrRobinson for Adaway
@HypoTurtle You are the real MVP, you quite literally made this possible, from creating modified files, to helping my stubborn brain understanding what to do!
@[email protected] You are just awesome bro, Giving me all the information I need!
@PizzaG for linking me to the the right places! You saved me so much time!
Android (Google) for Android
CyanogenMod Team for the apps
Donations
ORIOL BLADE RADUA - Thanks for the first donation; It means a lot to me!
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!​
....is there any chance for a 64bit system support?
<<<New World Order (NWO)>>>
[email protected] said:
....is there any chance for a 64bit system support?
<<<New World Order (NWO)>>>
Click to expand...
Click to collapse
Yes there is, it will probably be done by tomorrow!
moman2000 said:
Yes there is, it will probably be done by tomorrow!
Click to expand...
Click to collapse
Any news on 64 version?
Ota2501 said:
Any news on 64 version?
Click to expand...
Click to collapse
It is done! Uploading now!
moman2000 said:
It is done! Uploading now!
Click to expand...
Click to collapse
...great news!
<<<New World Order (NWO)>>>
[email protected] said:
...great news!
<<<New World Order (NWO)>>>
Click to expand...
Click to collapse
MEGA is being slow right now, so instead, I will upload to Google Drive first then MEGA later!
ETA 4 MINS
V3.0.203 x64 is out now!
moman2000 said:
V3.0.203 x64 is out now!
Click to expand...
Click to collapse
And off course, thank you very much, sire.
Ota2501 said:
And off course, thank you very much, sire.
Click to expand...
Click to collapse
My pleasure!
moman2000 said:
My pleasure!
Click to expand...
Click to collapse
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
pra27 said:
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
Click to expand...
Click to collapse
Can you get into Windows, or this error happening when you boot Remix OS? This seems to be related to the menu.lst file, did you edit it like shown in the picture?
moman2000 said:
Can you get into Windows, or this error happening when you boot Remix OS? This seems to be related to the menu.lst file, did you edit it like shown in the picture?
Click to expand...
Click to collapse
Yes I can boot into Windows. This error only appears whenever I install remix os and I just copy pasted and saved carefully all what you have posted in first post.
And that is same as the picture I think.
pra27 said:
Yes I can boot into Windows. This error only appears whenever I install remix os and I just copy pasted and saved carefully all what you have posted in first post.
And that is same as the picture I think.
Click to expand...
Click to collapse
Go to the remixOS folder and open the uninstaller, then reinstall it, open the menu.lst file and just add this: REMOUNT_RW=1 after SRC=RemixOS/
eg
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
Is this version working in Ubuntu?
SM-N920C cihazımdan Tapatalk kullanılarak gönderildi
matomik said:
Is this version working in Ubuntu?
SM-N920C cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
Yes it will work, just use grub-customizer to add an entry for remix os!
But I have realised that it wont work instantly, you will need to use windows, install it (follow the instructions),and then boot it (not from ubuntu's grub but windows), let it boot up then restart and boot from grub! If you have skype I could tell you how to do it easily! Just PM me!
you can fix playback 1080p problem
pra27 said:
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
Click to expand...
Click to collapse
Your problem is with the grub; not sure which grub @moman2000 added but if it's the one jide included then hopefully the ntfs grub module was also included and it just needs to be insmod'ed in grub.cfg/menu.lst
For me 64bit version don't start. Bootloop on remixos. With official version no problem.
framir said:
For me 64bit version don't start. Bootloop on remixos. With official version no problem.
Click to expand...
Click to collapse
I suspect it is Xposed not being comaptible with x64, I will need to ask @rovo89 where the files go for x64!

[HELP] Remix does not go beyond logo.

I have a HP Pavillion 15 laptop core i7 intel HD witn nvidia 840m onboard graphics.
I have tried installing remix os a hundred times now. no kidding
messing up bcd entries along the way but anyhoo,
here is what I do,
Disable Secure boot
Create a new NTFS 32GB partition.
Install Remix OS on it. with 16gb data partition.
Reboot , select Remix OS from os selection screen.
Now androidx86 logo comes up , formats the partition, I get a warning "Warning had difficulty in writing superblocks" something like that, then it takes me to remix os boot screen and thats it!
it has been hours now but it won't move beyond that point.
The Remix os logo simply keeps flashing infinitely. At this stage even the hard drive activity led on the laptop goes off....
I even tried setting noveau.modeset=0 i915.modeset=1 but nothing helps.
The Remix OS screen just keeps flashing.
I cannot find any solution to this,
Has anyone ever encountered this or know how to fix it?
tried androidboot.swrast=1
still nothing.
Running with DEBUG=1 gives some mount errors.
any help guys ?
any Jide staff members here?
vikas_toad said:
tried androidboot.swrast=1
still nothing.
Running with DEBUG=1 gives some mount errors.
any help guys ?
any Jide staff members here?
Click to expand...
Click to collapse
Try 'REMOUNT_RW=1'
Example:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/[B][COLOR="Red"] REMOUNT_RW=1 [/COLOR][/B]DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
It will convert the system.sfs file to system_dev.img and allow read/write!
Maybe that is the issue?
Good luck!
moman2000 said:
Try 'REMOUNT_RW=1'
Example:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/[B][COLOR="Red"] REMOUNT_RW=1 [/COLOR][/B]DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
It will convert the system.sfs file to system_dev.img and allow read/write!
Maybe that is the issue?
Good luck!
Click to expand...
Click to collapse
nope still the same.
anything that I can do to atealst understand whats going wrong ?
anyone?
vikas_toad said:
nope still the same.
anything that I can do to atealst understand whats going wrong ?
anyone?
Click to expand...
Click to collapse
Try using a different hard drive, the one you're using may be damaged in some way !
vikas_toad said:
tried androidboot.swrast=1
still nothing.
Running with DEBUG=1 gives some mount errors.
any help guys ?
any Jide staff members here?
Click to expand...
Click to collapse
Any chance those 'mount errors' are that /data is read-only?
If so from DEBUG=1 try:
Code:
cd /mnt/RemixOS
e2fsck -f data.img
reboot
moman2000 said:
Try using a different hard drive, the one you're using may be damaged in some way !
Click to expand...
Click to collapse
Using a laptop. Using a different harddrive isn't really an option
HypoTurtle said:
Any chance those 'mount errors' are that /data is read-only?
If so from DEBUG=1 try:
Code:
cd /mnt/RemixOS
e2fsck -f data.img
reboot
Click to expand...
Click to collapse
not sure what they are. any way I can capture logs so that I can post them here ??
I think that will better ..
Hi, i have the same problem, installed latest version, had to set nouveau.modeset=1 i915.modeset=0 because i have a Geforce 710m graphics card. I have an i3 laptop.
After i set these in menu.lst it boots till the Remix Os logo, but doesn't go past.
I have no idea what to try, i have windows 10
vikas_toad said:
Using a laptop. Using a different harddrive isn't really an option
not sure what they are. any way I can capture logs so that I can post them here ??
I think that will better ..
Click to expand...
Click to collapse
You can easily replace a hard drive in a laptop... I have done it hundreds of times, there should be a panel with a few screws on it!
Not so sure on capturing logs, maybe you can use "DEBUG=1"
@vikas_toad ""Warning had difficulty in writing superblocks" - your HDD is not up for the job. You need to try and fix the bad blocks or if it fails you need to replace the drive. @HypoTurtle gave you the best solution.
1. Boot Remix
2. In Grub selection select Remix and press "e" to edit the menuentry
3. If you are on legacy boot then use arrows to go to the kernel line and press "e" / if you are in UEFI boot (Grub2) then just move to the kernel line with arrows
4. Now add "DEBUG=1" without the quotation marks anywhere withing that kernel line, but after the kernel word.
5. On legacy press enter and then F10 / ON UEFI only press F10
6. Now follow @HypoTurtle tips:
HypoTurtle said:
Code:
cd /mnt/RemixOS
e2fsck -f data.img
reboot
Click to expand...
Click to collapse
7. Now try to boot Remix. If it fails I advise you to run disk checking and fixing for your whole drive.
If you are still unsure how to enter the DEBUG mode, you can go to this guide: http://support.jide.com/hc/en-us/articles/218463867-How-to-increase-the-memory-size-
If this helped remember to hit thanks for @HypoTurtle and me
This is what i got after i used DEBUG:
VFS: could not find a valid V7 on sda.
VFS: could not find a valid V7 on sda1.
VFS: could not find a valid V7 on sda2.
EXT4-fs (loop1): couldn't mount az ext3 due to feature incompatibilities.
What should I try?
Edit: i was able to boot fine with nomodeset vga="xxx"
But this is not ideal, no hardware acceleration and not good resolution.
@Szighy I don't know if your nvidia GPU is well supported, but I'm pretty sure that the Intel will work better, so instead of disabling Intel, disable nvidia. Use nouveau.modeset=0 and try to boot.
If that won't allow for complete boot then most likely you must disable nvidia GPU completely. Some devices allow that via BIOS settings - find graphics options and make sure the integrated GPU and only it is enabled.
If you don't have that option in BIOS then I'm sorry, but you will have to wait for new releases with fixes and better drivers or use software renderer (androidboot.swrast=1) or the nomodeset with properly picked resolution.
Remember that nvidia drivers are unofficial, they are actually reverse engineered and then adjusted to work on Linux. As far as I know Nvidia doesn't officially create Android drivers "we are on our own".
That's why nouveau will probably never be good enough.
Sent from mobile
Thanks for your detailed reply, already tried the first too methods, nouveau.modeset=0 fails, i am able to boot fine with vga=791 and and 794, everything else fails, if i set the exact resolution (using vga=ask, then selecting from the list, that fails too). So no way to adjust the resolution.
"androidboot.swrast=1" - i didnt hear about this one, do i add this like the flags? I have to do some research about it
EDIT: no option to selected integrated graphics in bios
EDIT 2: WOW, i was able to boot fine with androidboot.swrast=1.
You made my day, resolution is perfect now, i cant be thankful enough, i was trying the whole night.
@Szighy that's great Remember to report your problems here https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
androidboot.swrast=1 means Remix OS graphics are rendered by the CPU - games and 3D rendering will most likely be much slower and the whole system may be less stable, because in some cases the software renderer crashes.
I'd say swrast is a temporary solution. I hope your device gets better GPU support.
Sent from mobile
Vioner said:
@Szighy that's great Remember to report your problems here https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
androidboot.swrast=1 means Remix OS graphics are rendered by the CPU - games and 3D rendering will most likely be much slower and the whole system may be less stable, because in some cases the software renderer crashes.
I'd say swrast is a temporary solution. I hope your device gets better GPU support.
Sent from mobile
Click to expand...
Click to collapse
yep, definitely not ready to daily usage this way, i'll wait some time and hope it will get better support, but at least I could try it
HypoTurtle said:
Any chance those 'mount errors' are that /data is read-only?
If so from DEBUG=1 try:
Code:
cd /mnt/RemixOS
e2fsck -f data.img
reboot
Click to expand...
Click to collapse
Vioner said:
@vikas_toad ""Warning had difficulty in writing superblocks" - your HDD is not up for the job. You need to try and fix the bad blocks or if it fails you need to replace the drive. @HypoTurtle gave you the best solution.
1. Boot Remix
2. In Grub selection select Remix and press "e" to edit the menuentry
3. If you are on legacy boot then use arrows to go to the kernel line and press "e" / if you are in UEFI boot (Grub2) then just move to the kernel line with arrows
4. Now add "DEBUG=1" without the quotation marks anywhere withing that kernel line, but after the kernel word.
5. On legacy press enter and then F10 / ON UEFI only press F10
6. Now follow @HypoTurtle tips:
7. Now try to boot Remix. If it fails I advise you to run disk checking and fixing for your whole drive.
If you are still unsure how to enter the DEBUG mode, you can go to this guide: http://support.jide.com/hc/en-us/articles/218463867-How-to-increase-the-memory-size-
If this helped remember to hit thanks for @HypoTurtle and me
Click to expand...
Click to collapse
I tried that but it failed
Superblock invalid, trying bakup superblock
bad magic number in super block while trying to open data.img
The superblock cannot be read or does not describe a correct ext2 filesystem.
...............
you might try running e2fsck with an alternate superblock
e2fsck -b 8193 <device>
formatted the drive now.
I am running chkdsk with /x /f /r on the drive where Reix was isntalled
Let's see
C:\WINDOWS\system32>chkdsk G: /f /x /r
The type of the file system is NTFS.
Stage 1: Examining basic file system structure ...
256 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
276 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
11 data files processed.
CHKDSK is verifying Usn Journal...
1632 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
240 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
8393768 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
33653759 KB total disk space.
30804 KB in 7 files.
8 KB in 12 indexes.
0 KB in bad sectors.
47871 KB in use by the system.
45664 KB occupied by the log file.
33575076 KB available on disk.
4096 bytes in each allocation unit.
8413439 total allocation units on disk.
8393769 allocation units available on disk.
no problems found :/
reinstalling and trying again now
chkdsk shows no problems
Still no progress... I get the same error.. about writing to superblocks.
What else can I do ?
how do I capture logs so that I can post them here.
@vikas_toad please make a screenshot of SMART status of your hard drive.
Use AIDA64 for it - portable .exe here: http://download.aida64.com/aida64extreme575.zip
In Aida go to Storage -> SMART -> Select your drive -> Make screenshot
Should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from mobile
vikas_toad said:
I had a similar problem lately. Trying to format a hard drive to ext4. I kept getting the warning message about the super blocks. The answer was pretty simple.
Give this a try, reformat the partition as NTFS and and use the long formatting process where it writes zeros all the way across the partition.
It works for me.
Click to expand...
Click to collapse

[GUIDE] Remix OS 3.0 alongside GRUB2

Hello everyone!
After a long day yesterday trying to install Remix OS alongside my already existing Windows 10 and Fedora 24 installations, managed by GRUB2, I finally completed the task.
I decided that I'm going to save other people wanting to do this some trouble, and post the updated guide, since personally I couldn't find it anywhere. It's mainly based on this guide and other similar ones (including the one by @remixtester here on XDA), and since RemixOS changed the install process a little bit, now it's actually done in 10 easy steps.
Recommended system requirements:
2 GHz dual core processor or better
2 GB system memory
Minimum 8 GB of free hard drive space
Internet access is helpful
1. Download the official latest Remix OS 3.0
2. Install Remix OS to a flash drive, using the provided Windows tool. If you don't have Windows, use Rufus or similar piece of software for your OS.
3. Create an at least 8 GB ext4 partition, and disable secure boot. Remember the partition number you are assigned
4. Boot from the flash drive, from the menu that follows click "e" on Resident Mode.
5. Delete > DATA= USB_DATA_PARTIOTION=1 and replace it with > INSTALL=1
6. Select your partition number, format it to ext4
7. Skip GRUB2, skip EFI GRUB and skip Write/Read Access
8. Reboot back to your Linux distro and open the Terminal
9. Log in as superuser and input: > gedit /etc/grub.d/40_custom
Add (do not remove the existing text in the file) the following text to the file. Replace the "X" in set root='(hd0,gptX)' with your partition number. Also paste the text exactly as is, the formatting is crucial for it to work:
HTML:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
insmod ext2
set root='(hd0,gptX)'
linuxefi /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/RemixOS UVESA_MODE=1920x1080 verbose logo.showlogo=1
initrdefi /RemixOS/initrd.img
}
10. Rebuild your GRUB:
For Fedora distribution:
grub2-mkconfig -o /boot/efi/EFI/Fedora/grub.cfg
For other Linux distributions:
grub2-mkconfig -o /boot/grub2/grub.cfg
Alternatively:
update-grub
Upon reboot you'll see Remix OS added to your OS entries and you should be able to boot up and use it just fine.
@engmia Great guide! Although I prefer Grub-Customiser!
The GUI makes everything so easy!
Just to be sure...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If that's my partition list, and that the 20 GO is the partition I created for Remix OS, then I should write set root='(hd0,gpt4)' ?
7. SKIP GRUB2, EFI GRUB and Write/Read Access
Click to expand...
Click to collapse
So thats skip Grub2, skip EFI grub and Yes to W/R Access?
set root='(hd0,gptX)'
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B9L5kBcmfDqVbWxRU29CbDh4S00
This means it will read set root='hd2,gpt4)'?
Another thing is it cant find /RemixOS/kernel
any ideas?
Ok followed each step by step and i end up with
something (hd2,gpt4) something
must load kernel first
Click to expand...
Click to collapse
on bootup.
Now previously i had it installed via windows 10 on my ssd where i deleted the entry from windows boot manager and put the entry in grub. Everything booted fine. But i didnt want it on my ssd. So i followed this to put it on its own partition on a hdd with ubuntu on it. Also when i try to do the grub2-mkconfig it says "command not recognized did you mean grub-mkconfig"
Vodkanakas said:
Ok followed each step by step and i end up with
on bootup.
Now previously i had it installed via windows 10 on my ssd where i deleted the entry from windows boot manager and put the entry in grub. Everything booted fine. But i didnt want it on my ssd. So i followed this to put it on its own partition on a hdd with ubuntu on it. Also when i try to do the grub2-mkconfig it says "command not recognized did you mean grub-mkconfig"
Click to expand...
Click to collapse
In Ubuntu you can just do
Code:
sudo update-grub
Ok still cannot get this thing going. So heres the run down
UEFI Boot only in bios
sda1,2,3,4 Only windows 10 it makes 4 partitions
sdb1 storage
sdc1 efi
sdc2 ubuntu
sdc3 RemixOS
sdc4 Swap
so i do everything that the instructions say and i get an error for unable to find /RemixOS/kernel and i need to load the kernel first. i think its detecting the partition now due to no having the disk hd2,gpt3 error
Is it possible to install grub/theme using Windows?
Wryth said:
Just to be sure...
If that's my partition list, and that the 20 GO is the partition I created for Remix OS, then I should write set root='(hd0,gpt4)' ?
Click to expand...
Click to collapse
Yes, correct.
Vodkanakas said:
Ok still cannot get this thing going. So heres the run down
UEFI Boot only in bios
sda1,2,3,4 Only windows 10 it makes 4 partitions
sdb1 storage
sdc1 efi
sdc2 ubuntu
sdc3 RemixOS
sdc4 Swap
so i do everything that the instructions say and i get an error for unable to find /RemixOS/kernel and i need to load the kernel first. i think its detecting the partition now due to no having the disk hd2,gpt3 error
Click to expand...
Click to collapse
This sounds like an error due to a wrong path set in the GRUB configuration. Are you certain you have set the correct number for your device? Do you have 3 separate hard drives on your device?
engmia said:
This sounds like an error due to a wrong path set in the GRUB configuration. Are you certain you have set the correct number for your device? Do you have 3 separate hard drives on your device?
Click to expand...
Click to collapse
Yes three seperate hdd in computer and set root='(hd2,gpt3)'
Vodkanakas said:
Yes three seperate hdd in computer and set root='(hd2,gpt3)'
Click to expand...
Click to collapse
Sorry for the late reply. Frankly I don't know how to help you, I can only repeat that to me it looks an error in the partition path. Try double checking what number has your distribution been assigned to terminal.
Guys, FYI we are reworking the INSTALL=1 installer. It should be done within 2-3 weeks. Initial release might be unofficial.
i clicked remix os on the grub and this messages shows up
error: cant find command `linuxefi';
error: cant find command `initrdefi'.
Press any key to continue.....
Click to expand...
Click to collapse
what should i do now? my resolution is 1366x768, http://imgur.com/a/yz4xs
@Ravagioli in grub customizer change linuxefi to linux and initrdefi to initrd.
Can I set the data partition to a specific partiorion on my hdd ??
I have booted RemixOS with no problems however i think it would be better if i could mount one of my hard disk partition as the data partition !!
How can I do that ??
I'm on Kali linux and refind bootmanager !!
Is there a way to disable the Flashing Remix OS logo and see exactly what's going on in the terminal?
It seems to stick for an awful long time on this screen. I've put the files in a seperate partition in Ubuntu /dev/sda3 (hd0,3)
The boot sequence seems to go fine right until this screen, and I'm using the UVESA=1920x1080
I have a Lenovo laptop, booting in legacy mode with an intel chipset.
Thanks for your help
Lisa
This can only be done when install Remix to flash drive? What about hard drive?
uttarayan21 said:
I have booted RemixOS with no problems however i think it would be better if i could mount one of my hard disk partition as the data partition !!
How can I do that ??
I'm on Kali linux and refind bootmanager !!
Click to expand...
Click to collapse
pipyakas said:
This can only be done when install Remix to flash drive? What about hard drive?
Click to expand...
Click to collapse
This guide is for installing it to the hard drive?
Just make sure to check what the updates in the install procedure are, as you were informed the INSTALL=1 will be reworked and something might've changed.
lisa107b said:
Is there a way to disable the Flashing Remix OS logo and see exactly what's going on in the terminal?
It seems to stick for an awful long time on this screen. I've put the files in a seperate partition in Ubuntu /dev/sda3 (hd0,3)
The boot sequence seems to go fine right until this screen, and I'm using the UVESA=1920x1080
I have a Lenovo laptop, booting in legacy mode with an intel chipset.
Thanks for your help
Lisa
Click to expand...
Click to collapse
I'm quite sure there was a full text boot option somewhere, try Googling it. As far as I could remember, the flashing logo was there when the install procedure wasn't completed successfully. Can you boot from a USB drive?
Make sure to see the last few posts. @Vioner informed the install=1 will be reworked.
engmia said:
This guide is for installing it to the hard drive?
Just make sure to check what the updates in the install procedure are, as you were informed the INSTALL=1 will be reworked and something might've changed.
I'm quite sure there was a full text boot option somewhere, try Googling it. As far as I could remember, the flashing logo was there when the install procedure wasn't completed successfully. Can you boot from a USB drive?
Make sure to see the last few posts. @Vioner informed the install=1 will be reworked.
Click to expand...
Click to collapse
Thanks, but I managed to work out what my problem was, you need to ensure the SRC= command points to the remix 'system.img' I wrote everything up here for those still having problems:
https://forum.xda-developers.com/re...oot-screen-t3329554/post70838891#post70838891
lisa107b said:
Thanks, but I managed to work out what my problem was, you need to ensure the SRC= command points to the remix 'system.img' I wrote everything up here for those still having problems:
https://forum.xda-developers.com/re...oot-screen-t3329554/post70838891#post70838891
Click to expand...
Click to collapse
Awesome, happy to hear you worked it out.

Remix not booting from GRUB after update

Hi,
Updated Remix to version 3.0.207 yesterday. My PC has Ubuntu 16.04, Windows 10, and Remix OS booting through GRUB 2. After the update, I could no longer boot into Remix via GRUB. I get an error something like "Cannot locate kernel in /RemixOS/kernel" I found this thread and followed the instructions, but this didn't work. My current GRUB config for Remix looks like this:
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
linuxefi /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/RemixOS UVESA_MODE=1366x768 verbose logo.showlogo=1
initrdefi /RemixOS/initrd.img
}
I can see several problems with this since there is no "/RemixOS/kernel" directory and no "/RemixOS/initrd.img" on the Remix partition. How do I fix this problem? My Remix OS partition looks like this (I removed data.img to reduce size).
Thanks!
Kp
Before using the Grub 2 guide (I don't recommend it), how did you install Remix OS? (with Windows official tool/Linux official beta installer/bootable installer, manually using unofficial methods?)
Did you do manual changes to the grub configuration file?
Can't download that drop box file now, but I'll look later.
It'd be better if you posted a screenshot with filetree of partition where RemixOS folder is placed.
Vioner said:
How did you install Remix OS? (with Windows official tool/Linux official beta installer/bootable installer, manually using unofficial methods?).
Click to expand...
Click to collapse
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/F/RemixOS
Hope this is helpful.
Thanks!
Kp
Originally the grub configuration doesn't have static Remix path like in your case - it searches for it instead. Thanks to that, if you switch drives order (f.e. plug drive into different port) it still works.
So I highly recommend switching to this method. Rather try to use the original grub.cfg contents than use unofficial method. Any unofficial stuff makes support harder.
Also this method may be hindered if you have RemixOS folder on multiple partitions so have it in mind.
@HypoTurtle found what's the issue below.
Kpenguin.5284 said:
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
/F/RemixOS
Hope this is helpful.
Thanks!
Kp
Click to expand...
Click to collapse
Where is your system.sfs/kernel/initrd/ramdisk.img?
In the efi folder maybe?
Oh, ur kernel initrd and rmdisk system.sfs should all be in the RemixOS folder. I didn't look closely sorry. @HypoTurtle catched the problem.
The official installer wouldn't put system.sfs to anywhere else than RemixOS. You must've fiddled with the files. I've never heard of this kind of file setup.
I hope the recent OTA didn't go this wrong.
I installed Remix-OS (iso downloaded today) on my brother's laptop today after installing Manjaro Linux.
it failed to add itself in grub, and os-prober doesn't find it, but simply adding to /etc/grub.d/40_custom:
Code:
menuentry "Remix-OS" {
set root=(hd0,1)
linux /RemixOS/kernel
initrd /RemixOS/initrd.img
}
solved it.
you have to check out the HD numbering of Grub. the partition was the first of the only HD and I had to choose "hd0,1"
Vioner said:
You must've fiddled with the files. I've never heard of this kind of file setup..
Click to expand...
Click to collapse
I'm pretty sure I haven't messed with the files at all.
Here's a timeline of what I did before and after the update:
Got notification that a new update had been downloaded. Hit reboot and update. Computer reboots, and I select Remix in the GRUB menu. Remix boots to a blue update screen with a percentage bar. The update completes and the Remix desktop appears. I use Remix for about five minutes and then shut down. A few hours later, I try to boot into Remix, but it shows a black terminal-like screen with the "cannot find kernel" error.
I'm pretty sure I haven't done anything unusual with the system or files. I've searched in the Remix partition, but the kernel folder, rmdisk, and system.sfs are all missing. I don't understand how Remix was able to work at all after the update if those files were missing. Since those vital files are missing, I guess I'll have to reinstall Remix. Is it possible to me to keep data.img, reinstall the system files, and then copy it in so I don't have to reinstall all my apps and files?
Thanks for your help,
Kp
Yes, of course you can move data.img elsewhere and then restore it after reinstall.
Have you looked for the missing files? It'd be good to know where they landed eventually.
Vioner said:
Yes, of course you can move data.img elsewhere and then restore it after reinstall.
Have you looked for the missing files? It'd be good to know where they landed eventually.
Click to expand...
Click to collapse
They're nowhere to be found. Turned every folder inside out.
Kpenguin.5284 said:
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
/F/RemixOS
Hope this is helpful.
Thanks!
Kp
Click to expand...
Click to collapse
you are still having that problem? kernel and initrd.img should be in that boot folder
Just did a fresh install of the latest version of Remix OS using the official installer tool. My /RemixOS folder looks like this:
My grub config file in /etc/grub.d/40_custom looks like this:
Code:
menuentry "Remix OS" --class remixos --class android-x86 --class gnu-linux --class os {
set root=(hd0,6)
search --file --no-floppy --set=root /kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= USB_DATA_PARTITION=1
initrd /RemixOS/initrd.img
}
Remix still won't boot from GRUB and shows this error whenever I try to boot:
Code:
error: no such device: /kernel.
error: file '/RemixOS/kernel' not found.
alloc magic is broken at 0x9e64ae80: 9e524a20
Aborted. Press any key to exit.
Can someone please post what my grub config needs to look like in order for Remix to work? What am I doing wrong here? I copied the grub configuration out of /boot/grub/grub.cfg in the Remix partition. Please help.
Thank you!
Kp
Kpenguin.5284 said:
Just did a fresh install of the latest version of Remix OS using the official installer tool. My /RemixOS folder looks like this:
My grub config file in /etc/grub.d/40_custom looks like this:
Code:
menuentry "Remix OS" --class remixos --class android-x86 --class gnu-linux --class os {
set root=(hd0,6)
search --file --no-floppy --set=root /kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= USB_DATA_PARTITION=1
initrd /RemixOS/initrd.img
}
Remix still won't boot from GRUB and shows this error whenever I try to boot:
Code:
error: no such device: /kernel.
error: file '/RemixOS/kernel' not found.
alloc magic is broken at 0x9e64ae80: 9e524a20
Aborted. Press any key to exit.
Can someone please post what my grub config needs to look like in order for Remix to work? What am I doing wrong here? I copied the grub configuration out of /boot/grub/grub.cfg in the Remix partition. Please help.
Thank you!
Kp
Click to expand...
Click to collapse
I don't know what all those extra options are supposed to be doing, but they werent necessary on the install I did for my brother.
You can try a simple:
menuentry "Remix OS" {
set root=(hd0,6)
linux /RemixOS/kernel
initrd /RemixOS/initrd.img
}
Click to expand...
Click to collapse
capoeiraES said:
I don't know what all those extra options are supposed to be doing, but they werent necessary on the install I did for my brother.
Click to expand...
Click to collapse
I'm nearly positive those options aren't causing the issue. I tried that setup, and it didn't work.
Kpenguin.5284 said:
I'm nearly positive those options aren't causing the issue. I tried that setup, and it didn't work.
Click to expand...
Click to collapse
there is defently some problem with those options since they seam to try to set /kernel as a the root as if it was a HD
try if you find a solution with this search https://www.google.com.br/search?q=...=chrome..69i57j69i58&sourceid=chrome&ie=UTF-8
capoeiraES said:
there is defently some problem with those options since they seam to try to set /kernel as a the root as if it was a HD
try if you find a solution with this search https://www.google.com.br/search?q=...=chrome..69i57j69i58&sourceid=chrome&ie=UTF-8
Click to expand...
Click to collapse
I tried the configuration you posted, but no cigar. It's rather late right now where I live, so I can't look at the search you posted right now, but I will look at it as soon as I can. Thanks!
Update: Checked the search you posted, didn't find anything useful...
from what I read here, https://wiki.archlinux.org/index.php/GRUB, that search option is to search for the root partition. so having both lines, one to set root, and the other to search for it doesn't make sense.
I'm no grub expert. try to find help in a Linux forum.
Anyways, you can try to comenting that search line out

~RemixOS_x64- UEFI or Legacy -Xposed-SuperSU-Gapps~

~RemixOS_x64- UEFI or Legacy -Xposed-SuperSU-Gapps~
Based on version 3.0.207
UEFI Install
1- Download and extract the package I made
2- Run the installer and select the ISO file
3- Reboot and select: Remix OS option
4- Once in RemixOS open the play store and UPDATE SuperSU
5- Open SuperSU and update the binary. It should say success!!
6- Install XposedInstaller_3.0_alpha4.apk or XposedInstaller_3.1.1.apk (i installed 3.0 alpha4 but doesnt matter which)
7- Reboot and enjoy your RemixOS with newest SuperSU, working Xposed and Gapps
Legacy Install
1- Download and extract the package I made
2- Run the installer and select the ISO file
3- Reboot and select: Remix OS option
4- Once in RemixOS open the play store and UPDATE SuperSU
5- Open SuperSU and update the binary. It should say success!!
6- Install XposedInstaller_3.0_alpha4.apk or XposedInstaller_3.1.1.apk (i installed 3.0 alpha4 but doesnt matter which)
7- Reboot and enjoy your RemixOS with newest SuperSU, working Xposed and Gapps
~RemixOS_x64- UEFI or Legacy -Xposed-SuperSU-Gapps~: https://drive.google.com/open?id=0B_NCp06S3NUmWmVIVUN2ZXRzVDA
Xposed Installer 3.0 Alpha 4: https://drive.google.com/open?id=0B_NCp06S3NUmdG1XSWJGS3dBVUk
Xposed Installer 3.1.1: https://drive.google.com/open?id=0B_NCp06S3NUmU21iY3hCdUJtSFE
Credits go to all involved in creating the software in the first place. Please let me know if it works for you
PizzaG Windows 10 EFI Partition Helper: https://drive.google.com/open?id=0B_NCp06S3NUmUVpNR2RheHpOTlk
Run as Admin
The download link doesn't work, gives 404
@crazygamer64
Hopefully links are fixed. That's really odd, the links were working yesterday. But anyways, should be good again.
PizzaG said:
@crazygamer64
Hopefully links are fixed. That's really odd, the links were working yesterday. But anyways, should be good again.
Click to expand...
Click to collapse
worked now thanks!
@crazygamer64
How did the install go? I'm trying to get some feedback vs ROC version which is the same concept just put together a little different. Trying to narrow down some booting issues on various pc setups vs stock working. Thanks
PizzaG said:
@crazygamer64
How did the install go? I'm trying to get some feedback vs ROC version which is the same concept just put together a little different. Trying to narrow down some booting issues on various pc setups vs stock working. Thanks
Click to expand...
Click to collapse
Well, everything worked out great except for that termux command which gave me : can't open flash-script.sh
crazygamer64 said:
Well, everything worked out great except for that termux command which gave me : can't open flash-script.sh
Click to expand...
Click to collapse
UEFI or Legacy install? If UEFI, maybe try the steps from legacy. cd /system.xposed
then run sh flash-script.sh
PizzaG said:
UEFI or Legacy install? If UEFI, maybe try the steps from legacy. cd /system.xposed
then run sh flash-script.sh
Click to expand...
Click to collapse
Well if I try that then it gives me: no such file or directory edit: now it worked, u typed an . Instead of an /
Termux now gave me: can't create '/system/Xposed.prop': file already exists
Also I am using UEFI
Giving this a shot now. Will update.
Are you planning on maintaining this with OTA updates?
Edit: Awesome. I have Remix OS x64 with R/W and Xposed. Worked great, PizzaG. Many thanks!
Time to AdBlock the crap out of everything.
bobdamnit said:
Giving this a shot now. Will update.
Are you planning on maintaining this with OTA updates?
Edit: Awesome. I have Remix OS x64 with R/W and Xposed. Worked great, PizzaG. Many thanks!
Time to AdBlock the crap out of everything.
Click to expand...
Click to collapse
Glad it worked out for you. Yes, I'll do my best to maintain it as OTA updates come out
PizzaG said:
Glad it worked out for you. Yes, I'll do my best to maintain it as OTA updates come out
Click to expand...
Click to collapse
Awesome. One thing to note, I could not get SuperSu to open at all while in DEBUG mode. I ended up booting normal Remix OS and enabling the debug console and doing it this way. Just a heads up!
Sweet sweet proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, like I previously stated... If you also have another operating system installed (I have Windows 10 Pro x64) you can modify a few things about the new bootup process. Wherever you installed Remix OS (I've installed it to a seperate partition, so for me it is E:/), go there.
- Open the Remix OS folder
- Find "menu.lst" and open it with Notepad++
- Delete the entry for Remix OS DEBUG. Delete the whole entry
- Change "timeout" from '10' to '0'
- Save the file
It will look very similar to this:
Code:
default 0
timeout 0
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_x64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
What this will do is remove the entry for Remix OS DEBUG -- INSTALL XPOSED, force standard rooted/xposed Remix OS to boot automatically, and remove the 10 second timeout before the Remix OS selection allowing Remix to boot automatically after selecting it in the Windows bootloader. For advanced users, this can be accomplised in the Remix OS/Remix OS DEBUG selection screen also, by pressing Escape to enter the selection screen, "e" to edit lists, and following the on-screen instructions for deleting selections and saving.
Hope this helps!
Worked perfectly, thanks my friend.
After downloading, the RAR won't extract, says that the file is incomplete, any idea?
jor3l said:
After downloading, the RAR won't extract, says that the file is incomplete, any idea?
Click to expand...
Click to collapse
Your download may be corrupted, try downloading again.
Grindher said:
Your download may be corrupted, try downloading again.
Click to expand...
Click to collapse
Already tried 3 times, same result on my mac, just to confirm this is the MD5 of the file:
MD5 (RemixOS_x64- Xposed-SuperSU-Gapps[v2].rar) = 44ba6fcc6330ad98f1ac375d29b54c5f
---------- Post added at 03:15 AM ---------- Previous post was at 02:57 AM ----------
Worked using WinRar, seems like an issue with The Unarchiver (mac), now testing..
howdy,
successful x64 efi install, bootup, xposed (no flash-script, XposedInstaller_3.0_alpha4.apk works, 3.1.1 doesn't).
apparently everything is nominal. xposed youtube adaway seems to be working. (!)
(i do have a remix problem with my fav game five card draw - grunging $ and win/loss amounts, but that's a remix problem not your adaption)
HP Pavilion x2 12-b020nr 12" Detachable Laptop (Intel Core M3, 4 GB RAM, 128GB SSD) with Windows 10
32gb ntfs partition for remix, use grub2win to boot into remix
good work!
Thanks your work, but seem it not working with Ext4 File system of partition, how can i explan data partition Remix OS from 4Gb to 32Gb?
http://support.jide.com/hc/en-us/articles/218463867-How-to-increase-the-memory-size-
daWyrd1 said:
http://support.jide.com/hc/en-us/articles/218463867-How-to-increase-the-memory-size-
Click to expand...
Click to collapse
thanks you! but i wonderwhy which type format of partition is support for that? maybe only NTFS or include Ext4, bro?
Thanks, it work for me
daWyrd1 said:
howdy,
successful x64 efi install, bootup, xposed (no flash-script, XposedInstaller_3.0_alpha4.apk works, 3.1.1 doesn't).
apparently everything is nominal. xposed youtube adaway seems to be working. (!)
(i do have a remix problem with my fav game five card draw - grunging $ and win/loss amounts, but that's a remix problem not your adaption)
HP Pavilion x2 12-b020nr 12" Detachable Laptop (Intel Core M3, 4 GB RAM, 128GB SSD) with Windows 10
32gb ntfs partition for remix, use grub2win to boot into remix
good work!
Click to expand...
Click to collapse
I try but not work,still error like this
Any idea with my problem,bro?
Gửi từ Redmi Note 3 của tôi bằng cách sử dụng Tapatalk

Categories

Resources