Database Users

Rooting XXUEMJ7

Hi everybody
I am owner of S4 LTE (GT-I9505) with fw version XXUEMJ7.
I followed the instructions for rooting the phone using the correct files fo my phone's version.
I installed the TWRP recovery but I have the following problems:
1. SuperSu does not appear in my apps drawer.
2. Knox is still active.
3. Titanium Backup stuck trying get root permission and the same time I receive knox message on ststus bar.
4. Root Checker stuck and I receive knox message on the status bar.
5. Knox disabler is ineffective.
6. Terminal program is ineffective too and when I try su command I receive knox message again.
Is it safe to full wipe my phone and install an AOSP rom or there is any posibility to brick my phone?
TWRP recovery seems to work properly.
Sent from my GT-I9505 using XDA Premium HD app

pannik72 said:
Hi everybody
I am owner of S4 LTE (GT-I9505) with fw version XXUEMJ7.
I followed the instructions for rooting the phone using the correct files fo my phone's version.
I installed the TWRP recovery but I have the following problems:
1. SuperSu does not appear in my apps drawer.
2. Knox is still active.
3. Titanium Backup stuck trying get root permission and the same time I receive knox message on ststus bar.
4. Root Checker stuck and I receive knox message on the status bar.
5. Knox disabler is ineffective.
6. Terminal program is ineffective too and when I try su command I receive knox message again.
Is it safe to full wipe my phone and install an AOSP rom or there is any posibility to brick my phone?
TWRP recovery seems to work properly.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Same here i want to get rid of knox notification i don't care about knox trip or whatever i just want my phone rooted help me please ..

Hi everybody
Finally I flashed this rom via ODIN
http://forum.xda-developers.com/showthread.php?t=2250824&highlight=xxuemj7
And then liquidsmooth rom with TWRP recovery.
Everything looks to work smooth.

pannik72 said:
Hi everybody
I am owner of S4 LTE (GT-I9505) with fw version XXUEMJ7.
I followed the instructions for rooting the phone using the correct files fo my phone's version.
I installed the TWRP recovery but I have the following problems:
1. SuperSu does not appear in my apps drawer.
2. Knox is still active.
3. Titanium Backup stuck trying get root permission and the same time I receive knox message on ststus bar.
4. Root Checker stuck and I receive knox message on the status bar.
5. Knox disabler is ineffective.
6. Terminal program is ineffective too and when I try su command I receive knox message again.
Is it safe to full wipe my phone and install an AOSP rom or there is any posibility to brick my phone?
TWRP recovery seems to work properly.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
You can't because of KNOX, install a Pre-Rooted Rom instead.

BillvanHalen said:
You can't because of KNOX, install a Pre-Rooted Rom instead.
Click to expand...
Click to collapse
I did it.
First I installed the pre-rooted XXUEMJ7 rom and TWRP recovery with ODIN.
Then I downloaded Liquidsmooth v2.37 and flashed via TWRP.
Everything is fine now and Liquidsmooth rom works very well.

i9506 android 5 root

Hi guys i found root for s4 i9506 android 5
Link :laugh:
http://zidroid.com/how-to-root-galaxy-s4-lte-a-i9506-on-android-5-lollipop/

Here`s what I did:
Flash TWRP or CWM via odin
You have 2 options
1. Apply root directly from recovery and install supersu from playstore.
2. Flash Supersu.zip 2.45 via recovery.

kornelius1982 said:
Here`s what I did:
Flash TWRP or CWM via odin
You have 2 options
1. Apply root directly from recovery and install supersu from playstore.
2. Flash Supersu.zip 2.45 via recovery.
Click to expand...
Click to collapse
First time flash android 5 rom via odin.exe
And next step flash this file via odin.exe
File link
http://download.chainfire.eu/502/CF-Root/CF-Auto-Root/CF-Auto-Root-ks01lte-ks01ltexx-gti9506.zip
:good:

Rooted successfully but knox is still activated, supersu doenst detectid or remove it, anyone know how to remove knox in this update, please?

