Hey guys,
I know there are tons of Superuser apps and root methods such as cf autoroot but I'm hoping someone knows is how to root the S4 (SGH-M919) and have Koush's Superuser.apk be your SU client. I don't want to use Chainfire or SuperSU or anything else. It seems 4.3 for me will only accept SuperSU but I was hoping to use the CWM Superuser as I do on all of my other devices. Would hate to have a different SU just on this one device. Any ideas on how to get superuser.apk working on 4.3 on the S4 (Stock, custom recovery, rooted with SuperSU for now).
T-Mobile Galaxy S4 (SGH-M919)
Android 4.3 (MK2 full with KNOX through ODIN)
Don't care about tripping KNOX
Daistaar said:
Hey guys,
I know there are tons of Superuser apps and root methods such as cf autoroot but I'm hoping someone knows is how to root the S4 (SGH-M919) and have Koush's Superuser.apk be your SU client. I don't want to use Chainfire or SuperSU or anything else. It seems 4.3 for me will only accept SuperSU but I was hoping to use the CWM Superuser as I do on all of my other devices. Would hate to have a different SU just on this one device. Any ideas on how to get superuser.apk working on 4.3 on the S4 (Stock, custom recovery, rooted with SuperSU for now).
T-Mobile Galaxy S4 (SGH-M919)
Android 4.3 (MK2 full with KNOX through ODIN)
Don't care about tripping KNOX
Click to expand...
Click to collapse
Method 1
Use Odin to install a custom recovery of your choice.
Boot to recovery.
Flash any Superuser.apk you want.
Using Odin to install the recovery won't root the current ROM. It will just give you a custom recovery. From the custom recovery you can install anything you want, including the Superuser.apk of your choice.
Method 2
Root it using whatever root method works even if it installs SuperSU.
Uninstall SuperSU through the 1 click feature in the app.
Boot to your custom recovery. (Will NOT be automatically installed with CF Auto Root. You will have to flash a recovery after rooting)
Flash Superuser.
Reboot. Enjoy goodness.
Skipjacks said:
Method 1
Use Odin to install a custom recovery of your choice.
Boot to recovery.
Flash any Superuser.apk you want.
Using Odin to install the recovery won't root the current ROM. It will just give you a custom recovery. From the custom recovery you can install anything you want, including the Superuser.apk of your choice.
Method 2
Root it using whatever root method works even if it installs SuperSU.
Uninstall SuperSU through the 1 click feature in the app.
Boot to your custom recovery. (Will NOT be automatically installed with CF Auto Root. You will have to flash a recovery after rooting)
Flash Superuser.
Reboot. Enjoy goodness.
Click to expand...
Click to collapse
Hey SkipJacks! Thanks for the quick reply. Method 2 seems to be the closest for me but it seems to be a no go with Koush's SuperUser. It looks like it relies on some binaries that never download and it won't use the ones that SuperSU installs. I guess I'm gonna have to use SuperSU for now. Thanks again. I just prefer Koush's to Chains and Chainfires. Everything was working fine on 4.2.2 but from 4.3 on it's only been SuperSU.
I'm beginning to think it's broken as many people are saying the same thing.
Related
i want to root my m919 on uvuamdl
will cf auto root work on this update?
will i loose my data upon rooting
after i root my s4, i want to unroot and update back to the latest update can i do this? without my data being wiped n starting all over again, most likely use mobile odin? will my root changes still be applied, i want to add mobile data toggle
and how can i back up everything before hand
CF auto root does work with M919. I did that method. U will not lose your data with CF Auto root (using odin). U can easily unroot in the SuperUser app. If u want to install custom ROM, install a custom recovery using Goo Manager app in the play store (Team win recovery) or ROM manager (clock work mod recovery). You can backup your entire ROM using custom recovery.
Sent from my GT-I9505G using xda premium
I have an i747M, from Fido (rogers) running the stock 4.3 firmware. yesterday i tried to root it using odin to install CWM, and then CWM to install supersu.
after successfully installing supersu, i restarted the phone, and got knox blocking the app. i updated it from Play, but then i couldn't open it, and it said it can't install the binary. when my phone asked to update the security certificates, i (stupidly) agreed.
i downloaded the .zip for supersu 1.89, and tried installing that, with the same result, but this time i also can't uninstall supersu.
i've bumped my binary counter, but i'm back to basically stock now.
my goal is to install aokp. is there a way to do it without gaining root first?
if i install CWM through odin, can i flash the aokp rom from CWM?
will the phone reset the recovery?
is this risky?
You could try installing a pre-rooted Rogers rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
I was not able to find a pre-rooted 4.3 for Fido and, since you intend to install a custom rom and recovery, the pre-rooted Rogers ROM might be a good place to start.
It's there a reason to install a rooted rom before aokp? As far as I can tell, I can install aokp without rooting at all.
or am I missing something?
Sent from my SGH-I747M using xda app-developers app
Yes, you can just install a custom ROM without rooting first.
I mentioned the prerooted ROM because you post said you wanted to install su.
Ok, please confirm i have this procedure correct:
1. i use Odin to install CWM
2. boot straight into CWM
3. from inside CWM, i flash the AOKP zip file, and then the gapps zip file
my understanding is that this will keep cwm as my recovery and install aokp with gapps.
am i missing anything?
audit13 said:
Yes, you can just install a custom ROM without rooting first.
I mentioned the prerooted ROM because you post said you wanted to install su.
Click to expand...
Click to collapse
Milothicus said:
Ok, please confirm i have this procedure correct:
1. i use Odin to install CWM
2. boot straight into CWM
3. from inside CWM, i flash the AOKP zip file, and then the gapps zip file
my understanding is that this will keep cwm as my recovery and install aokp with gapps.
am i missing anything?
Click to expand...
Click to collapse
Just make sure you flash a tar version of CWM that is meant for your phone.
I can't really speak about 4.3 because I'm on 4.1.2 but the method you described is the same method I used.
Milothicus said:
I have an i747M, from Fido (rogers) running the stock 4.3 firmware. yesterday i tried to root it using odin to install CWM, and then CWM to install supersu.
after successfully installing supersu, i restarted the phone, and got knox blocking the app. i updated it from Play, but then i couldn't open it, and it said it can't install the binary. when my phone asked to update the security certificates, i (stupidly) agreed.
Click to expand...
Click to collapse
If you want to kill Konx to enable root you can flash this knox removal script: http://forum.xda-developers.com/showthread.php?t=2507931
If you are just going to flash AOKP via CWM, this may not be necessary, but this is the answer to your Knox problem.
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!!
hi;
I have a roger GS3(SGH-I747M) and recently I have updated to stock 4.4.2; then I flash cf-root throuth odin; trying to get root access; however, after I boot into the phone, I always gets a force close message on the phone and cannot get root access. Does anybody know what I can do to get root access on stock 4.4.2.
Please help!!!
Watch this: https://www.youtube.com/watch?v=AZgEVM2hSnI or search for towelroot.
TWRP or CWM?
audit13 said:
Watch this: https://www.youtube.com/watch?v=AZgEVM2hSnI or search for towelroot.
Click to expand...
Click to collapse
Towelroot seems quite easy. Once I do that, what's the best way to install latest TWRP or CWM on rooted 4.4.2? I had always heard GooManager, but now it's showing as not supported and unavailable.
No need to root. Just load a custom recovery and flash a custom ROM.
Flash recovery with odin.
pokerplayer999 said:
hi;
I have a roger GS3(SGH-I747M) and recently I have updated to stock 4.4.2; then I flash cf-root throuth odin; trying to get root access; however, after I boot into the phone, I always gets a force close message on the phone and cannot get root access. Does anybody know what I can do to get root access on stock 4.4.2.
Please help!!!
Click to expand...
Click to collapse
Like someone mentioned earlier, try flashing a custom recovery (I like philz touch myself) via odin. Once you access Recovery, if your phone isn't rooted upon trying to reboot you'll see a message that says "root priviliges may be lost, root (or something like it) binary su). Choose yes and your phone will be rooted once it boots. Install SuperSU (or kush's Superuser if you'd like) and then you'll see your phone is rooted.
I used TowelRoot and had absolutely no problems whatsoever. However, 4.4.2 seems to run extremely slow on the I747 so you might consider a custom ROM. That is the route I am looking into.
i used CF auto root to root my note on 4.4.4.
after i updated to 5.0.1 SU no longer works.
this is the error i received
"there is no SU binary installed, and SuperSU cannot install it. This is a problem! if you just upgraded to Android 5.0, you need to manually re-root.
so my question is what do i have to do you "manually" re-root?
--thanks
Odin CF auto root again. It still works. After that you can use flashify to get recovery
what is the best place to down OEM stock rom?
http://forum.xda-developers.com/showthread.php?p=59483780
abrigo74 said:
i used CF auto root to root my note on 4.4.4.
after i updated to 5.0.1 SU no longer works.
this is the error i received
"there is no SU binary installed, and SuperSU cannot install it. This is a problem! if you just upgraded to Android 5.0, you need to manually re-root.
so my question is what do i have to do you "manually" re-root?
--thanks
Click to expand...
Click to collapse
What I did was flash TWRP through odin, and then flash SuperSU from TWRP. If you get a message from SuperSU saying the su binary is out of date, update it via recovery and it will update and that message will go away.
TWRP odin tar: http://dl.twrp.me/trltespr/twrp-2.8.6.0-trltespr.img.tar
SuperSU: http://download.chainfire.eu/396/SuperSU/ Once flashed, I recommend updating it through play store and updating su binaries.
Thank you everyone for the help. I was easily able to get root back.
I have another question.
I'm not sure if this is a root issue or what, I imagine this that it is but, now whenever i touch the heart rate sensor it lights up, even when the screen is off / phone is locked. I know root breaks s heath is this the reason for the sensor being "always on"?
Sent from my SM-N910P using XDA Free mobile app