yashsingh1/xdaforums huggingface dataset:
[Remix OS for PC] electrikjesus:
Updated the OP with some more info and rearranged a few things based on suggestions. Thank you all for adding to the collection :)
[Remix OS for PC] HypoTurtle:
Yea, but if you were modifying the guide for PhoenixOS you'd also need an option for Windows [i.e. an archive manager of some sort e.g 7zip]

Just a suggestion but

[Color=blue]default 1
fallback 0[/color]
menuentry 'Remix OS_x64' --class android {
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}

menuentry 'Remix OS_x64- RW' --class android {
search --file --no-floppy --set=root /RemixOS/[color=blue]Read-Write[/color]
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}

Would be helpful to those using tablets without keyboards; the grub entry loaded being determined by a file called Read-Write in the RemixOS folder.
[Remix OS for PC] Vioner:
[MENTION=4056517]HypoTurtle[/MENTION] I don't understand how this is helpful:

search --file --no-floppy --set=root /RemixOS/Read-Write

Could you please explain?

You forgot to mention that the Read-Write file has to be created in the folder in order for the bootloader to find it - what you said of course implicates it, but people won't think of it...

If I understood well - u want tablet users to create or remove the read-write file whenever they want to switch the option?
[Remix OS for PC] bg260:
Yes, you are correct. Didn't think it through as always. That is exactly what I am trying to do. Make it available and easy for the Windows user.
[Remix OS for PC] HypoTurtle:
Yea, if you don't have the means to switch boot entry in grub your options are reduced to having to modify grub.cfg [i.e. mounting ESP] every time you want to switch. [Personally I have a small fat16 partition that I use as a second ESP/EFI]

