yashsingh1/xdaforums huggingface dataset:
[P8lite Q&A, Help & Troubleshooting] amageek:
If you have TWRP or CWM Recovery, do this

Since you're on bootloop, shutdown the device (press power key for few seconds until it completely shuts down). Then, press the following keys at the same time: Power + Volume Up for few seconds then as it vibrates leave the Power key but keep on pressing the Volume Up key. You will get to recovery mode and backup your data.

If no such recoveries then do this

Shutdown the device completely. Copy your current version or any other version (will be either UPDATE.ZIP or UPDATE.APP) in a folder , name that dload and paste it in your sdcard.. Now insert the sdcard into the phone, and restart it.. For few times, it may get in bootloop , if it gets, restart it again.. after few times, it will try to update the system itself and will find that dload folder in your sdcard and upgrade it..

That's it
[P8lite Q&A, Help & Troubleshooting] soony20008:
Thanks again man

But I'm not gonna lose my data such as photos,videos and contacts?

Because all my data in the internal storage
[P8lite Q&A, Help & Troubleshooting] PCSE:
You shouldn't lose your data since it is just like a firmware Update without any wipes. But I'm not gonna guarantee anything since idk what you did with your device.
[P8lite Q&A, Help & Troubleshooting] soony20008:
Thanks for everything guys.

I will try it and give you feedback
[Remix OS for PC] electrikjesus:
HELPFUL TOOLS & GUIDES

This section will be updated from time to time to include tools and links to things i may find helpful in this case.

Custom Android x86 - Grub theme

Here is a link to to my custom UEFI grub I use on my Surface Pro 3. The theme was adapted from a Surface grub theme I found online. I will say thanks here for whomever did that.

This can also serve as a guide to multibooting on UEFI based machines. Feel free to share it, just give me credit if you do ;)

https://drive.google.com/open?id=0B2hjuvxuncgYNmxWcHVSVXNVb2M

[IMG="Grub Theme"]http://dl-1.va.us.xda-developers.com/3/8/4/6/5/0/5/IMG_20160818_103047.jpg?key=rgJxMJrdRZCt9jITei519Q&ts=1471532365[/IMG]

[GUIDE] Installing android x86 without CD or USB

http://xdaforums.com/showthread.php?t=2414362

[WinApp][v2.4-Beta][+RemixOS] Android-x86 Installer UEFI Version

http://xdaforums.com/android/software/winapp-android-x86-installer-uefi-t3222483

[GUIDE] [ALTERNATIVE] Dual boot RemixOS (beta) alongside Windows

http://xdaforums.com/remix/remix-os/dual-boot-remixos-windows-usb-drive-t3324359

How to install Remix OS alongside Ubuntu (Dual Boot)

http://xdaforums.com/remix/remix-os/how-to-install-remix-os-alongside-t3352890

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

http://xdaforums.com/remix/remix-os/how-to-install-remix-os-to-hdd-using-t3300120
[Remix OS for PC] kretex:
REMOUT_RW=1 will extract system.sfs to .img its 2gb more, is it save to delete the system.sfs after .img created??
[Remix OS for PC] electrikjesus:
In my case, I did not. If you have the .ISO still, you could always delete it and extract it later for OTA.
[Remix OS for PC] Orion116:
This works great! Thanks for sharing it.
[Remix OS for PC] kretex:
Delete system.sfs after system_dev.img created will make remix stuck on boot :) so the result is do not delete the system.sfs :D
[Remix OS for PC] Vioner:
Thank you [MENTION=928479]electrikjesus[/MENTION] for this method. It's definitely the best out there as it doesn't hinder OTA updates and requires nothing but <3GB of additional storage and small change in grub.cfg file.

Other methods require changing initrd.img with system r/w properties and even if someone would want OTA, he'd have to keep a copy of system.img/.sfs file for swapping.

Best method for now.
[Remix OS for PC] lollyjay:
Works like a charm for legacy. I highly recommend this and it's far simpler than mine.

Thanks

Was not able to follow the UEFI though. mountvol X: /S returned "The parameter is incorrect." That's because you only need to do that with UEFI. If you change your instructions to say that first method is for ANY legacy BIOS installation (both 32 and 64)

---------- Post added 13th August 2016 at 12:11 AM ---------- Previous post was 12th August 2016 at 11:45 PM ----------

Suggested changes to clarify the OP:

For all RemixOS legacy installs:

