Question SmartView issue with Root - Samsung Galaxy S22 Ultra

Smart View does not connect after rooting One UI 5. I did the old trick of adding (wlan.wfd.hdcp=disable) to build.prob, but it did not help..
I would appreciate any support…

@dr.ketan
Your help is highly appreciated please…
Thanks in advance

Resolved… Thank you all
I used tasker run shell command:
setprop wlan.wfd.hdcp disable
And it worked

How did you try first to set wlan.wfd.hdcp=disable?
So which way did not work?

ZXR said:
How did you try first to set wlan.wfd.hdcp=disable?
So which way did not work?
Click to expand...
Click to collapse
I added wlan.wfd.hdcp=disable to build.prop using magisk

I am on UI5 now and setting wlan.wfd.hdcp=disable with MagiskHide Props Config (v6.1.2) did work.

Related

[Mod-Request] HAL1/HAL3 Swichter

Hi,
I saw now days few ROM has HAL switch. Which is fantastic to use any camera apps in our favourite ROM.
As that feature is not available in all ROM and if i want to try a ROM which has good battery life or good performance but that ROM lacks with that HAL switch feature, so i can't use my favourite cam app there.
Can anyone please make a TWRP flashable zip for
"HAL swichter - switch between hal1 and hal3"
So i can use or anyone can use Oxygen OS port Cam with Google Camera or Sultan's cam.
Thanks & Regards,
Normas Interruptor said:
Hi,
I saw now days few ROM has HAL switch. Which is fantastic to use any camera apps in our favourite ROM.
As that feature is not available in all ROM and if i want to try a ROM which has good battery life or good performance but that ROM lacks with that HAL switch feature, so i can't use my favourite cam app there.
Can anyone please make a TWRP flashable zip for
"HAL swichter - switch between hal1 and hal3"
So i can use or anyone can use Oxygen OS port Cam with Google Camera or Sultan's cam.
Thanks & Regards,
Click to expand...
Click to collapse
its just a shell command. do it in terminal. make a .txt right down the command to remember it, open shell execute it.
app ? heh..... make 2 .sh scripts. one with each command. Thats easy for the most amateur user.
For a more advanced user make a .sh script with an if command to getprop and if = {command1} true -> then {command2}.
Then this script in sd, link it on homescreen and single press it to execute. Voila. Here is your app.
kessaras said:
its just a shell command. do it in terminal. make a .txt right down the command to remember it, open shell execute it.
app ? heh..... make 2 .sh scripts. one with each command. Thats easy for the most amateur user.
For a more advanced user make a .sh script with an if command to getprop and if = {command1} true -> then {command2}.
Then this script in sd, link it on homescreen and single press it to execute. Voila. Here is your app.
Click to expand...
Click to collapse
Well, thank you for your reply ?.
But I'm kind of noob here who don't know how to make that script or .sh script. That's why i asked to someone to make a flashable zip so i can flash this via TWRP recovery and after that I don't need to do anything with emulator or other step.
Normas Interruptor said:
Well, thank you for your reply .
But I'm kind of noob here who don't know how to make that script or .sh script. That's why i asked to someone to make a flashable zip so i can flash this via TWRP recovery and after that I don't need to do anything with emulator or other step.
Click to expand...
Click to collapse
ok, but
i don't think anyone is interested in this.
for example me. i don't care changing hals to use different camera apps.
but the idea of how to do it is just like i said in the previous post. so someone that uses it and has a few script knowledge will do it
kessaras said:
ok, but
i don't think anyone is interested in this.
for example me. i don't care changing hals to use different camera apps.
but the idea of how to do it is just like i said in the previous post. so someone that uses it and has a few script knowledge will do it
Click to expand...
Click to collapse
I hope so
setprop presist.camera.HAL3.enabled=1
cpt.macp said:
setprop presist.camera.HAL3.enabled=1
Click to expand...
Click to collapse
Where i need to do that?
Please elaborate the full steps... As I'm using RR ROM unofficial by "niceash_soni"
Deleted
Normas Interruptor said:
Where i need to do that?
Please elaborate the full steps... As I'm using RR ROM unofficial by "niceash_soni"
Click to expand...
Click to collapse
Still haven't solved it ?
You just need to make a .sh script with just 2 if commands.
One will check for hal1 and one will check for hal3.
You don't need app and it's boring to open terminal and write a whole line every time you need to toggle that.
Try it and if you can't do it I'll write it for you when I'm back.
Or simply make 2 scripts with the setprop commands if you can't make it with the if command to check.
Tapping one script will do hal1=0 and hal3=1.
Tapping the other will do hal1=1 and hal3=0.
kessaras said:
Still haven't solved it ?
You just need to make a .sh script with just 2 if commands.
One will check for hal1 and one will check for hal3.
You don't need app and it's boring to open terminal and write a whole line every time you need to toggle that.
Try it and if you can't do it I'll write it for you when I'm back.
Click to expand...
Click to collapse
Thank you for your reply.
I'm noob bro.
I don't know how to do it...
If you can write down all the steps so i can try with it but with the above short note I can't understand what I need to do with script.
Please make a flashable zip if you can or any best thing.
Regards,
Normas Interruptor said:
Thank you for your reply.
I'm noob bro.
I don't know how to do it...
If you can write down all the steps so i can try with it but with the above short note I can't understand what I need to do with script.
Please make a flashable zip if you can or any best thing.
Regards,
Click to expand...
Click to collapse
pfffffffffffffffffff why nobody answers to him ?
2 scripts. +install app from play store to press and execute them.
Code:
#!/system/bin/sh
#Enable HAL3
setprop persist.camera.HAL1.enabled=0
setprop persist.camera.HAL3.enabled=1
echo "HAL3 Enabled"
Code:
#!/system/bin/sh
#Enable HAL1
setprop persist.camera.HAL3.enabled=0
setprop persist.camera.HAL1.enabled=1
echo "HAL1 Enabled"
Otherwise use if to check prop. getprop ........... > x if x=1 then ............
Use the 1st way for now. Going to bed cause im drunk xD
kessaras said:
pfffffffffffffffffff why nobody answers to him ?
2 scripts. +install app from play store to press and execute them.
Otherwise use if to check prop. getprop ........... > x if x=1 then ............
Use the 1st way for now. Going to bed cause im drunk xD
Click to expand...
Click to collapse
Thank you for your time.
But still I don't know how to use this ?...
Need more guidance.
Normas Interruptor said:
Thank you for your time.
But still I don't know how to use this ...
Need more guidance.
Click to expand...
Click to collapse
decompress at sdcard. search google , find app to easy press execute scripts, link scripts to homescreen , thats it.
Use local terminal for those command with root access , don't expect spoon feeding , use Google.
kessaras said:
pfffffffffffffffffff why nobody answers to him ?
2 scripts. +install app from play store to press and execute them.
Otherwise use if to check prop. getprop ........... > x if x=1 then ............
Use the 1st way for now. Going to bed cause im drunk xD
Click to expand...
Click to collapse
Here is my build.prop file... Can you please tell me which code do i need to use?
Or
If it is possible to you? Can you please add these codes in that build.prop file and share with me?
https://drive.google.com/file/d/0B5c0qxNUWHOkcFBYSmNpaE1xSFU/view?usp=drivesdk
Thanks
Normas Interruptor said:
Here is my build.prop file... Can you please tell me which code do i need to use?
Or
If it is possible to you? Can you please add these codes in that build.prop file and share with me?
https://drive.google.com/file/d/0B5c0qxNUWHOkcFBYSmNpaE1xSFU/view?usp=drivesdk
Thanks
Click to expand...
Click to collapse
its not a prop in build.prop. its a prop in the kernel, at another file, depending the kernel.
i think it was missing su permission. try those with an app that can execute scripts.
kessaras said:
its not a prop in build.prop. its a prop in the kernel, at another file, depending the kernel.
i think it was missing su permission. try those with an app that can execute scripts.
Click to expand...
Click to collapse
So, i have to flash the attached your Camera HAL zip that's it. Right?
Normas Interruptor said:
So, i have to flash the attached your Camera HAL zip that's it. Right?
Click to expand...
Click to collapse
No... In there , there are only 2 scripts. Want to enable hal1 ? You tap execute the hal1 script. Want to enable hal3? Execute hal3 script.
I didn't make any app or module.
But if this goes on for long I will make it.
I believe soon the maintainers will do something about that because many people ask for this now. If they don't do it, I'll do it in the end even if I don't care about hal -_-
Anyway. Search Google play for app that can execute scripts on tap and you are good with those 2 scripts for now. Easy tap the one you want.
kessaras said:
No... In there , there are only 2 scripts. Want to enable hal1 ? You tap execute the hal1 script. Want to enable hal3? Execute hal3 script.
I didn't make any app or module.
But if this goes on for long I will make it.
I believe soon the maintainers will do something about that because many people ask for this now. If they don't do it, I'll do it in the end even if I don't care about hal -_-
Anyway. Search Google play for app that can execute scripts on tap and you are good with those 2 scripts for now. Easy tap the one you want.
Click to expand...
Click to collapse
Well, i have tried two script apps... Script manager and shscript... Can't understand how to make these two command executable on one touch... People are smart who actually know that how to do that, even i have tried to watching YT videos as well, so i can understand how to make those scripts executable... But no luck...
You are the only one who help me alot here...
Heartiest thanks to you.
------------------------------------------
Now closing this thread as I'm so dumb to understand these methods, i know that would be very easy one for those who know how to do that... That's why people calling me here "spoon feeding" and all...
Now going to switching from RR ROM unofficial build by "Niceash_soni" to APEX ROM, however I don't feel comfortable on that, because that ROM has EAS kernel, that is very laggy all the time to me (using OP3). Don't know the reason behind that. So i would have to use that ROM with EXkernel for custom ROM V12 (latest one).
Though i love the RR ROM by "Niceash_soni" but he will not adding these method and sometimes he was very rude to me as i have request him twice. It's okay as i can understand he could be frustrating with so many requests or repeated requests.
__________________
Thank buddy, helping me so much here.
Normas Interruptor said:
Well, i have tried two script apps... Script manager and shscript... Can't understand how to make these two command executable on one touch... People are smart who actually know that how to do that, even i have tried to watching YT videos as well, so i can understand how to make those scripts executable... But no luck...
You are the only one who help me alot here...
Heartiest thanks to you.
------------------------------------------
Now closing this thread as I'm so dumb to understand these methods, i know that would be very easy one for those who know how to do that... That's why people calling me here "spoon feeding" and all...
Now going to switching from RR ROM unofficial build by "Niceash_soni" to APEX ROM, however I don't feel comfortable on that, because that ROM has EAS kernel, that is very laggy all the time to me (using OP3). Don't know the reason behind that. So i would have to use that ROM with EXkernel for custom ROM V12 (latest one).
Though i love the RR ROM by "Niceash_soni" but he will not adding these method and sometimes he was very rude to me as i have request him twice. It's okay as i can understand he could be frustrating with so many requests or repeated requests.
__________________
Thank buddy, helping me so much here.
Click to expand...
Click to collapse
Other people also ask in other roms. It's the same in the official rr. No worries. Soon someone that needs it, will do something. Otherwise me or some other guy will do. Since more people ask for it , it will definitely come.
Don't close the thread. It seems it's only you but there are hundreds more hidden behind this
It's just that our free time is always little as we work for more than 8 hours. Sometimes 12 hours. Anyway. Leave it as it is . Soon a maintainer or a senior will do something.

