ViPER4Android on Marshmallow. - Sony Xperia M4 Aqua

Sorry for another topic, but this seems unresolvable. SELinuxModeChanger says it can't obtain root, even tho I'm rooted, and no other app has a problem with root. Terminal Emulator also says that it has no permission when doing setenforce. And even if I flash a V4A build claiming to bypass enforcing SELinux, it constantly crashes, making my device unusable. Anyone else having a problem like this?

I have MM running on my E2353, and it is rooted, and I do have the problem too. I did see someone posting something about an Aroma based SELinuxModeChanger somewhere here. I'll try to find it and post it here.

There is a systemless root version for the Selinuxmodechanger app look at the thread

Related

Fix for android apk being disabled as system modified

Downloaded worldpay.apk available from their site. I have a rooted sanei n10 and updated ICS os. Anytime I try and open app it says ' the operating system of this device has been modified. Due to credit card security measures this app has been disabled' or a message very similar to this. I know some people had similar issue with barclaycard pingit but the fix for that doesn't work in this case. Ie install superSU, uninstall superuser, install hide my root. Hide my root always fails to hide su binary and says there is no su app to hide.
Need a fix that works for this ASAP.
Ajohnston01 said:
Need a fix that works for this ASAP.
Click to expand...
Click to collapse
I wish you luck with it, but unfortunately this is not the proper place to ask about that. Please use our Q&A forums for asking questions and kindly post a follow up in our Android Forums for others who may run into the same issue.
edit: If you're using super su try having it hide it/temp unroot and then wipe app data for worldpay. That should do it.

[Q] Cydia Substrate can't perform its "internal safety check"

Hello there xda developers-Community ,
this is my very first post and I hope this is the correct board I'm posting in .
I have an issue with Cydia Substrate on Android, but before explaining to you what the issue is, I'd like to explain to you what I wanted to do and why I need Cydia Substrate (if you don't really care you can skip this, of course ):
I'm using a banking-app which, when detecting root on a device, stops working completely (it doesn't just show a warning, it refuses the user from continuing to the next screen). Of course, I don't want to unroot my device. So I did some research and came across apps like Hide my Root and RootCloak which is a Xposed Module. All of these apps didn't work for me, even when installed and set up correctly. After doing some research again I found out that it doesn't work for other users either... Doing even further research I finally came across RootCloak Plus which works with Cydia Substrate and not Xposed anymore. I can't confirm it yet, but according to the thread this method should work with my app. So, I downloaded Cydia Substrate (I tried the Google Play-Version and the APK from the website) and RootCloak Plus from Google Play. But now we get to the main issue:
Everytime I open Cydia Substrate it shows me a message saying:
Note: something about your device made it impossible for Substrate to perform its internal safety check; can you please contact saurik via e-mail?
Click to expand...
Click to collapse
Of course, actually contacting saurik via e-mail wasn't my first option .
I tried to fix this issue on my own with doing the following:
I updated CyanogenMod to the latest nightly
I switched my superuser app from SuperSU to superuser and back to SuperSU
I tried changing the SELinux mode from "enforcing" to "permissive" with SELinuxModeChanger
Reinstalled the apps and rebooted my device serveral times
Unfortunately, even though this problem seems to be quite common, there are only a few to nearly no threads covering this topic anywhere (at least I only came across over a few of them).
Here are some of my specs and details, maybe any of this will help:
Device: Samsung Glaxaxy S4 (jfltexx)
CyanogenMod version: CyanogenMod 12 12.1-20150708-NIGHTLY-jfltexx (Android 5.1.1)
Superuser App: SuperSU Free (CM) v2.46 (binary up to date and SuperSU working with other apps just fine)
BusyBox version: BusyBox v1.23.2-Stericson
Root properly installed and working, confirmed by serveral apps.
Do you have any idea how to fix this issue? I hope you can help !
Thank you very much,
DigitalClark .
I have the exact same issue. On my streaming app, xposed module allows me to bypass warning, but I still can't watch any shows...
Lg G3 D855
Rooted, Resurrection remix 5.5.4
Lollipop 5.1.1
I've emailed Saurikit on the email address provided on google play, but no reply...
Sent from my LG-D855 using XDA Free mobile app
I have the same problem on a Sony Z2 (sirius) CM12.1
So if anyone has an idea for a solving I'd highly appreciate!
Bump, in-case if someone has ran across a similar issue and found a solution.
Cydia Substrate is supported on Android 2.3 to 4.3 according to their website. Also the app itself hasn't been updated since 2013. Thus the chances that it will work on 5.1.1 are pretty dim.
I get the same message. I am just wondering if SuperUser is the reason. I don't think SU can find it, will this cause the internal safety check message to occur?
If you jail break your device it will work
I have the same problem ASUS ZenFone 2

