I have read a lot about rooting prior to the new firmware. But I just got a new Sprint S5 yesterday, and it comes with firmware NK4 (4.4.4) I tried to odin flash the firmware from NE5 (from June 2014), and that boot me into a boot loop. So i had to Flash back to the NK4 (Nov.2014). This phone has NEVER been rooted. there is NO recovery flashed either.
Are there any suggestions or walkthroughs?
Here are the firmwares available from Sprint.
2014 November = NK4
2014 June = NE5
2014 April = ND2
2014 April = NCB
CF Autoroot works but will trip the Knox counter. If you do not care about that then that is the easiest way to go. There is a walkthrough here.
Towelroot was an option on the earlier firmware (kernel) and would not trip Knox. There are ways to use Towelroot if you are on the latest kernel but it requires flashing to old kernel using Odin, running towelroot, and reloading the current kernel. There is a thread on this process here somewhere but I don't have a link. I used CF Autoroot and tripped knox the day I bought my S5.
m20120 said:
CF Autoroot works but will trip the Knox counter. If you do not care about that then that is the easiest way to go. There is a walkthrough here.
Towelroot was an option on the earlier firmware (kernel) and would not trip Knox. There are ways to use Towelroot if you are on the latest kernel but it requires flashing to old kernel using Odin, running towelroot, and reloading the current kernel. There is a thread on this process here somewhere but I don't have a link. I used CF Autoroot and tripped knox the day I bought my S5.
Click to expand...
Click to collapse
I also forgot to mention that cf autoroot just boots be up to the Sprint boot up, and then hangs!!! So cf root doesnt seem to be an option on 4.4.4 NK4.
Yeah.....after NK4, you can almost forget Towelroot. There is a method in Q&A but doesn't seem 100% for some that I've spoken with. It takes a delicate hand and will probably only work on certain phones. And although CF-AutoRoot should work, you're gonna trip Knox no matter what. You may as well trip through Odin with PhilZ Recovery or the latest TWRP. Then flash the SuperSU.zip like the old ways of the S3.
And I know every Sprint store is different, but most reps know that we are root our phones.
Towel root will work, here are the steps and the kernels you will need.
1. Download and install towel root, but do not run.
2. Use odin to install NE5 kernel below, remember to unzip it first.
3. Boot phone and just hit ok or close to all the errors that will pop up because you have the wrong kernel installed.
4. Run towel root.
5. Use odin to install the NK4 kernel below.
6. After reboot, download supersu from the play store, then udpate binaries, answer yes to the disable knox prompt.
7. Profit!!! Use Galaxy Tools to unlock hotspot, or xposed framework and Wanum to customize phone.
What's the difference between the firmware and kernels?
Stuck
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
You need to flash the kernel that matches your baseband, you can find the tar and flashable versions here
http://forum.xda-developers.com/showthread.php?p=57469564
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
dewrust said:
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
Click to expand...
Click to collapse
My baseband is nk4
xSpaceGhost said:
What's the difference between the firmware and kernels?
Click to expand...
Click to collapse
Firmware is the modem, kernel, etc. Not what you need to use towel root. All you need is the kernel to get towel root to work. If you flash the whole firmware you won't get towel root to work and your phone may not even boot.
banccalif said:
You need to flash the kernel that matches your baseband, you can find the tar and flashable versions here
http://forum.xda-developers.com/showthread.php?p=57469564
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
Click to expand...
Click to collapse
dewrust said:
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
Click to expand...
Click to collapse
First i put supersu as a zip on my sd card, thenI had to install custom recovery through odin and then installed supersu via recovery and this worked fine.
Can you post the super SU file. I did the same method but had to install supersu from the playstore.
http://forum.xda-developers.com/showthread.php?p=23427715
Here's the link to chainfires stable version. In the OP scroll done to the link for the zip file under the play store versions
I am on nk4 (4.4.4) firmware and baseband. I rooted using this method. 1. Went to download mode and unchceck auto reboot and time. 2. Odin flash 6.26.6 philz recovery. 3. Then unplugged and entered recovery (made a backup) 4. Copied superSU to phone. 5. Rooted and rebooted. 6. Rebooted and installed superSU and disabled Knox. Check with root checker. (Happy face)
glad it worked.
jpgranger said:
Yeah.....after NK4, you can almost forget Towelroot. There is a method in Q&A but doesn't seem 100% for some that I've spoken with. It takes a delicate hand and will probably only work on certain phones. And although CF-AutoRoot should work, you're gonna trip Knox no matter what. You may as well trip through Odin with PhilZ Recovery or the latest TWRP. Then flash the SuperSU.zip like the old ways of the S3.
And I know every Sprint store is different, but most reps know that we are root our phones.
Click to expand...
Click to collapse
I think I have one of these phones. Just got it on the 17th and was on NK4. Just tried towelroot after using ODIN to NE5, with and without string 1337 0 1 7380 4 0, and couldn't make it rain. At this point all I want is to be able to tether the phone. I guess I am eventually going to trip knox so why wait?
travanx said:
I think I have one of these phones. Just got it on the 17th and was on NK4. Just tried towelroot after using ODIN to NE5, with and without string 1337 0 1 7380 4 0, and couldn't make it rain. At this point all I want is to be able to tether the phone. I guess I am eventually going to trip knox so why wait?
Click to expand...
Click to collapse
You should be able to use the galaxy tools app to get tethering, not sure if it requires root or not. If that doesn't work and you don't care about trippin knox you can re-download ne5 and follow these steps below to get root & custom recovery
1. flash ne5 full tar with odin
2. download towel root, install and run to gain root (Make it rain)
3. Install supersu from play store
4. Install flashify from play store, grant root access
5. Download recovery IMG (Make sure it's IMG and not tar or zip) twrp here >> http://techerrata.com/browse/twrp2/klte
6. Open flashify for root users and select recovery image, navigate to twrp or philz custom recovery you downloaded and flash within the app
7. Open supersu and follow steps to update binaries, phone will boot to recovery and complete the update then reboot automatically
8. Enjoy your rooted device
Then you can either flash a Hotspot mod compatible with your baseband or switch to custom rom that has it enabled natively like MOAR ROM
Can't I just use auto chainfire to root and recovery from Nk4?
The only reason I was looking at a custom rom would be battery life, but wow the S5 is destroying my S4 on battery. Still might give MOAR rom a go if Lollipop isn't being pushed out by Sprint anytime soon.
Can't I just use auto chainfire to root and recovery from Nk4?<br />
<br />
The only reason I was looking at a custom rom would be battery life, but wow the S5 is destroying my S4 on battery. Still might give MOAR rom a go if Lollipop isn't being pushed out by Sprint anytime soon.<br/>
See post 14 above those steps work and then use galaxy tools for hot spot. Worked great for me. Chainfires c.f. root did not work
banccalif said:
1. flash ne5 full tar with odin
2. download towel root, install and run to gain root (Make it rain)
3. Install supersu from play store
4. Install flashify from play store, grant root access
5. Download recovery IMG (Make sure it's IMG and not tar or zip) twrp here >> http://techerrata.com/browse/twrp2/klte
6. Open flashify for root users and select recovery image, navigate to twrp or philz custom recovery you downloaded and flash within the app
7. Open supersu and follow steps to update binaries, phone will boot to recovery and complete the update then reboot automatically
8. Enjoy your rooted device
Then you can either flash a Hotspot mod compatible with your baseband or switch to custom rom that has it enabled natively like MOAR ROM
Click to expand...
Click to collapse
.
Ended up using the oneclick NE5 from here, http://forum.xda-developers.com/showthread.php?t=2787760, knox says 0x0. Made it rain, still 0x0. And then odin 3.09 for philz recovery, still 0x0. As soon as I went into recovery it triggered 0x1 but not before. In case anyone new to the phone, like myself, cares what step triggers knox.
hello guys
i have a Samsung galaxy S6 g920F running on 6.0.1 with baseband G920FXXU3DPB6.
I have previously rooted my phone using CF-autoroot. Suddenly today when i tried to use superSU, it said "There is no SU binary installed, and superSU cannot install it. This is a problem!. If you have upgraded to Android 5.0, you need to manually re-root".
As i said above that i have rooted after i updated to 6.0.1 and was working till yesterday. i don't know what happen today that it started giving me this error.
I even downloaded latest cf-autoroot from its site and flash it through odin, but still no luck.
Can anyone please help me.
Thanks.
Flash a custom recovery and a kernel and then This
Had the same issue and doing this solved it. hope it helps
Here is how I get the root access back.
1. Copy to phone SuperSU 2.72
2. Flash with Odin arter97 kernel 13.1 (it has TWRP also)
3. Reboot in TWRP and flash SuperSU.
4. Reboot the phone
turulojko said:
Here is how I get the root access back.
1. Copy to phone SuperSU 2.72
2. Flash with Odin arter97 kernel 13.1 (it has TWRP also)
3. Reboot in TWRP and flash SuperSU.
4. Reboot the phone
Click to expand...
Click to collapse
can't we use on stock kernel only as it was before instead of flashing a custom kernel..?
Hi to all
I am trying to install magisk v9 in stock ROM without any success. Always after the installation phone boot to bootloader.
The Bootloader is unlock and when I un-install the magisk v9 the phone working properly.
Any idea how we could install magisk v9
Try factory reset or another version. I had installed Magisk v7, and few days ago updated to v9.
Great finding!!!
In Stock 6045 it is possible to install magisk-v7 or Magisk-v8.
In stock 6045 (5.0.2-010 02) it isn't possible to install Magisk-v9 via Manager or temp TWRP.
In case of temp TWRP device is stack to bootloader. It is possible to uninstall Magisk to work properly or install Magisk-v8
Any idea how to overcome the issue
totalcmdext said:
In stock 6045 (5.0.2-010 02) it isn't possible to install Magisk-v9 via Manager or temp TWRP.
In case of temp TWRP device is stack to bootloader. It is possible to uninstall Magisk to work properly or install Magisk-v8
Any idea how to overcome the issue
Click to expand...
Click to collapse
root your device, install permamently TWRP and no problem then
Stuck on Android splash image during boot, after downloading and installing Magisk Manager and Apk 12.0. I was rooted through KingRoot, SuperSu installed busybox as well. I uninstalled SuperSu (through in app options) getting ready for MagiskSU.
Heres the deal. Even though I have twrp working, I cant use it cuz of a broke screen. Im thinking a factory reset via hardware buttons is my best option. But how?
6045O running the Panasonic Eluga Switch. Rooted, twrp satana 3.0.0.1 installed
I have rooted Samsung Galaxy S5 on build PA2 (downgraded from marshmallow) 5.1.1 lollipop using kingroot. Initially wouldn't work but it worked when I booted the device after being dead for days and during a flood of notifications, I ran kingroot again and during the process the device soft rebooted, which seemed like a good sign. Once I rebooted I went to kingroot again and it completed the root process (though it reported failure) but I went to root checker and it confirmed that I have root. Also on full reboot, I see on the initial boot screen a grey lock that is unlocked and the word custom right below it. I was able to successfully change my boot animation and install busybox and use other root applications. Xposed does not work! I have not found any recoveries that will work with the device so I can't do custom roms (yet). I have not checked if Knox was tripped yet. If you have the PA2 update and want to root, try kingroot, it worked for me. I have not found out how to change superuser without removing root because I dislike kingroot su, I tried doing so using supersu but supersu failed. I hope for further progress on the root of this version and some recoveries for this build.
Hey! So let me get straight to the point . . . I used Odin flashed the TWRP recovery, installed SuperSU zip, installed NexusOS-9 ROM, then installed OpenGApps. However, my SuperSU app did not show up and Root Checker says I did not successfully root my phone. I have a Samsung S6 SM-G920T. Did I "root" my phone yet? and how come it shows up as not rooted? Please help. The Custom ROM and Gapps all work but it just says not rooted. Thanks in advance!