bryanfeanor said:
Rooted successfully but knox is still activated, supersu doenst detectid or remove it, anyone know how to remove knox in this update, please?
Click to expand...
Click to collapse
Supersu doesn't know yet how to treat to lolipop knox, let's wait to master chainfire and hope.

bryanfeanor said:
Rooted successfully but knox is still activated, supersu doenst detectid or remove it, anyone know how to remove knox in this update, please?
Click to expand...
Click to collapse
just install link2sd and in link2sd search knox and all file have knox on her rename remove it:good:
im sorry for my bad english

seli1987 said:
just install link2sd and in link2sd search knox and all file have knox on her rename remove it:good:
im sorry for my bad english
Click to expand...
Click to collapse
thanks, but what i did was freeze all knox apps and com.sec.knox. with titanium backup no issues so far

Replacing KingUser with SuperSU

Hi all, I just want to share this. Regarding to Kinguser cant be replace by SuperSU, I just solve this issue. But, I want to make it clear,
I FOUND THIS METHOD ACCIDENTALLY(by experimenting).
I just got Samsung Galaxy Grand Duos I9082, with home button not functioning. So I cant root it by custom recovery, which made me use Iroot(known as Vroot), 1 click rooting app. It will root using Kinguser binary. Which will give problem to replace it with SuperSU. Then install busybox.
So I reroot my phone using KingO root which will install SuperSU v2.02. I guest this is the point where SuperSU bin get hook in device(I tried installing various ver of SuperSU without success,"Installing Failed". And KingUser give perm to SuperSU using KingO root method.
So I go into SuperSU, install as system, reboot, install custom recovery, install SuperSU.zip thru recovery, reboot, uninstall KingUser(it will warn this will unroot your device back to normal, i just ignore and proceed), and this will erase SuperSU app too, but I guest it leave the binary installed. And again I reinstall SuperSu in normal way, with success.
And again, I'm not telling the best solution, just want to share what I've done. Hope this will help someone.
Good Day

I try to replace King User with the Terminal Emulator Method, and King User gone, but it unroot mi device
I have a Samsung i8200L.
After, I re-root my device (now with Kingo Root, thanks for mention it in your thread), and everything is ok, with SuperSU

Naimlaaa said:
Hi all, I just want to share this. Regarding to Kinguser cant be replace by SuperSU, I just solve this issue. But, I want to make it clear,
I FOUND THIS METHOD ACCIDENTALLY(by experimenting).
I just got Samsung Galaxy Grand Duos I9082, with home button not functioning. So I cant root it by custom recovery, which made me use Iroot(known as Vroot), 1 click rooting app. It will root using Kinguser binary. Which will give problem to replace it with SuperSU. Then install busybox.
So I reroot my phone using KingO root which will install SuperSU v2.02. I guest this is the point where SuperSU bin get hook in device(I tried installing various ver of SuperSU without success,"Installing Failed". And KingUser give perm to SuperSU using KingO root method.
So I go into SuperSU, install as system, reboot, install custom recovery, install SuperSU.zip thru recovery, reboot, uninstall KingUser(it will warn this will unroot your device back to normal, i just ignore and proceed), and this will erase SuperSU app too, but I guest it leave the binary installed. And again I reinstall SuperSu in normal way, with success.
And again, I'm not telling the best solution, just want to share what I've done. Hope this will help someone.
Good Day
Click to expand...
Click to collapse
Easiest method that worked for me!
Use es file explorer
change permision to /system/bin to rw, tick all
run updated supersu, it will ask to update su binary, use the normal option
Kinguser will ask permission from SuperSu, DENY!
Then you can successfully remove kinguser

Newyork! said:
Easiest method that worked for me!
Use es file explorer
change permision to /system/bin to rw, tick all
run updated supersu, it will ask to update su binary, use the normal option
Kinguser will ask permission from SuperSu, DENY!
Then you can successfully remove kinguser
Click to expand...
Click to collapse
I'm assuming you used SSU 2.49? As Chainfire said, he made this mostly for lollipop comparability, also for Kinguser replacements issues.
And thanks for sharing the workaround you've figured.:thumbup:
Sent from here to there

Naimlaaa said:
I'm assuming you used SSU 2.49? As Chainfire said, he made this mostly for lollipop comparability, also for Kinguser replacements issues.
And thanks for sharing the workaround you've figured.:thumbup:
Sent from here to there
Click to expand...
Click to collapse
I didn't figure it out. it just worked for me!

Newyork! said:
I didn't figure it out. it just worked for me!
Click to expand...
Click to collapse
Maybe someone will need it later, lucky them found an easy and more practical way.:thumbup:
Sent from here to there

Hope this will work
Worked on Galaxy S3 NEO ( GT-I9300I ) Android 4.4.4
The Steps that worked for me are as follows:
Start from HERE
1. Same steps untill SuperSu installed
2. When SuperSu launched itself (or you can launch it manually ) , it
will ask to update SU Binary, Click Normal.
3. Wait until SuperSu says other user management app detected (in my
case) and will ask you to remove it. Click cancel ( very important ).
4. When you Click Cancel, it will say Binary updated Successfully. And
will ask you to Reboot or OK. Click OK ( very important ) and not to
Reboot.
5. Now SuperSu will open normally but KingUser app will still be present
( in my case).
6. Now go to Settings in SuperSu App and Go to Clean Up options and
there you will find an option to remove other User Managemnt apps, just
click the option and Boom SuperSu will remove it completely from your
System.
Hope this will work for someone else also.
2nd Method:
Just simply install SuperSu from Play Store and follow the above steps
from Number 2 onwards. (Confirm if it works for you)
Credit to : Chainfire and MrW0lf

SuperSu Binaries are not installed and SuperSu cannot install these binaries.

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?

Help to root so far unsuccessful Telstra SM-G900I

G'day,
I have followed the instruction using the download on this page for SM-G900I without success. https://forum.xda-developers.com/showthread.php?t=2696537
I found another Telstra user who used the kltezt version, so I tried with the version from https://autoroot.chainfire.eu/ even though the build version is different. This time SuperSU asked to disable knox, I did so, verify with Root Checker, doesn't work. Reinstalled using Odin without auto reboot, SuperSU asked for New user or expert, I chose New User, nothing.
EDIT---
When using Root Checker it would ask for permission to verify, I would try and click button which would not work.
I have just uninstalled SuperSU and Root Checker worked. I have reinstalled SuperSU updated binary and restarted and now Root Checker fails.
Android: 6.0.1
AP: G900IDVU1CQD1
Any suggestions?
Samuel

G'day sir.
CF-Autoroot is the old method of rooting the S5 and it will fail in some cases because it is no longer updated. The current method of rooting the S5 is to use either the SuperSU zip from the SuperSU XDA thread or magisk from the Magisk thread. What's the difference? Magisk allows to hide root, superSU works better with some apps and with xposed.
Go to the TWRP website, locate the files for the G900F (klte) and download the latest version to your PC. Then flash the .tar file in ODIN under AP/PDA.
Immediately after flashing, you must reboot to recovery (hold power button, home button, volume up button) until you see "rebooting to recovery". Once in TWRP, flash the SuperSU or magisk zip then reboot.
All the best, Saber

Thanks for your reply. Though had to go do some hard Googling to fill in the gaps of the installation process, like adding the SuperSU zip to the memory card.
I was about to say it didn't work again, but then it clicked why I may not have been able to grant access in the past. I use the night overlay app "Twilight" and I know the system doesn't like it running when doing certain tasks and asks you to disable the overlay. I disabled Twilight and it worked. Double checked and it is definitely the problem. All that for probably nothing.
Now I can install apps to the external SD, well that's the plan anyway. I've had enough manually moving them over manually to make space.
Thanks once again for your assistance!
Samuel