Database Users

D802 CM13 SuperSU binary needs to be updated

Hello!
I have spent around 5-6 hours tonight fixing my phone. Before it had CM13 working just fine but my recovery didn't work (got an error when trying to enter recovery). I manged to solve that problem by doing lots of things I have already forgotten about now and to be honest I didn't really have any idea what I was doing as I am very new to this and have no knowledge about it.
Right now my CM13 works just fine. No problems booting. My recovery works just fine. I have CAF bootstack and the latest TWRP recovery that was mentioned in the guide. However, my SuperSU doesn't want to work properly. At first, I had to download the SuperSu app from Play Store. I don't know if that's how it is supposed to be. When I start the app it says "The SU binary needs to be updated. Continue?". I press Continue and it says "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary?". I have two options: "NORMAL" and "TWRP/CWM". If I press "NORMAL" it proceeds to installing and the circle is spinning and spinning... "Installing, please wait..." After about 30 seconds it says "Installation failed! Please reboot and try again". Rebooting and trying again doesn't help. If I try the TWRP/CWM option it reboots me into TWRP Recovery but nothing happens there. If I reboot system from recovery the problem remains. I googled a bit and found some thread where they said I needed to download some SuperSU zip-file and install it from recovery. I did that but that just broke it even more giving me some error saying SuperSu wasn't installed at all, or something like that. I ended up re-rooting the device and installing bootstack, CM, and GAPPS again.
I have enabled root access in the CM developer options menu, for both apps and ADB. I have downloaded Root Checker and it says i am rooted. In download mode it also says rooted.
Is there some step I have missed? Please help me. I just want CM13, Recovery, and SuperSU to all be working at the same time. Not just pick two, like I have done before.

I had the same problem on my d802. That thing you did in development settings worked for me. Is supersu so neccesary?

Seandroid not enforcing.

Hi guys i have rooted my phone recently and am on a custom rom now, but anytime i power on the phone i get this unfamiliar message that states.
Kerne is not seandroid enforcing
Set warranty Bit: Kernel.
please help!!
Sent from my GT-I9505 using XDA-Developers mobile app

Not A Problem
That is not an error it is simply stating that your SEANDROID is not enforcing meaning that more of the phones Sandbox has been disabled meaning that apps can do more than just with superuser access dont worry about it is normally fine.
My GT-i9505 Displays that on every boot and every Recovery Boot as i have TWRP installed and Resurrection Remix (2.7 (Android 6.0.1)) as the OS honestly its fine
-- Calsam12

calsam12 said:
That is not an error it is simply stating that your SEANDROID is not enforcing meaning that more of the phones Sandbox has been disabled meaning that apps can do more than just with superuser access dont worry about it is normally fine.
My GT-i9505 Displays that on every boot and every Recovery Boot as i have TWRP installed and Resurrection Remix (2.7 (Android 6.0.1)) as the OS honestly its fine
-- Calsam12
Click to expand...
Click to collapse
Ohh okay thanks very much
Sent from my GT-I9505 using XDA-Developers mobile app

S4 (i377m) running LineageOS 14.1: Problems with SafetyNet

Hi,
I could really use some help here with the i377m Canadian S4.
Basically, I want to make sure there is no root, that the bootloader is locked and that SafetyNet passes.
Here is what I did:
1) Downloaded Optimized LineageOS 14.1 and GApps, copied them on an SD card
2) Installed Samsung drivers and Odin
3) Installed the recommended TWRP (jfltecan) for LineageOS 14.1 , which is 3.1.0.
4) Installed TWRP via Odin
5) Booted to TWRP and cleared Dalvik, etc.
6) Installed Optimized LineageOS
7) Went to Developer Options, disabled Root
8) Flashed DisableSuperUser
9) Cleared Dalvik, etc. again
Safety Net Test says "CTS profile match: false" and "Basic Integrity: false"
I tried loading Pokémon GO (one of the few uses of this older device) and get "Unable to authenticate", another clue that SafeNet failed.
Also, I am getting the "Kernel is not Seandroid enforcing" and "Set Warranty Bit: Kernel" messages during bootup.
SELinux is set to "Permissive" and I read setting it to "Enforcing". The kernels found here for this model all seem to set to Permissive. At this point though I'm not sure and I would rather ask for guidance first.
Thanks for any help you may provide!

The bootloader on the sgh-i337m was never locked.

audit13 said:
The bootloader on the sgh-i337m was never locked.
Click to expand...
Click to collapse
Thanks... One thing I don't have to worry about.
I recall that at some point, I did give TWRP full access when prompted. Could this be one of the things that are triggering the Safety Net failures?
I don't know how to revoke the access I granted.

I don't think granting access to TWRP would affect the ROM since TWRP only runs when the phone boots into recovery.
Safetynet may be failing due to a custom ROM that hasn't been signed by Samsung.
You're getting the "not enforcing" because the phone has a custom ROM and recovery.

Kernel not seandroid enfoncing

Hello everyone,
I tried a month ago to root my s8,
but i froget to download no-verity-opt-encrypt!
so i reset my phone and used without the root.
but yesturday i tried to root it again!
I install twrp, normal. install no-verity-opt-encrypt-5.1 normal
but when i tried to install magisk or spuersu
it was saying that my boot image was already modified and i found that i need to flash a new one!
so i download one but now my phone is in a bootloop saying "Kernel not seandroid enfoncing"!
i tried to reset and install official rom, but odin write : "RESET" and "DONE" in two second and my phone just start bootlooping again...
I really don't know what to do.
I tried to call samsung
They say they don't support the root ;D
I found that i can extract the boot.img from official rom and remover the md5 hash at the end with cygin but i have no idee how this is working...
thanks in advance

Invalid kernel length after flashing TWRP

Hi,
I've istalled the latest LineageOS 18.1 on my T580. Unfortunatly I checked the option where Lineage would install its own recovery. Becaause I wanted to go back to TWRP I used the TWRP app to install the latest TWRP recovery. After a reboot the message "Could not do normal boot invalid kernel length" came and I can't boot either in the OS, nor recovery or download mode. Any chance of saving my device?

ro-mann said:
Hi,
I've istalled the latest LineageOS 18.1 on my T580. Unfortunatly I checked the option where Lineage would install its own recovery. Becaause I wanted to go back to TWRP I used the TWRP app to install the latest TWRP recovery. After a reboot the message "Could not do normal boot invalid kernel length" came and I can't boot either in the OS, nor recovery or download mode. Any chance of saving my device?
Click to expand...
Click to collapse
If you have the Exynos wifi variant, you should be able to flash TWRP recovery with Odin, like described here:
[Recovery][T580] Official TWRP for Galaxy Tab A 10.1 WiFi 2016 (gtaxlwifi)
Team Win Recovery Project 3.0.2-0 This is for the Exynos WiFi SM-T580 model only! WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your retailer to see if they will still cover...
forum.xda-developers.com