[GUIDE] Systemless Root ONLY FOR Remix Version .403 - Remix OS for PC

Thanks to @HypoTurtle for providing the .img files!
Root privilege allows users to download and use apps such as Titanium Backup. It also allows easier modification of settings.
I thought some of you would like a step-by-step to root the most recent .403 Remix OS. I have tried here to put together a procedure that even new members can follow. Please let me know how it works for you.
PLEASE REMEMBER THAT MESSING AROUND MIGHT RESULT IN PROBLEMS IF YOU DO NOT FOLLOW INSTRUCTIONS EXACTLY.
This is only for 64 bit. Please note that you MUST type all command line commands Exactly as shown (including spaces and caps)
To root you will need only two files: one is a modified ramdisk.img that you will install while in Windows; and one is a superuser su.img to add to the data partition from the Remix OS command line.
1 First, if you haven't already, download and install Remix OS Version .403 from their website. Go through the complete installation.
2 Next, from Windows, using your favorite browser, download ramdisk-403.img and su.img from:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkVWRxU3pYMzVUWEU
3 To substitute the new ramdisk.img:
a Open the File Explorer and copy the ramdisk-403.img file.
b From the File Explorer, click on the Drive with your Remix OS.You will see a "RemixOS" folder.
c Click on it to open it. Now you should see the files including one named ramdisk.img.
d Click on the ramdisk.img and select rename the ramdisk.img to ramdiskorig.img to save it "just in case"
e Now rename the ramdisk-403.img to ramdisk.img
4 To finish you need to restart and boot into Remix OS.
a First thing to do in Remix is go to Settings/Experimental features/Enable terminal debug console and activate it.
b Open the File Manager and click on the Disk with Windows installed (usually Disk 1 or Disk 2)
c Click on "Users" and then on your user ID folder
d Find the "Downloads" folder and click on it. You should see the su.img that you downloaded while in Windows
e Click on the su.img file and drag it to the Download folder on the left. It will copy the su.img to your Download folder
5 Now you are ready to copy the su.img into your /data partition.
a Press ALT&F1 to open the command line. You should see a line of text with the # symbol.
b To copy su.img into /data, at the command line type: cp /data/media/0/Download/su.img /data/su.img
c Note that there are spaces ONLY after cp and img
d Press ENTER. If you receive no error message then you did it correctly.
Press ALT&F7 to leave the command line. Play it safe and reboot. You now can download and run any app that requires root access.
Set to go! Have fun. Let me know how it works for you.

---

Working

---

Works with 402???
My WiFi didn't broke with 402, so I'll not upgrade to 403...

---

Regnas said:
Works with 402???
My WiFi didn't broke with 402, so I'll not upgrade to 403...
Click to expand...
Click to collapse
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!

---

lollyjay said:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
Click to expand...
Click to collapse
Yeah, it's funny...
Anyway,I'll try that later..
Cheers..

---

