I recently rooted my device SM-N900 running android lollipop
SuperSU cannot update Binary .. it shows installation failed and when I reboot my device I stuck on boot loop and I have to re-flash official firmware again
help plz
The best way to install SuperSU and update the binary is from recovery. Just go to whatever custom recovery you have (I use TWRP myself), install the latest SuperSU zip package (version 2.46 is the latest AFAIK) from there. I am sure you know where to get the SuperSU zip from.
There will be no need to update or install anything from your ROM after you have done the above.
I have searched the forums here and couldn't find a direct solution to my problem.
My problem is after flashing a custom rom, I get the seandroid kernel enforcing error along with the boot loop. I understand this is kernel related, as when I restored my stock backup, then tried just flashing the custom kernel to that stock firmware, i got the same thing.
My question: is there a way to install custom roms/custom kernels without this damn seandroid boot loop annoyance?
I tried:
TWRP 2.8.5.0
Firekat N4ANK4V11X ROM
I was able to root successfully using auto root via odin, so root isn't a problem. I want a custom rom.
My KNOX version is:
Standard SDK 5.2.0
Premium SDK 2.2.0
Customization SDK 2.0.0
IM 2.0.0
CEP 2.0.0
Enterprise Billing 1.0.0
SE for Android 2.2.0
SSO 2.2.0
TIMA 3.0
VPN 2.2.0
Okay I solved my own problem. I downgraded twrp to 0.8.2.1 as this was the recommended Canadian version from the twrp site. I then realized I was trying to flash the wrong rom and firmware versions. All works great now on firekat v11x rom and 3.10.5-AELKernel-v7.2. This thread can be closed now
Hello there, I've been looking around online looking for a way to solve my SuperSu problem, but I haven't found a solution yet I was wondering if you guys could help me.
I installed my root using Odin and CF-ROOT I then realized I had both, Kingroot and SuperSU. Kingroot was the one with the root authorization and SuperSU did not have root authorization. Before I did anything SuperSU used to say "Binaries need to be updated use Normal Or TWRP/CWM," but after I used "Replace kingroot with supersu" It now says "No binaries are installed and SuperSU cannot install them." I'VE tried many methods to solve this. By the way I'm new to this stuff.
Methods used: About Device:
1. Flash updates binaries. 1. Model number: SM-G900T
2. Flashed SuperSU update. 2. Android version: 4.4.2
3. Tried to eradicate SuperSU.
SuPeRsUpRoBlEmS said:
Hello there, I've been looking around online looking for a way to solve my SuperSu problem, but I haven't found a solution yet I was wondering if you guys could help me.
I installed my root using Odin and CF-ROOT I then realized I had both, Kingroot and SuperSU. Kingroot was the one with the root authorization and SuperSU did not have root authorization. Before I did anything SuperSU used to say "Binaries need to be updated use Normal Or TWRP/CWM," but after I used "Replace kingroot with supersu" It now says "No binaries are installed and SuperSU cannot install them." I'VE tried many methods to solve this. By the way I'm new to this stuff.
Methods used: About Device:
1. Flash updates binaries. 1. Model number: SM-G900T
2. Flashed SuperSU update. 2. Android version: 4.4.2
3. Tried to eradicate SuperSU.
Click to expand...
Click to collapse
Are you on TW stock rom or Custom Rom? do you have recovery flashed?
My SuperSU app is losing root access when I try to install Xposed.
I looked into the problem, and I discovered that my /system/bin/app_process32 and /system/bin/app_process are linked to /system/xbin/daemonsu, but Xposed unlinks this and links to /system/bin/app_process32_xposed, which, for some reason, seems to make me lose the su binaries. I had recently reflashed the Nexus 4 system images(boot, bootloader, userdata, system, cache, radio and recovery), after which I used CF Auto-Root to root my phone(again). I installed twrp-3.0.2-0-mako and Cataclysm(here), but now I'm having this problem. Can anybody help?
I'm assuming you're using Cataclysm Mod on Marshmallow?
Try flashing, in order:
- Fake Nexus ROM 20160412
- TWRP 3.0.2
- CataclysmMod January stable
- Xposed 82
- SuperSU 2.68
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Hipp0123 said:
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Click to expand...
Click to collapse
Hard to help if you do not write in detail. Such as phone type, links you have used, etc etc
Hipp0123 said:
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Click to expand...
Click to collapse
You need to flash SuperSU manually.
1. Flash TWRP
2. Format data
3. Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip
http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
You simply brick your phone. You need to know that there is not Chainfire-AUTO-Root for Nougat, so you need first flash Stock FIRMWARE from Sammobile, then flash TWRP and flash SuperSU
Or you can flash many of 100 roms with prerooted supersu and busybox.
Hi there,
After upgrading my S7 Edge G935F to stock version xxu1dqd7 (with latest May 2017 upgrades) I had to install TWRP (twrp-3.1.1-0-hero2lte.img) again.
Unfortunately this change will NOT recognise my pattern lock now! I had to re-install the stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) using the HOME_CSC file to hold my data.
This re-installation brought me back to the game, but without TWRP and hope for root, but the pattern pin (the same) is now working...
Update 1
Installing TWRP (twrp-3.1.1-0-hero2lte.img) over the new stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) without having the pattern lock enabled feature during start will result in stuck on
the samsung title.
Update 2
I had to repeat the step above (stock firmware), so stay now without root.
Will check later with other stock versions
>It seems you didn't format the data partition or dm-verity was not installed. Happened to me, won't boot if >anything is altered like when installing a custom recovery.
Yes, I did it with and without dm-verity, All 3 options,
TWRP (ok, but pattern lock will not recognized)
TWRP + supersu (2.82) (stuck on the samsung logo)
TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo)
Yes, I didn'T format the data partition. Didn't want to lose my data ( Never had a problem to upgrade stock roms on my old S4 and root after).
Before the stock upgrade, I run with the Jan 2017 patch level (I bought this 2 days ago) and was able to root with the above method.
Today I wanted to jump the the latest stock version but run in trouble then.
Update 3
Downgrading to Stockrom from 2017-Jan-30 Germany 7 G935FXXU1DQB3 G935FDBT1DQA8 is not an option (anymore), The system boot up but with lot of errors and it's unresponsable and not usable.
Upgade then to the April patch status (2017-Apr-17 Germany 7 G935FXXU1DQD7 G935FDBT1DQD1) brought me back to operational,
but TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo).
Will try it now with the Februar patch version
Downgrade to the Feb patch status (2017-Feb-23 Germany 7 G935FXXU1DQBX G935FOXJ1DQB2) had the same resut like the Jan version - not usable.
I'll give up now and install the April version without TWRP.
I need root to restore my apps AND data with Titanium Pro.
seppdep said:
Hi there,
After upgrading my S7 Edge G935F to stock version xxu1dqd7 (with latest May 2017 upgrades) I had to install TWRP (twrp-3.1.1-0-hero2lte.img) again.
Unfortunately this change will NOT recognise my pattern lock now! I had to re-install the stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) using the HOME_CSC file to hold my data.
This re-installation brought me back to the game, but without TWRP and hope for root, but the pattern pin (the same) is now working...
Update 1
Installing TWRP (twrp-3.1.1-0-hero2lte.img) over the new stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) without having the pattern lock enabled feature during start will result in stuck on
the samsung title.
Update 2
I had to repeat the step above (stock firmware), so stay now without root.
Will check later with other stock versions
>It seems you didn't format the data partition or dm-verity was not installed. Happened to me, won't boot if >anything is altered like when installing a custom recovery.
Yes, I did it with and without dm-verity, All 3 options,
TWRP (ok, but pattern lock will not recognized)
TWRP + supersu (2.82) (stuck on the samsung logo)
TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo)
Yes, I didn'T format the data partition. Didn't want to lose my data ( Never had a problem to upgrade stock roms on my old S4 and root after).
Before the stock upgrade, I run with the Jan 2017 patch level (I bought this 2 days ago) and was able to root with the above method.
Today I wanted to jump the the latest stock version but run in trouble then.
Update 3
Downgrading to Stockrom from 2017-Jan-30 Germany 7 G935FXXU1DQB3 G935FDBT1DQA8 is not an option (anymore), The system boot up but with lot of errors and it's unresponsable and not usable.
Upgade then to the April patch status (2017-Apr-17 Germany 7 G935FXXU1DQD7 G935FDBT1DQD1) brought me back to operational,
but TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo).
Will try it now with the Februar patch version
Downgrade to the Feb patch status (2017-Feb-23 Germany 7 G935FXXU1DQBX G935FOXJ1DQB2) had the same resut like the Jan version - not usable.
I'll give up now and install the April version without TWRP.
I need root to restore my apps AND data with Titanium Pro.
Click to expand...
Click to collapse
With the TWRP + supersu root method, no matter what 7.0 stock ROM you use, you will not succeed before you disable boot pin and format data. You can restore data after rooting.
So start with the latest stock ROM that is working 100% for you, flash twrp, format data, flash supersu, and it should work. You have to format data because root and stock rom currently does not work with encryption.
Or even simpler, use the new cf autoroot, however it seems you still have to format data.
I had high hopes that the new cf autoroot nougat binary would work with encryption, but alas it seems it doesnt, at least I had the same wrong pin code at boot issue as with twrp. I havent had time to test it, nor to format data and root, so I am currently not rooted.
doclorenzo said:
With the TWRP + supersu root method, no matter what 7.0 stock ROM you use, you will not succeed before you disable boot pin and format data. You can restore data after rooting.
So start with the latest stock ROM that is working 100% for you, flash twrp, format data, flash supersu, and it should work. You have to format data because root and stock rom currently does not work with encryption.
Or even simpler, use the new cf autoroot, however it seems you still have to format data.
I had high hopes that the new cf autoroot nougat binary would work with encryption, but alas it seems it doesnt, at least I had the same wrong pin code at boot issue as with twrp. I havent had time to test it, nor to format data and root, so I am currently not rooted.
Click to expand...
Click to collapse
Thank you doclorenzo.
I had success with the latest stock version (xxu1dqd7) and your recomendation to format data in TWRP.
In short: Boot in Download mode, Install TWRP via Odin, Boot into TWRP - format data, supersu (2.82) + dm-verity
and then restore all data. Unfortunately it requires lot of time (at least 4 hrs to restore the apps + more for fine tuning)
Thank you and hope to have a better way with the next stock update and TWRP