So I bought my GN3, 3 weeks ago.
I decided to root 2 days ago.
I followed the instructions for CF autoroot, but something is wrong...
It has only "Half-rooted" my phone, and continues to do so.
I know this because:
1) When I try to load the Xposed Framework, it will not load the modules...and continues to show my phones status as not have the xposed framework installed, only the installer... and no matter how many times I hit the "install\update" button, it just sits there.
2) When I try to test the root, with root check, root checker says "phone is moving slowly" then reports that I do not have root./
The Boot Loader screen shows the following:
3) Knox Kernel Lock: 0x0
4) Knox Warranty Void: 0x1
5) Write Protection: Enable
when the phone reboots, the SuperSU is installed..
YET, Genie Go will no longer load, because it reports the phone as being rooted.
Can I get some help?
I have tried the root process, 4 times...
wphend00 said:
So I bought my GN3, 3 weeks ago.
I decided to root 2 days ago.
I followed the instructions for CF autoroot, but something is wrong...
It has only "Half-rooted" my phone, and continues to do so.
I know this because:
1) When I try to load the Xposed Framework, it will not load the modules...and continues to show my phones status as not have the xposed framework installed, only the installer... and no matter how many times I hit the "install\update" button, it just sits there.
2) When I try to test the root, with root check, root checker says "phone is moving slowly" then reports that I do not have root./
The Boot Loader screen shows the following:
3) Knox Kernel Lock: 0x0
4) Knox Warranty Void: 0x1
5) Write Protection: Enable
when the phone reboots, the SuperSU is installed..
YET, Genie Go will no longer load, because it reports the phone as being rooted.
Can I get some help?
I have tried the root process, 4 times...
Click to expand...
Click to collapse
Also, when I run the CF root, when it is loading into recovery\bootloader to install the binaries, I see a message that says SEANDROID
wphend00 said:
Also, when I run the CF root, when it is loading into recovery\bootloader to install the binaries, I see a message that says SEANDROID
Click to expand...
Click to collapse
Can you get into recovery? Or, have you installed it? You might as well do this (download the TWRP file to your computer, and the zip file to your phone before you start)...
Since Knox is already tripped, you should put your phone in download mode (from power off, hold volume down + home key + power key) flash the latest version of TWRP using PC Odin (versions 1.85, 3.07 or 3.09 are fine), using this tar file in the PDA slot...
https://www.dropbox.com/s/5t7oz141ub9nuqz/openrecovery-twrp-2.6.3.7-hltespr.img.tar
Make sure that on PC Odin that only PDA is checked, and if auto reboot is selectable, deselect it. As soon as it completely flashes, quickly hold the home button + volume up. This should take you straight into recovery.
From recovery, click install, then navigate to the location on your device where you downloaded this file (remember, I said to download everything first, and this should be on your phone), and flash,
https://www.dropbox.com/s/0sb2grrj6lv39yc/UPDATE-SuperSU-v1.91.zip
That has the latest version of SuperSU, including the binaries. After flashing, reboot. You should have full root and working recovery.
And no longer in an irksome state of mind.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Can you get into recovery? Or, have you installed it? You might as well do this (download the TWRP file to your computer, and the zip file to your phone before you start)...
Since Knox is already tripped, you should put your phone in download mode (from power off, hold volume down + home key + power key) flash the latest version of TWRP using PC Odin (versions 1.85, 3.07 or 3.09 are fine), using this tar file in the PDA slot...
https://www.dropbox.com/s/5t7oz141ub9nuqz/openrecovery-twrp-2.6.3.7-hltespr.img.tar
Make sure that on PC Odin that only PDA is checked, and if auto reboot is selectable, deselect it. As soon as it completely flashes, quickly hold the home button + volume up. This should take you straight into recovery.
From recovery, click install, then navigate to the location on your device where you downloaded this file (remember, I said to download everything first, and this should be on your phone), and flash,
https://www.dropbox.com/s/0sb2grrj6lv39yc/UPDATE-SuperSU-v1.91.zip
That has the latest version of SuperSU, including the binaries. After flashing, reboot. You should have full root and working recovery.
And no longer in an irksome state of mind.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I still get "partial root".
When ever I try anything, using TWRP...I get
"e:unable to mount 'usbstorage'
The update zipe file works... but does not flash completely...
please help me.
wphend00 said:
I still get "partial root".
When ever I try anything, using TWRP...I get
"e:unable to mount 'usbstorage'
The update zipe file works... but does not flash completely...
please help me.
Click to expand...
Click to collapse
The unable to mount USB storage is an error message you may safely ignore IF you get a successful flash. If the flash fails, you'll get a red-lettered error message indicative of an unsuccessful flash.
Please advise as to which you are experiencing.
Also, could you provide a bit more detail on what you mean by partial root.
Thanks.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
The unable to mount USB storage is an error message you may safely ignore IF you get a successful flash. If the flash fails, you'll get a red-lettered error message indicative of an unsuccessful flash.
Please advise as to which you are experiencing.
Also, could you provide a bit more detail on what you mean by partial root.
Thanks.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Well I appreciate the pointers there. I'm coming from htc and lost the Samsung ways. Why did I stay there so long? So many bricks and locked bootloaders. Note 3 was a bit of an impulse buy. Hope it is as solid as it is big. Thanks again, needed that TWRP file. Goo isn't working for me...
Related
---Make sure you have the drivers installed for your SGP 5.0 USA (capacitive buttons)----
-This has worked for me whenever I enter boot-loop during installing a ROM.
-Download a stock firmware (this one is for US ((capacitive buttons)) Samsung Galaxy Player 5.0): http://forum.xda-developers.com/showthread.php?t=1520728
-Download a .pit file/partition file (contains it for all SGP's): http://forum.xda-developers.com/showthread.php?t=1472897&goto=nextnewestz
-Boot into downloading mode (Volume down first, then power button, release when an triangle and Android guy using a shovel is shown)
-Open up odin
-Click on "PDA", and select "ueki8_min.tar.md5", that should be the stock ROM you downloaded (where ever you saved it), then click "PIT" and select your SGP 5.0 .pit file, which should read "G70-GalaxyPlayer5.0-8gig.pit"
-Press "Start", the process should take 2-5 minutes, it might freeze at some point in time but it's still working. You will know it's finished when it says "PASS" in the first, top right box.
-Then boot into recovery mode (Volume UP, then power), but what is important is that you release the second the triangle/android shovel is gone and shows a black screen or else it will go to a battery charging.
-Then you select "Wipe data/factory reset" and "Wipe cache partition", then "reboot system now" and then your SGP should be able to boot at this point.
*An extra note, the stock ROM I linked is rooted, but it's basically the same as STOCK ROM, with all the Samsung Bloatware.
And to remove the root, you have to get Root Browser from the Play Store and delete "Superuser.apk" in "System/app" and delete "su binary" in "system/bin. After you delete those two files, reboot and you should be unrooted.
(tell me if there is a problem with my guide, or if you have a problem.)
I have followed the instructions but I can't boot into recovery for some reason it only bootloops when I try using the stock rom. entropy kernel + rom is fine but stock rom and kernel only cause boot loops :/
Nevermind i'm ok lol messed around with it for about 20 mins and eventually got it working. Not even sure how to explain how i did it
Silvrsun said:
I have followed the instructions but I can't boot into recovery for some reason it only bootloops when I try using the stock rom. entropy kernel + rom is fine but stock rom and kernel only cause boot loops :/
Nevermind i'm ok lol messed around with it for about 20 mins and eventually got it working. Not even sure how to explain how i did it
Click to expand...
Click to collapse
lol it's k.
Old(ish) thread but since someone used it recently and may in the future might I recommend you note that any attempt to resurrect a device will be best accomplished using a STOCK Samsung usb cable. Speaking from many experiences it is very possible that a device will not be recognized using the pc tools without the stock cable. Just a recommendation. Thanks.
I have search for days to figure out how to unbrick my sgp 5, this however is the most complete and simple guide that have fix my problems after several bricks trying to install custom roms while the forum as down, with bad info on google. I would like to add to make sure that KIES is installed as the drivers become unrecognizable after a brick. Thanks for this post, hardest thing was finding the exact files for the US version as there several out there, the ones you listed worked perfectly together and recovery mode takes a few tries.
KIES
samsung . com/us/support/owners/product/YP-G70CWY/XAA
No one should ever use the pit that comes with that zip file!
Sent from my SAMSUNG-SGH-I577 using xda app-developers app
galax5 said:
---Make sure you have the drivers installed for your SGP 5.0 USA (capacitive buttons)
Click to expand...
Click to collapse
Well how do I make sure I have these drivers?
I have a boot loop when charging device when off and device attempts to load the charging status system.
Anyway I recently installed a new ROM and kernel and the capacitive buttons are dead now (their leds are still on, but they don't actually do anything).
I thought finding out about the driver you were talking about might lead me to a solution.
Does the Odin Version matter?
galax5 said:
-
-Open up odin
-Click on "PDA", and select "ueki8_min.tar.md5", that should be the stock ROM you downloaded (where ever you saved it), then click "PIT" and select your SGP 5.0 .pit file, which should read "G70-GalaxyPlayer5.0-8gig.pit"
-Press "Start", the process should take 2-5 minutes, it might freeze at some point in time but it's still working. You will know it's finished when it says "PASS" in the first, top right box.
Click to expand...
Click to collapse
I remember when I was attempting to root the SGP5 the first time, I ran into trouble with using too new of an odin version. Do you remember which version you used for this? I've tried 1.7&1.85 but to no effect....
AndItsBricked said:
I remember when I was attempting to root the SGP5 the first time, I ran into trouble with using too new of an odin version. Do you remember which version you used for this? I've tried 1.7&1.85 but to no effect....
Click to expand...
Click to collapse
1.85 works fine for me. Check to see if your drivers are properly installed
I have a boot loop when charging device when off and device attempts to load the charging status system.
[HOW-TO] Update to 4.4.2 NAB & NC5 w/Root from MJ4 Rooted without triggering Knox 0x1
This How-to guide will show you how to update from Jellybean MJ4 Android 4.3 with Root and Knox 0x0 to KitKat NAB Android 4.4.2 with Root without triggering the Knox 0x1 Warranty Bit.
This guide will be useful to those who want to have Root on their phone without triggering the Knox Warranty bit (and losing your warranty) and don't care/mind about flashing custom recoveries, kernels and ROM's. I, for one, only need Root so I can use Root apps like Xposed, Titanium Backup, AdAway, etc.
I also have a Galaxy S4 and a Nexus 5 and I don't use custom kernels and ROM's on those phones either (I just like stock & Root, lol~). And I don't have phone insurance on my Note 3 and S4 so that's why I want to keep Knox at 0x0 just in case. Also, I like the feeling of out-smarting/going around Samsung's ridiculous Knox implementations.
Disclaimer/Heads-Up
You undertake these steps at your own risk to your phone. This method has been used successfully many times by many users to go from Rooted 4.3 to Rooted 4.4.2 without triggering the Knox Warranty bit. Please read the instructions carefully in the entire post and download/install all the files before proceeding.
=============================================================
Now, onto the steps.
Before beginning the process, make sure you have the following installed on your phone and Windows laptop:
1. Samsung USB driver (PC) (So your Windows PC can detect your Note 3 when you plug it in.)
2. Odin v3.09 (PC) (You'll be using this to flash the NAB bootloader. I modified the .ini file for flashing the bootloader correctly. Clicking on the link will lead you to download Odin v3.09 from my Dropbox account.)
3. Mobile Odin Pro v4.0 (phone) (You'll be using this to flash the NAB tar file to update to Android 4.4.2.)
**Please DO NOT use Mobile Odin Lite. It won't work. If you already have Mobile Odin Lite installed, uninstall it & reboot your phone. Then download & install Mobile Odin Pro.
4. The NAB tar file, transferred over to the root directory of your phone (phone) (Thanks to @freeza for getting this for us~!)
5. The NAB engineering bootloader (PC) or stock NAB bootloader (PC). (Again, thanks to @freeza ~!!)
6. Kingo Android Root (I used v1.1.8.1835 to Root MJ4 4.3) (PC) (You can use this, without triggering Knox 0x1, to Root your stock MJ4 4.3.)
7. Stock NAB 4.4.2 CSC.tar file. (PC) You'll need to flash this with desktop Odin in order for your phone to have the correct CSC information as well as important System apps. If you don't flash this, you'll lose the ability to choose GSM/UMTS in the Mobile Network setting and you'll have S-Pen-related app crashes.
8. Odin v3.04 (for flashing the above CSC.tar file) (PC).
** Optional: If you don't like seeing multiple lines of code every time you reboot your phone (b/c of the engineering bootloader that has been flashed), you can flash the stock NAB bootloader prepared by rwilco12 for us.
His One-Click stock NAB bootloader can be downloaded here.
If you want the stock NAB bootloader in tar format, you can download it from my Dropbox here.
Before I began the process, my Note 3 was as follows:
Stock MJ4 Rooted (achieved with Kingo Android Root)
Stock MJ4 kernel
MJ4 baseband
MJ4 bootloader
Knox Warranty Bit = 0x0
{
"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"
}
[1] Backup anything that's important to you first just in case (e.g., app data, pictures, videos, SMS, call log). I like to backup using Helium, MyBackup Pro, Titanium Backup, & SMS Backup & Restore.
[2] Open up Mobile Odin Pro v4.0 and click on "Open file...". Select the NAB tar file. Make sure the following options are checked:
-"Enable EverRoot"
-"Inject Superuser (SuperSU)"
-"Inject Mobile Odin"
[3] Click on "After flash..." and choose "Download Mode."
[4] Finally, click on "Flash firmware." The phone will reboot automatically and MOP will begin flashing the NAB tar. You'll see a screen like this:
(Modile Odin Pro v4.0 flashing the NAB tar)
[5] Once MOP has finished flashing the NAB tar, it'll boot you directly into Download mode.
(Knox Warranty Bit is still 0x0)
[6] Now, open Desktop Odin v3.09 (download from link above). Click on the "BL" button and select the NAB bootloader you downloaded earlier.
-Be sure the following options are unchecked: "Auto Reboot" and "F. Reset Time."
-Also, the "Phone Bootloader Update" box should be checked.
Now, click on the "Start" button. Wait until it reports "Pass."
[7] Hold down the Power button until the phone reboots. Right when the phone vibrates and begins to restart, press and hold down "VOL UP + HOME + POWER" until the phone enters into this screen:
(The screen looks like this b/c the NAB bootloader is the engineering bootloader version. Note that the Knox Warranty Bit is still 0x0.)
[8] Press the Power button until the phone reboots. Right when the phone vibrates & begins to restart, press and hold down "VOL DOWN + HOME + POWER" until you get to this screen:
[9] Press "Volume down" to cancel and restart the phone.
[10] The phone will reboot and start up normally. Your Note 3 may stay at the yellow Sprint screen for longer than you're used to. Be patient.
Next comes the normal Samsung boot animation.
Then the "Android is upgrading..." pop-up will appear and your apps will be optimized.
Let the phone settle for about 5 to 10 minutes. Upon settling down, reboot your phone once.
[11] Now that your phone has settled down, shut it off completely. Then boot into Download Mode (VOL DOWN + POWER + HOME).
[12] Open desktop Odin v3.04 by right-clicking it & choosing "Run as administrator."
[13] Click on the PDA button and select the csc.tar file. Click Start and let the flash finish and auto-reboot your phone.
And now, everything's finished~!
Some people have experienced unstableness in the NAB 4.4.2 environment after the flash. It could be because of some apps that were installed in the MJ4 4.3 environment that's causing the problem. If that's your case, I recommend booting into stock recovery and performing a factory reset/data wipe. You'll have to reinstall your apps again but at least you'll have a clean start.
**Warning: If you decide to flash the NAB tar file with Desktop Odin instead, you'll lose Root.
==============================
Through this method, I was able to go from Stock Rooted 4.3 to Stock Rooted 4.4.2 while keeping my Knox Warranty bit at 0x0.
You can check on your Knox Warranty Bit status by restarting the phone and going into Download Mode.
Full setting available under Mobile Network
Writing a text message with the S-Pen
Screen write
How to Update from Stock, Rooted NAB 4.4.2 to Stock, Rooted NC5 4.4.2 (Knox stays 0x0)
Files Needed
1. NC5 tar file. You can download the tar file from here:
http://samsung-updates.com/device/?id=SM-N900P
I placed the NC5 tar into my Internal Storage of the phone (not microSD).
2. NC5 CSC file ( <-- Download from my Dropbox)
3. Odin v3.04
4. NC5 modem file ( <-- Download from my Dropbox) (Credit goes to freeza)
5. NC5 stock Bootloader (optional) ( <-- Download from my Dropbox) (Flash with my modified Odin v3.09 & use the BL button).
Flashing Instructions
1. Make sure your copy of Mobile Odin Pro is at version 4.10.
2. Open MOP v4.10 and select the NC5 tar file. You don't need to set up the phone to boot into Download Mode after the flash. Click on "Open file...". Select the NC5 tar file. Make sure the following options are checked:
-"Enable EverRoot"
-"Inject Superuser (SuperSU)"
-"Inject Mobile Odin"
3. After the flash has completed and phone has rebooted, check Settings. Everything should be NC5 except for the baseband.
4. Shut off the phone completely. Then enter into Download Mode by holding down POWER + VOL DOWN + HOME.
5. Flash the NC5 baseband/modem using Odin v3.04 and using the PDA button. Let the phone reboot.
6. Check Settings. Everything should be NC5 now.
7. Reboot the phone into Download Mode again. Using Odin v3.04 and the PDA button, flash the NC5 CSC file.
8. You're done~!!
9. (Optional step) Steps 1 through 7 will update your phone to NC5, except for the bootloader. The bootloader will remain NAB. Even with the NAB bootloader, the phone will work just fine after updating to NC5 for everything else.
However, if you would like to have the bootloader version to be NC5 as well, then flash the stock NC5 bootloader via Odin v3.09. Be sure to power down the phone completely and reboot into Download Mode from a cold state in order for the bootloader flash to stick.
Can someone with the phone info app and Knox tripped see if it reports 0x1. I was unaware that the app developer found a way to read the actual bit.
Thank you for this guide! Will try it out when I get home
Sent from my SM-N900P using xda app-developers app
NAE? Where is this coming from?
Sent from my SM-N900P using Tapatalk
MikeyLee said:
NAE? Where is this coming from?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
LOL fixed the title~
Sent from my Nexus 5 using Tapatalk
optimummind said:
LOL fixed the title~
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
lol I was gonna say
First thank you very much for posting this.
I have just one question. Do we have to flash the engineering bootloader?
Porsche928Guy said:
First thank you very much for posting this.
I have just one question. Do we have to flash the engineering bootloader?
Click to expand...
Click to collapse
Yes, until @freeza has the time to release the official NAB bootloader for us to flash.
Sent from my SPH-L720
I'm trying this now, wish me luck! One thing I'd like to mention regarding your step #4. You said, "The NAB tar file, transferred over to the root directory of your phone (phone)". I tried copying the file to the root of my phone and it locked up my phone, probably because it is too big. I had to do a battery pull to get back up. Mobile Odin Pro found the file in a directory on my external card so I would advise copying it there.
Uh-oh, one more thing. I got the NAB tar file flashed with MOP, but in PC Odin 3.09.03 you said, "-Also, the "Phone Bootloader Update" box should be checked." That option is grayed out. How can I enable that? I'll wait for a reply before flashing the engineering bootloader.
JimSmith94 said:
I'm trying this now, wish me luck! One thing I'd like to mention regarding your step #4. You said, "The NAB tar file, transferred over to the root directory of your phone (phone)". I tried copying the file to the root of my phone and it locked up my phone, probably because it is too big. I had to do a battery pull to get back up. Mobile Odin Pro found the file in a directory on my external card so I would advise copying it there.
Click to expand...
Click to collapse
That's interesting that a simple file transfer would lock up the phone. Which app did you use to make the transfer? I used ES Explorer.
Sent from my SPH-L720
optimummind said:
That's interesting that a simple file transfer would lock up the phone. Which app did you use to make the transfer? I used ES Explorer.
Sent from my SPH-L720
Click to expand...
Click to collapse
I used Root Explorer. I assume that it either can't handle 2.2+GB files or the phone didn't have enough space left for the copy.
---------- Post added at 07:44 PM ---------- Previous post was at 07:39 PM ----------
Thought I'd make this a separate post: One more thing. I got the NAB tar file flashed with MOP, but in PC Odin 3.09.03 you said, "-Also, the "Phone Bootloader Update" box should be checked." That option is grayed out. How can I enable that? I'll wait for a reply before flashing the engineering bootloader.
JimSmith94 said:
I used Root Explorer. I assume that it either can't handle 2.2+GB files or the phone didn't have enough space left for the copy.
---------- Post added at 07:44 PM ---------- Previous post was at 07:39 PM ----------
Thought I'd make this a separate post: One more thing. I got the NAB tar file flashed with MOP, but in PC Odin 3.09.03 you said, "-Also, the "Phone Bootloader Update" box should be checked." That option is grayed out. How can I enable that? I'll wait for a reply before flashing the engineering bootloader.
Click to expand...
Click to collapse
Did you download Odin v3.09 from my Dropbox in the 1st post? It's been modified to allow that checkbox to be checked already.
Sent from my Nexus 5 using Tapatalk
optimummind said:
Did you download Odin v3.09 from my Dropbox in the 1st post? It's been modified to allow that checkbox to be checked already.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh sorry, my bad. I had a newer version and thought newer was better. Okay, everything flashed, and I did the two reboots with volume up and volume down as you said. It rebooted and updated apps, and got to the lock screen with a couple notifications in the notification bar.
However, I got a "waiting for connection" message at the bottom of the screen and the screen went black and I couldn't wake it up with the power button. I have rebooted it several times and was able to boot all the way a few times, but the screen times out whether I am using it or not and it won't wake up. I also get a smartcardservices has stopped message and the phone is running quite hot.
Any ideas?
Thanks for this. Exactly what ive been waiting for!
Sent from my GT-N8013 using Tapatalk
JimSmith94 said:
Oh sorry, my bad. I had a newer version and thought newer was better. Okay, everything flashed, and I did the two reboots with volume up and volume down as you said. It rebooted and updated apps, and got to the lock screen with a couple notifications in the notification bar.
However, I got a "waiting for connection" message at the bottom of the screen and the screen went black and I couldn't wake it up with the power button. I have rebooted it several times and was able to boot all the way a few times, but the screen times out whether I am using it or not and it won't wake up. I also get a smartcardservices has stopped message and the phone is running quite hot.
Any ideas?
Click to expand...
Click to collapse
The "Waiting for connection" message should disappear once your phone connects to Sprint via 3G or 4G. My phone did something along the line of "Final connection has completed" thing after first boot.
If you keep getting errors, you might want to do a factory reset/data wipe from within the stock recovery (hope you backed up your files).
Sent from my Nexus 5 using Tapatalk
Does this works (and keeps 0x0) with OTA 4.4.2 ? I mean can I root 4.4.2, flash kernel and 0x0?
Sent from my SM-N900P using xda app-developers app
erik077 said:
Does this works (and keeps 0x0) with OTA 4.4.2 ? I mean can I root 4.4.2, flash kernel and 0x0?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I don't know whether this engineering bootloader will trip the Knox warranty bit or not when one flashes a custom recovery afterwards. It'd be great if someone could verify for us. It'd be sweet if it didn't so that people can flash custom kernels, recoveries, and ROM's without tripping Knox.
Edit: Sorry for any confusion. I've updated my words in the above paragraph.
optimummind said:
I don't know whether this engineering bootloader will trip Knox or not. It'd be great if someone could verify for us. It'd be sweet if it didn't so that people can flash custom kernels, recoveries, and ROM's without tripping Knox.
Click to expand...
Click to collapse
As of this writing, one will never be able to flash custom recovery, flash kernels or any rom in the dev forum without tripping Knox.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Someone once reported that they had a knox tripped phone they brought in to a sprint store and a guy actually reset his phone to factory, including knox was set back to 0x0. I never heard any other stories like that though so who knows.
Sent from my SM-N900P using XDA Premium 4 mobile app
Okay, I'm officially lost. This guide is about not tripping Knox and the OP says the engineering bootloader must be flashed, but then a few posts above this states they don't know if flashing the engineering bootloader will trip Knox. So does it trip Knox or not? Or is this referring to the comment I made about phone info not reporting everything for our phone correctly?
Sent from my SM-N900P using xda app-developers app
evilvoice said:
Okay, I'm officially lost. This guide is about not tripping Knox and the OP says the engineering bootloader must be flashed, but then a few posts above this states they don't know if flashing the engineering bootloader will trip Knox. So does it trip Knox or not? Or is this referring to the comment I made about phone info not reporting everything for our phone correctly?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I may hedge on the Knox question, likely will in my prior post, but that does not detract one jot from the utility of this thread.
Sent from my SM-N900P using Xparent BlueTapatalk 2
---------- Post added at 09:17 AM ---------- Previous post was at 09:10 AM ----------
KEYofR said:
Someone once reported that they had a knox tripped phone they brought in to a sprint store and a guy actually reset his phone to factory, including knox was set back to 0x0. I never heard any other stories like that though so who knows.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Either urban legend or maybe true. William of Occam would assert the former, I'll not speak in absolutes and simply state that it were true, more would know about it. The latent desire in having this capability is strong enough to believe that, if it is possible at the Sprint store, the good folks here would've published it.
Sent from my SM-N900P using Xparent BlueTapatalk 2
First, a HUGE thanks goes to @garwynn for being my team mate and working with me on all these projects! Another big thanks to @micmars for posting the original NC5 TAR here.
Second, I was asked to make this one-click to help simplify the process of restoring a stock factory build for our Note 3 users. I do not own a Note 3 so I have not been able to test this as I would normally prefer to do before releasing. I do however feel comfortable that it should work as designed. Due to the fact that we do not have a Note 3 to be testing it on, at this time neither myself or Garwynn are planning on releasing a rooted One-Click. There is a lot more risk involved when building the rooted versions and we don't want to take that risk with other people's phones.
This Odin One-Click.exe contains the Stock SM-N900P NC5 Bootloader, Kernel, Modem and ROM for the Sprint Samsung Galaxy Note 3 (SM-N900P). Yes, that means this comes with the full Knox Bootloader.
There has been no change to the ROM from the initial build released by Samsung.
This will NOT trigger the Yellow Triangle NOR will it increment the Odin flash count.
This one-click resets your whole phone to the stock NC5 experience, similar to a factory restore and it may wipe all data. It also contains the full bootloader and Knox.
Instructions:
1: Backup anything important and Disable any PINs.
During this process your phone's software will be returned to the Stock setup. All system data will be lost. To be safe, it is best to archive your backup off your phone, ie on your PC or Dropbox.
2: Install Samsung USB/Android drivers (if necessary).
Samsung Drivers Download Link
3: Download the NC5 Stock ROM One-Click.
SM-N900P NC5 Full Restore Unrooted (Compressed Archive).exe (Resets user data)
4: Unzip One-Click ROM using 7zip (this package is a self-extracting exe you should just be able to double-click on it after download and it will do the rest).
5: Start the Odin One-Click.
Navigate to the location where the "SM-N900P NC5 Full Restore Unrooted.exe" was saved upon extract from the 7Zip archive.
Double-click on "SM-N900P NC5 Full Restore Unrooted.exe". *On Vista or newer, you may need to right-click on the file and Run as Administrator.
6: Place phone in Download Mode.
- Power phone completely off.
- Press and hold Volume Down, Home and Power buttons, all at the same time.
- Release the buttons only when the ‘Warning!!’ message appears.
- Press [Volume Up] to enter Download mode.
7: Connect USB cable to PC and phone.
Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click.
8: Start Odin flash process.
Press [Start].
9: Complete - PASS!
Status should change to green PASS! At this point your phone should automatically reboot.
Android Instructions:
Download and install ZArchiver on your phone. Use it to unpack the Odin One-Click 7zip self-extracting exe file (long press on the 7zip exe. Select "Open As Archive". Select the One-Click.exe and then select Extract). Use Mobile Odin to Open File on the "SM-N900P NC5 Full Restore Unrooted.exe". FYI - Modem will not flash with Mobile Odin.
The boot process will take slightly longer than usual during which time you'll see the Sprint 4G logo screen.
Congratulations! You've flashed the Factory Restore NC5 build!
XDA:DevDB Information
[ROM][ODIN] SM-N900P NC5 (NC5 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), ROM for the Sprint Samsung Galaxy Note 3
Contributors
rwilco12
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2015-02-09
Last Updated 2015-02-09
Download Link: http://www.rwilco12.com/forum/showthread.php?tid=621
rwilco12 said:
Download Link: http://www.rwilco12.com/forum/showthread.php?tid=621
Click to expand...
Click to collapse
I will be flashing this in about and hour and will let you know how it goes.
Thanks for all the hard work!
EDIT: Worked like a charm, no issues, no problems.
Question: Is there a root method for NC5? or a stock rooted one?
piizzadude said:
I will be flashing this in about and hour and will let you know how it goes.
Thanks for all the hard work!
EDIT: Worked like a charm, no issues, no problems.
Question: Is there a root method for NC5? or a stock rooted one?
Click to expand...
Click to collapse
We won't be doing a rooted one-click due to issues with Knox. You should be able to root it with any of the existing methods for previous builds.
Sent from my d2lte using Tapatalk
Haven't jumped to nc5 yet. Guess now that this is here I have no excuse.
Sent from my SM-N900P using Tapatalk
so could this be used to upgrade to NC5 from MJ4? Thanx for all the work and info!
Buslova said:
so could this be used to upgrade to NC5 from MJ4? Thanx for all the work and info!
Click to expand...
Click to collapse
Yep. Odin is essentially a drive imaging utility. It takes a pre-built image of a partition and then wipes the existing partition's data and replaces it with the new image. So in theory as long as you have the right partitions setup you could use this to put any device on NC5 (mind you there are no other devices that I know of that share the exact same partition structure with the Sprint N3).
Awesome i was just talking about this yesterday wondering g if there was one in the process of being made
Sent from my SM-N900P using Tapatalk
Anyone have an idea of the easiest way to go from Stock Rooted MJ4 (Knox 0X1) to NC5. I have no problem flashing a custom recovery and Knox is already tripped.
I was thinking of using this full restore to NC5 and then rooting through a more conventional method. Odin a custom recovery, then flash SuperSU through recovery. I think SuperSU will disable Knox.
The other option I was considering was using the instructions in optimummind's thread here: http://forum.xda-developers.com/showthread.php?t=2658315. The only benefit to that is I would not lose my data, but it seems like a lot more work.
Ideas?
I used this and rooted with chainfires method. Pretty easy
Sent from my SM-N900P using Tapatalk
If you have rooted with CF-AUTOROOT and trip Knox to 0x1. Can this method return your rom to factory and erase Knox error reading ?
Sent from my SM-N900P using XDA Premium 4 mobile app
JimmyMPR said:
If you have rooted with CF-AUTOROOT and trip Knox to 0x1. Can this method return your rom to factory and erase Knox error reading ?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, I started the process, will keep you updated.....
Unroot process tooks about 15 mins, sweet.
All applications were not erased from the phone, apps and data still intact. :laugh:
Root were removed successfully. :good:
Knox Trip Counter still in 0x1.
Excellent work !
JimmyMPR said:
Unroot process tooks about 15 mins, sweet.
All applications were not erased from the phone, apps and data still intact. :laugh:
Root were removed successfully. :good:
Knox Trip Counter still in 0x1.
Excellent work !
Click to expand...
Click to collapse
The only question that I have, is data was not supposed to be erased? Status changed from custom to official and loose root, but Data and downloaded installed apk's still intact on the phone..... Why?
My Software version and Baseband version sill shows NAB. Build number shows NC5 though.
It didn't do a factory reset and all my apps were intact along with my settings.
mrnamster said:
My Software version and Baseband version sill shows NAB. Build number shows NC5 though.
It didn't do a factory reset and all my apps were intact along with my settings.
Click to expand...
Click to collapse
Did you factory reset prior to flashing? And did you flash this from a completely powered off state?
Flash it again. It'll stick.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Did you factory reset prior to flashing? And did you flash this from a completely powered off state?
Flash it again. It'll stick.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
My Software version and Baseband version shows NC5, Root dissapeared but I didn't do a factory reset. All my apps, Data and settings were intact too.
JimmyMPR said:
My Software version and Baseband version shows NC5, Root dissapeared but I didn't do a factory reset. All my apps, Data and settings were intact too.
Click to expand...
Click to collapse
If you are now all NC5, then enjoy the fact that you didn't lose anything. Root gets nuked due to it but being included.
Now you can remain stock, flash recovery and a pre-rooted rom, or just recovery and the latest root.
Congrats!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Did you factory reset prior to flashing? And did you flash this from a completely powered off state?
Flash it again. It'll stick.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
That did the trick! Thanks!
I did a factory reset/wipe in TWRP, powered down, booted into Download mode, and flashed.
Everything shows NC5 now in About device.
rwilco12 said:
First, a HUGE thanks goes to @garwynn for being my team mate and working with me on all these projects! Another big thanks to @micmars for posting the original NC5 TAR here.
Second, I was asked to make this one-click to help simplify the process of restoring a stock factory build for our Note 3 users. I do not own a Note 3 so I have not been able to test this as I would normally prefer to do before releasing. I do however feel comfortable that it should work as designed. Due to the fact that we do not have a Note 3 to be testing it on, at this time neither myself or Garwynn are planning on releasing a rooted One-Click. There is a lot more risk involved when building the rooted versions and we don't want to take that risk with other people's phones.
This Odin One-Click.exe contains the Stock SM-N900P NC5 Bootloader, Kernel, Modem and ROM for the Sprint Samsung Galaxy Note 3 (SM-N900P). Yes, that means this comes with the full Knox Bootloader.
There has been no change to the ROM from the initial build released by Samsung.
This will NOT trigger the Yellow Triangle NOR will it increment the Odin flash count.
This one-click resets your whole phone to the stock NC5 experience, similar to a factory restore and it may wipe all data. It also contains the full bootloader and Knox.
Instructions:
1: Backup anything important and Disable any PINs.
During this process your phone's software will be returned to the Stock setup. All system data will be lost. To be safe, it is best to archive your backup off your phone, ie on your PC or Dropbox.
2: Install Samsung USB/Android drivers (if necessary).
Samsung Drivers Download Link
3: Download the NC5 Stock ROM One-Click.
SM-N900P NC5 Full Restore Unrooted (Compressed Archive).exe (Resets user data)
4: Unzip One-Click ROM using 7zip (this package is a self-extracting exe you should just be able to double-click on it after download and it will do the rest).
5: Start the Odin One-Click.
Navigate to the location where the "SM-N900P NC5 Full Restore Unrooted.exe" was saved upon extract from the 7Zip archive.
Double-click on "SM-N900P NC5 Full Restore Unrooted.exe". *On Vista or newer, you may need to right-click on the file and Run as Administrator.
6: Place phone in Download Mode.
- Power phone completely off.
- Press and hold Volume Down, Home and Power buttons, all at the same time.
- Release the buttons only when the ‘Warning!!’ message appears.
- Press [Volume Up] to enter Download mode.
7: Connect USB cable to PC and phone.
Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click.
8: Start Odin flash process.
Press [Start].
9: Complete - PASS!
Status should change to green PASS! At this point your phone should automatically reboot.
Android Instructions:
Download and install ZArchiver on your phone. Use it to unpack the Odin One-Click 7zip self-extracting exe file (long press on the 7zip exe. Select "Open As Archive". Select the One-Click.exe and then select Extract). Use Mobile Odin to Open File on the "SM-N900P NC5 Full Restore Unrooted.exe". FYI - Modem will not flash with Mobile Odin.
The boot process will take slightly longer than usual during which time you'll see the Sprint 4G logo screen.
Congratulations! You've flashed the Factory Restore NC5 build!
Click to expand...
Click to collapse
rwilco12 great work !!! I have used this twice, with complete success. On the third time, everything seems ok? But, there is no Sprint 4G logo screen. Any ideas as to why? :fingers-crossed:
So here is where I'm @:
Until a few days ago I had a custom ROM (cm12.1) running on my S3 I9300 International. I encrypted it weeks ago.
So now I decided to decrypt it. I did this by heading to the settings = Backup & reset and tapping the Factory reset option at the bottom of the screen.
What happened is that my phone rebooted and got stuck in the startup of TWRP recovery (so the TWRP logo keeps blinking, it doesn't get me into recovery).
So now my phone doesn't do anything. I only can get into downloading mode. Downloading mode says the following:
Odin mode
Product name: GT-I9300
Custom binary download: Yes (3 counts)
System status: Custom
So I downloaded Odin and started it. Odin sees my phone. I tried to install some stock firmware (don't know if this is the right solution), but it failed.
What can I do to get my phone operational again?
I really need some help. The did read the forums. But I'm no pro and i don't know what to do.
@ChefHooah said:
So here is where I'm @:
Until a few days ago I had a custom ROM (cm12.1) running on my S3 I9300 International. I encrypted it weeks ago.
So now I decided to decrypt it. I did this by heading to the settings = Backup & reset and tapping the Factory reset option at the bottom of the screen.
What happened is that my phone rebooted and got stuck in the startup of TWRP recovery (so the TWRP logo keeps blinking, it doesn't get me into recovery).
So now my phone doesn't do anything. I only can get into downloading mode. Downloading mode says the following:
Odin mode
Product name: GT-I9300
Custom binary download: Yes (3 counts)
System status: Custom
So I downloaded Odin and started it. Odin sees my phone. I tried to install some stock firmware (don't know if this is the right solution), but it failed.
What can I do to get my phone operational again?
I really need some help. The did read the forums. But I'm no pro and i don't know what to do.
Click to expand...
Click to collapse
Explain in details how did Odin fail!
Sent from my Q10101 using XDA Free mobile app
I started Odin3 v3.10 and plugged in my phone. In box AP I added the md5 file (I9300XXUGOC1_I9300TNLGOC1_I9300BOUGNB1_HOME.tar.md5) and in the options menu I checked auto reboot and F. Reset Time. And hit the Start button.
After a couple of minutes Odin said something like FAILS.
@ChefHooah said:
I started Odin3 v3.10 and plugged in my phone. In box AP I added the md5 file (I9300XXUGOC1_I9300TNLGOC1_I9300BOUGNB1_HOME.tar.md5) and in the options menu I checked auto reboot and F. Reset Time. And hit the Start button.
After a couple of minutes Odin said something like FAILS.
Click to expand...
Click to collapse
That "something" is what i wanted to know. Print screen when Odin stops with Fail at the end.
Sent from my iPhone using Tapatalk
Stevica Smederevac said:
That "something" is what i wanted to know. Print screen when Odin stops with Fail at the end.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Hi
You requested a screenshot about the Odin procedure. So I restarted Odin and retried to install the firmware, so that I could take some screenshots. It did PASS! this time. I have no clue why it failed last time.
When the phone rebooted after the Odin install, it gave a message that the partition was bad. So the phone did a reboot and fixed the errors. And now the phone works.
I installed a dutch T-Mobile firmware Android 4.3. So now I only have to root the phone to and install a custom ROM (ArchiDroid) once again.
I wanna thank you for replying and trying to help me. Much appreciated. What is you're opinion on what was wrong with my phone? What would be the technology name about the error
@ChefHooah said:
Hi
You requested a screenshot about the Odin procedure. So I restarted Odin and retried to install the firmware, so that I could take some screenshots. It did PASS! this time. I have no clue why it failed last time.
When the phone rebooted after the Odin install, it gave a message that the partition was bad. So the phone did a reboot and fixed the errors. And now the phone works.
I installed a dutch T-Mobile firmware Android 4.3. So now I only have to root the phone to and install a custom ROM (ArchiDroid) once again.
I wanna thank you for replying and trying to help me. Much appreciated. What is you're opinion on what was wrong with my phone? What would be the technology name about the error
Click to expand...
Click to collapse
Who knows, so many things could have gone wrong. I never encrypted my phone so maybe you did something wrong when decrypting. As far as Odin's issue, there are number of things that could go wrong. Important thin is that it works now[emoji106][emoji481]
Sent from my iPhone using Tapatalk
Hello all!
I was just wondering if there is a method to root my T-mobile GS5 version 5.1.1 build number G900TUVS1FOL1.
I am new to rooting and haven't done it before and with the research I've done so far, it seems like there are a ton of ways to root, but as well as damage your phone so if possible I would like some help with this or get directed to the correct tutorial to root my current version.
There are so many out there that its confusing to figure which tutorial is the right one to follow or if there is even one out there for my current version, I appreciate any help, thanks!
ktobar said:
Hello all!
I was just wondering if there is a method to root my T-mobile GS5 version 5.1.1 build number G900TUVS1FOL1.
I am new to rooting and haven't done it before and with the research I've done so far, it seems like there are a ton of ways to root, but as well as damage your phone so if possible I would like some help with this or get directed to the correct tutorial to root my current version.
There are so many out there that its confusing to figure which tutorial is the right one to follow or if there is even one out there for my current version, I appreciate any help, thanks!
Click to expand...
Click to collapse
Install TWRP in Odin with auto-reboot disabled, immediately boot into recovery and flash the SuperSUv2.67.zip
Thanks for the links. I'm also very new to rooting. Just tired using CF Auto Root and soft bricked my phone because I didn't know there wasn't a new enough version for my G900TUVS1FOL1 build version. I flashed the stock firmware with Odin and surprisingly it booted and all my data is still intact!? I didn't lose anything like I was expecting.
So now what? Instead of CF Auto Root I can use the method you just mentioned? Also, when I clikc the TWRP link there are a ton of them, which one do I pick? And do I just need the .tar file? Or do I need the .img as well?
A little more detail and I can probably get through this. THanks!
Dorsant said:
Thanks for the links. I'm also very new to rooting. Just tired using CF Auto Root and soft bricked my phone because I didn't know there wasn't a new enough version for my G900TUVS1FOL1 build version. I flashed the stock firmware with Odin and surprisingly it booted and all my data is still intact!? I didn't lose anything like I was expecting.
So now what? Instead of CF Auto Root I can use the method you just mentioned? Also, when I clikc the TWRP link there are a ton of them, which one do I pick? And do I just need the .tar file? Or do I need the .img as well?
A little more detail and I can probably get through this. THanks!
Click to expand...
Click to collapse
Yes the method I said will work, it's what I used to root OL1. On the TWRP link, download the file named twrp-3.0.0-0-klte-klte.img.tar. You only need the tar file, not the img file
tried this on my girl's S5, got stuck on white tmobile screen...flashed twrp in odin with auto-reboot unchecked, soon as odin said "pass" I pulled the battery, flashed the supersu suggested and got stuck on the screen...i let it sit close to 20 minutes before re-flashing stock firmware.....did i miss something??
EDIT- missed where it said "do not hit root" in TWRP, re-installed and have root, thanks!
This method also worked for me. Phone successfully rooted! Thank you.
This method works. Thank you im now rooted
Set warranty bit kernel
What do I do if when I flashed twrp it said set warranty bit kernel
Do I have to wipe for this method
broad_st_bully said:
tried this on my girl's S5, got stuck on white tmobile screen...flashed twrp in odin with auto-reboot unchecked, soon as odin said "pass" I pulled the battery, flashed the supersu suggested and got stuck on the screen...i let it sit close to 20 minutes before re-flashing stock firmware.....did i miss something??
EDIT- missed where it said "do not hit root" in TWRP, re-installed and have root, thanks!
Click to expand...
Click to collapse
HI, okay, i am experiencing the same thing on my s5 after following all instructions. (I'm a newbie at this stuff)> Everything went perfectly, flashed the correct twrp on odin with auto-rebooted unchecked, i swiped to install. After the reboot, at the start up screen it said "Set Warranty Bit: Kernel", took a long time but then it got stuck on the T Mobile screen where I cannot do anything.
Please tell me what you did to fix this!!! (not sure what you meant by "do not hit root" or how/what you reinstalled exactly) Step by step instructions because again I'm new at this and desperate!! Thank you!!
ktberr said:
HI, okay, i am experiencing the same thing on my s5 after following all instructions. (I'm a newbie at this stuff)> Everything went perfectly, flashed the correct twrp on odin with auto-rebooted unchecked, i swiped to install. After the reboot, at the start up screen it said "Set Warranty Bit: Kernel", took a long time but then it got stuck on the T Mobile screen where I cannot do anything.
Please tell me what you did to fix this!!! (not sure what you meant by "do not hit root" or how/what you reinstalled exactly) Step by step instructions because again I'm new at this and desperate!! Thank you!!
Click to expand...
Click to collapse
After you flash supersu and it says "this device is not rooted , do you want to root" make sure you say no because that doesnt actually root your device , it just bricks it.
This guy needs help said:
After you flash supersu and it says "this device is not rooted , do you want to root" make sure you say no because that doesnt actually root your device , it just bricks it.
Click to expand...
Click to collapse
I figured it out in the time being, now it's rooted!!
Thanks everyone on this thread
Can u flash custom ROM ???
Nice, Ty
This guy needs help said:
After you flash supersu and it says "this device is not rooted , do you want to root" make sure you say no because that doesnt actually root your device , it just bricks it.
Click to expand...
Click to collapse
Ty, have all the day searching this now is rooted my s5 at the first try
thisisapoorusernamechoice said:
Install TWRP in Odin with auto-reboot disabled, immediately boot into recovery and flash the SuperSUv2.67.zip
Click to expand...
Click to collapse
I tried installing TRWP from Odin, with auto-reboot disabled. It appeared to load into my phone, a window in Odin said "Pass!". But then how do I immediately boot into recovery? None of the keys on my phone were responding. I had to pull the battery. And then when I rebooted with Power - Volume Up, I didn't have the TWRP recovery.
And also, should I be installing twrp-3.0.0-0? Or should I use the newest one twrp-3.0.2-1??
From what I read elsewhere about Odin, once the file has flashed onto your phone, the phone should reboot automatically. If I uncheck auto-reboot, then how do I reboot the phone?
jkq1996 said:
And also, should I be installing twrp-3.0.0-0? Or should I use the newest one twrp-3.0.2-1??
From what I read elsewhere about Odin, once the file has flashed onto your phone, the phone should reboot automatically. If I uncheck auto-reboot, then how do I reboot the phone?
Click to expand...
Click to collapse
Use 3.0.2-1. Uncheck auto reboot, when Odin says pass, simply hold down home, vol+, and power
thisisapoorusernamechoice said:
Use 3.0.2-1. Uncheck auto reboot, when Odin says pass, simply hold down home, vol+, and power
Click to expand...
Click to collapse
Thank you that worked, my phone is rooted!!
Now, I have to decide whether or not I will try to flash a custom ROM, or just delete crap from the phone that I don't want...
Can I use any Root Uninstaller app or is there a good one that someone can recommend??
thisisapoorusernamechoice said:
Install TWRP in Odin with auto-reboot disabled, immediately boot into recovery and flash the SuperSUv2.67.zip
Click to expand...
Click to collapse
I've tried this method twice now - both times the root works but a few days later the root disappears. During the period where the device is rooted everything seems to work correctly including root. I haven't done anything that could possibly remove root - I haven't even restarted my phone. Any ideas? I used Odin v3.10.7, TWRP 3.0.2-1, and SuperSU BETA-v2.71. Should I try it with SuperSU v2.67 instead?
EDIT: I've re-rooted with SuperSU v2.67, if anything happens I'll update this post.