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.
I have recently rooted my phone i think gone through all the steps on galaxys4root.com. When I was done I tried to update su binary and it said installation failed.then tried to go on titanium backup and it said rom is not rooted .ok i got su app to update but it now saying there is no su binary installed and super su cannot install it . This is a problem But the phone says it is rooted so do I need to re root the phone
Thanks for any help
willdoe said:
I have recently rooted my phone i think gone through all the steps on galaxys4root.com. When I was done I tried to update su binary and it said installation failed.then tried to go on titanium backup and it said rom is not rooted .ok i got su app to update but it now saying there is no su binary installed and super su cannot install it . This is a problem But the phone says it is rooted so do I need to re root the phone
Thanks for any help
Click to expand...
Click to collapse
I think the steps on galaxys4root.com may be outdated or used properly on an older version of Android. Try CF Auto-Root: http://forum.xda-developers.com/showthread.php?t=2294005
Vigz said:
I think the steps on galaxys4root.com may be outdated or used properly on an older version of Android. Try CF Auto-Root: http://forum.xda-developers.com/showthread.php?t=2294005
Click to expand...
Click to collapse
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
willdoe said:
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
Click to expand...
Click to collapse
No. However, CF Auto-Root will flash stock recovery. If you want to install custom ROMs, simply re-flash CWM Recovery.
willdoe said:
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
Click to expand...
Click to collapse
ok thanks a bunch one more question what steps should i follow to re-flash cwm recovery
willdoe said:
ok thanks a bunch one more question what steps should i follow to re-flash cwm recovery
Click to expand...
Click to collapse
I am guessing here but please correct me if i am wrong cf auto root gives me root then i should follow galaxy s4root.com instrutions on how to install cwm recovery
willdoe said:
I am guessing here but please correct me if i am wrong cf auto root gives me root then i should follow galaxy s4root.com instrutions on how to install cwm recovery
Click to expand...
Click to collapse
Once you are rooted you have to choose which recovery you want. Twrp is the most compatible with most Roms out there. To get cwm you need to install ROM manager from the market. The option to flash recovery will be inside. If you want twrp download goo manager and the option to flash will also be in the app. Good luck!
Sent from my SGH-M919 using xda app-developers app
mrzhadow said:
Once you are rooted you have to choose which recovery you want. Twrp is the most compatible with most Roms out there. To get cwm you need to install ROM manager from the market. The option to flash recovery will be inside. If you want twrp download goo manager and the option to flash will also be in the app. Good luck!
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You can also get either TWRP or CWM as a Tar file that can be flashed in Odin.
You can also download the .img files and flash either with Flashify.
There are a lot of ways to flash recoveries. Each with specific advantages for specific situations.
Ok thanks a bunch to all of ya in my situation I am just trying to get root on my phone it is a t-mobile S4 its running 4.2.2 it seemed easy enough on galaxyS4root.com I think I guessed wrong so I will definitely try cf auto root though I am not done trying yet so again thanks for your time
willdoe said:
Ok thanks a bunch to all of ya in my situation I am just trying to get root on my phone it is a t-mobile S4 its running 4.2.2 it seemed easy enough on galaxyS4root.com I think I guessed wrong so I will definitely try cf auto root though I am not done trying yet so again thanks for your time
Click to expand...
Click to collapse
That website you tried seems to have borked you all up. Cut your losses with methods from there and start over with the CF Auto Root method. it will work perfectly in 30 seconds.
Ya I was pretty aggravated lastnight but got up this morning used cf autoroot and so far so good super su has binary installed titanum back has root its going good so far thanks again for yalls help
I'm not exactly new to the rooting scene nut lets just say i'm not that expert at it.
THe problem im now getting is on my Samsung Galaxy Note 2(Sgh-1317m) i had it rooted when i was on DN3 but then i wished to update
to 4.4.2, my root was gone. When I tried to re-root it via CF-Auto Root it flashes successfully no probs. But when i open SuperSU it says no SU binary installed and im not able to access root. Is there any way to get root successfully on 4.4.2 or do i have to get back to DN3.
Get back to me ASAP. :good:
Regards,
xtrmewhacker
Special Thanks To Chainfire who made rooting so damn easy!
Try reloading SuperSU from play store
xtrmewhacker said:
. . . When I tried to re-root it via CF-Auto Root it flashes successfully no probs. But when i open SuperSU it says no SU binary installed and im not able to access root. Is there any way to get root successfully on 4.4.2 or do i have to get back to DN3.
Click to expand...
Click to collapse
This is my first post to XDA. I'm brand new to rooting though reasonably competent technically. Wanted to root for access to root-only apps, but wanted to wait for 4.4 in case I ended up unable to receive future updates. 4.4.2 OTA came in yesterday so I tried flashing. Used Odin to install TWRP recovery then used TWRP to load TeamEpic Root From Recovery. When done, root apps said I was not rooted. Loaded SuperSU and it said SU binary was missing and I should reroot. Found CF-Autoroot and loaded it through ODIN. Red-logo thing appeared and system recovered but apps still said no root. Loaded "Root Checker Basic" from play store and it confirmed still no root. Tried to run SuperSU but found it to be missing. Reloaded SuperSU from Play Store. As SuperSU was finishing installing, popup message said something about Root Checker wanting access. I said "grant" and then found that Boot Checker verified root access. So I'm on my way.:victory:
Suggestion to xtrmewhacker: remove SuperSU and reinstall from Play Store.
SuperSU couldn't install the latest binary? I did the same as you, install 4.4 stock, flash cf-auto root, installed supersu from play store.
Supersu then installed via normal (not twrp), disabled knox, and rebooted. Everything was fine after.
dwightarthur said:
This is my first post to XDA. I'm brand new to rooting though reasonably competent technically. Wanted to root for access to root-only apps, but wanted to wait for 4.4 in case I ended up unable to receive future updates. 4.4.2 OTA came in yesterday so I tried flashing. Used Odin to install TWRP recovery then used TWRP to load TeamEpic Root From Recovery. When done, root apps said I was not rooted. Loaded SuperSU and it said SU binary was missing and I should reroot. Found CF-Autoroot and loaded it through ODIN. Red-logo thing appeared and system recovered but apps still said no root. Loaded "Root Checker Basic" from play store and it confirmed still no root. Tried to run SuperSU but found it to be missing. Reloaded SuperSU from Play Store. As SuperSU was finishing installing, popup message said something about Root Checker wanting access. I said "grant" and then found that Boot Checker verified root access. So I'm on my way.:victory:
Suggestion to xtrmewhacker: remove SuperSU and reinstall from Play Store.
Click to expand...
Click to collapse
Thm man appreciate it...I'm rolling now.:good:
This crying moose for confirmation
I'm having an issue on 4.4 where supersu just keeps crashing and I can't even open it. I've tried everything. At one point it opened and started to work but after I reset my phone its back to saying "unfortunately, supersu has stopped working"
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
No progress yet
I managed to flash custom recovery through which i flashed DN3 so im at DN3 but still no root.
i use cf auto and now SuperSU keeps shutting down I keep getting the msg
"Unfortunately,SuperSU has stopped working".
Help plz.
Regards,
xtrmewhacker
I got the same thing with cf-autoroot. I went in to philz touch and applied root there. Reboot and you should be able to dl from the market or do like I did and flash the zip version.
Sent from my Note 3...making all others drool!
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
Hey guys I've been trying to root my tablet all day today. I tried using chainfires one click method with odin. SuperSU got installed but it closes as soon as it opens(I have tried going to the play store but it says SuperSU is a system app and will only let me open). I've no clue what to do at this point. Is there a way I can use odin to go back to stock? Before the 4.4.2 update or better, is there any different root method for 4.4.2?
I rooted my n5110 on 4.4.2 NE2 using Kingo. It takes awhile but worked. I had the same issue with CF-Autoroot.
Alright I'll see what happens. I'll try that
Thanks I'll post results later
Kingo just failed for root
SuperSU still doesn't even open. It closes automatically
Kingo didn't work. CF oneroot with odin didn't work. I have no clue whats going on.
I am having the exact same issue, neither CF-AutoRoot nor Kingo has been successful at getting root access...
on KOT49H N5110.XXDNE1
The thing has resisted my concentrated efforts for two evenings thus far
root with cf-autoroot and try update supersu from here
https://www.dropbox.com/s/x8cr7ytfcqxmlmc/SuperSU 2.01.apk
then launch supersu to update su binary and disable knox notification
memooffon said:
root with cf-autoroot and try update supersu from here
https://www.dropbox.com/s/x8cr7ytfcqxmlmc/SuperSU 2.01.apk
then launch supersu to update su binary and disable knox notification
Click to expand...
Click to collapse
Dude.... I don't even know what to say. You un****ed my tablet lol. Much appreciated. I did have to go into SuperSU and enable it at boot and make it install as a system app. Otherwise when I restart tablet it would keep force closing again
darandster2 said:
Dude.... I don't even know what to say. You un****ed my tablet lol. Much appreciated. I did have to go into SuperSU and enable it at boot and make it install as a system app. Otherwise when I restart tablet it would keep force closing again
Click to expand...
Click to collapse
Don't forget to hit his "Thanks" button.
I have a problem to root my note 5110
It has 4.4.2 and I can't enter in download mode
Do you have an idea to do it (I tried the classical method)?
Thanks
darandster2 said:
Hey guys I've been trying to root my tablet all day today. I tried using chainfires one click method with odin. SuperSU got installed but it closes as soon as it opens(I have tried going to the play store but it says SuperSU is a system app and will only let me open). I've no clue what to do at this point. Is there a way I can use odin to go back to stock? Before the 4.4.2 update or better, is there any different root method for 4.4.2?
Click to expand...
Click to collapse
Use this method :
1. Flash the CF auto root via odin
2. Flash TWRP or CWM recovery via odin
3. Boot to recovery
4. Flash this : http://goo.gl/kpOHVm
5. Reboot
After that, open supersu and update binary + disable Knox.