yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Accessories] Clayter21:
I've looked over the threads and they seem to be older for when the phone first came out. I cant seem to find a definitive answer for a case that fits tempered glass without popping up the edges. Any suggestions.
[Samsung Galaxy S7 Edge Accessories] neezy13:
There are plenty of updates if you check through the tempered glass screen protector thread. The last 10 pages or so are the most current info.

The real answer to your question is "it depends." The cases that do work typically have such a slim margin that manufacturing variation can cause it to work fine for one person and not for another. I have a Cover-Ups Explorer wood back case and it fit with both of the TGSP I tried, but it was very close. Right now I'm using the Supcase Unicorn Beetle Pro with my Amazingthing TGSP. This case is similar to an otterbox in construction as it is two pieces and the front goes over the screen and then you put the back on. This prevents it from lifting the corners. It is a tight fit though.
[Samsung Galaxy S7 Edge Accessories] Clayter21:
appreciate it
[Remix OS for PC] lollyjay:
Thanks to [MENTION=4056517]HypoTurtle[/MENTION] 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.
[Remix OS for PC] muzab a:
Working
[Remix OS for PC] Regnas:
Works with 402???

My WiFi didn't broke with 402, so I'll not upgrade to 403... ;)
[Remix OS for PC] lollyjay:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
[Remix OS for PC] Regnas:
Yeah, it's funny...

Anyway,I'll try that later..

Cheers..
[Remix OS for PC] HypoTurtle:
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]
[Remix OS for PC] lollyjay:
Yes, do you just want an lsmod output or do you want more specific?
[Remix OS for PC] HypoTurtle:
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.
[Remix OS for PC] lollyjay:
I don't have 402 any more. Here is one from 403. Maybe [MENTION=6106737]Regnas[/MENTION] 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
[Remix OS for PC] ssanjy:
Hi [MENTION=4762414]lollyjay[/MENTION], 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...
[Remix OS for PC] Regnas:
I would like to help but I don't know how to generate this info..

What is this?
[Remix OS for PC] HypoTurtle:
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.
[Remix OS for PC] ssanjy:
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
[Remix OS for PC] lollyjay:
Hi you might try Root Browser from Play Store it can change permissions
[Remix OS for PC] HypoTurtle:
It would need both from the same device; think I found a 402 that you posted elsewhere.

[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]

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.
[Remix OS for PC] mrpras:
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
[Remix OS for PC] lollyjay:
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
[Remix OS for PC] mrpras:
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 :)
[Remix OS for PC] lollyjay:
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
[Remix OS for PC] lollyjay:
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.
[Remix OS for PC] xc3nt4ur0x:
NOT WORK =(

This is NOT work for me ... I did all steps but NOT WORK ROOT.

What can I do? ... I dont speak english! and I dont use traslator!

Pardon me for my grammar! =D
[Remix OS for PC] lollyjay:
What is your language? What step did not work.
[Remix OS for PC] xc3nt4ur0x:
now work! =)

Hey now yes works! Thank you! Thank you! Now remix is root. I did try again and this time WORK!

=)
[Remix OS for PC] lollyjay:
My pleasure!
[Remix OS for PC] spicemaster:
Thank you for explaining how to achieve systemless root access...

i'm able to get root access to run apps like adaway, root explorer, etc. But I'm not able to mount system as R/W in order to modify contents in system partition like build.prop or add/remove apps, bootanimation, etc.

please let me know how to mount system as R/W

thank you once again.
[Remix OS for PC] lollyjay:
Hi I use Solid Explorer but you might try Root Browser from Play Store it can change permissions
[Remix OS for PC] spicemaster:
hi... thank you for your suggestions... i tried solid explorer and tried to remove the bootanimation.zip and some other system apps but all attempts failed (just like it did when i'd used root explorer) with the same error "unable to mount system" (as R/W).

Are you able to modify system partition files, for example, are you able to atleast rename bootanimation.zip or some similar file? or is it just me?
[Remix OS for PC] lollyjay:
Yep I was able to rename it in Solid Explorer.
[Remix OS for PC] spicemaster:
Weird. I will try reinstalling later and try to root again as per your guide, again to see if I missed something.

For now, I'll boot to Windows and use rmxtools to extract system.img, make the necessary modifications I wish to make and then repack system.img to boot to remix os

Thanks again. I am glad I can at least use apps that's require root access.. modifying system is only required once in a blue moon, but root access to run those apps is needed on every boot.
[Remix OS for PC] xc3nt4ur0x:
Remix os sometimes freezes

Hi! again! :D :o

I have a question... Remix sometimes freezes constantly or the screen goes black for a few seconds / minutes but the mouse work .... in some cases "Remix OS" restarts only ....

Why does this happen? Its my Lapto or Remix Version?

I have a Lapto HP - 14 w006-la

mmm other little thing, the camera, microphone and bluetooth not work, why?

I remember you, I dont speak english! Sorry for my grammar!

:) :D :good: :laugh:
[Remix OS for PC] lollyjay:
Hi what is your primary language?
[Remix OS for PC] lollyjay:
Oops! My "misteak". I forgot that I was using Phoenix OS. I'm testing both on identical Lenovo ThinkPad Twist "laplets" :p

