The why
A lot of this has been said in other threads, however I decided to gather all the up-to-date (as of Jun 17, 2014) instructions and info in this thread to alleviate fears of the infamous 'KNOX WARRANTY VOID 0x1' and help people with the process. People with tripped KNOX can of course use this as well, however it won't untrip their devices, duh.
The cheers
First of all big cheers for Pinkie Pie (person who discovered the Linux kernel vulnerability that makes rooting without tripping KNOX possible), geohot (person that used the vulnerability to make a rooting app), chainfire (developer of SuperSU), rovo89 and Tungstwenty (developers of Xposed). Go and donate to these guys if you can!
The what
This post will tell you how to upgrade your P605 to 4.4.2, if you haven't already. And how to install SuperSU and Xposed all the while keeping your KNOX counter at 0x0, CURRENT BINARY: Samsung Official and SYSTEM STATUS: Official!
Note: The versions in this text are just for reference - telling you what versions already worked. New ones will surely also work, so you should usually download the newest available.
The how
Firmware
4.4.2 NEE P605XXUCNE2 (any of the current 4.4.2 firmwares should be fine, although Samsung might use an updated kernel for the future versions, disabling towelroot)
From http://forum.xda-developers.com/showpost.php?p=53092676&postcount=1
Simple instructions available here http://www.sammobile.com/firmwares/3/?download=30325 (you can also download the firmware from here, but download is slow for free accounts)
Root
From http://towelroot.com
No special instructions (it's a 1-click root)
SuperSU
Version 1.99.rc5 from http://download.chainfire.eu/448/SuperSU/
Extract Superuser.apk (in 'common') from the zip, install and run
Answer yes to the Disable KNOX prompt (don't worry, KNOX will not be tripped)
Xposed
From http://repo.xposed.info/module/de.robv.android.xposed.installer (version 2.6.1)
No special instructions
The victory
Congrats! Now you should be on a rooted, SuperSUed, Xposed KitKat with warranty left intact! However before sending it to Samsung, e.g., for repairs, you should flash your original firmware, of course.
Can this be made to work with the SM-P600 on Android 4.3 unrooted? Any help will be appreciated. This would be a dream.
no.0ne said:
SuperSU
Version 1.94 from Google Play (Jun 17, 2014)
Answer yes to the Disable KNOX prompt (don't worry, KNOX will not be tripped)
At the end it will say it failed, however it will be working!
If you are annoyed by the 'failed' message for some reason, download an updated version from http://download.chainfire.eu/448/SuperSU/ (you'll have to flash it manually though) which supposedly fixes it.
Click to expand...
Click to collapse
Just Download specified zip and extract superuser.apk from common folder and install as normal program, don't download play version
İ am gonna try and write my appreciate ) thanks in advance
It did work . Thanks to you and that steps i have rooted kitkat knox is 0*0 what i was waiting for last 5 months. Thank you so much now i can use my tablet in full capacity
iPhone 'den Tapatalk aracılığı ile gönderildi
Eudeferrer said:
Can this be made to work with the SM-P600 on Android 4.3 unrooted? Any help will be appreciated. This would be a dream.
Click to expand...
Click to collapse
It seems that so far people have had no success using towelroot on P600. Wait and hope it will change...
Hello, i want to do this on clean tablet, so i want to do clean install , how can i clean it all had before, from odin? And is nee nordic kitkat rom suitable for all p605 , i am frightened about boatloader problem and soft brick before i done i wanted to ask. Thanks in advance.
yararli said:
Hello, i want to do this on clean tablet, so i want to do clean install , how can i clean it all had before, from odin? And is nee nordic kitkat rom suitable for all p605 , i am frightened about boatloader problem and soft brick before i done i wanted to ask. Thanks in advance.
Click to expand...
Click to collapse
You can wipe the tablet from recovery:
Turn tablet off
Turn it on holding Volume Up + Power Button until you see something on the screen
Wipe data/factory reset
Reboot
NEE will be fine for all P605, however I don't know if it works with something like P605V (US Verizon).
no.0ne said:
You can wipe the tablet from recovery:
Turn tablet off
Turn it on holding Volume Up + Power Button until you see something on the screen
Wipe data/factory reset
Reboot
NEE will be fine for all P605, however I don't know if it works with something like P605V (US Verizon).
Click to expand...
Click to collapse
Should i do this before or after kitkat installation ? And where can i find usb installation of p605 when it is taken into download mode for pc to recognize the tablet.
I have no windows pc now im gonna do that on thursday ı was waiting this topic for 4 months thank you so much
iPhone 'den Tapatalk aracılığı ile gönderildi
yararli said:
Should i do this before or after kitkat installation ? And where can i find usb installation of p605 when it is taken into download mode for pc to recognize the tablet.
I have no windows pc now im gonna do that on thursday ı was waiting this topic for 4 months thank you so much
iPhone 'den Tapatalk aracılığı ile gönderildi
Click to expand...
Click to collapse
First you wipe then you flash
You can download the driver from the Samsung website, e.g., http://www.samsung.com/us/support/owners/product/SM-P605VZKEVZW (don't worry that it is on the US page, the driver is the same for all Samsung devices)
Glad I can help. I waited for root quite long myself :victory:
In the thread discussing towelroot on P605, people claimed installing xposed would change your binary to custom. That's holding me back for now, can you confirm that it stays official?
Matthias.ja said:
In the thread discussing towelroot on P605, people claimed installing xposed would change your binary to custom. That's holding me back for now, can you confirm that it stays official?
Click to expand...
Click to collapse
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
valexi said:
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
Click to expand...
Click to collapse
alright, thanks!
so if i have some warranty issues, wiping everything from recovery or re-flashing the unrooted stock ROM would make everything official again, right? I know I sound like a scared little girl, but I just really don't want to risk my warranty on this rather expensive device
Heyy its wonderful i did it but there is a problem about kitkat rom i saw a little lags and the biggest problem is whatsapp says it is not compatible with this device also twitter in playstore what should i do thnx for your all help
iPhone 'den Tapatalk aracılığı ile gönderildi
valexi said:
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
Click to expand...
Click to collapse
So i just tried and installed xposed, and funnily enough, my system status stayed official, even inside the ROM. I won't complain though..
Hello i should restore system defaults how should i do directly by using recovery mode can i clean systam cache and ... Or before it should i unroot from su?
iPhone 'den Tapatalk aracılığı ile gönderildi
To make sure; unroot and then factory reset
Matthias.ja said:
So i just tried and installed xposed, and funnily enough, my system status stayed official, even inside the ROM. I won't complain though..
Click to expand...
Click to collapse
As long using stock recovery and it will stay Official. Just custom recovery will give custom.
dt33 said:
As long using stock recovery and it will stay Official. Just custom recovery will give custom.
Click to expand...
Click to collapse
No it doesn't. You dont seem to understand difference between "system status" in Download mode or inside of the ROM.
Here is couple of pictures to make you understand.
In the picture below you can see system status official. This will change, if you install CUSTOM ROM or CUSTOM RECOVERY. Towelroot does not change any of these data here:
In the picture below you can see Device status "custom". This can change to custom if you ROOT the device and/or install SuperSU or Xposed framework. This has NOTHING to do with the status in the Download mode as seen in the first picture.
I hope that people wouldn't mix these things, because they are rather easy to understand. Talking about things that you dont really understand will cause confusion and makes people asking more stupid questions.
Thank you!
valexi said:
No it doesn't. You dont seem to understand difference between "system status" in Download mode or inside of the ROM.
Here is couple of pictures to make you understand.
In the picture below you can see system status official. This will change, if you install CUSTOM ROM or CUSTOM RECOVERY. Towelroot does not change any of these data here:
In the picture below you can see Device status "custom". This can change to custom if you ROOT the device and/or install SuperSU or Xposed framework. This has NOTHING to do with the status in the Download mode as seen in the first picture.
I hope that people wouldn't mix these things, because they are rather easy to understand. Talking about things that you dont really understand will cause confusion and makes people asking more stupid questions.
Thank you!
Click to expand...
Click to collapse
Pls, explain how come it stays Official after rooted with towelroot, installed SuperSu and Xposed?
http://forum.xda-developers.com/showpost.php?p=53452193&postcount=33
dt33 said:
Pls, explain how come it stays Official after rooted with towelroot, installed SuperSu and Xposed?
http://forum.xda-developers.com/showpost.php?p=53452193&postcount=33
Click to expand...
Click to collapse
I'm not quite sure, but it seems that in some cases the ROM can detect if it's rooted.
For me it changed to "Custom" after rooting with towelroot and SuperSU installation. I changed it back to Official with Wanam xposed.
Related
I managed to get root, and with the help of the KNOX Disabler app, I disabled Knox nonsense, using RootExplorer, deleted the Knox files from /system/apps folder.
You need to flash Philz_touch_5.15.0-n7100.tar.md5 recovery, reboot. Switch off phone. Start phone in recovery mode. Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5.
Restart phone and run previously installed KNOX Disabler. I downloaded and installed the version 1.0.1.
Let me know how you get on.
Thanks to the dev owners of the said recovery, CWM-SuperSu and KNOX Disabler.
I am a happy user again. Lol!
how about warranty bit status in download mode? still 0?
sora9009 said:
how about warranty bit status in download mode? still 0?
Click to expand...
Click to collapse
I did not care about Knox warranty, however following your question I went into download mode. This is what I see:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (12 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
WARRANTY BIT: 0
That is all the information at present. I hope this answers your question.
Cheers.
thanks for answering.:good:
sora9009 said:
thanks for answering.:good:
Click to expand...
Click to collapse
You are welcome.
YOSEFE said:
I managed to get root, and with the help of the KNOX Disabler app, I disabled Knox nonsense, using RootExplorer, deleted the Knox files from /system/apps folder.
You need to flash Philz_touch_5.15.0-n7100.tar.md5 recovery, reboot. Switch off phone. Start phone in recovery mode. Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5.
Restart phone and run previously installed KNOX Disabler. I downloaded and installed the version 1.0.1.
Let me know how you get on.
Thanks to the dev owners of the said recovery, CWM-SuperSu and KNOX Disabler.
I am a happy user again. Lol!
Click to expand...
Click to collapse
Sorry--but this is a bit ambiguous--
"Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5."
I follow that we Flash CWM-Supersu-v.0.99. zip in Philz Recovery[which we have previously flashed to device with ODIN]--but what is the tar.md5 bit about--surely we don't reflash Philz in ODIN, again--or, are you simply referring to the, now, on board, CWM Recovery?
Not trying to be a 'smart-alec' just not following.
be a smart user and assume that he just copy paste the previous line because he dont want to retype the recovery name.
Hey, @YOSEFE, just another question--which ROM were you using before you Flashed this latest leak?
Reason I'm asking is that, I am currently on Dr.Ketan's 'hybrid' ROM which is a mix of XXMI6, and XXMJ2 plus mods taken from latest Note3 firmwares--and, it's great with many things not available to standard Note 2.
I would like your opinion of this latest leak firmware, XXUEMJ5, and how it compares--presumably it doesn't have any of the fancy Note 3 'gizmos'???
But, is it fast, smooth, clean, not buggy. etc....
BTW I'm not saying that Dr. K's ROM is not super fast, smooth, clean, etc...in fact it's excellent but, just wanting a comparison, to see if there was any good reason to Flash it.
haybill said:
Sorry--but this is a bit ambiguous--
"Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5."
I follow that we Flash CWM-Supersu-v.0.99. zip in Philz Recovery[which we have previously flashed to device with ODIN]--but what is the tar.md5 bit about--surely we don't reflash Philz in ODIN, again--or, are you simply referring to the, now, on board, CWM Recovery?
Not trying to be a 'smart-alec' just not following.
Click to expand...
Click to collapse
Philz Recovery will have already been flashed by others, however I mention it because there will be those who have not flashed anything past the firmware or ROM.
If CWM Recovery works for anyone that is fine too, but I have flashed Philz Recovery on advice somewhere in a thread. (Lazy me, can't say which thread).
edan1979 said:
be a smart user and assume that he just copy paste the previous line because he dont want to retype the recovery name.
Click to expand...
Click to collapse
You are 100% correct.
haybill said:
Hey, @YOSEFE, just another question--which ROM were you using before you Flashed this latest leak?
Reason I'm asking is that, I am currently on Dr.Ketan's 'hybrid' ROM which is a mix of XXMI6, and XXMJ2 plus mods taken from latest Note3 firmwares--and, it's great with many things not available to standard Note 2.
I would like your opinion of this latest leak firmware, XXUEMJ5, and how it compares--presumably it doesn't have any of the fancy Note 3 'gizmos'???
But, is it fast, smooth, clean, not buggy. etc....
BTW I'm not saying that Dr. K's ROM is not super fast, smooth, clean, etc...in fact it's excellent but, just wanting a comparison, to see if there was any good reason to Flash it.
Click to expand...
Click to collapse
I was on XXMI6. The ROM can be a bit laggy. As someone pointed out to me, it is only a test firmware. Nevertheless, it is smooth enough for my daily use.
There are obviously no Note 3 goodies on the ROM. If those are very important to you, and considering the amount of trouble you have gone through to flash Doc's ROM, I would say keep Doc's ROM.
Thanks for the info @YOSEFE, The Good Doctor's latest work is pretty cool and definitely what I want. Sometimes we get caught up in Flash mania and need to find a good solution and stick with it.
All the best.
Sent from my GT-N7100 using xda app-developers app
edan1979 said:
be a smart user and assume that he just copy paste the previous line because he dont want to retype the recovery name.
Click to expand...
Click to collapse
Thanks for your input--nice to know some of us are smart alecs.
I agree with what you have said below.
haybill said:
Thanks for the info @YOSEFE, The Good Doctor's latest work is pretty cool and definitely what I want. Sometimes we get caught up in Flash mania and need to find a good solution and stick with it.
All the best.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
how can i use efs professioal to fix 0049 imei problem?
does any body know how to use it?
OP:
R u on mj5?
Knox Disabler only disables notifications?
Thx
Sent from my GT-N7100 using Tapatalk
I'm on MJ5.
I have no knox notifications anymore.
I also used Root Explorer to search for all knox files and references to knox, I then deleted all these. My phone still works well.
No guarantees from me though. I took a risk, thankfully, my phone did not suffer any problems.
Sent from my GT-I9505 using xda app-developers app
I am just an end user like most people. I don't know anything about EFS issues.
I'm unable to comment on the question you asked.
Sent from my GT-I9505 using xda app-developers app
YOSEFE said:
I managed to get root, and with the help of the KNOX Disabler app, I disabled Knox nonsense, using RootExplorer, deleted the Knox files from /system/apps folder.
You need to flash Philz_touch_5.15.0-n7100.tar.md5 recovery, reboot. Switch off phone. Start phone in recovery mode. Flash CWM-SuperSu-v0.99.zip in Philz_touch_5.15.0-n7100.tar.md5.
Restart phone and run previously installed KNOX Disabler. I downloaded and installed the version 1.0.1.
Let me know how you get on.
Thanks to the dev owners of the said recovery, CWM-SuperSu and KNOX Disabler.
I am a happy user again. Lol!
Click to expand...
Click to collapse
LOL , Why we need KNOX Disabler ? Installing that app ask fr root permission . And if i am rooted why do i need to disable it its already disabled.
BTW Not work on Note 7100 4.3 JB
Formingus said:
LOL , Why we need KNOX Disabler ? Installing that app ask fr root permission . And if i am rooted why do i need to disable it its already disabled.
BTW Not work on Note 7100 4.3 JB
Click to expand...
Click to collapse
You are too late in responding to this.
That method you refer to was one of the two or so of available means. Since then, Chainfire has released superuser version that incorporates a disabler or uninstaller.
just wanted to let u know that I successfully rooted my sm-p905 with geohot's rooting method without tripping knox!!!
its just a simple apk installation procedure....!!!
I bet all the TNT/ V guys will be happy to hear that......
have fun!!
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=206285968
snir2 said:
just wanted to let u know that I successfully rooted my sm-p905 with geohot's rooting method without tripping knox!!!
its just a simple apk installation procedure....!!!
I bet all the TNT/ V guys will be happy to hear that......
have fun!!
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=206285968
Click to expand...
Click to collapse
A PHOTO
snir2 said:
A PHOTO
Click to expand...
Click to collapse
Can I ask a huge favor? Can you write a simple list of steps you did. That thread is chaos from people who have 10 different devices. Like a simple
1. step a
2. step b
I don't want to screw up the device I just bought yesterday lol.
Jpfan01 said:
Can I ask a huge favor? Can you write a simple list of steps you did. That thread is chaos from people who have 10 different devices. Like a simple
1. step a
2. step b
I don't want to screw up the device I just bought yesterday lol.
Click to expand...
Click to collapse
sure,
1. downloaded the file from towelroot.com
2. installed the apk file
3. Run the app
4. the device rebooted
5. installed supersu from the play store
done....
snir2 said:
sure,
1. downloaded the file from towelroot.com
2. installed the apk file
3. the device rebooted
4. installed supersu from the play store
done....
Click to expand...
Click to collapse
Wow, Ok I thought there would be more haha. You said you were on a sm-p905, I wonder if this will go as smooth on an sm-p900. I'm on the wifi not lte version. Any guess?
Thanks for summarizing that though.
edit: seeing mixed results related to the Exynos chips from people's s4s and s5s. hmm.
snir2 said:
just wanted to let u know that I successfully rooted my sm-p905 with geohot's rooting method without tripping knox!!!
its just a simple apk installation procedure....!!!
I bet all the TNT/ V guys will be happy to hear that......
have fun!!
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=206285968
Click to expand...
Click to collapse
Can you please tell more details about your SM-P905
AP, CP, CSC (These can be found at least on SM-P905 by opening dialer, then type *#1234#)
Kernel version (Settings - General - About device)
And for any else of you, if you try this method, report please how did it go, did you got root? did it trip KNOX flag and what firmware version you were using, thanks
I have the international SM P905 this method did not work. Tried it twice
Sent from my SM-P905 using Tapatalk
Jpfan01 said:
Wow, Ok I thought there would be more haha. You said you were on a sm-p905, I wonder if this will go as smooth on an sm-p900. I'm on the wifi not lte version. Any guess?
Thanks for summarizing that though.
edit: seeing mixed results related to the Exynos chips from people's s4s and s5s. hmm.
Click to expand...
Click to collapse
anyway from what i have read so far there is no harm in trying...... In the worst case scenario it will not work....
SM-P900 On KOT49H.P900XXUANC4
Does not work, but did not trigger knox. So no harm no fowl. Shame, really got my hopes up.
Spere said:
Can you please tell more details about your SM-P905
AP, CP, CSC (These can be found at least on SM-P905 by opening dialer, then type *#1234#)
Kernel version (Settings - General - About device)
And for any else of you, if you try this method, report please how did it go, did you got root? did it trip KNOX flag and what firmware version you were using, thanks
Click to expand...
Click to collapse
here
snir2 said:
here
Click to expand...
Click to collapse
Thank you..
Anyway, I pulled the trigger and tried this on my SM-P905, it kinda worked.. I'll post my device info later since I didn't have time for that, had to go to work just after rooting..
SM-P905
AP: P905XXUAND1
CP: P905XXUANA7
CSC: P905NEEAND1
Kernel verison: 3.4.0-1131235 (April 3 2014)
Okay then..
I installed and ran tr.apk
Then after reboot I checked recovery
KNOX Warranty Void: 0x0
System status: custom
Then I installed SuperSU (v1.94 if I remember right) from play store (and paid version also)
When I open SuperSU, it asks me to install binary. Since I got stock recovery, I can't use that option and instead choose normal way.
SuperSU says: install failed, please reboot your device
Anyway my device is rooted since Greenify and couple other root apps worked (and SuperSU asked to grand or deny access for those apps)
But because I cannot install that binary, I cannot open SuperSU to change settings etc..
There is v1.99r4(?) of SuperSU, but that is flashable .zip file, and how I'm supposed to install that with stock recovery. And I'm sceptic about flashing anything, in case of triggering KNOX.
Okay, as #snir2 said, I downloaded SuperSU from HERE (was v1.99r5). I unzip that and took Superuser.apk from there and installed it on my NP 12.2. After that SU updated binary using normal method like it should and everythings ok
And after all this odin mode still shows this:
System Status: Custom
KNOX Warranty Void: 0x0
Will do some tests tomorrow and if there comes anything interesting, I'll post some info..
Sent from my SM-N9005 using XDA Premium HD app
Spere said:
Thank you..
When I open SuperSU, it asks me to install binary. Since I got stock recovery, I can't use that option and instead choose normal way.
SuperSU says: install failed, please reboot your device
But anyway my device is rooted since Greenify and couple other root apps worked (and SuperSU asked to grand or deny access for those apps)
But because I cannot install that binary, I cannot open SuperSU to change settings etc..
There is v1.99r4(?) of SuperSU, but that is flashable .zip file, and how I'm supposed to install that with stock recovery. And I'm sceptic about flashing anything, in case of triggering KNOX.
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
JUST OPEN THE Zip.
U will find the apk file inside...
milan188 said:
I have the international SM P905 this method did not work. Tried it twice
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
did u check with "root checker"?
at first the binaries weren't installed for me, but, when checking with "root checker" I did have root.
the supersu in the play store is not the last version of the app... u need to download it from chainfire's site:
download.chainfire.eu/supersu
then it will install the binaries
snir2 said:
JUST OPEN THE Zip.
U will find the apk file inside...
Click to expand...
Click to collapse
Thank you, that did work!!
Spere said:
Thank you..
Anyway, I pulled the trigger and tried this on my SM-P905, it kinda worked.. I'll post my device info later since I didn't have time for that, had to go to work just after rooting..
SM-P905
AP: P905XXUAND1
CP: P905XXUANA7
CSC: P905NEEAND1
Kernel verison: 3.4.0-1131235 (April 3 2014)
Okay then..
I installed and ran tr.apk
Then after reboot I checked recovery
KNOX Warranty Void: 0x0
System status: custom
Then I installed SuperSU (v1.94 if I remember right) from play store (and paid version also)
When I open SuperSU, it asks me to install binary. Since I got stock recovery, I can't use that option and instead choose normal way.
SuperSU says: install failed, please reboot your device
Anyway my device is rooted since Greenify and couple other root apps worked (and SuperSU asked to grand or deny access for those apps)
But because I cannot install that binary, I cannot open SuperSU to change settings etc..
There is v1.99r4(?) of SuperSU, but that is flashable .zip file, and how I'm supposed to install that with stock recovery. And I'm sceptic about flashing anything, in case of triggering KNOX.
Okay, as #snir2 said, I downloaded SuperSU from HERE (was v1.99r5). I unzip that and took Superuser.apk from there and installed it on my NP 12.2. After that SU updated binary using normal method like it should and everythings ok
And after all this odin mode still shows this:
System Status: Custom
KNOX Warranty Void: 0x0
Will do some tests tomorrow and if there comes anything interesting, I'll post some info..
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
mine says: "System Status: official"
snir2 said:
mine says: "System Status: official"
Click to expand...
Click to collapse
I'm not worried about custom status because if I'm right:
- I cannot accidentally update phone since OTA is not possible with custom status
- I can fake status back to official using Wanam Xposed
- I can get status back also by flashing stock rom again, if I need to
Does this work on WiFi only version?
Sent from my SM-N900P using XDA Free mobile app
milan188 said:
I have the international SM P905 this method did not work. Tried it twice
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
For those who can't root for P905 (LTE version), I have found a solution.
1. Update the kernel to NC1 or newer through Download Mode
(like this one at the bottom of OP)
2. Root with towelroot. This time if you see those wordings after pressing "Make it ra1n", it works!
I have P905ZSUANB1/P905XXUANA7/P905OZSANB1 on my tablet and after I update the kernel to NC1, I got it rooted! YAY!
BTW I get "System status: Official" in both Download Mode and under Settings, and also 0x0 for the f**king KNOX thing
One4mNoWhere said:
Does this work on WiFi only version?
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
maybe try reading the previous posts.. no it doesnt.
Sent from my HTC6435LVW using Tapatalk
Broomfundel said:
SM-P900 On KOT49H.P900XXUANC4
Does not work, but did not trigger knox. So no harm no fowl. Shame, really got my hopes up.
Click to expand...
Click to collapse
Seconded, on SM-P900 this did not work. Tried twice. Though I had my hunch it would not.
I just tested Towelroot on my GT-I9506 running latest NEE 4.3 and it worked like a charm and did not trigger Knox.
Thread found here:
http://forum.xda-developers.com/showthread.php?t=2783157
Happy rooting
banerbocken said:
I just tested Towelroot on my GT-I9506 running latest NEE 4.3 and it worked like a charm and did not trigger Knox.
Thread found here:
http://forum.xda-developers.com/showthread.php?t=2783157
Happy rooting
Click to expand...
Click to collapse
Works perfectly!
Please, can you help me?
I've downloaded the towelroot apk and installed it. Then, once the phone was rebooted, I've installed supersu from playstore, but it ask me to update de SU binaries, I select the normal option but it gives me a message about samsung knox and if I want to try to disable it, I select no because I don't know if it will affect to the knox counter.... What are the steps please?
And if I download the suggested SuperSU from the towelroot thread, I can't install it because it's a flashable zip that I can't install because I have stock recovery...
Alestilohomer said:
Please, can you help me?
I've downloaded the towelroot apk and installed it. Then, once the phone was rebooted, I've installed supersu from playstore, but it ask me to update de SU binaries, I select the normal option but it gives me a message about samsung knox and if I want to try to disable it, I select no because I don't know if it will affect to the knox counter.... What are the steps please?
And if I download the suggested SuperSU from the towelroot thread, I can't install it because it's a flashable zip that I can't install because I have stock recovery...
Click to expand...
Click to collapse
Towelroot installs needed files for root. I didnt install SuperSU at all from play store cause its not latest version.
ChainFire is updating SuperSU soon and when latest version (1.99) is online you can install it from play store.
After Towelroot I just installed Titanium Backup (and pro key) and freezed all crap including knox.
After using towelroot on a KNOX-enabled stock 4.3 device, is is possible to revert back to the 4.2.2 bootloader without burning the e-fuse?
Ok, tried to delete system apps, including the knox ones, with root explorer and was successfull!
And about the downgrade, it will change the knox status for sure, because knox is in the bootloader too, not only the apps and libraries, and here, root doesn't made any chance...
Enviado desde mi GT-I9506 mediante Tapatalk
The KNOX e-fuse should be burned only by the bootloader in ODIN mode when it flashes an unsigned file to the device. Getting local root on the device and writing a new bootloader directly to the flash should not be able to affect the e-fuse?
tlund said:
The KNOX e-fuse should be burned only by the bootloader in ODIN mode when it flashes an unsigned file to the device. Getting local root on the device and writing a new bootloader directly to the flash should not be able to affect the e-fuse?
Click to expand...
Click to collapse
It is slightly wrong. You shoud burned KNOX when you flash different version of kernel, recovery, bootloader.
You can flash system, modem, NON-HLOS and maybe others. I've tested only system and NON-HLOS.
Now I have my GT-I9506 Singapore version with KNOX warranty void 0x0 in this configuration:
System and NON-HLOS from Finladian version: I9506XXUBNE1
The others from original Sigapore version: I9506XXUBND2
towelroot.com installed and working!
Thanks to towelroot
tomogo said:
It is slightly wrong. You shoud burned KNOX when you flash different version of kernel, recovery, bootloader.
You can flash system, modem, NON-HLOS and maybe others. I've tested only system and NON-HLOS.
Click to expand...
Click to collapse
Yes, but you are talking about flashing this via download/odin mode, right?
My point is that with root, you should be able to modify the flash directly, overwriting the bootloader.
Would it be possible to receive original updates OTA with this root?
Sendt fra min GT-I9506 med Tapatalk
Probably not
topimax said:
Would it be possible to receive original updates OTA with this root?
Sendt fra min GT-I9506 med Tapatalk
Click to expand...
Click to collapse
As we have root I would think (so don't quote me on this) that OTA is blocked. But as I see it it does not really matter as the next update for this devise is probably going to be 4.4.2 and flashing that probably also means loosing root.
Now that was a lot of probably but as I see it..
You need "Official" status under Phone Info to receive OTA updates. ROOT will be overwritten by the updates.
After root it's very common to have "Custom" status, but you can cheat it with Traingle away app (not tested by me) or sometimes you can be "Official"after Wipe ( it depends what changes has been done to the system)
mar10o said:
You need "Official" status under Phone Info to receive OTA updates. ROOT will be overwritten by the updates.
After root it's very common to have "Custom" status, but you can cheat it with Traingle away app (not tested by me) or sometimes you can be "Official"after Wipe ( it depends what changes has been done to the system)
Click to expand...
Click to collapse
I would think getting the OS" 4.4.2 is only part of the package (BTW 4.2.2 vrzn w/gs4 rooted with ease) but you also get other surprises...
Not exactly like a box if lucky charms either.
Samsung or vrzn either one are not fond of rooting.
Triangle away didn't help me unless i did something wrong.. I still have the unlock icon when booting and phone info says "custom" but knox is 0x0
Sent from my GS4 Zombie Communicator
windstrings said:
I would think getting the OS" 4.4.2 is only part of the package (BTW 4.2.2 vrzn w/gs4 rooted with ease) but you also get other surprises...
Not exactly like a box if lucky charms either.
Samsung or vrzn either one are not fond if rooting.
Triangle away didn't help me unless i did something wrong.. I still have the unlock icon when booting and phone info says "custom" but knox is 0x0
Sent from my GS4 Zombie Communicator
Click to expand...
Click to collapse
Was told that xposed could chance the status from custom to official.
Sendt fra min GT-I9506 med Tapatalk
For those who failed check last version !
For me
V1 Towel root didn't work
V2 towel root didn't work
V2.1 (downloaded today) = SUCESS
I9505XXUFNC4
Will it work in gt-I9505 4.4.2 XXUFNBA without tripping knox
bertrand13 said:
For me
V1 Towel root didn't work
V2 towel root didn't work
V2.1 (downloaded today) = SUCESS
I9505XXUFNC4
Click to expand...
Click to collapse
I do not seem to be able to find V 2.1 Can you guide me please? Thanks
Don't know why he doesn't label his site or the filename better but it should be the latest version when you download from his site.
When you open the app to install it, it should say the version at the top.
Sent from my GS4 Zombie Communicator
mohammedkhairy said:
Will it work in gt-I9505 4.4.2 XXUFNBA without tripping knox
Click to expand...
Click to collapse
It should work. It does not trip Knox
kerko said:
I do not seem to be able to find V 2.1 Can you guide me please? Thanks
Click to expand...
Click to collapse
Well I downloaded it from the towelroot web :laugh::laugh:
I saw on XDA tnat somebody mentionned a new version so I tried
If you need more PM me...
hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/
jgfernog said:
hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/
Click to expand...
Click to collapse
Same here , when Im rooting doesnt show anything , and the smartphone turns on without showing the red android that suppose to show
jgfernog said:
hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/
Click to expand...
Click to collapse
Same here, maybe installing xposed and putting a request for a module? although s health and private mode don't work on my note 4 either (xposed running)
UnboundDemon said:
Same here, maybe installing xposed and putting a request for a module? although s health and private mode don't work on my note 4 either (xposed running)
Click to expand...
Click to collapse
this is a kernel related, I think. Everybody says that it still working on Snapdragon's Note 4, but here at Exynos, you can't activate it.
jgfernog said:
this is a kernel related, I think. Everybody says that it still working on Snapdragon's Note 4, but here at Exynos, you can't activate it.
Click to expand...
Click to collapse
I dont think it is that, I have a friend with the same model that us, and the activation works on his phone :s
So, guys, have anyone solved this problem?
I also have rooted Note 4 and neither "Remote controls" nor "reactivation lock" can I activate...
reactivetion lock not working
I also encountered a similar case but only used through l launch , give me one new idea when it dies in it :good:
Guys, has anybody solved this problem?
Here I am, rooted GS5 with MM fw, before root it worked, as it did with lollipop and kitkat.
After root it doesn't turn on anymore, I reflashed stock recovery too. I guess it's related to knox 0x1, with rooted knox 0x0 kitkat and lollipop I could enable it.
Or maybe it's kernel related, so systemless root with stock kernel could be the solution
Good news, after reflashing a stock firmware I could enable RL back. So it's not knox related but root related. Tomorrow I'll try with systemless root
Joker87 said:
Good news, after reflashing a stock firmware I could enable RL back. So it's not knox related but root related. Tomorrow I'll try with systemless root
Click to expand...
Click to collapse
I think what is needed it to copy your stock recovery from an official touchwiz rom and flash it. You will need a tar.gz converter to flash it via odin. Sometime ago I tried it where your root remains but you have a stock recovery. I believe all those Samsung security features like Reactivation Lock relies on a stock recovery and not a custom like ( TWRP/CWM)
chaundb said:
I think what is needed it to copy your stock recovery from an official touchwiz rom and flash it. You will need a tar.gz converter to flash it via odin. Sometime ago I tried it where your root remains but you have a stock recovery. I believe all those Samsung security features like Reactivation Lock relies on a stock recovery and not a custom like ( TWRP/CWM)
Click to expand...
Click to collapse
I reflashed stock recovery but still no luck. It's root related, or better kernel related, as someone posted above. I'm on systemless root and it shows "warranty bit kernel" message at boot. With rooted lollipop and stock kernel/recovery it worked
Joker87 said:
I reflashed stock recovery but still no luck. It's root related, or better kernel related, as someone posted above. I'm on systemless root and it shows "warranty bit kernel" message at boot. With rooted lollipop and stock kernel/recovery it worked
Click to expand...
Click to collapse
Really, so how can I do the same on Marshmallow. Where can I obtain a systemless root method for my SM-N910H Note 4 ???
chaundb said:
Really, so how can I do the same on Marshmallow. Where can I obtain a systemless root method for my SM-N910H Note 4 ???
Click to expand...
Click to collapse
Just flash supersu beta via twrp
You must have stock boot.img, I suggest reflashing the entire stock firmware if you did some modifications
Joker87 said:
Just flash supersu beta via twrp
You must have stock boot.img, I suggest reflashing the entire stock firmware if you did some modifications
Click to expand...
Click to collapse
Look...i am currently rooted. I have twrp 3.0 and i flashed super su beta. I dont have any modified or special kernels of that sort...just root. So are you telling me all i need to do is flash the original touchwiz boot.img from the marshmallow rom file ( i will have to go convert it to a Tar file) ???.... And that will give me the ability to stay rooted and be able to use reactivation lock again ???
chaundb said:
Look...i am currently rooted. I have twrp 3.0 and i flashed super su beta. I dont have any modified or special kernels of that sort...just root. So are you telling me all i need to do is flash the original touchwiz boot.img from the marshmallow rom file ( i will have to go convert it to a Tar file) ???.... And that will give me the ability to stay rooted and be able to use reactivation lock again ???
Click to expand...
Click to collapse
Nope... rl doesn't work with any root method
Joker87 said:
Nope... rl doesn't work with any root method
Click to expand...
Click to collapse
Ok..thats what i thought.......its best we stay without it then. Or go back completely stock and unrooted to use the feature.
Hello, seen there is no new news about this.. Has anyone got around this?
Can we root and activate the reactivation lock now?
Thanks
Hello,
I have a galaxy s4 on 4.4.2 that I rooted using kingroot a while back. It is a US Cellular SCH-R970. Knox has not been tripped. Under device status it says the phone is custom. This means I cannot update to 5.0.1.
My question is, how would I return the phone to official status without 1. Tripping knox, and 2. Keeping all of my data. Also, do you know if I can root with kingroot once I get on 5.0.1.
Baseband is R970TYUFNK1.
Thank You!
Hi,
Flash a proper complete stock firmware via ODIN. Firmware for R970TYUFNK1 is R970TYUFNK1 (itself).
Sent from my GT-I9500
krasCGQ said:
Hi,
Flash a proper complete stock firmware via ODIN. Firmware for R970TYUFNK1 is R970TYUFNK1 (itself).
Sent from my GT-I9500
Click to expand...
Click to collapse
Would you happen to know where I can find a download for that? Also wouldn't flashing that delete everything?
Thanks for all the help!
BeastMode6 said:
Would you happen to know where I can find a download for that? Also wouldn't flashing that delete everything?
Thanks for all the help!
Click to expand...
Click to collapse
SamMobile, Samsung Updates, or via SamFirm app. I usually rely on SamFirm.
Edit: As long as Re-partition and NAND Erase All is unticked on Odin, it should be fine.
PS Note: You can install newer firmware over your current firmware via Odin, too.
Sent from my GT-I9500
krasCGQ said:
SamMobile, Samsung Updates, or via SamFirm app. I usually rely on SamFirm.
PS Note: You can install newer firmware over your current firmware via Odin, too.
Sent from my GT-I9500
Click to expand...
Click to collapse
This won't delete anything on my phone though, right?
BeastMode6 said:
This won't delete anything on my phone though, right?
Click to expand...
Click to collapse
It would be wise to backup and wipe data before flashing. Otherwise you might encounter problems.
And do not use kingoroot to root lollipop. It used to not work or cause problems. Use cf autoroot method, if your device is supported.
GDReaper said:
It would be wise to backup and wipe data before flashing. Otherwise you might encounter problems.
And do not use kingoroot to root lollipop. It used to not work or cause problems. Use cf autoroot method, if your device is supported.
Click to expand...
Click to collapse
Problem is cf auto root trips knox.
If I flash R970TYUgoh2 would I keep knox at 0x0 and all of my apps? Then I can root with kingroot.
BeastMode6 said:
Problem is cf auto root trips knox.
If I flash R970TYUgoh2 would I keep knox at 0x0 and all of my apps? Then I can root with kingroot.
Click to expand...
Click to collapse
Yes, but backup is mandatory. About Kingroot, see again previous post.
Sent from my GT-I9500
BeastMode6 said:
Problem is cf auto root trips knox.
If I flash R970TYUgoh2 would I keep knox at 0x0 and all of my apps? Then I can root with kingroot.
Click to expand...
Click to collapse
Having knox triggered is just a bunch of crap from Samsung to scare you. Unless you actually use knox. Or if you are afraid from losing your warranty. Which is also crap, because, whilst reading the warranty file, I saw that it won't cover water damage, it won't cover a broken screen and a bunch of other stuff. The only thing it covers is actual hardware failure. And if the phone is new, that's pretty unlikely. Even if it does fail, Samsung has no way to see if knox has been triggered until they change your hardware and are able to boot up the phone. At that point they can't refuse to take it into warranty service anymore.
GDReaper said:
Having knox triggered is just a bunch of crap from Samsung to scare you. Unless you actually use knox. Or if you are afraid from losing your warranty. Which is also crap, because, whilst reading the warranty file, I saw that it won't cover water damage, it won't cover a broken screen and a bunch of other stuff. The only thing it covers is actual hardware failure. And if the phone is new, that's pretty unlikely. Even if it does fail, Samsung has no way to see if knox has been triggered until they change your hardware and are able to boot up the phone. At that point they can't refuse to take it into warranty service anymore.
Click to expand...
Click to collapse
Wow, that warranty is a load of ****. Also the phone is over a year old so I'd doubt it's still under warranty anyway.
What would you recommend to make a backup? I don't have fast Internet at all (300 kbps down), so I think a local backup would be more efficient.
Thanks for all the help! Have a good Christmas!
BeastMode6 said:
Wow, that warranty is a load of ****. Also the phone is over a year old so I'd doubt it's still under warranty anyway.
What would you recommend to make a backup? I don't have fast Internet at all (300 kbps down), so I think a local backup would be more efficient.
Thanks for all the help! Have a good Christmas!
Click to expand...
Click to collapse
Since it is rooted I suggest titanium backup to backup apps and data.
GDReaper said:
Since it is rooted I suggest titanium backup to backup apps and data.
Click to expand...
Click to collapse
OK I flashed 5.0.1 successfully, all my data carried over. Now I need to root. Do you know where I can download the cf autoroot files for jflteusc or sch-r970 on 5.0.1?
There is a cf auto root thread in the general section. Or you could simply google "cf auto root s4".
Make sure to read the thread.
GDReaper said:
There is a cf auto root thread in the general section. Or you could simply google "cf auto root s4".
Make sure to read the thread.
Click to expand...
Click to collapse
I got it, now on 5.0.1 rooted. Would it be safe to install cwm via odin?
BeastMode6 said:
I got it, now on 5.0.1 rooted. Would it be safe to install cwm via odin?
Click to expand...
Click to collapse
cwm is outdated. Use twrp. And yes, you can install it via odin or other methods.
GDReaper said:
cwm is outdated. Use twrp. And yes, you can install it via odin or other methods.
Click to expand...
Click to collapse
OK I have that installed now. I'm looking for some new roms and found that there are practically none for the sch-r970. Could I just use roms for the gt i9505 (jflte) or would this not work at all? I'm looking for a 6.0 rom.
JDCTeam AOSP has your device model on the support list. They have Lollipop and Marshmallow.
But you should be able to use other GT-I9505 roms too.
GDReaper said:
JDCTeam AOSP has your device model on the support list. They have Lollipop and Marshmallow.
But you should be able to use other GT-I9505 roms too.
Click to expand...
Click to collapse
Under their downloads section they have 2 untagged files (doesn't say GSM or cmda) and one GSM (won't work). Will one of the untagged roms work?
BeastMode6 said:
Under their downloads section they have 2 untagged files (doesn't say GSM or cmda) and one GSM (won't work). Will one of the untagged roms work?
Click to expand...
Click to collapse
Marshmallow roms have been split into gsm and cmda, due to changes in the radio. You have a cmda device.
The initial build of aosp marshmallow was for both cmda and gms devices. The newest build (the december 24th build) is split into two. Gsm version has been released but cmda version needs more work.
So you will have to download the 6th december build which was unified. Or the lollipop builds.
Lollipop builds have a different thread and a different link.