never asks for root

Newest stable version works but doesn't ask for root privilege. Rooted using Chainfire's supersu.
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now
Best of luck
Sent from my Sony Xperia SP using XDA Labs
Which settings require root? I've toggled all the settings and none of them made it ask for root.
olliebean said:
Which settings require root? I've toggled all the settings and none of them made it ask for root.
Click to expand...
Click to collapse
For me it asked for root when I changed settings under "wake up tracking and cut off".
If nothing happens to you reboot your phone and try again, you could also check to see if there is any denied requests of greenery in super su app and manually grant it.
Sent from my Sony Xperia SP using XDA Labs
ghst7 said:
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now
Best of luck
Click to expand...
Click to collapse
Oh it works just fine. It's just not showing up in Supersu as having root access.
I have the same problem.
After I updated from the market today I can't get greenify to properly request root access.
When I run it I tell it I'll rooted, see it saying it's requesting root access but supersu doesn't prompt then says it can't get root. Same results with rebooting.
In supersu there are no request prompts from greenify. I deleted the greenify access to see if that would get it to reprompt but it still says can't get root and supersu shows no requests in logs.
Other apps still work fine in supersu.
Edit --
Interesting, I disabled the module in xposed and when it prompts for root supersu pops right up. So I gave it access that way but logs show that once the module is reenabled it never asks for root.
Weird
Can't get root privilege
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
rockah said:
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
Click to expand...
Click to collapse
Got mine to work by deselecting Greenify module in Xposed and rebooting. Started Greenify app and it said to either to activate the Xposed module or select non-root mode. I clicked on Greenify settings and tried to change Xposed settings and a popup window asked if I wanted to activate Xposed module. I selected yes, Xposed started, I selected Greenify module and rebooted. During the bootup process, Greenify asked for root permissions.
A similar process worked for me: deactivated the Xposed module, rebooted, started the Greenify app, then I went into the Greenify settings and turned on the enhanced wake up tracker, which caused Greenify to request root. Granted permission, then reactivated the Xposed module and rebooted again. Checked in SuperSU that Greenify had permissions, then I just had to re-enable the Xposed based features in the Greenify settings.
Having done that, however, I see from the SuperSU logs that Greenify isn't actually requesting any root permissions since I re-enabled the Xposed module. I suspect the new version is using Xposed for all its root access and no longer needs root permissions for the app in Boost (Xposed) mode.
Lots of guessing here.
I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
dreinulldrei said:
Lots of guessing here.
I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
Click to expand...
Click to collapse
Read prior posts for further guidance. Seems others have got it to work. I had zero/nada/no problems on latest betas w/Xposed and SuperSU 2.76. YMMV.
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
dreinulldrei said:
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
Click to expand...
Click to collapse
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).
BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.
Wonder if I should drop back to v2.76 and how to even do that without losing root?
Davey126 said:
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).
BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
Click to expand...
Click to collapse
---------- Post added at 03:55 PM ---------- Previous post was at 03:43 PM ----------
This page has a link to the SuperSU v2.76 zip on ChainFire's site, which can be flashed with TWRP, etc depending on your phone.
https://www.progeeksblog.com/download-supersu-for-android/
I have not tried to flash it myself.
divineBliss said:
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.
Wonder if I should drop back to v2.76 and how to even do that without losing root?
Click to expand...
Click to collapse
If life is good don't change anything! I'm not out to skewer SuperSU v2.78; the problems I and a few others experienced are likely outliers with various contributing factors. That said, SuperSU 2.76 has been rock solid on my devices as have most of ChainFire's previous releases. Sticking with what works for now.
rockah said:
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
Click to expand...
Click to collapse
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
If you moved Greenify apk to
"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
craigevil said:
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
Click to expand...
Click to collapse
divineBliss said:
If you moved Greenify apk to
"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
Click to expand...
Click to collapse
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
I don't think you can do anything to the SuperSU configuration to make it so apps in priv-app have to ask for SU permission. I have other apps in there and have never seen them ask and they are not in SuperSU log either.
I moved my Greenify apk into priv-app because it wasn't clear to me that there was nothing to gain by doing that as I already had Xposed installed and working. Have since moved it back to original folder in /data/app/.
Davey126 said:
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
Click to expand...
Click to collapse
- Android 6.0.1
- SuperSU 2.78 (systemless root)
- Xposed
- latest Greenify Beta from PlayStore (in Root+Boost mode)
- NOT installed as system app or anything.
Same problem here -- Greenify never asks for root, is not listed in SuperSU logs. Greenify initially had root access iirc, but one of the updates from PlayStore removed it.
Nevertheless Greenify seems to be working fine though.
EDIT: All other root apps on my phone (OnePlus 2, stock OxygenOS 3.1) don't have any issues with root access.
Sent from my OnePlus 2 using Tapatalk

