Tuesday, 26 July 2016

Make Viper4Android 2.4.0.1 work on Android 6.0



I had some trouble trying to make Viper4Android v2.4.0.1 work on my Honor 5C running Android 6.0. This could be helpful…

Viper4Android didn't work after installation and reboot, the driver status showing as "abnormal". It seems related to a change in default SELinux policy.

I read that changing globally the SELlinux policy to "permissive" can solve the problem but it may be an extreme solution (SELinux is a security feature to restrict what an application can do, I don't know the potential edge effects).

I found another solution on the web, which consists in patching the SELinux policies at boot, just enough for Viper4Android to work.

If you did not make a systemless installation of SuperSU, open an adb shell and use these commands (courtesy of androiding.how):


Code:


su
mount -o rw,remount /system
cd /system/su.d
echo '#! /system/bin/sh' > 50viper.sh
echo '/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"' >> 50viper.sh
chmod 755 50viper.sh
cd /
mount -o ro,remount /system


And reboot.

If you did make au systemless installation of SuperSU, open an adb shell and use this instead:


Code:


su
mount -o rw,remount /su
cd /su/su.d
echo ‘#! /system/bin/sh’ > 50viper.sh
echo ‘/su/bin/supolicy –live “allow mediaserver mediaserver_tmpfs:file { read write execute };”‘ >> 50viper.sh
chmod 755 50viper.sh
cd /
mount -o ro,remount /su
exit


And reboot.



No comments:

Post a Comment