Rooted Pixel 2 Hotspot -- "To enable, go to att.com/mywireless or dial 611."

Rooted Pixel 2 Hotspot -- "To enable, go to att.com/mywireless or dial 611."
Ex-squeeze me? You're a Pixel! You're not supposed to respect carrier crap!
Is there a good way to bypass this with root? All I have done so far is upgrade completely to the latest version of 8.1 and installed Magisk.
Thanks.
starkruzr said:
Ex-squeeze me? You're a Pixel! You're not supposed to respect carrier crap!
Is there a good way to bypass this with root? All I have done so far is upgrade completely to the latest version of 8.1 and installed Magisk.
Thanks.
Click to expand...
Click to collapse
in build.prop add line:
net.tethering.noprovisioning=true
build.prop is at root level/system
Probably you can put it anywhere in build.prop, but I put it just after the other "net" command.
Then you should be good to go. Type carefully. Not sure what would happen if you type an invalid command in build.prop.
tedr108 said:
in build.prop add line:
net.tethering.noprovisioning=true
build.prop is at root level/system
Probably you can put it anywhere in build.prop, but I put it just after the other "net" command.
Then you should be good to go. Type carefully. Not sure what would happen if you type an invalid command in build.prop.
Click to expand...
Click to collapse
Thanks for this
starkruzr said:
Thanks for this
Click to expand...
Click to collapse
Did that solution work? I'm contemplating buying a Pixel 2 but want to make sure the hotspot feature works. I'm on the original Verizon unlimited and still want to be able to hotspot.

