Hi,
I clicked by accident something in the superSU settings. No idea what I have changed. Could someone tell me the defaults and especially those from the security section?
Mine at the moment are:
Enable su during boot [ ]
Mount namespace seaparation [V]
Enable multi-user [ ]
Tapjacking protection [V]
Any other critical setting that someone should be aware of?
jcur said:
Hi,
I clicked by accident something in the superSU settings. No idea what I have changed. Could someone tell me the defaults and especially those from the security section?
Mine at the moment are:
Enable su during boot [ ]
Mount namespace seaparation [V]
Enable multi-user [ ]
Tapjacking protection [V]
Any other critical setting that someone should be aware of?
Click to expand...
Click to collapse
Enable SU during boot should be ticked...
Cheers
dirlan2001 said:
Enable SU during boot should be ticked...
Cheers
Click to expand...
Click to collapse
Thank you. Is that a recommended setting or a default one?
jcur said:
Thank you. Is that a recommended setting or a default one?
Click to expand...
Click to collapse
AFAIK it's always been on on my devices.... guess that means it's a default setting. And logically, if it's not ON, it's not usefull. Some settings or apps need to be kept under control at boot.
Cheers
dirlan2001 said:
AFAIK it's always been on on my devices.... guess that means it's a default setting. And logically, if it's not ON, it's not usefull. Some settings or apps need to be kept under control at boot.
Cheers
Click to expand...
Click to collapse
Thank you. I followed your advice and set it to ON.
jcur said:
Thank you. I followed your advice and set it to ON.
Click to expand...
Click to collapse
You're welcome
Related
I get a strange behaviour with CM's File manager.
Advanced access mode is disabled on VJ 4.2.2, 5.0
Any ideas how to enable it? (Tick box is disabled)
modestos said:
I get a strange behaviour with CM's File manager.
Advanced access mode is disabled on VJ 4.2.2, 5.0
Any ideas how to enable it? (Tick box is disabled)
Click to expand...
Click to collapse
In File manager -> Settings -> General Settings -> Access mode. Is this what you're talking about? I think its Safe mode by default, but I can change it.
Sent from my N90DC_S using xda app-developers app
Yes, but in my case it is disabled and thus non selectable.
modestos said:
Yes, but in my case it is disabled and thus non selectable.
Click to expand...
Click to collapse
Just a question for OP since I am having the same problem, do you have any apps or scripts installed to move data to the external SD card?
I used to be able to access the advanced mode and it is grayed out now, and I was thinking it may have stopped working once I enabled Mounts2SD.
I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)/
The main functionality i want is the ability to turn on/off:
Airplane mode
Location Completely (when screen off)
GPS when opening apps that use maps
Mobile data
Can anyone suggest the best way to get this functionality back if its possible?
farquea said:
I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)/
The main functionality i want is the ability to turn on/off:
Airplane mode
Location Completely (when screen off)
GPS when opening apps that use maps
Mobile data
Can anyone suggest the best way to get this functionality back if its possible?
Click to expand...
Click to collapse
You could try some of the run shell commands from this thread https://forum.xda-developers.com/u/tasker-tips-tricks/best-run-shell-commands-tasker-t3419204 or use the AutoTools plugin https://play.google.com/store/apps/details?id=com.joaomgcd.autotools
Majority (if not all) of Secure settings stuff is now easily available on AutoTools.
Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?
farquea said:
Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?
Click to expand...
Click to collapse
You're gonna have to run that command. It should work fine then.
farquea said:
Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?
Click to expand...
Click to collapse
What ADB command are you talking about?
farquea said:
I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)
Click to expand...
Click to collapse
I'm on Nougat as well and I'm using Secure Settings every day, it works fine for me...
The adb command worked but my bigger problem was that my phone had lost root. All fixed now tho
You can replace Secure Settings with SecureTask plugin. Free and it works great.
kitkat85 said:
You can replace Secure Settings with SecureTask plugin. Free and it works great.
Click to expand...
Click to collapse
Sounds great. Can you please provide a link? Thanks!
AJH101 said:
Sounds great. Can you please provide a link? Thanks!
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.balda.securetask
kitkat85 said:
https://play.google.com/store/apps/details?id=com.balda.securetask
Click to expand...
Click to collapse
Fantastic, thank you.
---------- Post added at 08:07 AM ---------- Previous post was at 07:25 AM ----------
kitkat85 said:
https://play.google.com/store/apps/details?id=com.balda.securetask
Click to expand...
Click to collapse
Forgive me, is this not very similar to the Auto Tools plug in? [emoji4]
AJH101 said:
Fantastic, thank you.
---------- Post added at 08:07 AM ---------- Previous post was at 07:25 AM ----------
Forgive me, is this not very similar to the Auto Tools plug in? [emoji4]
Click to expand...
Click to collapse
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.
kitkat85 said:
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.
Click to expand...
Click to collapse
Thanks. I will start digging!
kitkat85 said:
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.
Click to expand...
Click to collapse
@automess... I have used both and though autotools is 2.99 I find it more user friendly. But both are equally up to task.
digitalpig82 said:
What ADB command are you talking about?
I'm on Nougat as well and I'm using Secure Settings every day, it works fine for me...
Click to expand...
Click to collapse
Hi, I'm in nougat with a ROM but I can't open tasker. I hope anyone can help
@farquea,::if you want to stick with securesettings in noughat,here is the work around i am using, found the fixfrom superSu forum..
Obviously i am using superSu to give root access for secure settings..
First flash superSu in systemless mode in twrp.
After reboot, using terminal emulataor type the following command
su
echo "BINDSYSTEMXBIN=true" >> /data/.supersu
and reflash superSU from twrp..securesettings will be enabled...
Reference :
1) https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
2) https://forum.xda-developers.com/showpost.php?p=66140836&postcount=5493
This may help you if u want to stick with securesettings
vedhavyga said:
@farquea,::if you want to stick with securesettings in noughat,here is the work around i am using, found the fixfrom superSu forum..
Obviously i am using superSu to give root access for secure settings..
First flash superSu in systemless mode in twrp.
After reboot, using terminal emulataor type the following command
su
echo "BINDSYSTEMXBIN=true" >> /data/.supersu
and reflash superSU from twrp..securesettings will be enabled...
Reference :
1) https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
2) https://forum.xda-developers.com/showpost.php?p=66140836&postcount=5493
This may help you if u want to stick with securesettings
Click to expand...
Click to collapse
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.
JRJ442 said:
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.
Click to expand...
Click to collapse
i think dat also..but not sure if enter both the values, will supersu install in systemless mode?
JRJ442 said:
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.
Click to expand...
Click to collapse
I'm using the Magisk interface and Secure Settings just works with the root method that is built into Magisk,
Also thinks like AndroidPay work with Magisk
Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.
Tmobilefan906 said:
Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.
Click to expand...
Click to collapse
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Code:
/sbin/su -c "svc data enable"
axxbat said:
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Click to expand...
Click to collapse
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas
Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?
axxbat said:
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas
Click to expand...
Click to collapse
u didn't offend me at all
axxbat said:
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?
Click to expand...
Click to collapse
What u mean skipped su perms?
Tmobilefan906 said:
What u mean skipped su perms?
Click to expand...
Click to collapse
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?
axxbat said:
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?
Click to expand...
Click to collapse
I guess I'm not too worried about it. As long as the task works, I'm fine with it. Haha
I'd even take an explanation of how to do it, I could possibly figure it out from there.
You might wanna try this:-
https://forum.xda-developers.com/moto-z-play/how-to/how-to-enable-miracast-t3565852
How to enable Miracast | Moto Z Play - XDA Forums - XDA Developers
Sent from my Moto G3 Turbo Edition
Is there a way to do that with a Magisk module?
ird0 said:
Is there a way to do that with a Magisk module?
Click to expand...
Click to collapse
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Much appreciated, thanks.
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Just to make sure, did I do it right?
http://imgur.com/ZkE0tin
ird0 said:
Just to make sure, did I do it right?
http://imgur.com/ZkE0tin
Click to expand...
Click to collapse
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Didgeridoohan said:
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Click to expand...
Click to collapse
Thanks for spotting that. I can't test it until I get home. Much appreciated
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Didgeridoohan said:
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Click to expand...
Click to collapse
Seems I can connect but then my phone does a UI restart. I guess it just doesn't work or I'm missing some kind of library or something.
I'm stuck at the same point on my P2XL. Did you ever figure it out?
Stuck here too. I can enable the menu but when I try to connect, I get a restart of the UI and I go back to the lock screen. Pixel 2 XL
I finally gave up.
I just saw a recent post on the Pixel forum with a guide to get it working (at least for the original Pixel.) Maybe this could prove useful:
https://forum.xda-developers.com/pixel/how-to/guide-how-to-enable-miracast-pixel-t3888780
Credit to sbjbs
Sent from my Pixel 2 using Tapatalk
I have patched august boot image and root with magisk .Can I just use ota to update?
bartoloandre98 said:
I have patched august boot image and root with magisk .Can I just use ota to update?
Click to expand...
Click to collapse
it's in the other thread already. Does not work
Benjamin_L said:
it's in the other thread already. Does not work
Click to expand...
Click to collapse
so what is the way forward? format?
bartoloandre98 said:
so what is the way forward? format?
Click to expand...
Click to collapse
some user is reporting success. So just try. You will loose root if it works and need a patched september boot image afterwards
I will try this when I'm home:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
hugopg said:
I will try this when I'm home:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Did it work ?
It would be great if this method works, so no more patching of boot.img and flashing after every new OTA.
hugopg said:
I will try this when I'm home
Click to expand...
Click to collapse
Hey, did it work?
I really need to be assured .
*the fact that he disappear may not looks solid good ????
Didn't work for me.
rafihasan710 said:
Hey, did it work?
I really need to be assured .
Click to expand...
Click to collapse
I've tried it, but the update failed again
Lurensu said:
I've tried it, but the update failed again
Click to expand...
Click to collapse
When you enable hal3 API you modify the system partition. If even mounting it rw trips the "modified detector" it is no wonder ota does not work
Benjamin_L said:
When you enable hal3 API you modify the system partition. If even mounting it rw trips the "modified detector" it is no wonder ota does not work
Click to expand...
Click to collapse
This.
From what I understand, and the following confirms it, some people have simply edited the properties file in System (thus no updates) and some have used the 'setProp' command, which doesn't modify System.
The following explains it:
"Android system properties are being managed by special property_service. The /system/build.prop is just one out of 4-6 (depending on the version) read-only files containing the default values that property_service uses to populate its internal in-memory database with during start-up. So changes to the files during run time would not propagate until after reboot.
The setprop and getprop commands are used to access the data in that database. Unless the property name starts with persist. - then the value gets stored in /data/property folder."
So, it seems that if all you do with root is use setprop, you should continue to get the updates.
AsItLies said:
This.
From what I understand, and the following confirms it, some people have simply edited the properties file in System (thus no updates) and some have used the 'setProp' command, which doesn't modify System.
The following explains it:
"Android system properties are being managed by special property_service. The /system/build.prop is just one out of 4-6 (depending on the version) read-only files containing the default values that property_service uses to populate its internal in-memory database with during start-up. So changes to the files during run time would not propagate until after reboot.
The setprop and getprop commands are used to access the data in that database. Unless the property name starts with persist. - then the value gets stored in /data/property folder."
So, it seems that if all you do with root is use setprop, you should continue to get the updates.
Click to expand...
Click to collapse
I've used a Magisk module to enable camera2api.
I've now uninstalled magisk, anyone has an idea about how should I procede?
Lurensu said:
I've used a Magisk module to enable camera2api.
I've now uninstalled magisk, anyone has an idea about how should I procede?
Click to expand...
Click to collapse
This probably also does the setprop stuff. Do you know if uninstalling it restores the original state?
rafihasan710 said:
Hey, did it work?
I really need to be assured .
Click to expand...
Click to collapse
I won't try that because I've changed the build.prop to enable HAL3 and cameraApi2. So i'll need to flash the system.img BEFORE doing that... I'll do it next week only.