[GUIDE] MODIFY REMIX 3.0.101 to 3.0.104 FOR SYSTEM READ-WRITE - Remix OS for PC

UPDATED 2016-08-12 I HIGHLY RECOMMEND A BETTER METHOD FOUND HERE:
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
FEWER CHANCES OF ERROR :laugh:
UPDATED 2016-08-09 TO INCLUDE 32 BIT DIRECTIONS MANY THANKS TO @ireMaN FOR INPUT
THIS IS MODIFIED NOW FOR BOTH 32 AND 64 BIT!
THIS IS ALSO ONLY FOR HDD INSTALLATIONS
Fellow Remixers:
As many have found out, version 3 of RemixOS doesn't allow changes to the system. This is because instead of a system.img it now uses a system.sfs. For most of us there is no advantage to this, and it makes it impossible to perform even simple mods to the build.prop.
So we must convert that pesky system.sfs to a system.img and substitute a modified initrd.img.
There has been so much interest in this that I have tried to write a guide. I hope it is accurate, but I encourage feedback to improve it. EDIT 2016-08-03: WORKS FOR 3.0.102 ALSO
EDIT: 2016-08-09 WORKS FOR 3.0.103 ALSO
Here it goes:
ALL OF THIS IS DONE FROM WINDOWS. From File Explorer, navigate to your partition with RemixOS folder. Note the drive letter; mine was d:
1 Open the RemixOS folder on that drive; you should see a system.sfs file.
2 First you need to download the correct (32 or 64) modified initrd.img from here:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkTm5raUZRZXl4NkE
3 Use File Explorer to navigate to the Downloads folder; you should see a file named initrd_(32 or 64)_rw_3.0.101.img
4 Copy that file into the RemixOS folder on the drive where you installed Remix.
5 Open the RemixOS folder; you should see both the original initrd.img and the new initrd_(32 or 64)_rw_3.0.101.img
6 Rename the initrd.img to oldinitrd.img to save it in case you need it
7 Rename the initrd_(32 or 64)_rw_3.0.101.img to initrd.img
8 Next convert that system.sfs file to a system.img file
9 Using your web browser, download and install RMXTools from http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
10 Then in File Explorer, navigate to Downloads folder and extract the RMXTools zip. (EDIT: You may need 7zip to extract it)
11 Then navigate to the newly created RMXTools folder and navigate to the bin64 folder
12 Open a command window by using shift&right mouse button and selecting the Open command window here
13 Assuming that your RemixOS folder is on drive c: type unsquashfs.exe -d c:\temp c:\RemixOS\system.sfs
If your drive letter is e: for example, you would substitute e: for c: (EDIT: Do not change the -d as it is part of the command)
You should see it writing blocks for a few seconds
This should create a new system.img file on drive d: in folder temp
14 Now you need to navigate again to the drive with the RemixOS folder. You should see your newly created system.img in the temp folder
15 Copy it into the RemixOS folder
16 Now open the RemixOS folder; you should see your new system.img alongside the original system.sfs.
17 Rename the system.sfs to oldsystem.sfs to keep it in case you need it again
OK now time to reboot into Remix
You should now have writable system
Hope this helps
If it works for you please hit the "thanks" and if you're REALLY happy then I can always use coffee money
NOTE: TO TAKE OTA UPDATE YOU NEED TO DO THE Following FROM WINDOWS:
A In File Explorer, navigate to the RemixOS folder
B Find and rename the initrd.img to initrd_(32 or 64)_rw_3.0.101.img depending on your version
C Find and delete system.img
D Rename oldsystem.sfs to system.sfs
E Reboot ti RemixOS and download the update and select the Reboot option.
F After the OTA is installed and you are at the desktop you need to repeat steps 6 through 17 above
Any suggestions to make this easier please let me know. Please PM me and I will answer your questions.

---

Thanks a lot... Will try and reply you soon.... But I'm sure it works
Sent from my S II using XDA Labs

---

