Is this possible? https://www.xda-developers.com/camera2api-magisk-module-enables/
I think I read somewhere that Sony implemented their own modified version of Camera2API thus preventing other apps from using it.
Don't think this would work as a simple build.prop edit would've the same effect.
Already tried that module and nope, doesn't work.
Related
I recently downloaded an app called "Island" from the google play store and stumpled across this problem:
"The security policy prevents the creation of a work profile because a Custom OS has been installed on this device.
I have a Samsung Galaxy S7 (7.0)
Rooted with Unofficial Xposed Framework (by PurifyOS)
Also have Superkernel v2.70 installed.
Is there a way to bypass this using an Xposed module or other rooted applications?
You can try xTouchWiz Xposed module which has a function to fake the system status as Official instead of Custom under the security hacks section.
Alternatively you can use Magisk which should hide everything but Xposed from apps.
What worked for me was connecting the device to wifi or putting in an activated sim card before doing the work profile setup process.
Same problem here (S9 Soldier Rom), did someone made it work?
No one yet?
Has anyone gotten this to work?
Beanvee7 said:
You can try xTouchWiz Xposed module which has a function to fake the system status as Official instead of Custom under the security hacks section.
Alternatively you can use Magisk which should hide everything but Xposed from apps.
Click to expand...
Click to collapse
I don't have Xposed but I recently rooted with Magisk. And MagiskHide is not working for this. Do we have to hide system apps as well? I actually get this error when I add my Gsuite work account.
Tried many apps but none is working with stock rom with root. I know gravitybox can do it but I don't want to install xposed framework just for this...
Thank you for the tips in advance.
Custom rom is also no option?
We offer that feature. You could also just lower the brightness/set different steps for the different light sensor values.
j to the 4n said:
Custom rom is also no option?
We offer that feature. You could also just lower the brightness/set different steps for the different light sensor values.
Click to expand...
Click to collapse
Sorry I didn't mention I have to use stock rom due to the fingerprint payment issue.
I just thought if there's a simple way to turn the light off by editing a system file
Tried echo "0" > /sys/class/leds/indicator/bln but no luck.
jwong.hhf said:
Sorry I didn't mention I have to use stock rom due to the fingerprint payment issue.
I just thought if there's a simple way to turn the light off by editing a system file
Tried echo "0" > /sys/class/leds/indicator/bln but no luck.
Click to expand...
Click to collapse
Fingerprint payment issue? What would a custom rom change? I mean you are rooted already, so I assume you are using Magisk to bypass safetynet.
That will also work on a custom rom.
If your if a carrier specific billing you can use the Magisk Module version of our rom. It is a 180MB magisk module that you can disable anytime to return back to stock.
Else you could edit framework-res to turn off the button lights, should need an edit in services.jar too to bypass signature check ...and make it an magisk module.
j to the 4n said:
Fingerprint payment issue? What would a custom rom change? I mean you are rooted already, so I assume you are using Magisk to bypass safetynet.
That will also work on a custom rom.
If your if a carrier specific billing you can use the Magisk Module version of our rom. It is a 180MB magisk module that you can disable anytime to return back to stock.
Else you could edit framework-res to turn off the button lights, should need an edit in services.jar too to bypass signature check ...and make it an magisk module.
Click to expand...
Click to collapse
Only Chinese stock rom support two major fingerprint payment apps in China. So I have to stick to stock rom. Sad...
Had anybody figured it how to hide BusyBox from SPay so that we can still use it? I really want to install some custom profiles on my pixel, but SPay is more important. We can hide root, that i know, but not sure about BusyBox.
I've been searching for how to trick Pay as well. It's detecting root. I'm running a HTC U11 with LeeDroid Oreo rom and Magisk 15. Every Sammy app is Magisk Hidden and the magisk app has been renamed. It passes safely net. Busybox is fully masked from any app, so I'm not sure what the hangup is. I did a search but only found lots of notes about the csc (not an issue in the US?).
I'll do the reading if there is a search string I'm missing. Thanks!
jimbob_sf said:
I've been searching for how to trick Pay as well. It's detecting root. I'm running a HTC U11 with LeeDroid Oreo rom and Magisk 15. Every Sammy app is Magisk Hidden and the magisk app has been renamed. It passes safely net. Busybox is fully masked from any app, so I'm not sure what the hangup is. I did a search but only found lots of notes about the csc (not an issue in the US?).
I'll do the reading if there is a search string I'm missing. Thanks!
Click to expand...
Click to collapse
Reading a thread where it says to try and hide root/BusyBox from any other app the targeted one calls on. For example: hide from camera since SPay has permission to use the camera.
https://forum.xda-developers.com/showpost.php?p=73145987&postcount=4
Would you be up for trying any of these solutions and posting your findings?
Yeah this is a big issue I'm facing as well and I'm really curious as to why certain ROMs have no issues and others are seemingly impervious to the methods used to hide root from SPay.
If anyone has any insight into how to get this to work please share so that we can all benefit.
I'm us a US Unlocked HTC U11 with LeeDroid's rom. Release R114 now works with SPay. Remnants of Busybox were in a key path and all kinds of apps weren't working (SPay, WeMo...). With this release, Magisk hide allows SPay to work just fine without any crazy tricks. I hope this helps someone.
I don't know if there's an app that will search any rom for busybox, but it would certainly help those of us with a Sammy watch.
What are you using Busy Box for, out of curiosity..?
Sent from my Pixel 2 XL using Tapatalk
Some Aroma mods use BusyBox and so do some versions of V4A. Xposed uses it too.
Edit: currently using Magisk w/ BusyBox installed on BenzoRom and SPay still works.
I am using EdXposed, and have tried all the DisableFlagSecure modules, and also used Smali to add a module to Magisk to achieve the same result. None of it works.
I am using a Pixel 3 with Android Pie. I do not really want to update to 10 because then I won't be able to write to the system folder if I ever want to.
Am I missing something easy? Other modules in EdXposed and Magisk work OK, and I have a feeling this module is doing what is supposed to do, but there is something that is keeping it from triggering.
I'm working on porting "CIT test" application from MIUI to custom Android 11 ROMs (for calibrating proximity and fingerprint sensors), with end goal of creating a Magisk module. I'm stuck now with the application calling android.os.ServiceManager/addService, which fails with SecurityException -- I presume because I removed android:sharedUserId="android.uid.system" from its manifest, so it doesn't run with system app permissions. Currently I place it in /system/priv-app instead, which allows me to give it at least all the manifest permissions that it requires.
AFAIU, there is no way for me to simply use android.uid.system, as it requires one to sign the package with the same keys that were used for the ROM itself. As my idea is to have a general Magisk module, this is out of the question. However, because obviously I expect devices to be rooted (and can require Xposed), I want to find some way of circumventing signature check for this one package. Say, using Xposed to patch signature check, and to allow my public key to be used for android.uid.system apps. I don't want to completely disable signature checks, as this greatly compromises security.
I also thought of somehow using su to run this application as root, but apparently this is also not possible.
Is there a way to do this or something similar? Maybe I miss another way of implementing what I want? Any help or links are greatly appreciated.
I am curious about this too. It would help install the nReal nebula service on non-carrier devices and use nRreal Light AR glasses with the Nebula app.
Re-add the android.uid.system line
disable your Android Signature Verification
install with magisk to /system/app or priv-app