Related
|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here.
If you have not updated to 4.4, go here.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Edit:
Here is some potentially useful info for root method #1 from ansonantonym.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery then flash SuperSu and the Knox Remover
4) Reboot
5) Download SuperSu from the Play Store
6) Open SuperSu and update the binary when prompted
7) Reboot
8) Enjoy rooted 4.3/4/4
Downloads:
Odin
TWRP (Odin flashable tar)
SuperSu (v1.65)
SuperSu (v2.01)
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
Please be sure to thank Chainfire, Dees_Troy, and Kaito95.
*****
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeremyds45 said:
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
upndwn4par said:
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
Click to expand...
Click to collapse
Ah it is so nice to have root again... Thank you so much for putting up with a noob.
Crazy events of a noob that lead me to root
Installed ota 4.3
Tried to root and install superuser by odin and then custom recovery to flash
Root didn't happen because of knox
Could only get to CWM custom recovery if it was right after odin and battery pull?...
Flashed the script to remove knox, which did remove knox
Tried the same root method as above and no root access
Tried supersu and then updating in play with no success
Changed security update settings etc nothing
Reset delvik, cache, permissions, etc nothing
Different root method and files for odin, and custom recovery stuck
Used files from this thread, went into custom recovery and flashed supersu
Installed supersu from play store...
Updated the binary using custom recovery
Rebooted...
ROOT access, all root applications work fine and root sticks even after reboots
I never messed with cf auto root method
THANK you guys for your time effort and sharing, helps noobs out like me a lot!
Sweet! I've missed root since I upgraded using the OTA file you provided. Looking forward to much other great things coming from you
Thank You
upndwn4par said:
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here. Make sure you understand the risks and uncertainties described in the OP.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery and flash SuperSu.
4) Flash the Knox Remover
5) Reboot
6) Download SuperSu from the Play Store
7) Update the binary when prompted
8) Reboot
8) Enjoy 4.3
Downloads:
Odin
TWRP (Odin flashable tar)
UpdateSuperSu
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
*****
Click to expand...
Click to collapse
Method two absolutely worked. Thank you so much. I was scared to flash TWRP but knowing you did it gave me the courage. Have full root and happy
questions about this root
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
THANKS!!!! your a lifesaver didn't know how much longer i could take without root
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
bkong said:
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
Click to expand...
Click to collapse
use the TWRP method worked perfected for me
Thanks
PimpMyPC said:
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
Click to expand...
Click to collapse
The second method worked great. I believe (and the way that worked for me) that you use your custom recovery to flash the knox script, not using Odin and pda. I don't think it removed anything other than knox, there is a different script for removing knox and att bloatware. Should still be able to factory reset... But can't guarantee that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Root & Knox
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
tailgunner9 said:
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
Click to expand...
Click to collapse
Those settings are just for granting device administrator privileges. If unchecked, Knox is still doing it's thing, just not at an administrative level.
Yes, it is safe to try and root.
I have Android Device Manager as admin. That way if I ever lose my device I can just log in to the Play Store and locate and / or wipe the device.
To do this just flash the recovery.img file using odin and clicking the pda button correct?
Is there a way to freeze Knox instead of deleting it in the event I would want to go back to full stock?
After you are rooted, use an app like Titanium Backup(pro) or My Backup pro. Both will freeze it.
Root
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
tailgunner9 said:
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
Click to expand...
Click to collapse
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
indymx said:
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
Click to expand...
Click to collapse
Thanks indymx, may get the nerve up to try it on my AT&T S3. Let me know if you run into any problems. Guess Rom Manager and other programs that require Root are working Ok and you have rebooted few times to be sure it keeps Root?? Have Happy Thanksgiving.
sooo i was stock i took the OTA update to 4.3 mk6
i decided i didn't care about the knox counter so i rooted and custom recovery (this is the rom location http://forum.xda-developers.com/showthread.php?t=2589891) and this is the recovery location http://forum.xda-developers.com/showthread.php?t=2159652
now every thing is working (SU, Titanium Back up, and so on)
however when i try certain apps (game killer, game chi) it says i don't have root
i have searched everywhere but i am not seeing any posts about this
any help would be greatly appreciated
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
thanks for the help i will try this now
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
i uninstalled superSU then went to the market and downloaded and updated that didn't work it was still the same
no i have downloaded and installed from customer recovery and when i open superSU it says i need to manually re-root my phone so i guess i need to re flash my rom from original post?
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Zen Arcade said:
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Click to expand...
Click to collapse
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Remove them from SU list. Restart app and approve the SU request again.....
dicksteele said:
Remove them from SU list. Restart app and approve the SU request again.....
Click to expand...
Click to collapse
okay done and no change
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Which apps?
Zen Arcade said:
Which apps?
Click to expand...
Click to collapse
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
mrnewspaper said:
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
Click to expand...
Click to collapse
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Zen Arcade said:
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Click to expand...
Click to collapse
i didn't see those notes but thanks to everyone for all the help and i will look in to stepping back again (i bricked the first time)
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Zen Arcade said:
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Click to expand...
Click to collapse
awesome thank you
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
pavanchirmade said:
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
Click to expand...
Click to collapse
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Zen Arcade said:
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Click to expand...
Click to collapse
I flashed the same one.
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Zen Arcade said:
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Click to expand...
Click to collapse
Here's a screenshot.
That's the correct file...
A deeper dive would involve looking at the permissions and properties of su and daemonsu in /system/xbin as well as a few other SuperSU related files in /system and subdirectories.
If you are running a custom kernel it's possible that it is pushing an older version of SuperSU (or other superuser app).
Do you have only the SuperSU app installed (i.e. no SuperUser or other app in the app drawer)?
Reaching at this point as it's not typical for the current versions of SuperSU to lose root.
One thing you can try is root with current, boot phone, immediately run SuperSU, choose "Full Unroot", reboot boot phone, then shutdown and reflash cf-auto-root and see if it sticks.
As for flash counter, once you get root to stick, you can use Triangle Away to reset that to zero - works for everything but the knox warranty counter.
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Stewegg said:
Can't even start SuperSU
Click to expand...
Click to collapse
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
VeeDaub said:
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
Click to expand...
Click to collapse
Where is the Reactivation Lock located?
I can not find it in the Security Settings.
mrevankyle said:
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Click to expand...
Click to collapse
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Stewegg said:
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Click to expand...
Click to collapse
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
Link to philz recovery tar for our phone i317M
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/philz_touch_6.19.3-t0lteatt.tar.md5
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
Simple. First get the root. Like the su binary and stuff. once you are rooted get suersu. What I mean by first get root is literally get root through a program or something. After this you will have root but you wont have root access. So get supersu now and launch the app. It will ask to update your su binary. Say yes. then the thing will say something about knox then ask you if you want to try to disable knox. Tap yes and knox should be disabled and your su binary should be updated and working.
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
My phone is I317M Rogers, it run stock 4.3. I followed this guide, http://forum.xda-developers.com/showthread.php?t=2618261 rooted success.
Eun-Hjzjined said:
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Click to expand...
Click to collapse
ifentanez said:
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
Click to expand...
Click to collapse
koodiifin said:
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
......
Click to expand...
Click to collapse
koodiifin's way worked perfectly!
Thank you koodiifin!
I have a T-Mobile Galaxy S4 and I tried rooting it using the CF-Auto-Root, but when I open SuperSU, it says "there is SU binary installed, and SuperSU cannot install it." I decided I want to root it all the way but I can't figure this out. How do I root this phone?? Do I have to use the CyanogenMod?? Please help!!
chosenginger said:
I have a T-Mobile Galaxy S4 and I tried rooting it using the CF-Auto-Root, but when I open SuperSU, it says "there is SU binary installed, and SuperSU cannot install it." I decided I want to root it all the way but I can't figure this out. How do I root this phone?? Do I have to use the CyanogenMod?? Please help!!
Click to expand...
Click to collapse
Ok, So my question would be did you use Odin to install CF-Auto-Root? Most I've seen use it and have no problem. Odin installs it then the phone reboots and that's when a special recovery is installed and then loaded and the root process is done. After that stock recovery is again installed. Not positive but I heard there may be other methods named similiar to this that will root phones that have 4.3 and lower.
Make sure you have the version mentioned here http://forum.xda-developers.com/showthread.php?t=2294005
Also. if you think for some reason that your phone maybe rooted but SuperSU isn't working right you could always go to the Play store and download Chainfire's SuperSU and then install it. If your phone was truly rooted this should fix SuperSU
Corwinder said:
Ok, So my question would be did you use Odin to install CF-Auto-Root? Most I've seen use it and have no problem. Odin installs it then the phone reboots and that's when a special recovery is installed and then loaded and the root process is done. After that stock recovery is again installed. Not positive but I heard there may be other methods named similiar to this that will root phones that have 4.3 and lower.
Make sure you have the version mentioned here http://forum.xda-developers.com/showthread.php?t=2294005
Also. if you think for some reason that your phone maybe rooted but SuperSU isn't working right you could always go to the Play store and download Chainfire's SuperSU and then install it. If your phone was truly rooted this should fix SuperSU
Click to expand...
Click to collapse
I have the SGH-M919 model and yes I used ODIN, but whenever I open SuperSU, it comes up that it has no binary. I already checked and I have the chainfire version.
Sent from my SGH-M919 using xda app-developers app
I have searched the forums for my device, and other people's posts trying to find a way to root my device. Towelroot did not work for me. I read that i could install Philz touch recovery and root with that, but i cannot find the version of that for my phone. If somebody could point me in the direction of a method to root my phone, i would very much appreciate it
The Cheese Deity said:
I have searched the forums for my device, and other people's posts trying to find a way to root my device. Towelroot did not work for me. I read that i could install Philz touch recovery and root with that, but i cannot find the version of that for my phone. If somebody could point me in the direction of a method to root my phone, i would very much appreciate it
Click to expand...
Click to collapse
You could download GooManager (or Flashify) off the Play Store, install custom recovery (TWRP) and root. It will install the one for your phone automatically.
You need root to use GooManager.
Im curious, what happened with Towelroot? I cant see any reason it wouldnt work. Can you tell me the steps you used?
DocHoliday77 said:
You need root to use GooManager.
Im curious, what happened with Towelroot? I cant see any reason it wouldnt work. Can you tell me the steps you used?
Click to expand...
Click to collapse
I downloaded the towelroot apk, installed it and clicked "make it rain" and the app said i should have root. I downloaded root checker and it says i do not have root access.
After running Towelroot You have to install SuperSU from the Play Store, then open the app and let it update the binary and disable Knox.
If SuperSU hangs, reboot and it'll work on the second try.
DocHoliday77 said:
After running Towelroot You have to install SuperSU from the Play Store, then open the app and let it update the binary and disable Knox.
If SuperSU hangs, reboot and it'll work on the second try.
Click to expand...
Click to collapse
I had tried CF-Auto-Root before towelroot, and it seems to have either partially installed SuperSU, or SuperSU just doesn't like my phone. It shows up in my app list as "eu.chainfire.supersu.MainActi" and force closes when i try to open it. I cannot uninstall it. (i should have mentioned this in my OP maybe)
Oh ok. That makes more sense to me for why Towelroot didn't work then. Probably the easiest fix would be to reflash the firmware with Odin, then try Towelroot first. Since you dont have root now, its going to make fixing the problem any other way near impossible.......actually, now that I said that, you could flash twrp recovery, then use its file manager to manually delete any traces of the failed root.
Still, I think the firmware flash is an easier and safer option. But its up to you how you want to proceed.
DocHoliday77 said:
Oh ok. That makes more sense to me for why Towelroot didn't work then. Probably the easiest fix would be to reflash the firmware with Odin, then try Towelroot first. Since you dont have root now, its going to make fixing the problem any other way near impossible.......actually, now that I said that, you could flash twrp recovery, then use its file manager to manually delete any traces of the failed root.
Still, I think the firmware flash is an easier and safer option. But its up to you how you want to proceed.
Click to expand...
Click to collapse
I successfully flashed TWRP, exactly what files should i delete?
Check the cf autoroot thread to be sure, but probably the su binary, install-recovery.sh, daemonsu, etc.
DocHoliday77 said:
Check the cf autoroot thread to be sure, but probably the su binary, install-recovery.sh, daemonsu, etc.
Click to expand...
Click to collapse
The recovery file manager does not see a lot of the files on my phone. It does see the SuperSU folder, but even if i delete or rename it, it just fixes itself upon reboot. I'm thinking of flashing the 4.4.2 firmware through odin, is a factory reset absolutely necessary to do that?
I flashed the firmware, ran towelroot, installed SuperSU, installed the binary, disabled Knox, and i am now running a rooted device!
Thank you very much DocHoliday77 for all of your help, i greatly appreciate it.
Which firmware did you reflash? Stock 4.4.2??
I cannot find towelroot on the app store. Are there any suggestions on what to do without towelroot