You will want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, travel to C:\RemixOS (where the installer should have installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add the REMOUNT_RW=1 entry like you see below:

For RemixOS x64 UEFI installs only:

You will also want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, hit the start menu, and type in CMD, and then right click, and open as administrator. It should look like the window below:
[Remix OS for PC] Vioner:
Mounting EFI/System partition

[MENTION=4762414]lollyjay[/MENTION] Remix OS can be installed on 32bit UEFI as well - I successfully installed it on my Asus T100TA using the official tool and to my surprise... it works. For releases 2.0X I used Android-x86 installer, but now even official version works.

Anyway, I didn't have any problems with mounting the system (efi) partition in windows, but I've been doing this many times before and using a bit different way:

Run CMD.exe as Admin <- IMPORTANT and enter following commands:

taskkill /im explorer.exe /f

This will kill explorer.exe process - don't be surprised :D It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.

mountvol X: /s

This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.

Write:

explorer

This will run explorer as Administrator and will allow you to browse the mounted system partition.

The above may not work for all devices, as some handle UEFI differently.
[Remix OS for PC] lollyjay:
Yeah def doesn't work for my Dell.
[Remix OS for PC] Vioner:
[MENTION=4762414]lollyjay[/MENTION] which DELL do you have (exact model) and which operating system?
[Remix OS for PC] electrikjesus:
Thanks for the suggestion. I will update the OP to better clarify.

I will also update the OP to include your suggestions about explorer as well :)

Thanks to both of you!
[Remix OS for PC] Cyborg Ninja:
Ubuntu 14.04+

Hi guys, for those who use Ubuntu and want the RW feature, open Grub customizer, if you do not have:

sudo apt-add-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer

Then, highlight your RemixOS and click on the little pencil to edit.

Then insert REMOUNT_RW=1 here after the "CMDLINE" and it will look something like this:

insmod part_gpt
search --file --no-floppy --set=root /RemixOS/system.sfs
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE REMOUNT_RW=1
initrd /RemixOS/initrd.img

Save, reboot and boot up your RemixOS and it will do the rest, have to wait a couple minutes and you are all set. This will even let you remove the preinstalled superuser it came with and install Chainfire's SuperSU in its place.
[Remix OS for PC] GameOver69:
USB Boot

How would i be able to apply this to RemixOS running off a USB stick/drive?

Thanks
[Remix OS for PC] superspin:
Great work, thank you for sharing.
[Remix OS for PC] Vioner:
Accessing EFI / ESP / System partition on Windows 10

Is your Dell using Windows 10?

I just learned that Windows 10 has EFI partition sometimes already mounted under Z: letter, but it's hidden.

A very quick and easy way to access ESP (EFI System Partition) in Windows 10: (no command line use needed!)

Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.

Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (Z:) or type in "z:" in the filepath bar"

Now go to boot/grub/grub.cfg and edit it accordingly with Notepad++ or other editor

Save the file and your're ready to go

If this still doesn't work - try this:

[MENTION=4762414]lollyjay[/MENTION] and others, let me know if it works for you - Windows 10 Home here.

[MENTION=928479]electrikjesus[/MENTION] c'mon update the OP with our input! :D :)
[Remix OS for PC] lollyjay:
Yep that's exactly what I needed to do. Thanks
[Remix OS for PC] electrikjesus:
Updated ;)
[Remix OS for PC] lollyjay:
Hey I think I found a method that will work for all Windows 10 UEFI installations. I have tried it on three different laptops, with the only thing same is UEFI and Windows 10:

1 Right click on the Window at left end of the taskbar

2 Select "Command Prompt (Admin)"

3 At the command prompt (assuming you don't have a z drive), type: mountvol z: /s

4 At the command prompt, type: notepad.exe

5 When Notepad window opens, select File/Open

6 In lower right of the notepad open window, set to "All Files (*.*)

7 Navigate on the left column to the z drive and click on it

8 Select boot and then grub then open grub.cfg

9 Navigate to the space between " logo.showlogo=1 DATA= "

10 Add: REMOUNT_RW=1 so it is " logo.showlogo=1 REMOUNT_RW=1 DATA= "

11 Select File/Save to save your modified grub.cfg

12 Select File/Exit

13 At the command prompt, type: mountvol z: /d

14 Close the command window

15 Reboot to RemixOS - you should see it writing the new system image file

Hope this helps some who are not experts
[Remix OS for PC] electrikjesus:
Yeah, I guess any notepad app will do. I didn't even think about using the built one app cause I'm so used to my fancy notepad :)
[Remix OS for PC] Vioner:
Good guide overall, but :D

13. should be

mountvol z: /d

/d is for dismounting /s is for mounting system partiton. Also this point is not necessary, because if you reboot, the partition will be unmounted anyway.
[Remix OS for PC] lollyjay:
Ho Li Crap!