changing orientation
Thanks a lot. Not only you are a very helpful person , you have lots of patience. Thanks for all your inputs and guidance. I checked using CPU-Z and find all sensors are working including rotation sensor. I alos see that the new build.prop has the line ro.remixos.box is set to flase. But still my surface pro does not auto rotate to portrait mode. I am also not able to force it into portrait mode. Can you help please?
Thanks
lollyjay said:
Fellow Remixers:
There has been so much interest in this that I have tried to write a guide. I hope it is accurate, but I encourage feedback to improve it.
Here it goes:
All of this is done from Windows. From File Explorer, navigate to your partition with RemixOS directory. Note the drive letter; mine was d:
Open the RemixOS folder on that drive; you should see a system.sfs file.
First you need to download a modified initrd.img from here:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkTm5raUZRZXl4NkE
Use File Explorer to navigate to the Downloads folder; you should see a file named initrd_rw_3.0.101.img
Copy that file into the RemixOS folder on the drive where you installed Remix.
Open the RemixOS folder; you should see both the original initrd.img and the new initrd_rw_3.0.101.img
Rename the initrd.img to oldinitrd.img to save it in case you need it
Rename the initrd_rw_3.0.101.img to initrd.img
Next convert that system.sfs file to a system.img file
Using your web browser, download and install RMXTools from http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
Then in File Explorer, navigate to Downloads folder and extract the RMXTools zip.
Then navigate to the newly created RMXTools folder and navigate to the bin64 folder
Open a command window by using shift&right mouse button and selecting the Open command window here
Assuming that your RemixOS folder is on drive d: type
unsquashfs.exe -d d:\temp d:\RemixOS\system.sfs
If your drive letter is e: for example, you would substitute e: for d:
You should see it writing blocks for a few seconds
This should create a new system.img file on drive d: in folder temp
Now you need to navigate again to the drive with the RemixOS folder. You should see your newly created system.img in the temp folder
Copy it into the RemixOS folder
Now open the RemixOS folder; you should see your new system.img alongside the original system.sfs.
Rename the system.sfs to oldsystem.sfs to keep it in case you need it again
Rename the initrd_rw_3.0.101.img to initrd.img
OK now time to reboot into Remix
You should now have writable system
Hope this helps
If it works for you please hit the "thanks" and if you're REALLY happy then I can always use coffee money
Any suggestions to make this easier please let me know.
Click to expand...
Click to collapse

---

Some Question
Any suggestions to make this easier please let me know.
Click to expand...
Click to collapse
how to mount HDD Partition like previous version? is there any trick to show it again?
Hope Anyone Here Can Help

---

rajnallan said:
Thanks a lot. Not only you are a very helpful person , you have lots of patience. Thanks for all your inputs and guidance. I checked using CPU-Z and find all sensors are working including rotation sensor. I alos see that the new build.prop has the line ro.remixos.box is set to flase. But still my surface pro does not auto rotate to portrait mode. I am also not able to force it into portrait mode. Can you help please?
Thanks
Click to expand...
Click to collapse
Thank you for the compliment. My knowledge does not extend to that area; perhaps @HypoTurtle can help?

---

asuduakali said:
Any suggestions to make this easier please let me know.
how to mount HDD Partition like previous version? is there any trick to show it again?
Hope Anyone Here Can Help
Click to expand...
Click to collapse
I wish I knew...
Edit: I suspect that they locked access to speed up the system by disabling disk i/o

---

