Systemless-root for RemixOS [64bit] - Remix OS for PC

Systemless-root for RemixOS
64bit 2.0.205
This comes in two parts.
1. A modified ramdisk.img
2. A su.img file that needs to be copied to /data/su.img
In order to copy the su.img into position, use ALT&F1 to cp it into position or open/mount data.img using cygwin/Linux
Within su.img there are files that can be modified as if they are system files.
If you want to modify another system file; either copy it into /su/vendor or add the path to /su/systemfiles.txt
Within /su/su.d there are a couple of scripts that are run at boot; feel free to remove/modify.
su.d scripts
Scripts described here
Feel free to post what modification you need root to do; and if possible with systemless-root I'll add it to su.img as standard.
Optional
Sticking to the above keeps system.img as OTA-updatable; replacing the ramdisk with the original will let the OTA apply
If you want read-write access to /system and break OTA - you can use the modified initrd.img
Download folder
64bit 2.0.205
32bit already has system root without modifying system - but doesn't have the benefit of altering system files.
If there is a need I will try and create a 32bit version
SU credit goes to Chainfire

---

HypoTurtle said:
Systemless-root for RemixOS
64bit 2.0.205
This comes in two parts.
1. A modified ramdisk.img
2. A su.img file that needs to be copied to /data/su.img
In order to copy the su.img into position, use ALT&F1 to cp it into position or open/mount data.img using cygwin/Linux
Within su.img there are files that can be modified as if they are system files.
If you want to modify another system file; either copy it into /su/vendor or add the path to /su/systemfiles.txt
Within /su/su.d there are a couple of scripts that are run at boot; feel free to remove/modify.
su.d scripts
Scripts described here
Feel free to post what modification you need root to do; and if possible with systemless-root I'll add it to su.img as standard.
Optional
Sticking to the above keeps system.img as OTA-updatable; replacing the ramdisk with the original will let the OTA apply
If you want read-write access to /system and break OTA - you can use the modified initrd.img
Download folder
64bit 2.0.205
32bit already has system root without modifying system - but doesn't have the benefit of altering system files.
If there is a need I will try and create a 32bit version
SU credit goes to Chainfire
Click to expand...
Click to collapse
hi! how do i do this on windows? i can't actually access /data when it's installed in a folder on c: as dualboot

---

bombaglad said:
hi! how do i do this on windows? i can't actually access /data when it's installed in a folder on c: as dualboot
Click to expand...
Click to collapse
Easiest way is via ALT&F1.
1. boot into RemixOS,
2. download su.img
3. press ALT&F1
4. type cp /data/media/0/Download/su.img /data/su.img
5. reboot
When the ramdisk.img is switched you will have root available for apps.

---

Many thanks for your efforts. I have access to dozens of Lenovo ThinkPad laptops. I can experiment with your method.
Sent from my LENOVO 33476WU using XDA Labs

---

I can report success on a Lenovo ThinkPad Twist.
First followed your instructions; then manually activated Google Play Services; disabled com.jide.apppolicy; disabled com.jide.filelauncher to use custom launcher.
I'm very impressed. You could make an app to do everything both from Windows side and from Remix side. :laugh:
Sent from my Nexus 7 using XDA Labs

---