Yes I only put that in in case the person doesn't reboot. Thanks for the correction I changed it.
[Remix OS for PC] ranaxda200:
Hey guys, I'm new to RemixOS. I tried temp system.sfs command method to extract system with RMXtool but failed to copy to

/system any file. So I wanna try this. I've legacy boot win7 64bit, g41m combo mb, core2duo processor so installed x86 Remix OS. BTW I'm unable to find any menu.lst file in boot/grub folder.

How to enable this method in my system? Please help me.

Here is the RemixOS root folder.
[Remix OS for PC] Vioner:
[MENTION=5293792]ranaxda200[/MENTION] in this thread we tIell you how to mount ESP - EFI System Partition, not the android system partition.

Anyway, I don't really know what you are asking, but it's unrelated to this guide then you should ask it elsewhere.
[Remix OS for PC] ranaxda200:
Sorry for wrong section So how do I enable the RemixOS system r/w mount to copy to /system , do you have any idea? Already tried the RMXtool system.sfs command method to extract system and reroot SuperSu but still can't toggle r/w. Is there any other way?
[Remix OS for PC] Vioner:
This thread is a guide for mounting Remix OS /system partition as writable by applying REMOUNT_RW=1 to the grub.cfg/menu.lst file.

After doing that you will be able to remove built-in superuser app and replace it with Chainfire's SuperSU all within Remix OS - no need to extract system.sfs/iso and repack it after modification.

Remember though that REMOUNT_RW=1 works this way:

1. While booting, the REMOUNT_RW=1 parameter is picked up by the bootloader.

2. Remix OS bootloader will use system_dev.img (writable) instead of system.sfs/img.

If system_dev is.img does NOT exist, bootloader will create it from system.sfs - additional ~2.5GB storage.

3. System will be booted using system_dev.img

4. If you will want to use the OTA, all you'll should be required to do is to remove REMOUNT_RW=1 from grub or set it =0. I'm not sure though if it's necessary, because I haven't tested this yet.

Just use the guide from 1st post.
[Remix OS for PC] HypoTurtle:
No it's not this thread is about adding REMOUNT_RW=1 to grub. [Mounting esp just being what's needed if you did a UEFI harddrive install]

[MENTION=5293792]ranaxda200[/MENTION] your pics are a bit blurry; but that grub.cfg in the first pic is what you should edit.
[Remix OS for PC] ranaxda200:
But mine is legacy boot. Do I follow your guide to edit grub.cfg. BTW I can edit **grub.cfg** from windows with notepad editor, right?

---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------

Should I edit this part and add *REMOUNT_RW=1* in resident mode? right?
[Remix OS for PC] Vioner:
[MENTION=5293792]ranaxda200[/MENTION]

I guess the guide does not include all legacy boot matters - USB/HDD installation. But yes, you should edit the grub.cfg file if you don't have the menu.lst

Add the REMOUNT_RW=1 to resident mode right after logo.showlogo=1 or right before DATA=

Do have in mind that you will need additional ~2.5 GB of free space on the USB drive!
[Remix OS for PC] ranaxda200:
You said " while booting REMOUNT=1 Parameter is picked up" didn't get it? Booting as normal.

BTW still I can't copy or paste anything to /system and unable to toggle mount r/w. SuperSu enabled though.
[Remix OS for PC] Vioner:
I just explained how this parameter works - the bootloader picks it up - recognizes it and does it's job accordingly.

Did you apply the REMOUNT_RW=1 to both places?

You can also just find all files with the bootloader configuration - files that have the menuentries for remix, then apply REMOUNT_RW=1 to all of them. It won't brake anything.
[Remix OS for PC] ranaxda200:
You mean all the *grub*. CFG files with menuentries? BTW I find them all in 'boot' and 'efi>RemixOS' folder. Edited REMOUNT_RW=1 after logo.showlogo=1. Right?
[Remix OS for PC] Vioner:
"boot" folder only, "efi" doesn't apply for legacy boot devices. Can't you just test it youself instead of asking over and over? It won't brake anything. I have never installed on a USB that's why I'm not sure, but it won't hurt to add this REMOUNT-RW=1 to all bootloader configuration files...

