[SuperSU] jerryasher:
Failing to update **from version 2.65** on Galaxy Note 2, SGH-T889

I'm a clueless noob, so sorry.

Rooted my stock galaxy note 2 earlier today using chainfire auto root.

Knox got it the way, but supersu ... seemed to uninstall it and it remained uninstalled past several reboots. And then Knox came back (!) and supersu wouldn't uninstall it.

I disabled Knox using Package Disabler Pro, and both Root Checker and Root Check seem to agree I have root, as does Titanium Backup and SD Maid Pro.

Regardless .. on boot, I see a # notification and it tells me SuperSU The binary needs to be updated!

I say continue and normal and it spins for a minute or so saying it is installing, then croaks and says Installation failed! Please reboot and try again.

BUT ... SuperSU is already on version 2.65, isn't that the latest version?

- Exact device model

Samsung Galaxy Note II, T-Mobile

- Exact firmware version

Stock firmware (but rooted this morning)

Baseband: t889uvucoh4

kernel: kernel 3.0.31-2835337

Build number

Jss15j.t889uvucoh4

SE for Android status

Enforcing

SEPF_SGH-T889_4.3_0035

- Exact Android version

Android 4.3

- Exact SuperSU version

When Knox blocked SuperSU

I installed chainfire 2.65 via https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip

- Interfering apps

There are some apps that can interfere with SuperSU installation, primarily:

- other Superusery apps

- Xposed

- BusyBox (symlinked or non-symlinked)

No other superusery apps, no exposed, no busybox (but I did install a busybox installer)

Include in your report if you have one or more of these installed.

- Update methods tried

I've tried:

In-app 'normal',

- What kind of root are you left with?

Everything seems to work fine, root seems to work, but I'm a clueless noob, so what do I know?

What I see is a notification that supersu needs to be updated.

No log at the moment, I am installed Android Studio and will see if I can get one later.

# - Logs from SuperSU (very important)

#

# If SuperSU keeps asking you to update the binaries after trying any

# which way and failing, please post the detection log. After updating

# has failed, don't reboot, but produce detection information via adb

# logcat -d | find /i "installer" > logcat.txt (Windows, use 'grep -i'

# instead of 'find /i' on Linux or OSX), which should produce a

# logcat.txt file in your current directory with several lines

# mentioning SuperSU. Attach this log file.

# - Various logs (very important)

# Some additional handy information can be gotten by via some adb shell

# calls. If you that working, copy/pasting the following commands should

# produce a nice sulog.txt file in your current directory, which you

# should attach to your post:

#

# (as always with copy/pasting, make sure you press enter a few times

# afterwards to make sure the last line was flushed)

#

# Code:

# adb shell getprop > sulog.txt

# adb shell toolbox id >> sulog.txt

# adb shell busybox >> sulog.txt

# adb shell su -v >> sulog.txt

# adb shell su -V >> sulog.txt

# adb shell su -h >> sulog.txt

# adb shell su --self-test >> sulog.txt

# adb shell ls -l /system/xbin/*su* >> sulog.txt

# adb shell ls -lZ /system/xbin/*su* >> sulog.txt

# adb shell ls -lZ /system/bin/toolbox >> sulog.txt

# adb shell ls -l /system/bin >> sulog.txt

# adb shell ls -l /system/xbin >> sulog.txt

# adb shell ps >> sulog.txt