lollyjay said:
I can report success on a Lenovo ThinkPad Twist.
First followed your instructions; then manually activated Google Play Services; disabled com.jide.apppolicy; disabled com.jide.filelauncher to use custom launcher.
I'm very impressed. You could make an app to do everything both from Windows side and from Remix side. :laugh:
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
I'll add those as a script in a future update, (custom launcher; gapps).
Not sure on a Windows app/script - how it would work is from scratch (i.e. no data.img).
1. create a small data.img file (50MB)
2. open/extract it via cygwin binaries (ie RMXTools)
3. copy in su.img
4. close data.img
5. resize data.img to desired size
From within Remix without root only access to /data is via ALT&F1 so not really possible any other way (except using a rooted system.img; which kinda defeats the point).
What i do want to do however is have the ramdisk.img auto-switch back to stock if there is an OTA to apply.
Thinking out loud if someone can think of a better procedure:
Default way.1. OTA downloaded to /sdcard/autoupdater/incremental_remix_x86_*.zip
2. /sdcard/autoupdater/incremental_remix_x86_* copied to /sdcard/autoupdater/otapackage.zip
3. System reboots
4. Initrd.img/x86update locates the otapackage.zip; and applies the OTA
5. Otapackage.zip removed​With altered ramdisk the above happens except the OTA quietly fails.
Proposed solution1. Have a copy of ramdisk.img at a known location (within su.img [/su] if need be)
2. On boot check the /sdcard/autoupdater/incremental*.zip files for one that is looking for the SHA1 of the stock ramdisk you have saved
3. Copy ramdisk.img into correct location (combination of find -path ... and cat /proc/cmdline to find it) - keeping a copy of the modified one.
NB This requires the partition you are booting from to be mounted (I'm not sure if the su.img in OP has a script that unmounts all HDD partitions)
4. Copy the located /sdcard/autoupdater/incremental_remix_x86_* to /sdcard/autoupdater/otapackage.zip
5. Reboot
6. Ramdisk.img switch back to the modified one would need to be manually switched again - to get root​

---

Well I just downloaded the .205 from Jide.com about 1 hour ago. It's now the official beta download. Systemless root worked again.

---

A humble request
I am testing an experimental build for Jide devs. Would you be able to send me a rooted ramdisk.img based on this one?

---

lollyjay said:
I am testing an experimental build for Jide devs. Would you be able to send me a rooted ramdisk.img based on this one?
Click to expand...
Click to collapse
That is identical to the cn one made before (just an updated build date - selinux_version). I'll attach the two here anyway.
Can you post your grub.cfg for that build; I noticed a few more arguments in a grub file in the 402 OTA that I no longer have.
For anyone else reading; the attached are for use with the su.img in the OP

---

HypoTurtle said:
That is identical to the cn one made before (just an updated build date - selinux_version). I'll attach the two here anyway.
Can you post your grub.cfg for that build; I noticed a few more arguments in a grub file in the 402 OTA that I no longer have.
Anyone else; the attached are for use with the su.img in the OP
Click to expand...
Click to collapse
Thanks again. Here is the grub. cfg:
set timeout=30
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Windows' {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
menuentry 'Remix OS' --class android-x86 {
insmod /efi/RemixOS/ntfs64.mod
insmod /efi/RemixOS/exfat64.mod
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_cn_x86_64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}
---------- Post added at 01:52 AM ---------- Previous post was at 01:34 AM ----------
Will the original su.img still work?

---

lollyjay said:
Thanks again. Here is the gru. cfg:
set timeout=30
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Windows' {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
menuentry 'Remix OS' --class android-x86 {
insmod /efi/RemixOS/ntfs64.mod
insmod /efi/RemixOS/exfat64.mod
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_cn_x86_64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}
---------- Post added at 01:52 AM ---------- Previous post was at 01:34 AM ----------
Will the original su.img still work?
Click to expand...
Click to collapse
Yea, haven't touched su.img since the original; it'll work fine and the su binary will update fine with SuperSU; so think I'll leave it as is; unless there's a bunch of scripts/tweaks that I think could do with being dumped in there...
[I think it's SERIAL=random logo.showlogo=1 that the OTA tried to add; there might've been something else too]
Edit. @lollyjay in regards to your wifi issue - blacklisting b43 and bcma modules should work as a workaround at least until Jide get the auto-modprobe working properly.
[/su/vendor/etc/modules.blacklist]
Code:
blacklist evbug
blacklist b43
blacklist bcma

---

HypoTurtle said:
Yea, haven't touched su.img since the original; it'll work fine and the su binary will update fine with SuperSU; so think I'll leave it as is; unless there's a bunch of scripts/tweaks that I think could do with being dumped in there...
[I think it's SERIAL=random logo.showlogo=1 that the OTA tried to add; there might've been something else too]
Click to expand...
Click to collapse
Again thanks. Since I have the Chinese version the - cn ramdisk.img worked fine.
Sent from my on Z00A using XDA Labs

---

lollyjay said:
Again thanks. Since I have the Chinese version the - cn ramdisk.img worked fine.
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
The other one should work (on cn system) with androidboot.hardware=remix_x86_64; but I haven't a clue if there is a difference system-wise between the two versions (perhaps just cn version + languages packs = Universal ??)

---

Since thermald is now used. I disabled Intel_pstates driver(seems to be broken for haswell ult) to use acpi.
Change the governor to conservative using su.d script.
System idles @ 759 MHz as opposed to 1600 mhz when running Intel_pstates with turbo disabled

---

@HypoTurtle thanks for doing this
Could you please make Remix 32bit version and a separate version for PhoenixOS?
Wysłane z mojego Nexus 4 przy użyciu Tapatalka

---

Ventricle said:
@HypoTurtle thanks for doing this
Could you please make Remix 32bit version and a separate version for PhoenixOS?
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
Click to expand...
Click to collapse
Can you attach a copy of the original ramdisk.img for those.
I have a version for Phoenix done; just not sure if it's for the latest version.
Maromi said:
Since thermald is now used. I disabled Intel_pstates driver(seems to be broken for haswell ult) to use acpi.
Change the governor to conservative using su.d script.
System idles @ 759 MHz as opposed to 1600 mhz when running Intel_pstates with turbo disabled
Click to expand...
Click to collapse
disabling turbo works for me on core M; I'll see if I can emulate what you did anyway.

---

Any update for v.2.0.402?? [emoji4]

---

kretex said:
Any update for v.2.0.402?? [emoji4]
Click to expand...
Click to collapse
#9 for the ramdisk
I'll update OP once I get the 32bit ones done.
Is the read/write [break OTA] initrd.img still needed by anyone?

---

The root is embedded in recent 32bit remix - with the root access prompt - no need for any systemless root or any other You can write on system partition with any root file explorer. I guess it's the same for 64bit but I may be wrong.
EDIT:
@HypoTurtle I've attached the initrd.img file from recent PhoenixOS image (version 1.0.9-RC)
HypoTurtle said:
Systemless-root for RemixOS
Sticking to the above keeps system.img as OTA-updatable; replacing the ramdisk with the original will let the OTA apply
If you want read-write access to /system and break OTA - you can use the modified initrd.img
Click to expand...
Click to collapse
If I want write access to /system I need to modified initrd.img? Are you sure? If its superuser than it should allow me write wherever I want.
Anyway, is this 64bit made specifically for 64bit architecture or just for the 64bit Remix? I'm asking because I want to know if I can test the files with Phoenix or should I wait for 32bit files?
Thanks.

---

Will we see systemless Xposed soon??