Call recording

Can anyone confirm that this 9.0 pie update breaks all call recording app from the play store. Thanks for your feedback.
Updated to Android 9 today and boldbeast no longer works, it will record my voice but not that of the call )-: I am considering root now to get the feature back as i did find it useful.
Update: found this on the play store https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en_GB
Its all working fine now as it enables the oneplus6 built in recorder.
Thanks
But that also means that it wouldn't work without root like myself. Right?
Guess I gotta stick with my 8.1 until someone figures this one out. This one feature is like super important to me atm.
Thanks again for your kind reply.
Hi,
No root required, my phone is standard no unlocked bootloader and no root.
You just need to install the software, then enable developer options on your phone, enable usb debbugging and send the following command to your phone. adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
Then you will have the option in the software (joneplustool) to enable call recording and also restore calling recorder at boot.
Then on the phone dialler , go into settings and enable call record.
xtruss said:
restore calling recorder at boot.
Click to expand...
Click to collapse
That's a bummer...
But hey, thanks a lot for your kind reply. And as for myself, I've been using Cherinbo, pretty decent I would say.
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
vibo2013 said:
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
Click to expand...
Click to collapse
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
You seem as though you just want to promote a product to me, and one that doesn't work.
Darkest shades said:
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
Click to expand...
Click to collapse
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
xtruss said:
You seem as though you just want to promote a product to me, and one that doesn't work.
Click to expand...
Click to collapse
Lol, not my intention. But the one thing that I like about this one is that all saved, recorded files doesn't appear into my music player, where as for others, they always does. Thanks for confirming that it doesn't work.
vibo2013 said:
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
Click to expand...
Click to collapse
It's ok, you help a lot already.
Thanks for your help guys.
I am very happy with the built in call recorder. What is the benefit of having a third party app to record calls?
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Void
---------- Post added at 02:57 AM ---------- Previous post was at 02:49 AM ----------
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
dgunn said:
Void
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
"adb shell settings put global op_voice_recording_supported_by_mcc 1"
It enables the default, native Call Recorder found on op6 and op5 and I really like it. It recorded all my today's calls ranging from 625KB to 2.29MB all good quality(aac files)
eliaspizarro said:
Requeriments:
root
terminal with su permisions
Manual steps
Method 1 (works until reboot):
Create a file ex. incall.sh:
Code:
#!system/bin/sh
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
execute from terminal: $ sh incall.sh
Method 2 (works until reboot):
with adb: > adb shell "settings put global op_voice_recording_supported_by_mcc 1"
My steps (permanent):
Install termux (add su permisions)
in termux: $ termux-setup-storage
Install termux boot
create folder un termux home path (default) named: .termux
in termux: $ ln -s /storage/emulated/0/<your boot script folder> ~/.termux/boot
create script in /storage/emulated/0/<your boot script folder>
Code:
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
exit
reboot
Click to expand...
Click to collapse
..
This is what I'm getting
sh: $: not found
Just by telling us to install this and add home path here..... We need instructions
---------- Post added at 06:26 PM ---------- Previous post was at 06:04 PM ----------
and again
sh: adb: not found
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
You can also use Tasker to enable native call recording (provided you've granted WRITE_SECURE_SETTINGS permission to Tasker).
It seems the system deactivates jOnePlus from activating call recorder after 8 hours. Anyway to make it a permanent activation?
Even after removing jOnePlus from the battery optimize list, the call recorder still gets deactivated after a couple of hours.
obislu said:
mzsquared said:
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
I took the official OTA Pie upgrade and enabled the recorder with adb command after that. I'm not planning to root my phone, at least not yet. I'm enjoying the Pie Rom as is. It's all good, actually great with the night mode, there is no bloat. I disabled few apps, mainly from google and that's that. I remember times when rooting was an important necessity, I've had a Motorola Defy XT, long time ago, with 1GB RAM and no space for any extra apps, rooting was mainly used for getting the bloat out and moving apps to SD card by way of creating ext4 partition.
My OP6 has 256GB storage space, 8GB RAM and I just don't feel like constantly reloading the system, chasing newest twrps and Magisk versions, softbricking etc,etc.. and having my phone 'off line' for hours while I'm fixing it.
Click to expand...
Click to collapse

[HELP] How to alter build.prop? Magisk Rooted

So I have my 930-F S7 systemless rooted with Magisk and with encryption.
I noticed that after rooting I wasn't able to use SmartView on my TV anymore, I've tried lots of things but eventually came to a proposed solution of editing build.prop and adding the following line to the end of it and it should work:
wlan.wfd.hdcp = disable
Click to expand...
Click to collapse
Unfortunately when trying to alter build.prop there was always an error saying it was read only, after a quick research it seems it's because it's a systemless root, so I should try doing it directly with Magisk.
Found myself to a helpful thread, that told me to put the above command line into a blank .txt and paste it into:
/sbin/.core/img/.core/post-fs-data.d
Click to expand...
Click to collapse
But it failed, I wasn't able to paste the file.
So I don't know what to do, has anyone faced this issue and can help me?
I was able to fix this issue and FINALLY be able to Smart View / Screen Mirror to other devices.
To do so I installed Didgeridoohan's MagiskHide Props Config Module. Installed a Terminal Emulator and proceeded to include the line mentioned on my previous post to build.prop.
After that, voila it was finally fixed.
Done.
The line is already present in my custom Rom. The problem is elsewhere.
CyberBeaR said:
I was able to fix this issue and FINALLY be able to Smart View / Screen Mirror to other devices.
To do so I installed Didgeridoohan's MagiskHide Props Config Module. Installed a Terminal Emulator and proceeded to include the line mentioned on my previous post to build.prop.
After that, voila it was finally fixed.
Click to expand...
Click to collapse
can please tell me the steps how did u you do tha
please
thanks.

Unable to set selinux permissive

I'm using rmx3171_c06 stock rom.
i want to use viper4android which requires selinux permissive.
but when i flashed a module which makes phone permissive it automatically backs to enforcing ,help!!
May be the reason is that the module will not work because phone's kernel is compiled with always enforcing config, e.g., stock Samsung kernels.
is any other option?? like customise the kernel
san.v90 said:
I'm using rmx3171_c06 stock rom.
i want to use viper4android which requires selinux permissive.
but when i flashed a module which makes phone permissive it automatically backs to enforcing ,help!!
Click to expand...
Click to collapse
It's an old app but have you tried the Selinux Switch app? I was the tester for that app when it was made. It worked well at the time, the app hasn't been updated in a while so I'm not sure how well it still works.
i just use "setenforce 0" to make it Permissive.
This is a temporary solution, doesn't survive a reboot.
xXx yYy said:
This is a temporary solution, doesn't survive a reboot.
Click to expand...
Click to collapse
Yeah i know. Forgot to mention it.
Canny1913 said:
Yeah i know. Forgot to mention it.
Click to expand...
Click to collapse
xXx yYy said:
This is a temporary solution, doesn't survive a reboot.
Click to expand...
Click to collapse
Selinux Switch app has a setting to persist through reboot. All that is required is root and a kernel that supports permissive mode.
Or, a script can be created to automatically run the setenforce 0 command during reboot.
You must not tell me what I already know.
xXx yYy said:
You must not tell me what I already know.
Click to expand...
Click to collapse
That wasn't directed at anyone specific, hence, the multi-quote, no need to quote the OP as well as they would get notification for all comments. Additional information for anyone reading the thread since it wasn't stated by anyone else in previous comments to the thread.
san.v90 said:
is any other option?? like customise the kernel
Click to expand...
Click to collapse
Change the SELINUX value to SELINUX=permissive and/or SELINUX=disabled in the file /etc/selinux/config - requires phone is rooted and partition /etc is mounted as RW.
xXx yYy said:
Change the SELINUX value to SELINUX=permissive and/or SELINUX=disabled in the file /etc/selinux/config - requires phone is rooted and partition /etc is mounted as RW.
Click to expand...
Click to collapse
Sorry sir, but there is no file like /etc/selinux/config
-plz suggest another trick
Droidriven said:
It's an old app but have you tried the Selinux Switch app? I was the tester for that app when it was made. It worked well at the time, the app hasn't been updated in a while so I'm not sure how well it still works.
Click to expand...
Click to collapse
Yes i have tried but still nothing happening
i think it's impossible in this device
san.v90 said:
Sorry sir, but there is no file like /etc/selinux/config
-plz suggest another trick
Click to expand...
Click to collapse
Was my fault: path to SELinux policy file should be /system/etc/selinux/config
xXx yYy said:
Was my fault: path to SELinux policy file should be /system/etc/selinux/config
Click to expand...
Click to collapse
still can't find any config file
Its not in system its in boot
I am having the same problem, I tried all possibilities
I am using the Umidigi A13 Pro Max 5G on Android 12.
I think it is to do with Android 12 security that is preventing
Selinux from going permissive.
None of the old methods work with it now.
Yes there is no config file in the selinux directory.
I don't really know what to do, Viper will only
work with permissive mode.
Any ideas guys !!!!
ScarletWizard said:
Did u try thr repackaged version?
Click to expand...
Click to collapse
Thank you very much for getting back
Yes I did and also installed the
Audio Modification Library
Still no joy
I am very familiar with this as I used to
have issues with the Umidigi F2 and I
managed to sort that out
I think that the issue here is with
Android 12 security
None of the existing solutions
works with it
I even tried terminal commands
like getenforce and setenforce
and sestatus to temporarily
change selinux mode to permissive
Unfortunately some Mods like
viber4android will only work
when selinux is in permissive mode
that's a job for viber4android maintainer, but you can try yourself. just needs patience.
https://forum.xda-developers.com/t/4534599
I think that it's not a good idea to run in permissive mode.
You've got a jillion apps on your device that are just waiting to do stuff if you turn enforce off.
In any case...
When I want to make permanent permissive I just mod the kernel.
In my experience, the kernel starts out permissive then turns on enforce at some point.
Easey-peasy, just dump the kallsyms, get the address of sel_write_enforce.
In A64 just replace the two first instructions:
Code:
d2800000 mov x0, #0x0
d65f03c0 ret

Categories

Resources