With the proposed; it looks for the read-write file and if it's there boots entry 1; if it isn't boot fails and switches to entry 0. You could do the reverse I guess with a file called OTA [so you know what it's for]

And it was a suggestion to electric - as something he could add to OP; and I'm sure he'd have clearly pointed out the need/purpose of whatever the specified file will be [might as well call it EJ]
[Remix OS for PC] Vioner:
[MENTION=4056517]HypoTurtle[/MENTION] that's a very good idea! Definitely should be in the guide :)
[Remix OS for PC] andros705:
Errors

I am not able to decompress the system.sfs file. I don't have any system_dev.img in my RemisOS directory and manually decompressing system.sfs gives me ERROR:

$ ./unsquashfs.exe system.sfs

zlib::uncompress failed, unknown error -3

read_block: failed to read block @0x45d0c717

FATAL ERROR aborting: uncompress_inode_table: failed to read block

Parallel unsquashfs: Using 4 processors
[Remix OS for PC] lollyjay:
Err... Are you using the method in the OP of this thread? :confused:
[Remix OS for PC] arts821:
great thank u:good:
[Remix OS for PC] lollyjay:
Isn't it possible to repack the system_dev.img back into system.sfs to take OTA? Or would your mods cause the OTA problems? :confused:
[Remix OS for PC] electrikjesus:
No. Jide's updater looks for a modified system.sfs, and if it sees it, the ota won't apply
[Remix OS for PC] lollyjay:
OK that's what I feared. I made a list of all my system mods so I can do them again after the OTA
[Remix OS for PC] bg260:
I have 4 configuration files in the iso.

grub.cfg = UEFI

grub.cfg.install =?

syslinux.cfg = Legacy?

isolinux.cfg = Legacy?

They all contain the same data, only the formatting is slightly different. Any insight on whether I am in the ballpark. Or am I swinging at a knuckler?

The goal would be. Average user downloads package, starts installer and has new 3rd option in start menu. "Install w/root access"

Thanks

Bill
[Remix OS for PC] electrikjesus:
I'd start with the grub.cfg.install first, then package up the iso and see if that was the right one. Uncharted territory my friend, so trial and error. The other option is to edit them all, but then you have no idea which one was the right one in order to report back ;)
[Remix OS for PC] bg260:
Thanks. I have edited them all. I have the third option shown. Which is a good start. I had a machine go down and the only room I have for an install is on some old hardware. Haven't had success yet and it's inconclusive why. Might have to decide between Win 7 and 10 to make room for UEFI install. Hmmmm.
[Remix OS for PC] electrikjesus:
I ended up making a lite install of win10 and putting that on my w500. it only took up a couple gigs... but it was better than the 15-20 gigs Acer had on it.
[Remix OS for PC] kage69:
same problem

same problem here with remix 3.0.201

how you solve it?
[Remix OS for PC] bg260:
Well, I managed to create a 16Gb partition by doing a live partition table swap:eek:. Borked my BCD in the process but grub-customizer fixed that.

Unfortunately, none of the changes worked. I don't think the command line exists for Phoenix. I'm going to try a different angle. Will check in if I find anything . I appreciate the input.
[Remix OS for PC] electrikjesus:
No. For PhoenixOS, there isn't any options to expand the system.sfs I don't think. Your best bet is to package the iso with a pre-rooted system.img, and then let the PhoenixOS installet do the rest
[Remix OS for PC] bg260:
Yeah, that's what I've done, already. The complaint I'm hearing is the lack of access to windows partitions. Stickmount remedies that, but causes problems if not unmounted when booting to Windows.

It was worth a shot. I'm going to look into systemless, or start digging through my old Remix stuff.

I apologize, I forgot to mention that I was trying to adapt Phoenix to your method. Or I figured you had run into it somewhere.
[Remix OS for PC] HypoTurtle:
I could modify the initrd.img if you want [I was about to do so for RemixOS] - and add in a mechanic for the OTA to still apply.

[MENTION=7185243]bg260[/MENTION] - systemless stuff is about somewhere for PhoenixOS; haven't checked the xposed with it yet.
[Remix OS for PC] bg260:
Sorry, I did not mean to hijack your thread. I am bouncing ideas around. I have looked into Systemless root, I just liked the idea of root being optional in a single package. Root isn't for everyone that's for sure.
[Remix OS for PC] Digong:
i followed all this, i thought i will be able to save and write files directly to my windows and other partition but i still can't :(

why is higher version of remix such a nuissance :/

all these things used to work with remix 2.0, including the basic functionality of resizing playstore window and the capability to snap/resize windows into screen edges..

this little things are what's preventing me from staying with the 3.0
[Remix OS for PC] Cyborg Ninja:
Encryption

Another obrservation, if you have your OS encrypted and have Remix sharing your HDD with your base OS, Remix will not boot. encryption prevents it from reaching the the boot file.

So deactivate whatever encryption of the drive that shares with Remix whether it be Bitlocker or the encryption that comes with your OS installer. Ubuntu/Linux users can still encrypt their home folders if they wish and Remix will still boot.
[Remix OS for PC] Vioner:
[MENTION=7554495]Digong[/MENTION] this guide is for people wanting to have Remix /system partition writable, nothing more.

If you want any more partitions mounted then you need Stickmount app for that.

Sent from mobile
[Remix OS for PC] Ja_som:
Hi,

thanks for this guide...

I've installed latest Remix OS x64 via installer to my HDD, added remount command, rebooted...

It created new system file, but then it stuck on the RemixOS boot screen....

Can you help me?

[MENTION=5532339]DarkAM[/MENTION] how you solved it?
[Remix OS for PC] electrikjesus:
Did you test the latest update first to make sure the kernel updates work with your system?
[Remix OS for PC] Ja_som:
Yes, everithing works fine when I run it with the first option w/o remount_rw
[Remix OS for PC] Vioner:
[MENTION=5201515]Ja_som[/MENTION] are you sure you have the storage space needed for the operation? System_dev.img can take additional ~2.7GB of storage. It may have gotten corrupted while creation though.

It might be possible that you have to make the first Remix Boot before using REMOUNT, but I'm not sure.
[Remix OS for PC] Ja_som:
Yes, I have about 60 GB of free storage on that partition.

(Sorry, but) What is Phoenix Boot? :)
[Remix OS for PC] Vioner:
Haha, sorry, Remix :) both end with "ix" :)