Latest Magisk beta resolves SafetyNet on stock ROM

Hello guys!
If you update to the latest Magisk version (v16.4), you will notice that it will now pass SafetyNet check.
Check attached screenshots!
rzarectha said:
Hello guys!
If you update to the latest Magisk version (v16.4), you will notice that it will now pass SafetyNet check.
Check attached screenshots!
Click to expand...
Click to collapse
Thats nice to know. I mean i havent used magisk yet (on previous phone it didnt work at all). Currently still on supersu. But its good to know that it works again, so i might switch in the future.
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
GodOfPsychos said:
Thats nice to know. I mean i havent used magisk yet (on previous phone it didnt work at all). Currently still on supersu. But its good to know that it works again, so i might switch in the future.
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
Click to expand...
Click to collapse
I think it's just as good as SuperSU in handling root apps. The way Magisk stands out though is the modules. I would recommend that you install only the magisk manager (it does not mess with anything in your phone if you just install it), and browse through the list of modules it has. It's very similar to the way modules in xposed look like. Maybe you can find some interesting functionality in there.
I am using the greenify module (works much like boost mode on xposed), busybox, adblocker, systemiser (turns user apps in sys apps), debloater (completely uninstall user apps). There's a ton of mods though, I don't even understand what most actually do.
Keep in mind that having xposed installed will break safetynet no matter what. Magisk can't hide it.
rzarectha said:
I think it's just as good as SuperSU in handling root apps. The way Magisk stands out though is the modules. I would recommend that you install only the magisk manager (it does not mess with anything in your phone if you just install it), and browse through the list of modules it has. It's very similar to the way modules in xposed look like. Maybe you can find some interesting functionality in there.
I am using the greenify module (works much like boost mode on xposed), busybox, adblocker, systemiser (turns user apps in sys apps), debloater (completely uninstall user apps). There's a ton of mods though, I don't even understand what most actually do.
Keep in mind that having xposed installed will break safetynet no matter what. Magisk can't hide it.
Click to expand...
Click to collapse
Edit: i moved this issue to the Q&A and help section since more issues keep coming
https://forum.xda-developers.com/axon-7/help/finally-decided-to-switch-supersu-to-t3787201
just switched to latest stock rom (1.2.0 B10) and installed magisk (16.4). it works and safetynet passes. the problem i got now is that the greenify module fails to install in magisk (see screenshot)
do i gotta flash the module through TWRP maybe? still a newbie to magisk since the axon 7 is the first phone to have it working
EDIT: for some reason magisk doesn't remember which apps have requested root after a reboot. everytime i reboot i get a prompt to allow root access to all my root apps (like greenify). idk why this is happening. i mean, root itself is working as it should. i already uninstalled bloatware and disabled/freezed things like the powermanagement
I'm interested in knowing where Magisk is at