lollyjay said:
I wish I knew...
Edit: I suspect that they locked access to speed up the system by disabling disk i/o
Click to expand...
Click to collapse
I succeed to do it using stickmount after i copied these imgs .
just check usbstorage folder with file explorer ( i'm using ES)

---

lollyjay said:
Fellow Remixers:
There has been so much interest in this that I have tried to write a guide. I hope it is accurate, but I encourage feedback to improve it.
Here it goes:
All of this is done from Windows. From File Explorer, navigate to your partition with RemixOS directory. Note the drive letter; mine was d:
Open the RemixOS folder on that drive; you should see a system.sfs file.
First you need to download a modified initrd.img from here:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkTm5raUZRZXl4NkE
Use File Explorer to navigate to the Downloads folder; you should see a file named initrd_rw_3.0.101.img
Copy that file into the RemixOS folder on the drive where you installed Remix.
Open the RemixOS folder; you should see both the original initrd.img and the new initrd_rw_3.0.101.img
Rename the initrd.img to oldinitrd.img to save it in case you need it
Rename the initrd_rw_3.0.101.img to initrd.img
Next convert that system.sfs file to a system.img file
Using your web browser, download and install RMXTools from http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
Then in File Explorer, navigate to Downloads folder and extract the RMXTools zip.
Then navigate to the newly created RMXTools folder and navigate to the bin64 folder
Open a command window by using shift&right mouse button and selecting the Open command window here
Assuming that your RemixOS folder is on drive d: type
unsquashfs.exe -d d:\temp d:\RemixOS\system.sfs
If your drive letter is e: for example, you would substitute e: for d:
You should see it writing blocks for a few seconds
This should create a new system.img file on drive d: in folder temp
Now you need to navigate again to the drive with the RemixOS folder. You should see your newly created system.img in the temp folder
Copy it into the RemixOS folder
Now open the RemixOS folder; you should see your new system.img alongside the original system.sfs.
Rename the system.sfs to oldsystem.sfs to keep it in case you need it again
Rename the initrd_rw_3.0.101.img to initrd.img
OK now time to reboot into Remix
You should now have writable system
Hope this helps
If it works for you please hit the "thanks" and if you're REALLY happy then I can always use coffee money
Any suggestions to make this easier please let me know.
Click to expand...
Click to collapse
Tried it now. Worked like a charm. killing the thanks button

---

Everything working fine... I'd clean install replacing both files, thank you very much, and also i installed SuperSU for better root magement and besides.. with this one StickMount works perfectly...

---

doing this Adaway can work?

---

dark8899 said:
doing this Adaway can work?
Click to expand...
Click to collapse
Yes, of course

---

asuduakali said:
how to mount HDD Partition like previous version? is there any trick to show it again?
Hope Anyone Here Can Help
Click to expand...
Click to collapse
Try changing ro.remixos.scan_all_parts=false
rajnallan said:
Thanks a lot. Not only you are a very helpful person , you have lots of patience. Thanks for all your inputs and guidance. I checked using CPU-Z and find all sensors are working including rotation sensor. I alos see that the new build.prop has the line ro.remixos.box is set to flase. But still my surface pro does not auto rotate to portrait mode. I am also not able to force it into portrait mode. Can you help please?
Thanks
Click to expand...
Click to collapse
Haven't found what's forcing landscape; yet... maybe see what changing ro.remixos.has_adjust_display=false does; but it's probably nothing
xSilverLight said:
Everything working fine... I'd clean install replacing both files, thank you very much, and also i installed SuperSU for better root magement and besides.. with this one StickMount works perfectly...
Click to expand...
Click to collapse
Yea, stickmount seems to need the [updated] superSU su binary; so either system.img rw or systemless root would do [also the build.prop edit mentioned above might be an alternative to stickmount but editing build.prop needs system rw anyway].
Addendum; if anyone is using my 32bit su.img; you need to make a /su/xbin_bind folder and reboot before SuperSU will update the binary

---

HypoTurtle said:
Yea, stickmount seems to need the [updated] superSU su binary; so either system.img rw or systemless root would do [also the build.prop edit mentioned above might be an alternative to stickmount but editing build.prop needs system rw anyway].
Addendum; if anyone is using my 32bit su.img; you need to make a /su/xbin_bind folder and reboot before SuperSU will update the binary
Click to expand...
Click to collapse
Exactly, also I'll try that you mention and thanks for the info..
And also.. thanks for all your contributions

---

HypoTurtle said:
Try changing ro.remixos.scan_all_parts=false
Haven't found what's forcing landscape; yet... maybe see what changing ro.remixos.has_adjust_display=false does; but it's probably nothing
IT is already showing ro.remixos.has_adjust_display =false
The latest remix OS based on Marshmallow carries all these changes.
Click to expand...
Click to collapse

---

Thanks. Now I can use stick mount and access my hdd.

---

hhaiwzz said:
Thanks. Now I can use stick mount and access my hdd.
Click to expand...
Click to collapse
You're very welcome my pleasure

---

I'm at a loss as to how to get this working on a USB install on my system. Are people using hard drive installs or USB flash drive ones? I'm using a 64gb Sandisk Extreme flash drive.
1st off - using the Windows tool that comes in the installer from Jide's website (downloaded file I have is Remix_OS_for_PC_Android_M_64bit_B2016072603.zip ) to "install" RemixOS onto the flash drive works flawlessly but after that I'm unable to see any other volumes other than one called REMIX_OS which is not a system volume. I've formatted the flash drive 4 times already and redid the installation each time. Each time the install is perfectly bootable but in terms of being able to boot into windows and brows the RemixOS folder to modify system files there is no change, I'm unable to see all volumes on the flash drive. I only see one volume while in windows and that one appears to be an SD CARD (It's called REMIX_OS and only has an Android and Lost folder in it) rather than the system volume for Android.
If I insert the flash drive into my Macbook I'm able to see two volumes, the volume called REMIX_OS I referred to earlier and another volume called REMIXOSSYS which does have the system files in it (with the initrd.img and system.sfs that need to be replaced) . .
So after using the RMXTools on my Windows machine to create a system.img file (which ends up ballooning to 2.6gb, is that the right size?) and downloading the requisite initrd_rw_3.0.101.img and renaming both original files on the REMIXOSSYS volume (using my Mac) and copying the new ones onto the flash drive volume I'm able to boot into RemixOS on my PC normally.
Everything works fine until I actually try to edit build prop as a test at which point I'm unable to. The system itself operates just fine otherwise but system still isn't writeable.
I'm not quite sure why others are easily able to do everything they need to do on their PC's using windows explorer to modify the system files and I'm not. I tried it on both my home and work PCs and the result is the same. Nonetheless I'm thinking that since all that is supposed to be required to make system writeable is to replace the initrd.img and system.sfs with the modified initrd.img and a system.img file then it really shouldn't matter if I do it using a Mac or a PC . . i'm confused at this point lol.
Any thoughts?

---

rajnallan said:
HypoTurtle said:
Try changing ro.remixos.scan_all_parts=false
Haven't found what's forcing landscape; yet... maybe see what changing ro.remixos.has_adjust_display=false does; but it's probably nothing
IT is already showing ro.remixos.has_adjust_display =false
The latest remix OS based on Marshmallow carries all these changes.
Click to expand...
Click to collapse
Yea; I said change it. i.e. to true
Click to expand...
Click to collapse

---

muzzy996 said:
I'm at a loss as to how to get this working on a USB install on my system. Are people using hard drive installs or USB flash drive ones? I'm using a 64gb Sandisk Extreme flash drive.
1st off - using the Windows tool that comes in the installer from Jide's website (downloaded file I have is Remix_OS_for_PC_Android_M_64bit_B2016072603.zip ) to "install" RemixOS onto the flash drive works flawlessly but after that I'm unable to see any other volumes other than one called REMIX_OS which is not a system volume. I've formatted the flash drive 4 times already and redid the installation each time. Each time the install is perfectly bootable but in terms of being able to boot into windows and brows the RemixOS folder to modify system files there is no change, I'm unable to see all volumes on the flash drive. I only see one volume while in windows and that one appears to be an SD CARD (It's called REMIX_OS and only has an Android and Lost folder in it) rather than the system volume for Android.
If I insert the flash drive into my Macbook I'm able to see two volumes, the volume called REMIX_OS I referred to earlier and another volume called REMIXOSSYS which does have the system files in it (with the initrd.img and system.sfs that need to be replaced) . .
So after using the RMXTools on my Windows machine to create a system.img file (which ends up ballooning to 2.6gb, is that the right size?) and downloading the requisite initrd_rw_3.0.101.img and renaming both original files on the REMIXOSSYS volume (using my Mac) and copying the new ones onto the flash drive volume I'm able to boot into RemixOS on my PC normally.
Everything works fine until I actually try to edit build prop as a test at which point I'm unable to. The system itself operates just fine otherwise but system still isn't writeable.
I'm not quite sure why others are easily able to do everything they need to do on their PC's using windows explorer to modify the system files and I'm not. I tried it on both my home and work PCs and the result is the same. Nonetheless I'm thinking that since all that is supposed to be required to make system writeable is to replace the initrd.img and system.sfs with the modified initrd.img and a system.img file then it really shouldn't matter if I do it using a Mac or a PC . . i'm confused at this point lol.
Any thoughts?
Click to expand...
Click to collapse
Method works only for hdd installations afaik

---

wow thanks for this, now since we have an open system, can we install xposed framework?