Sent from mobile
[Remix OS for PC] Ja_som:
I use the first boot, also used it few days before used remount boot, or you mean other boot?
[Remix OS for PC] MarcoPLs:
i was able to mount x: but theres no files inside (there are folders but i cant find anything in x:/boot/grub

NEVERMIND
[Remix OS for PC] Dunard:
Going to try this out. Here is the commands that I use to mount.

diskpart

list disk

select disk 0

list partition

select partition 2

assign letter=b

exit

Then use the Explorer++ with admin enabled.

Browse on the Hidden partition b.

No need to kill anything. Reboot twice will change the partition b back to hidden.

================================================================

Thanks a lot. I mess up on my first try. But I got it to work after reinstalled.
[Remix OS for PC] namitutonka:
Thanks [MENTION=928479]electrikjesus[/MENTION], [MENTION=4056517]HypoTurtle[/MENTION], & [MENTION=4762414]lollyjay[/MENTION]. My Dell XPS 12 9250 is now dual-booting Win10 and Remix OS. Now I am looking into enabling xposed framework but have to study [MENTION=5674828]moman2000[/MENTION] 's thread "[WIP] Remix OS for PC W/ Xposed Project ROC - V3.0.207 [Pre-rooted] [Busybox] [GAPPS]"
[Remix OS for PC] moman2000:
Hey, Thank you for your interest in Project ROC!

In this post on my forum I have attached a logcat due to Xposed causing Remix OS x64 to not be able to boot. Perhaps some of you guys and you yourself could help me fix this issue...

Regards,

Mohamed
[Remix OS for PC] bobdamnit:
This explains why I couldn't get your version to boot. I tried the x64 version a while ago and it just didn't boot. :(

Also, in order to make this work for x64 versions of official Remix OS, you must edit the second option as follows (add the red bolded portion):

title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86[COLOR="Red"][B]_x64[/B][/COLOR] androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot

Otherwise it just will not boot.

Edit:

This is entirely optional, but I opted to do it. I didn't want to wait for the timeout, and I wanted Remix OS to boot directly to R/W. So, before I modified my menu.lst file, I copied it to somewhere safe so I had a backup. Then, I modified the

menu.lst file to look exactly like this, enabling auto-boot to R/W mode, removing the option screen, and the timeout:

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

Explanation: I removed the first entry entirely. Then, I copied in the modified part from the original post. Because I'm using the x64 version of Remix OS, I added the _x64 part also. Then, I changed the timeout value from '10' to '0'. (zero)

Again, entirely optional. Much cleaner in my opinion. I still see the Windows bootloader, however now when I pick Remix OS, it will automatically load Remix OS in R/W without the 10 second timeout.
[Remix OS for PC] ouro898:
Thanks for the great help you guys provided. I was able to root my Remix OS. The problem, though, is when I try to play graphics heavy games on the rooted entry like CSR 2 or Marvel Future Fight, it always crashes. Another problem I encounter is that the WiFi and Bluetooth won't turn on. I have to use an ethernet cable to connect online every time.

I'm using a UEFI laptop and here is a copy of my grub.cfg:

set prefix=/efi/RemixOS

if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi

set default="${saved_entry}"
function savedefault {
saved_entry="${chosen}"
save_env saved_entry
}

function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod vbe
insmod vga
insmod video_bochs
fi
}

if loadfont unicode ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod gettext
fi

terminal_output gfxterm
set timeout=30

if [ -s $prefix/themes/Aurora-Penguinis/theme.cfg ]; then
source $prefix/themes/Aurora-Penguinis/theme.cfg
fi

menuentry 'Windows' {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}

menuentry 'Remix OS' --class remixos --class android-x86 --class gnu-linux --class os {
insmod ntfs
insmod exfat
savedefault
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}

menuentry 'Remix OS- RW' --class remixos --class android-x86 --class gnu-linux --class os {
insmod ntfs
insmod exfat
savedefault
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}

submenu 'Remix OS Advanced Options' --class remixos --class android-x86 --class gnu-linux --class os {
menuentry 'Remix OS - Verbose Mode - Save log files for debugging' --class remixos --class android-x86 --class gnu-linux --class os {
insmod ntfs
insmod exfat
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 SAVE_LOGS=1
initrd /RemixOS/initrd.img
}
}

It's fairly long compared to what you guys have, which is only a few lines. I'm hoping somebody can help me about this.
[Remix OS for PC] UmarAbid3DArtist:
I am stuck I wish their was video on how to do this i am stuck at the grub.cfg, grub32.cfg & grub64.cfg and I have the iso from their website. I am not sure in what i sposed to do at this step grub.cfg, grub32.cfg & grub64.cfg? Help I wish their was program that could do this for use for noob like me.
[Remix OS for PC] Dunard:
It sucks that Phoenix OS doesn't have Remix OS boot. Remix OS have a nicer one.
[Remix OS for PC] electrikjesus:
Hello everyone. Since this is my own thread, I have decided it's not hijacking to use it to help announce an ongoing project we at Bliss Roms have started. May I present to you, Bliss-x86 https://xdaforums.com/android/software/x86-bliss-x86-pc-s-t3534657/post70462761#post70462761
[Remix OS for PC] Michajin:
Changing the .ISO before install works by adding REMOUNT_RW=1 to the (3) files. Full root now after install on a usb 3.0. Great job with the help!
[Remix OS for PC] electrikjesus:
Nice! I wasn't 100% sure if it would work ;)
[Remix OS for PC] pkopalek:
Okay - after re-reading this thread two more times, I'm still a bit confused here --

Do you mean (on the ISO before installing) - where I push 'Tab', and add REMOUNT_RW=1 into the installation command? Because that would make sense to me. Otherwise, I don't quite grasp which 3 files.

To me - THIS SOLUTION (which works upon installation and is permanent) would really be the cream of the crop.

I see 4 modifiable files that seem to have some helpfulness:

grub.cfg = UEFI

grub.cfg.install =?

syslinux.cfg = Legacy?

isolinux.cfg = Legacy?

These are the three I'm GUESSING I'm looking at (all from OP):

Part 2 Now that we have the partition mounter, we can open Notepad++ or your favorite code editor as administrator (the same was as before, right click and open as administrator), and browse to X:\BOOT\grub\ and open grub.cfg (Explorer.exe will not show the mounted partition, so we use Notepad++ as an Admin to do this). Then add a second boot entry containing the REMOUNT_RW=1 entry like you see below: (mine might vary from yours a tiny bit)

Code:

menuentry 'Remix OS_x64' --class android {

search --file --no-floppy --set=root /RemixOS/kernel

linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1

initrd /RemixOS/initrd.img

}

menuentry 'Remix OS_x64- RW' --class android {

search --file --no-floppy --set=root /RemixOS/kernel

linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1

initrd /RemixOS/initrd.img

}

Save it and also do this for grub32.cfg & grub64.cfg if they are in that directory as well.
[Remix OS for PC] gbeggo:
[MENTION=5201515]Ja_som[/MENTION] did you ever figure out how to fix that problem?
[Remix OS for PC] Ja_som:
Nope
[Remix OS for PC] gbeggo:
RIP
[Remix OS for PC] D2Dchris:
I succeeded adding REMOUNT_RW=1 to the grub entry. My system files are now writable (i'm now able to apply AdAway, thanks a lot).

But i cannot seem to get Chainfire's SuperSU working (error: SU binary occupied). How did you replace the preinstalled superuser?

Here is how I replaced the buildin superuser app by SuperSU:

https://xdaforums.com/phoenix-os/phoenix-os-news-qa--development/root-how-to-root-phoenix-os-replacing-t3677945
[Remix OS for PC] iCung:
hi, i tried this method but unfortunately, the additional menu doesn't appear when I reboot my notebook. the only menu that appears are windows, remix, and remix debug. do you know why it doesn't appear? i did exactly what you told.
[LG G2 Mini] 0v3rl0rd:
Hi

I have a problem with my D620R. The device reboots.

First of all, let me explain what I did. It had this version before I did anything: V20b-EUR-XX, android 5.0.2.

It was completely stock and I wanted to install CM13, so I did the following:

1. Rooted (link): installed kingroot > rooted > replaced it with supersu > updated bineries. Everything worked ok.

2. Unlocked the bootloader (link): downloaded "aboot_d620r_20a_patched.7z (264.4 KB)" from linked post and flashed it using "dd if=/sdcard/aboot_D620r_20a_patched.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot".

3. Installed TWRP 3.0.2. using RASHR as described here.

4. Downloaded and copied the latest nightly (cm-13.0-20160802-NIGHTLY-g2m.zip).

5. Downloaded and copied the latest gapps (open_gapps-arm-6.0-pico-20160802.zip).

6. Made a backup via TWRP.

5. Cleaned the data, cache and system partitions. Flashed nightly and flashed gapps.

Everything went fine, as far as I could tell.

The problem is - it reboots.

I thought that it had random reboots but then I realized that it reboots at specific actions:

1. I open a (no-matter-which) app

2. I open the recent apps menu and "clean" the app >> SEE THIS VIDEO

3. It reboots.
[LG G2 Mini] natlegal2:
Me too.

I'm having the exact same issue too, I think there's something wrong with the new updates. Try to download an older version to see if everything works alright for you (that solved my problem) [downloaded the "cm-13.0-20160731-NIGHTLY-g2m.zip" version]
[Galaxy Ace II General] beardedpanda:
You always wanted to change your OS from bloated Windows to something different or you're tired of maintaining your virtual machine to flash your device freely. I know that pain!

Now, you could stop cursing your powerlessness. Here comes the solution to all problems.

The answer is called Heimdall. This is a multiplatform tool for flashing our phones (not only ours) like Odin (Odin is available only for Windows). It's created by Glass Echidna, I've just compile binaries of most recent version to make it "multi-distribution". I don't want put you to sleep so, let's get started!

Installation method:

[U][COLOR="green"]For more info look at the Video tutorial section of this post[/COLOR][/U]
[LIST=1]
[*]Download ROM you want to flash and extract it to the one folder
[*]Download the attachment and extract the binaries to /usr/local/bin/
[*]Install the prerequisites: sudo apt-get install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev
[*]Open terminal window and type: sudo heimdall-frontend
[*]Change tab to Flash and load the pit file
[*]Click on Add to add partition to flash and corresponding files to them [COLOR="Red"](!! MBR,GPT partition is use to repartition our device, so you have to put a .pit.md5 file to it when you want repartition your device !!)[/COLOR]
[*]Put your phone into Download mode and connect it to the PC using USB cable
[*]In Heimdall Frontend click Start and wait
[*]Enjoy :)
[/LIST]

Pit extraction:

[LIST=1]
[*]In Heimdall frontend click Utilities tab
[*]Click under Print Pit - Device
[*]Click under Download pit - Save as
[*]Choose the name and destination
[*]Click Download and wait
[*]Enjoy ;)
[/LIST]

