After much reading and experimenting, I am stumped. I have tried rooting using Odin 3.09 and twrp 2.8.0.1. using various techniques. I can get to where it boots into twrp, but when I try reboot it doesn't give me the root option. I also tried this kazil-tech.weebly.com/ technique of loading a zip version of SuperSU v2.46. The links to the files are all broken and the versions are not given, s I really don't know what is required, but that technique went exactly as described. The only problem is it didn't root the tab. It did take root checker two tries to discover it wasn't rooted. Is my problem that the kernel is too new and all the Odin techniques are not compatible? Is there any other way to get this to work?
dcuste said:
After much reading and experimenting, I am stumped. I have tried rooting using Odin 3.09 and twrp 2.8.0.1. using various techniques. I can get to where it boots into twrp, but when I try reboot it doesn't give me the root option. I also tried this kazil-tech.weebly.com/ technique of loading a zip version of SuperSU v2.46. The links to the files are all broken and the versions are not given, s I really don't know what is required, but that technique went exactly as described. The only problem is it didn't root the tab. It did take root checker two tries to discover it wasn't rooted. Is my problem that the kernel is too new and all the Odin techniques are not compatible? Is there any other way to get this to work?
Click to expand...
Click to collapse
Proper links to SuperSU zips:
SuperSU 2.46 zip
SuperSU 2.49 zip
Related
Hello, I'm having a problem when rooting my device. I've successfully flashed the CF-Auto-Root file and it says "PASS" in Odin but the phone boots into recovery and won't boot to the OS and the recovery is showing this message: "Recovery is not Seandroid enforcing".
I've used this file to root: http://download.chainfire.eu/727/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltedx-smg900f.zip How can I fix this? I've flashed BOB7 stock and the phones back to normal but I need to root in order to install a custom recovery (Philz)
Thanks.
KayKrate said:
Hello, I'm having a problem when rooting my device. I've successfully flashed the CF-Auto-Root file and it says "PASS" in Odin but the phone boots into recovery and won't boot to the OS and the recovery is showing this message: "Recovery is not Seandroid enforcing".
I've used this file to root: http://download.chainfire.eu/727/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltedx-smg900f.zip How can I fix this? I've flashed BOB7 stock and the phones back to normal but I need to root in order to install a custom recovery (Philz)
Thanks.
Click to expand...
Click to collapse
You can try this if you want it works when using TWRP recovery but not sure about Philz
Make sure you don't have super user app installed on your phone
Download the attached zip and put it in a folder on your phones internal storage
Install Philz custom recovery via Odin
When the phone reboots go to the market and install Chainfires SuperSU, this one here
Once installed reboot phone into recovery and install the zip file you downloaded above
Reboot the phone and go to the SuperSU app and tap it, give it a moment and it should ask for you to grant root access
If it has worked as it does with TWRP you will be rooted, let me know if it works or not.
ag4751 said:
You can try this if you want it works when using TWRP recovery but not sure about Philz
Make sure you don't have super user app installed on your phone
Download the attached zip and put it in a folder on your phones internal storage
Install Philz custom recovery via Odin
When the phone reboots go to the market and install Chainfires SuperSU, this one here
Once installed reboot phone into recovery and install the zip file you downloaded above
Reboot the phone and go to the SuperSU app and tap it, give it a moment and it should ask for you to grant root access
If it has worked as it does with TWRP you will be rooted, let me know if it works or not.
Click to expand...
Click to collapse
I don't really want to risk anything , I've also noticed that there are 2 CF-Auto-Root files , one that says kltedx and other that says kltexx. Should I give the other one (kltexx) a try? Also , my friend told me that I need to root first and then install a custom recovery (Philz).
KayKrate said:
I don't really want to risk anything , I've also noticed that there are 2 CF-Auto-Root files , one that says kltedx and other that says kltexx. Should I give the other one (kltexx) a try? Also , my friend told me that I need to root first and then install a custom recovery (Philz).
Click to expand...
Click to collapse
I never mentioned CF Auto Root the process mentioned above doesn't use it. it is just TWRP Recovery 2.4 or higher you install via Odin
Then SuperSu form the marked
Then boot into recovery and install the zip file which updates SuperSU binary to give root access
That's it, no CF Aoto Root
ag4751 said:
I never mentioned CF Auto Root the process mentioned above doesn't use it. it is just TWRP Recovery 2.4 or higher you install via Odin
Then SuperSu form the marked
Then boot into recovery and install the zip file which updates SuperSU binary to give root access
That's it, no CF Aoto Root
Click to expand...
Click to collapse
Are you sure that your method is going to work on my G900F? I'm on Lollipop OB7 if that makes any difference.
KayKrate said:
Are you sure that your method is going to work on my G900F? I'm on Lollipop OB7 if that makes any difference.
Click to expand...
Click to collapse
It is totally tour choice to try or not, my phone details are in the screen clip attached
ag4751 said:
It is totally tour choice to try or not, my phone details are in the screen clip attached
Click to expand...
Click to collapse
Same as mine , so you've used exact same method on the same firmware version (BOB7) ?
Nevermind , It appears that there's another G900F , one's kltexx and kltedx and kltexx worked for me and the other didn't. Thanks for helping tho
Has anyone tried simply flashing a custom recovery, then using the recovery to flash SuperSU as a way to gain root access?
Or do i need to find a rootable kernel somewhere?? I google this issue alot recently, and just want to find out if someone has done this successfully. Odin is killing me because no matter what i DO try to flash using it, fails... other than the Stock Android 5.0.1 firmware. Am i missing something, or can someone give me directions to the simplest instructions possible to gain root on it. I know this has been asked alot, but most solutions i have found have only been for other carriers, and lower builds of the firmware. I would be willing to downgrade to KitKat if necessary... but also that seems impossible because the bootloader blocks downgrades... Please Help
Worked Like A Charm
So its done!! Simple and easy... Three steps! (make sure to copy the newest SuperSU file to your sdcard first)
***Boot into ODIN Download Mode***
1. Using ODIN flash TWRP 2.8.4.0 (dont let it reboot on its own afterwards!... YOU MUST BOOT INTO RECOVERY ON YOUR OWN THE FIRST TIME TO LET TWRP PATCH THE ROM)
2. While in TWRP recovery, then install SuperSU zip file from your SDcard
3. Select reset and perform the "Factory Reset" option.
!!! Success... !!! you now have a rooted Sprint S4 with the OF1 build of lollipop...
*********Credit to "bilgerryan"
For the proper process to use!
:laugh:
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?
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
Can anyone give me instructons on how to twrp n rot sm-j320zn ? I cant find the corrcy twrp for this model not having much luck thanks guys
koniva85 said:
Can anyone give me instructons on how to twrp n rot sm-j320zn ? I cant find the corrcy twrp for this model not having much luck thanks guys
Click to expand...
Click to collapse
Don't know if you still need the info, but I've just worked out TWRP. I've been rooted for ages but never saw your post; it's only because I decided to try TWRP again that I found you in a Google search.
TWRP that works on the J320ZN is for j3lte. To download: https://dl.twrp.me/j3lte/
Others have had issues installing SuperSU.zip in TWRP.... as did I. The only way to get root that would work is CF-Auto-Root..... because usually SuperSU.zip would then cause a bootloop. BUT of course, what I didn't realize at the time, was CF-Auto-Root once installed reflashed stock recovery! But what it DID enable me to work out (once it clicked in my head that this was going to be the issue and after I'd nearly set up my phone again) was that I was getting a dm-verity error.... something I know nothing about other than it's a new thing I have to do on my Samsung Galaxy Tab A. So MAYBE SuperSU wasn't installing because of that? Who knows.
Anyway, now I'm fully working with TWRP and root and it's sticking with no problems.
So install TWRP the usual way....(I used twrp-3.2.1-0-j3lte.img from the link above). If you need help with this quote me and ask, or look for a TWRP tutorial on j3lte (I know the J320YZ uses this TWRP and has a tutorial on how to install TWRP with Odin).
Then install the latest SuperSU.zip:
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip through TWRP "Install" method.... it must be on your external SD card. Go to the "Install" button on TWRP menu, select storage to extSD and then find SuperSU.zip.
THEN I had to install the Dm-verity and Forced Encryption Disabler through TWRP "Install" method (so this file also needs to be on your external SD card):
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
I used no-verity-opt-encrypt-6.0.zip
Then reboot, and reset up your phone.
FINALLY!
Whether you need to do the dm-verity thing I don't know... I'm FAR from an expert. This was all through trial and error but it is the only way to keep root through TWRP without CF-Auto-Root.....FOR ME PERSONALLY.
You could try just TWRP and the latest version of of SuperSU.zip through TWRP....see if that works. If you get stuck in a bootloop, then I just flashed CF-Auto-Root with Odin and it fixed that.... then start the install process again, this time adding dm-verity patch AFTER SuperSU.zip.
If you want to skip TWRP and just root your phone, then the easiest way is to flash CF-Auto-Root with Odin. File at https://download.chainfire.eu/986/CF...etrieve_file=1.