i noticed that xz has support of kcal module.
but it pops error because of selinux enforceing.
is there method to change this? i can't find sepolicy in my phone.
thanks.
WanderMax said:
i noticed that xz has support of kcal module.
but it pops error because of selinux enforceing.
is there method to change this? i can't find sepolicy in my phone.
thanks.
Click to expand...
Click to collapse
A little info would be helpful, like is your device rooted?
lilbrat said:
A little info would be helpful, like is your device rooted?
Click to expand...
Click to collapse
rooted, rwrp installed, 7.11fw
WanderMax said:
rooted, rwrp installed, 7.11fw
Click to expand...
Click to collapse
If you using magisk as your root method, there is a module you can use, Magisk Selinux Manager.
Also have a look here.. https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
from twrp
flash this module!
it will change the SElinux to Permissive! (Yes/NO)
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042
and try the KCAL
Related
I am trying to get xprivacy working on my Oneplus One and I've tried a few things, but I cannot get past the bootscreen.
ROM: cm-12-20150211-UNOFFICIAL-sm-temasek-bacon-v7.5.1
Kernel: Boeffla-kernel-3.0-beta10-CM-bacon-l474-2015-02-08-152937.CWM
I extracted the boot.img from the Boeffla kernel, unpacked it, modified the \rmdisk\service_contexts with geany and appended it with
Code:
xprivacy453 u:object_r:system_server_service:s0
repacked it, and flashed it with flashify.
When booting, it gets stuck on the bootscreen; Where it normally says Powered by ANDROID, it only shows "Powered" of which only the top half gets printed before seizing.
I can hard reset it, go back into twrp, and restore just the boot partition and get it back up.
What am I doing wrong?
bump
As I know XPrivacy doesn't work with Lollipop?
soralz said:
As I know XPrivacy doesn't work with Lollipop?
Click to expand...
Click to collapse
It does if you u modify the boot.img or set the selinux to permissive or disabled.
I got it working now, but it required no modifications of boot.img
Went into twrp and made a backup
wiped the system and cache partitions
dirty flashed the latest Cm12 nightly
flashed AK.122.OPO.SKULL.CM12 kernel
flash Cm12 xposed alpha
rebooted
installed SeLinuxModeChanger app from the app market and changed it to permissive
rebooted phone
installed xprivacy
enabled it in xposed, launched it, and then rebooted
checked the xprivacy in xposed and it was working
ahb83 said:
I got it working now, but it required no modifications of boot.img
Went into twrp and made a backup
wiped the system and cache partitions
dirty flashed the latest Cm12 nightly
flashed AK.122.OPO.SKULL.CM12 kernel
flash Cm12 xposed alpha
rebooted
installed SeLinuxModeChanger app from the app market and changed it to permissive
rebooted phone
installed xprivacy
enabled it in xposed, launched it, and then rebooted
checked the xprivacy in xposed and it was working
Click to expand...
Click to collapse
This kernel AK122 has this in the notes "Audit Control for SeLinux on/off (Disabled by default)" This means that you got it working by finding a kernel with selinux as permissive. The app does not do anything.
mattrb said:
This kernel AK122 has this in the notes "Audit Control for SeLinux on/off (Disabled by default)" This means that you got it working by finding a kernel with selinux as permissive. The app does not do anything.
Click to expand...
Click to collapse
The status says enforcing without that app (I think it's still permessive because I couldn't activatie xprivacy without this ak kernel (only installed the kernel).
Thanks!
mattrb said:
This kernel AK122 has this in the notes "Audit Control for SeLinux on/off (Disabled by default)" This means that you got it working by finding a kernel with selinux as permissive. The app does not do anything.
Click to expand...
Click to collapse
Why is it that if I do a fresh install of Temasek with gapps and AK kernel it works fine, but when I install xprivacy.apk it bootloops?
Does the SeLinuxModeChanger app say that it is permissive on first run?
mattrb said:
Does the SeLinuxModeChanger app say that it is permissive on first run?
Click to expand...
Click to collapse
yes
mattrb said:
Does the SeLinuxModeChanger app say that it is permissive on first run?
Click to expand...
Click to collapse
Did it all over again and installed nothing except the framework and synapse. Set synapse to permissive and then rebooted; verified by going into about phone and SeLinux was at permissive. Installed xprivacy, activated it, and rebooted. Stuck in bootloop again
Seems to be a bug in xposed framework as noted by M66B.
https://github.com/M66B/XPrivacy/issues/2162
After updating to Magisk 17.1 where safety net check is supposed to be fixed I'm still receiving the same invalid response. Any ideas would be helpful.
Try to go settings and turn off Magisk hide and then on.
Only cts is failing in my case
No problem for me.
dgunn said:
After updating to Magisk 17.1 where safety net check is supposed to be fixed I'm still receiving the same invalid response. Any ideas would be helpful.
Click to expand...
Click to collapse
vjendra said:
Only cts is failing in my case
Click to expand...
Click to collapse
Flash the latest Uninstaller followed by 17.1 in twrp without any wipe. That should solve the problem :good:
Sent from my OnePlus6 using XDA Labs
Funk Wizard said:
Flash the latest Uninstaller followed by 17.1 in twrp without any wipe. That should solve the problem :good:
Click to expand...
Click to collapse
This worked but uninstalled all of my mods. Safety net check passed. So I installed the mods again and back to being invalid. Thank you for the fix lol but I broke it again i guess
dgunn said:
This worked but uninstalled all of my mods. Safety net check passed. So I installed the mods again and back to being invalid. Thank you for the fix lol but I broke it again i guess
Click to expand...
Click to collapse
There has been lot of reports for invalid cts, I guess wait for the next update
Sent from my OnePlus6 using XDA Labs
Funk Wizard said:
There has been lot of reports for invalid cts, I guess wait for the next update
Sent from my OnePlus6 using XDA Labs
Click to expand...
Click to collapse
Thank you will do. As long as everything works in not worried about it really. Just never seen it before and no one had an answer for 17.1.
i just updated the magisk manager and didn't update to 17.1 but after the check it says all good even with all modules installed so good to see its working again.
dgunn said:
After updating to Magisk 17.1 where safety net check is supposed to be fixed I'm still receiving the same invalid response. Any ideas would be helpful.
Click to expand...
Click to collapse
same problem here
i installed the manager first and it passed all checks and after a reboot i installed the 17.1 update and after reboot everything still passed so i can confirm its working.
Which OS is everyone using?
mykenyc said:
Which OS is everyone using?
Click to expand...
Click to collapse
5.1.1
Sent from my OnePlus6 using XDA Labs
There's no way for me to pass ctsprofile... I never used a custom rom, and today I flashed the open beta, then I flashed magisk uninstaller and then the 17.1 magisk. No way to pass ctsprofile for me...
Jack_Sparrow_ said:
There's no way for me to pass ctsprofile... I never used a custom rom, and today I flashed the open beta, then I flashed magisk uninstaller and then the 17.1 magisk. No way to pass ctsprofile for me...
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/guild-to-pass-safetynet-oxygen-android-t3838123
justen7723 said:
https://forum.xda-developers.com/oneplus-6/how-to/guild-to-pass-safetynet-oxygen-android-t3838123
Click to expand...
Click to collapse
Thanks, this worked!!!
dgunn said:
After updating to Magisk 17.1 where safety net check is supposed to be fixed I'm still receiving the same invalid response. Any ideas would be helpful.
Click to expand...
Click to collapse
Same here I've installed Magisks 17.1 on two different stock samsung devices now but can't pass both SafteyNet checks on either devise, installed Via:
magisks manager -> patched boot.img -> flashed patched boot image with Odin while under samsung download mode.
Ticked hide apps within Magisks but they just keep unticking themselves
Redundant. Delete
Deacon-Frost said:
Try to go settings and turn off Magisk hide and then on.
Click to expand...
Click to collapse
Turning off magisk hide results in CTS profile failure and basic Integrity failure. Changing the fingerprint as suggested in build prop did nothing and continued to give invalid response.
Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part
You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2
Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!
Next time don't be a twrp and use twrp
dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update
Here's what I did to get Viper working on Android 10 custom ROMs on Poco F1, I've looked at various methods from different sources and this finally worked for me.
Note that I'm not responsible for anything that happens to your device!
1. Reboot into recovery, flash v4a_rootless zip (drivers)
2. Flash Audio-Modification-Library in recovery
3. Reboot to system
4. Flash v4afx_2.7.1.0 in magisk
5. Change SELinux to permissive and reboot
Note that if your ROM is already permissive then it must work after step 4 and reboot
Tested on Havoc OS 3.0
Need SELinux enforcing? Try this: https://forum.xda-developers.com/showpost.php?p=81138825&postcount=16
It worked! I can't believe finally something worked! I can't thank you enough man!
Will this magisk module cause bootloop?
It worked for me too. Thanks so much
3arllscn said:
Will this magisk module cause bootloop?
Click to expand...
Click to collapse
Not if you followed the instructions prior to flashing it (manual drivers and aml from twrp)
viv29 said:
Here's what I did to get Viper working on Android 10 custom ROMs on Poco F1, I've looked at various methods from different sources and this finally worked for me.
Note that I'm not responsible for anything that happens to your device!
1. Reboot into recovery, flash v4a_rootless zip (drivers)
2. Flash Audio-Modification-Library in recovery
3. Reboot to system
4. Flash v4afx_2.7.1.0 in magisk
5. Change SELinux to permissive and reboot
Note that if your ROM is already permissive then it must work after step 4 and reboot
Tested on Havoc OS 3.0
Click to expand...
Click to collapse
How about Bluetooth headset?
viv29 said:
Not if you followed the instructions prior to flashing it (manual drivers and aml from twrp)
Click to expand...
Click to collapse
Thanks man it's 100% :working ?
faxel said:
How about Bluetooth headset?
Click to expand...
Click to collapse
Don't have one so can't check.
Viper and music players crash/hang when I have viper activated on bluetooth devices
tested on latest cRdroid 6.0
Not working
Sunemol said:
Not working
Click to expand...
Click to collapse
You need to connect to the internet. The installer downloads the latest apk, then the installation will continue.
---------- Post added at 08:00 AM ---------- Previous post was at 08:00 AM ----------
Works like a charm, thank you very much!!!!!
Sunemol said:
Not working
Click to expand...
Click to collapse
Viper installation in magisk needs internet connection
Edit: fixed after installing drivers zip again n removing audio mod from magisk.
But V4a stops working once u toggle on off button. U gotta stop the app and start it again to make it work with V4a ? if u toggle on button on V4a without fcing app it won't work
And what about Dolby Atmos there is any solution
abdohop said:
And what about Dolby Atmos there is any solution
Click to expand...
Click to collapse
haven't tried it myself yet.
I found another method which works with SELinux enforcing. Needs magisk installed.
1. Install the 2.7.1.0 viper apk from XDA Labs
2. Open the apk, grant it superuser access and press restart on the popup
3. Press power+volume up to go into recovery while it is restarting (dont let it restart, go into recovery instead)
4. Go to terminal in TWRP and navigate to /data/adb/modules/ViPER4AndroidFX by doing this:
cd /data/adb/modules/ViPER4AndroidFX
5. Now rename the post-fs-data.sh to something else like post-fs-data.sh.bak or delete it by doing this:
mv post-fs-data.sh post-fs-data.sh.bak
6. You're all done, restart into system now.
NOTE: Turning off master limiter and setting it back on doesnt work. It has to be on by default all the time (probably it enables at startup and cant be toggled)
If you encounter a bootloop delete ViPER4AndroidFX inside /data/adb/modules
rm -rf /data/adb/modules/ViPER4AndroidFX
For some reason, the above method is not working for me. On latest Havoc OS build 8/12/19. First time I follow the above steps Viper still gives a pop up saying drivers not installed. I click on install again, follow the same renaming method. Second time Viper opens but driver status is abnormal.
Anubhav997 said:
For some reason, the above method is not working for me. On latest Havoc OS build 8/12/19. First time I follow the above steps Viper still gives a pop up saying drivers not installed. I click on install again, follow the same renaming method. Second time Viper opens but driver status is abnormal.
Click to expand...
Click to collapse
Try changing selinux to permissive :/ looks like there's no other option for now :/
Anubhav997 said:
For some reason, the above method is not working for me. On latest Havoc OS build 8/12/19. First time I follow the above steps Viper still gives a pop up saying drivers not installed. I click on install again, follow the same renaming method. Second time Viper opens but driver status is abnormal.
Click to expand...
Click to collapse
Working for me OnePlus 3T and OnePlus 5 both with Newest Havoc Rom.
viv29 said:
Try changing selinux to permissive :/ looks like there's no other option for now :/
Click to expand...
Click to collapse
Yup this works. No doubt.
I guess I'll stay with android 9 for a while. Need SELinux enforcing and Viper also
Hey, I needed a little help. I was trying to get busybox installed so I can run Viper4Android. Downloaded the busybox installer from the market and went through the typical in-App installation. Went for the reboot and got into a bootloop.
So my question is... How do we get busybox for our G7 Power? What's the preferred method?
Thanks in advance!
Their is a module on magisk for it
DonSolo said:
Hey, I needed a little help. I was trying to get busybox installed so I can run Viper4Android. Downloaded the busybox installer from the market and went through the typical in-App installation. Went for the reboot and got into a bootloop.
So my question is... How do we get busybox for our G7 Power? What's the preferred method?
Thanks in advance!
Click to expand...
Click to collapse
BusyBox is not needed. I have Viper 4 Android running on CrDroid and just have Magisk installed. Magisk root has BusyBox working already in the background.
vi
Rondeau79 said:
BusyBox is not needed. I have Viper 4 Android running on CrDroid and just have Magisk installed. Magisk root has BusyBox working already in the background.
Click to expand...
Click to collapse
B__B said:
Their is a module on magisk for it
Click to expand...
Click to collapse
Every time I try to run Viper4Android without busybox it gives me errors about it not being installed. I'll try the magisk module and report my findings here. Thanks guys
This happens each time I try without magisk
Tried the magisk busybox module.... bootloop lol
DonSolo said:
This happens each time I try without magisk
Tried the magisk busybox module.... bootloop lol
Click to expand...
Click to collapse
im using this module without any issue on crdroid
vinoxflame said:
im using this module without any issue on crdroid
Click to expand...
Click to collapse
WTF lol
What version of Magisk are you running?
Ok so I got it to work... Turns out I was using the "HiFi" version... Tried the regular FX and it worked like a charm.
Thanks you guys! This is why XDA exist! I've been around for a very long time and this site never disappoints!!
If a Mod could close the thread that'd be cool... Problem solved here!