Video tutorial

TUTORIAL

Mirror:

Google drive
[Remix OS for PC] lucasdeeiroz:
Hello, I'm facing a big problem on latest update for Remix OS.

My Remis OS 2.0 HDD installation was ok, I was running it normally. When 3.0 update came, I was sure that it would work ok too. But it didn't.

-The first problem appeared at USB writing speed test. The result was something like "Can't test writing speed. System may not boot". This screen is skipped.

-Then, system start to format data.img in Android-x86 logo screen. Well, another error appears: "can't format data". This screen is skipped as well.

-Finally, system boot start, at Remix OS logo screen. It does try to do something, my HD tries to load the system, it seems. But this process never finishes. This screen never is skipped, system does not reboot, no errors appears in the screen.

Again, Remix OS 2.0 works normally.

Here is my Notebook specs:

Samsung ATIV Book 2

Intel Core i5

Inter HD Graphics 4400

NVIDIA GeForce 710M

HDD installation
[XDA Assist] XDA Visitor:
i know the basic procedure to unlock the bootloader but i think i screwed up big time. i was running resurrection remix's marshmallow rom and then i downgraded to official kitkat 4.4.4 but it had a blur line on screen going down again & again so i updated it to lollipop via ota. as soon as the update finished installing, instead of restarting, my phone switched off and it never started again. i had hard bricked my phone. i somehow managed to get it to bootloader but now it shows that my device is locked. i tried to unlock it by the procedure mentioned on motorola's website but when i tried to get oem lock data by command $ fastboot oem get_unlock_data, it says "could not get unlock data". please help me to fix this.

device: moto g xt1033 (2013)
[XDA Assist] Trafalgar Square:
Hello and thank you for using XDA Assist,

please create an account and ask in our Android Q&A section:

Moto G Q&A, Help & Troubleshooting

The experts there will be able to help you.

Best regards & good luck

Trafalgar Square

XDA Assist
[Wing, P4350 General] duprade:
Hey guys, Saw this over in the general forum and I thought it was pretty funny so I wanted to share it with all Wing users.

LINK:

Is it me or the Wing seems kinda gay?