Hi. Seeking advice from pros...
I have recently enabled permission to Write System Settings thru ADB for Tasker.
Now that January security patch is ready to install, do I have to remove that permission first? Or I can install OTA straight away?
Edit: Updated OTA anyways and it turned out fine. In case anybody wondering
Related
Everytime I open SuperSU, it keep asking for update, but when i click okay, it keep saying that it failed...
Ziken said:
Everytime I open SuperSU, it keep asking for update, but when i click okay, it keep saying that it failed...
Click to expand...
Click to collapse
When you click update does it request superuser permissions?
Have you disabled first superuser?
Then you have to open and update the binares of supersu
At the end you can update from market the app and re-upgrade new binaries
how to disaple superuser i installed supersu and it replaced superuser without configuring anything and begin to appear in situations that need permissions do it mean that superuser is disabled although indid not do anything to disable it or extra steps needed to disable superuser completely ??
okay...i was able to fix it...someone need to modify the guide to include that we have to go to google play and download the SuperUser by ChainDD to fix the SU update request. best i can figure out is that SuperUser was borked and probably couldn't update itself. it not odd to see that happen.
I have SuperSU v2.40 on CM11S. Initially when I started using apps that required root worked with the prompt. I was trying to give root permission to MultiROM Manager via the prompt and for some reason the prompt window is unresponsive to taps/touches. This problem also happens in any new app that also requires root access. I tried disabling the prompt and selecting the option to grant all apps root permission and that seems to solve the problem, but obviously that is not something I'd like to use on a daily basis. Is this a known issue with SuperSU? What should I do to fix this? Re-install? I did not find any way to add apps to the SuperSU list manually (on the non-Pro version), is there one?
I installed root by flashing it through TWRP (2.8.4.1) after completely restoring back to CM11S (44S, Stock Kernel) via fastboot couple of days back.
UPDATE: The problem was with Tapjacking protection under SuperSU's Settings. Switched off temporarily, gave some apps the root permission and switched it back on.
UPDATE 2: The problem was because of Lux. The app controls the brightness by putting an overlay which prevents you from tapping the SuperSU prompt.
Came here to say exactly what you found out lol glad you figured it out
If you ever have issues trying to install an apk in the future, it's due to the same thing with lux. Disable it temporarily and you will be able to click the install button for the apk.
Sent From Lollipopified Bacon Goodness!
Hello,
I don't want to take the OTA update and lose Xposed (or root). I have already disabled the notification.
I keep having a full screen nag. It keeps downloading Blur_Version.24.3.7.obake-maxx_verizon.Verizon.en.US.zip to /cache/ and the only way to get it to go away temporarily is to delete that zip, but it keeps showing back up...
I tried putting FOTAkill.apk in /system/app but it disappeared. I don't think I can actually write to that directory (which is why I can't unlock my bootloader / have custom recovery).
I have looked for the update apks to rename but I'm not sure it will take either, even if I could find them.
Edit: I have solved this myself using Tasker. I bought it a while ago so I'm not sure if you can do it with the free version if there even is one.
Profile Event > System > Device Boot
Action 1. Run Shell Command: am force-stop com.motorola.ccc.ota (use root checked)
Easy to do with Debloater. Block damn 3c_ota.apk, or smth like that )
+cache wipe in recovery
Hi All,
I have a Nexus 7 2013 and I wish to update it. However when the OTA update is run a error message appears. I rooted the tablet several months ago and have since then un-rooted it. When I run a root checker Superuser Binary Files are still installed alongside BusyBox. Could this be the reason as to why the OTA is failing if so, how do I completely remove the files?
Thanks
which SU , manager you used?
maybe you uninstalled the wrong way.
if bussybox is installed, open the remove binary and uninstall.
if not working, install the SU manager you used, go to setting of it and " remove root/binaries"
Ok so I have a friend that bought the pixel via verizon, and took it onto Tmobile. Trying to unlock the hotspot tether via build.prop edit.
The Pixel (Was on Android 7.1) has been unlocked via dePixel8 and rooted via Chainfire. Root Checker also verifies this.
However, whenever we try to access the build.prop through Root Explorer, ES File Manager, and the like, SuperSU prompts and gives root access but no way to save an edited build.prop.
I tried mounting /system as R/W via multiple adb commands which were unsuccessful, I think due to the new partition scheme. I don't remember the commands I used, I googled for them and have since closed those tabs.
Thought that maybe the root messed up somehow so re-did the Chainfire root with no change to the system, in fact it even seems like root is even more broken with ES File Manager no longer able to view the root directory.
We are currently downloading the google edition NDE63V Factory Image in hopes of getting rid of any hidden Verizon security "features" that may be causing this issue along with getting rid of the Verizon bootloader.
All OTAs will be sideloaded after we put on NDE63V Image to protect from a Verizon bootloader being placed back onto the phone.
Has anyone else with Verizon Pixel had issues with root features and troubles mounting anything as R/W? Any ideas on a possible fix without needing to flash NDE63V?
There's no Verizon-specific build.prop security feature to my knowledge. The command "mount -o rw,remount /system_root" should work. If it fails, can you post the error you get?
dnbonds said:
Ok so I have a friend that bought the pixel via verizon, and took it onto Tmobile. Trying to unlock the hotspot tether via build.prop edit.
The Pixel (Was on Android 7.1) has been unlocked via dePixel8 and rooted via Chainfire. Root Checker also verifies this.
However, whenever we try to access the build.prop through Root Explorer, ES File Manager, and the like, SuperSU prompts and gives root access but no way to save an edited build.prop.
I tried mounting /system as R/W via multiple adb commands which were unsuccessful, I think due to the new partition scheme. I don't remember the commands I used, I googled for them and have since closed those tabs.
Thought that maybe the root messed up somehow so re-did the Chainfire root with no change to the system, in fact it even seems like root is even more broken with ES File Manager no longer able to view the root directory.
We are currently downloading the google edition NDE63V Factory Image in hopes of getting rid of any hidden Verizon security "features" that may be causing this issue along with getting rid of the Verizon bootloader.
All OTAs will be sideloaded after we put on NDE63V Image to protect from a Verizon bootloader being placed back onto the phone.
Has anyone else with Verizon Pixel had issues with root features and troubles mounting anything as R/W? Any ideas on a possible fix without needing to flash NDE63V?
Click to expand...
Click to collapse
Might as well use the latest factory image. (7.1.1 build NMF260)
I updated to the latest build with a clean install. Installed TWRP. Rooted with SR5. Then did the build.prop edit and it's working fine for me. (Verizon Pixel on Verizon's network)