I am currently on the NC5 build, and I have root. I have safestrap working, I can login as su on a terminal, and I have used the SELinux mod app to change the SELinux status to 'permissive"
I verified this with
Still, Debian-Kit cannot find SU. Trying to unpack it returns the ASH error mentioned in thread 2475803
Linux Deploy also fails with the mount point error others have mentioned.
Is this related to Knox? I have been thinking about switching to T-Mobile for the unlocked bootloader so I could install a different kernel, but I should be able to proceed with the permissive status, right?
If this is a problem with Knox, then I suppose that any current Samsung device will not allow chroot Linux or Debian-Kit?
I got a Samsung to use as a full Linux OS on my Desktop - this is a deal breaker for me.
FWIW, I had been on NK1, but I could not get SELinux to change to permissive, so I downgraded to NC5.
I verified this with
Code:
#getenforce
PermissiveStill, Debian-Kit cannot find SU. Trying to unpack it returns the ASH error mentioned in thread 2475803
Linux Deploy also fails with the mount point error others have mentioned.
Is this related to Knox? I have been thinking about switching to T-Mobile for the unlocked bootloader so I could install a different kernel, but I should be able to proceed with the permissive status, right?
If this is a problem with Knox, then I suppose that any current Samsung device will not allow chroot Linux or Debian-Kit?
I got a Samsung to use as a full Linux OS on my Desktop - this is a deal breaker for me.
FWIW, I had been on NK1, but I could not get SELinux to change to permissive, so I downgraded to NC5.
from xda-developers http://ift.tt/1bCWcPf
via IFTTT

Aucun commentaire:
Enregistrer un commentaire