Okay so I have seen an update to SuperSU in the app store.
I had manually installed SuperSu through TWRP recovery when I rooted the tablet, as per the instructions on this thread:
http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-10-5-wifi-semi-t3242433
However, now I'm unconvinced of the benefits of updating SuperSu through the Google Play store, as I have had issues updating it previously (with the welll-known updating binary issues). Also I've heard of many issues where the binary doesn't update properly (both on the Tab S and other devices).
The way I see it, SuperSu is doing its job, and I don't make drastic modifications to my tablet that require an update to SuperSu at present. I have also disabled OTA updates as they tend to not work with rooted devices. So I'm holding off on the update for now.
Any thoughts?
If it ain't broke don't fix it.
@snapper.fishes:
That's what I was thinking too...Thanks!
Related
OK, I know this has been asked and asked again, but I have been reading and digging and googling for several days now, and cannot find a solution.
I've got a JB S3 At&t, and wanted to root it, so after reading for a few weeks, I got the "Samsung_Galaxy_S3_ToolKit_v7.0", donated, and got 7.2 (newest version). I flashed with the toolkit to get an unsecured boot image, with SuperSU 1.04, busybox, and TWRP .
Root happened fine. The phone booted, and when I went to open SuperSU (the icon was in my apps), it asked to update the binaries. I said yes, it failed, and the app opened anyway to allow me to access the options. Triangle away worked fine.
The update binaries thing was bugging me, so I updated to SuperSU 1.10 via google store, and the same thing happened, but now I could not access the program after the binary update failed. It still works (triangle away asks and gets permission) but I could not access the program any longer. It just closes after it informs me that updating the binaries failed.
I have tried installing the program as an app, pushing an APK, and installing a zip from recovery. No matter what I do, it ends up the same.
I have also re-flashed the boot several times, and tried a different method using Odin directly and CF-Root. (seems to be the only way to uninstall it) I have tried numerous combinations, but to no avail. I feel like I have done everything I know how to do short of an unroot to stock and try again.
Any helpful suggestions are welcome.
I'd like to be able to use the program, but this is turning into an OCD nightmare. I'd post this in a development forum, but do not have enough posts yet.
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
illmatic24 said:
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
Click to expand...
Click to collapse
Thanks. I ended up doing it the hard way. (I swear I had auto email notification enabled here, or I would have seen your post and tried it)
Anyway, I cleared caches/userdata/wipe cache partition first, then flashed a stock unrooted 4.1.1 rom from here,
Then I used CF-autoroot, and low and behold, SU was showing up as an app. (it was not previously when I used CF-AR)
I let it update itself and bam, it works! Installed adbd insecure, and it works too. (it was not showing up as an app when I did it before either)
Next I added TWRP 2.4.3.0. and everything still works!
Either the stock AT&T rom on this unit had something interfereing with root, or the root image I used in the toolkit has an issue. I'm leaning towards a toolkit issue since when I used it and it installed TWRP 2.4.1.0, I could not get into recovery, just a black screen.
I lieu of this, I'm limiting my use of the toolkit.
Curiously, the toolkit also allows a sideload via TWRP/CWM, but does not provide a driver. Windows 7 cannot recognize the phone in recovery mode with a custom recovery installed, although it does when a stock recovery is. I have yet to find a driver.
Hi sorry I am new here, I looked around and did not see an answer to this
I rooted my S3 yesterday using Kingo Android root and as far as I can tell everything worked properly (other apps detect that phone is rooted) but SuperSu is not working because Knox keeps on blocking it. I read a few fixes like just uninstalling SU and reinstalling via the play store but Kingo installed SuperSu as a system app so I cannot do this.
Do I have to reroot or is there an easy way to reinstall SuperSU so that knox is not in the way (all none of the ways to deactivate Knoxs from within the phone do not work because none of my root apps have superuser), I am a bit of a noob when it comes to cell phones.
An suggestions? Also I am looking to keep the data that is already on the phone
EDIT: I got it working
For anyone else having this issue I went to chainfire's website and downloaded the newest version of SuperSU
I opened the Zip found the apk (found in the common folder) and uploaded it to my phone.
Using the default filemanager I opened and installed the apk.
Since it is a higher version then the one in the store it let me update the original failed SU install.
Upon starting SU it updated the binaries and also disabled knox.
Just tried this way and it worked for me thanks. I had same issues there was no option to update from store and Knox kept stopping such..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
My tablet is currently on stock MRA58K. I've rooted it, installed TWRP, and have Xposed installed (if that matters). I've been holding off installing the OTA system update(s) because I didn't want to mess with re-rooting (I see that's not a concern). Anyways, after searching for a fix to my Netflix playback problem, I see that it was fixed with one of the monthly updates (MRA58U). With this information I went through the steps of installing the OTA update (Settings->About Tablet->System updates). The updated downloaded and asked me if I wanted to install it and restart the tablet. Everything looked normal. When the tablet rebooted it booted straight into recover (TWRP). Confused by this, I just rebooted into system from TWRP. As far as I can tell the update didn't install. The build is still MRA58K and I still have the Netflix playback issue.
Is there a way to manually download and install the incremental monthly updates? I don't want to install the full blown factory image and have to re-setup the tablet.
Thanks
Maybe just get some MRA58V ROM since you have TWRP? And yeah, you wont be able to install official OTA with TWRP, you need to be stock for that.
A couple hours ago my phone with unlocked bootloader, twrp and magisk root installed an OTA update without me initiating it. This failed and the phone was stuck in twrp recovery and couldn't boot until I flashed a stock rom through fastboot and restored my backups.
Now I want to prevent this from happening again. How do I block the phone from checking for OTA updates?
I will have to install them manually anyway so the OTA checking is not helpful.
Same thing happened to me except I was dumb enough to try and install myself the update... You can install Titanium Backup and freeze the Motorola Update app. Also, you can go under dev options and disable automatic updates (this alone didn't work for me).
How to prevent OTA updates, without root, please?
I followed this guide, the method 4 worked for me when my phone was rooted.
http://www.droidviews.com/disable-ota-notifications-android-devices/
With help from the Google, I finally recalled how I'd done it in the past.
Initially, I thought rooting would stop OTA updates, but that may have been prior to Marshmallow or with SuperSU.
This time, I used Titanium Backup (must be rooted) to freeze the MOTOROLA UPDATE SERVICE app.
As soon as it was frozen, the OTA notification disappeared from the notification bar and I gave not seen it return, for a couple days.
Yay! I didn't want to go beyond the stock firmware version that is available and I really didn't want Oreo.
Another way is to use a firewall app.
Also you can just add Motorola's address to your 'host' file to block it
Im the opposite, I want the notifications, without the automatic installation.
Wonder if I changed the permissions of the folder the updates download to, would that prevent automatic install?
also, there is an option in developer options, to turn off OTA.
Since updating to C.48 (2125 [phone], coming from C.47, my Google Play and Pay have stopped working on my rooted phone (Magisk 24.3), even though it passes SafetyNet with YASNAC. When I try to open Play I get a "Try Again" screen. When I try to open Pay, I get "Google Pay is updating right now...". I've got Universal SafetyNet Fix 2.2.1 and MagiskHide Props Config installed, and Play and Pay in the Deny List. Tried using Shamiko 0.4.4 (while disabling deny) with no better results. Cleared cache and data on both apps multiple times. Uninstalled Magisk and unrooted, and everything worked again. Re-rooted w/o opening either app, put them both into "deny" and, for a brief time, both worked -- but eventually (without my doing anything that I could tell), they both reverted to the behavior described above.
I'm wondering if this behavior has anything to do with the April security update included in C.48? Because it's really odd that I YASNAC still shows safetynet as having passed. More likely, it's user error on my part, but has anyone else run into this yet on C.48?
I have a LE2127 running your firmware and I don't notice issues. One thing you could try is just flashing the update zip over your current OS using the OPlocalupdate apk here https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Thanks. I presume you're rooted? Which version of Magisk are you using and are you using Deny List or Shamiko?
rogerinnyc said:
Thanks. I presume you're rooted? Which version of Magisk are you using and are you using Deny List or Shamiko?
Click to expand...
Click to collapse
Yes, I'm rooted. I'm using Denylist on Magisk 24.3.
No problems on my end with Gpay while rooted
I gave up and did a total restore with MSM and then made sure to root and fill up the Deny List (and add SafetyNet Fix) before opening up Google Pay or Play. That seemed to work. Not sure how I messed it up in the first place, but I think it was in upgrading from C47 to C48 and my sequencing of unrooting, upgrading, clearing storage in the apps and re-rooting. Thanks all.