Hello All,
I recently flashed KitKat 4.4.2 successfully but now I need to re-root. I see dodgy posts about rooting certain ways. Can someone please point me to the right direction in the easiest and safest way to root on KitKat? Thanks!
Suicide_Evo said:
Hello All,
I recently flashed KitKat 4.4.2 successfully but now I need to re-root. I see dodgy posts about rooting certain ways. Can someone please point me to the right direction in the easiest and safest way to root on KitKat? Thanks!
Click to expand...
Click to collapse
You can use CF Auto Root to re-root the phone. The only problem is this method will trip the Knox warranty void counter which can't be reset at this time. You flash it through odin and after it roots, you need to disable Knox. To do that, download (or update) SuperSU and when you run it for the first time, it will give you an option to disable Knox for the root to fully work. Finally, you can install the custom recovery. While this is optional, this is strongly recommended. You can use CWM or TWRP by downloading from either ROM Manager or Goo Manager depending on what recovery you want. After doing that, you should have a fully working root
Download CF Auto Root: http://download.chainfire.eu/233/CF-Root/CF-Auto-Root/CF-Auto-Root-d2spr-d2spr-sphl710.zip
You can also flash the SuperSU zip after using Odin to flash a custom recovery (I recommend philz)
Sent from my Sprint Galaxy S3 rocking Bilgerryans Wicked X ROM with the fluidity script, Tweaked out with a bunch of xposed modules, powered by Ktoonsez KT747 Kernel!!
Related
Hey,
Flashed to 4.3 official yesterday and I now want the DN3 ROM. I saw a KNOW WARRANTY option and thought I wont root till I know what this is.
Is it safe for me to root? All I want to do is root get CWM then flash DN3 and I'll be set.
If it is safe to root, can you post a link to a guide and if it isn't any hassle a link to get CWM as when I tried to get it, it never loaded up properly and wouldn't install the DN3 from my zip (When I was on 4.1.2)
All help will be appreciated
Spunkiest said:
Hey,
Flashed to 4.3 official yesterday and I now want the DN3 ROM. I saw a KNOW WARRANTY option and thought I wont root till I know what this is.
Is it safe for me to root? All I want to do is root get CWM then flash DN3 and I'll be set.
If it is safe to root, can you post a link to a guide and if it isn't any hassle a link to get CWM as when I tried to get it, it never loaded up properly and wouldn't install the DN3 from my zip (When I was on 4.1.2)
All help will be appreciated
Click to expand...
Click to collapse
There Is No Method To Root Without Voiding Knox Warranty....If You Want To Root Ur Phone And Remove Knox.....Try This - forum.xda-developers.com/showthread.php?p=48551128
As long as you have not done anything to trip it yet, flash DN3 bootloader, with your rom and you should be free of knox right?
I dropped Illusion and went full unrooted stock for the OTA to 4.3, which was not as awesome as I hoped it would be. So back to root and a custom rom!! Rooted MK4 with ease using kingoroot, used SuperSU to drop KNOX. I think after these steps is where my issues begin. Use goomanager to install twrp, and finally use billard412's wicked awesome "Back to UNROOTED Stock with Auto Flash Count Reset" to get back to MC2 in order to flash a custom rom. I have gotten stuck in a boot loop twice doing this and resolved both with the awesome forums here! The problem was both ROM's i went to (Dirty Unicorns and Smasher X) worked awesomely except for no mobile service on either.
So do I need to go back to MC2 in order to flash a custom ROM or can I go straight from rooted / custom recovery MK4 into a custom ROM. Or is there another flaw in my mechanics? I have seen a bunch of comments on using CWM instead of TWRP, is that my issue? Does CWM work in a similar fashion as TWRP? (I have only ever used TWRP) Thanks for any assistance, and fingers crossed there is not an unseen by me thread on this exact issue!
xysterztia said:
I dropped Illusion and went full unrooted stock for the OTA to 4.3, which was not as awesome as I hoped it would be. So back to root and a custom rom!! Rooted MK4 with ease using kingoroot, used SuperSU to drop KNOX. I think after these steps is where my issues begin. Use goomanager to install twrp, and finally use billard412's wicked awesome "Back to UNROOTED Stock with Auto Flash Count Reset" to get back to MC2 in order to flash a custom rom. I have gotten stuck in a boot loop twice doing this and resolved both with the awesome forums here! The problem was both ROM's i went to (Dirty Unicorns and Smasher X) worked awesomely except for no mobile service on either.
So do I need to go back to MC2 in order to flash a custom ROM or can I go straight from rooted / custom recovery MK4 into a custom ROM. Or is there another flaw in my mechanics? I have seen a bunch of comments on using CWM instead of TWRP, is that my issue? Does CWM work in a similar fashion as TWRP? (I have only ever used TWRP) Thanks for any assistance, and fingers crossed there is not an unseen by me thread on this exact issue!
Click to expand...
Click to collapse
Hey I think I am having a similar issue. I had to root back to stock MC2, take my phone to Sprint, have them reset it. Now I am on MK4 4.3 unrooted. When I tried to root, I got a Samsung message saying that there was an unauthorized app (SU) trying to run and prompted me to update Samsung security policy. What can I do to be rooted again so I can install custom ROMs again. Thanks!
cashdude1971 said:
Hey I think I am having a similar issue. I had to root back to stock MC2, take my phone to Sprint, have them reset it. Now I am on MK4 4.3 unrooted. When I tried to root, I got a Samsung message saying that there was an unauthorized app (SU) trying to run and prompted me to update Samsung security policy. What can I do to be rooted again so I can install custom ROMs again. Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2539227 <-- install SuperSU from play store and then google search Kingo Root, dl kingo root, run kingo root, enable USB debugging, connect, and follow on screen instructions!
Also that unauthorizing app is KNOX and big thanks should go to lorjay589 for posting work around. Also you should read his thread and understand all dangers and voidednous that now potentially comes with rooting.
That was the problem! I wish I would have tried before posting! My issue was either using TWRP or downgrading to MC2, I just tried again using CWM and root on MK4. Dirty Unicorns loaded perfectly and data is running!
Thanks for the tip, that helped me out also
hey guys,
I need help asap! I tried using the video on this website to root my tmobile S4. I downloaded Kies, Odin 3.07, ROOT_M919UVUAMDL.zip, and CWM as recovery-clockwork-touch-6.0.3.2-jfltetmo.tar, I did NOT install triangle away( i forgot). I went through the steps and passed in Odin. then, when I pulled the battery and booted in CWM i couldnt find the file so i went to the store to buy a sdcard. when I came home i re-ran through Odin and found the root zip on the external sdcard. I successfully installed the root zip and clicked reboot. my problem arose when it showed a "KERNEL IS NOT SEANDROID ENFORCING" in red, and a "SET WARANTY BIT: KERNEL" in yellow. it seems to be frozen in this screen and i can only use the CWM and Download mode. I have tried re-using Odin .
Please help!!
That's an old root method. You can either
1) flash a custom ROM and go about your business
2) Odin back to stock firmware and root with cf-auto root or towelroot
Sent from my SGH-M919 using Tapatalk
serio22 said:
That's an old root method. You can either
1) flash a custom ROM and go about your business
2) Odin back to stock firmware and root with cf-auto root or towelroot
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm sorry, I'm a Noob. but 1) where can I get a custom ROM and how do i apply it? 2) can you elaborate on your #2?
scott560 said:
I'm sorry, I'm a Noob. but 1) where can I get a custom ROM and how do i apply it? 2) can you elaborate on your #2?
Click to expand...
Click to collapse
1) You can find tons of Custom ROMs here: http://forum.xda-developers.com/galaxy-s4-tmobile/development
You usually flash them to your phone via a Custom Recovery such as CWM or TWRP. Or, is some cases you can use ODIN. Read, Read, Read, Read before your flash. It is very easy to do, but you need to understand what you are doing. All Custom ROMs come pre-rooted.
2) You can download a stock ROM from here:
http://www.sammobile.com/firmwares/
Or, you can use Kies to download and install the most recent firmware for your phone.
TowelRoot is a new option for rooting stock ROMs that are version 4.4.2 (KitKat). This method of rooting doesn't trip the Knox flag.
Here's a video: https://www.youtube.com/watch?v=ZGwMs8JPBhE
Rob
rlichtefeld said:
1) You can find tons of Custom ROMs here: http://forum.xda-developers.com/galaxy-s4-tmobile/development
You flash them to your phone via ODIN. Read, Read, Read, Read before your flash. It is very easy to do, but you need to understand what you are doing. All Custom ROMs come pre-rooted.
2) You can download a stock ROM from here:
http://www.sammobile.com/firmwares/
Or, you can use Kies to download and install the most recent firmware for your phone.
TowelRoot is a new option for rooting stock ROMs that are version 4.4.2 (KitKat). This method of rooting doesn't trip the Knox flag.
Here's a video: https://www.youtube.com/watch?v=ZGwMs8JPBhE
Rob
Click to expand...
Click to collapse
Thanks for replying however, you do not flash custom ROMs via Odin, you need a custom recovery like twrp or cwm.. Stock firmware you do flash via Odin.. And their Knox flag is already tripped, wouldn't matter
serio22 said:
Thanks for replying however, you do not flash custom ROMs via Odin, you need a custom recovery like twrp or cwm.. Stock firmware you do flash via Odin.. And their Knox flag is already tripped, wouldn't matter
Click to expand...
Click to collapse
Thanks for correcting me that most of the time you flash Custom ROMs via a Custom Recovery on the S4.
But, if I'm not mistaken you can flash Custom ROMs via ODIN as long as in the right format and you select the correct partition.
However, most of my Custom ROM history is with a HTC device, so I may be mistaken.
rlichtefeld said:
Thanks for correcting me that most of the time you flash Custom ROMs via a Custom Recovery on the S4.
But, if I'm not mistaken you can flash Custom ROMs via ODIN as long as in the right format and you select the correct partition.
However, most of my Custom ROM history is with a HTC device, so I may be mistaken.
Click to expand...
Click to collapse
It is possible but 99% of custom ROMs are not made to be flashed with Odin, in the past two years I've only seen about 1. And it is also inconvenient
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
itsfredo said:
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
Click to expand...
Click to collapse
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
The Sickness said:
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
Click to expand...
Click to collapse
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
I don't know if towelroot will root 4.2.2, but it doesn't install a recovery.
Rob
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
lordcheeto03 said:
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
This.
You really don't need CF Auto Root at all until all you want to do is root the stock rom.
If you want to install a customer rom, use Odin to install a custom recovery and flash whatever you want from there.
lordcheeto03 said:
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Use cf autoroot and flash clockworkmod through Odin. Download rommanager. Download a rom. Hit install rom from SD card. Pick your ROM from downloads.
itsfredo said:
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Click to expand...
Click to collapse
I understand your apprehension, i really do. What I've said to do has worked for me when i got the phone over a year ago, and has worked here recently when i did it again. I'm trying to tell you there is no need for an updated way of doing what you want. If you want root, use CFauto root. Like i said, that method was done specifically for MDB and MDL firmwares, there is no better choice. Newer yeah, but better? Not a chance. Your firmware is equally outdated and it's worked for millions of users without fail.
As far as a custom ROM goes, find one you want to use, put it on your SD card, pick a recovery (CWM, Philz, or TWRP), flash that in Odin, boot to recovery (power+volume up) , do a full wipe (system, data, and cache) select the ROM, and flash. No need to root at all if you want to go straight to a custom ROM.
EDIT: Obviously, you might want to perform a nandroid backup once you flash your recovery... but that's really optional as long as you have the stock Odin-flashable firmware. Totally up to you.
Sent from my SGH-M919 using XDA Premium 4 mobile app
So i've had my gs4mini a while now and it refuses to root.
it is i9192 (dual sim) out of box running 4.4.2. cf-root fails and i'm running out of options. I really want cm 12.1 on my device.
how can i achieve root?
is it true that i need root to install a custom recovery? like the one posted here http://forum.xda-developers.com/android/general/root-samsung-galaxy-s4-mini-dual-sim-gt-t2819284
any advice will be helpful.
niklus101 said:
So i've had my gs4mini a while now and it refuses to root.
it is i9192 (dual sim) out of box running 4.4.2. cf-root fails and i'm running out of options. I really want cm 12.1 on my device.
how can i achieve root?
is it true that i need root to install a custom recovery? like the one posted here http://forum.xda-developers.com/android/general/root-samsung-galaxy-s4-mini-dual-sim-gt-t2819284
any advice will be helpful.
Click to expand...
Click to collapse
Your goal is to use CM12.1, you can directly flash custom recovery via Odin then proceed with CM installation steps.
You don't need root to install custom recovery.
& CF-AUTO-ROOT is meant to root the devise without replacing stock recovery and trip Knox warranty status.