Specially for you I'll install Remix to a USB drive just to make sure... Ugh... you annoy me :D
[Remix OS for PC] ranaxda200:
Hey sorry to annoy you and curse myself for being a noob, lol. But hey I installed RemixOS on my pc drive not USB.
[Remix OS for PC] Vioner:
[MENTION=5293792]ranaxda200[/MENTION] ok, then the fault is on both mine and yours side :D I've read what you wrote too quickly and missed some things (legacy/hdd). And it seems like the guide is written wrong - menu.lst does not apply for all installations. You need to modify /boot/grub/grub.cfg like below:
[Remix OS for PC] ranaxda200:
Deleted
[Remix OS for PC] Vioner:
Yes, sorry, I've just edited my post. You need to edit /boot/grub/grub.cfg file by adding "REMOUNT_RW=1" right before "DATA="

We just spammed the thread, damn.

[MENTION=928479]electrikjesus[/MENTION] please check if your guide is written the right way for legacy devices. Some people don't have the menu.lst file and they should edit /boot/grub/grub.cfg instead of it - you should include that in the guide.
[Remix OS for PC] lollyjay:
I feel your pain :crying:

Anyway would you be willing to make step by step instructions for taking an OTA?
[Remix OS for PC] HypoTurtle:
For the OTA you should be fine just deleting the system_dev.img before/after the OTA has applied.

i.e. you start with a system.sfs and a system_dev.img both on 104

201 OTA downloads; and on reboot system.sfs unpacks to system.img and OTA is applied to the system.img

The 201 system.img is then repacked to a system.sfs replacing the 104 system.sfs

Leaving you with a 201 system.sfs and a 104 system_dev.img as system.sfs isn't reunpacked due to the presence of the previous system_dev.img

tl;dr delete the system_dev.img so the updated system.sfs can unpack again.
[Remix OS for PC] lollyjay:
You and I know how to do it. I was referring to a noob-friendly 1 2 3 etc. Guess I can do it...
[Remix OS for PC] Cyborg Ninja:
Observations:

-OTA downloads and supposedly installs but nothing changes...stays at v.102

-I have found that removing/deactivating the "REMOUNT_RW=1" reinstalls all the bloatware I had removed

-Only way I have been able to update my Remix (with the RW=1) is by downloading the latest version and extracting the 4 files (system.sfs, initrd.img, kernel, ramdisk.img) deleting the old files, pasting the new ones into the Remix folder. This though causes Playstore to not work and seems like I have to reinstall Google Play services and things seem to flow again. All my apps and data seem to be fine.

-Maybe with Titanium backup you could reinstall all of your apps/data after a fresh install of the updated RemixOS with the RW=1 (have not tried this yet but a possible theory)

-All of this done in Ubuntu, maybe helpful for Windows users? :D
[Remix OS for PC] Vioner:
Well removing REMOUNT_RW=1 causes the boatloader to start R/O unedited system.sfs to load instead of the system_dev.img from which you removed the bloatware.
[Remix OS for PC] Cyborg Ninja:
So I should direct grub to load the system_dev.img instead of system.sfs?
[Remix OS for PC] Vioner:
Whenever you will want to update to a newer version, no matter if via OTA or manually, you'll lose all changes you made to the /system partition.

If you can't live with that then you'd have to:

1. download the updates manually or over OTA

2. check which files changed

3. copy the changed files to your system_dev.img.

That's the only thing I think that would work. I wouldn't recommend it though.

Modifying system image files and still wanting updates is contradictory.

OTA downloaded update could work for you because AFAIK it downloads only the "differences" and not the whole remix.iso. I haven't fiddled with it so I'm not sure.
[Remix OS for PC] Cyborg Ninja:
Silly me, I asked the same question as someone else in the first few posts......

No, the OTA did not work, it downloaded, rebooted, went through the process and when I entered, still showed "102" and not "104." I had to do it manually as in my 3rd observation by replacing those files. Not really a time consuming task though to update manually. I have not lost any changes to /system as long as I kept the "system_dev.img" file (just the google services issue). I could replace the system.sfs with the new one.
[Remix OS for PC] electrikjesus:
OK. I'm not going to quote you all for this, but I will address each and every one of your questions the best I can with as few answers as possible... Here we go:

1) I will be updating the OP with a revised "easy" (better defining the MBR based method and options) and "advanced" (for us multi-OS users) set of instructions. And on top of that, I will also include a guide for handling OTA with this method.

2) I might also add a "helpful tools & guides" section for the less advanced that want to learn more ;)

That should just about cover it. I'll work on the OTA section tonight, cause I see that many are confused as to what to do :) LOL
[Remix OS for PC] Vioner:
[MENTION=928479]electrikjesus[/MENTION] I've tried to solve [MENTION=5293792]ranaxda200[/MENTION] issue with him and so far the results are:

