BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
That said, this will root the SM-G900T (T-Mobile Galaxy S5) no matter what version of android you're running. Make sure you read this entire post and understand everything before trying anything.
PREPARATION: Disclaimer out of the way, now for the fun stuff. First, preparation, you need to download the following files to your PC: Odin 3.11.1 (this is Odin, it flashes stuff to Samsung android phones); twrp-3.0.2-2-klte.img.tar (this is the custom recovery we're going to use). Extract the Odin zip file to your PC's Desktop. Download the file named UPDATE-SuperSU-v2.79-20161211114519.zip somewhere to your phone's internal storage or external SD, doesn't really matter which. Now in your phone's settings, go to About device, scroll down to Build number. Repeatedly tap Build number until your phone tells you Developer options have been turned on. Go back and enter developer options, enable USB debugging and hit OK. At this point you'll want to connect your phone to your PC with USB, just to make sure it actually connects (it should). If not, you can download the USB drivers from here (scroll down to Downloads section), but most likely this won't be necessary. OK prep work done, now we get to actually get started on rooting our phone. Make sure your phone has at least 50% battery, this is always a smart safety step.
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.11.1.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-2-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Please note the first boot might take a while. If after 10 minutes or so the phone has not rebooted, you should boot back into TWRP, install the supersu zip file again, and this time wipe cache and dalvik before rebooting. Otherwise the cache and dalvik wipe is not necessary. I will eventually post pictures to demonstrate all the steps in the 2nd post, and hopefully FAQs or whatever in the third post.
If you want to hit the thanks button that would be awesome, but the real credit goes to chainfire for his amazing work with supersu and really just all things root in general; and Dees_Troy for doing an excellent job developing and maintaining TWRP custom recovery for our device. They're the real heroes, I just wrote up this guide
Pictures to Demonstrate Steps
Sorry all the pictures are sideways. If you want, you can still view them by clicking the following link, file names begin with corresponding step numbers: https://www.dropbox.com/sh/wgguior3q2c6638/AAAzas50Zd-Du7jNXI3HsZU2a?dl=0
Proof I have the SM-G900T, latest 5.1.1 firmware, unmodified:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 1:
Step 2:
Step 3:
Step 4:
Step 5:
Step 6:
Step 7:
Step 8:
Proof We're Now Rooted:
FAQ's
Does this method work with the new marshmallow (6.0.1) firmware?
Yes. I have done it myself, it works
So I'm rooted now what?
Once you're rooted, you can use certain apps you would be unable to use not rooted. A few I would definitely recommend checking out: AdAway (an adblocker), Viper4Android (significantly, noticeably improve your audio quality by tweaking the settings in this app), Titanium Backup (not only backup and restore app settings, but freeze/uninstall unwanted system apps, aka bloatware), and a root-enabled file explorer such as Root Browser or ES File Explorer (with the root option enabled) is recommended. If you plan to install Viper4Android, before doing so please first flash this file in TWRP and then reboot, edit the following lines in the file /system/build.prop, and reboot again once the edits are made:
Code:
lpa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Where can I find custom ROMs for this phone?
Touchwiz (Samsung's version of Android similar to the one that comes stock with the phone) based ROMs can be found in the T-Mobile Galaxy S5 Android Development Section. AOSP (Google's original version of Android) based ROMs, such as CyanogenMod, AOKP, Mokee, Bliss, AICP, Resurrection-Remix, etc. can be found in the S5 Unified Development Section. I must warn you i can give a lot more information on the aosp based ROMs since that is my personal preference in overall Android experience, as a result my knowledge of touchwiz based development is much shakier. To each their own, and we ought to cherish android's ability to give us such a powerful freedom of choice and fight for this continued ability for our control of our personal devices against current trends of locking everything down too tight to allow for true development based innovation. Remember, when getting ROMs from this section, this phone's development name is klte (as opposed to kltevzw, kltespr, klteusc, etc.)
More info to come
Thank you very much for posting this, I just got a used S5 in the mail today and your process worked like a charm. Rooted on the first pass.
thisisapoorusernamechoice said:
Reserved, FAQ's or something
Click to expand...
Click to collapse
It works is cm stable
Sent from my LG-D851 using Tapatalk
---------- Post added at 01:09 PM ---------- Previous post was at 12:32 PM ----------
thisisapoorusernamechoice said:
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
That said, this will root the SM-G900T (T-Mobile Galaxy S5) no matter what version of android you're running. Make sure you read this entire post and understand everything before trying anything.
PREPARATION: Disclaimer out of the way, now for the fun stuff. First, preparation, you need to download the following files to your PC: Odin 3.10.7 (this is Odin, it flashes stuff to Samsung android phones); twrp-3.0.2-1-klte.img.tar (this is the custom recovery we're going to use). Extract the Odin zip file to your PC's Desktop. Download the file named BETA-SuperSU-v2.71-20160331103524.zip somewhere to your phone's internal storage or external SD, doesn't really matter which. Now in your phone's settings, go to About device, scroll down to Build number. Repeatedly tap Build number until your phone tells you Developer options have been turned on. Go back and enter developer options, enable USB debugging and hit OK, also enable Allow mock locations a couple lines below it. At this point you'll want to connect your phone to your PC with USB, just to make sure it actually connects (it should). If not, you can download the USB drivers from here (scroll down to Downloads section), but most likely this won't be necessary. OK prep work done, now we get to actually get started on rooting our phone. Make sure your phone has at least 50% battery, this is always a smart safety step.
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.10.7.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-1-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Please note the first boot might take a while. If after 10 minutes or so the phone has not rebooted, you should boot back into TWRP, install the supersu zip file again, and this time wipe cache and dalvik before rebooting. Otherwise the cache and dalvik wipe is not necessary. I will eventually post pictures to demonstrate all the steps in the 2nd post, and hopefully FAQs or whatever in the third post.
@lox2013
Click to expand...
Click to collapse
Cm 13 is instill thanks to u should get all the credit BC nobody else find out
Sent from my LG-D851 using Tapatalk
SuperSU Install?
Thank you for putting this together with simple to follow steps!
Hypothetically if someone were to accidentally swipe to install supersu at step 7 rather than just rebooting, what problem(s) does that cause?
thisisapoorusernamechoice said:
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.10.7.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-1-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Click to expand...
Click to collapse
I might should have not been doing this for the first time at 3a? How much trouble did I cause myself but letting TWRP install supersu by swiping?
Thank you again.
SethVIII said:
Thank you for putting this together with simple to follow steps!
Hypothetically if someone were to accidentally swipe to install supersu at step 7 rather than just rebooting, what problem(s) does that cause?
I might should have not been doing this for the first time at 3a? How much trouble did I cause myself but letting TWRP install supersu by swiping?
Thank you again.
Click to expand...
Click to collapse
I'm pretty sure it'll cause a bootloop, I would recommend against doing the swipe to install when twrp asks you to, saying supersu isn't installed (it is when you install the zip, twrp just can't detect it). The reason for this is something in the kernel called selinux (long story, Google it if you want the full blown details) but the short version is starting with android 5.1.1 older versions of supersu (ie the one twrp wants to install for you automatically) usually cause a bootloop. The supersu zip file I link to in my post is specifically designed to avoid this issue. Thanks for reminding me, I wanted to put this question in the FAQ section. It's an important issue and something anyone who wants to know a little more about android should be aware of
thisisapoorusernamechoice said:
I'm pretty sure it'll cause a bootloop, I would recommend against doing the swipe to install when twrp asks you to, saying supersu isn't installed (it is when you install the zip, twrp just can't detect it). The reason for this is something in the kernel called selinux (long story, Google it if you want the full blown details) but the short version is starting with android 5.1.1 older versions of supersu (ie the one twrp wants to install for you automatically) usually cause a bootloop. The supersu zip file I link to in my post is specifically designed to avoid this issue. Thanks for reminding me, I wanted to put this question in the FAQ section. It's an important issue and something anyone who wants to know a little more about android should be aware of
Click to expand...
Click to collapse
Thank you for your quick and helpful response. So if my phone is booting now, with supersu installed, does that mean I am good to go?
Bootloop may be what happened. After awhile, I pulled the battery, booted back into TWRP and reinstalled the supersu zip file. I did not wipe cache or dalvik but I also did not swipe to install supersu. My phone now boots and acts fine other than showing "Set Warranty Bit : kernel", but I think that is expected, correct?
SethVIII said:
Thank you for your quick and helpful response. So if my phone is booting now, with supersu installed, does that mean I am good to go?
Bootloop may be what happened. After awhile, I pulled the battery, booted back into TWRP and reinstalled the supersu zip file. I did not wipe cache or dalvik but I also did not swipe to install supersu. My phone now boots and acts fine other than showing "Set Warranty Bit : kernel", but I think that is expected, correct?
Click to expand...
Click to collapse
The Set Warranty Bit: kernel thing is normal, that's just your phone telling you it's rooted (I mean it's technically telling you the kernel has been modified, in this case only just to allow for supersu to be installed). As long as you're booting fine, that's what's important. Thanks for the feedback, and I hope I've been helpful
thisisapoorusernamechoice said:
The Set Warranty Bit: kernel thing is normal, that's just your phone telling you it's rooted (I mean it's technically telling you the kernel has been modified, in this case only just to allow for supersu to be installed). As long as you're booting fine, that's what's important. Thanks for the feedback, and I hope I've been helpful
Click to expand...
Click to collapse
Yes, very helpful, thank you.
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
VICIOUSVIC1 said:
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
Is confirm I rooted my gf phone the s5 5.1.1 it works she running cm 13 most stable rom
Sent from my SM-N920C using Tapatalk
VICIOUSVIC1 said:
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
FYI, I don't know of any Custom ROMs that are not already rooted. Rooting is only needed for Stock ROMs.
Rob
Trying with FOL, downloaded via the link provided here. After installing TWRP, i have to remove the battery to get the phone to turn off. It still acts as if it were being updated, and the power button does not work. Taking out the battery, putting it back in, and pressing vol up, home, power brings up twrp.
After hitting install, the zip file fails:
<<<<<<<<<<<
Updating partition details...
...done
Full SELinux suppot is present.
MTP Enabled
Installing zip file ' /external_sd/._BETA-SuperSU-v2.
71-20160331103524.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Error installing zip file '/external_sd/._BETA-
SuperSU-v2.71-20160331103524.zip'
Updating partition details...
...done
<<<<<<<<<<<
About Device shows the baseband version: G900TUVS1FOL1
I'm probably just doing something wrong. With some help, i'd like to try again.
trips KNOX
thisisapoorusernamechoice said:
BACKGROUND: Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
Click to expand...
Click to collapse
not good to trip KNOX from what I understand. maybe there can be included in this a way to remove KNOX? I know I posted this comment in another post that linked to this. I thought I was on the right post. sorry. OH and What is Kies and how is that pronounced?
musterion1973 said:
not good to trip KNOX from what I understand. maybe there can be included in this a way to remove KNOX? I know I posted this comment in another post that linked to this. I thought I was on the right post. sorry. OH and What is Kies and how is that pronounced?
Click to expand...
Click to collapse
Knox is Samsung's indicator if your phone has ever had a non-stock kernel installed. Currently there are very few pieces of software - Samsung only - that check this flag. One may be Samsung Pay. However, it doesn't cause any other problems with any other parts of Android. And, doesn't keep you from turning your phone back it, etc.
KIES is the software that Samsung supplies to flash updates, make backups, etc.
You can find it here: http://www.samsung.com/in/support/usefulsoftware/KIES/
Rob
SethVIII said:
Yes, very helpful, thank you.
Click to expand...
Click to collapse
When i hit the install supersu when twrp asked me i was put in a bootloop like thispoorusernamechoice said. I learned my lesson though?
I am a thank you slut.lol
rlichtefeld said:
Knox is Samsung's indicator if your phone has ever had a non-stock kernel installed. Currently there are very few pieces of software - Samsung only - that check this flag. One may be Samsung Pay. However, it doesn't cause any other problems with any other parts of Android. And, doesn't keep you from turning your phone back it, etc.
KIES is the software that Samsung supplies to flash updates, make backups, etc.
You can find it here: http://www.samsung.com/in/support/usefulsoftware/KIES/
Rob
Click to expand...
Click to collapse
Thank you Rob.
---------- Post added at 04:02 AM ---------- Previous post was at 03:15 AM ----------
thisisapoorusernamechoice said:
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
twrp-3.0.2-1-klte.img.tar (this is the custom recovery we're going to use).
Click to expand...
Click to collapse
twrp-3.0.2-1-klte.img.tar 10.6M
twrp-3.0.2-1-klte.img 10.6M
do I need both of these or just the very top one. I downloaded both ? in the event they are bother needed. but what one will we be using here Sir or Ma'am.
Yes this will trip Knox said:
did not seem to trip KNOX. so how di I remove KNOX altogether?
Click to expand...
Click to collapse
musterion1973 said:
twrp-3.0.2-1-klte.img.tar 10.6M
twrp-3.0.2-1-klte.img 10.6M
do I need both of these or just the very top one. I downloaded both ? in the event they are bother needed. but what one will we be using here Sir or Ma'am.
Click to expand...
Click to collapse
You just need the twrp-3.0.2-1-klte.img.tar 10.6M
Related
Here is a way to gain root if you all ready have the latest NH5 or NK2 firmware on your phone.. This way you dont have to revert back to an older complete firmware. This method also does not wipe out any of setting or mods that you may have done before you decided to root, like ringtones, clock settings, alarm settings, notifications etc.... If you update to the latest firmware and you use wanam or xposed, You will have to re install the framework from xposed to get all you settings restored. Once you install the Xposed framework you will have to restart the phone, all the modules should be restored to the way it was before you did the update.....This method should not trip Knox.
Before you try this method, you should disable Lookout apk and go into settings-general-security and uncheck verify apps, also put a check on unknown sources, then under security policy updates, uncheck the update box, also make sure to uncheck send security reports. This should prevent any hang ups while trying to install super user apk and disabling knox hang.
After you get root and back on NH5 or NK2 you can go back and put those checks back only if you plan on using the Knox security stuff, but it is not necessary if you dont. It does not affect anything you do with your phone anyway. This is up to you to decide. HAPPY ROOTING.. LOL
Thanks goes to @iworkout for pointing it out, as i did not run into the hang under superuser install for i just automatically do this when i root a phone without thinking.
.
.
1. Download these files to your computer and unzip them.. (ATTENTION,,, These boot.tar are not the bootloader.tar that everyone thinks it is. These are just boot.img (Kernels) needed to root and return back to latest stock with root.)
A- NE6 Boot.Tar----- NE6 BOOT.ZIP<<<< This is the kernel to root with.
.
B- NH5 Boot.tar------ NH5 BOOT.ZIP <<<< Earlier firmware before NK2, you only need to use this if you want to stay on NH5 otherwise skip this one..
.
C- NK2 Boot.tar------ NK2 BOOT.ZIP <<<<< This is the latest TMO Firmware as of 11/10/2014.
Download these files to your phone:
.
C- Download Towel Root from here ( TowelRoot ), and SuperSu ( from the Play Store) to your Phone..
2. Once you have the files unziped, Open up PC ODIN 3.09 which you can get here PC ODIN 3.09 .
.
3. Once you have opened up PC odin, click on AP and load the NE6 boot.tar.md5 file into the slot.
.
4. Put your phone into Download mode, By powering off the phone and holding the volume down and home button at the same time and press the power button, once you see the phone start to boot let go of the power button and you phone should go to download mode, Make sure you press the volume up button to enter download mode.
.
5. Connect the phone to the computer, Make sure the PC ODIN sees your phone, (If not make sure you have the latest drivers loaded.) Once PC odin sees your phone and you have the file loaded in the AP slot, you can go ahead and start the flash, this should only take about 30 seconds to complete and the phone should reboot. Once your phone reboots you should have NE6 Kernel loaded onto you phone. You shouldnt have any fc's ( as i did this and did not have any FC's).
.
6. Once your phone reboots click on Towel root and click on " Make it Rain". Your phone should now have root, You can close towel root,
.
7. Open up SuperSu and install the Binarys into your phone, Make sure you click Normal install and not CWM/TWRP. You then will be prompted to Disable knoxs, You click yes, (I clicked disable and have had no side effects.) You will have to reboot to make sure Super user takes effect. You can check to see if you have root by downloading root checker of your choice from the playstore.
7a, If you some reason you get an error saying the super user failed to install, Dont worry, just reboot your phone and and re run super su apk and you will see that it actually did install super user, you can verify by using root checker to verify. You do not need to restore your phone back to stock and start over.
.
8.Once you verified that you have root, You can now go back to step 3 and load the NH5 or NK2 Boot.tar.mds into the AP slot of Odin, and follow steps 4- 5. That is it. You now should be back on the latest NH5 or NK2 kernel and have root. You can check by usng root checker and to see if all your info, you can download Samsung Phone Info from the playstore, and this will show you all the files and knoxs should be 0x0.
.
Here is the full T-Mobile Stock NK2 Rom, Just in case you have to Odin back to stock if you mess up after you root and or want to take the Official update, But be warned that Official updates from any carrier may block Root.
.
Download------ Stock Full NK2 Rom 11/10/2014.
Here is the full T-Mobile Stock NH5 Rom, Just in case you have to Odin back to stock if you mess up after you root and or want to take the Official update, But be warned that Official updates from any carrier may block Root.
.
Download------ Stock Full NH5 Rom.
If you are having issues with odin failing, I would try a different cable, one that is not usb 3.0. I have read on the forums that some people have been having issues with odin failing due to the new usb 3.0 cable that samsung has issued with the Galaxy S5. Most people are using computers that are not able to support 3.0 usb, and this may be an issue for some with odin. This is just an idea so it may or may not work for you. If it still fails i would try a different usb, maybe one on that is on the back of a desktop instead of one in front, and maybe a different computer all together..
.
.
I only use a windows (Currently using Window 7) / linux pc to do most of my work on android. So i know this method and odin works. It seems that some users are having issues with mac and odin, so be carefull. Personally if you plan on working on android you should purchase a cheap windows pc or laptop. Plus you can dual boot a win pc to do linux as well. Linux is what i use to do alot of my cooking of roms with. So if you are using an apple product to do your flashing, than unfortunatly I can not help you with that.. Sorry.
.
Now remember that I am not responsible if you void your warranty or if you break your phone. This method worked for me and i found it easier and quicker this way. If something did not work then you did something wrong or did not read the instruction correctly.
.
If this method helped you in any way please hit the thanks button .. If the Mods would like to make this a sticky, please do. Thanks
Can anyone confirm that this works
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for posting this method - I just got a new S5 that came with NH5 and was about to try it, but the files you linked to don't match the files in your description.
"NE6 BOOT.ZIP" links to a file called "NE6Kernel.zip"
In Step 3, you say it should unzip to "NE6 BOOT.IMG" but instead the file is "boot.tar.md5"
The same goes for your NH5 link & the file inside.
Should I just ignore the mismatched file names and follow the same instructions?
iworkout said:
Thanks for posting this method - I just got a new S5 that came with NH5 and was about to try it, but the files you linked to don't match the files in your description.
"NE6 BOOT.ZIP" links to a file called "NE6Kernel.zip"
In Step 3, you say it should unzip to "NE6 BOOT.IMG" but instead the file is "boot.tar.md5"
The same goes for your NH5 link & the file inside.
Should I just ignore the mismatched file names and follow the same instructions?
Click to expand...
Click to collapse
Yes just ignore the file names and follow the steps. Cause inside the zip they are correct file name--- Boot.tar.md5 is actually a kernel that you are installing to get root. And pc odin does not reconize any other name but boot.tar.md5. I tried to rename the files and odin rejected it. So when you unzip the Boot.Zip, you know whats inside of that folder. Also renamed the files in op to make it less confusing..
.
If This helps you please hit the thanks button..
galaxyuser88 said:
Yes just ignore the file names and follow the steps. Cause inside the zip they are correct file name--- Boot.tar.md5 is actually a kernel that you are installing to get root. And pc odin does not reconize any other name but boot.tar.md5. I tried to rename the files and odin rejected it. So when you unzip the Boot.Zip, you know whats inside of that folder. Also renamed the files in op to make it less confusing..
.
If This helps you please hit the thanks button..
Click to expand...
Click to collapse
Done. It worked exactly as you described. Only hiccup was when SuperSU first attempted to disable KNOX, I got a message in my notification panel, "Security notice: unauthorized actions have been detected - reboot to undo changes."
My phone came with Lookout security installed, so I don't know if that had anything to do with it. I went to task manager and stopped Lookout and SuperSU (which just seemed to be hanging) and ran SuperSU a couple more times. It said KNOX disabled on the 2nd run.
Rebooted & installed root checker, verified root, installed NH5 in Odin and then verified root again. Thanks!
iworkout said:
Done. It worked exactly as you described. Only hiccup was when SuperSU first attempted to disable KNOX, I got a message in my notification panel, "Security notice: unauthorized actions have been detected - reboot to undo changes."
My phone came with Lookout security installed, so I don't know if that had anything to do with it. I went to task manager and stopped Lookout and SuperSU (which just seemed to be hanging) and ran SuperSU a couple more times. It said KNOX disabled on the 2nd run.
Rebooted & installed root checker, verified root, installed NH5 in Odin and then verified root again. Thanks!
Click to expand...
Click to collapse
Yeah i didnt have that issue, as soon as i got the phone i disabled that lookout crap. Also already had the security check also disabled, as when you install apks from outside the playstore, you are told to disable the security checks.
I will have to add that to the op when i get home and at my laptop.
It works
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Works!
nguyener said:
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Click to expand...
Click to collapse
This was my only hangup, as well. Beyond that, everything went smoothly, and I have root access with no Knox trip.
nguyener said:
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Click to expand...
Click to collapse
AndreTheShadow said:
This was my only hangup, as well. Beyond that, everything went smoothly, and I have root access with no Knox trip.
Click to expand...
Click to collapse
Yeah that is something with superuser and not the method. Maybe when they upgrade the supersu apk, it may correct that. But good to see that this helped out to acheive root for ya.
Thx worked like a charm. SuperSu did hang when i tried to disable knox. I just rebooted and used SuperSu again and it disabled with no problems. Now if someone could just point me to the volume boost hack I will be good. I cant find it for the life of me.
So by clicking "Disable Knox" will that prevent me from using ALL the apps like PayPal with FINGERPRINT login & Google Wallet to tap & pay? Isn't Knox also needed for private mode?
On the flip side, what if I click "NO" & keep Knox enabled? Can I still root? Will Knox counter be tripped?
Will this affect my ability to upgrade to Android L via normal stock method?
Does this affect anything like that negatively? I'm having trouble searching the internet for hours about these fine details. Thanks for this awesome bit of info!
Hypoxic1 said:
So by clicking "Disable Knox" will that prevent me from using ALL the apps like PayPal with FINGERPRINT login & Google Wallet to tap & pay? Isn't Knox also needed for private mode?
On the flip side, what if I click "NO" & keep Knox enabled? Can I still root? Will Knox counter be tripped?
Will this affect my ability to upgrade to Android L via normal stock method?
Does this affect anything like that negatively? I'm having trouble searching the internet for hours about these fine details. Thanks for this awesome bit of info!
Click to expand...
Click to collapse
Iam not sure what will not work if disable knox. I dont use anything that might need knox, so i can not help you there. I have had no negative affect from disabling knox.
You can always try it and see what happens. The worst thing you will have to do is odin back to stock and try again. This is how i found disabling knox did not affect my phone or the apks i use in anyway. Yes you can choose not to disable knox and you will still have root.
As far as upgrading, you can do it 2 ways.
1. Odin back to stock and take the upgrade. But be warned that if you take a stock update, you may lose the ability to root, if the update closes the holes.
2. You can wait for one of the great devs to take the update and clean it and post it in xda. This is the safer bet.
Thank you for the quick & informative response! I really do appreciate your time.
Hmm, I took the plunge & CAREFULLY read, re-read, re-read again to be sure of the instructions. It keeps giving me a fail now. When I click START in ODIN, it's like it doesn't wait for the phone to do it & gives me the fail. When looking at the phone, I can see the line/bar thing drawing from left to right & before it is finished "drawing" that line, ODIN gives me the fail. Great...
OK, got it to work by downloading the FULL 1.5GB files from another thread. But I still used YOUR instructions. Whew! What a task.
LOL, wow I messed up. Now I'm back on NH5 & it unrooted. OK, so now I've redone it again & back on a ROOTED NE6. I'm afraid to try the NH5 since it failed before & bricked my phone. Not sure how to proceed.
Hypoxic1 said:
OK, got it to work by downloading the FULL 1.5GB files from another thread. But I still used YOUR instructions. Whew! What a task.
LOL, wow I messed up. Now I'm back on NH5 & it unrooted. OK, so now I've redone it again & back on a ROOTED NE6. I'm afraid to try the NH5 since it failed before & bricked my phone. Not sure how to proceed.
Click to expand...
Click to collapse
Ok why did you go back to ne6? If you all ready were on nh5, than my methods works perfectly, except for a hiccup in su. Seems like you did something wrong. I would load the full factory stock nh5 rom thru odin and try my method again. This only works on a full nh5 stock rom. If you were on some other firmware(older) then trying to upgrade to nh5 with my file will not work. It is only the kernel and not the whole rom. Hence the title.
If pc odins fails before you start, then it sound like the drivers are not loaded correctly, or one of the files you downloaded is corupt. Check to make sure the md5 matches and or redownload the files again, and try to use chrome to download. Afh seems to have issues with other explorers. Dont ask cause i do not have a clue as to why. Also if you continue to have issue, i would try a different usb port, different cable and or a different pc.
I know this method works. For i have done it about 20 times, i like to flash stuff on my phone to see what works.
I did start with a new phone with NH5, but your method didn't take as stated in my prior post. I was extremely careful to follow the directions properly, as well. I just got this S5 brand new from T-Mobile the other day & already had latest NH5 on it.
So to UNBRICK my phone, I had to use the method by ashraf sharif (http://forum.xda-developers.com/tmo...tutorial-towelroot-onlatest-firmware-t2908019). But I'm afraid to proceed to updating to NH5 using his method, hence why I'm on NE6 at the moment.
Hypoxic1 said:
I did start with a new phone with NH5, but your method didn't take as stated in my prior post. I was extremely careful to follow the directions properly, as well. I just got this S5 brand new from T-Mobile the other day & already had latest NH5 on it.
So to UNBRICK my phone, I had to use the method by ashraf sharif (http://forum.xda-developers.com/tmo...tutorial-towelroot-onlatest-firmware-t2908019). But I'm afraid to proceed to updating to NH5 using his method, hence why I'm on NE6 at the moment.
Click to expand...
Click to collapse
If you are afraid to use my method, then purchase mobile odin pro and use that to upgrade to nh5. Read the thread were you got the full ne6 and follow his directions. I honestly can not understand what the issue is that you are having. Cause like i said before, I have done a full odin back to nh5 and used my method with no issues. My phone also came with NH5 from tmo. Sorry.
No, no. Don't be sorry. You're awesome for posting all this & helping me out. I have no idea why it did not work also since I've made no mods up to this point. I carefully read everything & did days of research prior to jumping into this on this phone. This sure isn't as easy as a Nexus device! I basically have OCD when I do this sort of stuff, so I carefully read every word many, many times.
Thanks for the "go ahead" tip on the mobile odin pro. I will do that since you recommend it. I'm just unsure how he states the bootloader needs to be flashed separately. I'm a bit scared of PC odin at this point, lol.
Hypoxic1 said:
No, no. Don't be sorry. You're awesome for posting all this & helping me out. I have no idea why it did not work also since I've made no mods up to this point. I carefully read everything & did days of research prior to jumping into this on this phone. This sure isn't as easy as a Nexus device! I basically have OCD when I do this sort of stuff, so I carefully read every word many, many times.
Thanks for the "go ahead" tip on the mobile odin pro. I will do that since you recommend it. I'm just unsure how he states the bootloader needs to be flashed separately. I'm a bit scared of PC odin at this point, lol.
Click to expand...
Click to collapse
That is why i figured out my method, too many steps with the other thread. I orignally did it his way many times on my phone and it does work, just alot of steps and it takes alot longer to flash and root and then flash again.. The problem with mobile odin pro is it doesnt flash all the files that a stock rom has in it, this is why you need to flash some files with pc odin and then the rest with mobile odin pro..
I have noticed that many have been willing to take the NK1 4.4.4 update and give up root access. Therefore I am putting this out there for those that have not done so but are considering doing so if they are able to keep root.
The following process will allow you to update to NK1 4.4.4 and keep root. However once updated to NK1 you will not be able to downgrade back to 4.4.2. If you screw something up after updating, e.g. while performing a mod, and have to flash back to stock you will permanently lose root access (unless an exploit is found in the future)! With that said I believe all of you are capable of making your own decision as to whether or not to proceed at your own risk!
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
Instructions:
1. Extract the N900V_NK1_Stock_Rooted_Firmware from the .rar and place it and the N900V_NK1_Stock_Partitions onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash firmware package" then locate and select the N900V_NK1_Stock_Rooted_Firmware. FlashFire will scan the firmware which may take several minutes to complete. Press "ok" once the md5 is confirmed then make certain that both "Boot" and "System" are selected. Press the checkmark to continue.
5. Press "(+)" again then press "Flash Zip or OTA" and locate and select the N900V_NK1_Stock_Partitions. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
6. Press “(+)” once again to bring up “Actions” and select “Wipe.”
7. Under the “Options” menu select all partitions except “Internal storage” then press the checkmark to continue.
8. From the main menu Tap-hold-drag your "Actions" and place them in the following order:
- "Wipe"
- "Flash firmware package"
- "Flash ZIP or OTA"
(leave default settings under "EverRoot" and "Reboot" options)
9. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flashes. Once complete your device will reboot and pause on the Verizon splash screen for two to three minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Changelog: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-galaxy-note-3-1-7-15.pdf
Notes:
1. The above process will not affect your User Data or Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to NK1.
3. To update to factory stock(unrooted) NK1 flash the N900VVRUDNK1_N900VVZWDNK1_N900VVRUDNK1_HOME.tar using Odin's PDA slot(AP in Odin v3.09+).
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Could anyone confirm if this works?
Everyone is too scared to try haha! I am sorry, but I will not do anything to my device unless there is an exploit found. Verizon and Samsung, just go away...
vazersecurity said:
Everyone is too scared to try haha! I am sorry, but I will not do anything to my device unless there is an exploit found. Verizon and Samsung, just go away...
Click to expand...
Click to collapse
There is no need to apologize, everyone should make their own decisions based on their own criteria. But this is an option for those that choose to take it.
muniz_ri said:
There is no need to apologize, everyone should make their own decisions based on their own criteria. But this is an option for those that choose to take it.
Click to expand...
Click to collapse
is not work my friend , am going try with NC4 , Kernel Unified_KK_Firmware
jmontalvo248 said:
is not work my friend , am going try with NC4 , Kernel Unified_KK_Firmware
Click to expand...
Click to collapse
If you are talking about downgrading you are right and someone else already confirmed that you cannot downgrade the kernel to NC4 after updating to 4.4.4. This thread is for those that have not yet updated to 4.4.4.
The VPN data disconnects would be enough to throw $20 to make sure this works. Can tell you how annoying that is when working from my phone.
nosit1 said:
The VPN data disconnects would be enough to throw $20 to make sure this works. Can tell you how annoying that is when working from my phone.
Click to expand...
Click to collapse
Putting a stock ROM together is rather straightforward so I'm pretty certain it works. And it's been downloaded 65 times so I suspect people are using it but for some reason choose to remain anonymous which is fine. But it would be nice to hear from someone that has tried it. Also, no donations are required but thank you nonetheless.
My safestrap (Safestrap-HLTEVZW-NC2-3.75-B04.apk) does not permit me to backup or restore anything. Can I perform the upgrade with wiping my user data?
twistedpos said:
My safestrap (Safestrap-HLTEVZW-NC2-3.75-B04.apk) does not permit me to backup or restore anything. Can I perform the upgrade with wiping my user data?
Click to expand...
Click to collapse
Sounds like there is a problem with your current installation of safestrap. Since safestrap is critical to this process I recommend that you reinstall safestrap or even consider reflashing NC4 and safestrap before proceeding.
Why does the download from US mirrors take 6 hours? I have a relatively fast PC and quite fast video card. Thanks!!!
alt230 said:
Why does the download from US mirrors take 6 hours? I have a relatively fast PC and quite fast video card. Thanks!!!
Click to expand...
Click to collapse
Neither of which have anything to do with your network speed or the server's network bandwidth and load.
Sent from my Note 3 via Tapatalk
alt230 said:
Why does the download from US mirrors take 6 hours? I have a relatively fast PC and quite fast video card. Thanks!!!
Click to expand...
Click to collapse
rofl
Works!
1. Did a full backup in Safestrap
2. Erased everything
3. Flashed N900V_NK1_100% rom
4. Restored just the /Data from backup
5. ODIN rebooted into download mode, ap > N900V_NK1_Stock_Kernel
5. Took 5 mins to come up, upgraded apps, had to close the setup wizard
6. System > 4.4.4 and Root status is still working!
Thanks much for this!
Awesome....this worked for me as well. Thanks!
Did exact same thing and Google play store keeps F/C....any suggestions?
gobucks41855 said:
Did exact same thing and Google play store keeps F/C....any suggestions?
Click to expand...
Click to collapse
Make sure google play services is up to date.
OPINIONS
would you rather have a stock rooted 4.4.4 rom and delete bloatware and do tweaks on your own or stick it out with 4.4.2 and run a custom rom by a developer?
xlylegaman said:
would you rather have a stock rooted 4.4.4 rom and delete bloatware and do tweaks on your own or stick it out with 4.4.2 and run a custom rom by a developer?
Click to expand...
Click to collapse
Be careful deleting apps which may cause stability issues due to dependencies. I recommend freezing apps instead.
Could this help find an exploit for those of us that took the update?
Sent from my HTC6435LVW using Tapatalk
This is for both US Cellular Samsung S6 and S6 Edge variant. Thanks also goes to @g.lewarne for his work on Unikernel as a couple of their ramdisk/kernel commits were needed to get this going. Also, thanks to @datajosh for this template And @bpdev for testing the 925R4 version...
This will trip KNOX. It will. Trip. KNOX. IF YOU HAVE NOT TRIPPED KNOX YET - THIS WILL TRIP IT. ALSO - you CANNOT downgrade after you take the OTA so be sure you want it.
I hope that's clear enough?
Instructions:
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Reboot in to download mode (Power + Home + Volume Down)
Use ODIN to flash 925R4root.tar or 920R4root.tar (depending on your device)
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent.
Downloads
925R4 - http://1drv.ms/1HeDWXO
925R4 Source
920R4 - http://1drv.ms/1NUVJ8B This is untested...I did not have a tester for this version....
920R4 Source
The 925R4 version may or may not work with the Sprint 925P variant...no working data confirmed!
ENJOY!
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
cpfeifer said:
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
Click to expand...
Click to collapse
You could go back to the stock kernel, but you would loose root. Also as stated above you would trip knox.
someone on a sprint s5 edge said the only thing they noticed didnt work was data..just posting for them since they under 10 post..so thats awesome! if we could get data goin..we can have root!!
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
this kernel has working data on the edge...if you could port the data stuff in yours it should be fine http://forum.xda-developers.com/spr...t/5-1-1-stock-of7-kernel-root-7-4-15-t3150350
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
borxnx said:
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
Click to expand...
Click to collapse
It should be flashed using ODIN...I believe I updated the link in the OP to fix that issue since I derp'd...
Sent from my SM-G920P using Tapatalk
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
sintro said:
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
Click to expand...
Click to collapse
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
cpfeifer said:
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
Click to expand...
Click to collapse
I reflashed back to stock, then installed supersu. Then opened it up, obviously it said "supersu binary not installed". Next, I flashed this kernel and once booted up supersu still repeats the previous message. In addition, root checker shows that phone is not rooted.
The only thing in the .tar file, for 920r4 at least because that's all I downloaded, is a modified kernel. Nothing about SuperSU or its binaries. This method alone does not root. This merely installs a modified SELinux permissive stock kernel. More steps are necessary to obtain root. You must flash either CF Auto Root or a custom kernel + SuperSU.zip.
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
borxnx said:
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
Click to expand...
Click to collapse
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
Thank you for redoing the ramdisk.
Will try out and let you know.
Anyone experiencing issues with 925r4? I have service but see no signal bars no matter where I go.
https://youtu.be/y7EpSirtf_E
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
This does indeed work. Thank you so much!
Edit...Added instructions I used to complete the root process.
First of all, I wanted to thank the OP of this thread for posting this guide and getting me headed in the right direction.
Credit to @djvoleur
I just wanted to share the method I used to root my USC Galaxy S6 with the Android 5.1.1 update. You will notice that the instructions are similar in the beginning. I added the extra steps that I used to complete the root process. I do not know if this method works for the Edge version.
As the OP states: This will trip knox. Personally, it doesn’t matter to me. I am too impatient and too much of a flash-a-holic to wait for a method that doesn’t trip knox.
Also, I am not a dev and I am unable to answer any questions other than how I obtained root. I am not responsible for any damage that might happen to your phone. Follow this procedure at your own risk.
Having stated these disclaimers, it really isn’t very difficult to implement. I’ve done it twice and both times worked perfectly.
Files you will need for flashing in Odin:
Odin 3.10.7 found here: http://tinyurl.com/puyq4v9
Rooted kernel 920R4root.tar found in the OP.
TWRP 2.7.8.0 (Sprint version, but I can confirm it worked for me. YMMV.) Here: http://tinyurl.com/phvrkaf
Files for flashing in TWRP:
Updated V-Kernel 920R4-071615.zip found here: http://tinyurl.com/o2h8rv4
Super SU v2.49 (beta) found here: http://tinyurl.com/or6mmqr
Now, PLEASE read these instructions before starting so that you will have a good understanding of what to do. After reading, you may begin.
Don’t forget to put the files for flashing in TWRP on your SD card (phone) before beginning this process.
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Boot into download mode (Power + Home + Volume Down)
Use ODIN to flash 920R4root.tar
Use ODIN to flash TWRP and make sure that reboot is NOT checked in options.
Unplug the phone and hold the Power + Volume Down key to reboot. When the screen goes blank, quickly hold the Power + Home + Volume Up key to boot into TWRP. If it doesn’t boot to TWRP, you may have to start over.
In TWRP flash the updated V-Kernel file first, then the Super SU file, and then reboot.
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent. (Worked for me.)
You now should be able to install Chainfire's Super SU app from the Play Store, and you can also use Root Checker to confirm you are rooted.
Good Luck!
Would this work on G920R7... J4 (rather than OF7) 5.1.1? That's what I have.
I see there is a PC1 update available also for my G920R7 which is 6.0 marshmallow.
Hard to believe I've had this device for a year with no root... Anyone can help me get this rooted? Thanks!
so after installing the intial kernel that did not work I scrolled through and saw the updated version...you should probably update the link for the untested r4 to the working version later posted...
my problem is that Im unable to load in anything but download mode due to kernel not seandroid enforcing basically not enabling me to load into recovery mode so I need the zipped version of the kernel to install via odin in download mode if possible otherwise im waiting on a 2 hour download of the stock kernal to install
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
en11gma said:
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
Click to expand...
Click to collapse
Use TB to remove the update apps - green phone icons in TB. That's how it always gets stopped on any samsung.
Below, not only will you find step by step instructions on how to root your device but also a FAQ section in post #2 that will guide you through the problems most of us encountered in the beginning. It is highly recommended that you read through all of it. Basic knowledge of ADB is required and if you don't have it then you should definitely read the FAQ section for ADB set up. Make sure you have all the files downloaded.
Update 10/25/2016: Attached at the end of this thread is a modified debloat script for knox removal and a few other apps. This will make your root experience a heck of a lot smoother than before. Just flash the zip using FlashFire without changing any settings. You may notice a reboot or two. There are few bloatware apps that will still be there (amazon shopping, amazon videos, amazon photos, etc) that you'll have to remove manually. Happy flashing and don't forget to hit that Thanks button down below!
Disclaimer:
This root method is NOT for beginners. It is NOT easy. If you don't get it then DON'T do it. Especially if you're worried about voiding the warranty and blah blah blah. Simply put, don't do it if you don't have the slightest idea of what you're doing. I'm tired of complaints. This guide is not for the faint of heart. Do this at your own risk!
Package Disabler Pro is required to get this rooting method working. Yes, it costs money ($.99) but it's the way I acheived this work around at the moment.
Be prepared to lose data (LTE) connection but don't be scared as it's an easy fix.
Make sure you don't have Secure startup set up before you start the process. Having this set up causes issues.
Must have ADB set up and installed system-wide.
This root method should be used with PE1 firmware for both the GS7 and the GS7 Edge. Although this root method might work with the latest firmware, users have been reporting issues dealing with APN's on the newest update. Look at post 2 FAQ's returning to stock for flashing PE1 firmware through Odin.
Do not update to PJ2 if you want to keep service with your root. Phone calls and text messages won't come through after rooting on PJ2.
Files you will need:
Odin by Princecomsy: http://d-h.st/gsDA
G935A: http://d-h.st/kDWz (S7 Edge)
G930A: http://d-h.st/o3hm (S7)
SuperSU: https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
Click on the BLUE "download" links. Extract everything into a folder easy to locate.
Here we go:
After downloading and getting set up Package Disabler Pro, you'll need to disable the following three packages:
samsung dm phone interface
samsung dm service
securityLogAgent.
Use the search box to easily find these packages.
Power off your device and boot into download/bootloader mode by pressing and holding the volume down, home, and the power button. Press volume up to get into bootloader.
Open PrinceComsy odin and flash the engineer boot.img by clicking AP and navigating to the file for your model. Click start and your device should reboot by itself.
Enable developer options by going to Settings>About Device and tapping Build Number till it shows Developer mode has been turned on. You will now have Developer options under the settings menu.
Enable USB debugging in the Developer options settings.
Extract the SuperSU zip and run the root.bat file. Your phone will reboot if the script is successfully ran.
Next, we'll get LTE data back:
Method A: BuildProp Editor (easiest method)
Open Build.Prop with BuildProp Editor and change the following settings:
ro.cdma.default_numeric=310000 to 310120
ro.cdma.default_alpha=Chameleon to Sprint
ro.build.characteristics=Chameleon to Sprint
Make sure you grant root permissions when it asks. You may have to try this twice. Reboot and LTE should stick.
Method B: Manual activation (also if you're not able to make any calls)
Enable the three packages disabled in step 1. Go into the phone dialer and type in ##72786# and your phone should reboot and begin the activation process. After the 5th retry, it will manually activate itself. It should say "writing to device". Don't click done yet. Press the home button and disable the three packages once again. Reboot.
Alternatively, after renabling the three packages and dialing ##72786#, you can go into Settings>Activate this device and manually try to activate it yourself. It still must say "writing to device". Don't click done. Disable the packages once again. Reboot. Voice and LTE should stick.
Download S7_or_S7Edge_Fixes_V15.zip to your internal or external storage and install install FlashFire from the playstore.
Open FlashFire and let it acquire root access. Click the + button at the bottom right corner then click on Flash ZIP or OTA. Navigate and select the S7_or_S7Edge_Fixes_V15.zip. file. Leave the options alone and click the check in the top right. Scroll down to the bottom and click flash. Your phone will reboot and flash the zip. This can take a while.
Go to Settings>Lock screen and security>Other security settings>Security policy updates and turn off "Automatic updates" and "Wi-Fi only". Reboot. This seems to be the culprit of the 7 day soft brick.
Open back up Package Disabler Pro and search for "software update". Disable both packages (com.sec.android.soagent and com.wssyncmldm)
Enjoy your rooted device with minimal to almost no lag.
???
Profit.
As always, be sure to donate to the people who actually helped achieved root: @Princecosmy, @br3w3r, and @Chainfire
For the bounty donate to [email protected] PayPal
Shout out to @psouza4, @izzibew26, @mhill1986, @LeftyGR, @Soooperstar, and to all of you who are contributing in making this root method easier everyday. Thanks for the feedback.
Originally, it started getting interesting at post #185:
http://forum.xda-developers.com/att-galaxy-s7/how-to/bounty-att-s7-root-exploit-t3341274/page4
I'm also keeping track of the Sprint Galaxy S7 Edge (SM-G935P) version:
http://forum.xda-developers.com/sprint-s7-edge/how-to/root-t3410424
FAQ's:
My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Download BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Credit goes out to: @guaneet for this fix
Can I install Xposed?
A: Yep. Here's how to do it:
fnztakedown said:
Alright. Here is a DB link of the two files I had installed to get xposed working. To flash this you will need flashfire.
Process is simple. Download both files and install the apk.
Open flashfire> select flash new file> find the xposed zip, flash. Give it a solid 5-7 minutes during boot up.
Ensure you do not have any major packages disabled and ensure you have BACKED UP YOUR ROM VIA FLASHFIRE. Please be aware, this was successful for me on the 935T and I do have random reboots at time. I cannot confirm this is the cause yet. I would also suggest finding the uninstall zip in the event you have issues you can flashfire back.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/sh/0yabdfx6ao69dpd/AAAnu-9Jv8W9stjjuG1Nq5jba?dl=0
Click to expand...
Click to collapse
Credit goes out to: @fnztakedown for these instructions
I'm having issues with ADB. Any help?
A: Easiest way to install ADB and its subsequent drivers would be to get it from here:
http://forum.xda-developers.com/showthread.php?t=2588979
It's SO easy to install and it takes most if not all of the hassle out of it.
Credit to @Snoop05 for this easy ADB installer.
How do I enable USB debugging?
A: Go to Settings>About device and tap Build number until it shows Developer options has been enabled.
I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. If you keep on getting stuck at the LTE splash screen you may have to factory reset your device. As soon as your phone restart quickly press the volume up + home + power button and let it boot into recovery. Wipe data/factory reset and cache partition.
I'd like to unroot and return to factory stock. How would I go about this?
A: Head on over to @psouza4's post HERE and follow his steps in the return to stock section. The steps are easy and he's posted mostly all the firmware.
[*]Does this method trip Knox?
A: No, it doesn't. And flashing back to stock will allow Knox to work again, as long as you didn't flash files from other sources (there are some that will trip Knox, so be careful).
[*]Does Samsung Pay work?
A: No, sorry. They can detect the rooted boot environment through a driver, so you can't even hide root from the app using RootCloak.
[*]Does Android Pay work?
A: It does, but you have to make a change that disables root and then reboot your phone. You can toggle this back/forth without flashing, but you either get root or Android Pay at any one time.
[*]What happens if I brick my phone?
A: As long as there are stock images to flash back to, it's almost impossible to do this no matter how badly the process goes. Check that we have stock images; if we do, then we can always flash them over the device using the unroot method in this guide. That practically guarantees a return-to-stock experience for a phone as long as it doesn't have any serious physical damage preventing it from powering on.
[*]I installed the ADB system-wide on my Windows computer/laptop, but I see "'adb' is not recognized as an internal or external command, operable program or batch file".
A: Your user profile path can't contain a space. That means if your Windows user is 'Somebody Nice' and thus your Windows user path is 'C:\Users\Somebody Nice', the install will fail. You can create another user on your computer (if prompted for a Microsoft login, choose to make only a local account) and enter a short, single-word name for your user. Sign into and use that user profile instead. Also, the path where you extract the SuperSU package can't contain a space, so try extracting them to somewhere simple like perhaps C:\S7Root.
More answers to FAQ's to come.
colormedroid said:
Just got home to test this out. Currently on PC5 since I've been waiting for this day to come. Will post back once I have results.
Just flashed the engineering boot.img. Make sure you boot into BOOTLOADER mode when using odin to flash this because the instructions don't show this. Also, make sure to back up all your stuff because most likely this will involve a factory reset.
Update #3: So, seems like our variant seems to have issues with the activation process. Here's what I did to fix it. It's a temporary fix until it gets figured out completely but it's a fix none the less.
1. Flash engineer boot.img through odin.
2. Factory reset/wipe
3. Go through the setup process without actually activating (once it gets to the activation screen press and hold the back button).
4. I signed into my google account through wifi and I downloaded Package Disable Pro+ Samsung (https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpremium). Yes it costs money but it's the way I achieved this work around at the moment.
5. I went into settings>Acitvate this device.
Don't click "done" after it gets activated.
6. Press the home button to get to the main screen and open up Package Disabler Pro+ Samsung
7. After Package Disabler Pro is set up... I searched for Samsung DM Service and I disabled it.
Voila! No more rebooting. Like I said, this is hopefully temporary until it gets figured out.
Now on to installing SU. I will post back with pictures of Root Checker.
Update #4: Installed SU through the root.bat file in the instructions. Took a screenshot of root checker. Here it is in all it's glory.
http://imgur.com/FHvak9Z
Almost forgot to mention that it seems that the engineer boot.img does lag the system a little bit so again, try it at your own risk. I for one will be trying this out like I have with all my older devices. Next step is Adaway =D.
Click to expand...
Click to collapse
I can't believe it! Have you tried to install adaway and xposed yet? You said the system lags a bit, is it laggy enough that it would become frustrating after using for a few minutes? I'm still on my Galaxy S5 and just deciding whether I should head to the Sprint store today or not.
slickdealers said:
I can't believe it! Have you tried to install adaway and xposed yet? You said the system lags a bit, is it laggy enough that it would become frustrating after using for a few minutes? I'm still on my Galaxy S5 and just deciding whether I should head to the Sprint store today or not.
Click to expand...
Click to collapse
Adaway installed successfully. Haven't installed xposed but someone said that you could do it through flashfire. That might have to wait for tomorrow as today is the 4th. M'urica!
*whoops, forgot to quote you my bad.
Sent from my SM-G935P using Tapatalk
It works
I tried it and it works also have adaway installed through f Droid
Can i install this update?
Sent from my SM-G930P using Tapatalk
You should NEVER install an over the air update if you want to keep root. Always get your updates from xda.
Sent from my SM-G930P using XDA-Developers mobile app
sml2004 said:
View attachment 3803555
Sent from my SM-G930P using XDA-Developers mobile app
Click to expand...
Click to collapse
Good job getting it working!
Sent from my SM-G935P using Tapatalk
colormedroid said:
Good job getting it working!
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
Now I guess we need Hotspot mod. And a damn sd card fix. Lol
Sent from my SM-G930P using XDA-Developers mobile app
Has anyone tried this on PF2? I honestly had to update and have been taking updates, because this is one ****ty sluggish phone. It seems to get worse the longer I have the S7. This is much like what happened with the S6, so root would be appreciated to alleviate it.
mafaesto said:
Has anyone tried this on PF2? I honestly had to update and have been taking updates, because this is one ****ty sluggish phone. It seems to get worse the longer I have the S7. This is much like what happened with the S6, so root would be appreciated to alleviate it.
Click to expand...
Click to collapse
Pf2 works
Sent from my SM-G930P using XDA-Developers mobile app
---------- Post added 5th July 2016 at 12:22 AM ---------- Previous post was 4th July 2016 at 11:50 PM ----------
Could someone drop their stock feature.xml file here?
Sent from my SM-G930P using XDA-Developers mobile app
I lost service. But I have root. I am Sprint. I thought that if I left SimCard in unlike with my S6, I would have service, but no. It has none. How do I fix it
I have SM-G930P that is still on APB5 can I do the process with APB5 or is there some other step that I have to do?
Thanks in advance!!
BTW, OP thanks for putting this thread together!
CharmedWhovian said:
I lost service. But I have root. I am Sprint. I thought that if I left SimCard in unlike with my S6, I would have service, but no. It has none. How do I fix it
Click to expand...
Click to collapse
Read post #2 please.
Sent from my SM-G935P using Tapatalk
treepog said:
I have SM-G930P that is still on APB5 can I do the process with APB5 or is there some other step that I have to do?
Thanks in advance!!
BTW, OP thanks for putting this thread together!
Click to expand...
Click to collapse
No problem. ?
This should work on APB5. Just make sure to read post #2 for activation problems.
Let me know if y'all need any help!
Sent from my SM-G935P using Tapatalk
Gear VR
I saw on AT&T bounty thread that gear vr may break. Can anyone confirm that this happens?
I have been waiting for root, using my S5 for things that I need root for. I do not want to lose the VR 3d video player and games I play just for root.
N3Cr0 Cr0W said:
I saw on AT&T bounty thread that gear vr may break. Can anyone confirm that this happens?
I have been waiting for root, using my S5 for things that I need root for. I do not want to lose the VR 3d video player and games I play just for root.
Click to expand...
Click to collapse
Actually, I was very happy that the Gear VR was still in action. So much so, that I did not notice that my Mobile Network State was Disconnected.
CharmedWhovian said:
Actually, I was very happy that the Gear VR was still in action. So much so, that I did not notice that my Mobile Network State was Disconnected.
Click to expand...
Click to collapse
haha, made me lol.
Sent from my SM-G935P using Tapatalk
Crap, now I went from having no service, to Avtivate Bootloop to Logo Bootloop. I rather have no service. I can't leave out of the house without music. wth do I do
Updated. I am now back to stock. but for a weird reason, Mobile Network state is still disconnected.
This tutorial gets your MetroPCS Grand Prime (model SM-G530T1) root, a deodexed and bloatware-free TouchWiz, 'fairly stock' ROM, and Xposed Framework. This method will likely work on the T-Mobile variant because much of this is actually intended for that variant... but no guarantees. If you do, indeed, attempt this with a non-MetroPCS variant, please let me know your model number and if it works or not so i can add it to the compatibility/incompatibility list.
Known compatible variants:
SM-G530T1 - MetroPCS
This tutorial comes with no guarantees or warranties. I am not responsible if you brick your device or for any damage caused by following this tutorial. You can most likely recover any problems you find along the way by simply flashing back to Stock with Odin, but I can't guarantee that you will be able to. This is true of basically everything on XDA, so no surprises here.
I estimate the entire process taking less than a half hour, assuming that everything goes as expected, and that you don't need to flash back to stock first.
There is one caveat... the TrapKernel method fully roots the device, but it trips Knox. If you don't want to trip Knox, don't use this method. As an alternative, if all you want is some minor root functionality, KingRoot will give you SOME root functionality, but not enough to install Xposed, or to do many things that a true root gives you. KingRoot can be found here: SITE / DOWNLOAD
At any time, even if you brick your device, you can probably always flash back to Stock. Here is the Stock MetroPCS SM-G530TI 5.1.1 ROM: THREAD / DOWNLOAD
Alright... without further adieu, here are the files you will need:
Odin SITE / DOWNLOAD
ShinySide's TrapKernel for SM-G530T THREAD / DOWNLOAD
DUHAsianSKILLZ's deodexed and bloatware-free ROM for SM-G530T: THREAD / DOWNLOAD
Chainfire's FlashFire SITE / DOWNLOAD
Xposed Installer THREAD / DOWNLOAD
TWRP 2.8.7.0 (for lollipop) THREAD / DOWNLOAD
Custom Xposed Framework for Samsung Lollipop THREAD / DOWNLOAD
Got all the files you need? Here are the steps:
1. On your phone, boot to Download Mode by booting your device while holding down the Down Volume and Home Button, then hitting Volume Up. Connect it to your PC. If your PC doesn't recognize the phone, you need to install drivers. There are lots of threads out there with tutorials on how to do that. This tutorial assumes you already have the drivers.
2. On your PC, open Odin, Click the "AP" button, Select the file: TrapKernel_G530T_AOF8_Root.tar.md5. Flash it. Let the phone boot normally. If it doesn't load after a few minutes, pull the battery and reboot. If it continues to get stuck on boot, it probably failed. Flash back to Stock and try again.
3. On your phone, once it fully boots up, download Chainfire's SuperSU from the Play Store. You'll need it in order to authorize the root app in the next step.
4. On your phone, download FlashFire from the Play Store at the link above, or if you have the APK, install it. Open FlashFire and authorize SU permissions. Hit the + button, then Wipe. Check System data, 3rd party apps, Dalvik cache, Cache partition, and Cache partition format, then click the Checkmark on the top-right to confirm. Now hit the + button again, then Flash Zip or OTA. Select GwizRomSMG530T-V1.1.zip, then click the Checkmark on the top-right. Now click Flash. The screen will go off during this step... DON'T WORRY. It will take about 10 minutes total to boot for the 'first time'. This ROM basically removes Knox, retains root, and frees up a lot of resources that Samsung was using for useless bloatware. Even if you stopped at this step, your phone will be MUCH better off than with a purely Stock ROM on it. I noticed a HUGE performance improvement after installing this ROM.
5. On your phone, install XposedInstaller_3.0_alpha4.apk.
6. On your phone, open FlashFire. Tap the + button, then Flash Zip or OTA. Find TWRP_2870_Samsung_SM_G530H.zip and flash it. This one takes a little while to load, so be patient. I would say, if you're at the 10 minute mark after tapping Flash, it probably failed so pull the battery and reboot. If it continues to happen, you'll likely need to flash Stock and start over completely.
7. The phone will boot back to your home screen. Once it does, restart it and go into Recovery Mode by booting the phone while holding the Volume Up and Home buttons.
8. Once in Recovery, tap Install. Find and choose the file xposed-v86.0-sdk22-arm-custom-build-by-wanam.zip and swipe the slider at the bottom to Install Xposed.
9. Once it finishes flashing and boots back up, you're good to go. Full Root. Bloatware-Free. Really fast. With Xposed.
10. One last thing, I would install an app like NoBloat or something to disable or delete the app com.tmobile.pr.adapt. It doesn't like that you rooted your device and will start acting up. The reason a T-Mobile app is there is because the bloat-free ROM you installed in step 4 above is based on a T-Mobile Stock ROM, not MetroPCS. You don't need it. It will ask for root permissions all the time, use cell data, and deplete your battery. Just disable it if you are not comfortable fully deleting it. I would also look into disabling/deleting some of the other apps like some of the Samsung stuff, but you'll have to research what is safe to remove. I know the com.tmobile.pr.adapt app is pointless and a data/battery hog.
Well then thanks for putting this together. Now everything is in one spot. Well done.
Sent from my SM-G530T using Tapatalk
after flashing "TrapKernel_G530T_AOF8_Root.tar.md5" Phone reboots fine, but wifi doesn't works anymore, I repaired it with SmartSwitch, reloading the firmware back to Stock.
bullracing said:
after flashing "TrapKernel_G530T_AOF8_Root.tar.md5" Phone reboots fine, but wifi doesn't works anymore, I repaired it with SmartSwitch, reloading the firmware back to Stock.
Click to expand...
Click to collapse
How did you end up doing that? I couldn't figure out how
you mean, how to restore to stock?
Download Smatch by Samsung, the use theere option "MORE" and go to "EMERGENCY SOFTWARE RECOVERY AND INTIALATION" there Switch will ask you phone the phone model and the SN number to get the original or Stock firmware to it
No... went to root my Samsung Galaxy Prime to remove bloatware
Help
GwizRomSMG530T-V1.1.zip will not install, there are 2 options to check on the flash screen, should I leave those blank or check them?