Your method is easiest way.
[Remix OS for PC] HypoTurtle:
Easiest way would be to use the modified initrd.img; feel free to add that to OP with using this will break OTA

afaik this is my su.img [64bit] unaltered [right [MENTION=4762414]lollyjay[/MENTION] ?]; in that case there is a bind mount script being run in /su/su.d; where files located at /su/vendor/* are loop mounted over /system/*

With the caveat being that some files [i.e. build.prop] are read before the loop mounting happens. I haven't checked if bootanimation can be replaced/removed this way yet; but for sure ro.* entries in build.prop can't be changed; others should be changable in some fashion without needing to mount system.img as rw.
[Remix OS for PC] spicemaster:
if a modified initrd.img provides r/w mount for system, but breaks OTA, then we can use it whenever we need to modify system files... and later when OTA is available, just restore stock initrd.img ???

could you provide a link to such a modified initrd.img file?

i tried replacing the stock initrd.img with the modified 64bit initrd.img provided by rmxtools to keep root in previous versions of remix os.

but that did not help - same situation prevailed - apps get root access, but system could not be mounted as r/w

thank you

---------- Post added at 12:24 PM ---------- Previous post was at 11:40 AM ----------

i edited su/vendor/systemfiles.txt and added the line: system/media/bootanimation.zip to the end of the list, and rebooted.

that gave me access to the bootanimation.zip file as r/w under /su/vendor/media/bootanimation.zip

i tried to replace the stock boot animation file with a custom boot animation, changed permission to rw-r-r and then browsed to /system/media (r/o) and confirmed that the file that appears there now is the custom boot animation file.

but upon restarting, the stock bootanimation showed up. and after the OS was completed loaded, i browsed to the system/media folder and confirmed that the bootanimation stored there is custom, and not stock which appears on boot.

so i figure maybe the systemless root retains original un-modified system until remix os is loaded (past the bootanimation phase) and then provides write acccess to whatever mount-points are specified in the su/vendor/systemfiles.txt

so, its pointless to try and replace bootanimation in systemless-root config?? in which case, i might as well just make all system changes including replacing my boot animation by extracting and repacking system.img using rmxtools in windows
[Remix OS for PC] HypoTurtle:
No, once system.img is mounted r/w even once it breaks OTA; replacing initrd.img won't fix it you'd also need to replace system.img. With system-less root OTA is also broken; but can be fixed by replacing the original ramdisk.img

This initrd.img should work fine even though it says its for 402.

Yea you're right about bootanimation; it must be loaded before the su.d's get run.

Just fyi you don't neccessarily need to edit systemfiles.txt; the presence of a file in /su/vendor/ is enough. The txt was more just for ease of messing with stuff/following otas. i.e. clear the /su/vendor folder after an OTA then reboot and you have the new system files to edit...
[Remix OS for PC] spicemaster:
Thank you for providing the appropriate initrd.img file to gain complete system r/w privileges... i'm finally able to modify system content as i see fit...

And most importantly, thank you for helping me understand the concepts behind systemless root access :cyclops:
[Remix OS for PC] dhanny:
do you have a initrd.img for 32bit .403 ?
[Remix OS for PC] lollyjay:
32bit already has su. Any reason to make it systemless?
[Remix OS for PC] wizmart:
i agree 32bit has su but the system stay r/o on ntfs partition even choosing r/w install. i got r/w system only on ext4 install, so how to get r/w system on ntfs?
[Remix OS for PC] dhanny:
yea, i agree to [MENTION=1675526]wizmart[/MENTION]

thats still r/o on ntfs.

and i installed using Remix OS Install Tool in Windows, yesterday. And i install SuperSU, but still get error update su.

so, how to make systemless on ntfs?

(btw, sorry for my bad english)
[Remix OS for PC] RemixOS_Jason:
Hey [MENTION=4056517]HypoTurtle[/MENTION] and [MENTION=260923]ANyOne[/MENTION] who's device seems to recognize 2.0.402 as the latest version... Can you please go to 'Settings > About' and take a screenshot? Please make sure that your 'Model number' and your 'Serial number' are visible in the screenshot and PM me here in XDA. Thanks!
[Remix OS for PC] pooniaprashant:
Will this break OTA?
[Remix OS for PC] HypoTurtle:
Temporarily - replacing the ramdisk.img with the stock version will fix it.
[Remix OS for PC] pooniaprashant:
Voila ?
[Remix OS for PC] spicemaster:
hello again,

now that remix marshmallow's been released, can we root this new version using the same su.img and ramdisk provided here?

and also, will i need a different modified initrd.img or can i use the initrd.img you have provided (from .402 ) ??

thank you.
[Remix OS for PC] HypoTurtle:
su.img would be fine; will need to download the others to check. In the mean time try the 402 imgs and see if they boot.

Edit. Just updated over - 402 (with minimal effort) and Remix 3.0 looks sharper on my screen and system(/settings)-wise it seems closer to stock Android-x86 (MM) {and thus also PhoenixOS} and as such it has proper root implemented by default.

I will still make an initrd.img for system rw and a ramdisk.img for systemless root (if you need to modify init.sh for example; and want to keep OTA support)

@RemixOS_Jason The one fix I still need to modify init.sh (or run a su.d) is for the touchscreen; which seems doesn't get released properly by Windows when trying to boot RemxOS. The fix is simply re-probing the i2c_hid module. i.e. rmmod i2c_hid && modprobe i2c_hid. source addition here xdaforums.com/showpost.php?p=64664052&postcount=2153 would do it
[Remix OS for PC] spicemaster:
my internet connection here is slow like 512Kbps, i'm downloading the 932MB zip file from jide.com at 50 to 60 KB/s... need to wait atleast another 3 to 4 hours until i'm done downloading.

i thought i'd ask you and get requirements for root ready by the time its done.

anyway, will try using the imgs from 402/403 and let you know when i'm done.
[Remix OS for PC] HypoTurtle:
Was hoping for an OTA but as I'm stuck on 402 anyway. I might as well download the whole thing; should take me ~1hr - so should have the .imgs ready to go.
[Remix OS for PC] lollyjay:
U R Da Man:good:
[Remix OS for PC] HypoTurtle:
Couple of files attached for those that need them. i.e. here

initrd.img will break OTA integrity of system.img

I have the read/write and systless_su down to simple scripts now (using chainfires's sukernel binary); so I'll post/integrate those at some point so you can autogenerate these - Jide probably could integrate a systemless_root switch [or at least my loop mounting script] into the Dev/Remix Options; they do have some sort of system_dev.img thing going on that I haven't figured out yet what it's purpose is/what it does.
[Remix OS for PC] dhanny:
is latest 32bit version still ready to root using SuperSU? or must make systemless-root ?

- sorry for my bad english -
[Remix OS for PC] HypoTurtle:
Root should be built in with 32bit; as it is with 64bit. And you shouldn't need SuperSU at all; and it may complain that the su binary is outdated [due to it not being it's binary].
[Remix OS for PC] spicemaster:
the built-in superuser, while it gave root permission to run apps like AdAway, it did not let the app modify hosts file in the system.

but, upon replacing the stock remix initrd.img and ramdisk.img with the ones you have provided here, I was able to get complete root access with system r/w

thanks again.

now the only thing is, other NTFS partitions on my laptop dont show up in file manager (like it used to in .205, .402 and .403), but thats not a question for this thread :)
[Remix OS for PC] HypoTurtle:
Just fyi. you only would have needed initrd.img; ramdisk.img won't be doing anything without a /data/su.img; and you don't really need systemless-root if you've got system.img as rw.

I'm using systemless with mine; [adaway, firewall, touchscreen fix] as I'm using the 1.1GB system.sfs [system.img is what... 2.5GB]
[Remix OS for PC] spicemaster:
What does this "touchscreen fix" fix as such?

I'm running remix os on a touch screen Razer blade. Touch seems to work out of the box on this laptop
[Remix OS for PC] HypoTurtle:
It's just reloading the touchscreen module.

My touchscreen doesn't get released by Windows it seems [rebooting from Windows to load RemixOS - touchscreen would be unresponsive; cold booting to RemixOS and touch works fine].

It's just rmmod i2c_hid && modprobe i2c_hid; saves me having to connevt a keyboard to run it.
[Remix OS for PC] ManikandanGuru:
How to make system read and write

Solid explorer says no root. AdAway not working.

I don't think the default root app is working good.

I have followed every thing started here.

Using marshmallow.

---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------

If I select root in es file explorer it says sorry test failed this feature cannot run on your device.
[Remix OS for PC] lollyjay:
Until we have a system that is write enabled we can not make modifications.