lollyjay said:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
Click to expand...
Click to collapse
Any chance you have an lsmod from both. I know the issue in 402 was that both wl and b43 were both loaded - it might be viable to create a broadcom switch to flick between the two [one's proprietary and the other is open-source]

---

HypoTurtle said:
Any chance you have an lsmod from both. I know the issue in 402 was that both wl and b43 were both loaded - it might be viable to create a broadcom switch to flick between the two [one's proprietary and the other is open-source]
Click to expand...
Click to collapse
Yes, do you just want an lsmod output or do you want more specific?

---

lollyjay said:
Yes, do you just want an lsmod output or do you want more specific?
Click to expand...
Click to collapse
Both outputs or a diff 402-dmesg 403-dmesg > 402-403_diff would be fine. For some reason I'm still on 402 -- haven't gotten the 403 ota yet.

---

HypoTurtle said:
Both outputs or a diff 402-dmesg 403-dmesg > 402-403_diff would be fine. For some reason I'm still on 402 -- haven't gotten the 403 ota yet.
Click to expand...
Click to collapse
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Module Size Used by Tainted: P
binfmt_misc 9163 1
hid_sensor_als 4217 0
hid_sensor_incl_3d 4947 0
hid_sensor_accel_3d 4768 2
hid_sensor_rotation 4683 0
hid_sensor_magn_3d 5925 0
hid_sensor_gyro_3d 4755 0
hid_sensor_trigger 3417 12 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d
industrialio_triggered_buffer 1874 6 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d
kfifo_buf 3374 1 industrialio_triggered_buffer
industrialio 45973 11 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger,industrialio_triggered_buffer,kfifo_buf
hid_sensor_iio_common 5514 7 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger
hid_sensor_custom 9846 0
rtsx_pci_ms 8248 0
memstick 9812 1 rtsx_pci_ms
rtsx_pci_sdmmc 15489 0
mac_hid 3843 0
bsd_comp 4698 0
ppp_deflate 3798 0
ppp_async 6285 0
pppoe 8725 0
pppox 2638 1 pppoe
ppp_generic 22934 5 bsd_comp,ppp_deflate,ppp_async,pppoe,pppox
slhc 5081 1 ppp_generic
wmi 8736 0
wl 6426390 0
cfg80211 477899 1 wl
uvcvideo 66519 1
snd_hda_codec_hdmi 38342 1
videobuf2_vmalloc 4693 1 uvcvideo
videobuf2_memops 2716 1 videobuf2_vmalloc
videobuf2_v4l2 19150 1 uvcvideo
videobuf2_core 21313 2 uvcvideo,videobuf2_v4l2
snd_hda_codec_realtek 67326 1
snd_hda_codec_generic 53744 1 snd_hda_codec_realtek
thinkpad_acpi 66626 1
nvram 6533 1 thinkpad_acpi
soc_button_array 2418 0
snd_hda_intel 28041 1
snd_hda_codec 105597 4 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel
snd_hda_core 53903 5 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec
snd_hwdep 5785 1 snd_hda_codec
snd_pcm 87019 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer 20488 1 snd_pcm
snd 65356 9 snd_hda_codec_hdmi,snd_hda_codec_generic,thinkpad_acpi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6615 1 snd
shpchp 23487 0
rtsx_pci 41858 2 rtsx_pci_ms,rtsx_pci_sdmmc
r8169 61453 0
mii 4910 1 r8169
psmouse 101828 0
pcspkr 2158 0
lpc_ich 14290 0
intel_rst 2468 0
i915 1084918 9
drm_kms_helper 108824 1 i915
drm 311256 11 i915,drm_kms_helper
fb_sys_fops 1759 1 drm_kms_helper
syscopyarea 3185 1 drm_kms_helper
sysfillrect 3485 1 drm_kms_helper
sysimgblt 2562 1 drm_kms_helper
i2c_algo_bit 5421 1 i915
i2c_i801 16755 0
hid_sensor_hub 11145 9 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_custom
hid_multitouch 10208 0
coretemp 6156 0
hwmon 4404 2 thinkpad_acpi,coretemp
btusb 31833 0
btrtl 4762 1 btusb
btbcm 7000 1 btusb
btintel 8387 1 btusb
bluetooth 444084 9 btusb,btrtl,btbcm,btintel
Sent from my on Z00A using XDA Labs

---

Hi @lollyjay, the method is simple and easy and is working great....Thanks a lot for that.....But how do we enable system r/w because it did not let me edit build.prop to enable brigntness slider... in earlier version I used modified initrd.img....it there any other way to achieve system r/w... Thanks...

---

lollyjay said:
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Click to expand...
Click to collapse
I would like to help but I don't know how to generate this info..
What is this?

---

ssanjy said:
Hi @lollyjay, the method is simple and easy and is working great....Thanks a lot for that.....But how do we enable system r/w because it did not let me edit build.prop to enable brigntness slider... in earlier version I used modified initrd.img....it there any other way to achieve system r/w... Thanks...
Click to expand...
Click to collapse
They have removed the brightness slider in 402 at least.
I'm not sure which ramdisk this is; check getprop and see what ro.remixos.box is set to.
I'll upload my ramdisk if you want to check if the slider was readded in 403 [if its set to true].
I also have the modified initrd.img on my thread; where these .imgs are from. But ideally it's best not to use it; the only downside being needing to modify ramdisk.img itself for ro.* prop entries.

---

HypoTurtle said:
They have removed the brightness slider in 402 at least.
I'm not sure which ramdisk this is; check getprop and see what ro.remixos.box is set to.
I'll upload my ramdisk if you want to check if the slider was readded in 403 [if its set to true].
I also have the modified initrd.img on my thread; where these .imgs are from. But ideally it's best not to use it; the only downside being needing to modify ramdisk.img itself for ro.* prop entries.
Click to expand...
Click to collapse
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Sent from my S II using XDA Labs

---

ssanjy said:
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Click to expand...
Click to collapse
Hi you might try Root Browser from Play Store it can change permissions
Sent from my on Z00A using XDA Labs

---

lollyjay said:
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
It would need both from the same device; think I found a 402 that you posted elsewhere.
Code:
[b]Removed[/b]
b43 375752 0
mac80211 504422 1 b43
ssb 45258 1 b43
rng_core 7153 1 b43
bcma 43126 1 b43
efivars 7470 0 [efi variables]
[b]Added[/b]
intel_rst 2468 0 [rapid storage tech]
psmouse 101828 0 [touchpad]
would be the module difference between 402 and 403; so perhaps just blacklisting b43 on 402 would have sufficed [the others are dependant on it]
ssanjy said:
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Sent from my S II using XDA Labs
Click to expand...
Click to collapse
The 402 initrd should work fine [attach the 403 here just so I can compare to 402 just to see if anything was changed] if you want to modify it that way; but the slider is gone. Only options would be to add a shortcut to the brightness activity from SystemUI or a brightness app.

---

Hey guys, I'm using an HD install of remix os 403 - replaced the ramdisk - went back into Remix but couldn't access the ALT+F1 terminal for whatever reason. Eventually I managed to get the su.img into the right folder in the data.img and nothing happens. How would I be notified that it has worked? Would I see something different on startup? I assume the su.img is being mounted etc by the modified ramdisk.img.
Would it be a possibility to just make a fresh, clean data.img with just that su.img file already in? That way I could try just replacing the data.img and starting fresh. At this moment I can't see any change from the su.img and ramdisk.img being in place. Probably it's a problem at my end - but i'm confused why the ALT+F1 root terminal doesn't work for me?
I'm using a UK keyboard on an Alienware M17x R4 - any suggestions would be very welcome.
By the way I used Paragon ExtFS for Windows to access the data.img and insert the su.img file (which I verified in the terminal of remixos (not the root terminal, I couldn't get that working) but I can use the LS command in /data and I see that su.img is there.
Thank you for any suggestions

---

mrpras said:
Hey guys, I'm using an HD install of remix os 403 - replaced the ramdisk - went back into Remix but couldn't access the ALT+F1 terminal for whatever reason. Eventually I managed to get the su.img into the right folder in the data.img and nothing happens. How would I be notified that it has worked? Would I see something different on startup? I assume the su.img is being mounted etc by the modified ramdisk.img.
Would it be a possibility to just make a fresh, clean data.img with just that su.img file already in? That way I could try just replacing the data.img and starting fresh. At this moment I can't see any change from the su.img and ramdisk.img being in place. Probably it's a problem at my end - but i'm confused why the ALT+F1 root terminal doesn't work for me?
I'm using a UK keyboard on an Alienware M17x R4 - any suggestions would be very welcome.
By the way I used Paragon ExtFS for Windows to access the data.img and insert the su.img file (which I verified in the terminal of remixos (not the root terminal, I couldn't get that working) but I can use the LS command in /data and I see that su.img is there.
Thank you for any suggestions
Click to expand...
Click to collapse
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
Sent from my on Z00A using XDA Labs

---

lollyjay said:
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
I hadn't enabled the console/debug option thank you for that!
Now I'll go and try again. Thanks for the fix, and the systemless root files. I'll be back if it doesn't work, otherwise thanks again!
---------- Post added at 05:50 PM ---------- Previous post was at 05:28 PM ----------
Okay thanks, so that works - Just a small suggestion that somewhere in your description (where you mention the Alt+F1) it could be worth mentioning about enabling the debug console because I didn't find that information when scouring around. Maybe would be helpful to others as ignorant as me

---

mrpras said:
I hadn't enabled the console/debug option thank you for that!
Now I'll go and try again. Thanks for the fix, and the systemless root files. I'll be back if it doesn't work, otherwise thanks again!
Click to expand...
Click to collapse
My pleasure. You can test root by downloading an app that requires root such as Titanium Backup. It will immediately let you know if it cannot acquire root privilege
Sent from my on Z00A using XDA Labs

---

Just wanted to note here that the Lenovo ThinkPad Twist is a great dual Windows /Ubuntu and Remix OS daily driver. Great touchscreen display and can be used as a (heavy) tablet with Remix OS. Look at this on eBay http://www.ebay.com/itm/162121987813
I bought three from a school for $99 each.
Sent from my on Z00A using XDA Labs