Question [CLOSED] How to install Viper4Android

As the title says, is it possible.and how to successfully install Viper4Android to Renoir, running MIUI 12.5+, A11 - assuming that the phone is already rooted by Magisk
Or at least, how to successfully install JanesDSP
If you have already Magisk and rooted your phone, you can install the module of Viper with it.
Thoiareg said:
If you have already Magisk and rooted your phone, you can install the module of Viper with it.
Click to expand...
Click to collapse
Did you try and does it really work for you?
I've posted to Viper4Android thread with more details - Viper4Android apk can never find drivers:
- It asks to install drivers and to reboot
- After rebooting and reopening, Viper4Android apk again does not find drivers and asks to install and to reboot
- It can go endlessly
I tried with AML, by debloating' MusixFM, no avail
---
Similarly, I tried but cannot properly install JamesDSP
It's app always crashes, with exception saying that it cannot find drivers
Reported also to JamesDSP thread
---
In both threads there are several other users with the new A11 phones who report the same problems (cannot install Viper4Android, neither JamesDSP)
Frankly, I don't have Renoir - I have Lisa (Xiaomi 11 Lite 5G NE), with MIUI 12.5.8, A11.
Still, I wanted to ask if somebody with the similar Renoir (Mi 11 Lite 5G) succeeded to install V4A or JamesDSP?
zgfg said:
Did you try and does it really work for you?
I've posted to Viper4Android thread with more details - Viper4Android apk can never find drivers:
- It asks to install drivers and to reboot
- After rebooting and reopening, Viper4Android apk again does not find drivers and asks to install and to reboot
- It can go endlessly
(...)
Click to expand...
Click to collapse
The magisk module is not a apk. It't a zip file.
Best Magisk modules
Looking for some of the best Magisk modules for modding? We’ve got all the information you need to get started right here. Read on!
www.xda-developers.com
Thoiareg said:
The magisk module is not a apk. It't a zip file.
Best Magisk modules
Looking for some of the best Magisk modules for modding? We’ve got all the information you need to get started right here. Read on!
www.xda-developers.com
Click to expand...
Click to collapse
Sorry, I'm 5 years user of V4A, used successfully on 5 phones so far - I perfectly know what is Magisk, Magisk modules, V4A module, how it installs, etc
I'm talking about the Viper4Android application that installs with the module and serves for managing presets, kernels, etc
If you have practical advice how to install to the new MIUI release.(that you can prove that it works), fine - otherwise please let's stop wasting the time
Good night
zgfg said:
Sorry, I'm 5 years user of V4A, used successfully on 5 phones so far - I perfectly know what is Magisk, Magisk modules, V4A module, how it installs, etc
I'm talking about the Viper4Android application that installs with the module and serves for managing presets, kernels, etc
If you have practical advice how to install to the new MIUI release.(that you can prove that it works), fine - otherwise please let's stop wasting the time
Good night
Click to expand...
Click to collapse
Sorry, but I don't know you.
So, I answer according to the information you give in your message.
You have a problem installing Viper, I suggest you install it via Magisk. And you answer by talking about an apk file. So your answers don't make sense.
Now be nicer to people who respond to you and try to help you.
Good luck in your problem.
Solved by temporarily disabling USNF 2.2.1 - then JamesDSP installed correctly.
Later I re-enabled USNF and now both modules work correctly
Still I wasn't able to make V4A working
Anyway, closing the thread
THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Forum Moderator

Categories

Resources