Hello.
So I installed a custom recovery, flashed lollipop fw and installed supersu.
Today I was trying to install Viper4Android but, unfortunately, it does not work.
I also installed the drm restore patch (audio clear + is working).
Is there any fix ? Is Viper working for someone here?
Thanks in advance.
Interested too, have a z3c too and have found a few threads describing the installation in 2 steps, flashing via recovery and installing an .apk but nothing specific for z3c.
will update this thread once I have a full nandroid backup and am ready to play around.
I was in the same situation as you guys and couldn't live without V4A.
You/we forgot 1 step
You need to set SELinux mode to permissive and then install V4A driver:
Use this simple app:
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Amy more advice? Tried that, then set it back, yet viper doesn't seem to be getting used although the driver is installed, where do I select viper as the processor for audio?
ovizii said:
Amy more advice? Tried that, then set it back, yet viper doesn't seem to be getting used although the driver is installed, where do I select viper as the processor for audio?
Click to expand...
Click to collapse
You don't, I was also looking for that for a while, but PowerAmp picks that up automatically and so I guess the entire OS
Sent from my D5803 using XDA Free mobile app
Dsteppa said:
I was in the same situation as you guys and couldn't live without V4A.
You/we forgot 1 step
You need to set SELinux mode to permissive and then install V4A driver:
Use this simple app:
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Click to expand...
Click to collapse
any idea what happened that google play store link is no longer valid? shall I chose another one or restore from backup?
ovizii said:
any idea what happened that google play store link is no longer valid? shall I chose another one or restore from backup?
Click to expand...
Click to collapse
Nope, seems like they removed it from the store
I've had a backup with TItaniumBackup but I was just curious what happened there...
Did as Dsteppa sayed. Worked for 10 sec. closed music app and viper and start again. Same thing. Btw I have force enable V4A. Then i went to viper settings and changed FX compatible mode to compatible and restart phone. Works perfectly! Thanks so much!
The solution is disable or froze "Sound Enhancement" app, and that's all, V4A is going to work fine without need of change the option to "Compatible Mode".
iFlasher said:
The solution is disable or froze "Sound Enhancement" app, and that's all, V4A is going to work fine without need of change the option to "Compatible Mode".
Click to expand...
Click to collapse
Thank i try now
MrPingle
Also make sure that Equalizer (in settings, not Viper) is set to Off mode.
I try to install V4A (through Apk) but when i install the drivers, a message says: "Driver install failed: the busybox installation on you device does not work... etc."
I have just installed the last version of busybox in /system/xbin and set Selinux permissive.
How can i resolve it?
I get root with Kingroot e after change binaries to Supersu's binaries.
I'm just creating this so that it'll be easy for everyone to post about the functionality of the awesome viper4android
I used it with SELinux mode changer and it worked. But is there like a more simple way to install and make the app work.
Any suggestions and workarounds?
Sent from my E6533 using XDA-Developers mobile app
from my side, am using androkernel v31, i had a problem when installing drivers for viper, it says installed but when phone is restarted, it asks to instal driver again.
fix: setting>app>viper4android, allow storage in permission
zemetal said:
from my side, am using androkernel v31, i had a problem when installing drivers for viper, it says installed but when phone is restarted, it asks to instal driver again.
fix: setting>app>viper4android, allow storage in permission
Click to expand...
Click to collapse
Hmmm, I had the same problem but soon as I set SELinux to permissive it worked.
njaya95 said:
Hmmm, I had the same problem but soon as I set SELinux to permissive it worked.
Click to expand...
Click to collapse
on mine, SELinux was already on permissive.
I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.
Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.
UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel:
Hey all,
Android 7.1.1, Magisk 20.4 (on Stable update channel), Magisk Manager is hidden (as "Manager", tried "MM" as well) and the updated Sony app was added to Magisk Hide list.
Data & Cache were cleared for the app as well.
https://play.google.com/store/apps/details?id=com.playstation.remoteplay
But on launch, it crashes with error 88001003, which seems to indicate root detection.
The previous version 3.0 has worked flawlessly on the same system with same settings.
Does anyone know a workaround, could the app now be checking the system for root-compatible apps and block from there ?
Any way to find out how the app detects root?
Any feedback is very welcome.
Full Manager obfuscation capabilities aren't available on Android versions lower than 9. Could be what's causing your issues...
For what it's worth I can start the app just fine on my Android 9 OP3T with Canary build 21004 and hidden Canary Manager 310.
Try uninstalling the Manager and see if that makes a difference.
Log Cat info :
Code:
[10-15 14:29:26.760 4218:4218 D/PRCNT_#RecentsModel#]
#createTaskStack# :: task=PS Remote Play, isTopRunningTask=false, isVisible=false, isLocked=false, isKnoxTask=false, isHideThumbnail=false, isLongLive=false
Didgeridoohan said:
Try uninstalling the Manager and see if that makes a difference.
Click to expand...
Click to collapse
Sadly no difference (and deleted app's data + cache of course). Would you have any other ideas?
Spartacus500 said:
Log Cat info :
Code:
[10-15 14:29:26.760 4218:4218 D/PRCNT_#RecentsModel#]
#createTaskStack# :: task=PS Remote Play, isTopRunningTask=false, isVisible=false, isLocked=false, isKnoxTask=false, isHideThumbnail=false, isLongLive=false
Click to expand...
Click to collapse
Thanks but I'm not sure how it's supposed to help?
Ps24u said:
Sadly no difference (and deleted app's data + cache of course). Would you have any other ideas?
Click to expand...
Click to collapse
Many things may trigger detection, not only Magisk:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Thanks Didgeridoohan, after many hours I found 2 culprits that triggered root detection on my system.
For the Sony Remote Play app mentionned in this thread: SELinux set to permissive was the culprit.
After disabling the Magisk module for SElinux, the app runs normally, no crash, all good.
But it's pretty annyoing having to reboot to enable/disable SELinux just to run this app.
Would you know if there's a way to either toggle SElinux in realtime while the os is running or to have the Sony app always believe SElinux is set to enforcing ?
For the second app, it was dumb, it looked for "twrp" folder on internal storage. After I renamed the folder, the app launches and runs perfectly.
But again it's far from ideal to do it manually all the time. So for this case also, is there a way to hide the "twrp" folder from this app, either via magisk module, script or otherwise?
Thanks a lot for your tips and awesome site, probably the best ressource for all things Magisk. :bow:
Ps24u said:
Would you know if there's a way to either toggle SElinux in realtime while the os is running or to have the Sony app always believe SElinux is set to enforcing ?
Click to expand...
Click to collapse
That's just a simple terminal command (which is exactly what the module uses and runs at boot). You can run that whenever and it'll change selinux to the state you want on the fly, no need for a reboot.
Permissive:
Code:
setenforce 0
Enforcing:
Code:
setenforce 1
Needs to be run as su, of course (you could add "su -c" in front of the command to make it easy).
You could either set up a script with an app like Tasker or use an app that's made for toggling selinux (if you look around there should be a few available).
For the second app, it was dumb, it looked for "twrp" folder on internal storage. After I renamed the folder, the app launches and runs perfectly.
But again it's far from ideal to do it manually all the time. So for this case also, is there a way to hide the "twrp" folder from this app, either via magisk module, script or otherwise?
Click to expand...
Click to collapse
To hide the TWRP directory you could use an isolation app to stop the app from detecting what you have on your device. When it comes up the internal storage, Storage isolation is the most powerful.
Another option could be to set up a Tasker task (or similar) that renames the folder and then launches the app. Another Tasker profile could then keep track of when the app is running and rename the folder again once it's closed. Or it might be more reliable to run a task manually when you're done with the app. I'm just mentioning this to show some options. It's nowhere near as elegant as using an isolation app...
Thanks a lot for your tips and awesome site, probably the best ressource for all things Magisk. :bow:
Click to expand...
Click to collapse
No worries, I'm glad you found it useful and could get things figured out.
Didgeridoohan said:
That's just a simple terminal command (which is exactly what the module uses and runs at boot). You can run that whenever and it'll change selinux to the state you want on the fly, no need for a reboot.
Permissive:
Code:
setenforce 0
Enforcing:
Code:
setenforce 1
Needs to be run as su, of course (you could add "su -c" in front of the command to make it easy).
You could either set up a script with an app like Tasker or use an app that's made for toggling selinux (if you look around there should be a few available).
Click to expand...
Click to collapse
That strangely doesn't do the trick. If SElinux is set to permissive at boot via Magisk module, toggling to Enforcing afterwards doesn't allow the app to launch (crashes with same error 88001003, even after deleting data+cache).
It seems the app somehow knows if SElinux was set to permissive on boot and doesn't care if SElinux is switched to Enforcing afterwards.
Due to how my setup works I need Permissive at boot (mount cifs folders) so I'm in pinch.
I use selinux_permissive_v2.zip on Magisk 20.4.
I also tried to set SElinux to permissive via a script in /data/adb/service.d
Code:
#!/system/bin/sh
setenforce 0
But same results, toggling to Enforcing afterwards doesn't allow the app to launch.
I tried toggling with "su -c setenforce 1" in Termux, and with SELinux Toggler.
However, If the phone boots with Enforcing, and then I toggle to Permissive after boot and then back to Enforcing, the app launches without issues, strange!
There is a mystery going on here...
Didgeridoohan said:
To hide the TWRP directory you could use an isolation app to stop the app from detecting what you have on your device. When it comes up the internal storage, Storage isolation is the most powerful.
Click to expand...
Click to collapse
That worked straight away, awesome!
On my Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE root Magisk, this application does not work, keeps saying "something went wrong", I changed the twrp folder to aaaTWRPaaa but still the application won't work. I also changed selinux mode changer to permisive, but after this change also doesn't work, my antivirus screams selinux permisive is dangerous. Any ideas ?
Spartacus500 said:
On my Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE root Magisk, this application does not work, keeps saying "something went wrong", I changed the twrp folder to aaaTWRPaaa but still the application won't work. I also changed selinux mode changer to permisive, but after this change also doesn't work, my antivirus screams selinux permisive is dangerous. Any ideas ?
Click to expand...
Click to collapse
From my testing, PS Remote Play doesn't care about TWRP folder.
Spartacus, for now try to boot with SElinux to Enforced, and clear data/cache for the app.
I hope Didgeridoohan can help solve the SElinux pemissive at boot mystery.
Ps24u said:
I hope Didgeridoohan can help solve the SElinux pemissive at boot mystery.
Click to expand...
Click to collapse
Not really... I've no idea why the app would behave like that.
But I have a thought: how do you set up your cifs folders mounting? With a script? If so, could you temporarily set SELinux permissive only during that time? If you're lucky, it might be that's enough... I have no idea how cifs folder mounting works, so I'm just throwing ideas aimed at your head.
Ps24u said:
From my testing, PS Remote Play doesn't care about TWRP folder.
Spartacus, for now try to boot with SElinux to Enforced, and clear data/cache for the app.
I hope Didgeridoohan can help solve the SElinux pemissive at boot mystery.
Click to expand...
Click to collapse
I did as you said, deleted the TWRP folder from internal storage, also deleted the Titanium backup folder, no result, Selinux I have enforcing, the application still shows an error on startup
I also have a question, is your audit error the same as mine? Maybe there is a bug here
audit (error)
Code:
type=1400 audit(1603135249.830:2343): avc: denied { read } for pid=7381 comm="zCloudWorkerThr" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0:c212,c259,c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=1 SEPF_SM-N935F_9_0001 audit_filtered
Code:
type=1400 audit(1603135249.830:2344): avc: denied { open } for pid=7381 comm="zCloudWorkerThr" path="/sys/fs/selinux/enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0:c212,c259,c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=1 SEPF_SM-N935F_9_0001 audit_filtered
Didgeridoohan said:
Not really... I've no idea why the app would behave like that.
But I have a thought: how do you set up your cifs folders mounting? With a script? If so, could you temporarily set SELinux permissive only during that time? If you're lucky, it might be that's enough... I have no idea how cifs folder mounting works, so I'm just throwing ideas aimed at your head.
Click to expand...
Click to collapse
In the context of Cifs, I need SELinux permissive during actual use, not only during the mounting phase, so it cannot be done unfortunately.
Spartacus500 said:
I did as you said, deleted the TWRP folder from internal storage, also deleted the Titanium backup folder, no result, Selinux I have enforcing, the application still shows an error on startup
I also have a question, is your audit error the same as mine? Maybe there is a bug here
audit (error)
Click to expand...
Click to collapse
I'm not sure what / how to "audit" ?
I'm back again, Samsung Galaxy S7 edge Custom Pie 9.0 Rom. Selinux enforcing, PS Remote Play 4.0.0 keeps crashing, I uninstalled Magisk root and PS Remote Play 4.0.0 app works fine on my S7, I reload Magisk root via TWRP and PS Remote Play 4.0.0 shows error again ...
You've added PS Remote Play to the "Magisk Hide" list already, right ?
If not, add it, then clear data/cache or Uninstall and reinstall the app but don't launch it, and reboot.
Ps24u said:
You've added PS Remote Play to the "Magisk Hide" list already, right ?
If not, add it, then clear data/cache or Uninstall and reinstall the app but don't launch it, and reboot.
Click to expand...
Click to collapse
Of course, right after installing Magisk I hid hide root for PS Remote Play 4.0.0 and also changed the name of Magisk manager to something else, cleaning the memory for this application does not help either, every time I open the application it says "something went wrong" and error code ... All I need to do is remove the Magisk root and the app works. I'm using Magisk 20400, tested 21000 and Canary 21005 version and on neither of these versions this app shows the same error
Sorry I can't help more. I'm on Magisk 20.4 and M.Manager 7.5.1, also on Android 7.1.1 official Sony rom.
I performed the test, removed the Magisk root, PS Remote Play 4.0.0 works, when I install only Magisk manager, then PS REMOTE PLAY 4.0.0 detects Magisk and shows an error, after removing Magisk manager, PS Remote Play 4.0.0 works again, but it's enough that I will upload root Magisk, hide root hide, remove Magisk manager then PS Remote Play 4.0.0 shows error ...
I've got the same issue, anyone find a workaround?
Same here. This app work in the past, now it doesnt open. I dont know why Sony now dont left we use it because of root. It thinks that we will hack something. Mas, if Sony continues to do this and **** the past generation with last updates I will left consoles for while.
Im using Android 8.1