1. He installed Remix using unofficial method - the guide in OP should mention that it's for installations made with the official tools or somehow differentiate between different types of installations, because clearly this matters and sometimes causes confusion and people waste time.

2. He used EasyBCD to install .ISO image of Remix on his HDD. That created a menu entry allowing to boot Remix.

3. Then he copied the .iso contents to the specified HDD and booted Remix.

4. This way, it's not possible to configure bootloader properties, because menu.lst and grub.cfg files just won't work. We tried all possible combinations.

5. What worked was editing the menuentry in the bootloader when you can select between Resident and Guest mode - we just pressed TAB on resident, added REMOUNT_RW=1 before DATA= and it worked.

6. But that was just one time modification that couldn't be saved for next boot.

I guess EasyBCD during iso installation, made somekind of an image using the boot files - including grub.cfg. Maybe it embedded grub.cfg contents in the .mbr file or something else? I don't know what can be in an mbr file except master boot record :D. I have no idea, but I'm sure we couldn't manipulate the configuration in any way, but directly in the boot selection menu.

We will reinstall using other method later.

Sleep :D
[Remix OS for PC] electrikjesus:
Yeah, that will be part of the advanced guide. The trick is to unpack the .iso, edit both the menu.LST and grub.cfg files to include a second or third boot entry for RW. Then repack the .iso, and install as he did the first time ;)
[Remix OS for PC] Vioner:
Yes I told exactly that to [MENTION=5293792]ranaxda200[/MENTION] :)

Anyway, I think installing using that method pretty much sucks because you can't edit grub.cfg/menu.lst at any time u want - you'd have to reinstall.
[Remix OS for PC] HypoTurtle:
Wouldn't work in his case, the grub and menu.lst[/grub.cfg] are replaced by those from EasyBCD. [MENTION=4666322]Ventricle[/MENTION] - I guess they installed/used NeoGrub? In that case have a look at C:\NST to see if there is a menu.lst there. But also isn't there a way to modify the boot entry within EasyBCD?

[MENTION=928479]electrikjesus[/MENTION] - for the guide you can circumvent most of the stuff on #1 by just creating a new fat16/32 partition and using that as a second ESP/EFI and I'm not sure how well spread it is [you'd need to check via something like minitool] but there is typically a 16MB unformatted partition after the ESP that can be formatted to fat16.
[Remix OS for PC] Vioner:
[MENTION=4056517]HypoTurtle[/MENTION] as I said we tried all possible combinations. No menu.lst file on the whole PC, we indexed all files and we didn't find it. But anyway, we made the menu.lst and grub.cfg files and they wouldn't work. Like I said, the boot configuration is built-in to the boot image when ISO is installed from easybcd.

I am 99% sure that [MENTION=928479]electrikjesus[/MENTION] method would work for easybcd.
[Remix OS for PC] electrikjesus:
I'm not getting the time I was looking to get tonight. So please be patient and I will update the OP as soon as possible
[Remix OS for PC] ranaxda200:
One thing to mention [MENTION=4666322]Ventricle[/MENTION] that REMOUNT_RW=1 was added before SRC (not before DATA). So far it's doing well. Today I'll reinstall RemixOS using official installer though I'm skeptical with my system to work. ;)
[Remix OS for PC] Vioner:
[MENTION=5293792]ranaxda200[/MENTION] it doesn't matter. I'll help you with adjusting the official installation to work for your PC.
[Remix OS for PC] electrikjesus:
I have updated the OP with a bunch more informational goodies :) let me know if I should add or re-word anything please. I want this to be as easy as possible for all
[Remix OS for PC] Cyborg Ninja:
Looks awesome. That tutorial for Ubuntu is tedious haha, my remix shares space with Ubuntu. Much much easier for me.
[Remix OS for PC] DarkAM:
Above quotes is just to mention you.

I follow the instruction for legacy and it's all have been done but on boot after it's finish extract the system-dev. It's booting and show remixos logo.... And that's it. I'm stuck at remixos logo , help please

Update

____&&&&

Nvm, i solve the problem myself
[Remix OS for PC] Vioner:
[MENTION=5532339]DarkAM[/MENTION] why not share the solution...?
[Remix OS for PC] bg260:
Thank you to all who contributed. This is by far the most accurate, informative and down to earth collection I have seen thus far, and there are many:(

I just have to adapt this to PhoenixOS and wait for the donations to start pouring in:eek::laugh:
[Remix OS for PC] HypoTurtle:
PhoenixOS isn't using lz4 last I checked; so you can pull the system.img with 7zip
[Remix OS for PC] bg260:
I just mount it with furius as root and copy it out.