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..
Related
Three new tools have been released or updated by their developers recently that may have a major impact on how we root and flash our phones. I will need to update the Guides with the new information, but first some confirmations are needed.
1) Chainfire has released a tool called Mobile Odin which will flash roms from the phone. There are two versions, Mobile Odin Pro which is available on the market for a small fee, and Mobile Odin Lite which is available free to xda members. Quoting from his thread: Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear. This tool was updated today (November 28, 2011) to work with a host of new phones, including SGH-I777.
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
3) CLShortFuse developed SuperOneClick Root over a year ago, and recently updated it (November 10, 2011) to include the ZergRush exploit and SU 3.0.
With these tools, if they work as advertised on our phone, it will be possible to root and install custom software without incrementing the flash counter. When you have used one or more of these tools, I would appreciate it if you would post your results back here in this thread so I can gather information to update the [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!!
Thanks.
I have used the new version of SuperOneClick with the zergRush exploit to successfully root my SG2. However I will mention that the Unroot feature of SuperOneClick did not work. I simply used the unroot script DooMLoRD provided in his thread and I was able to unroot successfully. I am currently still unrooted as I have a business app I have to run that will not if it detects root. However, I assume either SuperOneClick or DooM's script will work once again if needed.
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
lambition said:
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
Click to expand...
Click to collapse
No. At some point we may figure it out to reset it through software, but until then only jigs reset the counter.
Sent from my páhhōniē
I recently noticed after flashing to UnNamed that the caution sign didn't appear. Has the ROM been developed to not trigger it or does it have to do with using the jig? I bought a jig a month ago from mobiletechvideo and I've only used it once. I've flashed CM7, Galnet MIUI and UnNamed since with no caution sign.
These tools will probably provide a new way to flash custom software without incrementing the flash counter. None of them will remove the warning triangle or reset the flash counter, however.
The only two ways to remove the warning triangle, and get the AT&T boot screen back, are 1) jig and 2) flash a stock kernel with Odin or Heimdall.
The only known way to reset the flash counter is with a jig.
The only thing that causes the I9100 boot screen with the warning triangle and increments the flash counter is flashing a custom kernel with Odin or Heimdall. So, you can flash with adb or Android Terminal Emulator or ClockworkMod Recovery, or appearantly with the new Mobile Odin, without incrementing the flash counter.
I'm definitely interested in hearing about peoples results using these tools. That is the main purpose of this thread. Thanks.
I used the DooMLoRD method, which is really easy, and it's been working for several weeks with no issues. I haven't needed to unroot, so haven't tried that yet.
[Edit] I haven't tried flashing a new rom, so I can't comment on the flashing without triangle. I just wanted root for a couple small issues, I'm going to wait to start flashing until some stable releases of ICS start appearing.
I've used SuperOneClick with Zerg to root, then installed Entropy's Daily Driver through Android Terminal then flashed UnNamed through CWM all without tripping any counters.
Love it!
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Thanks for sharing
avidmovies said:
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Click to expand...
Click to collapse
The guide is still good. I'd like to provide all the options though.
At this point, it is clear that rooting with either SuperOneClick or ZergRush will be part of step 2 in the guide, and may be easier than using Odin or Heimdall.
Still waiting for any information on Mobile Odin. If it's easy to use on our phones, it may be an improvement over steps 3 and 4.
Thanks!
Sent from my Nexus S 4G using Tapatalk
Used the zergrush root and then mobile odin to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
gr8hairy1 said:
Used the zergrush root and then mobile odin lite to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
Click to expand...
Click to collapse
Did you use lite or pro?
Could you describe using Mobile Odin, setting it up, how the flashkernel works, etc?
I downloaded the zergrush root package from the op. Then went to (edit):
http://forum.xda-developers.com/showthread.php?t=1347899
and downloaded mobile Odin lite.
First downloaded Samsung kies for the proper drivers then downloaded and opened zergrush. When you first open zergrush by opening 'run me' (i think it was called) it will tell you everything you need to have already done before plugging in your phone. It recommends changing your screen timeout to 10. I'm guessing this is for adb use, as adb can not connect to your phone if the screen is off.
I then plugged the phone in and pressed a key for it to start. All in all it took around 5 minutes. Majority of the time was processes coming up that waited 40 seconds. Guessing the phone was doing things that you couldn't see. At no time did I need to press anything on the keyboard or phone.
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case out would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on.
That gives you this screen:
{
"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"
}
After that:
The only main option is kennel, and that's all I neededafter choosing it I got:
It was stored on the root of my internal sdcard, so I selected internal and then seen:
It obviously automatically put the kernel at the top by itself. Picked it and then had:
Chose flash kernel, rebooted the phone, and it was done. Downloaded unnamed, used three button hold to get into recovery, sure enough CWM was there, chose unnamed. Rebooted and viola, custom rom. Through this whole process the boot screen never changd to i9100 with the yellow exclamation point or was the flash counter tripped.
Sent from my páhhōniē
(yeah, I typed that all on my phone, talk about a sore hand)
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
gr8hairy1 said:
I downloaded the zergrush root package from the op. Then went on the android market and downloaded mobile Odin lite.
Click to expand...
Click to collapse
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
...
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case it would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on...
Click to expand...
Click to collapse
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
iainash said:
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
Click to expand...
Click to collapse
Yeah buddy! Need to put that step in there.
Though I'm a yengling fan
Edit: lol, just seen my guinness spelling error. Nice to know swype appreciates a good beer
Sent from my páhhōniē
creepyncrawly said:
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
Click to expand...
Click to collapse
You're right, I downloaded it from xda. Not sure how I got that mixed up. I'll update my post. Though I had taken a vicodin, alieve, and 2 benedryl around 1am, and it was almost 2am when I posted that. Stupid butt surgery is kicking my butt.
And correct, I did not download his flashkernel. I was tempted to flash it to check out what it did but it wasn't my phone I was working on. I stuck with flashing what I knew would get me cwm, and flashed Entropy512's kernel. Flashed with no issue.
Sent from my páhhōniē
creepyncrawly said:
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
Click to expand...
Click to collapse
First I wanted to say THANK YOU for all your help. I was able to follow your guide to flash my phone with out incrementing the flash counter.
But before I did that I did try DoomLoRD root fix. It worked as advertised and was exactly how the instructions were documented. I had no issues.
Again big thanks to you for all your help!
JUST THOUGHT I WOULD TOSS THIS UP IF ANYONE NEEDS IT, THERE IS A COPY IN BLOATWARE LISTS !!!
First what version of KIKAT are you on ? If you are on 4.4.4 NH7 or NK4 the latest upgrade then you can root with Chainfires CF-autoroot or his SuperSu v 1.94, v2.02 or 2.40 this will trip KNOX warranty. Towel Root will not work yet for NH7 or NK4. If you are still on 4.4.2 NC5 then you can use Towel Root to root your device, this will NOT trip KNOX warranty. If you root with Chainfires CF-autoroot or his SuperSu v 1.94 or v2.40 this will trip KNOX warranty on NC5. If you want odin flash a fresh copy of 4.3 NAB, 4.4.2 NC5, or 4.4.4 NH7 here is micmars link http://forum.xda-developers.com/showthread.php?t=2712205 or rpenrod23 [ odin ] (mirrors )http://forum.xda-developers.com/showthread.php?t=2522638 for NK4 and OC5 you will need to go here http://www.sammobile.com/firmwares/ . Make sure you have USB drivers installed on your PC here is the link http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
How to flash a fresh copy of a stock OS
1. download the version of KitKat you want to the desktop of your PC.
2. extract zip file to the desktop of your PC it will turn it into a .tar file
3. you need to install Samsung drivers on your PC you can get them from here http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
4. download odin to your desktop here is the link ( version 1.85 ) https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo ( version 3.07 ) http://www.mediafire.com/download/2uxt5u83qxhz6xr/Odin_v307.zip
5. completely power down device, reboot into download mode (hold power button, home button, and volume down button at the same time, then push the volume up button)
6. open odin on desktop, connect device to PC via USB cable COM: will light up in upper left corner of odin doesn't matter what color it is just shows a connection.
7. click the PDA button a box will open click on desktop then on KitKat file to open
8. now don't touch anything else and click start
9. it will take several minutes, then say pass, and automatically reboot device with new OS/ROM ( this will take 3 to 4 min. after you see Samsung logo )
10. Important !!! If the device was rooted or you are trying to downgrade from NH7 or NK4 back to NC5 the device may bootloop on the startup. ( you will know this when the Samsung logo is still on the screen after 6 to 7 min. )
11. to fix bootloop pull battery then reinstall, boot into download mode and use odin to flash the OS/ROM again it will take the second time and boot up.
Let's root the phone, there is a couple of ways. First if you are running NC5 4.4.2 you can download Towel Root directly to the device here is the link http://towelroot.org/ The second way if you are running any version of KitKKat is to use odin to flash the cf-autoroot .tar, just download cf-autoroot here is the link http://autoroot.chainfire.eu/ to your PC desktop and follow the same instructions listed above just use the root file in place of the rom .tar file. Remember to choose the right root file for the version of KitKat you running so you don't trip KNOX !!!
Recoveries, the two popular ones are TWRP and Philz CWM. INSTALLING A RECOVERY WILL TRIP KNOX WARRANTY!!! You need a recovery to flash roms so you need to make choice at this point ? Here is the link to Philz CWM latest version 6.48.4.tar http://forum.xda-developers.com/showthread.php?t=2201860 and TWRP here http://teamw.in/project/twrp2/201 download to desktop or downloads.
I run a stock rooted 4.4.2 NC5 with Philz custom recovery version 6.12.9 hltespr https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ . The device was rooted and warranty tripped the second day I owned it. I was in a Sprint corporate Store a couple of wks ago. Showed the tech my rooted note 3. He said I can't touch that, I said what if I unrooted the phone. He said no problem, now I can warranty the phone. He didn't care that the KNOX flag was tripped at all 0x1. Just can't be rooted when you bring it in for service. Sprint doesn't care about KNOX only Samsung cares about KNOX. What is KNOX, KNOX is a program that creates secure encrypted containerization of DATA so it can be sent to another location. So, when Samsung paid millions to the NSA to design the KNOX security containerization system, which apparently they won't warranty will work after the device is rooted, than maybe they care. Can you say track and spy on me !!!
Ok lets install a recovery !!!
1. you need Odin on the desktop of your PC here is the link ( version 1.85 ) https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo ( version 3.07 ) http://www.mediafire.com/download/2uxt5u83qxhz6xr/Odin_v307.zip
2. you need to install Samsung drivers on your PC you can get them from here http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
3. completely power down your device, and boot into download mode (press and hold the power button, volume down button, and the home button at the same time) a new screen will popup then push the volume up button to get into download mode.
4. click on the Odin zip file and extract to desktop, right click and run as administrator
5. with your device in download mode connect it to your pc via usb cable, COM: will light up in the upper left hand corner of Odin doesn't matter what color or number just shows a connection has been made.
6. click PDA box in odin, a box will popup click where ever you have recovery file downloaded, once open it will show up in box next to PDA
7. click start wait till you see pass and success , then your custom recovery is installed.
After the recovery is installed, download a copy of SuperSu to your desktop here is the link http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip to version v2.40 and for SuperSU 2.46 go here http://forum.xda-developers.com/showthread.php?t=1538053 . Then copy and paste to sd card via USB cable. Now the next thing you are going to do is completely power down the device and boot into recovery. (press and hold the power button, volume up button, and home button at he same time) a menu will come up, click on Install Zip, then sd card to install zip and root device. Boot device and verify it is rooted, then power down, and boot into recovery. Click on backup, MAKE A BACKUP OF YOUR ROOTED ROM !!! Then make a backup of EFS file by its self it will show up in your backup file on the sd card or ext sd card depending on where you choose to put it. Copy and paste the efs file someplace safe.
With the Google Play Store download some type of root file manager like ES File Manager or Root Explorer (what I use). Then you can remove/freeze/delete some of the bloatware on your stock rooted rom. Check out this thread on Bloatware removal http://forum.xda-developers.com/showthread.php?t=2770729
OK lets flash a rom !!!
First, you CANNOT flash a rom that is based on an older version of rom you are currently running. EX: If you are on KK 4.4.2 NC5 you can flash a rom based on NAB or NC5 but you CANNOT use a rom based on mj4 or older read the OP thread carefully . You can run AOSP roms as long as they are based on 4.4+. If you are running a KK 4.4.4 based rom, you will need to odin flash a stock lollipop 5.1.1 OS. Then root the lollipop 5.1.1 OS, install a lollipop compatible recovery. Now you can flash a lollipop based rom.
1. install the new rom zip you want to flash on your sd card via usb cable from PC or download directly to device
2. power down phone completely and boot into recovery
3. from the menu find and wipe cache, delvik cache, and wipe system to install new rom, NOT FACTORY RESET !!!
4. go back to menu and click on install zip then click on where you have the zip ( i.e. sd card ) and install this will take a minute or two
5. back to main menu and reboot device this will take several minutes on the first boot of a new rom
6. enjoy your new rom !!!
Lets do a restore from a backup recovery file !!!
1. completely power down device and boot into recovery
2. go to main menu and click on wipe system to install new rom ( no need to mess with the caches on a restore )
3. back to the menu click on back up and restore, then click on the backup file location ( i.e. sd card )
4. now click on restore
5. when its completed reboot device this will install your original rooted stock rom you made a backup for
Eventually you will figure out that you can make several backups and they have really weird numbered time stamps to identify them.
If my instructions are hard to follow you can find root and recovery installation videos here http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Malware in linked odin site
That odin site is complete malware. Its not where you should get odin.
juts said:
That odin site is complete malware. Its not where you should get odin.
Click to expand...
Click to collapse
Thanks, that just happened. Looks like the site has been hacked !!!
jimzweb1 said:
Thanks, that just happened. Looks like the site has been hacked !!!
Click to expand...
Click to collapse
I have a Note 3 locked to Sprint which announce "Invalid SIM card" everytime I get the sim in and of course it doesn't have network. So I have a question 4u that after flashing this ROM am I possible to use the SIM (I'm from VN) ?
3597dxta said:
I have a Note 3 locked to Sprint which announce "Invalid SIM card" everytime I get the sim in and of course it doesn't have network. So I have a question 4u that after flashing this ROM am I possible to use the SIM (I'm from VN) ?
Click to expand...
Click to collapse
No, it's my understanding the device has to be unlocked by sprint. There is an access code to do that, I have seen it just can't remember where. I will do a little searching.
Should make a noob tutorial since people are still confused.
asim.sidz said:
Should make a noob tutorial since people are still confused.
Click to expand...
Click to collapse
I guess if people are still confused, there are a lot of youtube videos that have walk-throughs as to how to root, install recovery, and flash a ROM. Maybe some people might be visual learners?
asim.sidz said:
Should make a noob tutorial since people are still confused.
Click to expand...
Click to collapse
If my instructions are hard to follow you can watch these videos http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Great work Jimmy
Pretty lucid , these tutorials are
great stuff !!!
Cool!
jimzweb1 said:
If my instructions are hard to follow you can watch these videos http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Click to expand...
Click to collapse
Thank you very much! I cannot imagine the process to get any easier than the way demonstrated in the ways that you directed me. Really appreciate it! Thanks again! Keep up the good work and support! :highfive:
I am on 4.4.4 NH7, how can i downgrade to 4.4.2 NC5?
i am facing gps fix issues...so wanted to give it a try. any ideas?
swapyworld said:
I am on 4.4.4 NH7, how can i downgrade to 4.4.2 NC5?
i am facing gps fix issues...so wanted to give it a try. any ideas?
Click to expand...
Click to collapse
You can't and you shouldn't . Flashing nc5 might brick your phone that's why we all believe one should always wait for a few weeks before jumping on a new ota as downgrade is not possible
Sent from my NOTE 3 .. size does matter .......
lord dredd said:
You can't and you shouldn't . Flashing nc5 might brick your phone that's why we all believe one should always wait for a few weeks before jumping on a new ota as downgrade is not possible
Sent from my NOTE 3 .. size does matter .......
Click to expand...
Click to collapse
My phone came with 4.4.4, that's the problem.. I was told it is possible by odin one click method by r wilco?
Sent from my SM-N900P using Tapatalk
swapyworld said:
My phone came with 4.4.4, that's the problem.. I was told it is possible by odin one click method by r wilco?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
First, if your device came with 4.4.4 NH7 it should be possible to down grade to 4.4.2 NC5. However, is the phone new and under warranty ? If so odin flashing back to NC5 won't trip the knox e-fuse, that happens when you install a custom recovery. Here we go, first BACK UP ALL YOUR DATA TO AN EXT SD CARD OR PC !!! ( i.e. pics, music, videos etc.) From my post here is the link for odin https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo download to PC desktop. Then go to micmars and download a copy of NC5 here is the link http://forum.xda-developers.com/showthread.php?t=2712205. It is a zip file so just right click and extract it to your desktop, that will change to a .tar file in a folder. Next extract the odin zip to your PC desktop, and open the odin file as administrator. Now connect your device to your PC via a USB cable. A box will light up in the upper left hand corner COM: doesn't matter what color it is just shows a connection. Now click on the PDA box a new window will open up click on desktop then click on the NC5.tar file to open. Then the file show up next to the PDA box don't touch anything else just click start. Sit back go get a coffee it is going to take few minutes.
Now here is the fun part, if your phone boots up GREAT !!! If it doesn't, and bootloops no problem this common when going back to NC5 it happened to me. Just pull the battery, then reinsert battery, and boot into your stock recovery ( hold the power button, volume up button, and menu button at he same time) once there navigate to factory reset with the volume button and click on factory reset with power button. Finally the phone should boot into NC5, now go to settings/general/about phone and see what version you have.
If you are still on NH7 no problem, it didn't stick go through the process again. Others have had the same thing happen to them, and it took the second time, in the end it's worth it.
I had all kinds of problems on NH7 and so have many others, I went back to NC5 and have had no problems, I'm going to stay here and wait till android 5.0 (lollipop) comes out. Enjoy !!!
Jimzweb1
You sent me here for the thread "How to root Galaxy Note 3".
Thing is, I know how to use CF Auto Root, but I'm pretty green even at that. Maybe a total of 10 phones for my family.
I took root off a Note 3 (sm-n900p) by upgrading to the new firmware (NK4). It was having issues and he wanted to go back to a stock. Now he needs root again and chainfire doesn't list a file for the NK4.
Chainfire says he needs a image file from the update to add to his list, but I do not have it. He also states that in most cases, root will work on the new firmware. But if does not, that's where things go black, what to expect and how to recover?
And from what I read, I can't go back to an early firmware?
Your help would be greatly appreciated, thanks.
btb601 said:
Jimzweb1
You sent me here for the thread "How to root Galaxy Note 3".
Thing is, I know how to use CF Auto Root, but I'm pretty green even at that. Maybe a total of 10 phones for my family.
I took root off a Note 3 (sm-n900p) by upgrading to the new firmware (NK4). It was having issues and he wanted to go back to a stock. Now he needs root again and chainfire doesn't list a file for the NK4.
Chainfire says he needs a image file from the update to add to his list, but I do not have it. He also states that in most cases, root will work on the new firmware. But if does not, that's where things go black, what to expect and how to recover?
And from what I read, I can't go back to an early firmware?
Your help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
First you have a S5 not a note 3 but other than size they are basically the same. Read the post above yours, the same thing will probably happen to you don't panic !!! I have to go to work will be back tonite if you want to wait so I can help as you do it or you can try it yourself even you loop it (like what happened to me and most people ) don't panic just follow the instructions in post # 14. You need a clean copy of NE5 go here enter SM-G900P in search on right, you will have to register but its free , I don't see a XDA site for stock NE5 so here is the link http://www.sammobile.com/firmwares/ enjoy !!!
jimzweb1 said:
First you have a S5 not a note 3 but other than size they are basically the same. Read the post above yours, the same thing will probably happen to you don't panic !!! I have to go to work will be back tonite if you want to wait so I can help as you do it or you can try it yourself even you loop it (like what happened to me and most people ) don't panic just follow the instructions in post # 14. You need a clean copy of NE5 go here enter SM-G900P in search on right, you will have to register but its free , I don't see a XDA site for stock NE5 so here is the link http://www.sammobile.com/firmwares/ enjoy !!!
Click to expand...
Click to collapse
LOL, I know I'm getting old and senile. Been called all kind of mean names and all, but I do believe I know what phone I'm working on. And thanks for the help, maybe a rain check for now. It's not my phone and he's not here.
Have a happy new year, as for me, I'm old and tired and going to bed.
btb601 said:
LOL, I know I'm getting old and senile. Been called all kind of mean names and all, but I do believe I know what phone I'm working on. And thanks for the help, maybe a rain check for now. It's not my phone and he's not here.
Have a happy new year, as for me, I'm old and tired and going to bed.
Click to expand...
Click to collapse
Sorry about that, I'm no spring chicken either. I'm sure you know what phone you have, I only based my statement on the firmware name (NK4). If you want try in the future I would glad to try and help !!! You will find as I have that here on XDA there is always someone to lend a hand !!!
jimzweb1 said:
Sorry about that, I'm no spring chicken either. I'm sure you know what phone you have, I only based my statement on the firmware name (NK4). If you want try in the future I would glad to try and help !!! You will find as I have that here on XDA there is always someone to lend a hand !!!
Click to expand...
Click to collapse
Yeah, I kind of figured that, plus the the model number is one letter different too. I would only try it if you are sure I won't lock up his phone using CF Auto root. I've been at this since the 27th, even throw money at chainfire, although I doubted that would do anything. I needed to donate anyway to show some support for his work.
My other question, can I put it back to the firmware he was on? It's was 4.4.4 (NH7). Then I could root his phone if I can't do it as you said in post #14.
btb601 said:
Yeah, I kind of figured that, plus the the model number is one letter different too. I would only try it if you are sure I won't lock up his phone using CF Auto root. I've been at this since the 27th, even throw money at chainfire, although I doubted that would do anything. I needed to donate anyway to show some support for his work.
My other question, can I put it back to the firmware he was on? It's was 4.4.4 (NH7). Then I could root his phone if I can't do it as you said in post #14.
Click to expand...
Click to collapse
No guarantee it won't bootloop !!! I did on my note 3, you just have to take a step back and keep going. Let me give you an overview, but then you need to follow the individual steps in my first post for each part you need to do.
Ok, the first thing you are going to do is BACK UP ALL THE DATA ON THE DEVICE !!! I.E. music, pics, and videos. These are found on the internal sd card copy and paste them on the desktop of your PC.
Now download Odin to your desktop and extract it. (get the link in 1st post) Download a fresh copy of NH7 4.4.4 to your desktop (get the link in 1st post) and extract it. Now follow the instructions in the first post to flash a stock rom. Let it boot up, if it bootloops take off the back and pull the battery. Let it sit for two minutes, replace the battery and hold the power button, volume up button, and the menu button at the same time. It should boot into a stock recovery, if it DOES use the volume button to navigate to factory reset and push the power button. Let device reboot this will take a couple of minutes. Now go to settings/general/about device and see what version of KK you are running.
If it DOES NOT boot into a stock recovery, and goes back to your custom recovery or bootloops. No problem, pull the battery let it set for a couple of minutes reinstall battery then hold the power button, volume down button, and menu button at the same time and boot into download mode. Go to the first post and flash the rom again it will stick the second time.
Once you are back to bone stock 4.4.4 NH7 just follow the first post for rooting and recoveries. I know this is your friend's device and you don't want to mess it up. So before you try anything check here http://autoroot.chainfire.eu/ go to SM-G900P NK4 and try the CF-auto root for the s5. The s5 and note 3 are pretty much the same. You can try to flash the root through odin the worst that can happen is it will fail and not install. Then you are back to try and going back to 4.4.4 NH7.
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.
I just got the S4 for Verizon prepaid. It came pre-installed with lollipop 5.0.1. I do enjoy tinkering and getting the most out of android, even if making the best of it beings verizon loves to lock stuff up. So before I start any tweaking, I don't want to end up with a soft brick so I want to be cautious and have something to fall back on which would be the firmware I can load back into the phone via Odin. So if anything bad cones I'm covered. No idea how many times the firmware for my prepaid s3 saved my phone lol. So it is needed but unfortunately prepaid firmware seems harder to get.
The firmware or build im exactly after is...i545ppvruaoh7 with kernel September 7 2015. (Not sure if that part matters) any help is appreciated. I seem to have posted this in the wrong section before. I was told to post here but if I'm wrong to post in this section then let me know. Thanks
Still no help?
I'm kinda in the same boat with a Verizon prepaid i545ppvruaoh7. I tried a few ways to root (downgrade to OC1 etc..) but wasn't able to get root until I used Kingroot. Now I am rooted, uninstalled Kingroot and installed Supersu. Root is working still but my Camera isn't working, my wifi passwords won't stick after reboot, and I get a security notification every few minutes. Seems like I need to be back on my original Kernel, which I didn't make a backup of to make everything OK again. Firmware for our I545ppvruaoh7 would fix my problems.
Sorry this doesn't help you @bjf189, but if I can find the firmware I will reply back to here.
ph19971207 said:
I'm kinda in the same boat with a Verizon prepaid i545ppvruaoh7. I tried a few ways to root (downgrade to OC1 etc..) but wasn't able to get root until I used Kingroot. Now I am rooted, uninstalled Kingroot and installed Supersu. Root is working still but my Camera isn't working, my wifi passwords won't stick after reboot, and I get a security notification every few minutes. Seems like I need to be back on my original Kernel, which I didn't make a backup of to make everything OK again. Firmware for our I545ppvruaoh7 would fix my problems.
Sorry this doesn't help you @bjf189, but if I can find the firmware I will reply back to here.
Click to expand...
Click to collapse
I have a few firmware sites bookmarked. Some have firmware for the prepaid s3 so I'm hoping in time they will have the s4 firmware as well. I don't understand why you had to downgrade your kernel though. I'm not real fond of how kernels work but I left it all alone. Didn't downgrade anything. Used king root to root. It said it wouldn't root but still I continued and it rooted. I removed all bloatware and adjusted a few things with pimp my rom. That's about it. I wanted to install safestrap but I see warnings that it don't work on 5.0 lollipop. So I'm avoiding that until firmware is released cause I'm not using that app flashfire being you have to be able to boot into system to use the app to do anything. Just to risky for me. As for your Wi-Fi problems I'm betting it's your kernel. Being the firmware is different, the kernel your looking for or suppose to have for the firmware isn't out yet. I'd give you my stock kernel that came with mine but not sure how you could flash a raw dump
I was able to reinstall my firmware for our i545ppvruaoh7 (with kernel September 7 2015) by using KIES. http://www.samsung.com/us/support/owners/app/kies
My phone is now exactly like it was when I un-boxed it. No root but everything is working again!
---------- Post added at 05:23 PM ---------- Previous post was at 05:16 PM ----------
[/COLOR]I have exactly this same phone and exactly the same issues. I went to the OC1 firmware via Odin a couple times fooling around. Got Rooted. But Charger and Camera went Adios.
Recovery is simple. Inside your Phone in a hidden Partition. It is the Verizon Diagnostic Utilities. When you first plug your phone into a USB you will see the 4 or 5 files.
Run the Application. It will install into your PC. Then with a good internet connection. Run the "Repair" module. It has a nice backup feature. Presto in 45 minutes your back
to "Bone Stock". Root is gone but your fully recovered.
OK now the good news. You want root on your PP version of the Verizon S4. Its available NOW. It can be done with a little skill
1. Download the King Root apk. build 4.8 10523. It's dated 2/4/2016. At first it sez not available for root. Then hit the try anyway. Download Root Checker. Confirm Root.
2. Get the King SU Un- installed. Go Here. http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
3. Download ES File Explorer, Terminal Emulator, and the enclosed Patch on the link above.
4. Follow the directions on the link.
5. You need to Unzip the Patch from wolfdroid into the correct directory. /sdcard/mrw/. Use ES File explorer for that
6. Run the emulator. Type SU to get to the root.
7. Then run the Patch/ batch command. sh /sdcard/mrw/root.sh
That will clean up the KingrootSU and some of the garbage files it leaves behind.
The Super SU will work and you can de-install anything KingRoot still on your phone at this point.
I have loaded Titanium and frozen my Bloat. Loaded my apps with Link2D so I can put them on my sd card. You need to Partition your SD drive correctly.
Using it for a few days now and its flawless. Everything works. Nice speed and full root. No ROM attempts yet. I will back it all up and try in a few weeks.
But have no fear. Your S4 PP Verizon OH7 is recoverable from the process above. No KNOX trip either.
bltserv said:
---------- Post added at 05:23 PM ---------- Previous post was at 05:16 PM ----------
[/COLOR]I have exactly this same phone and exactly the same issues. I went to the OC1 firmware via Odin a couple times fooling around. Got Rooted. But Charger and Camera went Adios.
Recovery is simple. Inside your Phone in a hidden Partition. It is the Verizon Diagnostic Utilities. When you first plug your phone into a USB you will see the 4 or 5 files.
Run the Application. It will install into your PC. Then with a good internet connection. Run the "Repair" module. It has a nice backup feature. Presto in 45 minutes your back
to "Bone Stock". Root is gone but your fully recovered.
OK now the good news. You want root on your PP version of the Verizon S4. Its available NOW. It can be done with a little skill
1. Download the King Root apk. build 4.8 10523. It's dated 2/4/2016. At first it sez not available for root. Then hit the try anyway. Download Root Checker. Confirm Root.
2. Get the King SU Un- installed. Go Here. http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
3. Download ES File Explorer, Terminal Emulator, and the enclosed Patch on the link above.
4. Follow the directions on the link.
5. You need to Unzip the Patch from wolfdroid into the correct directory. /sdcard/mrw/. Use ES File explorer for that
6. Run the emulator. Type SU to get to the root.
7. Then run the Patch/ batch command. sh /sdcard/mrw/root.sh
That will clean up the KingrootSU and some of the garbage files it leaves behind.
The Super SU will work and you can de-install anything KingRoot still on your phone at this point.
I have loaded Titanium and frozen my Bloat. Loaded my apps with Link2D so I can put them on my sd card. You need to Partition your SD drive correctly.
Using it for a few days now and its flawless. Everything works. Nice speed and full root. No ROM attempts yet. I will back it all up and try in a few weeks.
But have no fear. Your S4 PP Verizon OH7 is recoverable from the process above. No KNOX trip either.
Click to expand...
Click to collapse
I've known this but thanks for the tip. I already rooted using that method. I can't rely on that tool to fix a possible screw up. I messed something up on my s3 when I had it. Tried that same tool and it wouldn't go past 51% it kept crashing. So I'm not looking for any other method then the firmware to use in Odin but still thanks guys
bjf189 said:
I have a few firmware sites bookmarked. Some have firmware for the prepaid s3 so I'm hoping in time they will have the s4 firmware as well. I don't understand why you had to downgrade your kernel though. I'm not real fond of how kernels work but I left it all alone. Didn't downgrade anything. Used king root to root. It said it wouldn't root but still I continued and it rooted. I removed all bloatware and adjusted a few things with pimp my rom. That's about it. I wanted to install safestrap but I see warnings that it don't work on 5.0 lollipop. So I'm avoiding that until firmware is released cause I'm not using that app flashfire being you have to be able to boot into system to use the app to do anything. Just to risky for me. As for your Wi-Fi problems I'm betting it's your kernel. Being the firmware is different, the kernel your looking for or suppose to have for the firmware isn't out yet. I'd give you my stock kernel that came with mine but not sure how you could flash a raw dump
Click to expand...
Click to collapse
I have the Verizon S4 used the forum for
Wander share on PC downgraded kernel to oc1 to root and flashed of1 using Odin 3.07 the kernel flash took care of the security warning . Then I downloaded Stanglte non mdk oc1 of rom plus WiFi fix and beta super user zips kladhed with flash fire and I'm cooking however this is the only firm ware I have found working .
I'm still having no luck finding the oh7 firmware :/
Question. Why do you need the Firmware ? I have a Request in for it with SamMobil. Just to have the file. It will come in time. I reset my PP version with the Internal tool that's on the Hidden partition on your phone. You will see it when you first plug in the phone via usb and look at windows file explorer. It will time out after a minute or so then show you the contents in your phones file system.. Yes USB Debugging must be on. That will program when loaded on your PC will reload the original Firmware File completely. Phone will be BONE STOCK. I used it 4 times on my phone. Are you just attempting to root ? Mine sure is working good rooted. Camera, Network, Everything perfectly and I am rooted via Kingroot. Going back to OC1 will not work with this Variant. The reason the program would hang is PC or Network related. I am a windows Expert. Nothing wrong with that program. It will pick up where it left off too. Its very well written.
bltserv said:
Question. Why do you need the Firmware ? I have a Request in for it with SamMobil. Just to have the file. It will come in time. I reset my PP version with the Internal tool that's on the Hidden partition on your phone. You will see it when you first plug in the phone via usb and look at windows file explorer. It will time out after a minute or so then show you the contents in your phones file system.. Yes USB Debugging must be on. That will program when loaded on your PC will reload the original Firmware File completely. Phone will be BONE STOCK. I used it 4 times on my phone. Are you just attempting to root ? Mine sure is working good rooted. Camera, Network, Everything perfectly and I am rooted via Kingroot. Going back to OC1 will not work with this Variant. The reason the program would hang is PC or Network related. I am a windows Expert. Nothing wrong with that program. It will pick up where it left off too. Its very well written.
Click to expand...
Click to collapse
Sorry for the late reply. I never got an email saying you replied. I was just letting time pass and check time to time for the firmware. Anyways, I need the firmware as a safe resort. I'm also rooted with king root. King root does wonders lol. I refuse to do any modding or tinkering until I have the firmware cause if anything goes wrong, and I don't have the firmware then it's a higher chance of my phone not working and thus service days wasted. After getting the firmware, I'm looking to deodex and get xposed to work but before taking any of those steps, I wanna play it safe and cautious. Just cause it works for others, don't mean it's 100% to work for me. So that's why it's important for me to get the firmware for this phone. So as soon as sammobile releases that firmware to you or the public, can you link it on here for me? I'd greatly appreciate it
any one have any info on the firmware as of yet?
bltserv said:
Question. Why do you need the Firmware ? I have a Request in for it with SamMobil. Just to have the file. It will come in time. I reset my PP version with the Internal tool that's on the Hidden partition on your phone. You will see it when you first plug in the phone via usb and look at windows file explorer. It will time out after a minute or so then show you the contents in your phones file system.. Yes USB Debugging must be on. That will program when loaded on your PC will reload the original Firmware File completely. Phone will be BONE STOCK. I used it 4 times on my phone. Are you just attempting to root ? Mine sure is working good rooted. Camera, Network, Everything perfectly and I am rooted via Kingroot. Going back to OC1 will not work with this Variant. The reason the program would hang is PC or Network related. I am a windows Expert. Nothing wrong with that program. It will pick up where it left off too. Its very well written.
Click to expand...
Click to collapse
i found this site that only has it. think its legit? http://www.samsung-file.com/index.p...es)/Model_I/I545PP_(SCH-I545PP)/I545PPVRUAOH7
I saw that site. Wanted a big subscription fee as I recall. Sam Mobil will have it in due time. And I can reload with the Verizon Tools. So its built into that.
bltserv said:
I saw that site. Wanted a big subscription fee as I recall. Sam Mobil will have it in due time. And I can reload with the Verizon Tools. So its built into that.
Click to expand...
Click to collapse
im glad others can have the tools from Verizon to fall back on but i dont feel entirely safe about tinkering until i have that firmware. i had the S3 on prepaid and postpaid and prepaid had different firmwares so if anything is mistaked in between, im screwed. im looking at deodexing my stock rom after getting the firmware though so i can run xposed. im assuming im going to need to deodex it myself some way beings everyone who deodexed it before was on postpaid firmware. i just wish that sammobile would release it more quickly so i can start customizing and such. ive tried other prepaid firmware sites as well and put in requests for the specific firmware but not any replies on that as of yet. i do appreciate that you are keeping me up to date. thank you.
Any firmware come up yet for this? I've got nothing
Still looking?
I recently just go the phone as well and was successfully rooted with King. Every forum I found allows Custom Rom on the older variants of this model but not the PP, any luck yet?
ILoveLamp2234 said:
I recently just go the phone as well and was successfully rooted with King. Every forum I found allows Custom Rom on the older variants of this model but not the PP, any luck yet?
Click to expand...
Click to collapse
I have the stock OH7 Verizon PP...
Juacked up my OF1 so bad this was the only firmware I could get going.
Anyone know of unlocking bootloader on this firmware?
Where's the best place to upload it for sharing?
bjf189 said:
I just got the S4 for Verizon prepaid. It came pre-installed with lollipop 5.0.1. I do enjoy tinkering and getting the most out of android, even if making the best of it beings verizon loves to lock stuff up. So before I start any tweaking, I don't want to end up with a soft brick so I want to be cautious and have something to fall back on which would be the firmware I can load back into the phone via Odin. So if anything bad cones I'm covered. No idea how many times the firmware for my prepaid s3 saved my phone lol. So it is needed but unfortunately prepaid firmware seems harder to get.
The firmware or build im exactly after is...i545ppvruaoh7 with kernel September 7 2015. (Not sure if that part matters) any help is appreciated. I seem to have posted this in the wrong section before. I was told to post here but if I'm wrong to post in this section then let me know. Thanks
Click to expand...
Click to collapse
I've located a copy of i545ppvruaoh7...
I'm aware. I released it on here. Trying to restore the link
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